TruckCodex
Hubs

Crash Record MATBC0031434

FMCSA crash record in OXFORD on Sep 21, 2023.

Tow-Away Federal Recordable

What happened

On September 21, 2023, FMCSA recorded a tow-away crash with no reported injuries in OXFORD, Massachusetts. The vehicle was operated by PHOENIX COMMUNICATIONS INC (USDOT 1290132). Recorded conditions: 1 / 1 pavement. Reported by PHOENIX COMMUNICATIONS INC, FMCSA reference MATBC0031434.

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.

Geographic note

This crash is part of an active corridor: 26 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
3
Carrier
PHOENIX COMMUNICATIONS 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
0 injury · 4 tow-away
Crashes per 100 power units (24 mo)
2.3
2 crashes · 87 units
Days since prior carrier crash
279
Last on Dec 16, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within OXFORD, Massachusetts, 26 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
1
Weather
—
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 #:
MATBC0031434
Date:
Sep 21, 2023
Time:
0822
State:
Massachusetts
City:
OXFORD
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
PHOENIX COMMUNICATIONS INC (1290132)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 1FVACWFCXLHKW6314 2958140 (IN) PHOENIX COMMUNICATIONS INC 2 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4830371 Oct 12, 2024 CT Tow-Away 0 0
cr_4820237 Sep 30, 2024 CT Tow-Away 0 0
cr_4493452 Dec 16, 2022 MA Tow-Away 0 0
cr_4491916 Dec 13, 2022 MA Tow-Away 0 0
cr_4384993 Jun 28, 2022 MA Tow-Away 0 0
cr_3757847 Jan 16, 2019 MA Tow-Away 0 0
cr_3157074 Dec 16, 2015 MA Injury 0 1
cr_3075631 Jun 4, 2015 MA Tow-Away 0 0
cr_3084110 Jun 4, 2015 MA Tow-Away 0 0
cr_2674623 Feb 8, 2013 MA Tow-Away 0 0

Related records

Carrier
PHOENIX COMMUNICATIONS INC
USDOT 1290132 · 11 crashes · 60 inspections
Vehicle
VIN: 1FVACWFCXLHKW6314
Decode this VIN for make, model, year, and recall data.
State
Crashes in Massachusetts
Statewide crash records.
Agency
PHOENIX COMMUNICATIONS INC
Crashes reported by this law-enforcement agency.
City
Crashes in OXFORD, MA
All crashes on file for this city.
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.