FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10CA203 · Piper PA-18-150

11 Apr 2010 · Taft, CA, United States

Rapid River Aviation Piper PA-18-150 · Accident: loss of control on ground during takeoff

From Taft Kern County Airport (L17) to Meadows Field (BFL)

Report a problem

Event

NTSB case
WPR10CA203
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
N2887P
Onboard fatalities
Unknown
Route
From Taft Kern County Airport (L17), Taft, CATo Meadows Field (BFL), Bakersfield, CA
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 on ground
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

  • Aircraft › Aircraft oper/perf/capability

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

NTSB narrative

During takeoff from runway 07, as the pilot was becoming airborne, he encountered a strong southeasterly gust of wind. The pilot stated that despite his efforts at maintaining control, the gust was so strong that the right wing lifted up, and the airplane rolled over. At the time, the engine was already developing full power and the pilot's application of full flight control corrective actions was inadequate to counter the gust of wind during this critical phase of flight. The airplane, which became uncontrollable, came to rest upside down with broken wings and a crushed vertical stabilizer. The airport manager witnessed the mishap and corroborated the pilot's statements regarding the wind. The manager estimated the wind's speed was between 25 and 35 mph.

Probable cause

The pilot's loss of control during takeoff upon encountering a strong wind gust.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10CA203
Event ID
20100412X04612
Case number
WPR10CA203
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: e4f19e3532f2e94e91a6446a562f4bf667579844f27067805d92849a888944c1; retrieved 2026-09-15T13:51:03.295Z.