For the first time, automatic emergency braking is not a feature carmakers can choose to fit — it is a federal requirement. The National Highway Traffic Safety Administration (NHTSA) created a new Federal Motor Vehicle Safety Standard, No. 127, in a final rule published May 9, 2024 (89 FR 39686). The rule mandates automatic emergency braking (AEB) systems, including pedestrian AEB (PAEB), on light vehicles, and it spells out what an AEB system is expected to do rather than leaving the term to manufacturer interpretation.

NHTSA's own summary of the rule states both the mechanism and the purpose in plain terms, and it is worth quoting directly because it draws the line between AEB and ordinary driver braking.

"An AEB system uses various sensor technologies and sub-systems that work together to detect when the vehicle is in a crash imminent situation, to automatically apply the vehicle brakes if the driver has not done so, or to apply more braking force to supplement the driver's braking. This final rule specifies that an AEB system must detect and react to an imminent crash with both a lead vehicle or a pedestrian."— NHTSA, FMVSS for Automatic Emergency Braking Systems for Light Vehicles, source

Why the rule exists, and what it requires

FMVSS 127 did not arrive on its own initiative. The final rule states that it fulfills a mandate under the Bipartisan Infrastructure Law (BIL) directing the Department of Transportation to promulgate a rule requiring that all passenger vehicles be equipped with an AEB system. That statutory origin matters for reading the standard: the agency was directed to make AEB universal on passenger vehicles, and the rule's structure — a performance standard applied across light vehicles, including the pedestrian-detection requirement — is the agency's response. The stated purpose is to reduce the number of deaths and injuries from crashes in which drivers do not apply the brakes, or do not apply enough braking power to avoid or mitigate a crash, and to reduce the consequences of those crashes.

The rule's two detection requirements are the heart of it. An FMVSS 127 system must detect and react to an imminent crash with a lead vehicle — the rear-end collision case — and with a pedestrian, which requires a sensing and reaction capability that works on a much smaller, less radar-reflective object that can enter the path laterally. By writing pedestrian detection into the standard rather than treating it as an optional add-on, NHTSA set a performance floor that covers both the most common crash type and one of the most lethal for vulnerable road users. The rule expresses these as performance requirements the system must meet under defined test conditions, not as a particular sensor suite, which leaves manufacturers free to meet the bar with camera, radar, or fused approaches.

The dates that govern it

Two dates anchor the standard. The final rule was published in the Federal Register on May 9, 2024, and became effective on July 8, 2024 — the date the rule itself takes legal force. Compliance, however, is phased: the rule sets a later date by which the AEB and PAEB performance requirements must be met across newly manufactured light vehicles, giving manufacturers a lead time to engineer and validate systems to the standard's test criteria. NHTSA subsequently published a correction and reopened aspects of the rulemaking, which is a normal part of a major performance standard's life cycle; the underlying mandate — AEB and pedestrian AEB on light vehicles — is the through-line.

For a reader trying to separate the rule from the marketing, the precise points are these. FMVSS 127 is a binding federal standard, not a voluntary commitment like the earlier industry agreements on AEB. It requires the system to act in crash-imminent situations against both a lead vehicle and a pedestrian. It traces to a specific statutory mandate in the Bipartisan Infrastructure Law. And it is defined by performance — what the system must achieve in test scenarios — rather than by a prescribed hardware list. The authoritative text is the Federal Register final rule at 89 FR 39686, which states the requirement, the purpose, and the legal basis in the agency's own words.

Forward collision warning, and the two-part system

An FMVSS 127 AEB system is not only the braking action; the rule frames AEB as a system of sensing and sub-systems that detect a crash-imminent situation and respond. In practice that pairs automatic braking with a forward-collision-warning element — the alert that prompts the driver to act before the automatic intervention engages — and the standard's performance scenarios exercise both the lead-vehicle and pedestrian cases under defined approach speeds and geometries. The rule's choice to specify performance rather than hardware is deliberate: it sets the outcomes a system must achieve in test, such as avoiding or mitigating a collision with a lead vehicle or a crossing pedestrian within the tested speed range, and leaves manufacturers to meet those outcomes with whatever sensing architecture they validate. That is the same regulatory philosophy NHTSA used for stability control and tire-pressure monitoring — define the capability and the test, not the parts list.

The distinction between FMVSS 127 and earlier AEB efforts is worth stating precisely. Before this rule, AEB on U.S. vehicles spread largely through a voluntary commitment a group of automakers made to NHTSA and the Insurance Institute for Highway Safety, plus AEB credit in the agency's New Car Assessment Program. Those mechanisms drove broad adoption but were not binding safety standards, and they did not uniformly require pedestrian detection. FMVSS 127 converts the capability into a mandatory performance standard with a pedestrian-detection requirement built in, which is the change that matters: a feature that was widely offered becomes a feature that must be present and must meet a defined federal test. For anyone reading a window sticker or a safety claim on a new light vehicle, the rule is the reason "automatic emergency braking" is moving from a selling point to a baseline — and the Federal Register final rule is the document that defines exactly what that baseline must do.