# Incident 20150716010549I: Cessna 310J, Doylestown, PA, July 16, 2015

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 16, 2015, 21:30 local time
- Place: Doylestown, PA
- Airport: Doylestown
- 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: N515HW, a cancelled registration (https://openairdocs.org/deregistered/N515HW-2018-04-19) (OpenAirDocs)
- Registry model: Cessna 310J (registry code 2074226, https://openairdocs.org/model/cessna-310j) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 310J
- Reported engine: CONT MOTOR I0-470 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 514 total, 150 in this make and model, 9 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20150716010549I

## Narrative

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

ON 7/16/15 AT 2130 LOCAL TIME, ^PRIVACY DATA OMITTED^ WAS THE PILOT IN COMMAND OF N515HW (CE-310). ^PRIVACY DATA OMITTED^ HAD DEPARTED LYNCHBURG, VA (KLYH) ON AN IFR FLIGHT PLAN WITH A DESTINATION OF DOYLESTOWN, PA (KDYL). UPON ARRIVAL INTO THE DOYLESTOWN AREA, ^PRIVACY DATA OMITTED^ ENTERED THE TRAFFIC PATTERN FOR RUNWAY 5. ON FINAL APPROACH ^PRIVACY DATA OMITTED^ REALIZED THAT HE WAS TOO HIGH AND FAST AND PERFORMED A GO-AROUND BY RETRACTING THE GEAR AND FLAPS. ^PRIVACY DATA OMITTED^ THEN ENTERED THE PATTERN FOR ANOTHER APPROACH TO RUNWAY 5. WHILE IN THE PATTERN FOR THE SECOND APPROACH, ^PRIVACY DATA OMITTED^ STATED THAT HE HAD FAILED TO EXTEND THE LANDING GEAR. ON FINAL APPROACH TO RUNWAY 5, THE LANDING GEAR HORN WAS AUDIBLE AND WAS CONFUSED WITH THE STALL HORN. IN THE FLARE, IT BECAME APPARENT THAT THE AIRCRAFT WAS LOW (IN RELATION TO THE RUNWAY) WITH ONLY A 1/3RD OF THE RUNWAY REMAINING AND AT THAT TIME ^PRIVACY DATA OMITTED^ INITIATED A GO AROUND. DURING THE GO AROUND, THE  PROPELLERS STRUCK THE RUNWAY AND THE AIRCRAFT BECAME AIRBORNE LONG ENOUGH TO FLY OVER A FENCE AND FINALLY CAME TO A REST IN A FIELD ON THE OTHER SIDE OF THE AIRPORT. EVACUATION WAS COMPLETED AND NO INJURIES REPORTED BY THE PILOT/PASSENGER. MINOR DAMAGE TO THE AIRCRAFT HAD OCCURRED AND NO OTHER DAMAGE TO PROPERTY OR INJURY TO INDIVIDUALS ON THE GROUND REPORTED.

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.