NYC89FA167 · Piper PA-24-250
Piper PA-24-250 · Accident: in flight encounter with weather en route
From Bradford Regional Airport (BFD) to Pottstown Municipal Airport (N47)
Event
- NTSB case
- NYC89FA167
- 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
- 2 · 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-24-250
- Aircraft type
- Piper PA-24
- 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
- N6206P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bradford Regional Airport (BFD), Bradford, PATo Pottstown Municipal Airport (N47), Pottstown, 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
- En route · cruise
- 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
- In flight encounter with weather
- 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 › Design stress limits of aircraft, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS ON AN IFR FLT AT 7000 FT. AT 1158:29, THE PLT RPRTD, 'SIX TWO ZERO SIX PAPA SPINNING.' SUBSEQUENTLY, THE ACFT CRASHED ON WOODED TERRAIN NEAR THE TOP OF A MTN RIDGE. ACCORDING TO A WITNESS, WHO SAW THE ACFT BEFORE IT CRASHED, THERE WAS AN UNUSUAL CLOUD FORMATION IN THE AREA, AS WELL AS STRONG/GUSTY WINDS. HE SAID HE SAW THE ACFT DISAPPEAR BEHIND A WALL OF CLOUDS & REAPPEAR. HE INDICATED THE ACFT ENTERED A SPIN, THEN FLEW BACK UP ALMOST AS FAST AS IT CAME DOWN, BEFORE CRASHING. AN EXAM OF THE WRECKAGE REVEALED EVIDENCE THAT THE HORIZONTAL STABILIZERS SEPARATED IN FLT. THEY WERE FOUND AWAY FROM THE MAIN WRECKAGE & HAD FAILED IN A DOWNWARD DIRECTION FROM OVERLOAD. NO OTHER PREIMPACT PART FAILURE WAS EVIDENT. WEATHER RADAR DATA SHOWED THAT THE ACFT HAD CRASHED IN THE AREA OF A LEVEL 2 ECHO.
Probable cause
THE PILOT ALLOWED THE DESIGN STRESS LIMITS OF THE AIRCRAFT TO BE EXCEEDED AFTER ENCOUNTERING ADVERSE WEATHER CONDITIONS. WEATHER WAS A RELATED FACTOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC89FA167
- Event ID
- 20001213X28947
- Case number
- NYC89FA167
- 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: 4d11a6d8d3f18689279c557f03b54cf97b3779930c295e05dc414cebbd371fee; retrieved 2026-09-21T03:14:09.905Z.