TruckCodex
Hubs

Crash Record DC0025007388

FMCSA crash record in WASHINGTON on Jan 16, 2025.

Injury Federal Recordable

What happened

On January 16, 2025, FMCSA recorded an injury crash with 3 people hurt in WASHINGTON, District of Columbia. The vehicle was operated by BLUETRITON BRANDS INC (USDOT 297080). Recorded conditions: 1 / 1. Reported by READYREFRESH, FMCSA reference DC0025007388.

Carrier pattern note

This is the carrier's 64 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: 335 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
3
Vehicles
2
Carrier
BLUETRITON BRANDS INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
64
1 fatal · 30 injury
Crashes per 100 power units (24 mo)
1.6
38 crashes · 2,446 units
Days since prior carrier crash
55
Last on Nov 22, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within WASHINGTON, District of Columbia, 335 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 #:
DC0025007388
Date:
Jan 16, 2025
Time:
1255
State:
District of Columbia
City:
WASHINGTON
Fatalities:
0
Injuries:
3
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
BLUETRITON BRANDS INC (297080)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 12 1FDPF7ANXNDF11047 P1226473 (IL) READYREFRESH 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmsw88s5z004npev3pbr2oaiq Aug 10, 2026 NC Tow-Away 0 0
cr_5099651 Jan 29, 2026 GA Tow-Away 0 0
cr_5085591 Jan 12, 2026 ME Tow-Away 0 0
cr_5095879 Dec 20, 2025 FL Tow-Away 0 0
cr_5087291 Dec 12, 2025 TX Injury 0 5
cr_5084729 Dec 8, 2025 CA Tow-Away 0 0
cr_5070586 Nov 24, 2025 NY Tow-Away 0 0
cr_5064861 Nov 11, 2025 NC Tow-Away 0 0
cr_5062961 Oct 14, 2025 CA Tow-Away 0 0
cr_5052117 Sep 29, 2025 CA Injury 0 1

Related records

Carrier
BLUETRITON BRANDS INC
USDOT 297080 · 594 crashes · 1,170 inspections
Vehicle
VIN: 1FDPF7ANXNDF11047
Decode this VIN for make, model, year, and recall data.
State
Crashes in District of Columbia
Statewide crash records.
Agency
READYREFRESH
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.