FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA357 · Beech 58 TC

11 Jul 2010 · LaGrange, GA, United States

Beech 58 TC · Accident: explosion (non-impact) while standing

From LaGrange Callaway Airport (LGC) to Savannah Hilton Head International Airport (SAV)

Report a problem

Event

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

Beech 58 TC

Aircraft type
Beechcraft 58
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
N405RW
Operator
Unknown
Onboard fatalities
Unknown
Route
From LaGrange Callaway Airport (LGC), LaGrange, GATo Savannah Hilton Head International Airport (SAV), Savannah, GA
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
Standing · engine(s) start-up
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
Explosion (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

Cause areas

  • Personnel issues › Action/decision

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 had just been fueled by the lineman at the fixed-base operator (FBO), who secured the fuel caps after the service. During the climb after takeoff, the right-wing fuel cap came off of the wing, remaining attached only by the chain. An estimated 11 gallons of fuel was siphoned from the wing before the pilot returned to the airport and taxied back to the FBO. The pilot secured the cap and conducted a visual inspection of the right wing, before attempting to start the engine again. The right engine backfired, followed by a loud bang and whoosh sound; flames then rose from the right wing. A postaccident examination of the right wing revealed that the internal blast was a result of the backfire igniting fuel vapors that remained after the siphoning. The blast caused the upper wing skin to expand and separate from the retaining rivets. A soot trail originated at the exhaust pipes and traveled in an aft direction to the trailing edge of the wing.

Examination of the fuel cap revealed that the outer o-ring was dry and cracked, a washer was missing, the cap leaked under pressure, and that the force required to secure the cap exceeded the manufacturer’s specification. The airplane’s maintenance records did not indicate the last time the fuel cap was overhauled. Fuel cap maintenance is permissible by a Federal Aviation Administration (FAA) certified airframe mechanic or by an FAA-approved overhaul facility. While the cap’s manufacturer has standards on the required forces to secure the fuel cap lock tab and a leak testing process, the airplane’s maintenance manual does not mention either.

As a result of separate investigations, the airplane’s manufacturer has included in applicable airplanes’ maintenance manuals the following verbiage: “Note: Inspect the fuel filler cap outer o-ring for flexibility, splits cracks or distortion. If the o-ring is damaged in any way replace or overhaul the fuel cap.”

Probable cause

The pilot not allowing sufficient time for fuel spill vapors to dissipate before starting the engine. Contributing to the accident was the inadequate maintenance of the fuel cap.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA357
Event ID
20100713X43713
Case number
ERA10LA357
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, 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: 237dc8da7a31a47b230b30cf6697652c76b08a7647ce799284a1e25aa0cd73e5; retrieved 2026-09-15T14:41:29.543Z.