FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW96FA113 · Cessna 150

9 Feb 1996 · Galveston, TX, United States

Cessna 150 · Accident: in flight encounter with weather on approach

From Archer City Municipal Airport (T39) to Scholes International At Galveston Airport (GLS)

Report a problem

Event

NTSB case
FTW96FA113
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
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

Cessna 150

Aircraft type
Cessna 150
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
N7973F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Archer City Municipal Airport (T39), Huntsville, TXTo Scholes International At Galveston Airport (GLS)
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
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 encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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 › Proper altitude, not maintained
  • Pilot in command › VFR flight into imc, inadvertent

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

NTSB narrative

Weather along the route of flight was VFR until the airplane reached the destination airport, where the weather was IMC at night with heavy fog. According to airport authorities and en route ATC and AFSS facilities, no radio communication was received from the pilot after he filed his initial VFR flight plan. He received a weather brief (valid until 1830 CST) from an AFSS before his initial departure at 1636 CST. The pilot refueled en route and departed the refueling airport at about 1915. After an overdue message was received, airport personnel at the destination located the wreckage at 2120, approximately 1,550 feet beyond the departure end of runway 35. The wreckage (including ground scars) was distributed over a 160 foot area and on a heading of 350 degrees. The pilot was not instrument rated and his last flight was 105 days before the accident. He had logged about 250 hours of flight time, of which 5 hours were simulated instrument time, but no actual instrument time was logged. Also, he had about 23 hours of night time. No uncorrected defects were found in the maintenance records; physical examination of the airframe and engine revealed no anomalies. The altimeter at the accident site was 30.03. The pilot had 29.91 dialed into the altimeter. According to the pilot of another airplane, who flew the ILS approach at about 2115 cst, he entered a fog at about 400 feet agl and made a missed approach at the decision height, because the 'the runway lights were not visible and the incandescent approach lights were barely visible.'

Probable cause

the pilot's inadvertent flight into instrument meteorological conditions (IMC), and his failure to sufficient altitude. Factors relating to the accident were: darkness, foggy weather conditions, the pilot's lack of instrument experience, his lack of recent flight time, and spatial disorientation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW96FA113
Event ID
20001208X05237
Case number
FTW96FA113
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 1996-02-10.
  • API snapshot SHA-256: b9a533cc0ea795b4170351cbfaff316f3b2e7e268e808a8149a3bc2638339bd5; retrieved 2026-09-20T23:26:15.360Z.