# Accident 19950628019919A: Cessna 172M, Danbury, CT, June 28, 1995

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 28, 1995, 15:51 local time
- Place: Danbury, CT
- Airport: Danbury Municipal
- Damage: Substantial damage
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 41.5106° N, 73.4289° W: Placed by OpenAirDocs from the FAA’s distance and direction from , within about 3 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.5106&lon=-73.4289&mi=10
- Aircraft: N9176H, registered now (https://openairdocs.org/aircraft/N9176H) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYC O320E2D
- People aboard: 2
- Fatal injuries: 0
- NTSB investigation: [NTSB NYC95LA135](https://openairdocs.org/ntsb/NYC95LA135) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19950628019919A

## Narrative

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

BIENNIAL FLIGHT REVIEW CFI SIMULATED ENGINE OUT. MADE A FIELD DURING GO AROUND NO POWER. POSSIBLE ENGINE OVERBOOST.

## 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 NYC95LA135](https://openairdocs.org/ntsb/NYC95LA135), Jun 28, 1995: Cessna 172M (N9176H), Bridgewater, CT, substantial damage. Probable cause: the loss of engine power for undetermined reasons resulting in a forced landing, and a subsequent collision with trees.

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.