NYC91FA112 · Piper PA-30
Piper PA-30 · Accident: loss of control in flight en route
From Altoona Blair County Airport (AOO) to N97 · Clearfield, PA
Event
- NTSB case
- NYC91FA112
- 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
- 1 · 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
- Instrument Meteorological Cond
Piper PA-30
- Aircraft type
- Piper PA-30
- 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
- N8073Y
- Operator
- Frances Mccully
- Onboard fatalities
- Unknown
- Route
- From Altoona Blair County Airport (AOO), Altoona, PATo N97 · Clearfield, 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 · climb to 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
- Loss of control in flight
- 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
- Tree(s)
- 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 › Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING AN INSTRUMENT CLIMB THE PILOT LOST CONTROL OF THE AIRPLANE. THE PILOT HAD DEPARTED THE AIRPORT DURING LOW CEILINGS WITH LIGHT RAIN AND FOG. SEVERAL LAYERS OF CLOUDS EXISTED DURING THE CLIMB. RAIN, THUNDERSTORMS, AND TURBULENCE WITHIN THE THUNDERSTORMS HAD BEEN FORECAST. PILOT REPORTS EAST OF THE FLIGHT PATH HAD INCLUDED LIGHT ICING FROM THE SURFACE TO FIVE THOUSAND. THE AIRPLANE HAD BEEN CLEARED TO SIX THOUSAND. THE PILOT WAS INSTRUCTED TO CONTACT NEW YORK CENTER WITH AN ALTITUDE READOUT OF 4500 FT . THE PILOT NEVER ESTABLISHED CONTACT. CLEVELAND CENTER LOST RDAR CONTACT AT 5300 FT AT APPROXIMATELY NINE MILES FROM THE AIRPORT. THE AIRPLANE HAD BEEN AIRBORNE FOR APPROXIMATELY TEN MINUTES. THE AIRPLANE IMPACTED TREES, CABLES, AND TERRAIN. BASED ON THE PHYSICAL EVIDENCE THE AIRPLANE MAINTAINED STRUCTURAL INTEGRITY UNTIL IMPACT. POST ACCIDENT INVESTIGATION OF THE ENGINES REVEALED NO ANOMALIES THAT WOULD HAVE CONTRIBUTED TO THE ACCIDENT. THE WRECKAGE PATH WAS 1,176 FEET LONG.
Probable cause
THE PILOT'S LOSS OF CONTROL FOR UNDETERMINED REASONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC91FA112
- Event ID
- 20001212X16852
- Case number
- NYC91FA112
- 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: 04eeedc08a267a69ac8b9f79344e36de00041ba74bb6a9bed01611caf10a21b4; retrieved 2026-09-21T01:51:26.480Z.