FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA045 · Cessna 140

24 Nov 2001 · Gilchrist, TX, United States

Cessna 140 · Accident: in flight collision with terrain/water during takeoff

From Gilchrist, TX (no airport) to an unrecorded destination

Report a problem

Event

NTSB case
FTW02LA045
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
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
Visual Meteorological Cond

Cessna 140

Aircraft type
Cessna 140
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
N72701
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gilchrist, TX (no airport)To 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
Takeoff
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 terrain/water
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 › Carburetor heat, improper use of
  • Pilot in command › Wrong runway, selected

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

NTSB narrative

The pilot took off to the south from a grass field, which measured approximately 760 feet in length and was located adjacent to the Gulf of Mexico. The northern half of the field was mowed, whereas the southern half of the field was not. The pilot reported to the FAA inspector that he felt like the airplane's engine was not producing full power. The airplane neared the end of the field where it contacted a two-foot embankment with its tail wheel and nosed over inverted into water. The pilot reported that he left the carburetor heat in the ON position during takeoff. He also reported that he took off with a "slight tailwind." At the time of the accident, a nearby weather observation facility reported the wind from the northwest at 8 knots.

Probable cause

the pilot's improper use of carburetor heat during takeoff and his selection of a downwind runway, which resulted in a degradation of performance and the airplane impacting an embankment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA045
Event ID
20011205X02355
Case number
FTW02LA045
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: 0e6c3ec3d79ebeb0ddeb4d26095b895114dadb9d60245c4acefd33c47c874853; retrieved 2026-09-22T11:19:40.888Z.