NYC00FA079 · Beech 58
Beech 58 · Accident: loss of control in flight en route
From Tri-Cities Regional TN/VA Airport (TRI) to Eagle Creek Airpark (EYE)
Event
- NTSB case
- NYC00FA079
- 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
- 4 · 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
Beech 58
- Aircraft type
- Beechcraft 58
- 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
- N875JC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tri-Cities Regional TN/VA Airport (TRI), Kingsport, TNTo Eagle Creek Airpark (EYE), Indianapolis, IN
- 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
- 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 › Airspeed, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot filed an IFR flight plan, and received a standard weather briefing. The pilot was advised of occasional moderate rime or mixed icing below 10,000 feet for his route of flight. During the briefing the pilot stated, 'we got boots, and will be all right....' Approximately 5 minutes before the accident, the pilot reported the airplane was 'picking up' rime ice at 10,000 feet, and he requested 12,000 feet. He also reported that the windshield and wings were covered with ice, and that ice accumulation at 10,000 feet was moderate and steady. When the airplane started to climb to 12,000 feet, calibrated airspeed (CAS) began to decay. When the airplane reached 11,200 feet, and prior to the airplane starting a rapid descent, CAS had dropped to 85 knots. Minimum airspeed for icing conditions was published as 130 knots. In addition, the stall speed for the airplane was approximately 82 knots. The airplane was approved for flight into known icing conditions. Examination of the airframe, engines and propellers revealed no preimpact failures or malfunctions.
Probable cause
The pilot's failure to maintain airspeed during a climb, which resulted in a loss of aircraft control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00FA079
- Event ID
- 20001212X20551
- Case number
- NYC00FA079
- 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: d5b193be1e0e2587514d2ebf378773c06eb8b46f0eca18110c57023f48e06c2c; retrieved 2026-09-20T21:27:10.570Z.