FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Cal-Ore Life Flight Piper PA-31T accident

29 Jul 2016 · McKinleyville, CA, United States

Piper PA-31T · Accident: fire/smoke (non-impact) en route

From Crescent City, CA to Oakland, CA

Report a problem

Event

NTSB case
WPR16FA153
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
4 · 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
Instrument Meteorological Cond

Piper PA-31T

Aircraft type
Piper PA-31
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
N661TC
Onboard fatalities
Unknown
Route
From Crescent City, CATo Oakland, CA
Aircraft age
About 35 years (built 1981)
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
En route · climb to cruise
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
Destroyed

Cause areas

  • Aircraft › Aircraft systems

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

About 13 minutes after takeoff for a medical transport flight, while climbing through about 14,900 ft mean sea level (msl), the pilot reported to air traffic control (ATC) that he was smelling smoke in the cockpit and would be returning to the originating airport. The flight was cleared to return with a descent at pilot's discretion to 9,000 ft msl. The pilot replied, "okay," and said that it looked like he was going to lose some power shortly. The pilot then stated that he had smoke in the cockpit, declared an emergency, and requested that ATC contact the fire department. About 1 minute 15 seconds after the initial report of smelling smoke, the pilot made the last radio transmission of the flight stating that he had three people on board.

The wreckage was located about 9 hours later in an area of brush and heavily forested terrain. Portions of the burned and fragmented wreckage were scattered along a debris path that measured about 2,400 ft in length, which is consistent with an inflight breakup. The center fuselage and cockpit areas were largely intact and displayed no evidence of fire; however, there was an area of thermal damage to the forward fuselage consistent with an inflight fire. The thermal damage was primarily limited to the floor area between the two forward seats near the main bus tie circuit breaker panel and extended to the forward edge of the wing spar. All exposed surfaces were heavily sooted. Some localized melting and thermal-related tearing of the aluminum structure was present. The primer paint on the floor panels under the right aft corner of the pilot seat and the left aft corner of the co-pilot seat was discolored dark brown. An aluminum stringer in this location exhibited broomstrawing indicating that the stringer material was heated to near its melting point prior to impact. A single wire located in the area exhibited notching consistent with mechanical rubbing.

The main bus tie circuit breakers were partially missing. The remaining breakers were heavily sooted on their aft ends, and one breaker was thermally discolored. Areas of charring were on the backside of the panel. Examination of the wiring in this area showed evidence of electrical arcing damage. Four hydraulic lines servicing the landing gear system were located in this area, and all the lines exhibited signs of thermal exposure with melting and missing sections of material.

Six exemplar airplanes of the same make and model as the accident airplane were examined, and instances of unsafe conditions in which electrical lines and hydraulic lines in the area of the main bus tie circuit breaker panel were in direct contact were found on all six airplanes. Some of the wires in the exemplar airplanes showed chafing between hydraulic lines and the electrical wires, which, if left uncorrected, could have led to electrical arcing and subsequent fire.

Based on the unsafe conditions found during examination of the exemplar airplanes and the thermal damage to the area near the main bus tie circuit breaker panel on the accident airplane, including broomstrawing of the aluminum structure, electrical arcing damage to the wiring, and melting of the hydraulic lines, it is likely that an electrical wire near the tie bus circuit breakers chafed on a hydraulic line and/or airplane structure, which resulted in arcing and a subsequent in-flight fire that was fed by the hydraulic fluid.

Probable cause

An inflight fire in the floor area near the main bus tie circuit breaker panel that resulted from chafing between an electrical wire and a hydraulic line and/or airplane structure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR16FA153
Event ID
20160729X31455
Case number
WPR16FA153
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, coordinates. 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: a860e2031dbb3bb52da907b9055d20cc36c8bad2ff9eec446c789cfb4f244dbc; retrieved 2026-09-14T21:57:15.821Z.