Federal Vehicle Safety Standards and Recalls

Classification and applicable standards

The first inquiry identifies the vehicle or equipment and its intended use under Chapter 301. The manufacturer then determines the applicable FMVSS in Part 571 for the vehicle category and manufacture date. ADS capability is not a stand-alone substitute for that standards analysis. A steering-wheel-free design, passenger configuration, or software-controlled braking system can raise different questions under particular standards. [1, § 30102; 2]

The distinction also separates federal design law from Texas road operation. Texas § 545.455 requires federal compliance as one operating condition. A state authorization therefore does not promise that NHTSA has approved the vehicle's certification or every design feature. Conversely, federal certification does not supply every state commercial-service permission. [3, § 545.455(b)(3)]

Certification and temporary exemptions

Section 30115 requires the relevant manufacturer or distributor certification, with labeling and related requirements in Part 567. The certification rests on the applicable statutory and regulatory framework; it is not a representation that accidents are impossible. The manufacturer should maintain the engineering and test basis supporting the actual configuration. Later changes require examination of the responsibilities attaching to the actor making them. [1, § 30115; 4]

Section 30113 and Part 555 provide temporary exemption procedures for specified statutory grounds, subject to the required findings and limitations. An application does not authorize noncompliant sales while it is pending. A grant should be read for the covered manufacturer, vehicles, standards, quantities, conditions, and duration. It should not be advertised as an exemption from all federal vehicle law or as NHTSA endorsement of autonomous performance generally. [1, § 30113; 5, §§ 555.5 through 555.9]

Vehicles without conventional controls require close reading of the actual standards and any amended requirements or granted relief. The fact that a requirement historically assumed a human interface does not allow the manufacturer to disregard its text. Equally, absence of a steering wheel does not by itself establish that every FMVSS exemption is necessary. The particular design and effective standard control.

Defects and noncompliance after deployment

Chapter 301 separates a safety-related defect from noncompliance with an applicable standard. Sections 30118 through 30120 establish notification and remedy responsibilities in the circumstances specified by law. Part 573 addresses defect and noncompliance reporting, including the report required within five working days after the relevant determination. Part 577 governs notifications. A manufacturer should identify the correct trigger and responsible entity rather than wait for multiple crashes before evaluating a known safety issue. [1, §§ 30118 through 30120; 6, § 573.6; 7]

An over-the-air change may be a remedy, a performance improvement, or another modification. The delivery mechanism does not decide whether recall reporting and notice are required. When software corrects a safety defect or noncompliance, the manufacturer must analyze the same statutory framework, including affected vehicles, the condition being corrected, remedy effectiveness, and required communications. A release note alone does not establish completion of every duty. [1, §§ 30118 through 30120; 6; 7]

Crash reporting is a separate obligation

NHTSA's Third Amended Standing General Order 2021-01 imposes defined crash-reporting requests on served entities. Its scope, knowledge conditions, qualifying events, deadlines, updates, and submission instructions must be read separately from recall rules. A crash report is not itself a defect determination, and a company's absence from one reporting category does not resolve every other reporting obligation. [8]

The fleet and manufacturer should establish how incident information reaches the person responsible for evaluating the order. Contracts can address cooperation, but the order's duties attach according to its terms and service. A support contractor's initial report may be important even before root cause is known. Information gaps should be handled through the order's instructions rather than silently delaying a required initial submission. [8, Requests 1 through 3]

Evidence and change control

A useful vehicle safety record connects the hardware configuration, software version, calibration, ODD, test results, incident data, and corrective action. If an update changes braking or fallback behavior, the company should assess both compliance and safety-related defect implications. That is a recommended implementation approach to the cited duties, not a newly enacted general federal approval procedure.

Policy strategies and proposed standards can guide planning, but a proposal does not amend an effective FMVSS merely by being announced. The compliance file should distinguish effective text, a published proposal, a petition, a granted exemption, an agency investigation, and nonbinding guidance. This prevents a forward-looking product roadmap from being mistaken for present legal authority. [1; 2; 5]