Small Transport
Flight Crew Air Transport Pilot (ATP)
Communication Breakdown; Confusion; Situational Awareness
ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Took Evasive Action
Procedure; Human Factors
While on our flight to Scottsdale we were handed off to Luke AFB Approach north of the Phoenix area.  We were level at 6000 feet and approach called traffic at our 2 o'clock and 5500; a light aircraft I believe.  He then gave us a heading which put us directly toward the traffic.  I dialed in the heading; but my First Officer thought it odd enough; he questioned the controller why he was turning us directly toward the traffic.  The controller reiterated that he was talking to the aircraft and he was level at 5500 ft. Seconds later we got a TCAS traffic call followed but a RA climb; which we did.  We never saw the traffic; but we saw on the TCAS the aircraft had climbed to within 300 feet.  (It was hot and bumpy over the hills.)  We advised the controller of the RA.  Everything was routine up to this point; but when we reported the RA; the controller got upset at us for climbing and responding to a RA. (we climbed about 400 feet before returning to 6000).  He even questioned us why we were 'Using TCAS in a terminal area' and insisted the traffic was level at 5500.  I suspect this controller does not have a good understanding of how TCAS RA's work; and that we are required to respond.
Pilot reports of an airborne conflict that was pointed out by ATC. ATC turns the aircraft and the aircraft then receives an RA and climbs. ATC questions the pilot why they were using TCAS in a terminal environment and why they climbed.