Skip to main content
TruckCodex
Hubs

Crash Record MO0000103911

FMCSA crash record in NON-CITY OR UNINCORPORATE on Aug 3, 2023.

Injury Federal Recordable

What happened

On August 3, 2023, FMCSA recorded an injury crash with one person hurt in NON-CITY OR UNINCORPORATE, Missouri. The vehicle was operated by PASCHALL TRUCK LINES INC (USDOT 105234). Recorded conditions: 1 / 2 / 2 pavement. FMCSA reference MO0000103911.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
3
Carrier
USDOT 105234
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
115
3 fatal · 31 injury
Crashes per 100 power units (24 mo)
8.3
91 crashes · 1,092 units
Days since prior carrier crash
7
Last on Jul 27, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,881 carriers

Geographic context

How this crash sits in its setting.

Within NON-CITY OR UNINCORPORATE, Missouri, 3,481 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 #:
MO0000103911
Date:
Aug 3, 2023
Time:
0836
State:
Missouri
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
3

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
3 9 3 3AKJHHDV2MSMM0661 3035340 (IN) PASCHALL TRUCK LINES INC 3 No

Crash event

Event sequence description.

1:98:OTHER;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmvettpuu003vogss08y0ke4e Oct 13, 2026 KY Tow-Away 0 0
cmqafcggh003dqun6gc8yy7ex Jun 6, 2026 AR Tow-Away 0 0
cmphifne30045pjl95t5inav8 May 18, 2026 KY Injury 0 1
cmp0olg740027nuqwy3ta8be0 May 6, 2026 KY Tow-Away 0 0
cmodru16b003rnvfdglv3ak2s Apr 17, 2026 KY Injury 0 1
cmo6itl030017o1auud9uu4ty Apr 15, 2026 TN Injury 0 1
cmny3yfxk00bck38vni3m6l46 Apr 3, 2026 KY Tow-Away 0 0
cr_5118760 Mar 11, 2026 OH Tow-Away 0 0
cr_5111604 Feb 28, 2026 KY Injury 0 1
cr_5117386 Feb 19, 2026 CA Injury 0 1

Carrier booking & risk tools

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

Related records

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.