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

Piper PA-46 accident near Delano, California, July 17, 2012

On July 17, 2012 at about 6:40 pm local time, a Piper PA-46, registered N558RW, was substantially damaged in an accident during landing (flare/touchdown) near Delano, California (Delano Municipal airport). It was a business 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

The pilot's failure to extend the landing gear before touchdown. Contributing to the accident was the pilot's failure to perform the appropriate checklist due to distractions posed by another airplane inbound to the same airport and a cluttered radio frequency.

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

What the record shows

Date
July 17, 2012 · about 6:40 pm local time
Place
Delano, California · Delano Municipal · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-46 500TP · all PA-46s on the register
Registration
N558RW · no longer on the register · serial 4697346
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

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

The owner-pilot was the only person on board and was flying the turboprop airplane on a personal business trip. When he was about 10 miles south-southeast of the non-towered destination airport, he heard the pilot of a twin-engine airplane report that he was approaching the same airport from the north. The wind favored a landing on runway 32, and the turboprop pilot planned to fly a straight-in approach for landing on that runway. When the turboprop pilot was on final approach for runway 32 about 5 miles from the airport, he heard the twin-engine pilot announce that he was on the left base leg of the traffic pattern for runway 14. As the turboprop pilot continued the approach about 2 miles from the airport, he observed the twin-engine airplane on his traffic display; at that time, the twin-engine airplane was still about 6 miles from the airport. Constant radio transmissions from aircraft at two other non-towered airports in the vicinity precluded the turboprop pilot from communicating clearly with the twin-engine pilot to coordinate their arrivals. Based on the information from his traffic display, the turboprop pilot continued his straight-in approach for runway 32. Due to the distractions of the twin-engine airplane and the radio communication difficulties, the turboprop pilot did not perform the approach checklist and forgot to extend the landing gear, which he did not realize until touchdown. The airplane came to rest upright and intact about 50 feet off the side of the runway. The pilot was uninjured. Examination revealed substantial damage to the fuselage and wings. The pilot reported that he had traveled internationally in the preceding weeks and that he experienced some "mental fatigue." It was not determined whether or when the twin-engine airplane landed at the same airport.

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. Landing gear not configured during landing (flare/touchdown) defining event
  2. Abnormal runway contact during landing (flare/touchdown)
  3. Runway excursion during landing

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • factor Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • cause Aircraft › Aircraft systems › Landing gear system › Gear extension and retract sys › Not used/operated
  • factor Environmental issues › Operating environment › Communication system › (general) › Effect on personnel
  • factor Personnel issues › Psychological › Attention/monitoring › Attention › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 2,646 hours in all; 788 in this make and model; 33 in the last 90 days; 12 in the last 30 days
  • Last flight review: February 18, 2012
  • Medical certificate: Class 3
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 875 hours
  • Last inspection: annual inspection, February 15, 2012; 22 hours since
  • Maximum gross weight: 5,134 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Pratt & Whitney PT6 (turboprop); 0 hours total

The flight

  • Departed from: TRM Thermal CA at 5:15 pm
  • Destination: DLO Delano CA
  • Flight plan: none
  • Runway 32, 5,659 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 300° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 54°F (12°C)
  • Altimeter: 29.97 inHg
  • Observation at 1:35 am from PTV, 18 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

5 documents, released by the NTSB on September 11, 2012. 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.

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.