Narrative:

We were on a flight from atl to tys at night running on schedule. We were being vectored for a VOR runway 23L approach. WX was not a factor, visibility was 7 mi. I suggested to the controller that if he would vector us closer to the airport I would accept a visual approach. He did this and a short time later, asked if we had the field in sight. We did and a short time later he cleared us visual to runway 23R (no mention of traffic). He asked us to call our base turn. Due to workload of configuring the aircraft and radio talk we were late making the call. At this point we were both aware that he was working another aircraft on another frequency but we were not aware that this aircraft would pose any conflict since we did not have him in sight (an air carrier Y commuter). As we began our turn to final the controller pointed out the traffic at 1 O'clock position. My copilot acknowledged the traffic and said 'confirm you want us on the left now.' he said this for 2 reasons. One, to get the controller straightened out on which runway we were cleared to, and two, to let me know that we now needed to be lining up for the left. There was no immediate response from the tower. To add to the confusion, I had missed the call about the traffic. All I heard was 'confirm you want us on the left.' all I knew at this point was that there was a conflict over which runway we were to land on, not even realizing that there was another aircraft on final that was a potential conflict. When the TCASII traffic went off followed 3 seconds later by the RA 'climb' I simply executed the RA and aborted the approach. Following the RA I leveled my wings and commenced an immediate climb. The result was that our aircraft crossed the flight path of the commuter aircraft. My copilot was able to keep the aircraft in sight until we were clear of conflict. At no time did we believe that we would collide with the other aircraft.

Google
 

Original NASA ASRS Text

Title: NMAC BTWN AN MD88 TURNING FINAL FROM A VISUAL BASE LEG AND A DORNIER, DO228 ON APCH TO THE SAME PARALLEL RWY. RPTR ABORTED APCH AND BEGAN TO CLB IN RESPONSE TO A TCASII RA.

Narrative: WE WERE ON A FLT FROM ATL TO TYS AT NIGHT RUNNING ON SCHEDULE. WE WERE BEING VECTORED FOR A VOR RWY 23L APCH. WX WAS NOT A FACTOR, VISIBILITY WAS 7 MI. I SUGGESTED TO THE CTLR THAT IF HE WOULD VECTOR US CLOSER TO THE ARPT I WOULD ACCEPT A VISUAL APCH. HE DID THIS AND A SHORT TIME LATER, ASKED IF WE HAD THE FIELD IN SIGHT. WE DID AND A SHORT TIME LATER HE CLRED US VISUAL TO RWY 23R (NO MENTION OF TFC). HE ASKED US TO CALL OUR BASE TURN. DUE TO WORKLOAD OF CONFIGURING THE ACFT AND RADIO TALK WE WERE LATE MAKING THE CALL. AT THIS POINT WE WERE BOTH AWARE THAT HE WAS WORKING ANOTHER ACFT ON ANOTHER FREQ BUT WE WERE NOT AWARE THAT THIS ACFT WOULD POSE ANY CONFLICT SINCE WE DID NOT HAVE HIM IN SIGHT (AN ACR Y COMMUTER). AS WE BEGAN OUR TURN TO FINAL THE CTLR POINTED OUT THE TFC AT 1 O'CLOCK POS. MY COPLT ACKNOWLEDGED THE TFC AND SAID 'CONFIRM YOU WANT US ON THE L NOW.' HE SAID THIS FOR 2 REASONS. ONE, TO GET THE CTLR STRAIGHTENED OUT ON WHICH RWY WE WERE CLRED TO, AND TWO, TO LET ME KNOW THAT WE NOW NEEDED TO BE LINING UP FOR THE L. THERE WAS NO IMMEDIATE RESPONSE FROM THE TWR. TO ADD TO THE CONFUSION, I HAD MISSED THE CALL ABOUT THE TFC. ALL I HEARD WAS 'CONFIRM YOU WANT US ON THE L.' ALL I KNEW AT THIS POINT WAS THAT THERE WAS A CONFLICT OVER WHICH RWY WE WERE TO LAND ON, NOT EVEN REALIZING THAT THERE WAS ANOTHER ACFT ON FINAL THAT WAS A POTENTIAL CONFLICT. WHEN THE TCASII TFC WENT OFF FOLLOWED 3 SECONDS LATER BY THE RA 'CLB' I SIMPLY EXECUTED THE RA AND ABORTED THE APCH. FOLLOWING THE RA I LEVELED MY WINGS AND COMMENCED AN IMMEDIATE CLB. THE RESULT WAS THAT OUR ACFT CROSSED THE FLT PATH OF THE COMMUTER ACFT. MY COPLT WAS ABLE TO KEEP THE ACFT IN SIGHT UNTIL WE WERE CLR OF CONFLICT. AT NO TIME DID WE BELIEVE THAT WE WOULD COLLIDE WITH THE OTHER ACFT.

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.