FTW86FA127 · Beech 58
Enterprise Aviation Beech 58 · Accident: loss of control in flight while maneuvering
From William P. Hobby Airport (HOU) to an unrecorded destination
Event
- NTSB case
- FTW86FA127
- 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
- 3 · 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
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
- N61442
- Operator
- Enterprise Aviation
- Onboard fatalities
- Unknown
- Route
- From William P. Hobby Airport (HOU), Houston, TXTo not recorded
- 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
- Maneuvering
- 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
- Stall/spin
- 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
- Airspeed(vs) › Not maintained
- Dual student › Stall/spin, inadvertent
- Pilot in command(cfi) › Remedial action, not attained
- Pilot in command(cfi) › Supervision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A PVT PLT & INSTRUCTOR (CFI) WERE ON A LCL FLT WITH A 3RD OCCUPANT ABOARD. THE PURPOSE OF THE FLT WAS TO PROVIDE DUAL INSTRUCTION TO THE PVT PLT SO HE COULD OBTAIN A MULTI-ENG RATING. AT 1818, 1 OF THE PLTS CONTACTED HOUSTON TRACON & REQDRADAR ADZY & SAID THEY INTENDED TO DO SOME AIR WORK IN THE AREA. THE LAST TRANSMISSION WITH THE ACFT WAS AT 1847 WHEN THE CTLR ADZD THEY WERE CLR OF OTR TRAFFIC. APRX 4 MIN LATER, RADAR CONTACT WAS LOST. THE ACFT WAS FND WHERE IT HAD IMPACTED THE GND IN A RELATIVELY FLAT, WINGS LVL ATTITUDE. AN INV REVEALED EVIDENCE THE ACFT WAS SPINNING LEFT WHEN IT CRASHED. RADAR DATA SHOWED EVIDENCE THAT THE PLTS HAD MADE A SERIES OF STALLS JUST BFR THE ACFT ENTERED A RAPID DSCNT FMAPRX 7800' (DENSITY ALT APRX 10,250'). FOR THE ACFT'S WT & CONFIGURATION, STALL SPEED (VS) WAS DETERMINED TO BE 81 KTS. THE PUBLISHED MIN CTL SPEED (SEA LVL CONDS) WAS 81 KTS & THE INTENTIONAL 1 ENG INOP SPEED (VSSE) WAS 86 KTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW86FA127
- Event ID
- 20001213X34170
- Case number
- FTW86FA127
- 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: 93e8c6588f485a16810577c93a725bd7a180c134834b3ca68b2d0b09256ce05e; retrieved 2026-09-21T04:29:33.503Z.