FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA093 · Tillman Long EZ

12 Mar 2002 · Lockhart, TX, United States

Tillman Long EZ · Accident: loss of engine power during initial climb

From Lockhart Municipal Airport (50R) to Lockhart, TX

Report a problem

Event

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

Tillman Long EZ

Aircraft type
Tillman LONG EZ
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
N126DT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lockhart Municipal Airport (50R), Lockhart, TXTo Lockhart, 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
Initial climb
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 engine power
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

  • Reason for occurrence undetermined

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

NTSB narrative

The airplane had not been flown in three weeks, and the pilot planned to fly the airplane around the traffic pattern. The pilot performed a preflight inspection, taxied the airplane to the runway, and then performed a "normal" engine run-up prior to takeoff. Shortly after takeoff, approximately 200 feet agl, the engine began to lose power. The pilot "switched tanks, checked the mixture, and jockeyed the throttle a couple of times," with no response from the engine. Unable to make the runway, the pilot initiated a forced landing to a field, during which the airplane struck a fence separating the right wing and right main landing gear. The pilot stated that the airplane contained approximately 20 gallons of fuel prior to takeoff. The FAA inspector and the pilot performed a field inspection on the engine. No anomalies with the engine or airframe were noted during the examination. The reason for the loss of engine power was not determined.

Probable cause

the loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA093
Event ID
20020327X00405
Case number
FTW02LA093
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-03-13.
  • API snapshot SHA-256: d9717d872b48bace53a041e0d745f118fce221a7a0cba7c99f1683a8557d9b49; retrieved 2026-09-22T11:04:33.726Z.