FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Ameriflight Piper PA-31-350 accident

14 Oct 2008 · Portland, OR, United States

Piper PA-31-350 · Accident: powerplant system/component malfunction/failure during initial climb

From Portland International Airport (PDX) to Eastern Oregon Regional Airport at Pendleton (PDT)

Report a problem

Event

NTSB case
WPR09LA013
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
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-31-350

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
N3BT
Operator
Ameriflight
Onboard fatalities
Unknown
Route
From Portland International Airport (PDX), Portland, ORTo Eastern Oregon Regional Airport at Pendleton (PDT), Pendleton, OR
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 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
Initial climb
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
Powerplant system/component malfunction/failure
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 power plant

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

NTSB narrative

The pilot reported that shortly after departure, and about 1,000 feet above ground level, she noticed that the left engine’s manifold pressure dropped about 6 inches below the right engine’s indications. The engine was surging, and she thought that the turbocharger had stopped operating. The left cylinder head temperature was reading 0 degrees, but all other gauges were normal. No smoke or flames were noticed as the pilot returned to the airport for landing without declaring an emergency or shutting down the engine. During taxi to the ramp, the engine lost power. Postflight examination revealed a broken exhaust pipe on the right side of the exhaust system, with evidence of a fire in the accessory section and a burned-through section of skin. Metallurgical examination disclosed that the aft exhaust pipe flange had cracked and fractured due to fatigue. Dimensional measurements of the flange wall thickness were within design limits. The hardness was as expected for the specified type 321 steel, indicating that bending stresses acting on the flange exceeded its design capability. The cracking occurred due to excessive stresses that developed from thermal expansion of the exhaust line and insufficient sliding action at the slip joints within the exhaust pipe system. Bending of the flange and subsequent fatigue cracking indicated that the slip joints had likely not been working properly for some time.

Probable cause

An in-flight engine fire due to the fatigue fracture of an exhaust pipe that resulted from a failure of the pipe's slip joint.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA013
Event ID
20081015X60032
Case number
WPR09LA013
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: 04b4967c394e180409aac6b62f9be0d276528aeb269ab566787e01e3959c1c92; retrieved 2026-09-15T10:28:14.192Z.