Skip to main content
TruckCodex
Hubs

Crash Record MD24S0000923

FMCSA crash record in Maryland on Mar 4, 2024.

Tow-Away Federal Recordable

What happened

On March 4, 2024, FMCSA recorded a tow-away crash with no reported injuries in Maryland. The vehicle was operated by LIGHTNING TRANSPORTATION INC (USDOT 326966). Recorded conditions: 3 / 5 / 1 pavement. Reported by LIGHTNING TRANSPORTATION INC, FMCSA reference MD24S0000923.

Carrier pattern note

This is the carrier's 18 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
LIGHTNING TRANSPORTATION INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
18
1 fatal · 6 injury
Crashes per 100 power units (24 mo)
7.0
18 crashes · 256 units
Days since prior carrier crash
84
Last on Dec 11, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,985 carriers

Geographic context

How this crash sits in its setting.

Within Maryland, 4,095 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
3
Weather
5
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 #:
MD24S0000923
Date:
Mar 4, 2024
Time:
0507
State:
Maryland
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
LIGHTNING TRANSPORTATION INC (326966)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUJCRCK77PW86254 908F39 (MD) LIGHTNING TRANSPORTATION INC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;3:18:COLLISION INVOLVING FIXED OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5117783 Mar 6, 2026 NC Injury 0 1
cr_5121158 Mar 5, 2026 NC Injury 0 2
cr_5074571 Dec 11, 2025 GA Injury 0 2
cr_5071303 Nov 21, 2025 SC Tow-Away 0 0
cr_5056373 Oct 29, 2025 VA Tow-Away 0 0
cr_5047691 Oct 9, 2025 GA Tow-Away 0 0
cr_5000348 Jul 9, 2025 MD Tow-Away 0 0
cr_4999673 Jun 16, 2025 MD Injury 0 1
cr_4993108 Jun 12, 2025 GA Tow-Away 0 0
cr_4946544 May 21, 2025 SC Injury 0 1

Related records

Vehicle
2007 FREIGHTLINER Coronado
NHTSA recalls and complaints for this make/model/year.
Recall
20V214000
EXTERIOR LIGHTING
Recall
17V810000
EQUIPMENT
Recall
12V074000
ENGINE AND ENGINE COOLING:ENGINE:DIESEL
Carrier
LIGHTNING TRANSPORTATION INC
USDOT 326966 · 233 crashes · 592 inspections
Vehicle
VIN: 1FUJCRCK77PW86254
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
LIGHTNING TRANSPORTATION INC
Crashes reported by this law-enforcement agency.
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.