Narrative:

Coming into dfw we came in very close vicinity of another aircraft. We were in IFR conditions in and out of the clouds (mostly in). Regional approach had us at 6;000 ft and at 210 KTS; when we were given a turn to a heading of 270. There was a lot of rain in the area and flights were working around the weather. After making the turn and established on the heading the controller again said 'air carrier XXXX turn to a heading of 270.' we again read back the heading a second time thinking maybe he just forgot he had already gave it to us in a previous clearance. Shortly thereafter we heard the controller say something to the effect; 'air carrier XXXX I don't know where you are going; you have traffic; climb immediately to 7;000' and turn left to some heading. I could tell by the panic in his voice we were close to hitting someone. I pushed the throttle up and went from 6;000 to 7;000 ft in about 5 to 7 seconds. Both my first officer and I were wondering what happened; did we miss a call; take a turn meant for another aircraft or what? We were given vectors which amounted to a left 360 degree turn and told to intercept the ILS to 17C and cleared for the approach and to contact the tower. Nothing more was said. After parking at the gate I got the number for regional approach and called them and asked what happened still not sure if maybe we missed something. The supervisor was very nice and said three times it was a controller error and something about an another carrier's call sign that the controller got mixed up with ours. He did comment we did an excellent job and if we didn't climb as fast as we did the outcome could have been tragic. He said he had to file some kind of report on the controller and again thanked us for our good work. I saw some landing lights in the clouds but have no idea how close we really were. After talking to regional approach I then called my dispatcher and told him that we had what I would consider a near miss.

Google
 

Original NASA ASRS Text

Title: A DFW TRACON Controller confused air carrier call signs and erroneously issued a vector to an aircraft causing a conflict which was resolved by an urgent immediate climb clearance.

Narrative: Coming into DFW we came in very close vicinity of another aircraft. We were in IFR conditions in and out of the clouds (mostly in). Regional Approach had us at 6;000 FT and at 210 KTS; when we were given a turn to a heading of 270. There was a lot of rain in the area and flights were working around the weather. After making the turn and established on the heading the Controller again said 'Air Carrier XXXX turn to a heading of 270.' We again read back the heading a second time thinking maybe he just forgot he had already gave it to us in a previous clearance. Shortly thereafter we heard the Controller say something to the effect; 'Air Carrier XXXX I don't know where you are going; you have traffic; CLIMB IMMEDIATELY to 7;000' and turn left to some heading. I could tell by the panic in his voice we were close to hitting someone. I pushed the throttle up and went from 6;000 to 7;000 FT in about 5 to 7 seconds. Both my First Officer and I were wondering what happened; did we miss a call; take a turn meant for another aircraft or what? We were given vectors which amounted to a left 360 degree turn and told to intercept the ILS to 17C and cleared for the approach and to contact the Tower. Nothing more was said. After parking at the gate I got the number for Regional Approach and called them and asked what happened still not sure if maybe we missed something. The Supervisor was very nice and said three times it was a Controller error and something about an another carrier's call sign that the controller got mixed up with ours. He did comment we did an excellent job and if we didn't climb as fast as we did the outcome could have been tragic. He said he had to file some kind of report on the Controller and again thanked us for our good work. I saw some landing lights in the clouds but have no idea how close we really were. After talking to Regional Approach I then called my Dispatcher and told him that we had what I would consider a near miss.

Data retrieved from NASA's ASRS site as of April 2012 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.