FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX01FA160 · Bellanca 14-19

30 Apr 2001 · Casa Grande, AZ, United States

Bellanca 14-19 · Accident: fire/explosion during landing

From Chandler Municipal Airport (CHD) to an unrecorded destination

Report a problem

Event

NTSB case
LAX01FA160
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
1 · 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

Bellanca 14-19

Aircraft type
Bellanca 14
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
N521A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chandler Municipal Airport (CHD), Chandler, AZTo not recorded
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
Landing · landing roll
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/explosion
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

  • Fluid, fuel › Leak
  • Fuselage, crew compartment › Exploded
  • Fuselage, firewall › Fire

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

NTSB narrative

The airplane was making a precautionary landing due to a fluid leak (most likely fuel) in the cockpit and had an explosive flash fire in the cabin during the landing roll. The pilot stated that a clear fluid was running down the cabin side of the firewall from an area right of center. The right seat passenger reported that the leak appeared to be coming from behind the instrument panel directly in front of her position. The pilot then pulled back the power slowly and headed for the closest airport. A passenger and the ground witnesses described the touchdown and rollout as normal until an explosion occurred, which filled the cabin with flames and blew the entry door off the right side of the airplane. Witnesses on the ground reported seeing flames coming out of the front-bottom of the aircraft before hearing a "pop" in conjunction with the explosion inside the cockpit. The fabric-over-tubular-steel-frame airframe was thermally destroyed except for the steel components. An examination of the thermal damage patterns disclosed that the most extensive thermal damage appeared to be forward of the right front seat where the passenger reported the fluid leak. Also parts of the metal frame were severely warped, especially on the lower right-hand side near the firewall and below where the instrument panel would be. In addition the bottom braces of the engine mount were warped due thermal damage. Furthermore, there was sooting and heat resultant discoloration on the firewall in the engine compartment. On the topside and on the right-hand side of the firewall red and black discoloration without sooting was evident. The color on the right side of the firewall was a mixture of black and tan, with a little red. On the bottom part of the firewall there was minimal sooting and a tan color. The only flammable fluid lines on the right quadrant of the firewall are the pressure measurement lines for fuel, engine oil, and hydraulics. These Mil-6000 hose lines are connected to firewall and pass-through fittings, that are located almost directly in front of the right seat passenger's location on the upper part of the firewall. On the cabin side of the firewall, three other Mil-6000 hoses connect these fittings to a "3-in-1" instrument panel gage that displays the operating pressure of these three systems. No evidence was found in the maintenance records that these fuel lines had ever been replaced. While the fuel related components (i.e. carburetor, fuel pump, and associated lines) attached to the engine were thermally damaged, the degree of damage was significantly less than the fuel components attached to the firewall. The thermal damage and sooting patterns indicate that an accelerant based fire originated on both sides of the firewall near the bottom.

Probable cause

A fuel leak on the cabin and engine sides of the firewall with a probable origin at the firewall pass-through fitting for the fuel pressure gage line. The fire likely began on the engine side of the firewall near the bottom with the explosive ignition of the pooled fuel/vapors in the cockpit after burn through penetration of the fuselage fabric skin on the bottom aft side of the firewall. Further refinement of the leak source between the pass-through fitting and the lines/connectors could not be established due to thermal destruction of the components.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX01FA160
Event ID
20010518X00957
Case number
LAX01FA160
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-05-01.
  • API snapshot SHA-256: 30b4098a7758bc50f869a949b0050bd3e034b50a54bfc4bf75f25812234ae3a0; retrieved 2026-09-20T20:34:31.385Z.