Almost every new car sold today can see a stopped vehicle or a pedestrian and brake on its own. When that system works, a catastrophic crash becomes a near miss. When it fails to fire, brakes for a hazard that was never there, or was never installed in the first place, the braking system itself can become the center of the case — and the car keeps a record of exactly what it did. Here is how a medical-legal team reads one, and where the federal rule stands in 2026.
There is a category of catastrophic crash where the human driving is only half the story. The car saw the hazard — a stopped vehicle, a person in a crosswalk — and was supposed to do something about it. Automatic emergency braking, the technology that detects an imminent collision and applies the brakes without the driver touching the pedal, is now standard equipment on the overwhelming majority of new cars. When it works, it is one of the most effective safety systems ever put in a passenger vehicle. When it does not, the failure is measurable, the car often recorded it, and the case can look very different from an ordinary fender-to-fender collision.
This is a primer, from the medical side and the legal side, on how automatic emergency braking figures into a catastrophic injury case — what the federal rule requires, why that rule is not yet in force and may slip further in 2026, and the two very different ways a braking system ends up in the middle of a lawsuit.
Automatic emergency braking (AEB) uses cameras, radar, and sometimes other sensors to detect that a crash is about to happen and to apply the brakes automatically when the driver has not. It usually works alongside forward-collision warning, which alerts the driver first. Most systems also include a pedestrian-detection function designed to recognize a person in the vehicle's path and brake for them.
In April 2024, the National Highway Traffic Safety Administration (NHTSA) finalized Federal Motor Vehicle Safety Standard No. 127, which will require AEB, including pedestrian AEB, on virtually all new light vehicles. The standard sets real performance floors: a vehicle must be able to avoid striking a lead vehicle at speeds up to 62 mph, must apply the brakes automatically to avoid a vehicle collision at speeds up to 90 mph, and must detect and brake for a pedestrian — in daylight and in darkness — at speeds up to 45 mph. NHTSA estimated the rule would save at least 360 lives a year and prevent at least 24,000 injuries a year once fully in effect.
Here is the part most drivers do not know. FMVSS No. 127 is finalized, but its compliance deadline is September 1, 2029 for most manufacturers and September 1, 2030 for small-volume and final-stage manufacturers. Until then, AEB is nearly universal by voluntary industry commitment, not by federal mandate. The systems on the road today were built to the automakers' own standards, and they vary.
The rule has also been contested. The Alliance for Automotive Innovation petitioned NHTSA for reconsideration in 2024, then filed a petition for judicial review in the U.S. Court of Appeals for the D.C. Circuit in January 2025, arguing the standard's high-speed and pedestrian requirements are not practicable on the current timeline. In a status report filed with the D.C. Circuit on March 23, 2026, the Department of Transportation said it is preparing a notice of proposed rulemaking that would amend the standard and extend the compliance lead time — by roughly two years, according to the department's stated rationale of giving manufacturers more time for the harder parts of the test. Important caveat: that is a proposal, not a final action. As of mid-2026 the September 2029 deadline still formally stands, and the amendment has not been issued.
Why does a regulatory timeline matter to an injured family? Because it frames the standard of care. A crash where a vehicle's AEB did not prevent an avoidable collision is not judged against a rule that has not taken effect. It is judged against what the specific system in that specific car was designed and represented to do — and against what independent testing shows comparable systems could do. That is a product question, not a "was the mandate in force yet" question.
The single most useful fact in an AEB case is often already inside the car. Vehicles with advanced driver-assistance systems typically log whether forward-collision warning triggered, whether automatic braking engaged, how hard, and the speed and pedal inputs in the seconds around impact. Some of that lives in the federally regulated event data recorder; some lives in the manufacturer's proprietary driver-assistance logs, which take specialized tools and often a court order to extract.
When Herb Borroto, M.D., J.D., and the litigation team reconstruct one of these crashes, the data and the medicine are read together. The injury pattern establishes the forces the occupants actually experienced; the vehicle data establishes what the car did and did not do to reduce those forces. If the record shows the system never warned and never braked into a collision it was designed to detect, that gap is the case. If it shows the system braked but too late or too little, the question becomes why. And this data is fragile — it can be overwritten when the vehicle is driven, towed, repaired, or sold, which is the same reason the first 24 hours matter so much. The vehicle has to be preserved before its own black box is erased.
The first way a braking system enters a case is when it failed to do its job. The technology is not marketing — the Insurance Institute for Highway Safety (IIHS) has documented that forward-collision warning combined with automatic emergency braking cuts rear-end crashes by roughly half, and a 2025 IIHS analysis found modern systems reduced rear-end crashes by about 49 percent. Pedestrian AEB is associated with a 25–27 percent reduction in pedestrian crash risk and a 29–30 percent reduction in pedestrian injury crash risk. The systems work.
But IIHS has also mapped where they do not. Pedestrian AEB has been far less effective in the dark without street lighting, at speeds of 50 mph and above, and while the vehicle is turning. That distinction is where the case lives. If a pedestrian was struck at 30 mph on a lit street, straight ahead, by a vehicle whose system was built to brake for exactly that scenario — and the data shows it did nothing — a product-liability claim against the automaker or a sensor supplier can proceed alongside the claim against the driver. If the same person was struck at 55 mph on an unlit rural road, the physics and the technology's known limits may point the case entirely at driver conduct instead. The facts decide, and reading them correctly is the whole job. This is often the hidden layer in a pedestrian catastrophic injury case.
The second way is the mirror image of the first — the system brakes hard for a hazard that is not there. This is called phantom braking, and it is not hypothetical. NHTSA's Office of Defects Investigation has opened investigations into inadvertent AEB activation across multiple automakers. In one engineering analysis into certain model-year 2019–2022 Honda vehicles, regulators cited 106 complaints and 475 field reports of the automatic braking system activating when no obstacle was present. Owners of other vehicles have reported cars decelerating sharply from highway speed for no visible reason, and several manufacturers have issued recalls tied to AEB systems misreading ordinary driving conditions as emergencies.
A vehicle that slams on its brakes at 65 mph on an open highway can trigger a rear-end collision or a loss of control — a catastrophic crash caused by the safety system rather than prevented by it. These incidents have been the subject of NHTSA investigations and class-action litigation; in one closely watched case a federal jury found in favor of the manufacturer after it argued the system's limits were disclosed, while other matters remain open. As with any product claim, the outcome depends on the specific vehicle, its defect and recall history, and what the car's data shows it did in the moment. The point for an injured person is simply this: an unexplained hard stop with no obstacle is not necessarily driver error, and the vehicle's own logs may prove it.
Whether the theory is failure-to-brake or phantom braking, the early work is unusually technical:
Because these systems are woven into the broader world of automated driving, the analysis often overlaps with the questions raised in a self-driving car crash, where the vehicle rather than the driver was making decisions. The common thread is the same: modern cars generate a record, and the record is evidence.
If you or someone you love was catastrophically hurt in a crash involving a newer vehicle, three things matter early. First, the vehicle is evidence — its data can show whether a safety system did what it was supposed to, and that data disappears when the car is towed, fixed, or sold. Second, a crash where the car had automatic emergency braking should not be assumed to be a simple driver-error case; the presence, absence, or malfunction of that system can change who is responsible. Third, get in front of an attorney who has actually litigated vehicle data and product-defect theories, not just insurance claims. The federal government has decided this technology is important enough to require on every new car. The cases open now are part of how that promise gets enforced.
Not yet. NHTSA finalized Federal Motor Vehicle Safety Standard No. 127 in 2024, which will require automatic emergency braking, including pedestrian detection, on virtually all new light vehicles. But the compliance deadline is September 1, 2029 for most manufacturers, and September 1, 2030 for small-volume and final-stage manufacturers. In a March 2026 status report to the D.C. Circuit, the Department of Transportation said it is preparing a proposed rulemaking that would amend the standard and extend the compliance lead time. As of 2026, most new cars have AEB voluntarily, but it is not yet federally mandated.
Potentially, yes. If a vehicle was equipped with automatic emergency braking that should have detected the hazard and either did not activate or activated inadequately, the crash may support a product-liability claim against the automaker or a component supplier, in addition to any claim against an at-fault driver. The analysis turns on what the system was designed to do, what the vehicle's own data shows it did, and whether a defect or a reasonable design limitation explains the failure. It is fact-specific and depends on the vehicle and the jurisdiction.
Phantom braking is when an automatic emergency braking or forward-collision system brakes hard for a hazard that is not there. NHTSA's Office of Defects Investigation has opened investigations into inadvertent AEB activation across several automakers, and drivers have reported vehicles decelerating sharply at highway speed with no obstacle present. A sudden unwarranted stop can cause a rear-end collision or a loss of control, and such events have been the subject of NHTSA investigations and class-action litigation. Whether a specific incident supports a claim depends on the vehicle's data, the defect history, and the facts of the crash.
Often, yes. Vehicles with advanced driver-assistance systems typically log whether forward-collision warning fired, whether automatic emergency braking engaged, and the vehicle's speed and braking in the seconds around a crash. Some of this is captured in the event data recorder and some in the manufacturer's own driver-assistance logs. That record can show whether the system did what it was supposed to, and it can be overwritten or lost when a vehicle is towed, repaired, or sold, which is why preserving the vehicle early matters.
The full case-type overview for serious passenger-vehicle crashes.
The in-vehicle data that shows whether the brakes engaged.
Who is responsible when the computer was making the decisions.
Where pedestrian AEB helps — and where it does not.
Why the vehicle and its data have to be preserved immediately.
How speed, throttle, and braking in the final seconds get read.
The vehicle is evidence, and its data disappears fast. We move to preserve it, extract what the safety systems recorded, and evaluate whether the technology did what it was supposed to. Herb Borroto, M.D., J.D., reads the medicine. Alex Alvarez evaluates the case. Free, confidential.
Free, confidential case review. We respond within 24 hours.
No fees unless we recover compensation for you.
Your information is confidential. Submitting this form does not create an attorney-client relationship.
What Happens Next
If your information appears to qualify you for help, a lawyer or someone from their team will reach out to you. If you don't hear back within seven days, please speak with another law firm — every legal matter has a filing deadline, and waiting too long can cost you the right to recover.
