FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA295 · Pipistrel ALPHA TRAINER

29 May 2019 · Salida, CO, United States

Pipistrel ALPHA TRAINER · Accident: loss of engine power (total) during landing

From Gallup Municipal Airport (GUP) to Salida Airport - Harriet Alexander Field (ANK)

Report a problem

Event

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

Pipistrel ALPHA TRAINER

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
N40EN
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gallup Municipal Airport (GUP), Gallup, NMTo Salida Airport - Harriet Alexander Field (ANK), Salida, CO
Aircraft age
About 5 years (built 2014)
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
Landing
Defining eventThe 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 (total)
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

  • Aircraft › Fluids/miscellaneous hardware
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot reported that, after fueling the airplane, he did not realize that he had not replaced the fuel cap. During takeoff, the fuel gauge showed that the airplane had 74% of fuel remaining. About 5 nautical miles from the destination airport, the fuel gauge showed that the airplane had 10% of fuel remaining. He flew the airplane in a straight line to the end of the runway and reduced the engine throttle setting to idle, which set up a lower glidepath than normal. When the airplane reached a field west of the runway, the airplane "ran out of fuel." The pilot conducted a forced landing on the field, during which the airplane impacted a fence. The airplane sustained substantial damage to the forward fuselage. A Federal Aviation Administration inspector who examined the wreckage reported that less than 1/2 a gallon of fuel was recovered from the fuel tank. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Probable cause

The pilot's failure to replace the fuel cap after fueling, which resulted in a loss of engine power due to fuel exhaustion and a subsequent forced landing to a field and subsequent collision with a fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA295
Event ID
20190530X22914
Case number
GAA19CA295
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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 2019-05-30.
  • API snapshot SHA-256: d31914a25b59bef503f02bb8452bca6d0f81e7f582d6c38853bd4431bf428379; retrieved 2026-09-16T09:06:07.446Z.