FTW03LA143 · Piper PA-18A-150
Piper PA-18A-150 · Accident: loss of engine power during initial climb
From Aero Valley Airport (52F) to 52F
Event
- NTSB case
- FTW03LA143
- 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
Piper PA-18A-150
- Aircraft type
- Piper PA-18
- 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
- N9789D
- Operator
- Marcair
- Onboard fatalities
- Unknown
- Route
- From Aero Valley Airport (52F), Roanoke, TXTo 52F
- 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
- 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
- Fuel system › Starvation
- Pilot in command(cfi) › In-flight planning/decision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the takeoff climb of the 3rd or 4th touch and go, "the engine lost power and began to sputter." Prior to the flight, according to the cockpit fuel sight gauges observed by the private pilot, the left fuel tank indicated approximately 3/4 full of fuel, and the right tank indicated approximately 1/2 full of fuel. The private pilot, who was receiving instruction for a tailwheel endorsement, stated the fuel selector was selected to the left fuel tank at the time the engine lost power. After the engine lost power, the flight instructor initiated a forced landing to a field. During the forced landing, the airplane impacted trees and terrain, and came to rest on its nose. Examination of the airplane revealed the fuel system was intact, the left main fuel tank was empty, the right main fuel tank contained "plenty of fuel," and the fuel was clear of contaminants.
Probable cause
The flight instructor's inadequate in-flight planning/decision resulting in fuel starvation and the loss of engine power. 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 FTW03LA143
- Event ID
- 20030505X00619
- Case number
- FTW03LA143
- 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, coordinates. 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: ff3d379d8ad47dd14fa350efe8abb932d78e3b5a5b72e9bf42d3d3acf1cf6728; retrieved 2026-09-21T19:29:55.206Z.