# Accident 19900116000959A: Cessna 172M, Danbury, CT, January 16, 1990

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 16, 1990, 15:15 local time
- Place: Danbury, CT
- Airport: Danbury Municipal
- Damage: Destroyed
- Phase of flight: Starting Engines
- Operating rules: General operating rules (Part 91)
- Location: 41.3715° N, 73.4822° W: Placed by OpenAirDocs at DANBURY MUNI (DXR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.3715&lon=-73.4822&mi=10
- Aircraft: N9093H, a cancelled registration (https://openairdocs.org/deregistered/N9093H-1992-07-08) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYC O320H2AD
- Fatal injuries: 0
- Pilot flight hours: 425 total, 60 in this make and model, 20 in the last 90 days
- NTSB investigation: [NTSB NYC90LA056](https://openairdocs.org/ntsb/NYC90LA056) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19900116000959A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

FIRE ERUPTED STARTING ENGINE. FAILED TO NOTE LOOSE COWLING. NO AIR FILTER. FUEL LINE NOT CAPPED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC90LA056](https://openairdocs.org/ntsb/NYC90LA056), Jan 16, 1990: Cessna 172 (N9093H), Danbury, CT, destroyed. Probable cause: IMPROPER MAINTENANCE, INADEQUATE SURVEILLANCE BY THE COMPANY/OPERATOR, AND INADEQUATE PREFLIGHT BY THE PILOT, WHICH RESULTED IN A FIRE DURING AN ATTEMPTED ENGINE START. A FACTOR RELATED TO THE…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.