Piper PA-32R-300 accident near Tucson, Arizona, November 8, 2009
On November 8, 2009, a Piper PA-32R-300, registered N2165M, was substantially damaged in an accident during enroute (cruise) near Tucson, Arizona (Tucson International 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
A loss of engine power for undetermined reasons.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 8, 2009
- Place
- Tucson, Arizona · Tucson International Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32R-300 · all PA-32R-300s on the register
- Registration
- N2165M · no longer on the register · serial 32R-7880053
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While descending for landing, the engine lost partial power and the airplane could not maintain altitude. The pilot attempted to divert to a nearby airport; however, he was not able to arrest the airplane's descent and had to make a forced landing to a road. The pilot stated that about 20 feet above the ground, he believes the engine lost all power. The airplane landed hard, struck a road sign, departed the paved surface, and came to rest on the desert floor. A postaccident examination of the airplane and the fuel-injected engine revealed no mechanical anomalies that would have precluded normal operation.
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 (partial) during enroute (cruise) defining event
- Off-field or emergency landing during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Environmental issues › Physical environment › Object/animal/substance › Sign/marker › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 121 hours in all; 22 in this make and model; 33 in the last 90 days; 2 in the last 30 days; 30 as pilot in command
- Last flight review: October 8, 2009
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 15,362 hours
- Last inspection: annual inspection, April 1, 2009; 23 hours since
- Landing gear: retractable
- Engine: Lycoming Engines IO-540-K1G5 (piston); 0 hours total
The flight
- Departed from: IWA Mesa AZ at 11:16 pm
- Destination: TUS Tucson AZ
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 27°F (-3°C)
- Altimeter: 29.87 inHg
- Observation at 11:53 pm from TUS, 32 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.