Narrative:

Prior to landing on runway 25L; we briefed the txwys and expected taxi route. The taxi chart indicates that it is possible to taxi clear on taxiway an; then taxi onto taxiway M to cross runway 25R. That is the clearance we received. But when we cleared on taxiway an the txwys did not line up well and the lines indicated that it would be very difficult to taxi onto taxiway M. We expressed this to ground so he told us to turn left onto taxiway AC. I have since called ATC on the phone and asked about the confusion. I was told that the clearance should not have been given to taxi onto taxiway M from taxiway an and that the intent of the new txwys is to have traffic turn left onto taxiway AC. It might be helpful to have a NOTAM published with this information. While the confusion might be less during the day; at night I found the situation very problematic. Callback conversation with reporter revealed the following information: reporter advised that the center parallel taxiway AC and its connecting txwys to 25L and right was newly opened at the time of the incident. He stated they had been issued a special airport page to supplement the commercial airport page that shows no txwys in the area of the incident. Reporter's later conversation with ground control determined that the intent of this centrally located complex is as a location to shepherd aircraft across the complex. Connecting txwys are purposely not directly aligned to minimize the possibility of unintended rapid transit across both runways. ATC advised the clearance reporter received would not be the standard for aircraft transiting the area. Instead aircraft will generally be cleared to exit the runway via a connector taxiway; turn onto AC and await clearance to cross the opposite runway at an appropriate taxiway.

Google
 

Original NASA ASRS Text

Title: B757-200 CAPTAIN REPORTS THAT TXWYS AN AND M DO NOT MEET AS SHOWN ON THE GOVT ARPT PAGE.

Narrative: PRIOR TO LNDG ON RWY 25L; WE BRIEFED THE TXWYS AND EXPECTED TAXI RTE. THE TAXI CHART INDICATES THAT IT IS POSSIBLE TO TAXI CLR ON TXWY AN; THEN TAXI ONTO TXWY M TO CROSS RWY 25R. THAT IS THE CLRNC WE RECEIVED. BUT WHEN WE CLRED ON TXWY AN THE TXWYS DID NOT LINE UP WELL AND THE LINES INDICATED THAT IT WOULD BE VERY DIFFICULT TO TAXI ONTO TXWY M. WE EXPRESSED THIS TO GND SO HE TOLD US TO TURN L ONTO TXWY AC. I HAVE SINCE CALLED ATC ON THE PHONE AND ASKED ABOUT THE CONFUSION. I WAS TOLD THAT THE CLRNC SHOULD NOT HAVE BEEN GIVEN TO TAXI ONTO TXWY M FROM TXWY AN AND THAT THE INTENT OF THE NEW TXWYS IS TO HAVE TFC TURN L ONTO TXWY AC. IT MIGHT BE HELPFUL TO HAVE A NOTAM PUBLISHED WITH THIS INFO. WHILE THE CONFUSION MIGHT BE LESS DURING THE DAY; AT NIGHT I FOUND THE SITUATION VERY PROBLEMATIC. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: REPORTER ADVISED THAT THE CENTER PARALLEL TXWY AC AND ITS CONNECTING TXWYS TO 25L AND R WAS NEWLY OPENED AT THE TIME OF THE INCIDENT. HE STATED THEY HAD BEEN ISSUED A SPECIAL AIRPORT PAGE TO SUPPLEMENT THE COMMERCIAL AIRPORT PAGE THAT SHOWS NO TXWYS IN THE AREA OF THE INCIDENT. RPTR'S LATER CONVERSATION WITH GND CTL DETERMINED THAT THE INTENT OF THIS CENTRALLY LOCATED COMPLEX IS AS A LOCATION TO SHEPHERD ACFT ACROSS THE COMPLEX. CONNECTING TXWYS ARE PURPOSELY NOT DIRECTLY ALIGNED TO MINIMIZE THE POSSIBILITY OF UNINTENDED RAPID TRANSIT ACROSS BOTH RWYS. ATC ADVISED THE CLRNC REPORTER RECEIVED WOULD NOT BE THE STANDARD FOR ACFT TRANSITING THE AREA. INSTEAD ACFT WILL GENERALLY BE CLEARED TO EXIT THE RWY VIA A CONNECTOR TXWY; TURN ONTO AC AND AWAIT CLRNC TO CROSS THE OPPOSITE RWY AT AN APPROPRIATE TXWY.

Data retrieved from NASA's ASRS site as of May 2009 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.