FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

King Air Piper PA 28-181 incident

14 May 2014 · South Naknek, AK, United States

Piper PA 28-181 · Incident: fire/smoke (non-impact) while taxiing

From South Naknek Number 2 Airport (WSN) to Naknek, AK

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC14IA028
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
Incident
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
Charter & commuter
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

Piper PA 28-181

Aircraft type
Piper PA-28
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
N30541
Operator
King Air
Onboard fatalities
Unknown
Route
From South Naknek Number 2 Airport (WSN), South Naknek, AKTo Naknek, AK
Aircraft age
About 36 years (built 1978)
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 135: Air Taxi & Commuter
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
Taxi · to runway
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
Fire/smoke (non-impact)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None Possible conflict

Cause areas

  • Not determined › Not determined

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he was taxiing the airplane for departure when he and his passengers smelled smoke in the cabin. He shut the engine down, and he and the passengers then evacuated the airplane. After escorting the passengers to a safe location, he saw smoke coming from the engine cowling area and attempted to put out any fire with a fire extinguisher; however, his attempt to put out the fire was unsuccessful, and the fire continued to burn a majority of the fuselage. Due to extensive fire damage, the initiation source of the fire could not be determined.

Probable cause

A fire in the airplane’s engine compartment that initiated for reasons that could not be determined due to extensive fire damage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC14IA028
Event ID
20140520X62400
Case number
ANC14IA028
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, damage. 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: a3afc41aa7b801517d0f7fd8e99353b42127c60552017b000c4474559591eaf4; retrieved 2026-09-15T23:38:25.590Z.