Skip to main content
TruckCodex
Hubs

Crash Record NJ0022109543

FMCSA crash record in LAKEWOOD TWP on May 4, 2022.

Injury Federal Recordable Bus

What happened

On May 4, 2022, FMCSA recorded an injury crash with one person hurt in LAKEWOOD TWP, New Jersey. The vehicle was operated by SEMAN TOV INC (USDOT 1149194). Recorded conditions: 1 / 1 / 1 pavement. Reported by SEMAN-TOV INC, FMCSA reference NJ0022109543.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
SEMAN TOV INC
USDOT 1149194
Vehicle Type
Bus
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
10
3 injury · 7 tow-away
Crashes per 100 power units (24 mo)
5.9
7 crashes · 119 units
Days since prior carrier crash
27
Last on Apr 7, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,053 carriers

Geographic context

How this crash sits in its setting.

Within LAKEWOOD TWP, New Jersey, 62 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
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 #:
NJ0022109543
Date:
May 4, 2022
Time:
1603
State:
New Jersey
City:
LAKEWOOD TWP
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
SEMAN TOV INC (1149194)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 4 2 4UZABRDU4JCJG1832 S153S1 (NJ) SEMAN-TOV 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_5069772 Sep 15, 2025 NJ Tow-Away 0 0
cr_4940744 May 12, 2025 NJ Injury 0 1
cr_4936335 May 1, 2025 NJ Injury 0 1
cr_4928148 Mar 27, 2025 NJ Injury 0 6
cr_4920833 Feb 26, 2025 NJ Injury 0 1
cr_4857663 Dec 2, 2024 NJ Injury 0 1
cr_4836777 Oct 28, 2024 NJ Injury 0 1
cr_4790721 Jun 20, 2024 NJ Tow-Away 0 0
cr_4788104 Jun 4, 2024 NJ Injury 0 1
cr_4730772 Feb 22, 2024 NJ Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
SEMAN TOV INC
USDOT 1149194 · 106 crashes · 206 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Insurance
Insurance-lapse watch · HIGH
BMC-91 filing instability signal for this carrier.
HIGH
Vehicle
VIN: 4UZABRDU4JCJG1832
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
SEMAN-TOV INC
Crashes reported by this law-enforcement agency.
City
Crashes in LAKEWOOD TWP, 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.