Crash Record NJ0023139189
FMCSA crash record in EAST ORANGE CITY on May 11, 2023.
Injury
Federal Recordable
Bus
What happened
On May 11, 2023, FMCSA recorded an injury crash with one person hurt in EAST ORANGE CITY, New Jersey. The vehicle was operated by NEW JERSEY TRANSIT CORPORATION (USDOT 74293). Recorded conditions: 1 / 1 / 1 pavement. Reported by NJ TRANSIT CORPORATION, FMCSA reference NJ0023139189.
Carrier pattern note
This is the carrier's 424 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.
Fatalities
0
Injuries
1
Vehicles
2
Carrier
NEW JERSEY TRANSIT CORPORATION
Vehicle Type
Bus
Severity
Injury
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
424
8 fatal · 238 injury
Crashes per 100 power units (24 mo)
14.9
356 crashes · 2,394 units
Days since prior carrier crash
1
Last on May 10, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,837 carriers
Geographic context
How this crash sits in its setting.
Within EAST ORANGE CITY, New Jersey, 12 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- NJ TRANSIT CORPORATION · 3 reports
- CITY OF EAST ORANGE · 2 reports
- BIOTRANS LLC · 1 reports
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 #:
- NJ0023139189
- Date:
- May 11, 2023
- Time:
- 0640
- State:
- New Jersey
- City:
- EAST ORANGE CITY
- Fatalities:
- 0
- Injuries:
- 1
- Tow-Away:
- No
- 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 | 1N9416061CA140708 | OYA6325 (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 |
|---|---|---|---|---|---|
| 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 |
| cmsmuqxy80013pexoqlrn84lk | Aug 5, 2026 | NJ | Tow-Away | 0 | 0 |
| cmsbbctq4002tpemdbnvwc3ov | Jul 28, 2026 | NJ | Injury | 0 | 4 |
| cmrzwwgrl000rpe2147e2440t | Jul 20, 2026 | NJ | Injury | 0 | 1 |
Related records
Carrier
NEW JERSEY TRANSIT CORPORATION
USDOT 74293 · 4,484 crashes · 9,541 inspections
Vehicle
VIN: 1N9416061CA140708
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 EAST ORANGE CITY, 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.