After a collision, an airbag may have deployed, may not have deployed, or may have deployed in one seating position but not another. A dashboard warning lamp, event-data report, diagnostic scan, damaged module, deployed fabric, repair invoice, recall result, or occupant statement can answer a different part of the inquiry. None should be treated as the entire airbag-system record.

An airbag-system evidence record should connect the exact vehicle and seating position to photographs, warning-lamp information, deployment status, event-data fields when present, diagnostic scans, component identifiers, prior work, recalls, post-crash repair, and chain of custody without treating nondeployment as proof of a defect.

Identify the vehicle and every relevant seating position

  • Vehicle identification number, year, make, model, trim, build date, plate, owner, mileage, title status, and source for each field
  • Driver, right-front passenger, rear seating position, child-restraint location, occupancy as reported, seat position, and restraint use kept separate
  • Frontal, side torso, curtain, knee, seat-mounted, center, or other airbag identified from the vehicle documentation rather than assumed from appearance
  • Steering wheel, dashboard, seat, pillar, headliner, door, buckle, pretensioner, and warning displays photographed in context before alteration

Preserve the vehicle before repair, salvage, or disposal

  • Current custodian, storage facility, tow date, release authorization, insurer inspection, repair estimate, total-loss decision, auction, salvage, and disposal deadline
  • Written preservation notice identifies the vehicle, airbag and restraint components, electronic modules, keys, battery condition, photographs, diagnostic information, and requested inspection
  • No powering, clearing codes, replacing modules, cutting fabric, removing seats, reconnecting a battery, repairing, selling, or destroying solely for evidence collection without appropriate authorization and safety planning
  • Every transfer records date, time, releasing and receiving persons, location, condition, seal or key status, and work permitted

The National Highway Traffic Safety Administration’s airbag information explains that airbags are supplemental protection designed to work with seat belts, and that deployment generally involves a signal from the electronic control unit to an inflator. NHTSA also notes that deployed airbags can be used only once. Those general descriptions do not determine how a particular system should have responded in a particular collision.

Photograph deployment and nondeployment without interpretation

  • Wide vehicle view, seating position, airbag cover or seam, deployed material, tear pattern, residue, steering wheel, dashboard, pillar, headliner, seat, door, and surrounding collision damage
  • Front and rear of components when lawfully removed, label, barcode, serial or part number, manufacturer mark, date code, connector, wiring, mounting point, and visible alteration
  • Instrument-panel image at first safe opportunity, warning lamps, ignition state, odometer, message center, and photographer’s position and time
  • What was not visible or could not be safely accessed recorded instead of reconstructed later

Keep event-data fields within their regulatory scope

49 C.F.R. Part 563 applies to specified vehicles equipped with an event data recorder and sets requirements concerning recorded crash-event data. Its required data table includes, among other fields, driver frontal-airbag warning-lamp status, frontal-airbag deployment timing for the driver and right-front passenger, safety-belt status, and whether a complete file was recorded. Applicability, available fields, recording interval, download method, and limitations depend on the vehicle and event.

  • Vehicle and module supported by the retrieval tool, software and hardware version, adapter, power method, operator, date, time, location, and retrieval protocol
  • Original report and native data retained; printed or converted copies labeled; file hash and export details recorded when available
  • Warning-lamp status, deployment command or time, event count, completion field, belt status, speed, braking, and other fields reported exactly with units and limitations
  • No inference that a blank, unavailable, unsupported, incomplete, overwritten, or nonrecorded field means the event did not occur

Preserve diagnostic scans before and after work

  • Pre-repair scan, post-repair scan, scan tool, software version, vehicle identification, mileage, date, ignition state, battery condition, and technician
  • Diagnostic trouble code, status, module, description supplied by the tool, freeze-frame or related data, clearing event, and rescan kept as separate entries
  • Airbag-control module, occupant-classification system, seat sensor, buckle, pretensioner, impact sensor, wiring, connector, and other component named only when the record supports it
  • Code or scan result not translated into a component failure, collision cause, injury cause, or repair requirement without vehicle-specific technical analysis

Collect prior and post-crash repair records by version

  • Estimate, work order, invoice, technician notes, scan, calibration, parts list, photographs, supplement, payment, warranty, and completion record
  • Original-equipment, recycled, salvaged, remanufactured, or other component description attributed to the invoice or part record
  • Prior collision, airbag deployment, warning-lamp complaint, diagnostic code, recall work, module programming, seat or interior repair, and inspection searched within an appropriate period
  • Removed component retained when lawful and feasible, or disposition, recipient, date, reason, and photograph documented

Check recalls without treating the search as a complete history

NHTSA’s recall search can report specified unrepaired recalls associated with a vehicle identification number and provides broader searches for vehicles, tires, and equipment. NHTSA explains that the VIN result may omit completed repairs, some recently announced recalls, older recalls, certain manufacturers, other campaigns, and international recalls. Preserve the query date, VIN, result, recall number, remedy status, manufacturer communication, and repair documentation.

Separate the preserved facts from technical conclusions

North Carolina Rule of Evidence 702 addresses qualified expert testimony, sufficient facts or data, reliable principles and methods, and their application to the facts. Whether a system functioned as designed, whether a deployment threshold was met, whether a component or repair was defective, and whether an event caused an injury are different questions requiring an appropriate foundation.

  • Deployment or nondeployment recorded as an observation or data field, not an automatic conclusion about defect
  • Warning-lamp state kept distinct from the reason a lamp illuminated or whether a condition existed at another time
  • Recall applicability kept distinct from proof that the recalled condition occurred in this collision
  • Medical causation kept distinct from vehicle-system analysis and directed to appropriately qualified professionals

The related vehicle-preservation guide after a North Carolina crash explains the broader custody, inspection, repair, event-data, and disposal record. This page owns the narrower airbag deployment, warning-lamp, diagnostic, component, and recall file.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about Charlotte car accident claims involving disputed airbag-system evidence. Safety decisions belong with qualified vehicle and medical professionals, and legal conclusions depend on the complete evidence and circumstances.

Sources