Narrative:

I landed the aircraft on runway 18R and the captain cleared the runway at taxiway 29. Tower cleared us across runway 18L and told us to contact ground control on 121.8. Ground control told us to 'turn right on the outer taxiway (foxtrot) and then left on 31 and contact ground control on the east side of the airport on top of the 31 bridge.' as we taxied south on foxtrot, the captain began to slow the aircraft as he was looking left in preparation for the left turn from foxtrot onto 31. Just prior to turning, I observed another md-88 clearing runway 18L on taxiway 31. The other aircraft was not slowing down and had not contacted ground on 121.8. I told the captain that the other aircraft was coming fast and did not appear to be slowing to a stop. The captain immediately stopped the aircraft prior to taxiway 31. The other aircraft finally stopped (after veering to the right) and well into the intersection at foxtrot and 31. Ground control called us after we had stopped and stated he was not in contact with the other aircraft. The other aircraft pilot immediately stated he had priority since he was crossing runway 18L. Ground control told him he did not have priority and that he had not checked in after crossing the runway. Ground control told the other aircraft to continue taxiing, and for us to follow him on taxiway 31. Possible causes: 1) the other aircraft mistakenly thought he had priority. 2) late at night dfw tower will often clear an aircraft across runway 18L and have the aircraft contact ground control east on top of the 31 bridge. This normally is done when the tower controller is controling landing and taxiing aircraft on his side of the airport. 3) the other aircraft was on the wrong radio frequency. 4) the other aircraft did not see us. If we had not stopped our aircraft prior taxiway 31, the other aircraft would like have hit us. As it was, neither aircraft was closer than 100 ft.

Google
 

Original NASA ASRS Text

Title: RPTR'S TAXI PATH WAS VIOLATED BY ANOTHER ACFT WITHOUT CLRNC AND ON THE WRONG FREQ.

Narrative: I LANDED THE ACFT ON RWY 18R AND THE CAPT CLRED THE RWY AT TXWY 29. TWR CLRED US ACROSS RWY 18L AND TOLD US TO CONTACT GND CTL ON 121.8. GND CTL TOLD US TO 'TURN R ON THE OUTER TXWY (FOXTROT) AND THEN L ON 31 AND CONTACT GND CTL ON THE E SIDE OF THE ARPT ON TOP OF THE 31 BRIDGE.' AS WE TAXIED S ON FOXTROT, THE CAPT BEGAN TO SLOW THE ACFT AS HE WAS LOOKING L IN PREPARATION FOR THE L TURN FROM FOXTROT ONTO 31. JUST PRIOR TO TURNING, I OBSERVED ANOTHER MD-88 CLRING RWY 18L ON TXWY 31. THE OTHER ACFT WAS NOT SLOWING DOWN AND HAD NOT CONTACTED GND ON 121.8. I TOLD THE CAPT THAT THE OTHER ACFT WAS COMING FAST AND DID NOT APPEAR TO BE SLOWING TO A STOP. THE CAPT IMMEDIATELY STOPPED THE ACFT PRIOR TO TXWY 31. THE OTHER ACFT FINALLY STOPPED (AFTER VEERING TO THE R) AND WELL INTO THE INTXN AT FOXTROT AND 31. GND CTL CALLED US AFTER WE HAD STOPPED AND STATED HE WAS NOT IN CONTACT WITH THE OTHER ACFT. THE OTHER ACFT PLT IMMEDIATELY STATED HE HAD PRIORITY SINCE HE WAS XING RWY 18L. GND CTL TOLD HIM HE DID NOT HAVE PRIORITY AND THAT HE HAD NOT CHKED IN AFTER XING THE RWY. GND CTL TOLD THE OTHER ACFT TO CONTINUE TAXIING, AND FOR US TO FOLLOW HIM ON TXWY 31. POSSIBLE CAUSES: 1) THE OTHER ACFT MISTAKENLY THOUGHT HE HAD PRIORITY. 2) LATE AT NIGHT DFW TWR WILL OFTEN CLR AN ACFT ACROSS RWY 18L AND HAVE THE ACFT CONTACT GND CTL E ON TOP OF THE 31 BRIDGE. THIS NORMALLY IS DONE WHEN THE TWR CTLR IS CTLING LNDG AND TAXIING ACFT ON HIS SIDE OF THE ARPT. 3) THE OTHER ACFT WAS ON THE WRONG RADIO FREQ. 4) THE OTHER ACFT DID NOT SEE US. IF WE HAD NOT STOPPED OUR ACFT PRIOR TXWY 31, THE OTHER ACFT WOULD LIKE HAVE HIT US. AS IT WAS, NEITHER ACFT WAS CLOSER THAN 100 FT.

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.