Piper PA-46-350P accident near Redmond, Oregon, July 21, 2009
On July 21, 2009 at about 9:00 pm local time, a Piper PA-46-350P, registered N117KR, was substantially damaged in an accident during approach near Redmond, Oregon (Roberts Field Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
An undetermined hydraulic system malfunction in the engine compartment during descent from cruise flight which resulted in an in-flight fire.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 21, 2009 · about 9:00 pm local time
- Place
- Redmond, Oregon · Roberts Field Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-46-350P · all PA-46-350Ps on the register
- Registration
- N117KR · registry record · serial 4636088
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that during the approach to the airport, the landing gear down and locked indicator lights (3-green) did not illuminate when the landing gear handle was placed in the down position. The pilot cycled the landing gear; however, the landing gear lights did not illuminate and the pilot activated the emergency landing gear extension system and declared an emergency. After the emergency was declared, the pilot noted flames emanating from the engine cowling and the cockpit began to fill with smoke. Shortly thereafter tower personnel reported that the airplane was trailing smoke and the pilot was cleared to land. The pilot reported that on short final to the runway the "engine experienced a significant, uncommanded decrease in power, but continued to provide partial power." After landing, the pilot and passenger exited the airplane and the fire was extinguished by airport fire department personnel. Examination of the airframe and engine revealed that the nose landing gear hydraulic actuator hose was separated from its corresponding B-nut coupler. The B-nut fitting remained attached to the threaded end of the hydraulic actuator; however, the hose was separated from the coupler at the coupler flange. The hose was covered by dark soot and extensive thermal damage was noted. The opposing end of the hydraulic hose was secured to its associated coupler and fitting. The hydraulic hose is positioned below the engine, adjacent to the turbo charger and exhaust. The examination also revealed that the upper right crossover exhaust pipe was separated from the intermediate crossover exhaust pipe. Fire damage was noted on both the internal and external exposed ends of both the intermediate and right crossover exhaust pipes in the area where they were intended to be connected. The hydraulic hose and associated coupler were removed from the airframe and examined by Safety Board investigators. Due to the extensive thermal damage, the failure mode of the hose was not determined, and the correlation between the exhaust leak and separated hydraulic hose was not established. Subsequent to the accident, the manufacturer amended the maintenance manual for the airplane to reflect changes in the service life limits for nose landing gear hydraulic hoses. The amendment states "Replace nose gear hydraulic hoses (gear actuator/door actuator/ sequence valve), as required; but do not exceed 1,000 hours time-in-service, or eight (8) years, whichever comes first."
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
- Fire/smoke (non-impact) during approach defining event
- Fire/smoke (non-impact) during emergency descent
- Fire/smoke (non-impact) during landing
The NTSB's findings
- Aircraft › Aircraft power plant › Engine exhaust › (general) › Malfunction
- Aircraft › Aircraft systems › Hydraulic power system › (general) › Failure
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 2,560 hours in all; 200 in this make and model; 2,390 as pilot in command
- Last flight review: February 28, 2009
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,818 hours
- Last inspection: annual inspection, February 1, 2009; 48 hours since
- Maximum gross weight: 4,300 lb
- Seats: 6
- Landing gear: retractable
- Engine: Lycoming TIO-540 (piston); 0 hours total
The flight
- Departed from: KDVO Novato CA at 7:00 pm
- Destination: KRDM Redmond OR
- Flight plan: none
- Runway 04, 7,038 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 91°F (33°C), dew point 36°F (2°C)
- Altimeter: 30.03 inHg
- Observation at 9:32 pm from KRDM, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
