AEB basics: detecting and reducing collision risk
Follow the chain from a detected obstacle to warning, braking and a possible stop.
- Distinguish warning from automatic braking
- Explain why speed affects stopping distance
- Recognize the limits of collision prevention
Detect a possible conflict
Automatic Emergency Braking looks for a collision threat in the vehicle’s path. Depending on the system, camera and radar observations help estimate the obstacle’s position and motion. Detection alone is not a reason to brake: the system needs to assess whether the obstacle presents a relevant conflict.
A stationary car beside the road and a stationary car directly ahead are different situations. Their position relative to our path matters.
Remember: AEB needs context about the path, not just the presence of an object.
Understand warning and intervention
A forward-collision warning alerts the driver. AEB can additionally request braking when the assessed threat warrants intervention. These are different functions, and the exact sequence varies between vehicles. Our animation separates detection, warning and braking so the decision chain is easy to inspect.
In the demo, the obstacle is marked first. A warning appears as the distance closes, followed by brake lights and falling speed.
Remember: A warning asks the driver to respond; automatic braking changes the vehicle’s motion.
Connect speed to stopping distance
During a delay before braking, a moving car continues to cover distance. Once braking starts, stopping distance depends on speed and available deceleration. In a simplified constant-deceleration model, braking distance is v² / (2a), with speed in m/s and positive deceleration magnitude a. Road grip and system response affect real outcomes.
At 10 m/s with 5 m/s² deceleration, ideal braking distance is 10 m. At 20 m/s with the same deceleration, it is 40 m. Delay distance must be added separately.
Remember: Doubling speed quadruples ideal braking distance when deceleration is unchanged.
Interpret the outcome honestly
AEB may avoid an impact, or it may only reduce the impact speed. Available space, visibility, target detection and braking capability all affect the result. A successful stop in a teaching example is not evidence that a real vehicle will stop in every condition. The driver still needs to observe traffic and act.
Compare the two starting speeds in the animation. The faster example leaves less space after stopping; that is an illustration, not a vehicle performance prediction.
Remember: Collision mitigation and collision avoidance are not the same outcome.
Engineering notes: architecture, limitations and efficiency
What the system can and cannot do
AEB combines perception, threat assessment and a brake request. The system estimates whether an object is in the path, predicts a possible conflict, decides whether to warn or intervene, and requests braking subject to vehicle dynamics, actuator limits and driver-state rules.
Known limitations
- Detection and classification are uncertain, especially for unusual objects, crossing traffic, small targets or partially occluded road users.
- Available deceleration depends on tyre grip, road surface, brake temperature, vehicle load and system response time.
- AEB is generally designed for defined operating scenarios; it is not a universal collision guarantee or a substitute for hazard perception.
When problems can occur
- Dirty, damaged or misaligned sensors can reduce detection quality.
- Rain, glare, darkness, snow, spray, curves and low-contrast targets can weaken perception or cause the feature to become unavailable.
- A system may warn without braking, brake later than expected, or stop mitigating when the target is outside its validated path or speed range.
AEB is a safety function, not a fuel-saving feature. Avoiding a crash can prevent major energy and repair costs, but normal AEB operation should not be evaluated by fuel economy. Unnecessary interventions would be undesirable, so threat assessment is designed to balance timely braking with false-alarm control.
- Build a scenario matrix for true and false obstacles
- Model reaction delay, tyre-road friction and deceleration limits
- Measure precision, recall and intervention timing
Connect the lesson to the animation.
Watch the warning appear before braking. Replay with “Increase starting speed” and compare the remaining gap after the stop.
Revisit the AEB demoApply what you learned.
Answer all three questions correctly to complete this basic lesson. You can review the explanations and retry as often as you like.
Continue into engineering.
Build on these basics with implementation, experiments and validation. More detailed engineering material is being developed.
Preview future technical topics
- Explore TTC and threat assessment
- Model braking limits and response delay
- Evaluate collision scenarios and failure cases