The U.S. aircraft register, updated daily
Accidents · NTSB WPR10FA239 · Final report

Piper PA-24-250 accident near Redmond, Oregon, May 14, 2010

On May 14, 2010 at about 2:18 pm local time, a Piper PA-24-250, registered N6967P, was substantially damaged in an accident during initial climb near Redmond, Oregon (Roberts Field Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 14, 2010 · about 2:18 pm local time · cases in 2010
Place
Redmond, Oregon · Roberts Field Airport · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-24-250 · all PA-24-250s on the register
Registration
N6967P · no longer on the register · serial 24-2108
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during initial climb defining event
  2. Aerodynamic stall/spin during initial climb
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land
  • Flight time: 10,000 hours in all
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Airframe total time: 2,143 hours
  • Last inspection: annual inspection, June 1, 2009; 12 hours since
  • Maximum gross weight: 2,900 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming O-540-A1D5 (piston); 0 hours total

The flight

  • Departed from: RDM Redmond OR at 2:18 pm
  • Destination: Burns OR
  • Flight plan: none
  • Runway 10, 7,006 ft by 100 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 48°F (9°C), dew point 37°F (3°C)
  • Altimeter: 30.04 inHg
  • Observation at 2:23 pm from RDM

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

8 documents, released by the NTSB on April 28, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR10FA239.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.