37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 365688 |
Time | |
Date | 199704 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : lal |
State Reference | FL |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Cheetah, Tiger, Traveler |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach landing other |
Flight Plan | None |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 20 flight time total : 1500 flight time type : 900 |
ASRS Report | 365688 |
Person 2 | |
Affiliation | Other |
Function | observation : passenger observation : observer |
Qualification | other other : other |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : far non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other other : unspecified |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation other |
Narrative:
Landed in error on the taxiway north of runway 9 during arrival at lal. Background: prior to departure, obtained the copious information regarding a fly-in via the internet. Was aware of the utilization of a taxiway as a runway during the fly-in, however, I did not specifically identify it as runway 9L/27R, ie, north of main runway. Additionally, was definitely preoccupied with concerns regarding traffic congestion, admonitions to listen -- don't transmit, and follow traffic. Arriving at the vicinity of lal, and following the defined arrival routing, the first (and only) controller communication directed to my aircraft, of which we were aware, was late on downwind for runway 9R. At that time, 2 aircraft immediately preceding us in the pattern were on mid and late final. They appeared to be about to land on the taxiway south of the main runway 9, and my passenger confirmed my impression to that effect. Turning base for the directed landing on runway 9R, intending to activate flaps, I was momentarily distracted to find the toggle switch broken and the handle retained in position only by the rubber boot. Continuing the landing approach with necessity of no-flaps landing, and with total radio silence since the previous directive to follow traffic, received when on late downwind, aligned for final to land on the taxiway. The taxiway was completely clear of any aircraft, vehicles or personnel, and receiving no further direction regarding touchdown location, landing was completed at far west end of the taxiway. Completing taxi to the first encounter with ground personnel, we were first made aware of having landed on the wrong surface. Possible prevention: I recall having and seeing both pictorial and diagrammatic depictions of the arrival environment, but do not recall seeing any airport layout diagrams identing the runways and txwys, in any of the fly-in information. Also, the temporary, x- out of such txwys during the fly-in might be worthy of future consideration. Am now aware of necessity to more completely prepare for arrival at such activities, including visualization of airport environment.
Original NASA ASRS Text
Title: PVT PLT IN AN AA5 CHEETAH LANDS ON TXWY N OF THE MAIN RWY, RWY 9. THE TXWY HAD BEEN DESIGNATED AS A RWY 9L USED FOR A FLY-IN ACTIVITY. HOWEVER, PLT HAD BEEN CLRED TO LAND ON RWY 9. HE WAS DISTRACTED BY A BROKEN FLAP SWITCH AND MADE A NO FLAP LNDG ON THE TXWY.
Narrative: LANDED IN ERROR ON THE TXWY N OF RWY 9 DURING ARR AT LAL. BACKGROUND: PRIOR TO DEP, OBTAINED THE COPIOUS INFO REGARDING A FLY-IN VIA THE INTERNET. WAS AWARE OF THE UTILIZATION OF A TXWY AS A RWY DURING THE FLY-IN, HOWEVER, I DID NOT SPECIFICALLY IDENT IT AS RWY 9L/27R, IE, N OF MAIN RWY. ADDITIONALLY, WAS DEFINITELY PREOCCUPIED WITH CONCERNS REGARDING TFC CONGESTION, ADMONITIONS TO LISTEN -- DON'T XMIT, AND FOLLOW TFC. ARRIVING AT THE VICINITY OF LAL, AND FOLLOWING THE DEFINED ARR ROUTING, THE FIRST (AND ONLY) CTLR COM DIRECTED TO MY ACFT, OF WHICH WE WERE AWARE, WAS LATE ON DOWNWIND FOR RWY 9R. AT THAT TIME, 2 ACFT IMMEDIATELY PRECEDING US IN THE PATTERN WERE ON MID AND LATE FINAL. THEY APPEARED TO BE ABOUT TO LAND ON THE TXWY S OF THE MAIN RWY 9, AND MY PAX CONFIRMED MY IMPRESSION TO THAT EFFECT. TURNING BASE FOR THE DIRECTED LNDG ON RWY 9R, INTENDING TO ACTIVATE FLAPS, I WAS MOMENTARILY DISTRACTED TO FIND THE TOGGLE SWITCH BROKEN AND THE HANDLE RETAINED IN POS ONLY BY THE RUBBER BOOT. CONTINUING THE LNDG APCH WITH NECESSITY OF NO-FLAPS LNDG, AND WITH TOTAL RADIO SILENCE SINCE THE PREVIOUS DIRECTIVE TO FOLLOW TFC, RECEIVED WHEN ON LATE DOWNWIND, ALIGNED FOR FINAL TO LAND ON THE TXWY. THE TXWY WAS COMPLETELY CLR OF ANY ACFT, VEHICLES OR PERSONNEL, AND RECEIVING NO FURTHER DIRECTION REGARDING TOUCHDOWN LOCATION, LNDG WAS COMPLETED AT FAR W END OF THE TXWY. COMPLETING TAXI TO THE FIRST ENCOUNTER WITH GND PERSONNEL, WE WERE FIRST MADE AWARE OF HAVING LANDED ON THE WRONG SURFACE. POSSIBLE PREVENTION: I RECALL HAVING AND SEEING BOTH PICTORIAL AND DIAGRAMMATIC DEPICTIONS OF THE ARR ENVIRONMENT, BUT DO NOT RECALL SEEING ANY ARPT LAYOUT DIAGRAMS IDENTING THE RWYS AND TXWYS, IN ANY OF THE FLY-IN INFO. ALSO, THE TEMPORARY, X- OUT OF SUCH TXWYS DURING THE FLY-IN MIGHT BE WORTHY OF FUTURE CONSIDERATION. AM NOW AWARE OF NECESSITY TO MORE COMPLETELY PREPARE FOR ARR AT SUCH ACTIVITIES, INCLUDING VISUALIZATION OF ARPT ENVIRONMENT.
Data retrieved from NASA's ASRS site as of July 2007 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.