TruckCodex
Hubs

Crash Record MN0230520326

FMCSA crash record in LAKELAND on Feb 21, 2023.

Tow-Away Federal Recordable

What happened

On February 21, 2023, FMCSA recorded a tow-away crash with no reported injuries in LAKELAND, Minnesota. The vehicle was operated by RESTAURANT TECHNOLOGIES INC (USDOT 868454). Recorded conditions: 1 / 1 / 1 pavement. Reported by RESTAURANT TECHNOLOGIES INC, FMCSA reference MN0230520326.

Carrier pattern note

This is the carrier's 24 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
RESTAURANT TECHNOLOGIES INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
24
1 fatal · 9 injury
Crashes per 100 power units (24 mo)
3.3
11 crashes · 337 units
Days since prior carrier crash
5
Last on Feb 16, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,687 carriers

Geographic context

How this crash sits in its setting.

Within LAKELAND, Minnesota, 5 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 #:
MN0230520326
Date:
Feb 21, 2023
Time:
1423
State:
Minnesota
City:
LAKELAND
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
RESTAURANT TECHNOLOGIES INC (868454)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 3 2NKHLJ9X0JM221732 2587PRA (MN) RESTAURANT TECHNOLOGIES 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
cmqlxkjvh0005p8trcdwev25j Jun 16, 2026 ME Tow-Away 0 0
cmphifneq0057pjl9s8zpxjq1 May 16, 2026 PA Tow-Away 0 0
cr_5117830 Mar 14, 2026 MN Tow-Away 0 0
cr_5089325 Jan 8, 2026 MO Injury 0 1
cr_5079420 Dec 28, 2025 MN Tow-Away 0 0
cr_5045718 Oct 12, 2025 TX Tow-Away 0 0
cr_5061084 Oct 11, 2025 MD Tow-Away 0 0
cr_5051169 Sep 22, 2025 FL Injury 0 1
cr_5007126 Jun 11, 2025 PA Tow-Away 0 0
cr_4857898 Dec 1, 2024 FL Tow-Away 0 0

Related records

Carrier
RESTAURANT TECHNOLOGIES INC
USDOT 868454 · 200 crashes · 1,075 inspections
Vehicle
VIN: 2NKHLJ9X0JM221732
Decode this VIN for make, model, year, and recall data.
State
Crashes in Minnesota
Statewide crash records.
Agency
RESTAURANT TECHNOLOGIES INC
Crashes reported by this law-enforcement agency.
City
Crashes in LAKELAND, MN
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.