FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10FA239 · Piper PA-24-250

14 May 2010 · Redmond, OR, United States

Piper PA-24-250 · Accident: loss of control in flight during initial climb

From Roberts Field (RDM) to Burns, OR

Report a problem

Event

NTSB case
WPR10FA239
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
1 · 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-24-250

Aircraft type
Piper PA-24
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
N6967P
Onboard fatalities
Unknown
Route
From Roberts Field (RDM), Redmond, ORTo 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
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

  • Aircraft › Aircraft oper/perf/capability
  • 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

A witness who was located in a vehicle adjacent to the accident site reported that while conducting a routine daily runway inspection, he observed the airplane in a near vertical attitude above the departure end of the active runway. The witness estimated that the airplane was about 100 to 200 feet above the ground when it performed a 360-degree roll and stalled. It then entered a nose-low attitude, made another 360-degree roll, and descended below a tree line. Another witness reported that he observed the airplane depart the active runway and initiate a normal climb. As the airplane reached the departure end of the runway it entered an abrupt climb at an approximate 90-degree angle. The witness further stated that the airplane climbed for approximately 200 feet, nosed over, and descended into the ground. A postaccident examination of the engine and airframe revealed no pre impact mechanical malfunctions. Toxicology tests of post-mortem samples from the pilot detected Amlodipine, a prescription medication used for the treatment of high blood pressure. The medication typically does not have any adverse effects, and is routinely approved by the Federal Aviation Administration.

Probable cause

The pilot's failure to maintain airspeed, which resulted in a stall and collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10FA239
Event ID
20100514X12745
Case number
WPR10FA239
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: a639ac297dfd47054663b8372fa7962545a1f8988e80bb5a2661b130ef38f521; retrieved 2026-09-13T20:48:09.568Z.