An A320 flight crew accepts a position and hold clearance meant for another aircraft at dtw, mi.

Attributes
ACN	534751
Time
Date	200201
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dtw.airport
State Reference	MI
Altitude	agl single value : 0
Environment
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : dtw.tower
Operator	common carrier : air carrier
Make Model Name	DC-9 30
Operating Under FAR Part	Part 121
Flight Phase	ground : position and hold ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 270 flight time total : 10000
ASRS Report	534751
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 80 flight time total : 15000 flight time type : 2400
ASRS Report	534752
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : took precautionary avoidance action other
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airport Company Flight Crew Human Performance ATC Human Performance Aircraft
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While waiting for takeoff at dtw runway 3L, the captain and I heard clearance to taxi into position and hold by dtw tower controller. I replied back with 'taxi into position and hold runway 3L.' while taxiing toward the runway, we saw a DC9 approaching the runway from the other side. We stopped and then heard clearance from the tower for them to take off. We queried the dtw tower controller about our taxi into position and hold clearance. Controller replied we had no such clearance. We held our position and then were cleared for takeoff after the DC9 departed. There was no conflict. In our analysis, we suspect a communication breakdown. We think the other aircraft (DC9) and us responded at the same time when replying to taxi into position and hold, therefore, blocking out each other's radio call. We also had an ACARS weight data change during the time this miscom took place, adding a distraction to the situation.

Original NASA ASRS Text

Title: AN A320 FLC ACCEPTS A POS AND HOLD CLRNC MEANT FOR ANOTHER ACFT AT DTW, MI.

Narrative: WHILE WAITING FOR TKOF AT DTW RWY 3L, THE CAPT AND I HEARD CLRNC TO TAXI INTO POS AND HOLD BY DTW TWR CTLR. I REPLIED BACK WITH 'TAXI INTO POS AND HOLD RWY 3L.' WHILE TAXIING TOWARD THE RWY, WE SAW A DC9 APCHING THE RWY FROM THE OTHER SIDE. WE STOPPED AND THEN HEARD CLRNC FROM THE TWR FOR THEM TO TAKE OFF. WE QUERIED THE DTW TWR CTLR ABOUT OUR TAXI INTO POS AND HOLD CLRNC. CTLR REPLIED WE HAD NO SUCH CLRNC. WE HELD OUR POS AND THEN WERE CLRED FOR TKOF AFTER THE DC9 DEPARTED. THERE WAS NO CONFLICT. IN OUR ANALYSIS, WE SUSPECT A COM BREAKDOWN. WE THINK THE OTHER ACFT (DC9) AND US RESPONDED AT THE SAME TIME WHEN REPLYING TO TAXI INTO POS AND HOLD, THEREFORE, BLOCKING OUT EACH OTHER'S RADIO CALL. WE ALSO HAD AN ACARS WT DATA CHANGE DURING THE TIME THIS MISCOM TOOK PLACE, ADDING A DISTR TO THE SIT.

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.