Crash Record NJ1998000937

FMCSA crash record in New Jersey on Jul 8, 1998.

Injury

What happened

On July 8, 1998, FMCSA recorded an injury crash with one person hurt in New Jersey. The vehicle was operated by ACCELA WORLDWIDE SOLUTIONS INC (USDOT 281858). FMCSA reference NJ1998000937.

Carrier pattern note

This is the carrier's 4 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 6–50 power units.

Fatalities
0
Injuries
1
Vehicles
Carrier
ACCELA WORLDWIDE SOLUTIONS INC
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
3 injury · 3 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 7 units
Days since prior carrier crash
90
Last on Apr 9, 1998
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,651 carriers

Geographic context

How this crash sits in its setting.

Within New Jersey, 8,191 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
NJ1998000937
Date:
Jul 8, 1998
Time:
0635
State:
New Jersey
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4340724 Apr 17, 2022 VA Tow-Away 0 0
cr_3426486 Jul 7, 2017 WV Tow-Away 0 0
cr_3379522 Mar 22, 2017 PA Tow-Away 0 0
cr_1844698 Jul 3, 2007 NJ Tow-Away 0 0
cr_1776584 Feb 16, 2007 NJ Injury 0 1
cr_1699045 Aug 20, 2006 VA Injury 0 1
cr_1691806 Aug 16, 2006 VA Tow-Away 0 0
cr_1607852 Dec 8, 2005 PA Injury 0 2
cr_1549603 Nov 8, 2005 VA Injury 0 3
cr_1448558 Jan 26, 2005 PA Injury 0 1

Related records

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.