TruckCodex
Hubs

Crash Record AL0004638209

FMCSA crash record in BIRMINGHAM on Mar 16, 2024.

Tow-Away Federal Recordable

What happened

On March 16, 2024, FMCSA recorded a tow-away crash with no reported injuries in BIRMINGHAM, Alabama. The vehicle was operated by SEI ACQUISITION LLC (USDOT 484360). Recorded conditions: 1 / 2 / 2 pavement. Reported by SKYLINE EXPRESS, FMCSA reference AL0004638209.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 255 crashes occurred in the same city in the past 24 months.

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

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
21
7 injury · 20 tow-away
Crashes per 100 power units (24 mo)
3.1
20 crashes · 650 units
Days since prior carrier crash
61
Last on Jan 15, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,849 carriers

Geographic context

How this crash sits in its setting.

Within BIRMINGHAM, Alabama, 255 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
2
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 #:
AL0004638209
Date:
Mar 16, 2024
Time:
1155
State:
Alabama
City:
BIRMINGHAM
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
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 6 12 3HSDJAPR0HN429853 U607089 (TN) SKYLINE EXPRESS 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
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

Vehicle
2017 INTERNATIONAL LF687
NHTSA recalls and complaints for this make/model/year.
Carrier
SEI ACQUISITION LLC
USDOT 484360 · 104 crashes · 1,105 inspections
Vehicle
VIN: 3HSDJAPR0HN429853
Decode this VIN for make, model, year, and recall data.
State
Crashes in Alabama
Statewide crash records.
Agency
SKYLINE EXPRESS
Crashes reported by this law-enforcement agency.
City
Crashes in BIRMINGHAM, AL
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.

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.