Narrative:

On approach to atlanta, we were directed to descend to 11000 ft as we leveled, approach gave us a left turn to approximately east (atl landing west, we were on rome arrival). An aircraft on departure climbing to 10000 triggered a TCASII RA. We climbed to 11300 before getting a visual on the traffic and returning to 11000. We advised the controller that we had experienced a TCASII RA. I have seen this exact scenario in dallas at dfw. TCASII doesn't know the departing traffic is going to level at 10000 so it projects a conflict with arriving traffic at 11000. If ATC does not provide more horizontal or vertical separation between arriving and departing traffic, these annoying TCASII RA's will induce pilots to start turning the system off in the air traffic area where it is most likely to save us from having an accident.

Google
 

Original NASA ASRS Text

Title: ACR MLG ALTDEV EXCURSION FROM CLRNC ALT IN RESPONSE TO TCASII RA.

Narrative: ON APCH TO ATLANTA, WE WERE DIRECTED TO DSND TO 11000 FT AS WE LEVELED, APCH GAVE US A L TURN TO APPROX E (ATL LNDG W, WE WERE ON ROME ARR). AN ACFT ON DEP CLBING TO 10000 TRIGGERED A TCASII RA. WE CLBED TO 11300 BEFORE GETTING A VISUAL ON THE TFC AND RETURNING TO 11000. WE ADVISED THE CTLR THAT WE HAD EXPERIENCED A TCASII RA. I HAVE SEEN THIS EXACT SCENARIO IN DALLAS AT DFW. TCASII DOESN'T KNOW THE DEPARTING TFC IS GOING TO LEVEL AT 10000 SO IT PROJECTS A CONFLICT WITH ARRIVING TFC AT 11000. IF ATC DOES NOT PROVIDE MORE HORIZ OR VERT SEPARATION BTWN ARRIVING AND DEPARTING TFC, THESE ANNOYING TCASII RA'S WILL INDUCE PLTS TO START TURNING THE SYS OFF IN THE ATA WHERE IT IS MOST LIKELY TO SAVE US FROM HAVING AN ACCIDENT.

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.