TruckCodex
Hubs

Crash Record PA403609600X

FMCSA crash record in READING CITY on Apr 24, 2024.

Injury Federal Recordable Bus

What happened

On April 24, 2024, FMCSA recorded an injury crash with one person hurt in READING CITY, Pennsylvania. The vehicle was operated by BERKS COUNTY INTERMEDIATE UNIT (USDOT 1748002). Recorded conditions: 1 / 1 / 1 pavement. Reported by BERKS COUNTY INTERMEDIATE UNIT, FMCSA reference PA403609600X.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
BERKS COUNTY INTERMEDIATE UNIT
Vehicle Type
Bus
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
4 injury · 4 tow-away
Crashes per 100 power units (24 mo)
0.9
2 crashes · 224 units
Days since prior carrier crash
133
Last on Dec 13, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within READING CITY, Pennsylvania, 37 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 #:
PA403609600X
Date:
Apr 24, 2024
Time:
1424
State:
Pennsylvania
City:
READING CITY
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
BERKS COUNTY INTERMEDIATE UNIT (1748002)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 4 2 4DRBUPWN1LB340058 SC-81232 (PA) BERKS COUNTY INTERMEDIATE UNIT 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
cmrk8iqyk002bpelcgi0invze Jul 7, 2026 PA Tow-Away 0 0
cr_5025745 Aug 26, 2025 PA Injury 0 1
cr_4766557 Jun 4, 2024 PA Injury 0 1
cr_4670282 Dec 13, 2023 PA Tow-Away 0 0
cr_4597777 Jul 11, 2023 PA Injury 0 1
cr_4537095 Mar 17, 2023 PA Injury 0 1
cr_4697816 Aug 19, 2022 PA Injury 0 4
cr_4330599 Mar 8, 2022 PA Tow-Away 0 0
cr_4346528 Mar 7, 2022 PA Tow-Away 0 0
cr_4247142 Oct 27, 2021 PA Injury 0 2

Related records

Vehicle
2020 IC BUS PB105
NHTSA recalls and complaints for this make/model/year.
Carrier
BERKS COUNTY INTERMEDIATE UNIT
USDOT 1748002 · 31 crashes · 86 inspections
Vehicle
VIN: 4DRBUPWN1LB340058
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
BERKS COUNTY INTERMEDIATE UNIT
Crashes reported by this law-enforcement agency.
City
Crashes in READING CITY, 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.