FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW94LA016 · Beech A36

12 Oct 1993 · Tomball, TX, United States

Beech A36 · Accident: in flight collision with object on approach

From Alice International Airport (ALI) to David Wayne Hooks Memorial Airport (DWH)

Report a problem

Event

NTSB case
FTW94LA016
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
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 A36

Aircraft type
Beechcraft 36
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
N6198A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Alice International Airport (ALI), Alice, TXTo David Wayne Hooks Memorial Airport (DWH)
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
Approach · IFR final approach
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 collision with object
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
Substantial

Cause areas

  • Pilot in command › Descent, continued
  • Pilot in command › Minimum descent altitude, disregarded
  • Pilot in command › Missed approach, delayed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE AIRPLANE STRUCK TREES DURING AN INSTRUMENT APPROACH. THE PILOT REPORTED HE HAD DESCENDED TO MINIMUMS (500 FEET MSL) AND ENGAGED THE AUTOPILOT IN THE ALTITUDE HOLD MODE. HE STATED THAT AFTER LOOKING OUT FOR THE RUNWAY, HE NOTICED THE AIRPLANE HAD DESCENDED BELOW 300 FEET MSL AND DESCENDED ANOTHER 150 FEET BEFORE IT STARTED CLIMBING AFTER HE INITIATED A GO AROUND. AIRPORT ELEVATION WAS 152 FEET. ATC TAPES INDICATED THE PILOT WAS GIVEN AN ALTITUDE ALERT AND THAT 15 SECONDS LATER HE STATED THAT HE WAS GOING AROUND. THE PILOT STATED HE THOUGHT HE ENCOUNTERED WINDSHEAR; HOWEVER, THE WINDS WERE 120 AT 7 KNOTS WITH NO GUSTS AND THERE WERE NO REPORTS OF WINDSHEAR IN THE AREA. THE AIRPLANE ULTIMATELY LANDED WITHOUT FURTHER INCIDENT AT A NEARBY VFR AIRPORT.

Probable cause

WAS THE PILOT'S DISREGARD FOR AND CONTINUED DESCENT BELOW MDA AND HIS DELAY IN EXECUTING A GO AROUND.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW94LA016
Event ID
20001211X13568
Case number
FTW94LA016
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 1993-10-13.
  • API snapshot SHA-256: 3d379c7484f156bbccc67101712d3695129d7780a180c1ef181494a598627e26; retrieved 2026-09-23T01:32:12.071Z.