Autonomous Vehicle Safety Distance Calculator

Calculate the minimum safe following distance for an autonomous vehicle — incorporating system latency, braking capability, and perception uncertainty into a single ISO 22737-aligned safety figure.

UDHY Tools / AV Safety Distance Calculator

⚙️ Input Parameters

Ego Speed (km/h)

Lead Speed (km/h)

Ego Decel (m/s²)

AV: 4–8 m/s²

Lead Emerg. Decel (m/s²)

Worst-case: 8–10

System Latency (ms)

Full pipeline

Perception Uncertainty (m)

Safety Margin

📊 Results

🚗

Enter parameters and click Calculate to see the minimum safe following distance for your AV’s safety case.

Minimum Safe Following Distance

—metres

Latency travel distance—

Braking distance differential—

Perception uncertainty—

Safety margin applied—

Time headway equivalent—

Why AV Safety Distance Matters

What This Calculates

The minimum safe gap between your AV and the vehicle ahead, combining three independent components: travel during system latency, braking distance differential between ego and lead vehicle, and position uncertainty from your perception system. All three must be summed — missing any one produces an unsafe result.

When to Use It

Writing a Safety Case for LTA, NHTSA, or UNECE regulatory submission
Setting forward collision avoidance thresholds in your planning module
Evaluating impact of latency improvements on required headway
ISO 22737 compliance documentation for low-speed AVs
Comparing headway requirements across different speed profiles

Formula

d_latency = v_ego × t_system d_brake = max(0, v_ego²/2a_ego − v_lead²/2a_lead) d_min = (d_lat + d_brake + σ) × safety_factor headway = d_min / v_ego ISO 22737 minimum: 1.5s

Practitioner note (Dr. Dilip Limbu, Moovita): The most underestimated variable is system latency. Engineers often account for perception inference time but forget the CAN bus delay to the brake actuator (typically 15–25ms additional) and the actuator’s physical response lag. Always use measured end-to-end latency from physical testing — not just inference time — for a safety-case-compliant result.

Built by Dr. Dilip Kumar Limbu · Co-Founder, MooVita · Former Principal Scientist, A*STAR · UDHY Engineering Tools

Limitations & Assumptions

Important engineering note: This calculator provides an engineering estimate and educational reference. It is not a substitute for vehicle-specific safety validation, hazard analysis, regulatory approval, or a formal safety case. Actual required following distance depends on the vehicle dynamics, actuator response, road conditions, ODD, sensor performance, control architecture and applicable regulatory requirements.

FAQs on AV Safety Distance

1. What is the minimum safe following distance for an autonomous vehicle?

There is no single fixed answer — the minimum safe following distance for an AV depends on vehicle speed, system pipeline latency, braking capability, and perception uncertainty. At 60 km/h with a typical 150ms system latency and 6 m/s² deceleration, the ISO 22737-compliant minimum is approximately 18–25 metres, applying a 1.5× safety factor. This calculator computes the precise figure for your specific system parameters.

2. How does system latency affect AV safety distance?

System latency is the time between an event occurring (e.g. the lead vehicle braking) and your AV's actuators physically responding. During this window, your vehicle continues at full speed. At 60 km/h with 150ms total pipeline latency, your vehicle travels 2.5 metres before any braking begins — this becomes part of the required following distance. Reducing pipeline latency directly reduces required headway, which is why perception and planning compute time matter for safety, not just accuracy.

3. What does ISO 22737 specify for AV following distance?

ISO 22737 (Low-Speed Automated Vehicles in Public Areas) recommends a minimum time headway of 1.5 seconds as the baseline safety margin for automated vehicles in mixed traffic. This corresponds to different physical distances depending on operating speed — at 20 km/h, 1.5s headway is approximately 8 metres; at 60 km/h, it is approximately 25 metres. The 1.5× safety factor in this calculator directly implements this ISO recommendation.

4. What is the difference between stopping distance and safety distance?

Stopping distance is the total distance required to bring a vehicle to a complete stop from a given speed, including reaction time and braking distance. Safety distance (following distance) is the minimum gap to maintain from the vehicle ahead to ensure a collision can be avoided if the lead vehicle performs an emergency stop. Safety distance accounts for the worst-case braking differential between the two vehicles, perception uncertainty, and the safety factor required for regulatory compliance — all of which stopping distance alone does not.

5. How does perception uncertainty affect safe following distance?

Perception uncertainty is the positional error in your sensor stack's estimate of the lead vehicle's location. A GPS/camera fusion system with 0.5m position uncertainty means the lead vehicle could actually be 0.5m closer than your system believes. This uncertainty must be added directly to the required following distance. Better sensor fusion (LiDAR map-matching, tight camera-radar-GPS fusion) reduces perception uncertainty and can meaningfully reduce required headway at the same speed.

6. Can an AV safely follow more closely than a human driver?

Potentially yes — but only if the AV's total system reaction time is meaningfully faster than a human's. Human reaction time averages 750ms; a well-engineered AV pipeline can achieve 100–200ms total latency. At 60 km/h, this difference (550ms) corresponds to approximately 9 metres less required following distance. However, this advantage is only realised if the AV's perception uncertainty is also low, its deceleration capability matches or exceeds human emergency braking, and the system safety factor meets regulatory requirements.