TruckCodex
Hubs

Crash Record CA1941013734

FMCSA crash record in LONG BEACH on Mar 20, 2022.

Injury Federal Recordable

What happened

On March 20, 2022, FMCSA recorded an injury crash with one person hurt in LONG BEACH, California. The vehicle was operated by IN-N-OUT BURGER INC (USDOT 493390). Recorded conditions: 3 / 2 / 2 pavement. Reported by IN-N-OUT BURGER INC, FMCSA reference CA1941013734.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
IN-N-OUT BURGER INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
6 injury · 8 tow-away
Crashes per 100 power units (24 mo)
3.2
7 crashes · 216 units
Days since prior carrier crash
18
Last on Mar 2, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,685 carriers

Geographic context

How this crash sits in its setting.

Within LONG BEACH, California, 207 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
3
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 #:
CA1941013734
Date:
Mar 20, 2022
Time:
0144
State:
California
City:
LONG BEACH
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
IN-N-OUT BURGER INC (493390)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 98 1XPXD49XXHD415923 9E86338 (CA) IN-N-OUT BURGER 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
cr_5012029 Jun 29, 2025 TX Tow-Away 0 0
cr_4929601 Mar 14, 2025 CA Injury 0 2
cr_4898613 Jan 29, 2025 CA Injury 0 2
cr_4874042 Jan 13, 2025 AZ Tow-Away 0 0
cr_4859060 Nov 15, 2024 CA Tow-Away 0 0
cr_4862219 Nov 8, 2024 CA Tow-Away 0 0
cr_4851183 Oct 10, 2024 CA Tow-Away 0 0
cr_4805807 Aug 15, 2024 CA Injury 0 1
cr_4756410 May 23, 2024 CA Injury 0 1
cr_4759794 May 20, 2024 CA Tow-Away 0 0

Related records

Vehicle
2017 PETERBILT 389
NHTSA recalls and complaints for this make/model/year.
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
20V130000
ELECTRICAL SYSTEM:12V/24V/48V BATTERY:CABLES
Recall
18V657000
ENGINE AND ENGINE COOLING:ENGINE:DIESEL
Carrier
IN-N-OUT BURGER INC
USDOT 493390 · 68 crashes · 273 inspections
Vehicle
VIN: 1XPXD49XXHD415923
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
IN-N-OUT BURGER INC
Crashes reported by this law-enforcement agency.
City
Crashes in LONG BEACH, CA
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.