Skip to main content
TruckCodex
Hubs

Crash Record DC0026025242

FMCSA crash record in WASHINGTON on Feb 25, 2026.

Tow-Away Federal Recordable Bus

What happened

On February 25, 2026, FMCSA recorded a tow-away crash with no reported injuries in WASHINGTON, District of Columbia. The vehicle was operated by WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY (USDOT 36845). Recorded conditions: 1 / 1. Reported by WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY, FMCSA reference DC0026025242.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY
USDOT 36845
Vehicle Type
Bus
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
142
1 fatal · 78 injury
Crashes per 100 power units (24 mo)
5.1
95 crashes · 1,864 units
Days since prior carrier crash
6
Last on Feb 19, 2026
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within WASHINGTON, District of Columbia, 293 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
—

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 #:
DC0026025242
Date:
Feb 25, 2026
Time:
1535
State:
District of Columbia
City:
WASHINGTON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY (36845)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 4 2 5FYC8FB10GC048217 B53052 (DC) WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY 3 No

Crash event

Event sequence description.

1:19:COLLISION WITH WORK ZONE MAINTENANCE EQUIPMENT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmsw88sf000g3pev3xfnfus0s Aug 7, 2026 DC Injury 0 1
cmrfwlwj1001zmlhrhorrkdl7 Jul 5, 2026 DC Injury 0 1
cmodru191008hnvfdkybr4drk Apr 17, 2026 DC Tow-Away 0 0
cmny3yg2x00f7k38v4l4pw6ld Apr 4, 2026 DC Injury 0 5
cmny3yg2s00f3k38vvdo9eu9w Apr 3, 2026 DC Tow-Away 0 0
cr_5122540 Mar 23, 2026 DC Injury 0 1
cr_5122539 Mar 22, 2026 DC Injury 0 1
cr_5115476 Feb 25, 2026 DC Tow-Away 0 0
cr_5115475 Feb 19, 2026 DC Injury 0 1
cr_5115474 Feb 16, 2026 DC Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2016 NEW FLYER Xcelsior
NHTSA recalls and complaints for this make/model/year.
Recall
25V542000
STRUCTURE
Carrier
WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY
USDOT 36845 · 1,889 crashes · 2 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 5FYC8FB10GC048217
Decode this VIN for make, model, year, and recall data.
State
Crashes in District of Columbia
Statewide crash records.
Agency
WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY
Crashes reported by this law-enforcement agency.
City
Crashes in WASHINGTON, DC
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.