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

Piper PA 28-140 accident near Brinnon, Washington, September 30, 2017

On September 30, 2017 at about 5:13 am local time, a 1967 Piper PA 28-140, registered N9549W, was destroyed in an accident during enroute (cruise) near Brinnon, Washington. It was an instructional flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was conditions the NTSB did not record.

The NTSB's probable cause their words, unchanged

The flight instructor's failure to completely and properly evaluate the student pilot's incorrectly- planned flight, and his failure to use all available resources to maintain situation awareness during the flight, which resulted in controlled flight into terrain.

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

What the record shows

Date
September 30, 2017 · about 5:13 am local time
Place
Brinnon, Washington · map
Type
Accident
Injuries
1 person was killed and 1 person was seriously injured.
Weather
conditions the NTSB did not record
Aircraft
Piper PA 28-140 140, built 1967 · all PA 28-140s on the register
Registration
N9549W · no longer on the register · serial 28-22981
Damage
Destroyed
Flight
Instructional flight · general aviation rules (Part 91)

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

The flight instructor and student pilot were conducting the student's first night flight: a cross-country visual flight rules flight to two other airports which concluded with a return to their home airport. Review of the student's flight planning documents, which included the penciled flight route on a Sectional Aeronautical chart and a hand-filled paper flight planning form, revealed that the student had planned to conduct the entire flight at an altitude of 3,500 ft msl. The student's plotted course for the last leg of the flight, which was drawn directly from the departure airport to the destination, passed over a peak with a charted elevation of 3,440 ft. While in the airplane, and prior to engine start, the student and instructor reviewed the planned flight and current weather. The first leg was flown using air traffic control (ATC) flight following services. This northeast-bound leg was flown at 4,500 ft, an altitude that was contrary to the FAA hemispheric rule (easterly flights should be flown at odd-thousand ft altitudes and westerly flights should be flown at even-thousand ft altitudes); ATC did not assign or question this altitude selection. The second leg was westbound and did not use ATC flight-following; the leg was flown at 3,500 ft, again contrary to the FAA hemispheric rule. The final, southbound accident leg was also flown at 3,500 ft; this altitude selection was erroneous for two reasons. First, it was contrary to the hemispheric rule, but more significantly, the student pilot's plotted course line on the Sectional chart passed directly over a peak that was charted as having an elevation of 3,440 ft. The airplane impacted the terrain immediately prior to that peak at an elevation about 3,075 ft mean sea level (msl). Examination of the airplane and engine did not reveal any pre-impact mechanical deficiencies or failures that would have precluded continued normal operation. Review of flight track and data from onboard personal electronic devices (PEDs) was consistent with a controlled flight into terrain (CFIT) event. Further review of the flight planning form showed an airport listed as a waypoint for the accident leg; the airport was located just east of the direct route between the departure and destination. If the pilots had chosen to navigate first toward this airport then to the destination rather than flying direct, the flight would have avoided the mountainous terrain. Additionally, the student's planned altitudes did not comply with Federal Aviation Administration regulations regarding cruise flight altitudes. The investigation was unable to determine why neither the student nor the flight instructor detected the erroneous planned and flown altitude. Although the student's work schedule in the days leading up to the accident may have been conducive to the development of fatigue and, subsequently, his error in planning, there was insufficient evidence to determine the presence or role of fatigue. Further, as pilot-in-command, the instructor should have reviewed the flight planning documents and detected these errors. Both the student pilot and the flight instructor owned multiple portable electronic devices (PEDs) equipped with flight planning and operating software capable of displaying geo-referenced flight and terrain information. As part of his training regimen, the flight instructor did not let the student use any PEDs during flight; however, the student stated that the flight instructor would typically use his PEDs to monitor or augment the flight while they were airborne. Whether the flight instructor was using his PEDs during the accident flight could not be determined; however, he had sufficient time, tools, and knowledge to detect the flight's improper altitude and proximity to terrain with or without the use of PEDs, and why he failed to do so and instead allowed the flight to remain on that track at that altitude could not be determined.   CFIT prevention is primarily dependent on pilots' complete and accurate situational awareness, which can be aided by many safety tools and measures. Despite the fact that the flight instructor held the knowledge, tools, and responsibility to ensure proper and safe conduct of the flight, particularly with regard to appropriate altitude selection, the circumstances of the accident indicate that neither he nor the student possessed complete and accurate situational awareness, most critically for the accident leg, which resulted in the CFIT event.

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. Preflight or dispatch event during prior to flight
  2. Controlled flight into terrain or object (CFIT) during enroute (cruise) defining event

The NTSB's findings

  • cause Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Instructor/check pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Instructor/check pilot
  • cause Personnel issues › Task performance › Use of equip/info › Use of available resources › Instructor/check pilot
  • cause Personnel issues › Psychological › Perception/orientation/illusion › Situational awareness › Instructor/check pilot
  • Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Student/instructed pilot
  • cause Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation

Dual student

  • Certificate: student
  • Flight time: 44 hours in all; 43 in this make and model
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

Flight instructor

  • Certificate: airline transport pilot, flight instructor
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 27,000 hours in all
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 5,495 hours
  • Last inspection: annual inspection, September 17, 2017; 34 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 6,807 hours total

The flight

  • Departed from: 0S9 Port Townsend WA at 4:59 am
  • Destination: SHN Shelton WA
  • Flight plan: none
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 140° at 5 knots
  • Visibility: 9 statute miles
  • Sky: overcast at 4,200 ft; a few clouds at 3,600 ft
  • Temperature: 55°F (13°C), dew point 52°F (11°C)
  • Altimeter: 30.04 inHg
  • Observation at 4:55 am from 0S9, 18 miles away

Injuries

FatalSeriousMinorNone
Flight crew11

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

24 documents, released by the NTSB on October 30, 2019. 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.