Narrative:

After landing on runway pl at ZZZ, we cleared onto taxiway a, tower advised to give way to an aircraft Y on taxiway B and to hold short runway pc for departure contact ground on 123.0 on taxiway a after crossing runway pc. My first officer read back clearance to cross runway pc and to contact ground on 123.0 on taxiway a as we were crossing runway pc. I heard tower tell aircraft Z to abort takeoff. I saw aircraft coming and added power to finish crossing as fast as possible. Aircraft Z continued the takeoff and was airborne well before taxiway a by 100 - 200 ft and my aircraft was stopped on the taxiway at the intersection of taxiway a and B, well clear of active runway. We were told to contact ground on 123.0 and continued taxi to gate. ATC never said any more about incident, and did not ask us to make contact by phone. Communications were very busy and confusing at the time, several jammed transmissions added to confusion. I asked the first officer if he was sure we were cleared to cross and he said it was. Supplemental information from acn 508160: we were starting to cross runway pc and we see departing traffic on runway pc. The tower controller panicked and told us to expedite across runway pc and he cancelled the takeoff clearance for the departing traffic. I heard and read back tower instructions. The same tower controller was handling too much traffic and the airport was very busy. Callback conversation with reporter revealed the following information: reporter stated after the incident he filed a report with his chief pilot. He said the chief pilot discussed the incident with the facility manager and was told that an operational error may have occurred.

Related reports:

Google
 

Original NASA ASRS Text

Title: AFTER LNDG AT ZZZ, CREW READS BACK TAXI INSTRUCTIONS INCORRECTLY AND CROSS RWY WHILE TFC IS DEPARTING.

Narrative: AFTER LANDING ON RWY PL AT ZZZ, WE CLRED ONTO TXWY A, TWR ADVISED TO GIVE WAY TO AN ACFT Y ON TXWY B AND TO HOLD SHORT RWY PC FOR DEP CONTACT GND ON 123.0 ON TXWY A AFTER CROSSING RWY PC. MY FO READ BACK CLRNC TO CROSS RWY PC AND TO CONTACT GND ON 123.0 ON TXWY A AS WE WERE CROSSING RWY PC. I HEARD TWR TELL ACFT Z TO ABORT TKOF. I SAW ACFT COMING AND ADDED POWER TO FINISH CROSSING AS FAST AS POSSIBLE. ACFT Z CONTINUED THE TKOF AND WAS AIRBORNE WELL BEFORE TXWY A BY 100 - 200 FT AND MY ACFT WAS STOPPED ON THE TXWY AT THE INTERSECTION OF TXWY A AND B, WELL CLEAR OF ACTIVE RWY. WE WERE TOLD TO CONTACT GND ON 123.0 AND CONTINUED TAXI TO GATE. ATC NEVER SAID ANY MORE ABOUT INCIDENT, AND DID NOT ASK US TO MAKE CONTACT BY PHONE. COMMUNICATIONS WERE VERY BUSY AND CONFUSING AT THE TIME, SEVERAL JAMMED TRANSMISSIONS ADDED TO CONFUSION. I ASKED THE FO IF HE WAS SURE WE WERE CLRED TO CROSS AND HE SAID IT WAS. SUPPLEMENTAL INFO FROM ACN 508160: WE WERE STARTING TO CROSS RWY PC AND WE SEE DEPARTING TFC ON RWY PC. THE TWR CTLR PANICKED AND TOLD US TO EXPEDITE ACROSS RWY PC AND HE CANCELLED THE TAKEOFF CLRNC FOR THE DEPARTING TFC. I HEARD AND READ BACK TWR INSTRUCTIONS. THE SAME TWR CTLR WAS HANDLING TOO MUCH TFC AND THE ARPT WAS VERY BUSY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED AFTER THE INCIDENT HE FILED A RPT WITH HIS CHIEF PLT. HE SAID THE CHIEF PLT DISCUSSED THE INCIDENT WITH THE FACILITY MANAGER AND WAS TOLD THAT AN OPERATIONAL ERROR MAY HAVE OCCURRED.

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.