# Incident 20020124002589I: Cessna 550, Penn Yan, NY, January 24, 2002

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 24, 2002, 18:13 local time
- Place: Penn Yan, NY
- Airport: Penn Yan Airport
- Damage: Minor damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Operator: SFOA
- Location: 42.6371° N, 77.0529° W: Placed by OpenAirDocs at Penn Yan Airport (PEO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.6371&lon=-77.0529&mi=10
- Aircraft: N87SF, registered now (https://openairdocs.org/aircraft/N87SF) (OpenAirDocs)
- Registry model: Cessna 560 (registry code 2076750, https://openairdocs.org/model/cessna-560) (OpenAirDocs)
- Registry engine: Pratt & Whitney Canada PW535A (registry code 52134, https://openairdocs.org/engine/pratt-whitney-canada-pw535a) (OpenAirDocs)
- Reported make and model: CESSNA 550
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 8,700 total, 1,500 in this make and model, 157 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020124002589I

## Narrative

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

(-23) UPON ENTERING VMC CONDITIONS WHILE CONDUCTING A NIGHT GPS RUNWAY 1 APPROACH, AT PENN YAN AIRPORT, THE CREW DID NOT MONITOR THE RATE OF DESCENT TO THE MINIMUM DESCENT ALTITUDE (MDA). THE AIRCRAFT CONTINUED BELOW THE MDA PRIOR TO REACHING A POINT IN SPACE WHERE A SAFE TOUCHDOWN COULD BE COMPLETED USING NORMAL MANEUVERING. THE AIRCRAFT STRUCK TREES, WHICH CAUSED THE PIC TO INITIALLY INCREASE ALTITUDE AND THEN, UPON VISUALLY ACQUIRING THE LANDING RUNWAY, COMPLETING AN UNEVENTFUL APPROACH TO TOUCHDOWN. POSTFLIGHT INVESTIGATION REVEALED DAMAGE TO THE LEFT WING LEADING EDGE AND LEFT LANDING GEAR. A SMALL PIECE OF WOOD APPROXIMATELY 4 INCHES LONG BY 1/2 INCH DIAMETER, WAS RECOVERED FROM THE ENGINE.

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.