skyward aviation Beech 65-A90 accident
Beech 65-A90 · Accident: hard landing
From Tri-Cities Regional TN/VA Airport (TRI) to Washington County Airport (AFJ)
Event
- NTSB case
- NYC98LA028
- 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
- Charter & commuter
- 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
Beech 65-A90
- Aircraft type
- Beechcraft 65
- 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
- N80GP
- Operator
- Skyward Aviation
- Onboard fatalities
- Unknown
- Route
- From Tri-Cities Regional TN/VA Airport (TRI), Bristol, TNTo Washington County Airport (AFJ), Washington, 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 135: Air Taxi & Commuter
- 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 · flare/touchdown
- 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
- Hard landing
- 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
- Stall
- 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 › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilots reported they experienced an engine fire during a missed approach in night, IMC conditions, and feathered the propeller and shut down the engine. On an approach to another airport, the airplane touched down short of the runway, traveled onto the runway, and then departed the left side of the runway. The pilot reported he could not maintain altitude due to ice accumulations, and the lack of power with one engine shut down. Examination of the wreckage revealed rotational damage to both engines and propellers consistent with operating engines. Neither propeller was in the feathered position. The pilot had been briefed about known moderate icing conditions, and isolated severe icing. The AFM recommended a minimum speed in icing conditions of 140 knots, and at less than 140 knots, ice could accumulate on the wings in unprotected areas. The pilot reported he flew the approach at 114 knots.
Probable cause
the failure of the pilot to maintain the minimum required airspeed while operating in icing conditions which resulted in ice accumulations and an inadvertent stall while on approach. Factors were the icing conditions and the pilot's lack of experience in the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC98LA028
- Event ID
- 20001208X09235
- Case number
- NYC98LA028
- 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 1997-11-14.
- API snapshot SHA-256: 962ec3ee526a2f3a7eebc561524224192fa6fb0a797371560bd10bc2c57df37f; retrieved 2026-09-18T17:18:25.300Z.