Skip to main content
TruckCodex
Hubs

Crash Record MEC00-060115

FMCSA crash record in Maine on Aug 14, 2007.

Injury

What happened

On August 14, 2007, FMCSA recorded an injury crash with one person hurt in Maine. The vehicle was operated by GAGNE & SON LLC (USDOT 6232). FMCSA reference MEC00-060115.

Fatalities
0
Injuries
1
Vehicles
—
Carrier
USDOT 6232
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
1 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 12 units
Days since prior carrier crash
215
Last on Jan 11, 2007
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,833 carriers

Geographic context

How this crash sits in its setting.

Within Maine, 1,472 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
MEC00-060115
Date:
Aug 14, 2007
Time:
1436
State:
Maine
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
GAGNE & SON LLC (6232)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4208344 Aug 25, 2021 ME Tow-Away 0 0
cr_2015196 Aug 27, 2008 ME Fatal 1 0
cr_1735895 Jan 11, 2007 ME Tow-Away 0 0
cr_1483797 May 11, 2005 ME Injury 0 1
cr_1281396 May 11, 2004 ME Tow-Away 0 0
cr_1265380 Apr 19, 2004 ME Tow-Away 0 0
cr_1118975 Jun 3, 2003 ME Tow-Away 0 0
cr_342245 Oct 9, 2001 ME Fatal 1 0
cr_699837 May 3, 2000 ME Injury 0 2
cr_698926 Aug 26, 1998 ME Injury 0 2

Carrier booking & risk tools

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

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.