FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04FA001 · Piper PA-32R-301T

1 Oct 2003 · Corona, CA, United States

Piper PA-32R-301T · Accident: fire en route

From Corona Municipal Airport (AJO) to Oakland San Francisco Bay Airport (OAK)

Report a problem

Event

NTSB case
LAX04FA001
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
2 · 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

Piper PA-32R-301T

Aircraft type
Piper PA-32
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
N481CA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Corona Municipal Airport (AJO), Corona, CATo Oakland San Francisco Bay Airport (OAK), Oakland, CA
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
En route · climb to cruise
First occurrenceThe 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
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

  • Exhaust system, clamp › Fatigue
  • Exhaust system, clamp › Separation

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Shortly after takeoff the pilot contacted air traffic controllers and declared an emergency due to an in-flight fire. An airborne witness in another aircraft reported seeing the accident airplane in level flight with black smoke emanating from it. The airborne witness then reported seeing the airplane bank to the left and enter a nose down spiral towards the ground. The airplane impacted flat level terrain in a steep nose down attitude and the post-impact fire consumed the majority of the airplane. The flight was airborne for about 4 minutes before it crashed. The on-scene and detailed post recovery examinations revealed evidence consistent with an in-flight fire in the lower aft engine compartment area in proximity to the turbocharger and the adjacent firewall. Evidence on the nose landing gear strut cylinder suggests that temperatures in this area exceeded the melting point of aluminum while the airplane was in flight. During the engine examination investigators noted that the tension ring of the turbocharger exhaust clamp that retains the exhaust duct to the turbine side of the turbocharger had fractured at the 11 o'clock position. The exhaust clamp bolt remained connected and properly safetied. With this clamp broken and the exhaust ducting loose, hot exhaust gasses would have been directed against the lower firewall. The examination of the turbocharger exhaust clamp showed a high temperature creep/stress rupture that initiated from a crack at one of the resistance welds that joins the sheet metal retainers to the tension ring. The turbocharger gases are approximately 1,200 to 1,500 degrees Fahrenheit, and the tension ring fracture surface showed intergranular brittle fracture across approximately 80-percent of the cross-sectional area initiating at the resistance weld. The heavily oxidized resistance weld region, when compared to the lighter oxidized sheet metal, suggested that the weld crack was pre-existing. A review of past historical Safety Board data revealed three other accidents, FTW98FA325, FTW99LA241, and CHI02FA042, with similar fractures of exhaust clamps, and other referenced data showed that Inconel 718 could crack in an intergranular mode in a time-dependent creep/stress rupture mode in this temperature range. Cockpit/cabin material that showed exposure to fire was found in the wreckage debris field away from any areas affected by the ground fire.

Probable cause

failure of the turbocharger exhaust clamp due to a pre-existing weld crack, which allowed the release of high temperature exhaust gasses in the engine compartment, causing an in-flight fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04FA001
Event ID
20031015X01737
Case number
LAX04FA001
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 171108fd51e96a0f5726a7699ae6e710667c41f92c4cb81c470295692211be62; retrieved 2026-09-20T18:55:38.262Z.