Skip to main content
TruckCodex
Hubs

Crash Record CT2500337096

FMCSA crash record in DANBURY on Sep 19, 2025.

Tow-Away Federal Recordable

What happened

On September 19, 2025, FMCSA recorded a tow-away crash with no reported injuries in DANBURY, Connecticut. The vehicle was operated by FEDERAL EXPRESS CORPORATION (USDOT 86876). Recorded conditions: 3 / 1 / 1 pavement. Reported by FEDERAL EXPRESS CORPORATION, FMCSA reference CT2500337096.

Carrier pattern note

This is the carrier's 2229 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.

Geographic note

This crash is part of an active corridor: 84 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FEDERAL EXPRESS CORPORATION
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2,229
53 fatal · 786 injury
Crashes per 100 power units (24 mo)
1.7
2,401 crashes · 138,481 units
Days since prior carrier crash
1
Last on Sep 18, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,864 carriers

Geographic context

How this crash sits in its setting.

Within DANBURY, Connecticut, 84 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
3
Weather
1
Road surface
1

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:
CT2500337096
Date:
Sep 19, 2025
Time:
2113
State:
Connecticut
City:
DANBURY
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FEDERAL EXPRESS CORPORATION (86876)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 4V4NC9EH3SN684469 2853980 (IN) FEDERAL EXPRESS CORPORATION 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmuqivngy000fnvixnjmegblk Sep 28, 2026 MN Tow-Away 0 0
cmup2ni6p00afl4z8zcsv3e54 Sep 21, 2026 OH Injury 0 2
cmup2ni6q00ajl4z8v44okx7q Sep 21, 2026 ME Tow-Away 0 0
cmu507cav000hpmtod4z1831t Sep 13, 2026 ME Tow-Away 0 0
cmu507ces005rpmtow13xvjpw Sep 9, 2026 NJ Tow-Away 0 0
cmtzbpprh000zpmsr5qlx21nw Sep 8, 2026 VA Injury 0 1
cmtqq5agv001zpmkttbo81660 Sep 2, 2026 NJ Injury 0 2
cmtmftnpq002vpmdxdrb4lbq3 Aug 28, 2026 KY Tow-Away 0 0
cmtl0dt2a002zpm66q8qu1cl3 Aug 27, 2026 NC Tow-Away 0 0
cmtfchmfj0009pmjnybpu3leu Aug 26, 2026 OK Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 86876 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
FEDERAL EXPRESS CORPORATION
USDOT 86876 · 9,258 crashes · 26,926 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 4V4NC9EH3SN684469
Decode this VIN for make, model, year, and recall data.
State
Crashes in Connecticut
Statewide crash records.
Agency
FEDERAL EXPRESS CORPORATION
Crashes reported by this law-enforcement agency.
City
Crashes in DANBURY, CT
All crashes on file for this city.
Index
All Crash Records
Browse FMCSA commercial vehicle crash records.
Database
Roadside Inspections
Inspection history and violation details.
Database
NHTSA Recalls
Active recall campaigns.

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾
An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.
Was this crash the carrier's fault? ▾
FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.
How does this crash affect the carrier's safety scores? ▾
Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.
Will this crash show up on the carrier's CSA SMS scores? ▾
If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.
How do I check the carrier's full crash history? ▾
Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.
What if details look wrong — how do I correct an FMCSA crash record? ▾
FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.