37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1338145 |
Time | |
Date | 201603 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Other Change in landing runway |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Multiengine Flight Crew Commercial Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 12 Flight Crew Total 2900 Flight Crew Type 1250 |
Person 2 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | Ground Event / Encounter Gear Up Landing |
Narrative:
Enroute at pattern altitude I entered a long left downwind (pursuant to tower instructions) during a busy sunday afternoon when there were many aircraft landings. As I proceeded on left downwind; I was flying toward the approach end of the runway when the tower asked if I could accept a landing and hold short of the cross runway which was the active runway. I apprised tower that I could accommodate that request and began a descent to a short left base to the runway. I then made the base to final turn and continued my descent without using the check list; focusing on touching down close to the numbers; and landing short to assure that I could stop before crossing the other runway. As I began my flare; all seem to be going well until the prop struck the runway and the aircraft settled onto the fuselage and came to an abrupt stop. During the earlier phase of this flight; I landed for lunch and made a second landing for fuel. After refueling I departed for the very short low level flight into the busy sunday afternoon airspace. I was describing to my inexperienced passenger the arrival/landing sequence into a towered airport; the ATIS requirements; the five mile class D reporting requirements and cautioned him to watch for other traffic in the pattern which we could hear being vectored by the tower. That conversation; together with the last minute runway change; was my concern about landing short and my explanations to my new-to-flying passenger. This likely disturbed my concentration and disrupted my normal landing procedure including my failure to use the pre-landing check list resulting in the gear up landing. Most of the time I use a check list; as on the two previous legs/landing in this flight; where I had my passenger-friend; read me the check lists. However; on this short leg; after start up and climb out; and the unexpected runway change; I did not consult the check list on descent to landing. One non-pilot recommendation that I believe would help reduce gear-up landings at towered airports would be to employ the military and [foreign] tower procedure; of having the tower controller request 'confirm gear down and locked'. Retractable pilots typically check their gear and reply 'gear down and locked'; while fixed gear pilots typically report 'gear down and welded'. I frequently fly into [foreign airports] and have found this to be a helpful reminder!
Original NASA ASRS Text
Title: Small aircraft pilot became distracted and landed gear up.
Narrative: Enroute at pattern altitude I entered a long left downwind (pursuant to Tower instructions) during a busy Sunday afternoon when there were many aircraft landings. As I proceeded on left downwind; I was flying toward the approach end of the Runway when the tower asked if I could accept a landing and hold short of the cross Runway which was the active Runway. I apprised Tower that I could accommodate that request and began a descent to a short left base to the Runway. I then made the base to final turn and continued my descent without using the check list; focusing on touching down close to the numbers; and landing short to assure that I could stop before crossing the other runway. As I began my flare; all seem to be going well until the prop struck the Runway and the aircraft settled onto the fuselage and came to an abrupt stop. During the earlier phase of this flight; I landed for lunch and made a second landing for fuel. After refueling I departed for the very short low level flight into the busy Sunday afternoon airspace. I was describing to my inexperienced passenger the arrival/landing sequence into a Towered airport; the ATIS requirements; the five mile Class D reporting requirements and cautioned him to watch for other traffic in the pattern which we could hear being vectored by the Tower. That conversation; together with the last minute Runway change; was my concern about landing short and my explanations to my new-to-flying passenger. This likely disturbed my concentration and disrupted my normal landing procedure including my failure to use the pre-landing check list resulting in the gear up landing. Most of the time I use a check list; as on the two previous legs/landing in this flight; where I had my passenger-friend; read me the check lists. However; on this short leg; after start up and climb out; and the unexpected Runway change; I did not consult the check list on descent to landing. One non-pilot recommendation that I believe would help reduce gear-up landings at Towered airports would be to employ the Military and [Foreign] Tower procedure; of having the Tower controller request 'Confirm Gear Down and Locked'. Retractable pilots typically check their gear and reply 'Gear Down and Locked'; while fixed gear pilots typically report 'Gear Down and Welded'. I frequently fly into [Foreign Airports] and have found this to be a helpful reminder!
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.