TruckCodex
Hubs

Crash Record NJ0007029062

FMCSA crash record in ROXBURY TWP on Sep 27, 2025.

Injury Federal Recordable

What happened

On September 27, 2025, FMCSA recorded an injury crash with one person hurt in ROXBURY TWP, New Jersey. The vehicle was operated by ALLEGIANCE TRUCKS LEASING LLC (USDOT 3508149). Recorded conditions: 3 / 1 / 1 pavement. Reported by ALLEGIANCE TRUCKS LEASING LLC, FMCSA reference NJ0007029062.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
5
Carrier
ALLEGIANCE TRUCKS LEASING LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
13
7 injury · 13 tow-away
Crashes per 100 power units (24 mo)
5.0
12 crashes · 242 units
Days since prior carrier crash
44
Last on Aug 14, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,773 carriers

Geographic context

How this crash sits in its setting.

Within ROXBURY TWP, New Jersey, 39 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 #:
NJ0007029062
Date:
Sep 27, 2025
Time:
0555
State:
New Jersey
City:
ROXBURY TWP
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
5
Carrier (USDOT):
ALLEGIANCE TRUCKS LEASING LLC (3508149)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 3HAEUMML7LL191232 14648NE (NJ) ALLEGIANCE TRUCKS LEASING LLC 2 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmp6e5pkd0033nuyqv9npfvon May 8, 2026 MA Tow-Away 0 0
cr_5082184 Dec 8, 2025 NJ Tow-Away 0 0
cr_5080281 Nov 13, 2025 MA Tow-Away 0 0
cr_5063243 Nov 6, 2025 NY Injury 0 1
cr_5025100 Aug 14, 2025 VT Injury 0 1
cr_4943838 May 11, 2025 OH Injury 0 3
cr_4935424 Apr 16, 2025 NY Injury 0 2
cr_4927294 Apr 2, 2025 NJ Tow-Away 0 0
cr_4923586 Mar 12, 2025 CT Injury 0 1
cr_4894111 Feb 4, 2025 MA Tow-Away 0 0

Related records

Vehicle
2020 INTERNATIONAL MV607
NHTSA recalls and complaints for this make/model/year.
Carrier
ALLEGIANCE TRUCKS LEASING LLC
USDOT 3508149 · 32 crashes · 54 inspections
Vehicle
VIN: 3HAEUMML7LL191232
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Jersey
Statewide crash records.
Agency
ALLEGIANCE TRUCKS LEASING LLC
Crashes reported by this law-enforcement agency.
City
Crashes in ROXBURY 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.