Crash Record NJ0021101195
FMCSA crash record in FIELDSBORO BORO on Jan 15, 2021.
Fatal
Federal Recordable
Bus
What happened
On January 15, 2021, FMCSA recorded a fatal crash that resulted in one death in FIELDSBORO BORO, New Jersey. The vehicle was operated by NEW JERSEY TRANSIT CORPORATION (USDOT 74293). Recorded conditions: 3 / 2 / 2 pavement. Reported by NJ TRANSIT CORPORATION, FMCSA reference NJ0021101195.
Carrier pattern note
This is the carrier's 340 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.
Fatalities
1
Injuries
0
Vehicles
1
Carrier
NEW JERSEY TRANSIT CORPORATION
Vehicle Type
Bus
Severity
Fatal
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
340
10 fatal · 184 injury
Crashes per 100 power units (24 mo)
16.3
391 crashes · 2,394 units
Days since prior carrier crash
1
Last on Jan 14, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,812 carriers
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 #:
- NJ0021101195
- Date:
- Jan 15, 2021
- Time:
- 2227
- State:
- New Jersey
- City:
- FIELDSBORO BORO
- Fatalities:
- 1
- Injuries:
- 0
- Tow-Away:
- No
- HazMat:
- No
- Vehicles:
- 1
- 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 | 1M8PDMBA9JP015011 | OYB4611 (NJ) | NJ TRANSIT CORPORATION | 2 | No |
Other crashes by this carrier
10 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cmrk8ir07003fpelc8nb6vfk2 | Jul 7, 2026 | NJ | Injury | 0 | 1 |
| cmrfwlwhw000tmlhrd3y7nev2 | Jul 6, 2026 | NJ | Tow-Away | 0 | 0 |
| cmr318zqb000jp8ay5xn0kk7q | Jun 27, 2026 | NJ | Tow-Away | 0 | 0 |
| cmr318zrt001tp8ayomvetf7c | Jun 26, 2026 | NJ | Tow-Away | 0 | 0 |
| cmqyq8pq7005vp8arjz88mutm | Jun 23, 2026 | NJ | Injury | 0 | 1 |
| cmqkg782c00a3p8fym94daqyz | Jun 11, 2026 | NJ | Injury | 0 | 1 |
| cmqkg784z00d3p8fygduwx8nz | Jun 11, 2026 | NJ | Tow-Away | 0 | 0 |
| cmqbvahab000fqumal7hozbui | Jun 9, 2026 | NJ | Injury | 0 | 3 |
| cmqesjq8y006np4us2l2fg0qr | Jun 8, 2026 | NJ | Tow-Away | 0 | 0 |
| cmqesjpkd002pp4us8vqjy4po | Jun 8, 2026 | NJ | Tow-Away | 0 | 0 |
Related records
Carrier
NEW JERSEY TRANSIT CORPORATION
USDOT 74293 · 4,474 crashes · 9,287 inspections
Vehicle
VIN: 1M8PDMBA9JP015011
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 FIELDSBORO 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.
How to evaluate a carrier's crash record
- Look at frequency, not any single crash. A single crash record rarely tells you anything decisive about a carrier. Pull the carrier's full multi-year crash list and look at the rate over time — clusters and trends matter more than any one event.
- Calculate crashes per power unit when data is available. Divide the 24-month crash count by the carrier's reported power units. A rate of one crash per power unit per year is high; a rate of one crash per ten power units per year is closer to industry baseline. Skip this step when power_units is missing or zero — the rate is meaningless without it.
- Filter for fault-attributed crashes. FMCSA crash records do not flag fault. To distinguish preventable from non-preventable, check whether the carrier requested a Preventability Determination through DataQs and what FMCSA ruled. Only the preventable crashes are a clean signal of carrier or driver behavior.
- Compare against fleet-size peers. Crash counts cannot be compared directly between fleets of different sizes. Use the SMS Crash Indicator percentile, or compare the carrier's crashes-per-power-unit rate against the median for its fleet-size cohort. A 50-truck carrier with 4 crashes in 24 months looks very different from a 5-truck carrier with the same count.
- Cross-reference with the SMS BASIC Crash Indicator. FMCSA's Safety Measurement System publishes a Crash Indicator percentile when the carrier has enough crashes and exposure to score. A score in the 65th percentile or higher triggers federal intervention thresholds. Always sanity-check raw crash counts against the percentile before drawing conclusions.
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.
Data sources & freshness
TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.
Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.
Refreshed daily.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Refreshed daily.
Cross-border carrier registry and Canadian recall campaigns where applicable.
Refreshed weekly.
TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.