FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA06CA025 · Piper PA-18-150

9 Dec 2005 · Prineville, OR, United States

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

From Prineville Airport (S39) to Burns Municipal Airport (BNO)

Report a problem

Event

NTSB case
SEA06CA025
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
N2584S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Prineville Airport (S39), Prineville, ORTo Burns Municipal Airport (BNO), Burns, OR
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
Initial climb
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
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command(cfi) › Remedial action, improper

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

NTSB narrative

The non-current private pilot, who occupied the front seat, initiated the takeoff with the flight instructor in the rear seat. While in a steep climb at an altitude of about 30 feet agl, a gust of wind lifted the left wing, which caused the airplane to roll over to the right. After the front seat pilot, at the command of the flight instructor, closed the throttle, the airplane impacted the side of the runway in a nose down, wings level attitude, resulting in a propeller strike and the collapse of both main landing gear. There were no anomalies reported with the airplane, which would have precluded normal operations.

Probable cause

Aircraft control not maintained by the private pilot during the initial takeoff climb, and the improper remedial action by the flight instructor. A factor was the wind gust.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA06CA025
Event ID
20060106X00023
Case number
SEA06CA025
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: 3400c85684f6bf999bd826b77bc387ba371e4dacb66bbcc297386ec595144919; retrieved 2026-09-22T05:12:42.475Z.