TruckCodex
Hubs

Crash Record KS2022E23500

FMCSA crash record in LENEXA on Mar 9, 2022.

Tow-Away Federal Recordable

What happened

On March 9, 2022, FMCSA recorded a tow-away crash with no reported injuries in LENEXA, Kansas. The vehicle was operated by GREENWOOD MOTOR LINES INC (USDOT 63391). Recorded conditions: 1 / 1 / 1 pavement. Reported by R L CARRIERS, FMCSA reference KS2022E23500.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
5
Carrier
GREENWOOD MOTOR LINES INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
534
22 fatal · 159 injury
Crashes per 100 power units (24 mo)
4.5
467 crashes · 10,382 units
Days since prior carrier crash
1
Last on Mar 8, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers

Geographic context

How this crash sits in its setting.

Within LENEXA, Kansas, 51 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 #:
KS2022E23500
Date:
Mar 9, 2022
Time:
0831
State:
Kansas
City:
LENEXA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
5
Carrier (USDOT):
GREENWOOD MOTOR LINES INC (63391)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XPBD49X9HD286664 2518820 (IN) R L CARRIERS 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
cmtmftnor0017pmdx5zixlcar Aug 29, 2026 FL Injury 0 6
cmtl0dt1t0027pm661v9skttq Aug 28, 2026 NC Injury 0 1
cmt1jo0yv000zpevkxridg62p Aug 14, 2026 NC Tow-Away 0 0
cmsw88shs00jvpev34j4mxsn3 Aug 6, 2026 MO Injury 0 1
cmsw88snp00qbpev3jb4acrnf Aug 5, 2026 KY Tow-Away 0 0
cms1c433n000lpee8liuoymit Jul 20, 2026 VA Tow-Away 0 0
cmrss3v1d003vpefb0zl2vyui Jul 14, 2026 WI Injury 0 2
cmqesjp410019p4us2czdvzx9 Jun 9, 2026 VA Tow-Away 0 0
cmpoujjtp003tr204w1mct2tg May 20, 2026 MN Injury 0 3
cmphifn62000bpjl9r3jaj9y4 May 19, 2026 MN Injury 0 1

Related records

Vehicle
2017 PETERBILT 579
NHTSA recalls and complaints for this make/model/year.
Recall
21V00N000
ELECTRICAL SYSTEM:WIRING
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
20V130000
ELECTRICAL SYSTEM:12V/24V/48V BATTERY:CABLES
Carrier
GREENWOOD MOTOR LINES INC
USDOT 63391 · 3,882 crashes · 11,003 inspections
Vehicle
VIN: 1XPBD49X9HD286664
Decode this VIN for make, model, year, and recall data.
State
Crashes in Kansas
Statewide crash records.
Agency
R L CARRIERS
Crashes reported by this law-enforcement agency.
City
Crashes in LENEXA, 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.