MD80S on approach vectors. Call sign similar with another aircraft on same frequency. Controller got...

Attributes
ACN	363678
Time
Date	199703
Day	Tue
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : dfw
State Reference	TX
Altitude	msl bound lower : 4000 msl bound upper : 4000
Aircraft 1
Controlling Facilities	tracon : dfw
Operator	common carrier : air carrier
Make Model Name	MD-80 Super 80
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	363678
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : far non adherence : published procedure other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

At approximately XA35L we were told to expect ILS vectors for ILS runway 17R. While being vectored the approach was changed to ILS runway 18L. Shortly thereafter, we were told to maintain 4000 ft and vectored southeast. A new ATC frequency was assigned after radio contact was established. We were told to expect vectors back around for ILS runway 17R. At 15 NM established on the approach we were told to contact tower on 126.55. At 13 NM contact was established and we were cleared to land on runway 18L. I then asked for verification of the landing runway. The controller corrected himself and stated that we were cleared for landing on runway 17R. When I questioned him to the amount of confusion, he stated that flight xx had cut across our intended approach course resulting in our approach changes and additional vectors. Possibly the similar call signs resulted or added to the confusion. Considering prior approach control instructions there was a loss of confidence in the cockpit when tower cleared us to land on the west side while on ILS final for runway 17R. I suggest similar call signs be eliminated as soon as possible.

Original NASA ASRS Text

Title: MD80S ON APCH VECTORS. CALL SIGN SIMILAR WITH ANOTHER ACFT ON SAME FREQ. CTLR GOT 2 ACFT MIXED UP AND SWITCHED RWY ASSIGNMENTS SEVERAL TIMES.

Narrative: AT APPROX XA35L WE WERE TOLD TO EXPECT ILS VECTORS FOR ILS RWY 17R. WHILE BEING VECTORED THE APCH WAS CHANGED TO ILS RWY 18L. SHORTLY THEREAFTER, WE WERE TOLD TO MAINTAIN 4000 FT AND VECTORED SE. A NEW ATC FREQ WAS ASSIGNED AFTER RADIO CONTACT WAS ESTABLISHED. WE WERE TOLD TO EXPECT VECTORS BACK AROUND FOR ILS RWY 17R. AT 15 NM ESTABLISHED ON THE APCH WE WERE TOLD TO CONTACT TWR ON 126.55. AT 13 NM CONTACT WAS ESTABLISHED AND WE WERE CLRED TO LAND ON RWY 18L. I THEN ASKED FOR VERIFICATION OF THE LNDG RWY. THE CTLR CORRECTED HIMSELF AND STATED THAT WE WERE CLRED FOR LNDG ON RWY 17R. WHEN I QUESTIONED HIM TO THE AMOUNT OF CONFUSION, HE STATED THAT FLT XX HAD CUT ACROSS OUR INTENDED APCH COURSE RESULTING IN OUR APCH CHANGES AND ADDITIONAL VECTORS. POSSIBLY THE SIMILAR CALL SIGNS RESULTED OR ADDED TO THE CONFUSION. CONSIDERING PRIOR APCH CTL INSTRUCTIONS THERE WAS A LOSS OF CONFIDENCE IN THE COCKPIT WHEN TWR CLRED US TO LAND ON THE W SIDE WHILE ON ILS FINAL FOR RWY 17R. I SUGGEST SIMILAR CALL SIGNS BE ELIMINATED ASAP.

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.

MD80S on approach vectors. Call sign similar with another aircraft on same frequency. Controller got 2 aircraft mixed up and switched runway assignments several times.