TruckCodex
Hubs

Crash Record MD23A1095268

FMCSA crash record in Maryland on Dec 18, 2023.

Injury Federal Recordable

What happened

On December 18, 2023, FMCSA recorded an injury crash with one person hurt in Maryland. The vehicle was operated by SEI ACQUISITION LLC (USDOT 484360). Recorded conditions: 1 / 1 / 2 pavement. Reported by SEI ACQUISITION LLC, FMCSA reference MD23A1095268.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
SEI ACQUISITION LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
23
6 injury · 22 tow-away
Crashes per 100 power units (24 mo)
3.1
20 crashes · 650 units
Days since prior carrier crash
14
Last on Dec 4, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,850 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 4,142 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
2

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 #:
MD23A1095268
Date:
Dec 18, 2023
Time:
0936
State:
Maryland
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
SEI ACQUISITION LLC (484360)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 2HSCUAPR18C660541 3514765 (IN) SEI ACQUISITION LLC 3 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5126040 Mar 10, 2026 NJ Tow-Away 0 0
cr_5121477 Feb 1, 2026 IL Injury 0 1
cr_5092708 Jan 21, 2026 MI Tow-Away 0 0
cr_5111001 Jan 21, 2026 PA Injury 0 1
cr_5094664 Nov 26, 2025 IL Tow-Away 0 0
cr_5071628 Nov 21, 2025 SC Injury 0 1
cr_5050762 Oct 1, 2025 PA Tow-Away 0 0
cr_5050189 Sep 17, 2025 PA Tow-Away 0 0
cr_5054128 Aug 22, 2025 AL Injury 0 1
cr_4995276 Jun 24, 2025 IL Tow-Away 0 0

Related records

Carrier
SEI ACQUISITION LLC
USDOT 484360 · 104 crashes · 1,105 inspections
Vehicle
VIN: 2HSCUAPR18C660541
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
SEI ACQUISITION LLC
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.