Work crash and near miss investigation: a step by step employer guide
What to do after a work crash or near miss, from the scene to lasting fixes
Safety Behind the Wheel Foundationdrivewithcare.org
Last reviewed:
For employers and fleets14 min read
Picture a technician backing a service van out of a tight driveway when a mailbox post goes down with a crunch. No one is hurt. What the company does next decides whether it learns something or just pays for a bumper.
Roadway crashes killed 1,146 U.S. workers on the job in 2024, according to the Bureau of Labor Statistics (BLS) [1]. The Network of Employers for Traffic Safety (NETS) estimates that crashes on and off the job cost U.S. employers $62 billion in 2023, in 2024 dollars. Property damage only crashes made up $7 billion of that [2].
The Occupational Safety and Health Administration (OSHA) advises reporting every crash to a supervisor quickly and reviewing it for root causes [8]. This guide walks through that process the way an incident investigator would, with 4 tools you can use right away.
The first hour: what the driver does at the scene
People come first, then paperwork. Our roadside breakdown guide covers where to wait and when to stay in the vehicle.
The Federal Motor Carrier Safety Administration (FMCSA) requires employers of commercial driver’s license (CDL) holders to give drivers post accident instructions before they drive [4]. A card in every vehicle does the job for any fleet.
The company's response: the first 24 hours
Give drivers one 24/7 number that a person answers. The supervisor who takes the call then works through 4 questions in order:
- Is everyone safe and getting care?
- How does the driver get home? A shaken driver shouldn’t keep driving. No one drives a damaged vehicle.
- Who must be notified? Use the table below.
- What evidence could we lose today?
Comparison compiled by Safety Behind the Wheel Foundation
| Rule | Who it covers | What it requires |
|---|---|---|
| OSHA severe injury reporting (29 CFR 1904.39) | All employers | Report a work related death within 8 hours, and an in patient hospitalization, amputation or eye loss within 24 hours. Crashes on a public street or highway are exempt unless they happen in a construction work zone [3]. |
| OSHA injury and illness log (29 CFR Part 1904) | Many employers with more than 10 employees, outside exempt industries | Injuries in crashes while working or traveling for work are generally work related. They may need to be logged even when no call to OSHA is due [3]. |
| FMCSA accident register (49 CFR 390.15) | Motor carriers operating commercial motor vehicles (CMVs) | Record each crash that meets the federal definition: a death, an injury treated away from the scene, or a vehicle towed for disabling damage. Keep the register and related reports for 3 years [4]. |
| FMCSA post accident testing (49 CFR 382.303) | Employers of CDL drivers | Test after any fatal crash, and after an injury or tow away crash when the driver is cited. Alcohol tests stop at 8 hours and drug tests at 32 hours [4]. |
| Insurance policy and lease | Everyone | Report on the timeline your policy or lease requires. |
Testing never requires delaying needed medical care [4]. The 29 OSHA approved State Plans must be at least as effective as federal OSHA [3]. So check whether yours adds reporting rules.
For workers without a CDL, state law and your policy govern testing after a crash. OSHA allows testing to find a root cause if it covers everyone whose conduct could have contributed, but not testing used to punish injury reporting [9]. OSHA also notes that mandatory testing after an injury can discourage reports [6]. Have qualified HR and legal counsel review your testing, discipline and privacy policies.
Preserve the evidence before it disappears
Skid marks wash away, memories fade and cameras record over old footage. OSHA’s investigation guide makes securing and documenting the scene the first step [5].
- Video and telematics: Have your vendor lock dashcam clips and trip data right away. For CMVs, video showing how a crash unfolded can qualify it for FMCSA’s preventability review [10].
- Event data recorder (EDR): If the vehicle has one, it may hold speed, braking and seat belt data from a few seconds around the crash [11]. Reading it takes special tools and access to the vehicle [11]. A federal rule lengthens the window recorded before a crash to 20 seconds, phasing in for light vehicles built from September 2028 [11].
- Hold repairs: Don’t fix, sell or scrap the vehicle until it is inspected and its data saved. For a vehicle you don’t own, get consent and legal advice first.
- Records: Save dispatch messages, route plans, timecards and maintenance files. CMV hours of service records must be kept at least 6 months [4], but pull them now.
- Statements: Interview people separately and soon. Explain that the goal is learning facts, not assigning fault. OSHA advises both steps [5].
Take care of the driver
Support comes before the interview, no matter who caused the crash.
- Medical care: Encourage a medical check after any significant crash. Our guide to care after a crash explains what to watch for.
- Emotional support: The National Institute for Occupational Safety and Health (NIOSH) calls strong emotions after a traumatic event ordinary. It advises professional help if distress lasts several weeks or disrupts daily life [12]. It was written for emergency responders but fits drivers, too. Offer your employee assistance program (EAP) that day and again a week later.
- Time and contact: Give paid time off for the rest of the shift and for medical visits. Check in at 24 hours and 1 week. Ease back in with a ride along after a serious crash.
Preventable is a learning label, not a verdict
FMCSA’s safety rating rules call a crash preventable if a driver using normal judgment could have foreseen it and avoided it. The avoiding steps must have been within the driver’s control and unlikely to cause another crash [4].
That differs from legal fault. Picture a driver hit by a red light runner. Police may cite only the other driver. Yet a review might find that scanning before entering could have prevented the crash.
FMCSA’s Crash Preventability Determination Program reviews 21 types of CMV crashes. Those found not preventable are dropped from the Crash Indicator score in FMCSA’s Safety Measurement System. The findings carry no FMCSA penalties [10]. Through June 26, 2026, the program found 71,446 of 74,513 decided cases not preventable, about 96% (our calculation) [10]. Carriers pick which crashes to submit, so that share doesn’t describe all truck crashes.
Inside your company, keep the safety review separate from discipline. OSHA’s guide warns that fault focused investigations breed fear of retaliation and make people reluctant to take part [5]. A “just culture” approach responds to the behavior, not the outcome:
Comparison compiled by Safety Behind the Wheel Foundation
| What happened | Example | Response |
|---|---|---|
| Honest mistake | Misjudged a gap in heavy traffic | Console the driver, then fix conditions that made the mistake easy |
| At risk shortcut | Skipped the walk around before backing because routes run late | Coach the driver and remove the pressure that rewards the shortcut |
| Reckless choice | Drove after drinking, or raced another driver | Discipline under written policy, decided by HR rather than the investigator |
Near misses: lessons that cost nothing
A near miss is a close call that could have hurt someone or damaged something but didn’t. Examples include a hard stop to avoid a rear end crash, a coworker stepping behind a backing van or a moment of nodding off. OSHA urges employers to look into close calls, not just injuries [5].
OSHA recommends a reporting process with an anonymous option, quick responses and feedback on what was done [6]. In practice:
- Make it fast: a 60 second form by QR code, text or voicemail.
- Make it safe: honest near miss reports never lead to discipline. Put that in writing.
- Close the loop: thank the reporter within a day and share the fix. OSHA notes that workers may stop reporting when management seems unresponsive [13].
- Sort by risk: log minor reports for trends. Fully investigate any that could have killed or badly hurt someone.
Telematics alerts, such as hard braking, can also reveal unreported near misses. Our guide to telematics for safety, not punishment shows how to use them for coaching.
How to investigate: from timeline to root cause
Match the effort to the potential severity, not the repair bill. OSHA recommends investigation teams of managers and employees working together [5], so include a respected peer driver.
Build the timeline
Start 72 hours before the event and end when the driver got home, noting sleep, shift start, dispatch calls, stops and the crash.
Sort the factors
Cross the phases of the crash with 4 groups of factors, so the review doesn’t stop at the driver.
Comparison compiled by Safety Behind the Wheel Foundation
| Factor | Before the crash | During the crash | After the crash |
|---|---|---|---|
| Driver | Sleep, training, experience, distraction, health | Speed, scanning, reaction | First aid, calling for help |
| Vehicle | Maintenance, recalls, mirrors, cameras, driver assistance features | Brakes, tires, air bags, crash protection | Fire, fuel leaks, data saved |
| Environment | Route, weather, light, road design, site layout | Road surface, guardrails, objects struck | Scene safety, emergency response time |
| Organization | Schedules, route planning, policies, supervision | Calls or dispatch messages while driving | Reporting, driver support, lessons shared |
Review fatigue and the schedule
NIOSH advises collecting sleep history, hours worked, time of day and hours of driving. It also urges training investigators to spot fatigue [14]. Ask about time pressure, too, and keep health answers confidential. Our guide to fatigue and scheduling at work has a full question set.
Check the vehicle
Pull maintenance and inspection records and any earlier defect reports. Look up open recalls by vehicle identification number (VIN) on the National Highway Traffic Safety Administration (NHTSA) recall site. Report suspected defects there [15]. Note which driver assistance features were on, whether they warned or braked, and whether sensors were recalibrated after past repairs.
Ask “why” until you reach the system
The immediate cause is what went wrong at the moment of the crash. The root cause is the underlying reason, usually in planning, management or design [5]. OSHA warns that fixing only the immediate cause treats a symptom, not the problem [5]. Asking “why” over and over, often called the 5 Whys, helps you dig down [5].
Comparison compiled by Safety Behind the Wheel Foundation
Investigation worksheet outline
| Section | What to record |
|---|---|
| Basics | Date, time, place, driver, vehicle, trip purpose, actual and potential severity |
| Response | Care given, notifications, tests, data holds |
| Evidence | Photos, video, telematics, EDR, police report, statements, records |
| Timeline | 72 hours before through the driver’s return home |
| Factors | Driver, vehicle, environment and organization grid |
| Fatigue and schedule | Sleep, hours, time of day, time pressure |
| Vehicle | Maintenance, recalls, driver assistance features, fit for the task |
| Causes | Immediate causes, root causes and the written “why” chain |
| Preventability | Finding and reasoning, for learning only |
| Actions and lessons | Items moved to the corrective action log; a de identified lesson to share |
| Sign off | Reviewers, plus a date to check results |
Corrective actions: fix the system first
Choose fixes with the NIOSH hierarchy of controls. It ranks elimination first, then substitution, engineering controls, administrative controls and personal protective equipment. NIOSH says the top 3 work better because they don’t depend heavily on people. The bottom 2 need constant effort from workers and supervisors [7].
Comparison compiled by Safety Behind the Wheel Foundation
| Control level | Driving examples |
|---|---|
| Eliminate | Hold a video meeting instead of a site visit; deliver to a dock that needs no backing |
| Substitute | Fly or take the train on long trips; use a smaller vehicle on tight city routes |
| Engineering | Backup cameras, automatic braking, pull through parking, better yard lighting |
| Administrative | Realistic route times, fatigue limits, a walk around rule before backing, coaching |
| Personal protection | Seat belts on every trip; high visibility vests at the roadside |
Training is an administrative control, so pair it with stronger fixes. If your “why” chain ends at the schedule, a refresher course won’t fix it.
OSHA advises giving each fix an owner and a due date, using stopgap controls until long term fixes arrive and checking with workers that they work [6]. Log every item, and close it only once it’s proven.
Comparison compiled by Safety Behind the Wheel Foundation
| # | Root cause | Action | Level | Owner | Due | Status | How we’ll know it worked |
|---|---|---|---|---|---|---|---|
| 1 | Stop times too short | Add 10 minutes per dock stop in routing software | Administrative | Dispatch manager | Nov. 15 | Open | On time rate holds, and no backing near misses for 90 days |
| 2 | Blind backing at Dock B | Paint a pull through lane | Eliminate | Facilities lead | Dec. 1 | In progress | No backing events at Dock B for 6 months |
| 3 | Vans lack cameras | Add backup cameras | Engineering | Fleet manager | Jan. 31 | Ordered | Backing crash rate falls over 12 months |
| 4 | Interim fix until item 2 is done | Spotter at Dock B | Administrative | Site supervisor | Now | Done | Weekly spot checks |
Trend analysis: find patterns before they become crashes
One crash tells a story, but a crash rate shows patterns across periods and teams, even as miles change:
Crash rate per million miles = crashes ÷ miles driven × 1,000,000
For example, 9 crashes over 2.4 million miles is a rate of 3.75 (our calculation). Small fleets should use a rolling 12 months.
Sort crashes and near misses by type, such as backing, rear end and intersection crashes, and by time of day, route, vehicle and driver experience. A cluster, like backing crashes at one site, points to a fix.
Crash counts look backward, so OSHA’s leading indicators guide suggests measures that show whether prevention is working [13]. Fleet versions include:
- Time from a hazard report to a management response
- Share of reported hazards acted on within 48 hours
- Hours from a crash to the start of the investigation
- Share of investigations that include a root cause analysis
- Corrective actions closed on time
A rise in near miss reports after you launch a program usually means trust is growing, not that driving got worse.
Share lessons without scaring people into silence
How you share lessons decides whether people report the next event.
- Send de identified safety alerts within 2 weeks. Cover what happened, why, what changed and what drivers can do, with no names.
- Hold 10 minute toolbox talks that ask drivers how they’d prevent the event.
- Post “you reported, we fixed” updates to prove that reporting leads to action.
- Don’t reward silence. OSHA says incentive programs shouldn’t discourage reporting [6]. Its rules also bar retaliation for reporting injuries [3].
Any answer that worries you becomes your next corrective action.
Frequently asked questions
Do I have to report a company vehicle crash to OSHA?
Sometimes. Employers must report a work related death within 8 hours and an in patient hospitalization, amputation or eye loss within 24 hours. Crashes on public roads are excluded unless they occur in a construction work zone [3]. The injury may still belong on your OSHA log.
What’s the difference between a preventable crash and an at fault crash?
Fault is a legal finding made by police, insurers or courts. Preventability asks whether the driver could reasonably have foreseen and avoided the crash [4]. A crash can be preventable even when the driver wasn’t at fault.
Should drivers be disciplined for preventable crashes?
Not automatically. Keep the safety review separate from HR. Respond to the behavior rather than the outcome. Save discipline for reckless choices under a written policy.
How soon should a crash investigation start?
Place evidence holds the same day. Start the investigation within 24 hours if you can. OSHA counts the delay before an investigation starts as a leading indicator [13].
The bottom line
Recommendation from Safety Behind the Wheel Foundation
Make the first hour about people, the first day about reporting and evidence, and the investigation about the system rather than the person. Then close every corrective action and share lessons without names. If drivers keep reporting near misses, your process is working.
Related articles
- Workplace motor vehicle safety program: a step by step employer guide
- Work driving fatigue: safer shifts, schedules and trip rules for employers
- Fleet telematics and driver cameras: how to coach drivers, not punish them
- Post crash care: what to do in the first minutes after a crash
- Workplace driving impairment: alcohol, drug and medication policies
Sources and further reading
- 1U.S. Bureau of Labor Statistics (BLS). National Census of Fatal Occupational Injuries in 2024 (news release). USDL-26-0230. February 19, 2026. bls.gov/news.release/cfoi.nr0.htm
- 2Network of Employers for Traffic Safety (NETS); Miller TR, McKnight AS (Pacific Institute for Research and Evaluation). Costs of Motor Vehicle Crashes to Employers: Latest Available Estimates and Key Findings. July 2026. trafficsafety.org (PDF)
- 3Occupational Safety and Health Administration (OSHA). Injury reporting and recordkeeping rules: 29 CFR 1904.5 (work-relatedness), 1904.35 (employee reporting and anti-retaliation) and 1904.39 (fatality and severe-injury reports), eCFR, up to date as of October 1, 2026; with OSHA’s Report a Fatality or Severe Injury, Injury and Illness Recordkeeping and Reporting Requirements and State Plans pages, accessed October 2026. ecfr.gov … 1904.39; ecfr.gov … 1904.5; ecfr.gov … 1904.35; osha.gov/report; osha.gov/recordkeeping; osha.gov/stateplans
- 4Electronic Code of Federal Regulations (eCFR). Federal Motor Carrier Safety Regulations: 49 CFR 382.209 and 382.303 (post-accident alcohol use and testing), Part 385 Appendix B (preventable accident standard), 390.5 (definition of accident), 390.15 (accident register) and 395.8(k) (record retention). Up to date as of October 1, 2026. 382.303; 382.209; Part 385 App. B; 390.5; 390.15; 395.8
- 5OSHA. Incident [Accident] Investigations: A Guide for Employers (December 2015) and The Importance of Root Cause Analysis During Incident Investigation (fact sheet OSHA 3895, October 2016), via OSHA’s Incident Investigation topic page, accessed October 2026. osha.gov/incident-investigation; Guide (PDF); Fact sheet (PDF)
- 6OSHA. Recommended Practices for Safety and Health Programs: Worker Participation; Hazard Prevention and Control. Accessed October 2026. osha.gov/safety-management/worker-participation; osha.gov/safety-management/hazard-prevention
- 7National Institute for Occupational Safety and Health (NIOSH). Hierarchy of Controls. Last reviewed April 10, 2024. cdc.gov/niosh/hierarchy-of-controls
- 8OSHA. Motor Vehicle Safety: Employers. Accessed October 2026. osha.gov/motor-vehicle-safety/employers
- 9OSHA. Clarification of OSHA’s Position on Workplace Safety Incentive Programs and Post-Incident Drug Testing Under 29 C.F.R. § 1904.35(b)(1)(iv) (standard interpretation memo). October 11, 2018. osha.gov/laws-regs/standardinterpretations/2018-10-11
- 10Federal Motor Carrier Safety Administration (FMCSA). Crash Preventability Determination Program (updated December 10, 2024), CPDP FAQs (updated December 5, 2024) and CPDP Quarterly Statistics (data as of June 26, 2026; updated August 17, 2026). fmcsa.dot.gov/crash-preventability-determination-program; FAQs; Statistics
- 11National Highway Traffic Safety Administration (NHTSA). Event Data Recorder (research page), accessed October 2026; and eCFR, 49 CFR Part 563, Event Data Recorders (including 563.7 and 563.11), up to date as of October 1, 2026. nhtsa.gov/research-data/event-data-recorder; ecfr.gov … part-563
- 12NIOSH. Traumatic Incident Stress: Information for Emergency Response Workers. DHHS (NIOSH) Publication No. 2002-107. October 2001. cdc.gov/niosh/topics/traumaticincident
- 13OSHA. Using Leading Indicators to Improve Safety and Health Outcomes. June 2019. osha.gov/leading-indicators; PDF
- 14NIOSH. Driver Fatigue on the Job. Last reviewed April 3, 2024. cdc.gov/niosh/motor-vehicle/driver-fatigue
- 15NHTSA. Recalls (VIN lookup) and Report a Safety Problem. Accessed October 2026. nhtsa.gov/recalls; nhtsa.gov/report-a-safety-problem
This article reflects the safety priorities of occupational incident investigation and fleet safety. It is general education, not legal, medical or professional advice for any organization or person. Have qualified HR and legal counsel review policies on reporting, testing, discipline and privacy. Laws, rules and data change, so verify details with official sources such as OSHA, FMCSA, NHTSA and your state agencies. Reviewed October 2026.
Keep reading
More on Workplace and fleet safety
Keep learning
Safe Driving Resource Center
Guides, self-checks and articles for drivers, parents of new drivers, and families recovering after a crash.
