FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC95LA227 · Cessna 172RG

28 Sept 1995 · Pittsburgh, PA, United States

Cessna 172RG · Accident: overrun during landing

From Pocono Mountains Municipal Airport (MPO) to Allegheny County Airport (AGC)

Report a problem

Event

NTSB case
NYC95LA227
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172RG

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N9497B
Onboard fatalities
Unknown
Route
From Pocono Mountains Municipal Airport (MPO), Mount Pocono, PATo Allegheny County Airport (AGC), PA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Overrun
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Airspeed, excessive
  • Pilot in command › Proper touchdown point, not obtained

Approximate · Estimated position: the centre of Pittsburgh, PA, the place the record names. Not the accident site.

NTSB narrative

THE PILOT WAS LANDING ON RUNWAY 23, A 2534 FOOT LONG RUNWAY, WHICH WAS NOT EQUIPPED WITH A VISUAL APPROACH SLOPE INDICATOR. THE AIRPLANE TOUCHED DOWN APPROXIMATELY 800 FEET FROM THE DEPARTURE END OF THE RUNWAY THEN FLOATED AND TOUCHED DOWN APPROXIMATELY 400 FEET FROM THE DEPARTURE END OF THE RUNWAY. THE PILOT APPLIED HEAVY BRAKING; HOWEVER, THE AIRPLANE CONTINUED OFF THE DEPARTURE END OF THE RUNWAY DOWN AN EMBANKMENT IMPACTING A TRAILER AND BUILDING. ADDITIONALLY, THE PILOT STATED, '...I LANDED FAST...', AND THAT THERE WERE NO MECHANICAL MALFUNCTIONS OR FAILURES. THE WINDS WERE REPORTED AS CALM.

Probable cause

the pilot's failure to obtain the proper touchdown point and excessive airspeed which resulted in an overrun and a subsequent collision with a trailer off the departure end of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC95LA227
Event ID
20001207X04579
Case number
NYC95LA227
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1995-09-29.
  • API snapshot SHA-256: 7f0c899fac05c8860f348e45c5931183742c6aa0b6a85ff1fc880f15f847fb8d; retrieved 2026-09-22T23:12:38.926Z.