Airbag Modules and the Event Data Recorder: What a Crash-Data Clear Actually Erases (and What It Does Not)

Who this is for

You are in the right article if any of these describe you:

• Your airbag light is on after a deployment, you have been told the module has to be "reset," and you want to know what that actually erases
• You have read that clearing an airbag module "deletes the black box" and you want a straight answer
• You are a shop that gets asked to reset modules and you want a defensible policy for when to say no
• You are an owner rebuilding a salvage or theft-recovery vehicle and you need to know what your obligations are
• You are in the middle of a claim or a lawsuit and someone told you to just get the module cleared

That last one is the reason this article exists. The honest version of the story is not complicated, but almost nobody writes it down, and the gap gets filled with two equally wrong beliefs: that a repair reset scrubs a legally significant record, or that the module holds nothing of interest at all. Neither is true.

What an event data recorder actually is

An Event Data Recorder, or EDR, is not a separate box bolted somewhere in the car. On the overwhelming majority of light vehicles it is a function hosted inside the airbag control module — the same unit variously badged ACM, SRS module, SDM (GM), RCM (Ford), ORC (Stellantis), SRS unit (Toyota, Honda), or airbag control unit. The restraint computer is already sampling acceleration, sensing occupants and watching the powertrain bus in order to decide whether to fire anything. The EDR function simply retains a short slice of that data when a qualifying event occurs.

In the United States, EDRs are federally defined. If a light vehicle is equipped with one, 49 CFR Part 563 specifies what it must record, at what rate, for how long, and how the data must be retrievable. That regulation is administered by the National Highway Traffic Safety Administration. Two consequences follow, and both surprise people:

First, EDRs are not mandatory — the format is. Part 563 does not force a manufacturer to install an EDR. It says that if one is installed, it has to record a defined data set in a defined way. In practice the point is academic: NHTSA has estimated that well over 90 percent of new light vehicles sold in the U.S. carry an EDR, a figure the agency has cited repeatedly in its rulemaking and research work. Assume your vehicle has one.

Second, the recording is short and narrow. Part 563 sets out roughly fifteen required data elements for any equipped vehicle — things like vehicle speed, engine throttle position, service brake status, safety belt status for the driver, airbag deployment timing, and the change in forward velocity. Pre-crash elements are captured over about five seconds before the event at half-second intervals. The crash pulse itself is recorded over a fraction of a second. There is no rolling video, no GPS track, no audio, and no continuous driving log in a Part 563 EDR.

That last point is worth repeating to anybody who has watched too much television. The airbag module is not a dashcam. It is a five-second snapshot plus a crash pulse.

Where the standards come from

The data-element structure did not appear from nowhere. Automotive engineering bodies had been standardizing event recording long before the federal rule; SAE International has published EDR-related recommended practices covering data definitions and retrieval that manufacturers and tool vendors work from, and the federal rule leans on that groundwork. Crash-research organizations were early users: the Insurance Institute for Highway Safety has used recorded crash-pulse data alongside its physical testing for years, precisely because a recorded delta-V is far more objective than an estimate made from bent metal.

The scale of the problem those groups work on is not small. NHTSA's own reporting puts U.S. traffic fatalities on the order of 40,000 a year, with millions of injury crashes on top of that. When that many events are being reconstructed by insurers, police, and researchers, an objective five seconds of vehicle data is enormously valuable — which is exactly why the rules around who can touch it exist.

The three different things people call "the crash data"

Almost every argument about airbag modules comes from collapsing three separate things into one phrase. Pull them apart and the whole topic gets simple.

1. Hard crash codes and the deployment record

When the module fires a squib — an airbag inflator or a seatbelt pretensioner — it writes a deployment command record and sets hard, non-erasable-by-scan-tool crash DTCs. This is deliberate. The module is designed to latch itself into a fault state so that a car cannot be put back on the road with a restraint system that has already been used and never inspected. A generic scan tool will read those codes and refuse to clear them; the airbag lamp stays on; and on most platforms the module will not arm normally again.

This is the thing that gets "cleared" in a repair. It is a lock-out, not a legal artifact.

2. The EDR event record

Separately, the module stores the Part 563 event data — the speeds, the belt status, the delta-V, the pre-crash interval. That record is what a crash reconstructionist or insurer wants. It is retrieved with a Bosch CDR-type tool (the Crash Data Retrieval system is the common commercial standard, with manufacturer-specific alternatives) either through the vehicle's diagnostic connector or by direct connection to the module itself. Retrieval produces a signed report.

Downloading an EDR is a forensic procedure with its own tooling, its own training, and its own chain-of-custody expectations. It is not something a repair reset performs, and it is not something a repair reset is designed to interact with.

3. Ordinary DTCs

Then there are the boring ones: an open squib circuit, a shorted clockspring, a seat-position sensor out of range, a low-voltage code from a weak battery. These come and go, clear normally with a scan tool once the fault is fixed, and are the entire subject of most airbag-light complaints that have nothing to do with a crash. If your light came on and you were never in a collision, start with our guide on what an airbag light after an accident actually indicates and work backward from the code.

The distinction almost everyone gets wrong

Here is the sentence that should be pinned to the wall of every shop:

Returning a module to a functional state is not the same act as erasing a legally significant EDR record, and neither one is a substitute for the other.

A bench reset is aimed at item 1 above. It removes the deployment lock-out so a module that is otherwise healthy can be reinstalled in a vehicle that has been properly repaired. Whether any part of the Part 563 event record survives, is overwritten, or is left untouched is module-, generation-, and platform-specific — and that variability is exactly why nobody honest will tell you a reset "wipes the black box." On some platforms the event buffer is written once and locked. On others it holds multiple events with the oldest overwritten. On others still, the reset path and the EDR buffer live in different regions of memory entirely and the reset does not go near it.

The correct professional posture is therefore not "we will erase it" or "we will preserve it." It is: if the record matters to anybody, image it first, before any work is done, using the right tool and the right person. Once that download exists as a signed report, the question of what a repair does to the module's memory stops being a live issue.

In eighteen years I have never once had a legitimate customer ask me to make crash data disappear. Legitimate customers ask me to make the light go out on a car they have already repaired properly. The moment somebody starts asking what the reset erases rather than what it fixes, that is the job you decline and the conversation you write down.

— Independent collision-electronics technician, 18+ years SRS and restraint systems (anonymized)

Who can lawfully access EDR data

Ownership and access are governed by a mix of federal rules and a state-by-state patchwork, and the short version is this: the data belongs to the vehicle owner, and getting it out of the car generally requires the owner's consent or legal process.

At the federal level, Congress addressed EDR ownership and access in the Driver Privacy Act, which establishes that data recorded by an EDR in a passenger motor vehicle belongs to the owner or lessee, and limits retrieval by others to a defined set of circumstances — owner consent, a court order or authorized judicial or administrative process, certain safety-research uses with identifying information removed, and emergency medical response. The regulatory framework surrounding vehicle data more broadly is administered through NHTSA, and the eCFR text of the recording requirements themselves sits in Part 563.

On top of that, a majority of U.S. states have their own EDR statutes, and they are not uniform. Some require written owner consent before retrieval. Some carve out insurer access when it is a condition of a claim. Some address law-enforcement access explicitly. Some are silent. The practical result for an owner is that you cannot reason about your rights from a single national rule — and the practical result for a shop is that you should never be the party making the call.

Consumer-privacy bodies have been paying increasing attention to vehicle data generally. The Federal Trade Commission has taken a public interest in how connected-vehicle data is collected and shared, and Consumer Reports has published extensively on automotive data privacy for owners. EDR data is the oldest and most tightly defined slice of that broader picture.

Why insurers and reconstructionists care so much

Because it settles arguments. A reconstruction built from crush measurement, skid marks and witness statements produces a range. An EDR download produces numbers: the vehicle was at this speed, the throttle was here, the brake switch was on or off, the belt was buckled or it was not, and the change in velocity was this much.

That objectivity cuts both ways, which is why owners should not assume the data is their enemy. It exonerates people constantly — the driver who was accused of speeding and was not, the driver who was said to have never braked and did. It is also a fraud-detection tool, and fraud is not a small problem: the National Insurance Crime Bureau puts the annual cost of insurance fraud in the United States on the order of hundreds of billions of dollars, spread across every line of coverage. Staged-collision and exaggerated-injury claims are precisely the cases where a five-second data snapshot changes the outcome.

If you are working through a claim on a damaged or stolen-recovered vehicle, the sequencing and paperwork side is covered in our guide to insurance claims involving module replacement.

Where we stop — the line a repair shop should not cross

This is the part of the article that is a policy statement, not a technical one.

Auto Module Lab does not service airbag or SRS modules from a vehicle that is involved in an active insurance claim, active litigation, or an open investigation. Not for $75, not for any amount. If that describes your situation, the answer is the same every time: stop, and have the EDR imaged by a qualified crash-data analyst before anything is done to the module.

Proof of ownership is required. Restraint-system work is security-adjacent, and we treat it the same way we treat immobilizer and key work. Registration or title in the name of the person ordering, or documented shop authorization from the owner, is the baseline.

We do not accept "make the data go away" as a job description. A customer whose vehicle has been properly repaired wants a functioning restraint system and a dark airbag lamp. That is a repair. Anything framed around the record itself rather than the vehicle's condition is not work we take, and we will say so plainly rather than quietly declining.

If you are unsure, image first. A CDR download is cheap relative to a disputed claim, it is non-destructive, and once the report exists nothing that happens to the module afterward can be characterized as spoliation. There is no downside to doing it in the right order. There is significant downside to doing it in the wrong one.

None of this is legal advice, and none of it substitutes for asking your own attorney or claims adjuster. It is simply how a bench shop stays on the right side of an easy line.

Repair reset versus forensic EDR download

	Crash-data clear (repair)	EDR imaging (forensic)
Purpose	Return a locked module to a serviceable state	Produce an evidentiary record of the event
Who performs it	Module repair technician on the bench	Trained crash-data analyst / reconstructionist
Tooling	Bench programmer, direct memory access to the module	Bosch CDR-type system or OEM equivalent, signed report
Access point	Module out of the vehicle, on the bench	Vehicle diagnostic port, or direct-to-module cabling
What it targets	Hard crash DTCs and the deployment lock-out	The Part 563 event record
Output	A module that arms and self-tests normally	A time-stamped report admissible in a claim or case
Legal footing	Ordinary vehicle repair, owner-authorized	Owner consent, court order, or statutory authority
Correct order	After imaging, if imaging is needed at all	Always first when the event is disputed
Our position	Offered at $75 for clean, owner-verified repairs	Not performed here — use a qualified analyst

What a crash-data clear actually does on the bench

With the legal ground covered, the mechanics are straightforward.

The module arrives, gets identified by part number and hardware revision, and is powered on a regulated bench supply. We read what is there before changing anything. Then the deployment lock-out and hard crash DTCs are cleared through the module's own service path, the unit is self-tested to confirm it arms normally and reports no residual internal faults, and it ships back. On a healthy module this is a fast, unglamorous, entirely repeatable job at $75 flat, with return shipping selected and paid at checkout starting from $24.95. The full process walk-through lives in our complete guide to airbag and SRS crash-data clearing, and the service itself is the airbag / SRS module crash data clear.

Which modules reset and which do not

Not every module is resettable, and it is worth understanding the three categories:

Resettable. The large majority of airbag control modules from the mid-1990s onward store the crash state in rewritable memory — EEPROM or a flash region — that can be returned to its pre-event value on the bench. This is the normal case.

Effectively single-use. A minority of modules, mostly older or specific to particular manufacturers, latch the deployment state in a way that no service path unlocks. The unit is functionally consumed by the deployment and has to be replaced. When we find one, we say so; nobody pays for a reset that cannot be performed.

Hard-locked by hardware damage. A module that took physical or electrical damage in the event — a cracked board, a blown driver stage, corrosion from airbag-deployment residue or from water intrusion — is not a data problem. It is a hardware problem, and clearing codes on it accomplishes nothing. This is where a bench evaluation at $150 earns its keep: the unit is powered, probed, and diagnosed properly rather than guessed at, and you get a real answer about whether it is worth repairing. Our write-up on what a bench evaluation finds that a scan tool cannot covers that process in detail.

A deployed squib circuit needs hardware, not software

This one catches people out constantly. If the module reports a deployed or open squib circuit, that is the module correctly telling you a pyrotechnic device has been used and is no longer there electrically. A used airbag inflator, a fired seatbelt pretensioner, and a spent side-curtain initiator are all one-shot devices. No amount of code clearing puts propellant back in a canister.

So the sequence is: replace the fired pyrotechnics and repair the wiring first, then clear the module. Clearing first simply means the fault comes back the instant the module runs its next self-test, and you have paid for a reset you now need to repeat. If you are trying to decide whether the module is even worth keeping, the economics are laid out in our reset versus replacement cost comparison.

Cost and decision framing

Three numbers frame the whole decision.

A crash-data clear is $75 on a module that is intact and belongs to a vehicle with no active claim, litigation, or investigation. A bench evaluation is $150 when you do not yet know whether the module is healthy — hardware damage, water intrusion, a suspect board, or a unit that has already failed a reset attempt somewhere else. Return shipping is chosen and paid at checkout, from $24.95. Against those, a dealer-supplied replacement airbag control module, VIN-programmed and installed, commonly runs well into the high hundreds and past a thousand dollars on premium platforms — which is why the reset path exists at all.

The decision tree is short:

1. Is the vehicle in an active claim, lawsuit, or investigation? If yes, stop. Get the EDR imaged by a qualified analyst. Come back afterward if the repair still makes sense.
2. Can you prove ownership? If not, that is where it ends.
3. Have the fired pyrotechnics and damaged wiring been replaced? If not, do that first.
4. Is the module physically intact? If you are not sure, order the evaluation rather than the reset.
5. If all four are clean, the reset is a $75 bench job and your restraint system comes back online.

Frequently asked questions

Does clearing my airbag module erase the black box data? A repair reset targets the crash codes and deployment lock-out, not the Part 563 event record, and whether any part of that record is affected varies by module, platform and generation. That is precisely why the correct answer is to have the EDR imaged first if the event is disputed, rather than relying on any assumption about what a reset does or does not touch.

Who legally owns the data in my car's event data recorder? Under federal law the EDR data in a passenger vehicle belongs to the vehicle's owner or lessee, and retrieval by anyone else generally requires owner consent, a court order or other authorized legal process, an emergency medical need, or de-identified safety research. A majority of states layer their own EDR statutes on top of that, and they differ meaningfully.

Will you reset a module from a car that is in an insurance claim? No. Auto Module Lab does not service airbag or SRS modules from vehicles involved in an active insurance claim, active litigation, or an open investigation, and we require proof of ownership on every restraint order. If that is your situation, have the EDR imaged by a qualified crash-data analyst before any repair work begins.

How much data does an EDR actually record? Roughly fifteen required data elements under 49 CFR Part 563, with pre-crash parameters captured over about five seconds before the event at half-second intervals plus the crash pulse itself. There is no video, no audio, no GPS trail, and no continuous driving history in a Part 563 event record.

Can you download my EDR for me since the module is already on your bench? No — that is a separate forensic discipline performed with a Bosch CDR-type system by a trained crash-data analyst, and it carries chain-of-custody expectations a repair shop should not be improvising around. We will tell you to have it done first, by someone qualified, whenever the event might be disputed.

My airbag light is on but I was never in a crash. Is this the same job? Usually not. A light with no deployment history is almost always an ordinary fault — a clockspring, a connector, a seat sensor, or a low-voltage event — and those clear normally with a scan tool once the underlying fault is fixed. A crash-data clear only applies when hard deployment codes have latched the module.

What if the module turns out to be damaged rather than just locked? Then it is a hardware problem and code clearing will not help, which is what the $150 bench evaluation exists to determine before you spend money on the wrong service. Cracked boards, blown driver stages, corrosion and water intrusion all present as a module that will not reset, and each needs a different answer.

The bottom line

The airbag control module holds two different things and they are not the same thing. One is a lock-out — hard crash codes and a deployment record whose entire purpose is to stop a car from going back on the road with a used restraint system. Clearing that is ordinary repair work, and it is a $75 bench job here once the fired pyrotechnics are replaced and the wiring is sound.

The other is the Event Data Recorder, a federally defined five-second slice of vehicle data governed by 49 CFR Part 563 and overseen by NHTSA, which belongs to the vehicle's owner and is retrieved by a trained analyst with a Bosch CDR-type tool — never by a repair reset, and never as a side effect of one.

If those two things are ever likely to be confused in your situation, the order of operations settles it: image first, repair second. And if the vehicle is in an active claim, lawsuit, or investigation, we are not the right shop for it and we will tell you so. For everything else — a properly repaired vehicle, a verified owner, and a module that just needs its lock-out cleared — start at the airbag / SRS module crash data clear service page, or order a bench evaluation if you need to find out what you are actually dealing with first. Message us with your VIN and the module part number and we will tell you honestly which one you need.