Narrative:

Taxiway's A1 and B3 closed due to construction. At gate I briefed to request runway 05R to takeoff due to maximum weight on runway 05L. Also briefed tower might have us use taxiway B2 or all the way down taxiway alpha; cross both runways and double back from the southeast to get to runway 05R. Ie both of us had reviewed the airport diagram and thought we had a plan. On taxi to runway 05R tower tells us to cross runway 05L and hold short of taxiway aa. As we are trying to start right engine and finish before takeoff checks; we are reviewing 10-9 page and for a moment misread it thinking that taxiway A4 is taxiway aa and there is momentary confusion on whether cleared to continue taxi around end of runway 05R also since we did not see taxiway aa on 10-9; and mistakenly had read taxiway A4 as taxiway aa. Looking out we see aircraft on final approach runway 05R and at last minute I notice taxiway aa sign off to my left so stop immediately; between runway 05L and runway 05R on taxiway alpha. So we did comply with hold short instructions and rest of flight uneventful. Upon leveloff at cruise we reviewed what had happened and discovered problems with 10-9 and 10-9B pages for MMMX. Previous revision dated 01/wed/06; 10-9B page does show taxiway aa. Current revision does not; nor does current 10-9 page. Those pages now show series of XXX's where actual open txwys in fact exist. This is quite confusing. We in fact were told to; and did taxi on those XXX's to get to runway 05R. In retrospect I was trying to be proactive in gate brief about possibility of taxi across both runways on taxiway alpha; then double back from the southeast to runway 05R; and that kind of set up a mindset. Then we couldn't find taxiway aa and were trying to get second engine started and look at 10-9 and saw taxiway A4 instead. While our crossing thru the approach path of runway 05R would not have caused an incident; it would have at the very least been embarrassing. As happens; it was hard to understand the controller since she was mixing a lot of spanish with english instructions also when working other traffic. It would have been easier had controller crossed; then held us on taxiway B2 awaiting runway 05R. Taxiway B2 is wide; and was wide open. In the end; clearing final runway 05R visually; the 'when in doubt; stop' technique; and at last minute being able to see the taxiway aa sign (amid all the barriers and construction going on on taxiway A1) is what resolved the situation. Getting those MMMX airport pages right would also be helpful.supplemental information from acn 717279: inaccurate chart combined with language barrier nearly resulted in runway incursion.callback conversation with reporter acn 717264 revealed the following information: reporter states as of 11/mon/06 no update from company or commercial chart publisher.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN MD80 TAXIING FOR TKOF AT MMMX FINDS SOME ERRORS ON COMMERCIAL CHART 10-9 AND 10-9B PAGES THAT LEAD TO A NEAR RWY INCURSION.

Narrative: TXWY'S A1 AND B3 CLOSED DUE TO CONSTRUCTION. AT GATE I BRIEFED TO REQUEST RWY 05R TO TAKEOFF DUE TO MAX WT ON RWY 05L. ALSO BRIEFED TWR MIGHT HAVE US USE TXWY B2 OR ALL THE WAY DOWN TXWY ALPHA; CROSS BOTH RWYS AND DOUBLE BACK FROM THE SE TO GET TO RWY 05R. IE BOTH OF US HAD REVIEWED THE ARPT DIAGRAM AND THOUGHT WE HAD A PLAN. ON TAXI TO RWY 05R TWR TELLS US TO CROSS RWY 05L AND HOLD SHORT OF TXWY AA. AS WE ARE TRYING TO START R ENGINE AND FINISH BEFORE TAKEOFF CHKS; WE ARE REVIEWING 10-9 PAGE AND FOR A MOMENT MISREAD IT THINKING THAT TXWY A4 IS TXWY AA AND THERE IS MOMENTARY CONFUSION ON WHETHER CLRED TO CONTINUE TAXI AROUND END OF RWY 05R ALSO SINCE WE DID NOT SEE TXWY AA ON 10-9; AND MISTAKENLY HAD READ TXWY A4 AS TXWY AA. LOOKING OUT WE SEE ACFT ON FINAL APCH RWY 05R AND AT LAST MINUTE I NOTICE TXWY AA SIGN OFF TO MY LEFT SO STOP IMMEDIATELY; BETWEEN RWY 05L AND RWY 05R ON TXWY ALPHA. SO WE DID COMPLY WITH HOLD SHORT INSTRUCTIONS AND REST OF FLT UNEVENTFUL. UPON LEVELOFF AT CRUISE WE REVIEWED WHAT HAD HAPPENED AND DISCOVERED PROBS WITH 10-9 AND 10-9B PAGES FOR MMMX. PREVIOUS REVISION DATED 01/WED/06; 10-9B PAGE DOES SHOW TXWY AA. CURRENT REVISION DOES NOT; NOR DOES CURRENT 10-9 PAGE. THOSE PAGES NOW SHOW SERIES OF XXX'S WHERE ACTUAL OPEN TXWYS IN FACT EXIST. THIS IS QUITE CONFUSING. WE IN FACT WERE TOLD TO; AND DID TAXI ON THOSE XXX'S TO GET TO RWY 05R. IN RETROSPECT I WAS TRYING TO BE PROACTIVE IN GATE BRIEF ABOUT POSSIBILITY OF TAXI ACROSS BOTH RWYS ON TXWY ALPHA; THEN DOUBLE BACK FROM THE SE TO RWY 05R; AND THAT KIND OF SET UP A MINDSET. THEN WE COULDN'T FIND TXWY AA AND WERE TRYING TO GET SECOND ENGINE STARTED AND LOOK AT 10-9 AND SAW TXWY A4 INSTEAD. WHILE OUR CROSSING THRU THE APCH PATH OF RWY 05R WOULD NOT HAVE CAUSED AN INCIDENT; IT WOULD HAVE AT THE VERY LEAST BEEN EMBARRASSING. AS HAPPENS; IT WAS HARD TO UNDERSTAND THE CTLR SINCE SHE WAS MIXING A LOT OF SPANISH WITH ENGLISH INSTRUCTIONS ALSO WHEN WORKING OTHER TFC. IT WOULD HAVE BEEN EASIER HAD CTLR CROSSED; THEN HELD US ON TXWY B2 AWAITING RWY 05R. TXWY B2 IS WIDE; AND WAS WIDE OPEN. IN THE END; CLRING FINAL RWY 05R VISUALLY; THE 'WHEN IN DOUBT; STOP' TECHNIQUE; AND AT LAST MINUTE BEING ABLE TO SEE THE TXWY AA SIGN (AMID ALL THE BARRIERS AND CONSTRUCTION GOING ON ON TXWY A1) IS WHAT RESOLVED THE SIT. GETTING THOSE MMMX ARPT PAGES RIGHT WOULD ALSO BE HELPFUL.SUPPLEMENTAL INFO FROM ACN 717279: INACCURATE CHART COMBINED WITH LANGUAGE BARRIER NEARLY RESULTED IN RWY INCURSION.CALLBACK CONVERSATION WITH RPTR ACN 717264 REVEALED THE FOLLOWING INFO: RPTR STATES AS OF 11/MON/06 NO UPDATE FROM COMPANY OR COMMERCIAL CHART PUBLISHER.

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