# Accident 20041010035199A: Cessna 172N, Clermont, NY, October 10, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 10, 2004, 00:34 local time
- Place: Clermont, NY
- Damage: Destroyed
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 42.1183° N, 73.8408° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=42.1183&lon=-73.8408&mi=10
- Aircraft: N2771J, a cancelled registration (https://openairdocs.org/deregistered/N2771J-2007-02-05) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- People aboard: 2
- Fatal injuries: 2
- Pilot flight hours: 1,231 total
- NTSB investigation: [NTSB NYC05FA001](https://openairdocs.org/ntsb/NYC05FA001) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20041010035199A

## Narrative

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

(-23) AIRCRAFT WAS TRAVELING FROM FARMINGDALE, NY TO JOHNSTOWN, NY. WHILE ENROUTE, THE PILOT ENCOUNTERED IMC CONDITIONS OVER GERMANTOWN, NY JUST AFTER MIDNIGHT. THE PILOT EXECUTED A DESCENDING RIGHT HAND 180 DEGREE TURN, BROKE OUT OF THE CLOUDS, FOLLOWED BY A SHARP DESCENDING LEFT HAND TURN AND CRASHED IN A FIELD FATALLY INJURING THE PILOT AND PASSENGER.

## 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 NYC05FA001](https://openairdocs.org/ntsb/NYC05FA001), Oct 10, 2004: Cessna 172N (N2771J), Germantown, NY, substantial damage, 2 fatal. Probable cause: The pilot's inadequate in-flight planning/decision which led to VFR flight into IMC and his loss of aircraft control. Factors were night and cloud conditions.

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.
