37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 136563 |
Time | |
Date | 199002 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tus |
State Reference | AZ |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Small Transport, Low Wing, 2 Recip Eng |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 75 flight time total : 2000 flight time type : 600 |
ASRS Report | 136563 |
Person 2 | |
Affiliation | government : faa |
Function | controller : ground |
Qualification | controller : non radar |
Events | |
Anomaly | incursion : runway |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
I switched to ground control and was told to taxi 'to runway 11' at tucson international. I taxied from tucson executive terminal northbound paralleling runway 11 to what should be an appropriate runup area at the north end of runway 11. I was then informed that I had taxied across an active runway 29 (although I looked for traffic as is my usual customary practice) and had taxied down a parallel taxiway that paralleled a long overrun area. After initiating my runup I was informed of the situation. I asked the ground controller to confirm my previous instructions, which he did in addition to mentioning that he 'was distracted' (or something to that effect) and for that reason had allowed this to happen. Closer observation of transient aircraft in taxiing in a non-standard environment. Standardization and clarification of where an aircraft should taxi to in regards to a runway 11 departure, as potential complications of taxiing across an active runway are obvious.
Original NASA ASRS Text
Title: PLT OF SMT CLEARED TO RWY 11 INADVERTANTLY TAXIED ACROSS ACTIVE RWY 29.
Narrative: I SWITCHED TO GND CTL AND WAS TOLD TO TAXI 'TO RWY 11' AT TUCSON INTL. I TAXIED FROM TUCSON EXECUTIVE TERMINAL NBOUND PARALLELING RWY 11 TO WHAT SHOULD BE AN APPROPRIATE RUNUP AREA AT THE N END OF RWY 11. I WAS THEN INFORMED THAT I HAD TAXIED ACROSS AN ACTIVE RWY 29 (ALTHOUGH I LOOKED FOR TFC AS IS MY USUAL CUSTOMARY PRACTICE) AND HAD TAXIED DOWN A PARALLEL TXWY THAT PARALLELED A LONG OVERRUN AREA. AFTER INITIATING MY RUNUP I WAS INFORMED OF THE SITUATION. I ASKED THE GND CTLR TO CONFIRM MY PREVIOUS INSTRUCTIONS, WHICH HE DID IN ADDITION TO MENTIONING THAT HE 'WAS DISTRACTED' (OR SOMETHING TO THAT EFFECT) AND FOR THAT REASON HAD ALLOWED THIS TO HAPPEN. CLOSER OBSERVATION OF TRANSIENT ACFT IN TAXIING IN A NON-STANDARD ENVIRONMENT. STANDARDIZATION AND CLARIFICATION OF WHERE AN ACFT SHOULD TAXI TO IN REGARDS TO A RWY 11 DEP, AS POTENTIAL COMPLICATIONS OF TAXIING ACROSS AN ACTIVE RWY ARE OBVIOUS.
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.