49 CFR Part 573: defect and noncompliance reports (the safety recall process)
A manufacturer that learns of a safety defect must notify the regulator and owners and remedy the defect; software recalls run through the same process.
Draft mapping. Drafted by the Register's agents from the rule's text and not yet confirmed by a person. It is the Register's reading, not legal advice: whether and how the rule applies to you is a question for counsel.
Controls this rule maps to
Required by the text The rule's text requires a measure that is this control, or plainly includes it. Implied A binding rule whose purpose needs this control, but whose text does not name it. The Register's reading. Recommended A voluntary standard or guidance recommends it; nothing binds you to it. Proposed Appears in a proposed rule or proposed provision that is not yet in force.
| Control | Strength | Where in the rule, and why | Confidence | Missing or failed in |
|---|---|---|---|---|
| Organizational recovery process C-R4 | Required by the text | the recall is the organizational recovery process with regulator visibility (Waymo, Zoox) | high | 1 case |
Cases that cite this rule
| Case | How the case cites it | Outcome |
|---|---|---|
| Zoox smoke scene 2026 | Part 573 safety recall process | Stopped by the operator's control |
| Waymo construction zones 2026 | Part 573 recall process | Stopped by the operator's control |
| Tesla FSD reduced visibility | NHTSA defect investigation authority | Ended in harm |