Which crashes belong in the federal accident register?

An insurance claim, a police response, and a federal accident-register entry can describe the same event without being the same record. A Federal Motor Carrier Safety Administration notice published September 9 seeks renewal of the information collection behind 49 CFR 390.15 and invites comments through November 9. It does not create a new accident definition, expand the required fields, or start a new routine submission to FMCSA. It is a current reason to test whether the carrier's existing register is using the right threshold and retaining the right reports. This resource is operational editorial analysis, not legal advice for a particular crash or carrier.

Classify the event before building the federal entry. The notice restates the definition in 49 CFR 390.5T: the occurrence must involve a commercial motor vehicle operating on a public road and result in a fatality; bodily injury to a person who immediately receives medical treatment away from the scene; or disabling damage that requires a motor vehicle to be transported from the scene by a tow truck or another motor vehicle. A company's incident, preventability, insurance, or customer-reporting categories may be broader. Editorial inference: keep those useful categories, but do not let their labels silently decide whether the event belongs in the section 390.15 register.

For each qualifying accident, the federal register must preserve a small, exact set of facts: the date; the city or town closest to the occurrence and the state; the driver's name; the number of injuries; the number of fatalities; and whether hazardous materials other than fuel spilled from the vehicles' fuel tanks were released. Section 390.15 requires the carrier to retain the register for three years after the accident. Editorial inference: use controlled fields for those facts rather than relying on a narrative claim note that may omit a location, mix injury counts, or change when a file is summarized.

The supporting-report duty has its own boundary. Section 390.15 requires copies of accident reports that a state or other governmental entity or an insurer requires the motor carrier to complete. FMCSA guidance says that does not require the carrier to seek out and retain reports prepared by state investigators or by insurers themselves; it concerns information the carrier or driver generates to fulfill those reporting obligations. Editorial inference: identify each document by who required it, who created it, and when it was submitted, then preserve the completed version with the register entry without presenting a third party's later report as a carrier-created filing.

A practical intake can keep the lanes separate. Editorial inference: assign one record owner to capture the event, test the public-road and outcome thresholds, create the register entry when required, link the carrier-generated government and insurer reports, and record who reviewed the classification. Maintain the broader safety, claims, employment, litigation-hold, customer, and equipment files under their own rules. A retained note explaining why a borderline event was or was not placed on the federal register can help a later reviewer reconstruct the decision, but that note is an internal control rather than a field required by section 390.15.

Production on inquiry is different from routine reporting. The September notice says section 390.15 does not require carriers to submit the register or records to FMCSA or another party as a standing filing, but the material must be available when an authorized Federal, state, or local official requests it. Other obligations can still run on separate clocks. FMCSA's Safety Planner points carriers to the hazardous-material incident rules when a release is involved, and state, insurance, testing, or other requirements may call for their own action. Editorial inference: add those possible triggers to the intake checklist without treating the accident register as proof that every separate duty is complete.

Use the renewal's burden numbers carefully. FMCSA estimates 115,547 annual respondents, 172,203 reportable accidents, and 18 minutes per response for the information-collection calculation, up from the currently approved estimates. Those are program-wide burden assumptions, not a new deadline, a recommended investigation time, or a benchmark for an individual carrier's crash rate. A useful three-year review instead compares the register with the carrier's incident and claim indexes, checks every required field and linked report, tests retrieval, and applies a defensible retention date. The finish line is a complete federal register that can be produced without confusing it with every other crash-related file.