Narrative:

On arrival to boston, requested runway 22 instead of runway 27. Was given vectors (020 degree heading) and descent to 6000 ft. Aircraft at 11000 ft told to slow, amend altitude to 7000 ft. Started descent. Received TCASII TA followed by RA. First officer flying, saw other aircraft climbing. Other aircraft (B737) made turn away from us. I talked to TRACON supervisor in boston. He was aware of incident and investigating. I feel that my request to the runway 22 changed their arrival plan to runway 27 and they did not adjust departing traffic properly. Supplemental information from acn 409195: saw other aircraft, looked at TCASII, showed 10000 ft climbing. Other aircraft queried ATC, said they saw us and would maintain visual. I stopped our descent and maintained visual. Other aircraft made left turn and stopped their climb. Supplemental information from acn 409559: passing approximately 10000 ft when the first officer verbalized that traffic on TCASII was appearing to close on us. We then heard the approaching traffic query about traffic (us) at their 12 O'clock position. ATC asked if they had us visually and they responded yes. ATC then told them to maintain visual separation. We had visual on the traffic and they were turning away from us, so we did not change course. We were on vectors. My best guess is the other aircraft was off course or ATC failed to recognize the traffic conflict in a timely fashion. Supplemental information from acn 409031: we spotted an L1011 at 11 O'clock, left to right, at 11000 ft descending. An immediate evasive maneuver to avoid collision was taken: 45 degree left bank, descending turn to 9500 ft. ATC notified/ conflict resolved. Supplemental information from acn 408889: I was on a combined position and did not notice the conflict until B737 pilot made a comment about it.

Google
 

Original NASA ASRS Text

Title: ACR L1011 FLC DSNDING ON VECTORS FOR SEQUENCED APCH OBSERVED A TCASII TA RA. FLC OBSERVED CLBING B737 INITIATING EVASIVE TURN AND DSCNT. B737 FLC BROUGHT EVASIVE ACTIONS TO APCH CTLR'S ATTN, WHO TRIED TO APPLY VISUAL SEPARATION. ACTIONS INSUFFICIENT AND NOT TIMELY TO MAINTAIN STANDARD SEPARATION CRITERIA.

Narrative: ON ARR TO BOSTON, REQUESTED RWY 22 INSTEAD OF RWY 27. WAS GIVEN VECTORS (020 DEG HDG) AND DSCNT TO 6000 FT. ACFT AT 11000 FT TOLD TO SLOW, AMEND ALT TO 7000 FT. STARTED DSCNT. RECEIVED TCASII TA FOLLOWED BY RA. FO FLYING, SAW OTHER ACFT CLBING. OTHER ACFT (B737) MADE TURN AWAY FROM US. I TALKED TO TRACON SUPVR IN BOSTON. HE WAS AWARE OF INCIDENT AND INVESTIGATING. I FEEL THAT MY REQUEST TO THE RWY 22 CHANGED THEIR ARR PLAN TO RWY 27 AND THEY DID NOT ADJUST DEPARTING TFC PROPERLY. SUPPLEMENTAL INFO FROM ACN 409195: SAW OTHER ACFT, LOOKED AT TCASII, SHOWED 10000 FT CLBING. OTHER ACFT QUERIED ATC, SAID THEY SAW US AND WOULD MAINTAIN VISUAL. I STOPPED OUR DSCNT AND MAINTAINED VISUAL. OTHER ACFT MADE L TURN AND STOPPED THEIR CLB. SUPPLEMENTAL INFO FROM ACN 409559: PASSING APPROX 10000 FT WHEN THE FO VERBALIZED THAT TFC ON TCASII WAS APPEARING TO CLOSE ON US. WE THEN HEARD THE APCHING TFC QUERY ABOUT TFC (US) AT THEIR 12 O'CLOCK POS. ATC ASKED IF THEY HAD US VISUALLY AND THEY RESPONDED YES. ATC THEN TOLD THEM TO MAINTAIN VISUAL SEPARATION. WE HAD VISUAL ON THE TFC AND THEY WERE TURNING AWAY FROM US, SO WE DID NOT CHANGE COURSE. WE WERE ON VECTORS. MY BEST GUESS IS THE OTHER ACFT WAS OFF COURSE OR ATC FAILED TO RECOGNIZE THE TFC CONFLICT IN A TIMELY FASHION. SUPPLEMENTAL INFO FROM ACN 409031: WE SPOTTED AN L1011 AT 11 O'CLOCK, L TO R, AT 11000 FT DSNDING. AN IMMEDIATE EVASIVE MANEUVER TO AVOID COLLISION WAS TAKEN: 45 DEG L BANK, DSNDING TURN TO 9500 FT. ATC NOTIFIED/ CONFLICT RESOLVED. SUPPLEMENTAL INFO FROM ACN 408889: I WAS ON A COMBINED POS AND DID NOT NOTICE THE CONFLICT UNTIL B737 PLT MADE A COMMENT ABOUT IT.

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.