The black box in your car: what it records about you at the moment of a crash

Everybody knows about the black box in an aircraft. Far fewer know that an equivalent device has been riding around in millions of ordinary cars for years.

It is not a separate box or optional equipment. The function is built into the restraints control module — the same one that fires the airbags.

What gets recorded

The parameter set is defined by standard and varies in detail between cars, but the core is consistent. When the module registers an event, it writes a snapshot of the few seconds before impact:

• Vehicle speed.
• Accelerator pedal position.
• Whether and how hard the brake was applied.
• Engine RPM.
• Steering angle.
• Whether the seatbelts were fastened — separately for driver and front passenger.
• Airbag deployment and the delay from the moment of impact.
• The number of previous system activations.
• The change in velocity during the impact itself.

Recording duration is typically about five seconds before the event, sampled several times per second.

What is not in there

An important fear to dispel. An event data recorder is not a surveillance system:

• It does not record continuously — only on activation, and it overwrites old data.
• It does not record audio or video.
• It does not store routes or coordinates — that is telematics, a separate system.
• It does not transmit anything anywhere by itself. The data sits in the module until somebody physically reads it.

So it is not “the car is watching you” but “the car remembered the last five seconds when something happened”.

What counts as an event

Not every hard stop is recorded. The threshold is tied to the change in velocity during an impact, and there are two event types.

A deployment event — the airbags fired. The record is locked permanently and not overwritten.

A non-deployment event — there was an impact but below the deployment threshold. That record is stored but can be overwritten by a later event.

Which is why data from a minor collision may survive, or may be gone if the car was subsequently involved in another.

Who has access

A question with no single answer across countries.

Technically, reading requires specialist equipment connected to the diagnostic port or directly to the module. A consumer adapter cannot read this data — standard OBD-II does not describe it. Why the standard does not cover everything is in the supported PIDs guide.

Legally, access depends on the jurisdiction: in some, the data is treated as the owner’s property and requires consent or a court order; in others it is available on request from law enforcement.

The practical conclusion for a driver is singular: this data exists and it is objective. It can equally confirm your account of events or contradict it.

What an owner can do

You cannot read the record itself with a consumer adapter. But adjacent information is available and useful:

1. The state of the restraints module. Whether it answers at all. A module missing from the roll call is an alarming sign. The related code is U0151.

2. B-series codes — airbag and pretensioner circuits, for example B0001.

3. The SRS lamp at key-on. A healthy module illuminates it for 3–5 seconds. If it never lights, either the bulb was removed or the module is silent.

4. The count of previous activations. On some cars this counter is available through manufacturer requests — and it answers “have the airbags fired”.

Vehicle inspection after a crash is built on exactly this; the full procedure is in the rebuilt salvage guide.

Why this matters when buying

The event data recorder is one more reason not to trust a clean dashboard.

A module holding a deployment record cannot be “fixed” by clearing codes. So the most common way to hide a crash is replacing the module with a donor or disabling it.

Both are visible through diagnostics: in the first case the module’s VIN does not match the body (see the Mode 09 guide), in the second the module simply does not answer.

In short

• The recorder is built into the airbag module and captures about five seconds before impact.
• It does not record continuously, does not capture audio, and does not transmit by itself.
• Consumer OBD adapters cannot read this data — specialist equipment is required.
• The data is objective and cuts both ways: it can confirm your account too.
• The record survives code clearing, so crashes get hidden by swapping modules — and that shows.

Download the app — B-series codes, the module roll call, and Mode 09 are read with an ELM327 adapter over Bluetooth SPP on Android.