An air carrier DC10 flight crew missed a taxiway while making their way to their gate and had to hol...

Attributes
ACN	384313
Time
Date	199710
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mke
State Reference	WI
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	DC-10 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 203 flight time total : 13960 flight time type : 334
ASRS Report	384313
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 10000 flight time type : 2000
ASRS Report	383702
Events
Anomaly	non adherence : far non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : became reoriented other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After landing and during our rollout on runway 7R, tower cleared us for a left turn on runway 1R and then advised us, 'cleared to the gate.' this would mean for us to make a left on taxiway M, cross runway 1L, left turn on taxiway east, a right turn on taxiway a, then another right turn on taxiway A1, then to the assigned gate. I was aware of the taxi restr for DC10 aircraft on taxiway B between taxiway right and taxiway A1, that is why I was planning on taxiing on taxiway east then taxiway a and then a right turn onto taxiway A1 as mentioned above. While I was proceeding south on taxiway east, I missed taxiway a which veers to the right, I started to slow when I saw runway 7R/25L sign on the left side of the taxiway, and proceeded to stop when I came upon the hold short line knowing then that I had passed taxiway a. At this same time, tower saw the situation and told us to stop because we were about to enter an active runway. We acknowledged, and apparently recognized the situation simultaneously, and I was already stopping the aircraft. I felt it was not an appropriate time to discuss this, since he was busy clearing 3 additional aircraft to land on runway 7R. We held short of runway 7R for the arrs, then we were cleared onto runway 25L then taxiway right, taxiway a, and taxiway A1 respectively, then to the gate. Some of the factors that led to this were that ATIS was reporting landing only on runway 1L and it was not until approximately 15-20 mi from the airport that we were to expect vectors for the visual to runway 7R. This was after I had briefed for the approach to runway 1L and its associated taxi in, with its restrictions. I then briefed for runway 7R. The other factor was the statement, 'taxi to the gate' while still on runway 7R which left it to us to determine our taxi route. This required 6 turns at night and the associated discussion with the crew as to the best route to get to the gate. These are some of the factors which led to my missing taxiway a.

Original NASA ASRS Text

Title: AN ACR DC10 FLC MISSED A TXWY WHILE MAKING THEIR WAY TO THEIR GATE AND HAD TO HOLD SHORT OF AN ACTIVE RWY UNTIL TFC CLRED SO THEY COULD GET BACK TO THE RAMP.

Narrative: AFTER LNDG AND DURING OUR ROLLOUT ON RWY 7R, TWR CLRED US FOR A L TURN ON RWY 1R AND THEN ADVISED US, 'CLRED TO THE GATE.' THIS WOULD MEAN FOR US TO MAKE A L ON TXWY M, CROSS RWY 1L, L TURN ON TXWY E, A R TURN ON TXWY A, THEN ANOTHER R TURN ON TXWY A1, THEN TO THE ASSIGNED GATE. I WAS AWARE OF THE TAXI RESTR FOR DC10 ACFT ON TXWY B BTWN TXWY R AND TXWY A1, THAT IS WHY I WAS PLANNING ON TAXIING ON TXWY E THEN TXWY A AND THEN A R TURN ONTO TXWY A1 AS MENTIONED ABOVE. WHILE I WAS PROCEEDING S ON TXWY E, I MISSED TXWY A WHICH VEERS TO THE R, I STARTED TO SLOW WHEN I SAW RWY 7R/25L SIGN ON THE L SIDE OF THE TXWY, AND PROCEEDED TO STOP WHEN I CAME UPON THE HOLD SHORT LINE KNOWING THEN THAT I HAD PASSED TXWY A. AT THIS SAME TIME, TWR SAW THE SIT AND TOLD US TO STOP BECAUSE WE WERE ABOUT TO ENTER AN ACTIVE RWY. WE ACKNOWLEDGED, AND APPARENTLY RECOGNIZED THE SIT SIMULTANEOUSLY, AND I WAS ALREADY STOPPING THE ACFT. I FELT IT WAS NOT AN APPROPRIATE TIME TO DISCUSS THIS, SINCE HE WAS BUSY CLRING 3 ADDITIONAL ACFT TO LAND ON RWY 7R. WE HELD SHORT OF RWY 7R FOR THE ARRS, THEN WE WERE CLRED ONTO RWY 25L THEN TXWY R, TXWY A, AND TXWY A1 RESPECTIVELY, THEN TO THE GATE. SOME OF THE FACTORS THAT LED TO THIS WERE THAT ATIS WAS RPTING LNDG ONLY ON RWY 1L AND IT WAS NOT UNTIL APPROX 15-20 MI FROM THE ARPT THAT WE WERE TO EXPECT VECTORS FOR THE VISUAL TO RWY 7R. THIS WAS AFTER I HAD BRIEFED FOR THE APCH TO RWY 1L AND ITS ASSOCIATED TAXI IN, WITH ITS RESTRICTIONS. I THEN BRIEFED FOR RWY 7R. THE OTHER FACTOR WAS THE STATEMENT, 'TAXI TO THE GATE' WHILE STILL ON RWY 7R WHICH LEFT IT TO US TO DETERMINE OUR TAXI RTE. THIS REQUIRED 6 TURNS AT NIGHT AND THE ASSOCIATED DISCUSSION WITH THE CREW AS TO THE BEST RTE TO GET TO THE GATE. THESE ARE SOME OF THE FACTORS WHICH LED TO MY MISSING TXWY A.

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.

An air carrier DC10 flight crew missed a taxiway while making their way to their gate and had to hold short of an active runway until traffic cleared so they could get back to the ramp.