FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02FA071 · Beech C23

17 Jan 2002 · Sinton, TX, United States

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

From Angelina County Airport (LFK) to Alfred C 'Bubba' Thomas Airport (T69)

Report a problem

Event

NTSB case
FTW02FA071
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
Unknown
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 C23

Aircraft type
Beechcraft 23
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
N6622X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Angelina County Airport (LFK), Lufkin, TXTo Alfred C 'Bubba' Thomas Airport (T69), Sinton, TX
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 missed 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
Destroyed

Cause areas

  • Pilot in command › Altitude/clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The single-engine airplane impacted trees and terrain during dark night instrument meteorological conditions with fog. The private pilot, sole occupant, was returning to the home base airport from a cross-country flight. The ATC controller issued the pilot the weather (wind 120 degrees at 9 knots, visibility 10, clouds 25,000 scattered, temperature 20 degrees Celsius, dew point 19 degrees Celsius, and the altimeter 30.02 inches Mercury) at the nearest airport (approximately 15 nautical miles from the destination airport) and told the pilot that fog was reported in the area. The pilot requested and was cleared for the non-precision approach VORDME 14 at the destination airport. Radar contact was lost with the aircraft at an altitude of 1,901 feet msl. Subsequently, the pilot transmitted in part "approach... can't find the airport." The controller instructed the pilot to execute the published missed approach instructions and asked the pilot for his next request. The pilot transmitted in part: "I've got it, I've got the strobe under me now sir." The controller requested if the airplane was landing and the pilot transmitted "affirmative sir I got the strobe." The controller asked the pilot if he was canceling IFR, and the pilot transmitted "no sir just a minute stay with me please sir." There were no further communications with the pilot. Witnesses near the airport reported hearing the airplane flying low, a loud boom, the sound of an explosion and fire. Local authorities, who responded to the accident site, reported "floating fog and mist in the vicinity of the airport." The pilot had accumulated 2,000 hours in the make and model of airplane. In 1996, the pilot had logged 122.8 hours of actual instrument flight time; however, neither the pilot's total or recency of IFR experience at the time of the accident could be verified. Flight control continuity was confirmed. Examination and teardown of the engine did not reveal any discrepancies that would preclude operation of the engine. The muffler was pressure tested in accordance with the manufacturer's heater muffler inspection procedures, and no leaks were detected. According to the NTSB metallurgist, the debris found on the carburetor inlet screen were deposits of the melted float assembly. No evidence of an in-flight mechanical and/or flight control malfunction was found that would have rendered the airplane uncontrollable prior to the impact.

Probable cause

The pilot's failure to maintain clearance with trees while executing a missed approach procedure. Contributing factors were the prevailing fog and the dark night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02FA071
Event ID
20020124X00113
Case number
FTW02FA071
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2002-01-18.
  • API snapshot SHA-256: 2dee6184b227e444e538cbe72ad09a64b8eebb8e62032ef933be77eaf39fbe8f; retrieved 2026-09-20T20:14:23.863Z.