FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC03LA002 · Piper PA-22

10 Oct 2002 · Wasilla, AK, United States

Piper PA-22 · Accident: nose over during landing

From Warren "Bud" Woods Palmer Municipal Airport (PAQ) to Wasilla Airport (IYS)

Report a problem

Event

NTSB case
ANC03LA002
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-22

Aircraft type
Piper PA-22
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
N7027D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Warren "Bud" Woods Palmer Municipal Airport (PAQ), Palmer, AKTo Wasilla Airport (IYS), Wasilla, 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 · landing roll
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
Nose over
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

  • Dual student › Brakes(normal), excessive
  • Pilot in command(cfi) › Supervision, inadequate

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

NTSB narrative

The flight instructor, seated in the right seat, was providing flight instruction/recurrent training to the private pilot, seated in the left seat, in a wheel-equipped airplane converted to a tailwheel configuration. The private pilot had accomplished two successful stop-and-go landings prior to the accident landing. On the third landing, during landing roll on a dry paved runway, the private pilot allowed the airplane to veer slightly to the left of the runway's centerline. The flight instructor attempted to realign the airplane by applying a slight amount of right rudder, the private pilot simultaneously applied heavy braking, and both wheels locked. The airplane subsequently nosed over, and sustained substantial damage to the wings, fuselage, and empennage. The flight instructor noted that there were no preaccident mechanical anomalies with the airplane.

Probable cause

The instructor's inadequate supervision of the pilot-rated dual student, and the dual student's excessive use of brakes during the landing roll, which resulted in the nose over of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC03LA002
Event ID
20021018X05342
Case number
ANC03LA002
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: 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 2002-10-11.
  • API snapshot SHA-256: 1fbc79bc10dc1a4c13160d12e3b89626cdb6cb3449a8b4e5f0e535bac50aa195; retrieved 2026-09-22T10:06:18.653Z.