Narrative:

Our flight landed on runway 13R and was told to taxi up to and hold short of runway 18R on taxiway 32, and stay on tower frequency. I inadvertently crossed runway 18R and stopped short of taxiway east which is between runway 18L and runway 18R and parallel to those runways. During this time an aircraft was taxiing south on taxiway east and both aircraft came to a stop at the intersection of taxiway east and taxiway 32. The tower asked if we were short of taxiway east. After we responded, we were told to give way to the aircraft on taxiway east and taxi across runway 18L and contact ground. I believe this event was caused due to the fatigue of a long and late flying day associated with the stress of holding for thunderstorms north of the airport and then navigation between these storms on descent. Also during the descent we were distraction by an unusual amount of ACARS messages in the form of sigmets about these same storms. These messages were being received even during landing and taxi in along with a very heavily congested tower frequency. In addition to this, the tower operator was also reading these same sigmets over the air, which added to some confusion and distraction. Also we were not told about the aircraft on taxiway east and as a result I judged that aircraft to be rolling out on runway 18R and was using that aircraft as a reference for holding short of runway 18R. In doing so I found myself to be on and crossing runway 18R. Rather than stop and block runway 18R I crossed and held short of taxiway east well clear of runway 18R. I feel if the tower would of had time to tell us about the aircraft on taxiway east that might have helped to avoid this event. Also I feel that 10 or 12 ACARS messages in a 15 min period is very distraction to the crew during critical phases of flight and taxiing on a congested airport.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLT CREW OF ACR LGT AT DFW CROSSES RWY THEY WERE TOLD TO HOLD SHORT OF AFTER THEIR LNDG DUE TO FATIGUE AND HIGH WORKLOAD IN ADVERSE WX.

Narrative: OUR FLT LANDED ON RWY 13R AND WAS TOLD TO TAXI UP TO AND HOLD SHORT OF RWY 18R ON TXWY 32, AND STAY ON TWR FREQ. I INADVERTENTLY CROSSED RWY 18R AND STOPPED SHORT OF TXWY E WHICH IS BTWN RWY 18L AND RWY 18R AND PARALLEL TO THOSE RWYS. DURING THIS TIME AN ACFT WAS TAXIING S ON TXWY E AND BOTH ACFT CAME TO A STOP AT THE INTXN OF TXWY E AND TXWY 32. THE TWR ASKED IF WE WERE SHORT OF TXWY E. AFTER WE RESPONDED, WE WERE TOLD TO GIVE WAY TO THE ACFT ON TXWY E AND TAXI ACROSS RWY 18L AND CONTACT GND. I BELIEVE THIS EVENT WAS CAUSED DUE TO THE FATIGUE OF A LONG AND LATE FLYING DAY ASSOCIATED WITH THE STRESS OF HOLDING FOR TSTMS N OF THE ARPT AND THEN NAV BTWN THESE STORMS ON DSNT. ALSO DURING THE DSNT WE WERE DISTR BY AN UNUSUAL AMOUNT OF ACARS MESSAGES IN THE FORM OF SIGMETS ABOUT THESE SAME STORMS. THESE MESSAGES WERE BEING RECEIVED EVEN DURING LNDG AND TAXI IN ALONG WITH A VERY HEAVILY CONGESTED TWR FREQ. IN ADDITION TO THIS, THE TWR OPERATOR WAS ALSO READING THESE SAME SIGMETS OVER THE AIR, WHICH ADDED TO SOME CONFUSION AND DISTR. ALSO WE WERE NOT TOLD ABOUT THE ACFT ON TXWY E AND AS A RESULT I JUDGED THAT ACFT TO BE ROLLING OUT ON RWY 18R AND WAS USING THAT ACFT AS A REFERENCE FOR HOLDING SHORT OF RWY 18R. IN DOING SO I FOUND MYSELF TO BE ON AND XING RWY 18R. RATHER THAN STOP AND BLOCK RWY 18R I CROSSED AND HELD SHORT OF TXWY E WELL CLR OF RWY 18R. I FEEL IF THE TWR WOULD OF HAD TIME TO TELL US ABOUT THE ACFT ON TXWY E THAT MIGHT HAVE HELPED TO AVOID THIS EVENT. ALSO I FEEL THAT 10 OR 12 ACARS MESSAGES IN A 15 MIN PERIOD IS VERY DISTR TO THE CREW DURING CRITICAL PHASES OF FLT AND TAXIING ON A CONGESTED ARPT.

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.