Skip to main content
TruckCodex
Hubs

Crash Record MD0007687416

FMCSA crash record in Maryland on Nov 20, 1997.

Tow-Away

What happened

On November 20, 1997, FMCSA recorded a tow-away crash with no reported injuries in Maryland. The vehicle was operated by COMMUNICATIONS CONSTRUCTION GROUP LLC (USDOT 546919). FMCSA reference MD0007687416.

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.

Fatalities
0
Injuries
0
Vehicles
—
Carrier
COMMUNICATIONS CONSTRUCTION GROUP LLC
Vehicle Type
—
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
2 injury · 3 tow-away
Crashes per 100 power units (24 mo)
1.0
2 crashes · 204 units
Days since prior carrier crash
2
Last on Nov 18, 1997
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,885 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 4,114 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 #:
MD0007687416
Date:
Nov 20, 1997
Time:
1345
State:
Maryland
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5084216 Feb 20, 2025 NH Fatal 1 2
cr_4895099 Feb 20, 2025 NH Fatal 1 0
cr_4620099 Sep 2, 2023 NH Tow-Away 0 0
cr_4541786 Mar 14, 2023 MD Injury 0 1
cr_4515096 Feb 14, 2023 ME Tow-Away 0 0
cr_4394964 May 12, 2022 NJ Injury 0 1
cr_4147954 Apr 5, 2021 DE Tow-Away 0 0
cr_3782181 Mar 6, 2019 NJ Tow-Away 0 0
cr_3750648 Feb 1, 2019 NH Injury 0 1
cr_3525542 Jan 2, 2018 GA 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.