Crash Record MD1210601581

FMCSA crash record in Maryland on Nov 11, 2012.

Tow-Away

What happened

On November 11, 2012, FMCSA recorded a tow-away crash with no reported injuries in Maryland. The vehicle was operated by VERIZON MARYLAND LLC (USDOT 339370). FMCSA reference MD1210601581.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
Carrier
VERIZON MARYLAND LLC
Vehicle Type
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
13
4 injury · 10 tow-away
Crashes per 100 power units (24 mo)
0.3
2 crashes · 635 units
Days since prior carrier crash
18
Last on Oct 24, 2012
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,828 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 4,403 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
MD1210601581
Date:
Nov 11, 2012
Time:
1352
State:
Maryland
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4861576 Nov 21, 2024 MD Tow-Away 0 0
cr_4907760 Oct 22, 2024 MD Injury 0 1
cr_4705405 Sep 20, 2023 MD Injury 0 1
cr_4695392 Sep 13, 2023 MD Tow-Away 0 0
cr_4437806 Oct 7, 2022 MD Tow-Away 0 0
cr_4380742 Jun 17, 2022 MD Injury 0 1
cr_4287581 Dec 22, 2021 MD Tow-Away 0 0
cr_4278725 Dec 14, 2021 MD Tow-Away 0 0
cr_4290836 Dec 7, 2021 MD Injury 0 2
cr_4253802 Oct 29, 2021 MD Tow-Away 0 0

Related records

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.