Narrative:

We departed phx on time. ATC clearance was SJN5 SID. After takeoff; ATC cleared us direct forpe intersection; about 080 deg heading; and climb to FL210 (not exactly sure of altitude). It was VFR; clear and great visibility; altimeter 29.93. Passing about 11;000 ft; I saw a target on the TCAS display. Target was inside the 6 mile scale; about 1;000 ft above; level; at 11:00-12:00. I then realized that I may need to initiate evasive maneuvering. ATC then transmitted to both aircraft traffic advisories. ATC called out our traffic less than 5 miles; 12:00; at 12;000 ft. Our TCAS now showed 600-800 ft above at 12:00. Conflicting aircraft confirmed and said he had us in sight. We did not see him yet. ATC did not give us any directions to de-conflict. We were climbing at climb power and about 2;000 FPM. Shortly after the ATC traffic advisory; the TCAS RA alert went off to descend. Since I had already thought about needing to take evasive action; I immediately disconnected the autopilot and transitioned from a climb to a descent (TCAS vsi showed to descend at 1;000 FPM). Still looking for a visual on the traffic with no luck; the TCAS RA alert changed to increase descent; which showed 1;500 FPM vsi now. I then visually sighted the traffic; nose on; just above the horizon; appearing to be in a slight right turn. I think he was on a heading of about 260 degree (180 degrees opposite to me). I turned my aircraft to the right; while ensuring my descent rate was still adequate. My first officer notified ATC of our TCAS RA and that we were complying with descent command. The aircraft passed off our left side; appearing to be within about 200 ft vertically and about 1/2 mile horizontally away from us. I told ATC that this was way too close and they said nothing. I asked who this aircraft was and the response was '[utility mission].' I asked why they were there and the response was 'protecting phoenix' (I think this response was from the pilot). I then asked why in this area; the response was 'we're supposed to be here.' all the responses were with a bit of attitude; a cavalier tone. I reiterated to ATC the severity of this and stated our separation distances. The other pilot stated that he disagreed with my observation. It was very difficult and frustrating to get information from ATC. They didn't seem to want to give us any help. Additionally; if the other aircraft was in their control and always there; as reported by the pilot; then why were we given a SID through their pattern? Also; if they were in ATC control; why weren't we given a vector or lower altitude to level off at to de-conflict? The event turned out to be uneventful; thank goodness. The passengers were unaware of the close proximity of the other aircraft; to the best of my knowledge. The flight attendants did feel the aircraft maneuver; but nothing too unusual. No one was injured.

Google
 

Original NASA ASRS Text

Title: An air carrier Captain reported a TCAS RA evasive maneuver at 11;000 FT on the PHX SJN5 SID when ATC made no attempt to positively separate another aircraft ATC was controlling. That aircraft's pilot reported the air carrier in sight.

Narrative: We departed PHX on time. ATC clearance was SJN5 SID. After takeoff; ATC cleared us direct FORPE Intersection; about 080 deg heading; and climb to FL210 (not exactly sure of altitude). It was VFR; clear and great visibility; altimeter 29.93. Passing about 11;000 FT; I saw a target on the TCAS display. Target was inside the 6 mile scale; about 1;000 FT above; level; at 11:00-12:00. I then realized that I may need to initiate evasive maneuvering. ATC then transmitted to both aircraft traffic advisories. ATC called out our traffic less than 5 miles; 12:00; at 12;000 FT. Our TCAS now showed 600-800 FT above at 12:00. Conflicting aircraft confirmed and said he had us in sight. We did not see him yet. ATC did not give us any directions to de-conflict. We were climbing at climb power and about 2;000 FPM. Shortly after the ATC traffic advisory; the TCAS RA alert went off to descend. Since I had already thought about needing to take evasive action; I immediately disconnected the autopilot and transitioned from a climb to a descent (TCAS VSI showed to descend at 1;000 FPM). Still looking for a visual on the traffic with no luck; the TCAS RA alert changed to increase descent; which showed 1;500 FPM VSI now. I then visually sighted the traffic; nose on; just above the horizon; appearing to be in a slight right turn. I think he was on a heading of about 260 degree (180 degrees opposite to me). I turned my aircraft to the right; while ensuring my descent rate was still adequate. My First officer notified ATC of our TCAS RA and that we were complying with descent command. The aircraft passed off our left side; appearing to be within about 200 FT vertically and about 1/2 mile horizontally away from us. I told ATC that this was way too close and they said nothing. I asked who this aircraft was and the response was '[Utility Mission].' I asked why they were there and the response was 'protecting Phoenix' (I think this response was from the pilot). I then asked why in this area; the response was 'we're supposed to be here.' All the responses were with a bit of attitude; a cavalier tone. I reiterated to ATC the severity of this and stated our separation distances. The other pilot stated that he disagreed with my observation. It was very difficult and frustrating to get information from ATC. They didn't seem to want to give us any help. Additionally; if the other aircraft was in their control and always there; as reported by the pilot; then why were we given a SID through their pattern? Also; if they were in ATC control; why weren't we given a vector or lower altitude to level off at to de-conflict? The event turned out to be uneventful; thank goodness. The passengers were unaware of the close proximity of the other aircraft; to the best of my knowledge. The Flight Attendants did feel the aircraft maneuver; but nothing too unusual. No one was injured.

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.