Crash Record ME000SO03712

FMCSA crash record in MONTICELLO on May 29, 2023.

Injury Federal Recordable

What happened

On May 29, 2023, FMCSA recorded an injury crash with one person hurt in MONTICELLO, Maine. The vehicle was operated by RIVER VIEW TRANSPORT LLC (USDOT 2575747). Recorded conditions: 1 / 1 / 1 pavement. Reported by RIVER VIEW TRANSPORT LLC, FMCSA reference ME000SO03712.

Fatalities
0
Injuries
1
Vehicles
1
Carrier
RIVER VIEW TRANSPORT LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
2 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 3 units
Days since prior carrier crash
131
Last on Jan 18, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,554,606 carriers

Contributing factors

What the responding officer recorded.

Light
1
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 #:
ME000SO03712
Date:
May 29, 2023
Time:
0631
State:
Maine
City:
MONTICELLO
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 10 2HSFMAMR2XC087021 8C6019 (ME) RIVER VIEW TRANSPORT LLC 3 No

Crash event

Event sequence description.

3:18:COLLISION INVOLVING FIXED OBJECT;1:6:NONCOLLISION:EXPLOSION OR FIRE;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

2 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4691298 Jan 25, 2024 ME Tow-Away 0 0
cr_4496357 Jan 18, 2023 ME 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.