FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC02FA097 · Piper PA-18

14 Aug 2002 · Skwentna, AK, United States

Piper PA-18 · Accident: loss of control in flight on approach

From Lake Hood Airport (Z41) to Skwentna Airport (SKW)

Report a problem

Event

NTSB case
ANC02FA097
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
2 · 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
N4065Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Hood Airport (Z41), Anchorage, AKTo Skwentna Airport (SKW), Skwentna, 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
Approach · VFR pattern base
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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall; Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed, inadequate
  • Pilot in command › Stall, inadvertent

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 pilot departed in a wheel-equipped airplane with one passenger on a cross-country flight en route to a remote airstrip. Family members reported that the pilot was en route to the family's remote cabin located adjacent to the destination airstrip, with an anticipated return 3 days later. When the airplane did not return, the flight was reported overdue. Search personnel checked the pilot's cabin and reported that there were no signs that anyone had been at the cabin recently. A review of the accident pilot's flight plan for the outbound portion of the flight revealed that the pilot cancelled his flight plan while still airborne, over the destination airport. Ground search personnel and aerial search personnel located the airplane wreckage along the anticipated final approach path to the destination airstrip. The accident site consisted of thick-forested terrain, with trees extending upwards of 30 feet. The airplane wreckage was not easily visible due to thick vegetation. The fuselage came to rest in an inverted and nose down attitude. A postaccident examination of the airplane did not reveal any mechanical malfunctions. No emergency locator transmitter (ELT) signal was received from the airplane. The ELT was found detached from its mounting tray, with the antenna lead still connected, and the switch in the ARM position. The ELT was sent to the manufacturer for disassembly and testing under supervision of the FAA. The test revealed that the G-switch, and all other components in the ELT, operated within the prescribed parameters. A review of recorded data obtained from the pilot's hand held GPS unit revealed that the airplane approached the destination airstrip from the southeast, and entered a right downwind approach for runway 27. The airplane then proceeded southeast bound, past the approach end of runway 27, and made a gradual turn, consistent with a right base leg for landing on runway 27. As the right turn progressed, the rate of turn increased sharply. The last GPS track recorded indicated a magnetic heading of 095 degrees. An autopsy of the pilot concluded he did not die immediately upon impact, but did not establish a time of death. Toxicological testing found very low levels of tetrahydrocannabinol in the pilot's blood.

Probable cause

The pilot's failure to maintain adequate airspeed while on approach to land, which resulted in an inadvertent stall, and subsequent collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC02FA097
Event ID
20020829X01490
Case number
ANC02FA097
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: 8190b006a6d0cd988d0d51bc3fbc3573b2152f53ea3dd96d077283c85001edb7; retrieved 2026-09-20T19:54:54.313Z.