FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC13CA092 · Piper PA-18-150

3 Sept 2013 · Skwentna, AK, United States Possible conflict

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

From Birchwood Airport (BCV) to Birchwood Airport (BCV)

Report a problem

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

Event

NTSB case
ANC13CA092
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-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
N40205
Operator
Unknown
Onboard fatalities
Unknown
Route
From Birchwood Airport (BCV), Chugiak, AKTo Birchwood Airport (BCV), Chugiak, 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
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 › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was taking off from an off-airport landing site near the top of a mountain ridge, in gusty wind conditions, in a tailwheel-equipped airplane. During the takeoff roll, a gust of wind pushed the airplane onto rough terrain, which resulted in the airplane becoming airborne before it had sufficient speed to maintain flight. When the airplane settled back to the ground, the main landing gear broke off, and the airplane nosed over, sustaining substantial damage to the wings and empennage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's decision to take off from a remote, rough landing site in gusty wind conditions, which resulted in a loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC13CA092
Event ID
20130904X44742
Case number
ANC13CA092
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, 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: b0841d89baae947125b612ff0699a8b32ee4ec7d826c51e6396334f6028470eb; retrieved 2026-09-15T22:43:45.588Z.