FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA285 · Piper PA18 150

25 May 2019 · Cody, WY, United States

Hoodoo Land Holdings Piper PA18 150 · Accident: abnormal runway contact during landing

From Yellowstone Regional Airport (COD) to Yellowstone Regional Airport (COD)

Report a problem

Event

NTSB case
GAA19CA285
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 PA18 150

Aircraft type
Piper PA18
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
N997CC
Onboard fatalities
Unknown
Route
From Yellowstone Regional Airport (COD), Cody, WYTo Yellowstone Regional Airport (COD), Cody, WY
Aircraft age
About 19 years (built 2000)
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
Abnormal runway contact
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 › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The student pilot reported that, during the instructional flight, he was practicing stop-and-go landings. On his second landing, while on short final, the glidepath was lower than normal, and he increased the power setting to extend the glide. After the airplane crossed the runway threshold, he flared slightly high and leveled the airplane to keep it from sinking too fast. The airplane bounced slightly on touchdown, and he overcorrected with rudder inputs due to a crosswind. The airplane rolled forward, and the tail began to rise. The flight instructor reported that, at this point, he took over control of the airplane and applied back stick pressure; however, the airflow was too slow over the elevator flight control surface to have effect, and the airplane nosed over and came to rest inverted. The left-wing lift strut and rudder were substantially damaged. The student and instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Probable cause

The student pilot's improper landing flare in crosswind conditions, which resulted in a bounced landing, and his subsequent loss of airplane control after overcorrecting with rudder. Contributing to the accident was the flight instructor's delayed remedial action, which resulted in a nose-over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA285
Event ID
20190526X53932
Case number
GAA19CA285
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: 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: 510642359d94e35249b10c1e7bd9e35e2dcb8ae4295c798ca15a962590863aa1; retrieved 2026-09-16T09:03:44.499Z.