WPR11LA168 · Cessna TU206G
Civil Air Patrol Cessna TU206G · Accident: loss of engine power (total) on approach
From Pierce County-Thun Field (PLU) to Pierce County-Thun Field (PLU)
Event
- NTSB case
- WPR11LA168
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna TU206G
- Aircraft type
- Cessna 206
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N6169Z
- Operator
- Civil Air Patrol
- Onboard fatalities
- Unknown
- Route
- From Pierce County-Thun Field (PLU), Puyallup, WATo Pierce County-Thun Field (PLU), Puyallup, WA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11LA168
- Event ID
- 20110319X95407
- Case number
- WPR11LA168
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 3ca00ce941cfe7ee2e8b09939c470c5bf04133b9a12735c0aa9ce7070d1e1bf9; retrieved 2026-09-15T15:56:02.827Z.