# Incident 20180207002069I: Cessna 310Q, Sand Springs, OK, February 7, 2018 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: February 7, 2018, 11:00 local time - Place: Sand Springs, OK - Airport: William Pogue - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 36.1397° N, 96.1246° W: Placed by OpenAirDocs: center of Sand Springs, OK, within about 6 miles (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=36.1397&lon=-96.1246&mi=10 - Aircraft: N7522Q, a cancelled registration (https://openairdocs.org/deregistered/N7522Q-2018-04-11) (OpenAirDocs) - Registry model: Cessna 310Q (registry code 2074242, https://openairdocs.org/model/cessna-310q) (OpenAirDocs) - Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs) - Reported make and model: CESSNA 310Q - Reported engine: CONT MOTOR I0-470 SERIES - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 1,120 total, 622 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/20180207002069I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. DURING A PHONE INTERVIEW WITH THE PILOT HE STATED THAT HE DEPARTED FROM KRVS WITH FLIGHT FOLLOWING FROM KTUL GOING TO KOWP, A SHORT FLIGHT THAT HE HAD DONE MANY TIMES. HE LEVELED OFF AT 2000 FEET FOR THE SHORT FLIGHT. THE CONTROLLER SOON RELEASED HIM TO CHANGE FREQUENCIES AND ADVISED HIM THERE WERE TWO AIRCRAFT IN THE OWP AREA. HE WAS ABLE TO SEE THE TRAFFIC ON HIS NEW GARMIN GTN 750. HE NOTICE ONE OF THE AIRCRAFT FLY AWAY FROM THE TRAFFIC AREA. HE THEN ANNOUNCED HE WAS ON A FIVE MILE FINAL TO RUNWAY 35 OWP. THE REMAINING AIRCRAFT (#2) ADVISED HIM THEY WERE ON A DOWNWIND LEG FOR 35 OWP. WHEN HE WAS THREE MILES OUT HE ADVISED THE #2 AIRCRAFT OF HIS LOCATION. THEY SAID THEY WERE UNABLE TO SEE HIM. AT THIS TIME HE TURNED ON HIS LANDING LIGHTS HOPING TO HELP #2 TO SEE HIM. AGAIN THEY SAID THEY DID NOT HAVE HIM INSIGHT. WHEN HE NOTICED ON HIS GTN 750 HE WAS PERPENDICULAR TO EACH OTHER, HE ADVISED #2 THAT HE WAS AT THEIR 3 O'CLOCK. AS HE REACHED ONE MILE FINAL, HE ADVISED THE #2 AIRCRAFT THAT THEY WERE BEHIND HIM AND WERE ABLE TO TURN BASE. THE AIRCRAFT LANDED WITH THE GEAR NOT EXTENDED. NO INJURIES OR DAMAGE OF PROPERTY, MINOR DAMAGE TO AIRCRAFT. ON 02/08/2018 CONDUCTED INSPECTION OF AIRCRAFT ON THE PARKING RAMP OF OWP. THE AIRCRAFT WAS OBSERVED WITH THE GEAR DOWN AND LOCKED AND TIED DOWN ON THE RAMP. DAMAGE TO AIRCRAFT WAS AS FOLLOWS: BOTH PROPELLERS HAD EXHIBITED TIP CURLING THE OUTER 12 PLUS INCHES. THE LOWER FUSELAGE SKIN HAD ABRASION DAMAGE, AS DID THE AUGMENTER TUBES ON BOTH NACELLES AND THE TAIL STRAKE. THE AFT SECTION OF THE NOSE GEAR DOORS ALSO HAD ABRASION DAMAGE FROM THE RUNWAY SURFACE. THE PILOT STATED THAT HE DOES REMEMBER REACHING FOR HE GEAR HANDLE EARLY UPON THE APPROACH AND SAYING TO HIMSELF IT WAS TO EARLY FOR THE GEAR TO BE EXTENDED. HE KNEW HE DIDN'T REACH FOR THE GEAR HANDLE AS THE PROPS WERE STRIKING THE GROUND. HE STATED THAT HE BROUGHT UP THIS POINT BECAUSE AFTER THEY PICKED UP THE AIRCRAFT OFF THE RUNWAY HIS PARTNER WAS ASKED TO LOWER THE GEAR SO WE COULD ROLL THE AIRCRAFT OFF THE RUNWAY. HE THEN SAID THE GEAR HANDLE WAS DOWN AND THE BREAKER FOR THE GEAR HAD POPPED. THE PILOT HAS STATED THAT HE HAD NOT EVER VERIFIED THAT HE HAD HIS THREE GREEN LIGHT VERIFICATION DURING HIS APPROACH. INSPECTION OF THE AIRCRAFT AND PILOT RECORDS REVEALED NO ISSUES. ## Other reports on N7522Q (1) Matched to the same aircraft by N-number and date. - [Incident 19940320010139I](https://openairdocs.org/incident/19940320010139I), Mar 20, 1994: Cessna 310Q (N7522Q), Sacramento, CA. Narrative: on March 20, 1994, at 7:50 pm PST, N7522Q, a Cessna 310Q, registered to george e. noud and deborah s. brown experienced an unsafe indication of the… 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.