Crash Record MD15A0113628

FMCSA crash record in Maryland on Mar 4, 2015.

Injury

What happened

On March 4, 2015, FMCSA recorded an injury crash with one person hurt in Maryland. The vehicle was operated by DTL TRANSPORT INC (USDOT 1637148). FMCSA reference MD15A0113628.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
Carrier
DTL TRANSPORT INC
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
2 injury · 4 tow-away
Crashes per 100 power units (24 mo)
7.1
7 crashes · 98 units
Days since prior carrier crash
91
Last on Dec 3, 2014
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,685 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 4,379 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 #:
MD15A0113628
Date:
Mar 4, 2015
Time:
1250
State:
Maryland
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
DTL TRANSPORT INC (1637148)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5122383 Mar 14, 2026 AL Tow-Away 0 0
cr_4990169 Jul 11, 2025 CA Tow-Away 0 0
cr_4877825 Dec 20, 2024 IN Tow-Away 0 0
cr_4849123 Nov 4, 2024 MO Tow-Away 0 0
cr_4848017 Nov 3, 2024 OK Tow-Away 0 0
cr_4834530 Oct 24, 2024 MO Tow-Away 0 0
cr_4811464 Sep 11, 2024 AZ Tow-Away 0 0
cr_4788017 Jul 9, 2024 CA Tow-Away 0 0
cr_4769641 Jun 24, 2024 TN Injury 0 1
cr_4651494 Nov 1, 2023 NM Injury 0 2

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.