Crash Record NJ0021704436

FMCSA crash record in OAKLAND BORO on Jul 9, 2021.

Injury Federal Recordable

What happened

On July 9, 2021, FMCSA recorded an injury crash with one person hurt in OAKLAND BORO, New Jersey. The vehicle was operated by LG TRUCKING AND REPAIR INC (USDOT 1205872). Recorded conditions: 1 / 2 / 2 pavement. Reported by LG TRUCKING AND REPAIR INC, FMCSA reference NJ0021704436.

Fatalities

Injuries

Vehicles

Carrier

LG TRUCKING AND REPAIR INC

USDOT 1205872

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 2 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 4 units

Days since prior carrier crash

Last on Jun 21, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,580,316 carriers

Geographic context

How this crash sits in its setting.

Within OAKLAND BORO, New Jersey, 6 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

ABF FREIGHT SYSTEM INC · 1 reports
FLEET16 TRUCKING LLC · 1 reports
F P DUFFY INC · 1 reports

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 #:: NJ0021704436
Date:: Jul 9, 2021
Time:: 0618
State:: New Jersey
City:: OAKLAND BORO
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: LG TRUCKING AND REPAIR INC (1205872)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	8	12	1XPHD49X8ED227174	AG72743 (PA)	LG TRUCKING AND REPAIR INC	3	No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

9 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4566815	May 30, 2023	CT	Tow-Away	0
cr_4199075	Aug 2, 2021	PA	Tow-Away	0
cr_4184252	Jun 21, 2021	PA	Injury	1
cr_3124050	Oct 7, 2015	CT	Tow-Away	0
cr_3049178	Mar 29, 2015	PA	Tow-Away	0
cr_2217778	Dec 29, 2009	OH	Injury	1
cr_1803773	Mar 16, 2007	PA	Tow-Away	0
cr_1532246	Jun 10, 2005	NJ	Tow-Away	0
cr_1345901	Jul 23, 2004	PA	Injury	3

Carrier booking & risk tools

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

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle

2014 PETERBILT 386

NHTSA recalls and complaints for this make/model/year.

Recall

20V199000

ELECTRONIC STABILITY CONTROL (ESC)

ELECTRICAL SYSTEM:ALTERNATOR/GENERATOR/REGULATOR

Carrier

LG TRUCKING AND REPAIR INC

USDOT 1205872 · 10 crashes · 6 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XPHD49X8ED227174

Decode this VIN for make, model, year, and recall data.

State

Crashes in New Jersey

Statewide crash records.

Agency

LG TRUCKING AND REPAIR INC

Crashes reported by this law-enforcement agency.

City

Crashes in OAKLAND BORO, NJ

All crashes on file for this city.

Station

I-287

Weigh / inspection station matching this crash location.

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.