FMVSS Considerations for Vehicles with Automated Driving Systems: Volume 2
archive: archived pipeline: cataloged verified
Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)
Summary
This report, titled *FMVSS Considerations for Vehicles with Automated Driving Systems: Volume 2*, addresses the regulatory barriers preventing the compliance verification of Automated Driving System-dedicated vehicles (ADS-DVs) under existing Federal Motor Vehicle Safety Standards (FMVSS). The research was motivated by the emergence of SAE Level 4 or 5 vehicles designed to operate exclusively via automated systems without manually operated driving controls. Current FMVSS regulations and test procedures inherently assume the presence of a human driver and traditional controls, creating unintended barriers for ADS-DVs. The study aims to develop "technical translations"—modifications to regulatory text and test procedures that maintain the original engineering performance intent while removing manual control-specific restrictions. The research team, led by the Virginia Tech Transportation Institute for the National Highway Traffic Safety Administration (NHTSA), analyzed 18 specific FMVSS: nine crash avoidance standards (Nos. 101, 103, 104, 110, 111, 113, 124, 125, and 126) and nine crashworthiness standards (Nos. 207, 208, 210, 214, 216a, 219, 222, 225, and 226). The methodology involved reviewing regulatory language and test procedures to identify barriers, such as references to steering wheels, driver seats, or manual brake application. The team developed translation options and evaluated their feasibility through engagement with stakeholders and Subject Matter Experts (SMEs). The scope was strictly limited to ADS-DVs lacking manual controls; dual-mode vehicles with manual backups were excluded as they can currently comply with existing tests. Key findings indicate that many regulatory barriers in the 100-series crash avoidance standards stem from assumptions about human operation, particularly regarding driver references, service brake application, and visibility. Technical translations often involved clarifying regulatory text to replace "driver" references with ADS-specific terminology or retaining performance requirements while removing manual control mandates. For visibility standards (Nos. 103, 104, 111, 113), options included retaining performance requirements for ADS-DVs or specifying requirements only for vehicles with manual controls. In the 200-series crashworthiness standards, the focus was on occupant protection regardless of seating role. Translations frequently involved mirroring passenger-side requirements to the left-front outboard seat for ADS-DVs, as the primary distinction between front seats in conventional vehicles is the presence of manual controls. Test procedure adaptations included using "if present" language for steering columns and expanding requirements for auditory alerts and telltales to account for non-human operators. The significance of this work lies in providing NHTSA with a structured set of options to verify the safety compliance of ADS-DVs without compromising engineering performance. The report concludes that while many barriers can be addressed through straightforward clarification, test procedures may require further refinement as ADS technology evolves. The findings support the regulatory adaptation necessary for the deployment of fully automated vehicles, ensuring that safety standards remain relevant and enforceable for innovative vehicle designs. The report also notes limitations, including the lack of full legal verification for the proposed options and the exclusion of unconventional seating configurations, which require further research.
Key finding
Technical translation options were developed for 18 FMVSS to remove regulatory barriers for ADS-dedicated vehicles, primarily by clarifying regulatory text to replace human-centric assumptions with ADS-specific requirements.
Methodology
review
Provenance
The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | rosap | — | — | 2 | 2026-05-23 |
| archive | success | — | — | — | 1 | 2026-05-23 |
| extract | success | cached | — | — | 2 | 2026-06-10 |
| clean | success | — | — | — | 1 | 2026-06-01 |
| chunk | success | — | — | — | 1 | 2026-06-01 |
| embed | success | — | — | — | 1 | 2026-06-02 |
| enrich | success | — | — | — | 1 | 2026-05-23 |
| promote | success | — | — | — | 1 | 2026-05-23 |
| summarize | success | llm | qwen3.6-27b-prismaquant | summ-v5 | 3 | 2026-06-10 |
| tag | success | vector_similarity | — | — | 19 | 2026-06-11 |
| verify | success | — | — | — | 2 | 2026-06-10 |
Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.
Topics
Ranked by relevance to this paper. Hover a topic for its definition.
Information type
What kind of knowledge this paper contributes, grouped by family — independent of topic (what it is about) and method (how it was studied).
- Applied Guidance: standards test procedures, design guidelines
- Methodological Resource: validation psychometrics