Crash Record DC0023010476
FMCSA crash record in WASHINGTON on Jan 20, 2023.
Injury
Federal Recordable
What happened
On January 20, 2023, FMCSA recorded an injury crash with one person hurt in WASHINGTON, District of Columbia. The vehicle was operated by 4P FOODS INC PBC (USDOT 3243721). Recorded conditions: 1. Reported by 4P FOODS, FMCSA reference DC0023010476.
Geographic note
This crash is part of an active corridor: 340 crashes occurred in the same city in the past 24 months.
Fatalities
0
Injuries
1
Vehicles
2
Carrier
4P FOODS INC PBC
Vehicle Type
Truck
Severity
Injury
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
1
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 6 units
Prior carrier crash
—
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,567 carriers
Geographic context
How this crash sits in its setting.
Within WASHINGTON, District of Columbia, 340 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY · 98 reports
- OFFICE OF THE STATE SUPERINTENDENT · 11 reports
- D C FIRE AND EMS DEPARTMENT · 11 reports
Crash details
Key facts from the FMCSA crash record.
- Report #:
- DC0023010476
- Date:
- Jan 20, 2023
- Time:
- 1015
- State:
- District of Columbia
- City:
- WASHINGTON
- Fatalities:
- 0
- Injuries:
- 1
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- 4P FOODS INC PBC (3243721)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 5 | 98 | 3ALACWFC7MDMJ3129 | 23500UA (VA) | 4P FOODS | 2 | No |
Other crashes by this carrier
2 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_4696781 | Jan 26, 2024 | VA | Injury | 0 | 2 |
| cr_4645910 | Sep 25, 2023 | VA | Tow-Away | 0 | 0 |
Related records
Carrier
4P FOODS INC PBC
USDOT 3243721 · 3 crashes · 10 inspections
Vehicle
VIN: 3ALACWFC7MDMJ3129
Decode this VIN for make, model, year, and recall data.
State
Crashes in District of Columbia
Statewide crash records.
Agency
4P FOODS
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.