FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN93FA066 · Cessna 310J

5 Jun 1993 · Broomfield, CO, United States

Cessna 310J · Accident: fire while standing

Report a problem

Event

NTSB case
DEN93FA066
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
0
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 310J

Aircraft type
Cessna 310
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
N3005L
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
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
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, oil › Contamination
  • Other maintenance personnel › Maintenance, service of aircraft/equipment, improper
  • Oxygen system › Leak

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

NTSB narrative

THE PILOT-IN-COMMAND AND INSTRUCTOR-TRAINEE WERE SITTING IN THE COCKPIT DISCUSSING THE LESSON PLAN. THEY SAW FIRE AROUND THE GLARESHIELD AND WINDSHIELD. POST-ACCIDENT INVESTIGATION TRACED THE FIRE PATTERN BACK TO THE NOSEWHEEL WELL AND THE OXYGEN SYSTEM BOTTLE. IT WAS LEARNED THAT THE REGULATOR HAD BEEN LEAKING AND THE ON-OFF CONTROL CABLE WAS BINDING. THE LEAK WAS THOUGHT TO HAVE BEEN FIXED. A MECHANIC SAID HE LUBRICATED THE COCKPIT END OF THE REGULATOR CONTROL. THE AIRCRAFT OWNER SAID THE MECHANIC USED AN AEROSOL CAN TO LUBRICATE SOMETHING IN THE NOSEWHEEL WELL. ACCORDING TO THE FIRE DEPARTMENT'S ARSON SQUAD, THE CAUSE OF THE FIRE WAS 'FRICTION OF ESCAPING OXYGEN IGNITING LUBRICANT ON CABLE.'

Probable cause

FRICTION OF ESCAPING OXYGEN UNDER HIGH PRESSURE IGNITING A LUBRICANT IN THE NOSEWHEEL WELL AREA, AND IMPROPER AIRCRAFT SERVICING BY MAINTENANCE PERSONNEL.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN93FA066
Event ID
20001211X12595
Case number
DEN93FA066
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. 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: a2622b12dc5b9512d615891eb7d5e44a1bdcca7174a1ce4c9f34cafbf5271756; retrieved 2026-09-21T22:56:08.179Z.