# Incident 20130730013269I: Beech P35, Show Low, AZ, July 30, 2013 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: July 30, 2013, 09:00 local time - Place: Show Low, AZ - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 34.2542° N, 110.0298° W: Placed by OpenAirDocs: center of Show Low, AZ, within about 6 miles (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=34.2542&lon=-110.0298&mi=10 - Aircraft: N519BD, a cancelled registration (https://openairdocs.org/deregistered/N519BD-2017-10-06) (OpenAirDocs) - Registry model: Beech P35 (registry code 1151530, https://openairdocs.org/model/beech-p35) (OpenAirDocs) - Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs) - Reported make and model: BEECH P35 - Reported engine: CONT MOTOR I0-470 SERIES - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Commercial pilot, flight instructor - Pilot flight hours: 2,236 total, 264 in this make and model, 12 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20130730013269I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON JULY 30, 2013 AT APPROXIMATELY 9:00 AM LOCAL ARIZONA TIME. N519BD LANDED GEAR UP ON RUNWAY 6 AT KSOW, SHOW LOW ARIZONA. THE AIRPLANE SKIDDED FOR APPROXIMATELY 655 FEET BEFORE COMING TO REST AT THE EDGE OF THE RUNWAY. DAMAGE TO THE AIRCRAFT INCLUDES SKIN DAMAGE TO THE UNDERSIDE OF THE FUSELAGE, BROKEN ANTENNAS ON THE UNDERSIDE OF THE FUSEALAGE, FLAP DAMAGE ON BOTH THE LEFT AND RIGHT FLAPS. IN ADDITION THE PROPELLOR BLADES ARE CURLED ON THE TIPS AS A RESULT OF CONTACT WITH THE RUNWAY SURFACE. THE PROPELLOR BLADES ARE ALSO DAMAGED AT THE PROPELLOR HUB. THERE WAS NO POST INCIDENT FIRE AND THE PILOT WAS NOT INJURED. AFTER STOPPING, THE PILOT SECURED THE AIRCRAFT BY TURNING OFF AVIONICS AND MASTER SWITCHES AND EXITED THE AIRCRAFT. AN EMPLOYEE AT THE AIRPORT CONTACTED A FLIGHT SERVICE STATION FOR THE PURPOSES OF ISSUING A LOCAL NOTAM THAT THE RUNWAY WAS OUT OF SERVICE. IN A TELEPHONE INTERVIEW THE AIRPORT MANAGER INDICATED HE MADE A NON-EMERGENCY CALL TO THE FIRE DEPARTMENT TO REQUEST ASSISTANCE WITH FIRE WATCH AND TO FACILITATE LIFTING THE AIRPLANE WITH THE FIRE DEPARTMENT'S AIR BAGS AFTER THE INCIDENT OCCURRED. THE PILOT OF THE AIRCRAFT SPOKE TO THE AIRPORT MANAGER AND A LINEMAN AT THAT TIME AND INDICATED THAT HE HAD NO INJURIES. IN A TELEPHONE INVERVIEW A LINEMAN AT THE AIRPORT STATED THAT THE PILOT HAD REPORTED HE WAS DELIVERING THE AIRCRAFT AND HAD DEPARTED FROM KVNY, VAN NUYS CA ENROUTE TO LUBBOCK TEXAS. THE LINEMAN ALSO STATED THAT THE PILOT INDICATED HE WAS CONCERNED ABOUT THE DENSITY ALTITUDE, WAS PREOCCUPIED WITH THE CALCULATIONS FOR THE DENSITY ALTITUDE AND SIMPLY FORGOT TO LOWER THE GEAR. THE AIRPORT MANAGER ALSO INDICATED THAT THE PILOT EXPRESSED THE SAME CONCERN ABOUT DENSITY ALTITUDE DURING HIS CONVERSATION HE HAD WITH THE AIRMAN. THE PILOT WAS INTERVIEWED ABOUT THE INCIDENT. DURING THIS TELEPHONE INTERVIEW HE STATED THAT HE HAD INTENDED TO LEAVE MUCH EARLIER FOR HIS ARRIVAL AT KSOW. THE PILOT STATED THAT HE WAS DELAYED BECAUSE THE RUNWAY AT KVNY, VAN NUYS CALIFORNIA, HIS DEPARTURE AIRPORT, DID NOT OPEN UNTIL LATER THAN HE ANTICIPATED AND HE HAD NO KNOWLEDGE OF THE LATE OPENING. THE PILOT INDICATED THAT THE FLIGHT FROM KVNY TO KSOW WAS WITHOUT INCIDENT. THE PILOT STATED THAT HE APPROACHED KSOW ON A VERY LONG FINAL FOR RUNWAY 6, APPROACHING FROM THE WEST. THE PILOT CONTINUED THAT HE BECAME CONCERNED WITH THE DENSITY ALTITUDE AT THE AIRPORT AS IT WAS SEVERAL HOURS LATER THAN HE EXPECTED. THE PILOT STATED THAT HE BEGAN TO CALCULATE THE DENSITY ALTITUDE AS HE APPROACHED THE AIRPORT, WHILE STILL ON A LONG FINAL APPROACH. THE AIRMAN WAS ASKED HOW FAR FROM THE AIRPORT HE WAS AT THE TIME HE BEGAN TO CALCULATE DENSITY ALTITUDE. HE INDICATED HE WAS SEVERAL MILES FROM THE AIRPORT. THE PILOT STATED THAT HE FORGOT TO UTILIZE HIS CHECKLIST, SPECIFICALLY THE BEFORE LANDING CHECKLIST. HE THEN STATED THAT HIS FIRST INDICATION OF THE GEAR NOT BEING DOWN AND LOCKED WAS ON TOUCHDOWN AND THE ENSUING SKIDDING DOWN THE RUNWAY. WHEN ASKED WHY HE FELT THIS INCIDENT OCCURRED THE AIRMAN STATED THAT HE JUST FORGOT TO PUT THE LANDING GEAR IN THE DOWN POSITION PRIOR TO LANDING. THE AIRMAN WAS ASKED IF THERE WERE ANY OTHER EXTENUATING CIRCUMSTANCES WHICH MAY HAVE LED TO THE INCIDENT SUCH AS WEATHER OR MECHANICAL ISSUES. THE AIRMAN STATED THAT THE WEATHER WAS SEVERE CLEAR WITH JUST A LIGHT BREEZE AND THE AIRPLANE HAD NO MECHANICAL ISSUES. HE STATED THAT THERE WERE NO EXTERNAL ISSUES THAT LED TO THE INCIDENT. HE AGAIN REITERATED THAT IT WAS HIS FAULT IN FORGETTING TO PUT THE GEAR DOWN AND HE WAS SHOCKED THAT IT HAD HAPPENED TO HIM. THE AIRMAN WAS ASKED IF HE HAD OBTAINED A PREFLIGHT BRIEFING FOR THE FLIGHT THAT DAY AND HE INDICATED HE HAD THROUGH FLIGHT SERVICE. THE AIRMAN WAS ALSO ASKED IF HE HAD GOTTEN A REVISED PREFLIGHT BRIEFING AFTER THE SEVERAL HOUR DELAY ON DEPARTURE. HE INDICATED HE DID NOT OBTAIN A REVISED BRIEFING. 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.