Skip to main content

Crash Record MD19A0582093

FMCSA crash record in Maryland on May 10, 2019.

Injury

What happened

On May 10, 2019, FMCSA recorded an injury crash with one person hurt in Maryland. The vehicle was operated by CASTERA TRANSPORTATION SERVICES LLC (USDOT 1623751). FMCSA reference MD19A0582093.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
—
Carrier
CASTERA TRANSPORTATION SERVICES LLC
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
3 injury · 9 tow-away
Crashes per 100 power units (24 mo)
4.2
1 crashes · 24 units
Days since prior carrier crash
38
Last on Apr 2, 2019
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,547 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 4,053 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 #:
MD19A0582093
Date:
May 10, 2019
Time:
1018
State:
Maryland
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5006354 May 31, 2025 PA Tow-Away 0 0
cr_4833016 Sep 7, 2024 PA Tow-Away 0 0
cr_4737305 Apr 20, 2024 VA Tow-Away 0 0
cr_4666628 Oct 7, 2023 MD Tow-Away 0 0
cr_4691251 Sep 7, 2023 MD Injury 0 2
cr_4696718 Jul 22, 2023 MD Tow-Away 0 0
cr_4598177 Jul 2, 2023 MD Injury 0 4
cr_4582951 Jun 23, 2023 NY Tow-Away 0 0
cr_4573947 May 25, 2023 PA Tow-Away 0 0
cr_4660187 May 16, 2023 VA Injury 0 4

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.