DEN08LA032 · Gomory Long EZ
Gomory Long EZ · Accident: loss of engine power en route
From Elton Hensley Memorial Airport (FTT) to Colonel James Jabara Airport (AAO)
Event
- NTSB case
- DEN08LA032
- 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
Gomory Long EZ
- Aircraft type
- Gomory 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
- N191PS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Elton Hensley Memorial Airport (FTT), Fulton, MOTo Colonel James Jabara Airport (AAO), Wichita, KS
- 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
- En route · cruise
- 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
- Fuel system › Starvation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, the airplane departed with approximately 2 hours flight time of fuel in the left fuel tank and 1.5 hours in the right fuel tank. During the flight at an altitude of 4,500 feet mean sea level, the fuel selector was in the left fuel tank position. The pilot reported that while en route, he decided to change the fuel selector position when the airplane was over the next airport. Approximately 5 minutes later and prior to switching the fuel tank selector to the right tank position, the engine lost power. The pilot switched fuel tanks and attempted to restart the engine; however, the engine did not restart. The pilot then elected to execute a forced landing to a field. During the forced landing, the airplane impacted terrain and came to rest upright. The engine was test run on the airframe for approximately 10 minutes with no anomalies noted. In the accident report section, "How could this accident have been prevented?", the pilot reported, "Add more than enough gas."
Probable cause
The loss of engine power due to fuel starvation. Contributing factors were the pilot's improper fuel calculations and in-flight planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08LA032
- Event ID
- 20071120X01818
- Case number
- DEN08LA032
- 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: b8e54aff202b1dc0821d0480d2b58fb5ccdc3b57119c26a7c5ef2a807330444d; retrieved 2026-09-21T18:21:21.815Z.