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

Cessna TU206G accident near Puyallup, Washington, March 19, 2011

On March 19, 2011 at about 6:15 pm local time, a Cessna TU206G, registered N6169Z, was substantially damaged in an accident during approach (VFR pattern final) near Puyallup, Washington (Pierce County Airport - Thun). It was an instructional flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilots’ activation of the fuel boost pump while preparing to land, which was contrary to checklist procedures and resulted in a loss of engine power.

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

What the record shows

Date
March 19, 2011 · about 6:15 pm local time · cases in 2011
Place
Puyallup, Washington · Pierce County Airport - Thun · cases near this airport · map
Type
Accident
Injuries
2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna TU206G · all TU206Gs on the register
Registration
N6169Z · no longer on the register · serial U20606172
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

The airplane was on the downwind leg of the traffic pattern during an instructional flight, and the pilots performed the prelanding checklist, switched the fuel selector to the right tank position, and activated the fuel boost pump. According to the flight instructor, the airplane “began sinking” while on final approach for the runway. When the pilots tried to add engine power, the engine did not respond, and the airplane collided with terrain short of the runway. The manufacturer’s approved checklist for the airplane indicates that the auxiliary fuel boost pump should be in the off position before landing. A representative from the engine manufacturer reported that operating the auxiliary fuel boost pump at a low engine power setting would “flood” the engine and result in a loss of engine power. It is likely that when the pilots applied power, the engine was flooded, which resulted in the total loss of engine power. Postaccident examination of the airframe and engine revealed no preaccident mechanical malfunctions or failures that would have precluded engine operations.

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. Loss of engine power (total) during approach (VFR pattern final) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Aircraft systems › Fuel system › Fuel pumps › Unneccessary use/operation other cases naming the fuel system
  • cause Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 458 hours in all; 4 in this make and model; 102 in the last 90 days
  • Last flight review: September 2, 2010
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Flight instructor

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instructor: glider; instructor: instrument airplane; instrument: airplane; rotorcraft: glider
  • Flight time: 1,800 hours in all; 55 in this make and model; 20 in the last 90 days; 10 in the last 30 days; 1,740 as pilot in command; 400 on instruments
  • Last flight review: May 17, 2009
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: rgt
  • Injury: minor injuries

The aircraft

  • Last inspection: 100-hour inspection, August 30, 2010; 4,308 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine: Cont Motor TSIO-520 SER (piston); 0 hours total
  • Operator: Civil Air Patrol

The flight

  • Departed from: PLU Puyallup WA at 5:00 pm
  • Destination: PLU Puyallup WA
  • Runway 34, 3,650 ft by 60 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: broken clouds at 5,000 ft
  • Temperature: 50°F (10°C), dew point 0°F (-18°C)
  • Observation at 4:45 pm from PLU

Injuries

FatalSeriousMinorNone
Flight crew2

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

6 documents, released by the NTSB on June 16, 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.

Other NTSB records under N6169Z the same tail number, which may have belonged to a different aircraft at the time

1982-10-07DEN83LA003 · accident near Rock Springs, WY · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/WPR11LA168.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.