TruckCodex
Hubs

Crash Record FL2501488002

FMCSA crash record in UNINCORPORATED on Oct 18, 2022.

Tow-Away Federal Recordable

What happened

On October 18, 2022, FMCSA recorded a tow-away crash with no reported injuries in UNINCORPORATED, Florida. The vehicle was operated by OLDCASTLE APG SOUTH INC (USDOT 907316). Recorded conditions: 1 / 1 / 1 pavement. Reported by OLDCASTLE APG SOUTH INC, FMCSA reference FL2501488002.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
OLDCASTLE APG SOUTH INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
24
11 injury · 21 tow-away
Crashes per 100 power units (24 mo)
6.4
17 crashes · 267 units
Days since prior carrier crash
102
Last on Jul 8, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,773 carriers

Geographic context

How this crash sits in its setting.

Within UNINCORPORATED, Florida, 4,876 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 #:
FL2501488002
Date:
Oct 18, 2022
Time:
1446
State:
Florida
City:
UNINCORPORATED
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
OLDCASTLE APG SOUTH INC (907316)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 5 1XPCDP9X7HD442092 GVUN88 (FL) OLDCASTLE APG SOUTH INC 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
cmt1jo104002tpevkkh6qtbhf Aug 13, 2026 NC Injury 0 1
cr_5101441 Dec 8, 2025 FL Injury 0 1
cr_5097055 Dec 4, 2025 IL Tow-Away 0 0
cr_5060196 Oct 27, 2025 GA Injury 0 1
cr_5057330 Oct 17, 2025 NC Injury 0 1
cr_5038872 Sep 24, 2025 SC Tow-Away 0 0
cr_5002862 Aug 5, 2025 NC Injury 0 1
cr_4993855 Jun 23, 2025 GA Tow-Away 0 0
cr_5008818 Jun 6, 2025 SC Injury 0 1
cr_4922952 Mar 20, 2025 FL Tow-Away 0 0

Related records

Vehicle
2017 PETERBILT 567
NHTSA recalls and complaints for this make/model/year.
Recall
21V00N000
ELECTRICAL SYSTEM:WIRING
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
20V130000
ELECTRICAL SYSTEM:12V/24V/48V BATTERY:CABLES
Carrier
OLDCASTLE APG SOUTH INC
USDOT 907316 · 147 crashes · 572 inspections
Vehicle
VIN: 1XPCDP9X7HD442092
Decode this VIN for make, model, year, and recall data.
State
Crashes in Florida
Statewide crash records.
Agency
OLDCASTLE APG SOUTH INC
Crashes reported by this law-enforcement agency.
City
Crashes in UNINCORPORATED, FL
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.