Classes / Fleet & Robotics class / Rover Ops Department
Rover Ops Track: Autonomy, Field Maintenance and Drones · Rank 5 coursework · Module 1 of 3 · about 40 min
Crash reporting for automated vehicles
NHTSA's SGO applies to identified manufacturers, developers and operators with defined ADS and Level 2 ADAS crash conditions. It was first issued in 2021 and amended in 2021, 2023 and 2025. It does not apply to every individual consumer or unrelated operator.
The current overview retains a thirty-second engagement window as one condition, alongside named-entity and crash criteria that differ for ADS and Level 2 ADAS. It describes five-day notice for the most severe report types and monthly reporting for certain others. Actual requirements and notice definitions need the responsible entity's current review, not a universal deadline assumed from a course.
For a fleet team this means data must be preserved and incidents escalated fast. A team lead needs to know who files the report, what logs are kept, and how long it takes to pull them.
Treat every incident as both a compliance event and a learning event. Review what the system saw, what it did and what the human did, then change the procedure if needed.
We distinguish a reporting threshold from a causal finding. NHTSA's current overview says the Standing General Order applies to specifically named entities, not every consumer or unrelated operator. The thirty-second engagement condition is one part of coverage; the actual ADS or Level 2 crash criteria and reporting provisions also matter.
Reported totals are not normalized crash rates. Exposure, operating domain, telemetry access, awareness and possible duplicate reports affect interpretation. A higher reported count cannot by itself establish that one system is less safe. A filed initial report can contain incomplete or unverified information without being a final finding about cause.
Worked example, fictional data review: two fleets report different counts, but neither dataset gives comparable distance, conditions or reporting completeness. The counts cannot establish a fair safety ranking. A separate incident log records engagement inside the time window but leaves the actual entity and crash criteria unassessed.
Practice, on paper: we preserve invented event timing, system state, source and unknowns for the responsible compliance team. Our self-check distinguishes internal escalation from an actual legal filing. We access no real crash data and submit no report.
Sources
Module quiz
10 questions, 8 correct to pass. You'll see what you missed and why, and you can retake it.