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

Piper PA46 accident near Seattle, Washington, June 2, 2016

On June 2, 2016 at about 9:20 am local time, a 1999 Piper PA46, registered N301DM, was substantially damaged in an accident during approach (IFR initial approach) near Seattle, Washington (Boeing Field/King County Intl). 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

The pilot’s failure to use the emergency procedures checklist for generator failures or for gear extension following a loss of electrical power due to the separated flag terminal of a diode in overstress, which resulted in a gear-up landing.

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

What the record shows

Date
June 2, 2016 · about 9:20 am local time
Place
Seattle, Washington · Boeing Field/King County Intl · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA46 350P, built 1999 · all PA46s on the register
Registration
N301DM · registry record · serial 4636231
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot departed in dark night conditions for the cross-country flight. While air traffic control vectored the accident airplane for the instrument approach to the destination airport, both of the airplane’s generator circuit breakers popped out, but the pilot did not observe a generator failure light. He subsequently pushed both circuit breakers in and they remained in. Shortly thereafter, when given the final vector to join the localizer, the instrument panel went dark, and all post lights, backlit gauges, and engine instrument gauges went dark and failed. The failure also affected the three green landing gear down-and-locked lights and the landing gear warning horn. According to the pilot, it was too dark to see the position of all the circuit breakers; rather than troubleshooting the problem in the air, he elected to proceed with the instrument approach. The pilot subsequently landed with the landing gear retracted, which resulted in substantial damage to the undercarriage and the left wing. A postaccident examination revealed that a diode located between the left main electrical bus circuit breaker and the main bus was found to have a separated flag terminal, which caused an open circuit. As a result, it is likely that before the accident, the left tie bus and main bus circuit was not providing a conductive electrical path, which required the right tie bus and main bus circuit to carry the full load. When the right main electrical bus circuit breaker tripped due to an excessive electrical load, the electrical path from the tie bus to the main bus no longer provided power. Subsequent testing of the subject diode revealed that the solder joint had failed in overstress though the diode itself was functional. The pilot reported that he did not refer to or use the airplane's emergency procedures checklist for a generator failure, which directs the pilot to reduce electrical loads in the event of such a failure. Depending on how much the electrical load was reduced, the pilot may have prevented the right main circuit breaker failure and retained the ability to lower the landing gear. Additionally, the pilot failed to use the emergency landing gear extension procedure. The generator failure emergency procedures checklist contains a CAUTION that states, "Without electrical power, the landing gear must be lowered with the emergency extension procedure. The gear position lights, and the flaps will be inoperative." Had the pilot used the checklists for a generator failure and, subsequently, for gear extension, this accident would have likely been prevented.

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. Electrical system malf/failure during approach (IFR initial approach) defining event
  2. Landing gear not configured during landing (flare/touchdown)
  3. Abnormal runway contact during landing

The NTSB's findings

  • cause Aircraft › Aircraft systems › Electrical power system › DC rectifier › converter › Failure
  • factor Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • factor Personnel issues › Action/decision › Action › Lack of action › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 2,080 hours in all; 57 in this make and model; 57 in the last 90 days; 21 in the last 30 days; 1,905 as pilot in command
  • Last flight review: March 6, 2016
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,582 hours
  • Last inspection: annual inspection, December 18, 2015; 86 hours since
  • Maximum gross weight: 4,358 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Pratt & Whitney PT6-35 (turboprop); 2,725 hours total

The flight

  • Departed from: RNO Reno NV at 6:57 pm
  • Destination: BFI Seattle WA
  • Flight plan: IFR
  • Runway 13R, 10,000 ft by 200 ft

Weather at the time

  • Light: night, dark
  • Wind: from 170° at 10 knots, gusting 18
  • Visibility: 10 statute miles
  • Sky: broken clouds at 3,100 ft; scat at 2,500 ft
  • Temperature: 61°F (16°C), dew point 57°F (14°C)
  • Altimeter: 29.92 inHg
  • Observation at 8:53 am from BFI

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

9 documents, released by the NTSB on August 10, 2020. 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.