TruckCodex
Hubs

Crash Record MD21A0776951

FMCSA crash record in Maryland on Mar 15, 2021.

Tow-Away Federal Recordable

What happened

On March 15, 2021, FMCSA recorded a tow-away crash with no reported injuries in Maryland. The vehicle was operated by FEDEX CUSTOM CRITICAL INC (USDOT 164025). Recorded conditions: 1 / 1 / 1 pavement. Reported by FEDEX CUSTOM CRITICAL INC, FMCSA reference MD21A0776951.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
3
Carrier
FEDEX CUSTOM CRITICAL INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
60
2 fatal · 20 injury
Crashes per 100 power units (24 mo)
3.9
32 crashes · 811 units
Days since prior carrier crash
6
Last on Mar 9, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 4,336 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
1
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 #:
MD21A0776951
Date:
Mar 15, 2021
Time:
1506
State:
Maryland
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
FEDEX CUSTOM CRITICAL INC (164025)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 3ALAC4DV0HDHT2860 PWM3181 (OH) FEDEX CUSTOM CRITICAL INC 2 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5126791 Mar 19, 2026 OH Tow-Away 0 0
cr_5116177 Mar 3, 2026 OH Injury 0 3
cr_5116146 Mar 3, 2026 OH Tow-Away 0 0
cr_5109002 Feb 16, 2026 OH Injury 0 1
cr_5110851 Feb 6, 2026 IN Tow-Away 0 0
cr_5082177 Dec 24, 2025 TN Tow-Away 0 0
cr_5082920 Dec 23, 2025 NC Tow-Away 0 0
cr_5062818 Nov 19, 2025 TN Injury 0 1
cr_5020053 Aug 29, 2025 TN Tow-Away 0 0
cr_5028573 Aug 22, 2025 VA Tow-Away 0 0

Related records

Carrier
FEDEX CUSTOM CRITICAL INC
USDOT 164025 · 959 crashes · 2,641 inspections
Vehicle
VIN: 3ALAC4DV0HDHT2860
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
FEDEX CUSTOM CRITICAL INC
Crashes reported by this law-enforcement agency.
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.