IAD02LA013 · Cessna 172S
Cessna 172S · Accident: fire/explosion while standing
From Leesburg Executive Airport (JYO) to Montgomery County Airpark (GAI)
Event
- NTSB case
- IAD02LA013
- 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
Cessna 172S
- Aircraft type
- Cessna 172
- 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
- N346ME
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Leesburg Executive Airport (JYO), Manassas, VATo Montgomery County Airpark (GAI), Gaithersburg
- 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) not operating
- 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
- Pilot in command › Security of cargo, improper
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 loaded with fishing and camping gear, and 15 gallons of 100LL aviation gasoline, in four, five-gallon fuel cans. The fuel cans and the gear were secured under a cargo net in the airplane 2 days prior to the accident. The pilot completed his preflight inspection with no anomalies noted, and checked the security of the cargo in the back of the airplane. There was no evidence of fuel spillage and no odor of fuel in the cabin. The pilot started the engine and taxied to the run-up area at the approach end of a runway, then applied the parking brake, and started the takeoff checklist. During the checklist, there was an "overwhelming fuel smell." The pilot shut down the engine with the mixture but left the master switch and the lights on. He looked for fuel on the floor of the cabin, but I couldn't see any. The pilot deplaned, and was about to close the door when the cabin exploded.
Probable cause
The pilot's improper stowage of hazardous material.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD02LA013
- Event ID
- 20011203X02332
- Case number
- IAD02LA013
- 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: 37248c1e1875edeb5461597ec0447b5bd11aa2eb0082c1e401d3b800b39b16ae; retrieved 2026-09-21T09:44:05.116Z.