OpenAirDocs.org

20071111826779I

Incident · Minor damage
Open the Markdown

FAA incident report · Socata TBM700 · Tucson, AZ · November 11, 2007

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
November 11, 2007 · 20:30 local
Place
Tucson, AZ
Airport
Tucson International
Phase of flight
Level Off Touchdown
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N220JM
Reported as
Socata TBM700
People aboard
4
Fatal injuries
0
Pilot’s flight hours
1,370 total58 in this make and model84 in the last 90 days

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.

(-23) The pilot gave a description of the evening's events. He stated he received multiple vectors onto final, intercepting the localizer just outside the final approach fix. It was a clear evening and the pilot said he had the runway in sight well before being cleared for the approach. He stated that before localizer intercept he was stabilized at 178 KIAS, with one notch of flaps and the gear down. After calling the airport in sight, he was cleared for the visual approach above 5000'. When cleared to land he verified 3 down and locked. The pilot, inexperienced with night operations (per his own admission), was busy trying to line up after a busy approach. After touching down gear up, the pilot and passengers evacuated the airplane, having received no response when trying to contact the tower. Approximately 5-10 min later, the pilot contacted a friend who then called the tower on the telephone to advise them that the aircraft had not cleared the runway, and that a 737 was on final. After the fire crew arrived the pilot asked the fire captain for permission to raise the partially extended gear in order to facilitate towing of the aircraft.

As the FAA filed it

(-23) THE PILOT GAVE A DESCRIPTION OF THE EVENING'S EVENTS. HE STATED HE RECEIVED MULTIPLE VECTORS ONTO FINAL, INTERCEPTING THE LOCALIZER JUST OUTSIDE THE FINAL APPROACH FIX. IT WAS A CLEAR EVENING AND THE PILOT SAID HE HAD THE RUNWAY IN SIGHT WELL BEFORE BEING CLEARED FOR THE APPROACH. HE STATED THAT BEFORE LOCALIZER INTERCEPT HE WAS STABILIZED AT 178 KIAS, WITH ONE NOTCH OF FLAPS AND THE GEAR DOWN. AFTER CALLING THE AIRPORT IN SIGHT, HE WAS CLEARED FOR THE VISUAL APPROACH ABOVE 5000'. WHEN CLEARED TO LAND HE VERIFIED 3 DOWN AND LOCKED. THE PILOT, INEXPERIENCED WITH NIGHT OPERATIONS (PER HIS OWN ADMISSION), WAS BUSY TRYING TO LINE UP AFTER A BUSY APPROACH. AFTER TOUCHING DOWN GEAR UP, THE PILOT AND PASSENGERS EVACUATED THE AIRPLANE, HAVING RECEIVED NO RESPONSE WHEN TRYING TO CONTACT THE TOWER. APPROXIMATELY 5-10 MIN LATER, THE PILOT CONTACTED A FRIEND WHO THEN CALLED THE TOWER ON THE TELEPHONE TO ADVISE THEM THAT THE AIRCRAFT HAD NOT CLEARED THE RUNWAY, AND THAT A 737 WAS ON FINAL. AFTER THE FIRE CREW ARRIVED THE PILOT ASKED THE FIRE CAPTAIN FOR PERMISSION TO RAISE THE PARTIALLY EXTENDED GEAR IN ORDER TO FACILITATE TOWING OF THE AIRCRAFT.