NYC85LA108 · Piper PA-23-250
Piper PA-23-250 · Accident: overrun during landing
From Buffalo Niagara International Airport (BUF) to Allegheny County Airport (AGC)
Event
- NTSB case
- NYC85LA108
- 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
Piper PA-23-250
- Aircraft type
- Piper PA-23
- 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
- N506AC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Buffalo Niagara International Airport (BUF), Buffalo, NYTo Allegheny County Airport (AGC), PITTBURGH, 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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 › Distance, misjudged
- Pilot in command › Lack of recent experience in type operation
- Pilot in command › Planned approach, misjudged
- Pilot in command › Proper touchdown point, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PURPOSE OF THE FLIGHT WAS TO POSITION THE AIRCRAFT AT PITTSBURGH, PA. DURING THE TAKEOFF ROLL AT BUFFALO, TWO TO THREE SHORT POWER SURGES IN THE NO. 1 ENGINE WERE EXPERIENCED BUT THE PILOT DECIDED NOT TO ABORT AND CONTINUED TO DESTINATION. THE AIRCRAFT RAN SMOOTHLY WITH THE MIXTURE LEANED AND THE RPM AT 2400. HOWEVER WHEN THE PILOT FURTHER LEAN THE LEFT MIXTURE, THE NO. 1 ENGINE BEGAN TO SURGE AS THOUGH IT WAS FUEL STARVED. A PRECAUTIONARY LANDING WAS MADE AT CLARION AIRPORT, WHILE LANDING, AT 60 KNOTS. THE AIRCRAFT CONTINUED ROLLING OFF THE RUNWAY THROUGH THE GRASS AND OVER A 10' CLIFF.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC85LA108
- Event ID
- 20001214X36309
- Case number
- NYC85LA108
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 4978ef68bfbb426aae06e3f6851c5238c2455e010c973898283a9900d01a3e71; retrieved 2026-09-23T18:01:12.887Z.