FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11FA383 · Boeing B-17G

13 Jun 2011 · Oswego, IL, United States

Liberty Foundation Boeing B-17G · Accident: fire/smoke (non-impact) during initial climb

From Aurora Municipal Airport (ARR) to Indianapolis Regional Airport (MQJ)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN11FA383
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
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

Boeing B-17G

Aircraft type
Boeing B-17
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
N390TH
Onboard fatalities
Unknown
Route
From Aurora Municipal Airport (ARR), Aurora, ILTo Indianapolis Regional Airport (MQJ), Indianapolis, IN
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
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
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
Substantial Possible conflict

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

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

NTSB narrative

The weekend before the accident, a fuel leak was identified. The fuel leak was subsequently repaired, and a final inspection the morning of the accident flight reportedly did not reveal any evidence of a continued fuel leak. Shortly after takeoff, the flight crew noticed a faint odor in the cockpit and a small amount of smoke near the radio room. The flight crew immediately initiated a turn with the intention of returning to the departure airport. About that time, they received a radio call from the pilot of the accompanying airplane advising that there was a fire visible on the left wing. The accident pilot subsequently executed an emergency landing to a corn field. Emergency crews were hampered by the muddy field conditions, and the fire ultimately consumed significant portions airframe.

In-flight photographs showed the presence of fire on the aft lower portion of the left wing between the inboard and outboard engines. Located in the same area of the fire were fuel tanks feeding the left-side engines. After landing, heavy fire conditions were present on the left side of the airplane, and the fire spread to the fuselage.

A postaccident examination noted that the C-channel installed as part of the No. 1 main fuel tank repair earlier in the week was partially separated. During the examination, the tank was filled with a small amount of water, which then leaked from the aft section of the repair area in the vicinity of the partially separated channel. Metallurgical examination of the repair area revealed a longitudinal fatigue crack along the weld seam.

The fatigue nature of the crack was consistent with a progressive failure along the fuel tank seam that existed before the accident flight and was separate from the damage sustained in the emergency landing and postlanding fire. The repair earlier in the week attempted to seal the leak but did not address the existing crack itself. In fact, the length of the crack observed at the time of the repair was about one-half the length of the crack noted during the postaccident examination, suggesting that the crack progressed rapidly during the course of the accident flight. Because the repaired fuel tank was positioned within the open wing structure, a fuel leak of significant volume would have readily vaporized, producing a flammable fuel vapor/air mixture. Although the exact ignition source could not be determined due to the fire damage, it is likely that the fuel vapor and liquid fuel encountered hot surfaces from nearby engine components, which initiated the in-flight fire.

Probable cause

An inadequate repair of the fuel tank that allowed the fuel leak to continue, ultimately resulting in an in-flight fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11FA383
Event ID
20110613X14032
Case number
CEN11FA383
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: 43179d3c95e2666368dc1c2adda5d0b487e4b9e16d4eed2ee6f19a576b46729e; retrieved 2026-09-15T16:16:37.754Z.