FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC10CA016 · Piper PA-17

31 Jan 2010 · Skwentna, AK, United States Possible conflict

Piper PA-17 · Accident: collision during takeoff/landing on approach

From Skwentna, AK to Skwentna, AK

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location and departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC10CA016
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-17

Aircraft type
Piper PA-17
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
N4568H
Operator
Ben Knapp
Onboard fatalities
Unknown
Route Narrative disagrees
From Skwentna, AKTo 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 final
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
Collision during takeoff/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

  • Personnel issues › Action/decision

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

NTSB narrative

The private pilot reported that he was on a personal flight and was attempting to land on a frozen lake. While on final approach to land, he said the airplane encountered a wind gust and that the left wing struck the top of a tree. The airplane descended and collided with terrain short of the intended landing site. The pilot stated that there were no preaccident mechanical problems with the airplane.

Probable cause

The pilot's decision to make a low-altitude approach to land over trees in gusting winds, which resulted in an in-flight collision with a tree and a loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC10CA016
Event ID
20100201X91417
Case number
ANC10CA016
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: e1d1025378e010cb43a22b7ff6bf0fd86edd81cccd6662061a29cf418347e3aa; retrieved 2026-09-15T13:39:36.594Z.