Crash Record MA1002362594

FMCSA crash record in Massachusetts on Jun 7, 2013.

Tow-Away

What happened

On June 7, 2013, FMCSA recorded a tow-away crash with no reported injuries in Massachusetts. The vehicle was operated by B L T TRANS INC (USDOT 2800512). FMCSA reference MA1002362594.

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
0
Vehicles
Carrier
B L T TRANS INC
Vehicle Type
Severity
Tow-Away

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 · 1 units
Days since prior carrier crash
129
Last on Jan 29, 2013
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,564,214 carriers

Geographic context

How this crash sits in its setting.

Within Massachusetts, 3,007 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 #:
MA1002362594
Date:
Jun 7, 2013
Time:
0830
State:
Massachusetts
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
B L T TRANS INC (2800512)

Other crashes by this carrier

9 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4374950 May 26, 2022 PA Injury 0 1
cr_3010610 Mar 15, 2015 ME Injury 0 1
cr_2682254 Jan 29, 2013 NJ Tow-Away 0 0
cr_2488610 Nov 1, 2011 FL Injury 0 2
cr_2461790 Sep 24, 2011 ME Tow-Away 0 0
cr_2421494 Jun 15, 2011 NY Tow-Away 0 0
cr_2384136 Mar 13, 2011 NY Tow-Away 0 0
cr_1589839 Nov 19, 2005 PA Tow-Away 0 0
cr_1451045 Mar 31, 2003 PA Tow-Away 0 0

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.