TruckCodex
Hubs

Crash Record NJ0021147541

FMCSA crash record in FORT LEE BORO on Oct 24, 2021.

Tow-Away Federal Recordable Bus

What happened

On October 24, 2021, FMCSA recorded a tow-away crash with no reported injuries in FORT LEE BORO, New Jersey. The vehicle was operated by NEW JERSEY TRANSIT CORPORATION (USDOT 74293). Recorded conditions: 3 / 1 / 1 pavement. Reported by NJ TRANSIT CORPORATION, FMCSA reference NJ0021147541.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
NEW JERSEY TRANSIT CORPORATION
Vehicle Type
Bus
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
335
7 fatal · 164 injury
Crashes per 100 power units (24 mo)
14.6
349 crashes · 2,394 units
Days since prior carrier crash
2
Last on Oct 22, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,845 carriers

Geographic context

How this crash sits in its setting.

Within FORT LEE BORO, New Jersey, 29 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
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 #:
NJ0021147541
Date:
Oct 24, 2021
Time:
2037
State:
New Jersey
City:
FORT LEE BORO
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
NEW JERSEY TRANSIT CORPORATION (74293)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 4 2 1N94161528A140049 OXZ4815 (NJ) NJ TRANSIT CORPORATION 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
cmtzbpps2001vpmsrlk2pe3hg Sep 8, 2026 NJ Injury 0 1
cmtwgme30005lpmiyxe455xj7 Sep 3, 2026 NJ Tow-Away 0 0
cmtwgme0o001jpmiyo2t20ptm Sep 3, 2026 NJ Injury 0 2
cmtmftnp0001hpmdx72glwxhw Aug 29, 2026 NJ Tow-Away 0 0
cmtgtnbzf002dpmmo6us2jv41 Aug 26, 2026 NJ Injury 0 2
cmtdwm2rg0021pmb9xyikeafr Aug 23, 2026 NJ Tow-Away 0 0
cmsw88s3o002zpev39d4u0nh4 Aug 10, 2026 NJ Tow-Away 0 0
cmsw88s8n007rpev33mp6jxbj Aug 10, 2026 NJ Tow-Away 0 0
cmsw88sez00fzpev3omfwks3j Aug 7, 2026 NJ Tow-Away 0 0
cmsw88sce00czpev39mdifi9g Aug 7, 2026 NJ Tow-Away 0 0

Related records

Carrier
NEW JERSEY TRANSIT CORPORATION
USDOT 74293 · 4,487 crashes · 9,633 inspections
Vehicle
VIN: 1N94161528A140049
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
NJ TRANSIT CORPORATION
Crashes reported by this law-enforcement agency.
City
Crashes in FORT LEE BORO, NJ
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.