FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC96LA062 · Piper PA-46-350P

12 Feb 1996 · Butler, PA, United States

Piper PA-46-350P · Accident: loss of control in flight on approach

From Erie International Tom Ridge Field (ERI) to Pittsburgh/Butler Regional Airport (BTP)

Report a problem

Event

NTSB case
NYC96LA062
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-46-350P

Aircraft type
Piper PA-46
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
N89HS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Erie International Tom Ridge Field (ERI), Erie, PATo Pittsburgh/Butler Regional Airport (BTP)
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
Approach · VFR pattern final
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Compensation for wind conditions, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was conducting an approach to runway 8, during which the left wing contacted the ground approximately 75 feet from the approach end of the runway. The airplane came to rest about 160 feet down the runway, and off the right side. A pilot who landed on runway 26, about 30 minutes prior to the accident flight, stated that the winds were out of the northwest at 15 knots with gusts, and he experienced plus and minus 10 knots on the airspeed while on final approach. The winds 19 miles to the east, at 1045 eastern standard time, were reported from 310 degrees at 15 knots with gusts up to 20 knots. An AIRMET was issued at 0345, with an advisory for occasional moderate turbulence below 8,000 feet. The AIRMET was reissued at 0945, with the added advisory of, 'Low level wind shear potential over the Boston Area Forecast area east of an Erie-Bristol line due to gusty northwesterly surface winds. Conditions ending by 1600.' An FAA Inspector examined the wreckage and found no preimpact anomalies with the airplane.

Probable cause

the pilot's inadequate compensation for wind conditions during the final approach, which resulted in the uncontrolled descent and subsequent collision with the ground. A contributing factor is windshear conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC96LA062
Event ID
20001208X05311
Case number
NYC96LA062
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: da74323ff4dbab22b526cdd8e0acc43803daf63e4cc3e891c637729bf4c5e613; retrieved 2026-09-21T12:54:10.064Z.