No-Contact and Blind Spot (Phantom Driver) Accidents

A driver drifts into your lane. You swerve, clip a guardrail, and total your car. The other vehicle never touched you, and it kept going before you could get a plate number. Or picture the other common version: a car merges out of a blind spot, forces you onto the shoulder at highway speed, and disappears before you've stopped shaking. In both situations, the driver who caused the wreck isn't standing next to you when police arrive, and there's no one to name on a claim form.

Insurers and courts use a few overlapping terms for this. When the at-fault vehicle never made contact and can't be identified, it's usually called a no-contact accident or, in policy language, a phantom vehicle claim. When the trigger is a driver who changed lanes without checking a blind spot, that's a lane-change or blind spot crash, and it can end with contact (a sideswipe) or without it (you swerved to avoid the sideswipe and hit something else instead). This guide covers both, because the same practical problem sits under each one: the person you'd normally sue is gone, unnamed, or was never touched by your car at all.

Why these crashes happen so often

Lane-change and blind spot collisions aren't unusual. Vehicles equipped with blind spot monitoring were involved in 14% fewer lane-change crashes of any severity and 23% fewer lane-change crashes with injuries than the same models without the technology, based on a 2018 analysis of police-reported crashes across 26 states by the Insurance Institute for Highway Safety.¹ IIHS researcher Jessica Cicchino estimated that if every passenger vehicle on the road had blind spot detection as effective as the systems studied, roughly 50,000 police-reported crashes a year could be prevented.¹ That gap is a rough measure of how often a driver changes lanes without ever seeing the car sitting next to them.

Large trucks carry an outsized share of this risk because their blind spots, often called no-zones, are bigger and sit in places car drivers don't expect. In a federal sample of 967 large truck crashes gathered for the Large Truck Crash Causation Study, roughly 14% involved a truck driver's failure to adequately survey the roadway, including blind spots, before a maneuver like a lane change.² Mirror gaps, trailer length, and driver distraction stack on top of that, and a passenger car can sit invisible to a truck driver for long stretches of highway.

True no-contact crashes don't show up as their own clean category in crash databases, because police and insurers track contact events, not near-misses that force someone off the road. The closest available data is hit-and-run statistics generally, which capture both a driver who strikes something and flees and a driver whose reckless move causes a crash before ever touching another vehicle. In 2022, hit-and-run crashes killed 2,972 people, 7% of all traffic deaths and the highest share ever recorded, according to the AAA Foundation for Traffic Safety.³ The total dipped slightly in 2023, but the share of all deaths involving a driver who fled kept climbing.³ Pedestrians and cyclists absorb a disproportionate share of that risk: about 1 in 4 pedestrian injuries and 1 in 5 cyclist injuries in 2023 happened in a hit-and-run crash, and more than 70% of hit-and-run deaths involved a pedestrian or cyclist.³ Fewer than half of hit-and-run drivers are ever identified.³

Why the fight moves to your own insurer

When police can't identify the other driver, or the other driver was never part of a collision you could photograph or measure, there's no liability policy to file a claim against. The claim you're left with runs through your own uninsured motorist (UM) coverage, the same coverage built for crashes with drivers who carry no insurance at all. That distinction matters more than it should: one in three U.S. drivers were uninsured or underinsured in 2023, up ten percentage points since 2017, according to the Insurance Research Council.⁴ Mississippi (28.2%), New Mexico (24.1%), and Washington, D.C. (23.1%) had the highest uninsured rates that year; Maine (5.7%), Utah (6.2%), and Idaho (6.4%) had the lowest.⁴ A phantom driver is, for claim purposes, uninsured by definition, since nobody has identified an insurer to bill.

Filing a UM claim over a phantom vehicle isn't automatic, though. Policies and state statutes build in safeguards against fraud, since "an unidentified car ran me off the road" is also exactly what someone would say after causing a single-car accident on their own. That's where state rules start to diverge sharply, and where a lot of legitimate claims get denied on a technicality.

The physical contact divide

Historically, most states required physical contact between the phantom vehicle and the insured's car before UM coverage would pay anything. The logic was blunt: contact leaves marks, and marks are hard to fake. New York still requires it outright. Under Insurance Law § 5217, coverage for an unidentified driver applies only if the injury arose out of physical contact of the motor vehicle causing the injury with the claimant or with the vehicle the claimant occupied.⁵ California's statute reads almost the same way: Insurance Code § 11580.2(b) conditions phantom-vehicle coverage on the bodily injury having arisen out of physical contact of the automobile with the insured or with an automobile that the insured is occupying.⁶ California courts have stretched what counts as contact, though. In Inter-Insurance Exchange of the Automobile Club v. Lopez, a fleeing driver struck one car, which was pushed into the insured's car; the court held that force transmitted through the middle vehicle satisfied the contact requirement even though the phantom vehicle never touched the insured's car directly.⁷

Other states went the opposite direction by statute. Missouri amended § 379.203.1 in 1982 to state that uninsured motorist coverage exists whether or not physical contact was made between the uninsured motor vehicle and the insured or the insured's motor vehicle.⁸ Washington and Wisconsin took a middle path: no contact is required, but the claimant has to produce corroborating evidence and hit specific deadlines. Washington's RCW 48.22.030 requires the facts to be corroborated by evidence other than the insured's own testimony, and requires the accident to be reported to law enforcement within 72 hours.⁹ Wisconsin's version is more detailed. Under § 632.32(2)(bh), a phantom motor vehicle is one that made no physical contact and whose operator and owner can't be identified, and § 632.32(2)(g)2 conditions coverage on corroboration by someone other than the insured, a police or DOT report within 72 hours, and a sworn statement filed with the insurer within 30 days.¹⁰

A third group of states arrived here through the courts rather than the legislature. Massachusetts' Supreme Judicial Court held in Surrey v. Lumbermens Mutual Casualty Co. that an insurer's own physical-contact policy language was unenforceable because it conflicted with the state's uninsured motorist statute.¹¹ Ohio never wrote a contact requirement into its UM statute, but insurers put one into their policies anyway, until the Ohio Supreme Court's 1996 decision in Girgis v. State Farm. In that case, an unidentified driver swerved into the insured's lane and forced her off the road; the court replaced the contact requirement with a corroborative-evidence test, holding that an insured could recover without contact if independent evidence supported the phantom vehicle's role in the crash.¹² Twenty years later, in Smith v. Erie Insurance Co., the same court went further and held that the insured's own contemporaneous statements, made in a police report, medical record, or 911 call, can themselves count as corroboration if those statements include supporting detail rather than a bare assertion.¹³ Whether your own statements can help prove your own claim is exactly the kind of question a specific state's rule answers, and this hub page can't.

Deadlines and paperwork that can sink a claim before it starts

Notice deadlines are where phantom vehicle claims most often die, and they run tighter than the deadlines most people associate with car accidents generally. Wisconsin and Washington both require a police report within 72 hours of the crash.^{10 9} Wisconsin adds a second deadline on top of it: a sworn statement to your own insurer within 30 days describing what happened.¹⁰ Other states use a 24-hour reporting window instead of 72. Miss either deadline, and an insurer has grounds to deny the claim regardless of how clearly the crash wasn't your fault. None of this is optional paperwork. It's a condition of coverage, and courts generally enforce it as written unless a state's case law has carved out an exception for late notice that didn't prejudice the insurer.

The evidence that actually moves these claims

Because there's no phantom driver to depose and no plate to trace, these claims live or die on corroborating evidence gathered close to the moment of the crash. The categories that consistently hold up:

• Independent eyewitnesses who saw the other vehicle's movement
• A 911 call made from the scene and preserved by the dispatch center
• The responding officer's crash report
• Dashcam or nearby surveillance footage
• Physical evidence such as skid marks or transferred paint showing an evasive maneuver happened
• Event data recorder ("black box") data pulled from your own vehicle

NHTSA's rule at 49 CFR Part 563 governs what those recorders capture, and a recent update extended the pre-crash recording window from 5 seconds at 2 Hz to 20 seconds at 10 Hz, giving investigators a longer, more detailed picture of the moments before impact.¹⁴ Medical records and the initial police report carry weight beyond their obvious use, too. Ohio's Smith decision turned on exactly this kind of evidence, treating a claimant's own consistent, detailed statements to police and medical staff as corroboration in their own right.¹³ The lesson travels well outside Ohio: what you say, and how much detail you give, in the first hour after the crash tends to matter more than what you say to an adjuster three weeks later.

What to do in the first hours

Move to safety if you can, then call 911 immediately, even if nothing touched your car. A recorded call establishes a timestamp and an official record that a phantom vehicle was involved, often the single most useful piece of corroboration you'll have. Get the names and phone numbers of anyone who saw the other vehicle, not just anyone who stopped to help afterward. Photograph the scene, your damage, and any skid marks or debris before traffic clears them away. If your car or a nearby business has a dashcam or security camera, ask about preserving the footage before it's overwritten. Then notify your own insurer promptly and ask exactly what your state requires for a phantom vehicle or no-contact claim, including the reporting window and the corroboration standard. Those answers are state-specific, and the page for your state is one click from this one.

When the identity surfaces later

Sometimes the driver isn't a true phantom, just unidentified at the scene. A traffic camera, a witness who caught a plate number after the fact, or a trucking company's own fleet telematics can turn a no-contact claim into an ordinary liability claim days or weeks later. Apprehended hit-and-run drivers are disproportionately caught close to their own zip code, which is part of why a doorbell camera or a canvassing officer turning up a name after the fact is common enough to plan for.³ Identification is a better outcome for you procedurally, since it puts a real insurer on the other side instead of your own UM adjuster, but it doesn't erase the reporting deadlines you already had to meet on the front end. Keep pursuing both tracks, your own UM claim and any lead on the other driver, until one of them resolves.

Getting help

Phantom vehicle claims turn on details that don't look important at the scene: which statute your state uses, whether your corroboration will hold up, whether a missed deadline is fatal or excusable. An attorney who handles these claims regularly can usually tell within minutes whether your evidence meets your state's standard, and can deal with an insurer that's often motivated to find a technical reason to deny. You can find one through thatcarhitme.com's legal directory. Statutes of limitations for these claims vary by state and by whether you're suing under a policy or pursuing a separate injury claim, so don't wait to find out where you stand.

This article is general information, not legal advice.

Sources

1. Insurance Institute for Highway Safety, "Effects of blind spot monitoring systems on police-reported lane-change crashes" (Cicchino, Traffic Injury Prevention, 2018), https://www.iihs.org/topics/bibliography/ref/2143

2. Federal Motor Carrier Safety Administration, Large Truck Crash Causation Study, Report to Congress, https://ai.fmcsa.dot.gov/downloadFile.axd?file=LTCCS+reportcongress_11_05.pdf

3. AAA Foundation for Traffic Safety, "Understanding the Increase in Fatal Hit-and-Run Crashes: Prevalences of Crashes, Injuries, and Deaths in the United States, 2017-2023," https://aaafoundation.org/research/understanding-the-increase-in-fatal-hit-and-run-crashes-prevalences-of-crashes-injuries-and-deaths-in-the-united-states-2017-2023/

4. Insurance Research Council, "Uninsured and Underinsured Motorists: 2017-2023," https://www.insurance-research.org/news-releases/one-three-drivers-are-either-uninsured-or-underinsured-us-exposing-themselves-and

5. New York Insurance Law § 5217, https://www.nysenate.gov/legislation/laws/ISC/5217

6. California Insurance Code § 11580.2, https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=INS&sectionNum=11580.2.

7. Inter-Insurance Exchange of the Automobile Club v. Lopez, 238 Cal. App. 2d 441 (1965), https://law.justia.com/cases/california/court-of-appeal/2d/238/441.html

8. Missouri Revised Statutes § 379.203, https://revisor.mo.gov/main/OneSection.aspx?section=379.203

9. Revised Code of Washington § 48.22.030, https://app.leg.wa.gov/rcw/default.aspx?cite=48.22.030

10. Wisconsin Statutes § 632.32, https://docs.legis.wisconsin.gov/statutes/statutes/632/iv/32?view=section

11. Surrey v. Lumbermens Mutual Casualty Co., 384 Mass. 171 (1981), https://masscases.com/cases/sjc/384/384mass171.html

12. Girgis v. State Farm Mut. Auto. Ins. Co., 75 Ohio St. 3d 302 (1996), https://law.justia.com/cases/ohio/supreme-court-of-ohio/1996/1996-ohio-111.html

13. Smith v. Erie Ins. Co., 2016-Ohio-7742, summary via Court News Ohio, https://www.courtnewsohio.gov/cases/2016/SCO/1116/151419.asp

14. National Highway Traffic Safety Administration, "Event Data Recorders," 49 CFR Part 563, https://www.nhtsa.gov/fmvss/event-data-recorders-edrs