TruckCodex
Hubs

Crash Record MO0000095430

FMCSA crash record in ST PETERS on Feb 2, 2022.

Injury Federal Recordable

What happened

On February 2, 2022, FMCSA recorded an injury crash with one person hurt in ST PETERS, Missouri. The vehicle was operated by ALIF UZ CORP (USDOT 3472462). Recorded conditions: 1 / 4 / 4 pavement. Reported by ALIF UZ CORP, FMCSA reference MO0000095430.

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
ALIF UZ CORP
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
15.3
23 crashes · 150 units
Prior carrier crash
—
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,680 carriers

Geographic context

How this crash sits in its setting.

Within ST PETERS, Missouri, 74 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
4
Road surface
4

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 #:
MO0000095430
Date:
Feb 2, 2022
Time:
1024
State:
Missouri
City:
ST PETERS
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
ALIF UZ CORP (3472462)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJGLDR4GS6Z1844 PWP1977 (OH) ALIF UZ CORP 3 No

Crash event

Event sequence description.

1:98:OTHER;3:98:OTHER:OTHER;4:6:NONCOLLISION:EXPLOSION OR FIRE;2:98:OTHER:OTHER

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5108421 Feb 12, 2026 AL Fatal 1 0
cr_5074208 Nov 13, 2025 CA Tow-Away 0 0
cr_5067455 Oct 23, 2025 IN Tow-Away 0 0
cr_5052768 Oct 16, 2025 OK Injury 0 1
cr_5031673 Sep 10, 2025 OK Tow-Away 0 0
cr_5026544 Sep 7, 2025 OR Tow-Away 0 0
cr_5025753 Aug 28, 2025 PA Tow-Away 0 0
cr_4998284 Aug 15, 2025 KS Injury 0 1
cr_5008245 Jul 31, 2025 PA Tow-Away 0 0
cr_5004079 Jul 13, 2025 NM Tow-Away 0 0

Related records

Vehicle
2016 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
20V214000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
19V093000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
ALIF UZ CORP
USDOT 3472462 · 29 crashes · 486 inspections
Vehicle
VIN: 3AKJGLDR4GS6Z1844
Decode this VIN for make, model, year, and recall data.
State
Crashes in Missouri
Statewide crash records.
Agency
ALIF UZ CORP
Crashes reported by this law-enforcement agency.
City
Crashes in ST PETERS, MO
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.