← Latest papers
⚡ electrical engineering

Risk Assessments for Evasive Emergency Maneuvers in Autonomous Vehicles

This paper introduces a novel, traceable verification and validation framework that integrates HARA, STPA, and Finite State Machine modeling to systematically assess Evasive Minimum Risk Maneuvers in autonomous vehicles, demonstrating through a T-junction case study that this unified approach achieves 100% hazard and parameter-space coverage while significantly improving collision avoidance rates compared to traditional methods.

Original authors: Aliasghar Arab, Milad Khaleghi, Koorosh Aslansefat

Published 2026-04-30
📖 5 min read🧠 Deep dive

Original authors: Aliasghar Arab, Milad Khaleghi, Koorosh Aslansefat

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are teaching a robot driver how to handle a sudden, terrifying emergency: a giant truck has just blocked the road ahead, and you are barreling toward it at high speed. What should the robot do? Slam on the brakes? Swerve wildly? Or is there a "Plan B" if the swerve fails?

This paper is about building a super-smart safety checklist to make sure autonomous vehicles (self-driving cars) can answer those questions correctly, especially in the most dangerous, "edge-case" situations where normal rules might fail.

Here is the breakdown of their new method, explained simply:

The Problem: Three Missing Pieces

The authors say that current safety checks for self-driving cars are like trying to build a house with only a hammer, only a saw, or only a blueprint. You need all three working together. They identified three gaps in how we currently test these cars:

  1. The "Two-Tool" Gap: Engineers usually use two different safety methods (called HARA and STPA) separately. It's like having a map and a compass but never using them together to navigate. The paper creates a single workflow that forces them to work as a team.
  2. The "Movie Scene" Gap: Safety checks often look at a snapshot in time (a hazard exists) or the end result (a crash happened). They miss the movie in between—the split-second moments where the car tries to dodge, fails, and then has to switch to a "damage control" mode. The paper adds a Finite State Machine (FSM), which is like a flowchart that maps out every possible "scene" the car can go through, from "Oh no!" to "I dodged it!" or "Okay, let's minimize the crash."
  3. The "Guessing Game" Gap: Traditionally, engineers pick test scenarios by guessing what might go wrong (e.g., "Let's test it on a rainy day"). This paper replaces guessing with a systematic generator that mathematically ensures they test every possible combination of speed, road grip, and timing, leaving no stone unturned.

The Solution: A Unified Safety Pipeline

The authors combined these three tools into one seamless pipeline:

  • Step 1 (HARA): Identifies what could go wrong (e.g., "The truck blocks the road").
  • Step 2 (STPA): Identifies how the car's brain might make a mistake (e.g., "The car swerves too late" or "The car swerves when it shouldn't").
  • Step 3 (FSM): Maps out the story of the event. If the car swerves and succeeds, it goes to "Safe." If it swerves and fails, it immediately transitions to "Mitigation" (trying to hit the truck at a glancing angle instead of head-on) or "Emergency Stop."

The Real-World Test: The T-Junction Truck

To prove this works, they tested a specific scenario: A self-driving car approaching a T-junction where a large truck has suddenly blocked the path.

They ran 1,880 computer simulations (a massive number compared to the usual handful) covering every possible speed, road condition (dry, wet, icy), and timing.

Here is the surprising discovery they made:
Because of the specific geometry of a T-junction, the car is almost always in a "binary" situation. It's either:

  • Full Avoidance: There is enough time and space to swerve or stop completely.
  • Unavoidable Crash: There is absolutely no time to stop or swerve; a crash is inevitable.

The "Middle Ground" is almost non-existent. The paper found that the "intermediate" option—where the car tries to swerve but fails, so it has to switch to a "damage control" mode—only exists in 1.9% of the possible situations. In other words, on a T-junction, you either make it or you don't; there is rarely a "maybe" zone. This is a physical reality that only their high-resolution testing could reveal.

The Results: Why This Matters

When they compared their new "Agile Evasive Maneuver" (swerving) against the old "Emergency Stop" (braking only):

  • Success Rate: The swerving strategy avoided collisions 81% of the time, compared to only 45% for braking alone.
  • Impact Speed: When a crash was unavoidable, the swerving strategy reduced the impact speed from 18.9 km/h down to 9.0 km/h. Think of this as the difference between hitting a wall at highway speed versus a slow jog; it drastically reduces the damage.
  • Coverage: Their method tested 100% of the possible hazards and scenarios. Traditional methods only tested about 1% (leaving 99% of the dangers unexplored).

The Bottom Line

This paper doesn't just say "self-driving cars are safe." It provides a traceable, mathematical proof that a specific safety feature (swerving to avoid a crash) works better than just braking, and it does so by mapping out every single possible way the system could fail or succeed.

They proved that by combining hazard analysis, control theory, and state-flow mapping, we can finally test self-driving cars with the same rigor as a pilot training for an engine failure, ensuring that when the unexpected happens, the car knows exactly which "scene" to play next.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →