After a car accident in Washington, D.C., one of the first things many people ask is: “What happens if the crash was partly my fault?” You may be thinking about your medical expenses, lost wages, property damage, or how you’ll recover financially—and wondering whether you can still move forward and seek financial compensation through a personal injury claim.
Washington, D.C. follows contributory negligence law, which means if you were found to have been even 1% at fault for an accident, the insurance company and other party (if it goes to court) can dismiss your case. In other words, if the at-fault driver’s legal team or the driver’s insurance company can successfully argue that you share just a small part of the blame, you may be left paying the costs on your own.
If you are concerned about your part in an accident and worry you will be barred from compensation, seek legal support from an experienced attorney. At Regan Zambri Long, our personal injury lawyers have helped clients push back against unfair blame and win complex car accident claims—even in cases involving partial fault.
Contact us today to schedule a free consultation
Contact Us Form
Complete this form and our team will get back to you as soon as possible
What Is Contributory Negligence in a DC Car Accident Case?
In the United States, there are two forms of liability under personal injury law. The applicable forms of liability are:
Most states follow comparative negligence laws, which, in essence, claim that if, for example, one party is 80% responsible for the accident and the other is only 20% liable, both can still recover damages according to their share of fault.
Conversely, under contributory negligence, if one person was in any way negligent in the accident, they cannot collect any damages from the at fault party. That’s why it’s important not to admit fault at the scene or during conversations with insurance companies. Currently, only Alabama, Maryland, North Carolina, Virginia, and Washington, DC. all follow contributory negligence.
Can You Still Win a DC Car Accident Case With Partial Fault?
If your DC car accident lawyer can prove that the other driver was acting with willful disregard for safety—such as driving drunk, texting behind the wheel, or speeding through a red light—you may still be able to seek compensation, even if you made a small mistake.
For example, let’s say you forgot to use your turn signal, but the other driver was drunk and speeding. Your attorney could argue that their reckless behavior was the main cause of the accident—and that your own actions didn’t rise to the level of “negligence” under the law.That’s why it’s so important to speak with a qualified D.C. car accident attorney experienced in partial fault cases and DC personal injury law.
Free Consult Today!
What to Do If You Might Be Partially Responsible for a Car Accident
Even if you think you made a mistake, here’s how to protect your right to recover damages:
Avoid admitting fault – Don’t apologize or guess what happened at the accident scene. In the heat of the moment, you may just start saying things to witnesses and police that may not even be totally accurate. Let the investigation speak for itself.
Document everything – Take photos, collect contact info from witnesses, and file a police report. Physical evidence from the accident scene is critical for showing who was truly at fault.
Get medical attention – Even minor injuries can become serious. Medical records play an important role in both your health and the value of your personal injury case.
Call a car accident lawyer – Before speaking to the other driver’s insurance company, call a personal injury lawyer who understands the insurance company investigation process. Your personal injury lawyer will manage all communications and work to protect your right to a fair settlement.
How Can a DC Car Accident Lawyer Help If I Was Partially at Fault?
At Regan Zambri Long, our team investigates every detail of your car accident case. We know how insurance companies assign fault—and how they try to use D.C.’s strict rules against you. We look at the evidence, talk to witnesses, and may bring in accident reconstruction experts to show which parties involved really caused the car crash.
Our attorneys will:
Investigate the accident and gather evidence
Secure police reports and witness statements
Review video footage (if available)
Consult accident reconstruction experts
Manage all communications with car insurance companies
Fight back against any unfair blame
Negotiate or litigate to maximize your financial recovery
We’ll work to help you recover damages for:
Medical expenses (past and future)
Lost wages and lost earning capacity
Pain and suffering
Vehicle repair or total loss
Emotional distress
Permanent disability or disfigurement
Long-term care for significant injuries
Increased insurance premiums resulting from the car accident
Car Accident Attorneys At Regan Zambri Long are Here to Help
Regan Zambri Long is dedicated to protecting the rights of injury victims in Washington, D.C. With more than two decades of experience, our car accident attorneys have taken on government entities and giant corporations in the Washington, D.C. Metro area to seek compensation our clients deserve following a catastrophic car accident.
Our personal injury and accident law firm is composed of fierce trial lawyers who have secured record-setting verdicts and settlements for our injury clients. No car crash case is too complex for our attorneys.
Whether you were involved in a car accident or truck accident or were hurt by a negligent party in Washington, D.C., Maryland, or Virginia, our legal team will put in the time, energy, and compassion needed to help you move forward.
Have you or your loved one sustained injuries in Washington DC, Maryland or Virginia? Regan Zambri Long PLLC has the best lawyers in the country to analyze your case and answer the questions you may have.
Cookie Consent
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Cookie Preferences
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
UserWay is an AI-powered accessibility widget that scans a website for WCAG and ADA accessibility issues and gives visitors on-page tools to adjust contrast, font size, navigation, and other display settings.
Set on the addtoany.com domain to remember which sharing services the visitor uses, so the share menu lists those services first.
9999 days
CallRail is a call tracking and analytics service. Its script swaps the phone numbers shown on a page and stores the visitor's referrer, landing page and session ID, so phone calls and form submissions can be attributed to the marketing source that brought the visitor to the site.
Stores a randomly generated form capture ID used to link a submitted form to this visitor session.
180 days
calltrk_session_id
Stores a randomly generated visitor session ID so that a later phone call or form submission can be matched to this visit.
180 days
calltrk_referrer
Stores the referring URL that brought the visitor to the site, so the traffic source of a phone call can be reported.
180 days
calltrk_landing
Stores the first page the visitor landed on, so the page that led to a phone call can be reported.
180 days
calltrk_override_src
Stores a traffic source supplied in the page URL, used to override the detected source and start a fresh tracking session.
180 days
calltrk_google_experiments
Stores the Google experiment IDs seen on the pages visited, so a phone call can be attributed to a test variant.
180 days
calltrk_nearest_tld
Written briefly to work out the broadest domain that will accept cookies when tracking across subdomains, then removed once that check completes.
3600 days, deleted as soon as the check finishes
CleanTalk offers effective spam protection and website security solutions to enhance user experience.
Name
Description
Duration
spbc_is_logged_in
Dashboard. Flag defines if a user was logged in.
Session
spbc_firewall_pass_key
The flag defines if the Security Firewall was passed.
Session
spbc_cookies_test
Cookie to test cookies so we know that everything working properly
Session
ct_sfw_
Group of cookies used for our SpamFireWall technology.
Session
ct_
Group of cookies used for storing dynamic variables from browser
Session
ct_pointer_data
Used in order to detect spam and improve the website's security. Does not store visitor specific data.
session
apbct_
Group of cookies which are set from backend and contain information about the current user
Session
apbct_cookies_test
Сookie to validate other cookies, so they can’t be spoofed.
Session
ct_timezone
Used in order to detect spam and improve the website's security.
Session
ct_ps_timestamp
Used in order to detect spam and improve the website's security. Does not store visitor specific data.
session
ct_has_scrolled
This cookie is used to distinguish between humans and bots.
session
ct_fkp_timestamp
Used in order to detect spam and improve the website's security. Does not store visitor specific data.
session
ct_check_js
Used in order to detect spam and improve the website's security.
session
apbct_antibot
This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
session
spbc_2fa_passed
Dashboard. Flag defines if Two-Factor Authentication was passed.
Session
spbc_log_id
Dashboard. User identification.
Session
spbc_timer
Dashboard. Time spent on the page.
Session
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
Facebook Pixel is a web analytics service that tracks and reports website traffic.
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
FPGCLGB
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
_gac_gb_
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
_gcl_gb
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
_gcl_gs
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
_gcl_aw
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 Days
Conversion
Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads.
90 days
__Secure-3PSID
Targeting cookie. Used to profile the interests of website visitors and display relevant and personalised Google ads.
2 years
__Secure-1PAPISID
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-3PSIDTS
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-1PSID
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-1PSIDCC
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-3PAPISID
Profiles the interests of website visitors to serve relevant and personalised ads through retargeting.
2 years
AEC
AEC cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user's knowledge.
6 months
ADS_VISITOR_ID
Cookie required to use the options and on-site web services
2 months
__Secure-3PSIDCC
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
__Secure-1PSIDTS
Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user.
2 years
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utma
ID used to identify users and sessions
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
Google Maps is a web mapping service providing satellite imagery, real-time navigation, and location-based information.
Registers a unique ID on mobile devices to enable tracking based on geographical GPS location.
1 day
VISITOR_INFO1_LIVE
Tries to estimate the users' bandwidth on pages with integrated YouTube videos. Also used for marketing
179 days
PREF
This cookie stores your preferences and other information, in particular preferred language, how many search results you wish to be shown on your page, and whether or not you wish to have Google’s SafeSearch filter turned on.
10 years from set/ update
YSC
Registers a unique ID to keep statistics of what videos from YouTube the user has seen.
Session
DEVICE_INFO
Used to detect if the visitor has accepted the marketing category in the cookie banner. This cookie is necessary for GDPR-compliance of the website.
179 days
LOGIN_INFO
This cookie is used to play YouTube videos embedded on the website.