TruckCodex
Hubs

Crash Record WI0000125535

FMCSA crash record in MILWAUKEE on May 22, 2025.

Injury Federal Recordable Bus

What happened

On May 22, 2025, FMCSA recorded an injury crash with one person hurt in MILWAUKEE, Wisconsin. The vehicle was operated by FIRST STUDENT INC (USDOT 354406). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference WI0000125535.

Carrier pattern note

This is the carrier's 728 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: 301 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
FIRST STUDENT INC
Vehicle Type
Bus
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
728
5 fatal · 302 injury
Crashes per 100 power units (24 mo)
1.5
539 crashes · 34,955 units
Days since prior carrier crash
3
Last on May 19, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within MILWAUKEE, Wisconsin, 301 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
1

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 #:
WI0000125535
Date:
May 22, 2025
Time:
0751
State:
Wisconsin
City:
MILWAUKEE
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FIRST STUDENT INC (354406)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 4 2 1BAKBCBA2EF300602 27451B (WI) FIRST STUDENT INC 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
cmsw88so600rhpev3x8531vrh Aug 5, 2026 MO Tow-Away 0 0
cmqkg78co00knp8fy0m4z4x21 Jun 10, 2026 NJ Injury 0 1
cmny3yh7c016hk38vejvw7z1u Apr 1, 2026 OH Tow-Away 0 0
cr_5127200 Mar 31, 2026 MN Injury 0 1
cmny3ygwq00wdk38v79rqx4gq Mar 31, 2026 MN Injury 0 1
cr_5124701 Mar 25, 2026 MN Tow-Away 0 0
cr_5126532 Mar 24, 2026 LA Tow-Away 0 0
cr_5121885 Mar 16, 2026 PA Injury 0 1
cr_5117794 Mar 12, 2026 MN Injury 0 1
cr_5117793 Mar 11, 2026 MN Tow-Away 0 0

Related records

Vehicle
2014 BLUE BIRD BB Conventional
NHTSA recalls and complaints for this make/model/year.
Carrier
FIRST STUDENT INC
USDOT 354406 · 8,067 crashes · 17,309 inspections
Vehicle
VIN: 1BAKBCBA2EF300602
Decode this VIN for make, model, year, and recall data.
State
Crashes in Wisconsin
Statewide crash records.
City
Crashes in MILWAUKEE, WI
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.