Piper PA 46-310P accident near Redmond, Oregon, March 1, 2015
On March 1, 2015 at about 5:40 pm local time, a 1988 Piper PA 46-310P, registered N9133G, was substantially damaged in an accident during enroute (cruise) near Redmond, Oregon (Roberts Field Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of engine power during cruise flight for reasons that could not be determined because postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 1, 2015 · about 5:40 pm local time · cases in 2015
- Place
- Redmond, Oregon · Roberts Field Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA 46-310P, built 1988 · all PA 46-310Ps on the register
- Registration
- N9133G · registry record · serial 4608111
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot reported that, about 30 minutes into the private, cross-country flight and while the airplane was cruising at 23,000 ft mean sea level, the engine started running roughly. The pilot noticed that the No. 5 cylinder head temperature (CHT) was lower than normal. He cycled the magnetos and noticed that the engine ran rougher than normal when the left magneto was selected. He then enriched the mixture, and the engine smoothed out. He continued to monitor the engine and adjust the mixture. About 30 minutes later, the engine lost power. The pilot diverted to a nearby airport and attempted to line up for a runway but did not have sufficient altitude. He performed a forced landing to the airport infield, which resulted in the nose landing gear collapsing and structural damage to the wing spar. Postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation. During an engine test run up to full power, the only anomaly noted was that the No. 5 CHT was 50 to 70° lower than all the other cylinders. However, the lower CHT likely would not cause a loss of engine power.
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
- Loss of engine power (total) during enroute (cruise) defining event
- Runway excursion during landing (landing roll)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 2,572 hours in all; 1,299 in this make and model; 90 in the last 90 days; 29 in the last 30 days
- Last flight review: April 22, 2014
- Medical certificate: Class 3 (waiver time limited special)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,208.3 hours
- Last inspection: annual inspection, October 16, 2014; 94 hours since
- Maximum gross weight: 4,101 lb
- Seats: 6
- Landing gear: fixed
- Engine: Cont Motor TSIO-520 SER (piston); 0 hours total
The flight
- Departed from: KFHR Friday Harbor WA at 4:00 pm
- Destination: KVGT North Las Vegas NV
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 180° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 34°F (1°C), dew point 16°F (-9°C)
- Altimeter: 30.19 inHg
- Observation at 5:56 pm from KRDM
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
7 documents, released by the NTSB on July 24, 2017. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Pilot's Statement | PDF, 1 page | View Download |
| 3 | Wreckage Examination Report | PDF, 4 pages | View Download |
| 4 | Engine Monitoring Data Plots | PDF, 3 pages | View Download |
| 5 | Fuel Sample Analysis | PDF, 2 pages | View Download |
| 6 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 7 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
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
- N9133G on the register today · the tail number may have moved to another aircraft since
- Piper PA-46 Malibu, Mirage, Matrix and M-Class 1,694 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Cont Motor TSIO-520 SER 4,110 aircraft carry this series today · as the NTSB recorded it
- Roberts Fld/Redmond Municipal · nearest airport
- Friday Harbor Airport · departed from
- North Las Vegas Airport · bound for
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 7,002 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR15LA137.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.
