Magellan
How to organize a carrier crash file from first call to closure
Organize crash evidence, accident-register records, testing decisions, claims and follow-up so the next coordinator can see what is complete and what remains open.
A first call rarely contains a complete account of a crash. The location may be uncertain, the police report unavailable and the vehicle's condition still being assessed. Open a controlled event file with the information actually known, label unknowns and identify who is coordinating the response. Do not wait for a polished narrative before preserving the basic chronology.
Immediate safety, emergency-response instructions and the applicable insurer or legal notifications take priority over administrative completeness. The record should support those actions, rather than delay them. Record the actual caller, call time, available identifiers and the source of each initial statement. Keep a later correction alongside the original note instead of silently rewriting what was first reported.
Use a case identifier connecting the driver, tractor, trailer and relevant movement. Assign a backup coordinator so the file does not depend on one person's inbox. Limit access to people with a legitimate role. An event record can be useful before the company knows whether the event meets a particular reporting definition; do not resolve that legal question by prematurely naming every incident a reportable accident.
Use the first-hour crash response guide (https://magellan.international/blog/crash-evidence-first-hour) for records that may be lost early.
An insurer's claim, a required accident register, a testing determination, a customer update, an equipment restriction and a possible data-review request answer different questions. For each part of the response, use the case index to show who is responsible, where its evidence is held, its status and the next action.
For accidents within the applicable federal definition, 49 CFR 390.15 requires an accident register kept for three years after each accident. Enter the required event details in the register and retain copies of accident reports required by state or other governmental entities or insurers. Keep any broader internal incident log clearly identified. Additional preservation duties or instructions may require longer retention of particular evidence. 49 CFR 390.15: accident records (https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-390/subpart-B/section-390.15)
Assess any post-accident drug/alcohol testing obligation without delay under the criteria and time limits in 49 CFR 382.303 (https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-382/subpart-C/section-382.303). Have an authorized reviewer record when the assessment began, the facts considered, the decision and any required action. Keep sensitive testing evidence in its restricted record. The general index needs the responsible contact and current action, rather than private results. An insurer’s instruction does not settle the regulatory decision.
Whether a specific crash meets a reporting/testing trigger and any litigation hold requires the actual facts and qualified review.
Identify available photographs, video, electronic records, driver and witness information, police materials, towing and repair documents, and relevant correspondence. Record what exists, who holds it and whether an overwrite or retention issue requires prompt action. Follow any preservation instruction from qualified counsel. Do not alter or selectively crop away context in an original evidence file.
Keep a source log containing filename, origin, acquisition date and a short description of what the item may establish. Restrict sensitive personal information and avoid distributing raw footage or medical details through a general team channel. A management summary should link to the controlled evidence, not become another uncontrolled copy of everything collected.
The first driver account may use local time while an electronic record uses UTC. Identify the time basis before treating that as a contradiction. Preserve uncertainty where it remains. A reconstructed chronology can help organize the file, but label it as a later reconstruction and cite its inputs. Keep it separate from the original records used to build it.
Once the underlying event is understood, assess whether there is a supported data issue or an eligible preventability request. The company's internal conclusion, an insurer's position and an FMCSA determination are distinct. Do not present one as proof of the others or promise that a favorable outcome resolves civil liability.
FMCSA’s Crash Preventability Determination Program (https://www.fmcsa.dot.gov/crash-preventability-determination-program) describes eligibility and submission evidence. Check the criteria applicable to the crash date. The program can change how a qualifying Not Preventable crash is treated in the Crash Indicator calculation; it is not a promise to delete the event from every record. Use the required evidence and record the actual determination.
For a separate identity, duplication or accuracy issue, consult DataQs Help Center: current request and review guidance (https://dataqs.fmcsa.dot.gov/HelpCenter/Faqs?topic_id=2). State precisely what is in dispute. Keep each request identifier, submitted packet and response with the case. A decision not to file should also be documented where the issue was considered; not every crash creates a valid correction or preventability request.
The CPDP eligibility and outcome guide (https://magellan.international/blog/crash-preventability-record) explains the separate FMCSA preventability decision.
An internal review should identify the evidence considered, the conclusion reached and any specific action justified by the facts. Avoid treating every crash as proof of driver fault, or treating a company belief that the crash was unavoidable as a reason to skip operating review. A useful question is what the company can learn or control without overstating what the evidence proves.
An action may concern equipment inspection, a dispatch communication, route information, training or preservation procedures. Define its owner, expected evidence and a way to check whether the change was used. “Discussed at the meeting” is different from “implemented and verified.” If no further action is warranted, record the basis for that conclusion rather than inventing activity for the file.
Keep legal analysis and privileged communications in the appropriate restricted location and follow counsel's direction on their handling. A general safety action register should point to the responsible adviser. Match vendor completion evidence to the affected vehicle or process, with the technical decision made by the qualified person.
Topics
- Carrier Crash Files and Accident Registers