Skip to main content
TruckCodex
Hubs

Crash Record NH0014154523

FMCSA crash record in NASHUA on Dec 13, 2023.

Tow-Away Federal Recordable

What happened

On December 13, 2023, FMCSA recorded a tow-away crash with no reported injuries in NASHUA, New Hampshire. The vehicle was operated by JKX LOGISTICS LLC (USDOT 3828932). Recorded conditions: 3 / 4 / 6 pavement. Reported by JKX LOGISTICS LLC, FMCSA reference NH0014154523.

Geographic note

This crash is part of an active corridor: 26 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
1
Carrier
JKX LOGISTICS LLC
USDOT 3828932
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
0 injury · 1 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 1 units
Prior carrier crash
—
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,569,614 carriers

Geographic context

How this crash sits in its setting.

Within NASHUA, New Hampshire, 26 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
4
Road surface
6

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 #:
NH0014154523
Date:
Dec 13, 2023
Time:
2133
State:
New Hampshire
City:
NASHUA
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
JKX LOGISTICS LLC (3828932)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 8 1FTFW1CF7CFB27747 ZTX7246 (PA) JKX LOGISTICS LLC 2 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

1 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4752408 Apr 30, 2024 VT Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2012 FORD F-150
NHTSA recalls and complaints for this make/model/year.
Recall
19V075000
POWER TRAIN:AUTOMATIC TRANSMISSION
Recall
16V248000
POWER TRAIN:AUTOMATIC TRANSMISSION
Recall
12V190000
EXTERIOR LIGHTING:BACK UP LIGHTS
Carrier
JKX LOGISTICS LLC
USDOT 3828932 · 2 crashes · 26 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: 1FTFW1CF7CFB27747
Decode this VIN for make, model, year, and recall data.
State
Crashes in New Hampshire
Statewide crash records.
Agency
JKX LOGISTICS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in NASHUA, NH
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.