Locomotive event recorders can document speed, braking and control inputs; they usually do not explain everything a person saw or why a component failed. Cameras add visual context but may not exist, cover the relevant angle or share the recorder's clock. A reliable investigation identifies each source, preserves its native format and aligns the clocks using common events.
“Black box” can mean several different sources
| Source | May help establish | Important limitation |
|---|---|---|
| Locomotive event recorder | Time, speed, distance, throttle, brake applications, horn or other specified channels depending on equipment | Does not necessarily show the scene or prove why an input occurred |
| Forward-facing image recorder | Track view, crossing occupancy, signals, visibility and sequence | Lens, frame rate, audio, glare and field of view can limit interpretation |
| Inward-facing image recorder | Crew activity and cab conditions | Availability and access are governed by equipment, date and law; privacy restrictions matter |
| Passenger-car or door diagnostics | Door commands, faults, bypass status or vehicle events | System capability differs by fleet and may require vendor software |
| Station, crossing or business CCTV | Passenger movement, warnings, platform or road sequence | Retention is owner-specific; displayed clock may be wrong |
| Dispatch, radio and signal logs | Authorities, communications, train detection and response | Technical codes need qualified interpretation |
Current federal rules: two provisions, two timelines
Under 49 CFR §229.135, a train operated faster than 30 mph generally must have an in-service event recorder in the lead locomotive, subject to listed exceptions. The rule specifies data elements for covered recorders and generally requires retention of the most recent 48 hours of operation. Older equipment and other rail modes can differ, so the actual locomotive and regulatory coverage must be identified.
When an accident or incident is required to be reported to FRA under 49 CFR Part 225, §229.135(e) directs the railroad to preserve the original recorder data or an exact copy for one year, unless FRA or the National Transportation Safety Board notifies it to preserve longer. This is an important protection, but it does not mean every station fall or alleged injury triggers federal one-year preservation. Other data streams can follow shorter operational schedules.
Passenger-train image rules are different. Section 229.136 establishes inward- and outward-facing image-recording requirements for covered intercity and commuter passenger lead locomotives beginning October 12, 2027. As of this page's July 2026 update, that mandate is not yet generally effective. Some railroads already use voluntary or separately required systems. Never state that every passenger train had federally mandated cameras “since 2018”; confirm operator, equipment and service date.
For covered systems once the rule applies, the regulation addresses a minimum recording duration and one-year preservation after reportable events. Access, use and privacy restrictions are also part of the rule. This page does not suggest that a passenger can directly obtain every recording on demand.
Make the preservation request identifiable
“Save all black-box and camera evidence” can be too vague to locate the event. A targeted request identifies the accident date and time zone, train symbol or number, locomotive and car numbers, direction, milepost or station, crossing DOT number if applicable, and a time window before and after the event. It can list native data, audit logs, exports, player software, manuals, calibration, time synchronization and chain-of-custody records.
Potential recipients include the operating railroad, track owner, station authority, signal contractor, road authority, police agency, nearby businesses and vehicle owner. A government public-record request is not always the same as a litigation-preservation notice, and an accident report does not automatically preserve every file. A lawyer can select the proper vehicle without creating access or spoliation problems.
Do not alter a downloaded file, rely only on a screen recording or upload the sole copy to social media. Keep the original and record who obtained it. If a vehicle, phone or dashcam contains data, avoid repair, factory reset or automatic overwrite until preservation options are discussed. No one should enter railroad property or interfere with official equipment.
Synchronize before drawing conclusions
Two devices labeled 2:14:05 p.m. may not have recorded the same instant. Analysts can anchor sources to a shared event: first crossing-light flash, brake application, horn onset, impact, door command, radio transmission or 911 connection. They then document the offset rather than silently changing timestamps.
Raw data should be interpreted by someone familiar with the recorder and train. Speed sampling, wheel slip, consist length, brake propagation and signal-system logic can matter. A plotted graph is a useful aid, but the download, channel definitions and assumptions must remain available for review.
On PTC-equipped territory, the reconstruction may also require onboard, wayside and back-office message records. The Positive Train Control accident evidence guide explains PTC's four core functions, system layers and why the absence of an enforcement does not by itself prove a malfunction.
Worked data example
Hypothetical: after a grade-crossing collision, a phone video appears to show that the train horn began two seconds before impact. Its file metadata reveals that the clip was transcoded by a messaging app. The original witness phone supplies a longer file. The locomotive recorder logs horn activation nine seconds before impact, while the forward camera's clock runs seven seconds slow. A crossing-light event visible in both videos allows the sources to be aligned.
After synchronization, the horn channel and images are consistent. The remaining disputes concern sight distance, crossing-warning timing and whether either operator could avoid impact—not an apparent clock contradiction. Preserving the original file changed the analysis.
Source-by-source checklist
- Identify every locomotive, car, station, crossing and vehicle by number where possible.
- Ask whether the event was FRA-reportable rather than assuming one-year preservation applies.
- Request native data, metadata and required software—not only PDFs or narrated clips.
- Preserve station and third-party video promptly because retention is system-specific.
- Keep a chain-of-custody log and calculate deadline issues separately.
- Use the larger train evidence checklist for physical, medical and witness proof.
Frequently asked questions
How much history does a locomotive event recorder retain?
For covered lead locomotives, current rules generally require specified data for the most recent 48 hours of operation. The actual device and download may differ, and not every rail vehicle is governed by the same provision.
Must recorder data be preserved after every passenger injury?
No. Federal one-year preservation applies after an accident or incident required to be reported to FRA under Part 225. Not every alleged injury necessarily meets that trigger, so prompt private preservation still matters.
Are inward- and outward-facing cameras already mandatory on every passenger train?
No. Some operators use them voluntarily, but the federal mandate in 49 CFR 229.136 for covered passenger lead locomotives begins October 12, 2027. Confirm the equipment, coverage and date.