Skip to main content
TruckCodex
Hubs

Crash Record CO2024001092

FMCSA crash record in Colorado on Jan 11, 2024.

Tow-Away Federal Recordable

What happened

On January 11, 2024, FMCSA recorded a tow-away crash with no reported injuries in Colorado. The vehicle was operated by NOOR EXPRESS LOGISTICS INC (USDOT 3863705). Recorded conditions: 2 / 1 / 1 pavement. Reported by NOOR EXPRESS LOGISTICS INC, FMCSA reference CO2024001092.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
NOOR EXPRESS LOGISTICS INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 fatal · 1 injury
Crashes per 100 power units (24 mo)
22.0
22 crashes · 100 units
Days since prior carrier crash
16
Last on Dec 26, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,020 carriers

Geographic context

How this crash sits in its setting.

Within Colorado, 2,997 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
2
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 #:
CO2024001092
Date:
Jan 11, 2024
Time:
0907
State:
Colorado
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
NOOR EXPRESS LOGISTICS INC (3863705)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDV1RSUR8204 PWY0811 (CO) NOOR EXPRESS LOGISTICS INC 3 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;3:1:NONCOLLISION:RAN OFF ROAD;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5105937 Feb 15, 2026 NC Tow-Away 0 0
cr_5083492 Dec 19, 2025 OH Tow-Away 0 0
cr_5087163 Dec 18, 2025 KS Tow-Away 0 0
cr_5076621 Dec 5, 2025 PA Tow-Away 0 0
cr_5035995 Sep 17, 2025 SC Injury 0 1
cr_5049202 Aug 1, 2025 VA Tow-Away 0 0
cr_5019477 Jul 29, 2025 IA Injury 0 1
cr_5020218 Jul 25, 2025 CA Tow-Away 0 0
cr_5012479 Jul 17, 2025 TX Tow-Away 0 0
cr_4955942 Jun 11, 2025 KY Tow-Away 0 0

Related records

Carrier
NOOR EXPRESS LOGISTICS INC
USDOT 3863705 · 29 crashes · 431 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: 3AKJHHDV1RSUR8204
Decode this VIN for make, model, year, and recall data.
State
Crashes in Colorado
Statewide crash records.
Agency
NOOR EXPRESS LOGISTICS INC
Crashes reported by this law-enforcement agency.
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.