NYC84FNE05 · Mooney M20C
Mooney M20C · Accident: fire en route
From Danbury Municipal Airport (DXR) to Igor I Sikorsky Memorial Airport (BDR)
Event
- NTSB case
- NYC84FNE05
- 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
Mooney M20C
- Aircraft type
- Mooney M20
- 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
- N74558
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR), Danbury, CTTo Igor I Sikorsky Memorial Airport (BDR), Bridgeport, CT
- 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
- En route · climb to cruise
- 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
- Exhaust system › Brittle fracture
- Exhaust system › Deteriorated
- Exhaust system › Leak
- Fuel system, line › Burned
Approximate · Estimated position: the centre of Danbury, CT, the place the record names. Not the accident site.
NTSB narrative
AN ENG COMPARTMENT FIRE OCCURRED SHORTLY AFTER TAKEOFF & SMOKE ENTERED THE COCKPIT. THE PLT THEN MADE A FORCED LANDING IN A SAND PIT APRX 1 MI FM THE ARPT. HE & THE PAX EXITED THE ACFT WITH SERIOUS BURNS. AN INV REVEALED AN EXHAUST PIPE HAD FAILED AT A PRE-EXISTING CRACK NEAR FUEL SUPPLY LINES. THE EXHAUST PIPE HAD BEEN PREVIOUSLY WELDED, BUT THE FAILURE WAS UNRELATED TO THE WELD REPAIR. THERE WAS EVIDENCE THE FUEL LINES WERE BURNED BY ESCAPING EXHAUST GASES WHICH RESULTEDIN THE FIRE. DRG AN ANNUAL INSPN ON 12/21/82, EXHAUST SYS CRACKS WERE WELDED & THE MECHANIC RETURNED THE ACFT TO SERVICEAS AIRWORTHY, BUT RECOMMENDED THE EXHAUST SYS BE REPLACED. NO CRACKS WERE FND DRG A SUBSEQUENT ANNUAL INSPN ON 2/2/84 AT A TOTAL AIRFRAME TIME OF 3316 HRS & AN ENG TIME OF 1754 HRS. THE FLT TIME FROM THE LAST INSPN TO THE TIME OF THE ACDNT WAS NOT DETERMINED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC84FNE05
- Event ID
- 20001214X40862
- Case number
- NYC84FNE05
- 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: 8d056add24cb706cc1119820c29cfca143b0b4b3cd41295dcd841c24b9bf2ec6; retrieved 2026-09-21T17:29:39.651Z.