An MD80 crew followed a clearance for another aircraft with a similar call sign at stl.

Attributes
ACN	496774
Time
Date	200103
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : stl.airport
State Reference	MO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : stl.tower
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp pilot : cfi
Experience	flight time last 90 days : 100 flight time total : 9000 flight time type : 100
ASRS Report	496774
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance Airport
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While waiting behind company MD80 at intersection right (stl airport) we heard them cleared across runway 30L. Next we heard, 'a-B-C cleared across runway 30L.' my first officer announced 'air carrier X, abc cleared across runway 30L.' we visually cleared left and right for traffic and started across the hold short line. The controller stated 'air carrier X expedite across runway 30L, previous clearance was for air carrier Y.' I inquired about us definitely being cleared across runway 30L and if there were conflicting call signs. The controller stated that crossing clearance was for 'air carrier Y, xabc' but he had 'coordinated our crossing with the tower when he saw us moving. Possibly the air carrier Y, X' of 'air carrier Y, xabc' was blocked by our company traffic crossing before us. After their crossing instructions, we heard just 'abc cleared across runway 30L.' we assumed it was meant for us (air carrier X, abc) as we were next at intersection right. We did visually clear the runway for potential traffic and there was not any conflict.

Original NASA ASRS Text

Title: AN MD80 CREW FOLLOWED A CLRNC FOR ANOTHER ACFT WITH A SIMILAR CALL SIGN AT STL.

Narrative: WHILE WAITING BEHIND COMPANY MD80 AT INTXN R (STL ARPT) WE HEARD THEM CLRED ACROSS RWY 30L. NEXT WE HEARD, 'A-B-C CLRED ACROSS RWY 30L.' MY FO ANNOUNCED 'ACR X, ABC CLRED ACROSS RWY 30L.' WE VISUALLY CLRED L AND R FOR TFC AND STARTED ACROSS THE HOLD SHORT LINE. THE CTLR STATED 'ACR X EXPEDITE ACROSS RWY 30L, PREVIOUS CLRNC WAS FOR ACR Y.' I INQUIRED ABOUT US DEFINITELY BEING CLRED ACROSS RWY 30L AND IF THERE WERE CONFLICTING CALL SIGNS. THE CTLR STATED THAT XING CLRNC WAS FOR 'ACR Y, XABC' BUT HE HAD 'COORDINATED OUR XING WITH THE TWR WHEN HE SAW US MOVING. POSSIBLY THE ACR Y, X' OF 'ACR Y, XABC' WAS BLOCKED BY OUR COMPANY TFC XING BEFORE US. AFTER THEIR XING INSTRUCTIONS, WE HEARD JUST 'ABC CLRED ACROSS RWY 30L.' WE ASSUMED IT WAS MEANT FOR US (ACR X, ABC) AS WE WERE NEXT AT INTXN R. WE DID VISUALLY CLR THE RWY FOR POTENTIAL TFC AND THERE WAS NOT ANY CONFLICT.

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.