TruckCodex
Hubs

Crash Record PA401669500X

FMCSA crash record in PINE CREEK TOWNSHIP on Feb 14, 2024.

Tow-Away Federal Recordable

What happened

On February 14, 2024, FMCSA recorded a tow-away crash with no reported injuries in PINE CREEK TOWNSHIP, Pennsylvania. The vehicle was operated by GP BROTHERS INC (USDOT 3427747). Recorded conditions: 2 / 4 / 6 pavement. Reported by GP BROTHERS INC, FMCSA reference PA401669500X.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
GP BROTHERS INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
0 injury · 9 tow-away
Crashes per 100 power units (24 mo)
4.0
1 crashes · 25 units
Days since prior carrier crash
3
Last on Feb 11, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,567 carriers

Geographic context

How this crash sits in its setting.

Within PINE CREEK TOWNSHIP, Pennsylvania, 28 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
2
Weather
4
Road surface
6

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 #:
PA401669500X
Date:
Feb 14, 2024
Time:
0216
State:
Pennsylvania
City:
PINE CREEK TOWNSHIP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
GP BROTHERS INC (3427747)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 8 4V4NC9EJ4RN631339 ZP06614 (CA) GP BROTHERS INC 3 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT;2:15:COLLISION INVOLVING TRAIN

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4818700 Sep 19, 2024 CA Tow-Away 0 0
cr_4774808 Jun 18, 2024 NM Injury 0 1
cr_4747932 May 2, 2024 AL Tow-Away 0 0
cr_4729360 Mar 25, 2024 KS Tow-Away 0 0
cr_4705893 Feb 11, 2024 TX Tow-Away 0 0
cr_4705092 Feb 11, 2024 TX Tow-Away 0 0
cr_4697183 Jan 29, 2024 AZ Tow-Away 0 0
cr_4755345 Jan 22, 2024 MO Tow-Away 0 0
cr_4677449 Dec 8, 2023 CA Tow-Away 0 0
cr_4631429 Oct 8, 2023 AR Tow-Away 0 0

Related records

Vehicle
2024 VOLVO TRUCK VNL
NHTSA recalls and complaints for this make/model/year.
Carrier
GP BROTHERS INC
USDOT 3427747 · 13 crashes · 0 inspections
Vehicle
VIN: 4V4NC9EJ4RN631339
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
GP BROTHERS INC
Crashes reported by this law-enforcement agency.
City
Crashes in PINE CREEK TOWNSHIP, PA
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.