# NTSB investigations, 2004: Fire

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB ANC05IA020](https://openairdocs.org/ntsb/ANC05IA020.md): Boeing 747-123 · Anchorage, AK · Incident · No injuries · Incident investigation · Final report · Dec 29, 2004 · N858FT · Minor damage
  > The failure of a high-pressure fuel line fitting, which resulted in an engine fire during takeoff/initial climb.
- [NTSB ATL05IA025](https://openairdocs.org/ntsb/ATL05IA025.md): Cirrus Design SR22 · Peachtree City, GA · Incident · No injuries · Incident investigation · Final report · Nov 16, 2004 · N723CD · Minor damage
  > The failure of maintenance personnel to properly torque a fuel line fitting, which resulted in a fuel leak and in-flight engine fire.
- [NTSB IAD05LA005](https://openairdocs.org/ntsb/IAD05LA005.md): Beech C24R · Hyannis, MA · Accident · No injuries · Limited investigation · Final report · Oct 15, 2004 · N6598C · Substantial damage
  > The mechanic's failure to secure the fuel pressure line to the fuel pressure gauge fitting, which resulted in an engine compartment fire and a subsequent loss of engine power.
- [NTSB ANC05LA003](https://openairdocs.org/ntsb/ANC05LA003.md): Scan 30 · Anchorage, AK · Accident · No injuries · Limited investigation · Final report · Oct 9, 2004 · N701Q · Substantial damage
  > An in-flight fire during cruise flight for an undetermined reason.
- [NTSB LAX04LA334](https://openairdocs.org/ntsb/LAX04LA334.md): British Aerospace BAE 125-1000A · San Francisco, CA · Accident · No injuries · Limited investigation · Final report · Sep 11, 2004 · N520QS · Substantial damage
  > An electrical arc from an undetermined source initiated a hydraulic line rupture, which resulted in an equipment bay fire.
- [NTSB ANC04LA104](https://openairdocs.org/ntsb/ANC04LA104.md): Piper PA-18-150 · Cantwell, AK · Accident · Minor injuries · Limited investigation · Final report · Sep 4, 2004 · N9796P · Destroyed
  > An in-flight fire for an undetermined reason, which resulted in an off-airport forced landing and subsequent destruction of the airplane by fire.
- [NTSB CHI04LA295](https://openairdocs.org/ntsb/CHI04LA295.md): Aero Commander Callair A-9B · Norton, KS · Accident · Serious injuries · Limited investigation · Final report · Jul 16, 2004 · N7798V · Substantial damage
  > The fire in the area of the fuel line and the unsuitable terrain encountered during an emergency landing by the pilot. Contributing factors were the pole.
- [NTSB ATL04LA153](https://openairdocs.org/ntsb/ATL04LA153.md): Convair Div. of Gen. Dynamics 440 · Beef Island · Accident · 1 fatal · Limited investigation · Final report · Jul 12, 2004 · N4826C · Substantial damage
  > The in-flight fire on the number two engine, for undetermined reasons.
- [NTSB FTW04LA142](https://openairdocs.org/ntsb/FTW04LA142.md): Piper PA-34-200T · Cleveland, TX · Accident · Minor injuries · Limited investigation · Final report · May 27, 2004 · N2948S · Destroyed
  > The in-flight fire that resulted from an electrical arc in the main battery cable near the main power bus. The cause of the arcing event could not be determined.
- [NTSB FTW04IA104](https://openairdocs.org/ntsb/FTW04IA104.md): Cessna 414 · Midland, TX · Incident · No injuries · Incident investigation · Final report · Mar 19, 2004 · N414FB · Minor damage
  > The in-flight wing fire for undetermined reasons.
- [NTSB CHI04LA078](https://openairdocs.org/ntsb/CHI04LA078.md): Cessna R182 · Elberfeld, IN · Accident · No injuries · Limited investigation · Final report · Feb 25, 2004 · N5450T · Destroyed
  > The in-flight and on-ground fires in the cabin and engine compartment for undetermined reasons during the flight's cruise and emergency landing.
- [NTSB NYC04LA060](https://openairdocs.org/ntsb/NYC04LA060.md): Stinson 108-3 · Sanford, ME · Accident · No injuries · Limited investigation · Final report · Jan 25, 2004 · N6234M · Destroyed
  > An engine fire for undetermined reasons during start-up.

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE year(c."eventDate") = 2004
  AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 171)
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?occurrence=171&year=2004

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.