FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC15CA022 · Piper PA 18A 150

19 Apr 2015 · Nondalton, AK, United States

Piper PA 18A 150 · Accident: loss of control in flight during takeoff

From Lake Hood Seaplane Base (PALH) to Nondalton Airport (5NN)

Report a problem

Event

NTSB case
ANC15CA022
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 18A 150

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
N2894Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Hood Seaplane Base (PALH), Anchorage, AKTo Nondalton Airport (5NN), Nondalton, AK
Aircraft age
About 56 years (built 1959)
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
Takeoff
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 control in flight
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

  • Personnel issues › Task performance

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

NTSB narrative

The pilot was on a personal cross-country flight in a tailwheel-equipped, single engine airplane. The pilot stated that although there was a strong crosswind on landing, he did not expect it to affect the airplane on takeoff. During the takeoff ground roll, when the pilot could no longer maintain directional control, he took off, climbing about 10 feet before losing altitude and impacting a ditch that is parallel to the runway. During the impact, the airplane sustained substantial damage and the pilot and sole occupant, sustained serious injuries. The pilot stated there were no preimpact mechanical malfunctions or anomalies that would have precluded normal operation.

Probable cause

The pilot's failure to maintain control of the airplane while taking off with a gusting crosswind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC15CA022
Event ID
20150421X05551
Case number
ANC15CA022
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: 603365446daeda191f0fc6aafdfb09f1c6a669f06a49ccd01e902f595f228c84; retrieved 2026-09-16T02:14:53.281Z.