Narrative:

On checking in with ground coming out of the ramp, our runway got changed from runway 32L (right near the ramp) to runway 27L. As we taxied to runway 27L, I had to enter the new runway data into our performance computer and enter the data into the FMS. We also had to cross runway 27L and runway 32L, so this delayed configuring the aircraft. I had my taxi chart (airport diagram) out and monitored our position as we got on taxiway M and crossed runway 32L. During the taxi, the captain (a line check airman) requested more than once that I extinguish my map light as it was distracting to him. Once on taxiway 'M,' I left the light off and simply watched for the taxiway leading to runway 27L. I had not noted its name, so I was trying to watch for the taxiway leading for runway 27L. Rather than a specific name. As it was, we missed taxiway 'M7' (access to runway 27L) and passed taxiway 'Q' and taxied on runway 22L, then made another right to line up with runway 27L. As such, we taxied on runway 22L without specific clearance to do so and on pavement not marked or depicted as a taxiway or runway (the extension of runway 27L is paved to runway 22L). We checked and verbalized that runway 22L was clear both ways, so no traffic conflict occurred. Lesson learned: 1) line check airman can make mistakes. I didn't feel comfortable while taxiing on taxiway M approaching runway 22L and allowed him to continue when he said that he knew where he was when I reached for my map light. 2) I was not emphatic enough to the captain in stating my concerns and failed to allay my feelings by checking the airport diagram. 3) I allowed him to taxi on pavement that had no markings or lighting as a taxiway coming off runway 22L and lining up on runway 27L. I felt that I had told him that it wasn't a taxiway, but he continued. I could have told him to 'stop' and get on the radio for clarification, but I didn't. 4) no matter how familiar the other guy says he is with the airport, monitor, monitor, monitor.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN MD11 CREW, TAXIING FOR TKOF AT ORD, MISSED THEIR ASSIGNED TXWY ENDING UP ON AN ACTIVE RWY WITHOUT A CLRNC.

Narrative: ON CHKING IN WITH GND COMING OUT OF THE RAMP, OUR RWY GOT CHANGED FROM RWY 32L (RIGHT NEAR THE RAMP) TO RWY 27L. AS WE TAXIED TO RWY 27L, I HAD TO ENTER THE NEW RWY DATA INTO OUR PERFORMANCE COMPUTER AND ENTER THE DATA INTO THE FMS. WE ALSO HAD TO CROSS RWY 27L AND RWY 32L, SO THIS DELAYED CONFIGURING THE ACFT. I HAD MY TAXI CHART (ARPT DIAGRAM) OUT AND MONITORED OUR POS AS WE GOT ON TXWY M AND CROSSED RWY 32L. DURING THE TAXI, THE CAPT (A LINE CHK AIRMAN) REQUESTED MORE THAN ONCE THAT I EXTINGUISH MY MAP LIGHT AS IT WAS DISTRACTING TO HIM. ONCE ON TXWY 'M,' I LEFT THE LIGHT OFF AND SIMPLY WATCHED FOR THE TXWY LEADING TO RWY 27L. I HAD NOT NOTED ITS NAME, SO I WAS TRYING TO WATCH FOR THE TXWY LEADING FOR RWY 27L. RATHER THAN A SPECIFIC NAME. AS IT WAS, WE MISSED TXWY 'M7' (ACCESS TO RWY 27L) AND PASSED TXWY 'Q' AND TAXIED ON RWY 22L, THEN MADE ANOTHER R TO LINE UP WITH RWY 27L. AS SUCH, WE TAXIED ON RWY 22L WITHOUT SPECIFIC CLRNC TO DO SO AND ON PAVEMENT NOT MARKED OR DEPICTED AS A TXWY OR RWY (THE EXTENSION OF RWY 27L IS PAVED TO RWY 22L). WE CHKED AND VERBALIZED THAT RWY 22L WAS CLR BOTH WAYS, SO NO TFC CONFLICT OCCURRED. LESSON LEARNED: 1) LINE CHK AIRMAN CAN MAKE MISTAKES. I DIDN'T FEEL COMFORTABLE WHILE TAXIING ON TXWY M APCHING RWY 22L AND ALLOWED HIM TO CONTINUE WHEN HE SAID THAT HE KNEW WHERE HE WAS WHEN I REACHED FOR MY MAP LIGHT. 2) I WAS NOT EMPHATIC ENOUGH TO THE CAPT IN STATING MY CONCERNS AND FAILED TO ALLAY MY FEELINGS BY CHKING THE ARPT DIAGRAM. 3) I ALLOWED HIM TO TAXI ON PAVEMENT THAT HAD NO MARKINGS OR LIGHTING AS A TXWY COMING OFF RWY 22L AND LINING UP ON RWY 27L. I FELT THAT I HAD TOLD HIM THAT IT WASN'T A TXWY, BUT HE CONTINUED. I COULD HAVE TOLD HIM TO 'STOP' AND GET ON THE RADIO FOR CLARIFICATION, BUT I DIDN'T. 4) NO MATTER HOW FAMILIAR THE OTHER GUY SAYS HE IS WITH THE ARPT, MONITOR, MONITOR, MONITOR.

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.