Crash Record PA2057856001

FMCSA crash record in Pennsylvania on Jun 26, 1992.

Property Damage

What happened

On June 26, 1992, FMCSA recorded a property-damage crash with no reported injuries in Pennsylvania. The vehicle was operated by GIANT EAGLE INC (USDOT 267104). FMCSA reference PA2057856001.

Fatalities
0
Injuries
0
Vehicles
Carrier
GIANT EAGLE INC
Vehicle Type
Severity
Property Damage

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
0 injury · 0 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 88 units
Prior carrier crash
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,833 carriers

Geographic context

How this crash sits in its setting.

Within Pennsylvania, 12,696 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
PA2057856001
Date:
Jun 26, 1992
Time:
0455
State:
Pennsylvania
Fatalities:
0
Injuries:
0
Tow-Away:
No
HazMat:
No
Carrier (USDOT):
GIANT EAGLE INC (267104)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_3660082 Jun 22, 2018 PA Tow-Away 0 0
cr_378903 Apr 4, 2002 OH Fatal 1 0
cr_945840 Sep 11, 2000 PA Injury 0 4
cr_944104 Jun 9, 2000 PA Injury 0 1
cr_943994 May 31, 2000 PA Injury 0 1
cr_1003922 Dec 20, 1999 PA Tow-Away 0 0
cr_1004205 Sep 4, 1999 PA Fatal 1 2
cr_1001541 Aug 28, 1999 PA Injury 0 1
cr_1000861 Jun 8, 1999 PA Injury 0 1
cr_1000384 Jun 4, 1999 PA Tow-Away 0 0

Related records

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.