OpenAirDocs.org

20150716010549I

Incident · Minor damage
Open the Markdown

FAA incident report · Cessna 310J · Doylestown, PA · July 16, 2015

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
July 16, 2015 · 21:30 local
Place
Doylestown, PA
Airport
Doylestown
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N515HW
Reported as
Cessna 310J
Reported engine
Continental I0-470 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Private pilot
Pilot’s flight hours
514 total150 in this make and model9 in the last 90 days
N515HWRegistration cancelled Apr 19, 2018 · Cessna 310JS/N 310J0102 · Built 1965Airframe modelCessna 310JEngine modelContinental I0-470 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.