Skip to main content
TruckCodex
Hubs

Crash Record KS2023E26393

FMCSA crash record in WICHITA on Jan 19, 2023.

Tow-Away Federal Recordable Bus

What happened

On January 19, 2023, FMCSA recorded a tow-away crash with no reported injuries in WICHITA, Kansas. The vehicle was operated by FIRST STUDENT INC (USDOT 354406). Recorded conditions: 5 / 1 / 1 pavement. Reported by FIRST STUDENT, FMCSA reference KS2023E26393.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FIRST STUDENT INC
USDOT 354406
Vehicle Type
Bus
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
685
7 fatal · 281 injury
Crashes per 100 power units (24 mo)
1.4
481 crashes · 34,955 units
Days since prior carrier crash
1
Last on Jan 18, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,867 carriers

Geographic context

How this crash sits in its setting.

Within WICHITA, Kansas, 113 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
5
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 #:
KS2023E26393
Date:
Jan 19, 2023
Time:
0633
State:
Kansas
City:
WICHITA
Fatalities:
0
Injuries:
0
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
1 4 2 1HA6GUBG7LN011264 702350 (KS) FIRST STUDENT 2 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
cmurx4kvj0019nv7mi8magqof Sep 28, 2026 MN Tow-Away 0 0
cmuar6ljk000bpma7lkzkmmfh Sep 15, 2026 ME Fatal 1 1
cmuar6lln001hpma7zwjojbyp Sep 14, 2026 MO Tow-Away 0 0
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

Carrier booking & risk tools

Check booking and risk signals for USDOT 354406 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
FIRST STUDENT INC
USDOT 354406 · 8,070 crashes · 17,482 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1HA6GUBG7LN011264
Decode this VIN for make, model, year, and recall data.
State
Crashes in Kansas
Statewide crash records.
Agency
FIRST STUDENT
Crashes reported by this law-enforcement agency.
City
Crashes in WICHITA, KS
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.