# Incident 20100701035989I: Cirrus Desi SR20, Doylestown, PA, July 1, 2010

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 1, 2010, 15:00 local time
- Place: Doylestown, PA
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 40.3142° N, 75.1277° W: Placed by OpenAirDocs: center of Doylestown, PA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.3142&lon=-75.1277&mi=10
- Aircraft: N1287C, registered now (https://openairdocs.org/aircraft/N1287C) (OpenAirDocs)
- Registry model: Cirrus Design SR20 (registry code 2130000, https://openairdocs.org/model/cirrus-design-sr20) (OpenAirDocs)
- Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs)
- Reported make and model: CIRRUS DESI SR20
- Reported engine: CONT MOTOR IO-360 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 3,135 total, 287 in this make and model, 22 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20100701035989I

## Narrative

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

ON 7/1/2010, ^PRIVACY DATA OMITTED^ STATED THAT HE WAS APPROACHING THE DOYLESTOWN (KDYL) AIRPORT FOR LANDING IN AN SR-20. HE LISTENED TO THE AWOS WHICH WAS REPORTING WINDS OF 330/11 G 16 KTS. ^PRIVACY DATA OMITTED^ ATTEMPTED A LANDING ON RUNWAY 23 AND DURING THE LANDING PHASE, HE STATED THAT HE "PORPOISED" THE AIRCRAFT THREE TIMES ON THE RUNWAY AND ENCOUNTERED A TAILWIND AS WELL. HE DECIDED TO EXECUTE A GO AROUND AND MADE A SECOND LANDING WITHOUT INCIDENT. ^PRIVACY DATA OMITTED^ DID NOT NOTICE THAT THERE WAS ANY DAMAGE TO THE PROPELLER UNTIL HE WAS PUSHING THE AIRCRAFT BACK INTO THE HANGAR.

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.