TruckCodex

Crash Record MD26A1331670

FMCSA crash record in SEVERNA PARK on Jan 29, 2026.

Tow-Away Federal Recordable

What happened

On January 29, 2026, FMCSA recorded a tow-away crash with no reported injuries in SEVERNA PARK, Maryland. The vehicle was operated by MEDTRANS LLC (USDOT 987933). Recorded conditions: 1 / 1 / 6 pavement. Reported by MED TRANS LLC, FMCSA reference MD26A1331670.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
MEDTRANS LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
93
2 fatal · 32 injury
Crashes per 100 power units (24 mo)
4.0
86 crashes · 2,128 units
Days since prior carrier crash
2
Last on Jan 27, 2026
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,808 carriers

Geographic context

How this crash sits in its setting.

Within SEVERNA PARK, Maryland, 6 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
6

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 #:
MD26A1331670
Date:
Jan 29, 2026
Time:
0922
State:
Maryland
City:
SEVERNA PARK
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
MEDTRANS LLC (987933)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 8 12 3HSDZTZR3NN548395 3127636 (IN) MED TRANS LLC 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
cmodru0z10001nvfd30ie4uvl Apr 22, 2026 MA Injury 0 1
cmo6itl8g0084o1auv3xj0ywj Apr 13, 2026 MO Tow-Away 0 0
cr_5122057 Mar 16, 2026 MA Tow-Away 0 0
cr_5122111 Mar 13, 2026 MI Injury 0 1
cr_5115483 Mar 6, 2026 IA Tow-Away 0 0
cr_5115159 Mar 3, 2026 PA Injury 0 1
cr_5125729 Feb 23, 2026 IN Tow-Away 0 0
cr_5109929 Feb 20, 2026 AL Injury 0 1
cr_5111436 Feb 6, 2026 CA Tow-Away 0 0
cr_5094248 Jan 27, 2026 TN Tow-Away 0 0

Related records

Carrier
MEDTRANS LLC
USDOT 987933 · 360 crashes · 1,917 inspections
Vehicle
VIN: 3HSDZTZR3NN548395
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
MED TRANS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in SEVERNA PARK, MD
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.

How to evaluate a carrier's crash record

  1. Look at frequency, not any single crash. A single crash record rarely tells you anything decisive about a carrier. Pull the carrier's full multi-year crash list and look at the rate over time — clusters and trends matter more than any one event.
  2. Calculate crashes per power unit when data is available. Divide the 24-month crash count by the carrier's reported power units. A rate of one crash per power unit per year is high; a rate of one crash per ten power units per year is closer to industry baseline. Skip this step when power_units is missing or zero — the rate is meaningless without it.
  3. Filter for fault-attributed crashes. FMCSA crash records do not flag fault. To distinguish preventable from non-preventable, check whether the carrier requested a Preventability Determination through DataQs and what FMCSA ruled. Only the preventable crashes are a clean signal of carrier or driver behavior.
  4. Compare against fleet-size peers. Crash counts cannot be compared directly between fleets of different sizes. Use the SMS Crash Indicator percentile, or compare the carrier's crashes-per-power-unit rate against the median for its fleet-size cohort. A 50-truck carrier with 4 crashes in 24 months looks very different from a 5-truck carrier with the same count.
  5. Cross-reference with the SMS BASIC Crash Indicator. FMCSA's Safety Measurement System publishes a Crash Indicator percentile when the carrier has enough crashes and exposure to score. A score in the 65th percentile or higher triggers federal intervention thresholds. Always sanity-check raw crash counts against the percentile before drawing conclusions.

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.

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

FMCSA

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.
NHTSA

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.
Transport Canada

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.