TruckCodex
Hubs

Crash Record TN0103483883

FMCSA crash record in Tennessee on Nov 17, 2022.

Injury Federal Recordable

What happened

On November 17, 2022, FMCSA recorded an injury crash with one person hurt in Tennessee. The vehicle was operated by MONTECORP LLC (USDOT 3491609). Recorded conditions: 2 / 1 / 1 pavement. Reported by MONTECORP LLC, FMCSA reference TN0103483883.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
MONTECORP LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
1 injury · 5 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 2 units
Days since prior carrier crash
124
Last on Jul 16, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,554,606 carriers

Geographic context

How this crash sits in its setting.

Within Tennessee, 7,415 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 #:
TN0103483883
Date:
Nov 17, 2022
Time:
0419
State:
Tennessee
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
MONTECORP LLC (3491609)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3HSDZAPR7JN417438 FT2836 (IA) MONTECORP LLC 3 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

7 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4658743 Nov 20, 2023 MO Tow-Away 0 0
cr_4660113 Nov 10, 2023 VA Tow-Away 0 0
cr_4653145 Oct 29, 2023 FL Tow-Away 0 0
cr_4393117 Jul 16, 2022 PA Tow-Away 0 0
cr_4360972 Apr 27, 2022 PA Tow-Away 0 0
cr_4241553 Oct 26, 2021 KY Tow-Away 0 0
cr_4217546 Jul 2, 2021 IL Tow-Away 0 0

Related records

Vehicle
2018 INTERNATIONAL LT625
NHTSA recalls and complaints for this make/model/year.
Carrier
MONTECORP LLC
USDOT 3491609 · 8 crashes · 0 inspections
Vehicle
VIN: 3HSDZAPR7JN417438
Decode this VIN for make, model, year, and recall data.
State
Crashes in Tennessee
Statewide crash records.
Agency
MONTECORP LLC
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.