Similar sounding call signs create problem with unauthorized runway crossing.

Attributes
ACN	272022
Time
Date	199405
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dfw
State Reference	TX
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	ground other : taxi
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : cfi pilot : atp
Experience	flight time last 90 days : 90 flight time total : 7500 flight time type : 750
ASRS Report	272022
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 8000 flight time type : 2500
ASRS Report	271884
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were air carrier a xyz landed runway 13R and cleared to taxi on a to 32 to hold short of runway 18R and monitor tower 124.15. Air carrier B xyz was on tower frequency landing 18R. Approach had issued us a warning of identical call sign numbers. While holding short, I went off frequency to confirm our gate -- captain stayed on tower frequency. I came back on and we continued to hold. Tower frequency was very busy -nonstop instructions. I heard, 'air carrier a xyz cross 18R contact ground 121.8.' the captain taxied across runway 18R as I acknowledged 'air carrier a xyz.' I then realized the instructions were probably wrong because we needed to stay on tower 124.15 to cross 18L. Tower called to see if we were still on frequency. I said, 'roger.' tower said they had intended for air carrier B xyz to cross. Air carrier B, holding on taxiway 29 between 18R and 18L, had not responded or moved. The captain and I agreed we had heard 'air carrier a xyz.' tower frequency was very busy -- nonstop tower talk with quick acknowledgments by aircraft. We called tower on the landline at their request. They said the controller and 2 supervisors agreed the call was air carrier B xyz not air carrier a xyz. They later said the tower tape recording confirmed this. 1) why did no one hear 'air carrier a' respond versus 'air carrier B'? 2) a review of the tape will reveal loud backgnd noise in the tower -- other controllers, call signs, and controllers talking to each other, supervisors including discussion of the 2 air carrier B and air carrier a xyz call signs, all on tower 124.15 frequency. 3) as first officer I should have remained on frequency and not contacted the gate even though controller pressure you to have your gate information as soon as you talk to ground. 4) as first officer, I should have questioned the taxi clearance part about contacting ground. If I had been 100 percent in the loop, I would have caught this as inappropriate for our position. 5) tower suggested in conversation with captain room for improvement by all parties and said they did not intend to pursue the incident further with air carrier a xyz.

Original NASA ASRS Text

Title: SIMILAR SOUNDING CALL SIGNS CREATE PROB WITH UNAUTH RWY XING.

Narrative: WE WERE ACR A XYZ LANDED RWY 13R AND CLRED TO TAXI ON A TO 32 TO HOLD SHORT OF RWY 18R AND MONITOR TWR 124.15. ACR B XYZ WAS ON TWR FREQ LNDG 18R. APCH HAD ISSUED US A WARNING OF IDENTICAL CALL SIGN NUMBERS. WHILE HOLDING SHORT, I WENT OFF FREQ TO CONFIRM OUR GATE -- CAPT STAYED ON TWR FREQ. I CAME BACK ON AND WE CONTINUED TO HOLD. TWR FREQ WAS VERY BUSY -NONSTOP INSTRUCTIONS. I HEARD, 'ACR A XYZ CROSS 18R CONTACT GND 121.8.' THE CAPT TAXIED ACROSS RWY 18R AS I ACKNOWLEDGED 'ACR A XYZ.' I THEN REALIZED THE INSTRUCTIONS WERE PROBABLY WRONG BECAUSE WE NEEDED TO STAY ON TWR 124.15 TO CROSS 18L. TWR CALLED TO SEE IF WE WERE STILL ON FREQ. I SAID, 'ROGER.' TWR SAID THEY HAD INTENDED FOR ACR B XYZ TO CROSS. ACR B, HOLDING ON TXWY 29 BTWN 18R AND 18L, HAD NOT RESPONDED OR MOVED. THE CAPT AND I AGREED WE HAD HEARD 'ACR A XYZ.' TWR FREQ WAS VERY BUSY -- NONSTOP TWR TALK WITH QUICK ACKNOWLEDGMENTS BY ACFT. WE CALLED TWR ON THE LANDLINE AT THEIR REQUEST. THEY SAID THE CTLR AND 2 SUPVRS AGREED THE CALL WAS ACR B XYZ NOT ACR A XYZ. THEY LATER SAID THE TWR TAPE RECORDING CONFIRMED THIS. 1) WHY DID NO ONE HEAR 'ACR A' RESPOND VERSUS 'ACR B'? 2) A REVIEW OF THE TAPE WILL REVEAL LOUD BACKGND NOISE IN THE TWR -- OTHER CTLRS, CALL SIGNS, AND CTLRS TALKING TO EACH OTHER, SUPVRS INCLUDING DISCUSSION OF THE 2 ACR B AND ACR A XYZ CALL SIGNS, ALL ON TWR 124.15 FREQ. 3) AS FO I SHOULD HAVE REMAINED ON FREQ AND NOT CONTACTED THE GATE EVEN THOUGH CTLR PRESSURE YOU TO HAVE YOUR GATE INFO AS SOON AS YOU TALK TO GND. 4) AS FO, I SHOULD HAVE QUESTIONED THE TAXI CLRNC PART ABOUT CONTACTING GND. IF I HAD BEEN 100 PERCENT IN THE LOOP, I WOULD HAVE CAUGHT THIS AS INAPPROPRIATE FOR OUR POS. 5) TWR SUGGESTED IN CONVERSATION WITH CAPT ROOM FOR IMPROVEMENT BY ALL PARTIES AND SAID THEY DID NOT INTEND TO PURSUE THE INCIDENT FURTHER WITH ACR A XYZ.

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.