Skip to main content
TruckCodex
Hubs

Crash Record MD26A1334490

FMCSA crash record in CROFTON on Feb 6, 2026.

Injury Federal Recordable

What happened

On February 6, 2026, FMCSA recorded an injury crash with 2 people hurt in CROFTON, Maryland. The vehicle was operated by WILTSHIRE TRUCKING CORPORATION (USDOT 2339865). Recorded conditions: 1 / 1 / 1 pavement. Reported by WILTSHIRE TRUCKING CORPORATION, FMCSA reference MD26A1334490.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
3
Carrier
WILTSHIRE TRUCKING CORPORATION
USDOT 2339865
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
2 injury · 4 tow-away
Crashes per 100 power units (24 mo)
11.1
2 crashes · 18 units
Days since prior carrier crash
530
Last on Aug 25, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,733 carriers

Geographic context

How this crash sits in its setting.

Within CROFTON, Maryland, 6 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
1
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 #:
MD26A1334490
Date:
Feb 6, 2026
Time:
1332
State:
Maryland
City:
CROFTON
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
WILTSHIRE TRUCKING CORPORATION (2339865)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 6 3BKDX4EX0LF380043 E72609D (MD) WILTSHIRE TRUCKING CORPORATION 3 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_5122693 Feb 6, 2026 MD Injury 0 1
cr_4884052 Aug 25, 2024 MD Tow-Away 0 0
cr_4912757 Jul 20, 2024 MD Tow-Away 0 0
cr_4911126 Jan 5, 2024 MD Tow-Away 0 0
cr_4297833 Jan 3, 2022 MD Tow-Away 0 0
cr_4167114 Jun 4, 2021 DC Injury 0 2
cr_3870916 Aug 6, 2019 MD Injury 0 1
cr_3673167 Aug 8, 2018 MD Injury 0 1
cr_3494464 Oct 2, 2017 MD Tow-Away 0 0
cr_3462590 Aug 11, 2017 MD Injury 0 1

Carrier booking & risk tools

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

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
WILTSHIRE TRUCKING CORPORATION
USDOT 2339865 · 13 crashes · 110 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3BKDX4EX0LF380043
Decode this VIN for make, model, year, and recall data.
State
Crashes in Maryland
Statewide crash records.
Agency
WILTSHIRE TRUCKING CORPORATION
Crashes reported by this law-enforcement agency.
City
Crashes in CROFTON, MD
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.