A recall is the end of a process, not the beginning. The mechanism that feeds NHTSA defect signals long before a Part 573 recall report is Early Warning Reporting (EWR), the system created by the Transportation Recall Enhancement, Accountability, and Documentation (TREAD) Act and codified at 49 CFR Part 579. Where Part 573 governs the formal recall, Part 579 governs the upstream data — the warranty claims, field reports, and casualty data that can flag a problem before it crystallizes into a determined safety defect.

The regulation states its own scope in a single sentence that maps the three statutory streams it implements.

"This part sets forth requirements for reporting information and submitting documents that may help identify defects related to motor vehicle safety and noncompliances with Federal motor vehicle safety standards, including reports of foreign safety recalls and other safety-related campaigns conducted outside the United States under 49 U.S.C. 30166(l), early warning information under 49 U.S.C. 30166(m), and copies of communications about defects and noncompliances under 49 U.S.C. 30166(f)."— 49 CFR 579.1, source

The three reporting streams

Part 579's scope statement names the three obligations precisely, each tied to a subsection of 49 U.S.C. 30166. The first, the early-warning information itself (30166(m)), is the periodic data submission most people mean by "EWR": manufacturers report, on a recurring basis, incidents involving deaths and injuries, property-damage claims, warranty claims, consumer complaints, and field reports relating to specified systems. The data is tabulated by vehicle make, model, model year, and system or component category, which lets NHTSA's analysts watch for a category that is generating an unusual cluster of claims. The reporting thresholds and the level of detail scale with a manufacturer's size — larger manufacturers report more granular data than very small ones — but the principle is constant: hand the agency the leading indicators, not just the lagging recall.

The second stream is foreign safety recalls (30166(l)). If a manufacturer conducts a safety recall or similar safety campaign on a vehicle or equipment item outside the United States, and a substantially similar product is sold in the U.S., Part 579 requires the manufacturer to report that foreign campaign to NHTSA. The logic is direct: a defect that triggered a recall abroad is a signal about products in the domestic fleet. The third stream is communications (30166(f)), implemented at 49 CFR 579.5, which requires each manufacturer to furnish NHTSA a copy of all notices, bulletins, and other communications — including technical service bulletins, warranty and policy-extension communiqués, and product-improvement bulletins — sent to more than one dealer, owner, or purchaser regarding a defect. That is how the agency sees the service bulletins automakers issue to their dealer networks.

Why EWR exists, and how it connects to recalls

The TREAD Act was enacted after a high-profile tire-and-vehicle defect episode in which the pattern of claims was visible in manufacturer data well before any recall. EWR is the structural response: it requires the data to flow to the regulator continuously, so the agency is not dependent on a manufacturer's own determination to learn that something is wrong. The purpose section of Part 579 states the aim plainly — to enhance motor vehicle safety by specifying the information and documents manufacturers must report so that potential defects can be identified. The data feeds NHTSA's defect-screening and investigation process; an EWR cluster or a foreign recall can be the trigger that opens a defect investigation, which can in turn lead to a Part 573 recall.

Two distinctions keep the picture accurate. First, EWR is not itself a recall, and an EWR submission is not an admission of a defect — it is raw signal data, reported on a schedule, that may or may not indicate a safety problem. Second, EWR runs in parallel with, and feeds into, the formal recall machinery: Part 579 surfaces the signals, the agency's investigations weigh them, and Part 573 governs the recall that may follow. Much of the aggregated EWR data is made available publicly, which is why analysts and journalists can watch claim trends by make and model. The authoritative description of what manufacturers must report, and under which statutory authority, is the text of 49 CFR Part 579 — the codified form of the TREAD Act's early-warning mandate.

How the data is structured — and why size matters

Part 579 organizes EWR reporting by product category — light vehicles, medium-heavy vehicles and buses, motorcycles, trailers, child restraints, and tires each have their own reporting subpart — and within each, by component or system categories such as steering, braking, electrical, power-train, and others. That categorization is what makes the data analyzable: NHTSA can watch the rate of, say, braking-related death-and-injury claims for a given make, model, and model year and compare it against the broader fleet. The regulation also scales the obligation to manufacturer size. Large-volume manufacturers must report the detailed, categorized quarterly data; smaller manufacturers below specified production thresholds report a reduced set, typically limited to incidents involving deaths. The design reflects a deliberate trade-off — the agency wants granular leading indicators from the manufacturers whose products dominate the fleet, without imposing the same reporting burden on a low-volume specialty builder.

One precise point often gets blurred: an EWR death-and-injury claim is a claim or notice a manufacturer received, not an adjudicated finding that the product caused harm. The data is a signal, weighted by category and volume, and its value is statistical — a cluster that stands out against the baseline is what prompts a closer look. That is why analysts treat EWR data as a screening tool rather than a verdict, and why NHTSA pairs it with defect investigations before any recall determination. The throughline from Part 579 to Part 573 is the agency's defect-screening process: early-warning data, foreign-recall reports, and service-bulletin copies flow in continuously; investigations weigh them; and a determined safety defect triggers the five-working-day recall report. The early-warning system is the front end of that pipeline, and its requirements are fixed in the text of 49 CFR Part 579.