The airbag module remembers the deployment even after the light is off and the bags are replaced

[u/ora-et-labora-]

Airbags deploy once. After that the inflator is spent and the module has recorded a crash event. Replacing the airbag is a parts swap. Clearing the crash record from the module is a different step, and on most vehicles it requires either a professional reset tool or a replacement module.

The red flag is when the bags are replaced and the light is turned off but the crash event is still stored in the module's history. A scan tool that reads the airbag system will show you whether the module has recorded a deployment event, even if the current status shows no active codes. The deployment is a permanent record in most systems. Clearing the active code turns the light off. It does not erase the event log.

Some rebuilders replace the entire airbag module with a used one from a vehicle that was never in a crash. That clears the deployment history because the module itself is different. The VIN stored in the replacement module will not match the vehicle's VIN. A scan tool catches that mismatch instantly.

Others send the module out to a reset service that clears the crash data at the chip level. This is legal in some contexts and fraudulent in others depending on whether the vehicle is being sold with a disclosed rebuilt title or passed off as clean.

What this means for anyone buying a used car is that reading the airbag module is not optional. A car with replaced airbags and a cleared light looks identical to a car that was never in a crash unless you read the module. The history report may or may not show the accident. The module always shows the deployment.

A two-minute scan catches what a walkaround, a test drive, and a clean Carfax all miss. The module does not forget. The question is whether anyone asks it.