FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC05CA140 · Piper PA-18

13 Sept 2005 · Nenana, AK, United States

Piper PA-18 · Accident: hard landing

From Nenana Municipal Airport (PANN) to Nenana, AK

Report a problem

Event

NTSB case
ANC05CA140
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-18

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
N7761D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Nenana Municipal Airport (PANN), Nenana, AKTo Nenana, AK
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
Landing · flare/touchdown
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
Hard landing
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

  • Pilot in command › Recovery from bounced landing, improper

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

NTSB narrative

The private certificated pilot was landing at a hunting campsite, where he had landed in the past. The grass-covered landing area is oriented northwest/southeast, and is about 600 feet long, and about 12 feet wide. The pilot said that he landed toward the southeast, and during the landing roll, the main landing gear tires encountered soft terrain. The airplane then nosed over and received structural damage to the rudder, the left wing, and the left wing lift strut. In the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) submitted by the pilot, the pilot reported that during the landing, a gust of wind resulted in a bounced landing. On the second contact with the landing area, the pilot indicated that he was unable to lower the tail of the airplane, and it began to rise, which resulted in a nose over. He reported the wind conditions as 220 degrees magnetic at 8 knots, gusts to 10 knots.

Probable cause

The pilot's improper recovery from a bounced landing during the landing roll, which resulted in a loss of control and a nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC05CA140
Event ID
20051006X01589
Case number
ANC05CA140
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: 9a40c58432ce2d19a1d7cae3da22bb1dec61668a506dadf61a5bffe0ec578eee; retrieved 2026-09-22T05:22:33.840Z.