FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12CA496 · Black Donald COZY III

29 Jul 2012 · Los Lunas, NM, United States

Black Donald COZY III · Accident: fire/smoke (non-impact) while taxiing

From Mid Valley Airpark (E98) to Mid Valley Airpark (E98)

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
CEN12CA496
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

Black Donald COZY III

Aircraft type
Black Donald COZY
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
N904DB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mid Valley Airpark (E98), Los Lunas, NMTo Mid Valley Airpark (E98), Los Lunas, NM
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
Taxi · from runway
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 power plant

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

NTSB narrative

While taxiing after landing, the engine lost power, and the pilot turned the airplane off the runway. The pilot exited the airplane and noticed smoke at the rear of the airplane near the engine. The pilot attempted to extinguish the fire; however, his efforts were unsuccessful, and the airplane was consumed by the fire. At the time of the accident, the airplane had accumulated 4.9 flight hours. Postaccident examination of the airplane found loose B-nuts on two fuel lines and one oil line. An oil streak was noted on the runway surface, and no oil was found in the engine. The pilot stated that the fire likely resulted from oil leaking onto the hot turbocharger.

Probable cause

A loose oil line, which allowed oil to leak onto the hot engine turbocharger and resulted in a fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12CA496
Event ID
20120731X40012
Case number
CEN12CA496
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: 1010973802be94dd7d5d0c68127fa21104b786d0107c63da0c37144b6b04f163; retrieved 2026-09-15T19:08:09.991Z.