---
title: "Event Data Recorder: What Your Car Actually Records About a Crash"
description: "Not a black box. A few seconds of vehicle data inside the airbag module, written only on a crash, owned by you under federal law, and readable only with a specialist tool."
url: "https://baronauto1.com/guides/event-data-recorder/"
type: "article"
published: "2026-08-31"
modified: "2026-08-31"
site: "Baron Auto"
disclaimer: "This site is under new ownership and is not affiliated with Baron Auto Emporium dealership."
---

# Event Data Recorder: What Your Car Actually Records About a Crash

> Not a black box. A few seconds of vehicle data inside the airbag module, written only on a crash, owned by you under federal law, and readable only with a specialist tool.

*Guides · 14 min read · 3,115 words*

## The short version

- An event data recorder is not a flight recorder. It is a few seconds of vehicle data stored inside the airbag control module, captured only when a crash or near-crash triggers it.
- A federal rule fixes what it must capture and how long the window is. The list is short, technical and entirely about vehicle dynamics: speed, throttle, braking, belt status, deployment timing.
- It does not record where you drove, what was said in the cabin, or a history of your journeys. Data of that kind exists in modern cars, and it comes from somewhere else.
- The data belongs to the vehicle’s owner under federal law. Access by anyone else generally requires consent, a court order, or one of a small number of statutory exceptions.
- Reading it requires a specialist tool and a physical connection to the vehicle. A buyer cannot check it before a purchase in any practical sense, and no history report contains it.
- What a buyer can get is the record of what a crash led to — claims, title brands, repairs recorded by whoever did them. That is a different dataset and it is the one worth checking.

The phrase most people reach for is “black box”, and it does more harm than good. It suggests a device continuously logging your driving, retrievable by anyone curious enough, and settling arguments about what happened. None of that is right, and the distance between the popular image and the actual device is where every practical question on this subject lives.

What is actually installed is a function of the airbag control module: a small, fixed-format record of a few seconds of vehicle data, written only when something violent enough happens, and readable only with a tool most workshops do not own. It is genuinely useful in a crash investigation and almost entirely useless for the thing people most want it for, which is finding out what a used car has been through.

**Figure: What the module stores, and for how long**

A comparison grid of seven kinds of vehicle data, showing which are captured in an event data recorder’s crash record and which are retained during ordinary driving.

A federal rule fixes the fifteen data elements a recorder must capture and fixes the window at roughly five seconds. Everything in the amber rows is real data a modern car may generate, and none of it is generated by this module — which matters, because the module is the part with a legal retrieval procedure attached to it.

## Where it lives and what it is part of

There is usually no separate box. The recording function sits inside the airbag control module — the unit that decides, in milliseconds, whether to fire the restraints. That module already has to measure deceleration, read the belt switches and monitor the sensors, because it cannot make its decision otherwise. The recorder is the part that keeps a copy.

Physically the module is typically under the centre console or beneath a front seat, bolted to the structure so it experiences the vehicle’s motion rather than the trim’s. That location is why a serious crash sometimes destroys the record along with the car, and why a flooded vehicle can lose it entirely.

There is no separate device behind the trim panel marked AIRBAG, and nothing labelled “recorder” anywhere in the car. Being part of the airbag system explains the shape of everything else. The data window is short because the airbag decision is short. The elements are the ones the module was already measuring. And the trigger is a crash-severity event, because that is the only thing the module is designed to notice.

## What the federal rule fixes

A federal regulation governs recorders in light vehicles, and understanding what it does and does not do resolves most of the confusion.

It does not require a manufacturer to fit one. What it does is specify, for any vehicle that has one, a minimum list of data elements that must be captured, the sampling rates, the length of the recording window, the survivability the module must demonstrate, and the requirement that the data be retrievable using commercially available equipment.

That last requirement is the reason retrieval tools exist at all. Before it, formats were proprietary and access was effectively at the manufacturer’s discretion.

The mandated list runs to fifteen elements and is resolutely technical: vehicle speed, engine speed, throttle position, service brake application, whether the belts were buckled, the change in velocity through the impact, airbag deployment status and timing, and the number of ignition cycles at the time of the event. The window is short — on the order of five seconds before the trigger, with the impact itself sampled far more finely.

Manufacturers may record more than the minimum and several do. Steering input, stability-control intervention and seat position appear in some systems. The mandated fifteen are the floor, not the ceiling, and what a particular car holds depends on who built it.

## What causes it to write

The module is deciding continuously and storing almost nothing. Data is held briefly in a rolling buffer and overwritten; only a qualifying event causes it to be committed.

Two categories of event exist. A *deployment event* is one where the restraints fired, and it is written permanently — the module is generally locked afterwards and the record cannot be overwritten by subsequent driving. A *non-deployment event* is a lesser impact or hard braking that exceeded the recording threshold without triggering the airbags, and these are typically stored in a small number of slots that later events can overwrite.

The practical implication is a common misunderstanding. A minor collision from four years ago is very unlikely to still be in the module, because ordinary driving with a few hard stops will have cycled it out. What survives indefinitely is the serious crash — which is also the one that left evidence everywhere else.

## Who the data belongs to

Federal law is clear on this and it surprises people: the data belongs to the owner or lessee of the vehicle, not to the manufacturer and not to whoever holds the retrieval tool.

Access by anyone else requires the owner’s consent or a narrow statutory basis — a court order or authorised judicial process, a formal safety investigation, emergency response to determine the need for medical assistance, or research use where the data is stripped of anything identifying the vehicle or its owner.

Two consequences follow. An insurer cannot simply read the module because it is handling a claim; it needs the owner’s agreement, and the policy may make that agreement a condition of cover, which is a different mechanism from a right of access. And a workshop cannot pull the data and pass it to a third party on its own initiative.

State law adds a further layer in many places, some of it stricter than the federal floor. Where this matters to you in a concrete way — a dispute, a claim, a subpoena — it is a question for a lawyer in your state rather than for a reference page.

## Actually getting the data out

Retrieval is a specialist activity and the barrier is real.

The tool is a crash data retrieval system: a hardware interface and software that understands each manufacturer’s format. It connects either through the diagnostic port under the dashboard, if the vehicle can be powered up, or directly to the module itself, if the vehicle cannot. The second case — a module removed from a wrecked car and read on a bench — is common in serious collisions.

Coverage is not universal. The tool supports the makes and model years its vendor has reverse-engineered or licensed, and older or rarer vehicles are frequently unsupported. Nor is operating it trivial: the raw output is a technical report, and interpreting it correctly — recognising a mis-triggered record, understanding what the change-in-velocity figure does and does not mean — is the actual expertise.

Who has one: collision reconstruction specialists, some law enforcement units, insurance investigators, larger independent forensic firms, and a small number of well-equipped workshops. Not, ordinarily, a dealership service department or an independent garage.

![A digital instrument cluster behind a steering wheel showing zero speed, the letter P for park, a trip distance and a range figure](https://baronauto1.com/assets/photos/under-dash-connector-1280.webp)

*Speed, gear and distance are on the display in front of the driver. Several of the same channels are what the module stores for the seconds before an impact — the difference is that these are shown live and then forgotten.*

## What people think is in there and is not

Four things, and each of them is genuinely recorded somewhere in a modern car, which is why the confusion persists.

Location. The recorder holds no position data at all. Cars know where they are, and connected vehicles transmit it, but that is the telematics system rather than the airbag module.

Audio and video. Not captured. Cabin microphones exist for calls and voice control, and cameras exist for driver monitoring and parking, and none of them feed this module.

A driving history. There is no log of your trips, your habitual speeds, or where you have been. The buffer holds seconds and discards them continuously.

Phone use. Not recorded here. A phone paired to the infotainment leaves traces in the infotainment.

The distinction matters because these systems have different owners, different access rules and different retention. Somebody investigating a crash may well obtain location data — from a telematics provider, under a different legal process, on a different timescale. That it exists does not mean the recorder held it.

## The modern complication

Where this subject gets genuinely difficult is that the airbag module is now the smallest and best-regulated of several systems recording something.

A connected vehicle transmits data to the manufacturer continuously: location, speed, diagnostic status, sometimes driving behaviour. An infotainment unit retains paired devices, contacts, call logs and navigation destinations, often long after a car changes hands. An insurance telematics device or app records journeys deliberately and by agreement. Advanced driver assistance systems keep their own operational logs.

None of that is the event data recorder, and none of it is covered by the federal rule that governs the recorder. It is governed instead by the manufacturer’s privacy policy, the terms you accepted when the service was activated, and whatever state privacy law applies — a considerably less settled arrangement than the one covering the fifteen elements in the airbag module.

For a used-car buyer there is a concrete action in this: clear the infotainment before you hand a car over, and check what a car you have bought still remembers about its previous owner. That data is far more personal than anything in the crash record, and unlike the crash record it is trivially accessible to whoever is sitting in the driver’s seat.

## What this means if you are buying a used car

The honest answer is that the recorder is not available to you, and treating it as a check you might run will only waste your time.

Consider what would be required. You would need the seller’s consent, since the data is theirs. You would need a specialist with the right tool and coverage for that make and model year. You would need the vehicle in front of them. And you would need a crash to have been recorded in the first place, which for anything short of a serious impact is unlikely to still be there.

Against that, consider what you can get in a few minutes without the seller’s cooperation. A serious crash leaves a trail across systems that do keep records: an insurance claim, possibly a title brand, a police report, repair work invoiced by whoever performed it, and in many cases an entry in the pooled federal title data. Running the identification number through [a full vehicle history report](https://carcheckervin.com) surfaces that trail, and it answers the question you actually had — has this car been in a significant collision — without any of the four obstacles above.

The second check is physical. Deployed airbags have to be replaced, and the replacement leaves evidence: new trim panels against old, mismatched fasteners, a dashboard that does not sit quite right, and a warning lamp that behaves oddly at key-on. An inspection by somebody who knows what a repaired restraint system looks like is worth more than any amount of speculation about what a module might contain.

One thing the module does tell you cheaply: if the airbag warning lamp does not illuminate at all when the ignition is switched on, the bulb or the circuit has been disabled. That is a deliberate act and it is nearly always hiding a fault.

## Crashes, claims and litigation

Where the data does get used, this is where.

In a serious collision with a dispute about what happened, the recorder can settle questions that witnesses cannot: what the speed was, whether the brakes were applied and when, whether the belts were buckled. Reconstruction specialists treat it as one input among several — scene evidence, vehicle damage, physics — rather than as a verdict, because a record can be triggered wrongly or damaged, and the change-in-velocity figure is routinely misread as impact speed.

Access typically comes through consent or a court order. In practice, in a contested claim, it is often the insurer or an attorney who arranges retrieval and the vehicle owner who authorises it.

Timing matters more than people expect. Wrecked vehicles are sold, dismantled and crushed on commercial timescales, and the module goes with them. Where the data is likely to matter, securing the vehicle or the module early is the step that preserves the option.

## If somebody hands you a retrieval report

It happens after a serious crash, usually through an insurer or an attorney, and the document is not written for a general reader. Four things are worth knowing before you form a view of it.

The change-in-velocity figure is not impact speed. It is how much the vehicle’s velocity altered during the impact, which depends on what was hit and how the structure absorbed the energy. A car striking a parked vehicle and a car striking a bridge abutment at the same road speed produce very different figures, and reading one as the other is the most common error made with these reports.

The pre-crash data is coarse. Speed, throttle and brake status are typically sampled once or twice a second across the window, so the record shows a trend rather than a continuous trace. Fine questions about the last half-second frequently cannot be answered from it.

Timing is relative to the trigger, not to the clock. Everything is expressed as an offset from the moment the module decided an event was occurring, so a report cannot tell you what time of day anything happened. That comes from elsewhere.

And a record can be wrong. Modules mis-trigger, sensors fail, and a heavily damaged unit can produce partial or corrupted output. A competent reconstruction treats the retrieval as one line of evidence to be reconciled with the scene, the damage and the physics — not as the answer that overrides them.

If the dispute is about whether a vehicle had been crashed before this one, the retrieval will not help at all: the module carries no history of earlier repairs. That question is answered from the claims and title record, and [a report covering prior damage and title brands](https://carcheckervin.com) is the ordinary way to establish it.

## Can it be erased?

Not by any normal means, and the answers people hope for do not exist.

A deployment record is generally locked and the module is treated as a replacement item after the airbags fire — which means a repaired vehicle usually has a new module with no history, not an erased one. Non-deployment records overwrite themselves in the ordinary course of driving, which is a design property rather than a feature you can invoke.

Disconnecting the battery does not clear it. Nor does clearing diagnostic trouble codes with a scan tool; that touches a different memory area entirely. Deliberately destroying or replacing a module to defeat an investigation is a different matter altogether and is treated accordingly.

If you are selling a car and concerned about what it holds, the recorder is the wrong thing to worry about. It holds seconds of vehicle dynamics from an event you would remember. The infotainment holds your address book, your home address and every destination you have navigated to, and it is the system that actually needs attention before the keys change hands.

## Common questions

### Does every car have an event data recorder?

No federal rule requires one to be fitted, but the great majority of modern light vehicles have the function because it is built into the airbag module. Coverage among older vehicles is patchier, and whether a particular car has one is a question about that model rather than about the law.

### Can I read my own car’s data?

Legally yes — it is your data. Practically you would need a crash data retrieval tool that supports your make and model year, or you would need to pay somebody who has one. Ordinary scan tools and phone-based diagnostic dongles cannot do it.

### Can an insurance company access it without telling me?

Not without a basis. Federal law requires the owner’s consent or a specific statutory exception such as a court order. Your policy may separately oblige you to cooperate with an investigation, which is a contractual matter rather than a right of access.

### Will a vehicle history report show what the recorder holds?

No. History reports are built from records that organisations file — titles, registrations, insurance claims, inspections, invoiced repairs. The module’s contents are not filed anywhere and reach nobody unless somebody physically retrieves them.

### How long does the data stay in the module?

A deployment record is typically permanent, and the module is usually replaced during repair rather than reused. Non-deployment records sit in a small number of slots and are overwritten by later events, so a minor incident from several years ago has very probably gone.

### Does it record my speed all the time?

No. Speed is held in a rolling buffer measured in seconds and continuously discarded. Only a qualifying event causes those seconds to be committed to memory, and nothing outside that window is retained.

### Is the recorder the same as the telematics system?

No, and conflating them is the source of most anxiety on this subject. The recorder is a crash-triggered store inside the airbag module, covered by a specific federal rule. Telematics is a connected service that transmits data continuously to the manufacturer under its own privacy terms.

### Should any of this change how I inspect a used car?

Only by removing one item from your list. The module is not checkable in a purchase context, so the effort belongs on the records a crash actually generates and on a physical inspection of the restraint system by somebody competent to judge it.

## Sources and further reading

- [NHTSA event data recorder research](https://www.nhtsa.gov/research-data/event-data-recorder)
- [Federal event data recorder rule](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-V/part-563)
- [NHTSA Office of Defects Investigation complaint database](https://www.nhtsa.gov/nhtsa-datasets-and-apis)
- [NMVTIS (US Department of Justice)](https://vehiclehistory.bja.ojp.gov/)
- [FTC used car buying guide](https://consumer.ftc.gov/articles/buying-used-car-dealer)

Recall, complaint and safety-rating figures on this page were retrieved from the federal databases above on August 19, 2026. Federal data changes — re-check any VIN before you rely on it.

---

*This site is under new ownership and is not affiliated with Baron Auto Emporium dealership.*

Canonical source: https://baronauto1.com/guides/event-data-recorder/