The Minimum Risk Condition: How Autonomous Vehicles Are Programmed to Fail Safely
As automated driving systems advance, international standards and state laws now mandate that vehicles must be capable of independently executing a Minimum Risk Maneuver to reach a safe, stopped state during a system failure.
Share this story
In short
- Level 3 and higher autonomous vehicles must be capable of independently executing a safe stop if their systems fail.
- This stable, stopped state is defined by the SAE J3016 standard as a Minimum Risk Condition (MRC).
- To reach an MRC, the vehicle performs a Minimum Risk Maneuver, relying on redundant sensors and backup computers.
The legal and engineering frameworks governing autonomous vehicles have fundamentally shifted the ultimate burden of safety from human reflexes to software protocols. State legislatures and international standards bodies have mandated that any vehicle operating at Level 3 autonomy or higher must be capable of independently removing itself from traffic when its systems fail. This requirement, formalized as the Minimum Risk Condition (MRC), ensures that a catastrophic sensor failure or an unmapped construction zone results in a controlled stop rather than a high-speed collision.[4][5]
For a consumer evaluating a next-generation vehicle equipped with advanced highway-assist features, this shift materially changes what they are purchasing. A buyer is no longer just acquiring a convenience feature that steers and accelerates; they are buying a predefined emergency protocol. If the driver suffers a medical emergency or simply fails to respond to a takeover prompt, the vehicle's onboard computers are legally and technically obligated to safely halt the car, activate hazard lights, and in some jurisdictions, contact emergency services.[5]
The foundation of this safety net is defined by SAE International's J3016 standard, which serves as the global benchmark for driving automation. Under this taxonomy, the Minimum Risk Condition is explicitly defined as a "stable, stopped condition" that reduces the risk of a crash. This state is the mandatory endpoint of a Dynamic Driving Task (DDT) fallback—the sequence of events that occurs when the automated system can no longer sustain operation.[4]
The distinction between a Level 2 driver-assist system and a Level 3 or Level 4 automated driving system hinges entirely on this capability. As legal scholar Bryant Walker Smith explained in a 2022 interview with The Regulatory Review, the defining characteristic of Level 4 autonomy is that "the automated driving system always achieves a minimal risk condition."
If a system requires a human to steer it to the shoulder during a failure, it remains a Level 2 or Level 3 system. The promise of Level 4 is the guarantee of a safe, autonomous stop.[2]
Reaching that stable state requires the vehicle to execute a Minimum Risk Maneuver (MRM). This is the active, physical process of decelerating, changing lanes if necessary, and bringing the chassis to a halt. Engineering this maneuver is exceptionally complex because the vehicle must safely navigate traffic at the exact moment its primary sensors or computers are experiencing a fault.[1][4]
A January 2026 peer-reviewed study published in MDPI highlighted the specific dangers of executing an MRM during a cascading sensor failure. When a vehicle loses its primary LiDAR or camera feeds at highway speeds, it loses its understanding of the surrounding environment. The vehicle must rely on redundant, secondary sensors to map a safe path to the shoulder without swerving into adjacent vehicles.[1]
To mitigate this, researchers have developed adaptive MRM strategies that generate virtual objects in the vehicle's software to represent areas of unknown risk. By evaluating the time-to-collision and time headway using whatever sensor data remains valid, the vehicle's fallback computer can calculate a conservative braking trajectory. This ensures the vehicle reaches a Minimum Risk Condition even when its perception of the road is severely degraded.[1]
While engineers focus on the physics of stopping, state governments are expanding the legal definition of what constitutes a safe stop. In the United States, the regulatory landscape is fracturing as states implement their own requirements for autonomous operations. A 2025 analysis by CMS Law noted that states like Texas have established specific frameworks for autonomous vehicles, but other states are pushing the requirements further.[3]
Virginia's recently updated Code § 46.2-1420 provides a stringent example of this legal evolution. The statute mandates that if an automated driving system fails, the vehicle must not only achieve a controlled stop, but must also execute a series of post-stop communications. The law requires the "activation of hazard lights on the vehicle," a direct "notification to the remote operations center," and the "initiation of a call for emergency services" if a danger is detected.[5]
This means that a vehicle which safely pulls over but loses its cellular connection may fail to meet the legal standard for a Minimum Risk Condition in certain jurisdictions. The World Economic Forum's Safe Drive Initiative, published in November 2020, anticipated these regulatory challenges, urging policymakers to develop scenario-based frameworks that account for the intersection of physical safety and digital connectivity.[4]
The reliance on connectivity exposes autonomous vehicles to a state of epistemic uncertainty. When a vehicle loses access to high-definition map updates, GPS corrections, or remote operator video feeds, its internal logic is programmed to be highly conservative. Modern safety standards dictate that in the face of such uncertainty, the vehicle must immediately transition to an MRC.[4][6]
In dense urban environments, this conservative programming can lead to systemic deadlocks. If a cellular network outage affects a fleet of robotaxis simultaneously, dozens of vehicles may execute a Minimum Risk Maneuver at the same time. Because the safest immediate action is often to stop in the active lane of traffic rather than attempt a blind lane change, these vehicles can quickly transform from mobility solutions into physical obstructions.[6]
To counter this, fleet operators rely on teleoperations—remote human monitors who can authorize a vehicle to proceed or guide it to a safer location. However, teleoperations cannot replace the onboard MRM capability. If the cellular link drops, the remote operator is blind, and the vehicle must rely entirely on its localized fallback protocols to secure the cabin and its occupants.[6]
For the consumer market, the robustness of the Minimum Risk Condition will dictate the pace of Level 3 and Level 4 adoption. Buyers and fleet operators must trust that the vehicle's worst-case scenario ends in a controlled stop, not a catastrophic failure. The engineering redundancies—backup power, secondary braking circuits, and isolated fallback computers—are the tangible assets that underwrite this trust.[2][6]
For the consumer market, the robustness of the Minimum Risk Condition will dictate the pace of Level 3 and Level 4 adoption.
The next critical threshold for the industry will be the harmonization of these standards. As the National Highway Traffic Safety Administration (NHTSA) evaluates petitions for wider autonomous deployments in 2026, the agency must reconcile the strict physical definitions of SAE J3016 with the expanding communication requirements of state legislatures. Until a unified federal standard emerges, the definition of a safe stop will continue to vary by jurisdiction.[5][6]
Terms to know
- Minimum Risk Condition (MRC)
- A stable, stopped state achieved by an automated driving system to minimize crash risk after a system failure.
- Minimum Risk Maneuver (MRM)
- The automated sequence of braking and steering actions required to bring a vehicle to a Minimum Risk Condition.
- Dynamic Driving Task (DDT)
- All the real-time operational and tactical functions required to operate a vehicle in on-road traffic.
- Operational Design Domain (ODD)
- The specific operating conditions—such as weather, road types, and speeds—under which an automated driving system is designed to function.
- SAE J3016
- The international standard published by SAE International that defines the six levels of driving automation, from Level 0 to Level 5.
Questions readers ask
What is a Minimum Risk Condition (MRC)?
An MRC is a stable, stopped state that an autonomous vehicle must reach when its automated driving system fails or encounters a situation it cannot handle. It is designed to reduce the risk of a crash.
What is the difference between an MRC and an MRM?
The Minimum Risk Maneuver (MRM) is the active physical process of slowing down and steering the vehicle to a safe location. The Minimum Risk Condition (MRC) is the final, stopped state achieved at the end of that maneuver.
Does the driver need to take over during an MRM?
In a Level 4 autonomous vehicle, the system must execute the maneuver and reach the MRC entirely on its own. In a Level 3 vehicle, the system will prompt the driver to take over, but must still be capable of stopping safely if the driver does not respond.
What happens if the vehicle's sensors fail completely?
Vehicles are designed with redundant, secondary sensors and backup computers. If the primary sensors fail, the fallback system uses the remaining data to calculate a conservative braking trajectory and bring the vehicle to a halt.
Different angles
Automotive Engineers
Focus on the physical execution of a safe stop through redundant hardware and software.
For systems engineers, the Minimum Risk Condition is a physics and probability problem. They argue that the vehicle's primary directive must be to shed kinetic energy and reach a stable state without colliding with other objects. This requires immense investment in redundant braking circuits, secondary compute modules, and fallback sensor suites that can take over instantly if the primary system faults. From this perspective, the MRC is successfully achieved the moment the vehicle's velocity reaches zero in a safe location.
State Regulators
Emphasize post-stop communication and liability management.
State lawmakers and departments of motor vehicles view the physical stop as only the first half of the requirement. Regulators argue that an autonomous vehicle stranded on a shoulder remains a hazard if it cannot communicate its status. They mandate that a true Minimum Risk Condition must include automated hazard light activation, immediate alerts to a remote operations center, and the ability to dispatch emergency services if a crash is detected, ensuring the vehicle does not become a permanent obstacle.
Consumer Safety Advocates
Demand absolute transparency regarding when and how the vehicle will surrender control.
Safety advocates stress that the transition to a Minimum Risk Condition must be seamless and entirely independent of human intervention for Level 4 systems. They raise concerns about the 'grey area' of Level 3 autonomy, where a driver might be expected to take over but fails to do so in time. Advocates argue that manufacturers must clearly communicate the limitations of their fallback systems to buyers, ensuring that consumers understand exactly what the vehicle will do if it encounters an unmapped construction zone or a sudden blizzard.
- Systems Engineers
- Prioritize the physical and computational reliability of the fallback maneuver.
- Legal & Regulatory Authorities
- Focus on statutory compliance, liability, and post-stop communication requirements.
- Global Policy Strategists
- Advocate for unified, scenario-based frameworks to prevent fragmented safety standards.
Perspectives this story doesn't cover
- Municipal traffic planners managing the impact of stalled autonomous vehicles in urban centers.
- Insurance actuaries calculating the liability shift from human drivers to automated fallback systems.
Sources
[1]MDPISystems EngineersMinimum Risk Maneuver Strategy for Automated Driving System Under Multiple Conditions of Sensor Failure
Read on MDPI →
[2]The Regulatory ReviewLegal & Regulatory AuthoritiesAutonomous Driving Levels and Minimal Risk Conditions with Bryant Walker Smith
Read on The Regulatory Review →
[3]CMS LawLegal & Regulatory AuthoritiesCMS Expert Guide to Autonomous Vehicles (AVs): Texas, United States
Read on CMS Law →
[4]World Economic ForumGlobal Policy StrategistsSafe Drive Initiative: Creating safe autonomous vehicle policy
Read on World Economic Forum →
[5]Virginia's Legislative Information SystemLegal & Regulatory AuthoritiesCode of Virginia: Chapter 14.2. Automated Driving Systems
Read on Virginia's Legislative Information System →
[6]Factlen Editorial TeamSystems EngineersSynthesis by Factlen editorial team
Read on Factlen Editorial Team →
More in Automotive & Transportation
See all →Robotaxi Safety
Waymo Reports 82 Percent Drop in Injury Crashes Across 271 Million Autonomous Miles
6 sources
Sensor Physics
Why LiDAR Goes Blind in Fog While Automotive Radar Sees Straight Through It
2 sources
Sensor Interference
How Coherent Heterodyne Mixing Prevents Optical Crosstalk in FMCW LiDAR
3 sources
Autonomous Navigation
Urban Canyon Multipath Skews Satellite Fixes by Tens of Meters, Forcing Autonomous Vehicles to Localize via LiDAR Map Matching
8 sources
Comments
Every angle. Every day.
Get Automotive & Transportation stories with full source coverage and perspective breakdowns, free every day.




