Date: 201404
Local time of day: 0001-0600
Location: P50.TRACON, AZ
Flight conditions: VMC
Weather elements / visibility: Clear
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B PHX
ATC / advisory: TRACON P50
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Confusion; Distraction; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Procedure
Primary problem: Airspace Structure

Narrative: Aircraft X was descending into KSDL on the JCOBS2 arrival with assigned expectations of a visual approach to Runway 03 at KSDL. Between POURS and SLIMY; while flying an assigned heading; we were given the instruction to descend to 7;000 feet.  We observed a TCAS target at our one o'clock climbing into a potential conflict. The controller gave us a left turn to 120 degrees; but it was obvious that this wasn't going to keep us clear of an RA. We asked for a further turn to the left to avoid traffic; and were told that we could come another 5 degrees left. By that time; not only would the 5 degrees failed to avoid the RA; but before we could ask for a larger turn; we were forced into a TCAS climb. During this entire time we were operating in Class B airspace under the positive control of Phoenix Approach; who is required to provide sequencing and separation. By descending us to the floor of the Class B airspace while failing to maintain lateral separation from VFR traffic not under the control of Phoenix Approach; the controller failed to provide that separation. The VFR traffic was climbing the entire time we had him on our TCAS and when the vertical separation was less than 500 feet; we got an RA. I immediately called the Supervisor at PHX Approach. He said that descent to 7;000 feet in that area is mandatory due to separation requirements with departing traffic from KPHX that is crossing above at 8;000 feet. This is a situation where you can have three aircraft with zero lateral separation all crammed into 1100 vertically; guaranteeing TCAS RA's; and all of them are in complete compliance with the airspace requirements and Phoenix Approach. I don't understand how PHX Approach can claim to provide separation services when they fail to provide those services. That is the purpose of Class B airspace. Arrivals into KSDL cause more RAs than the rest of CONUS combined and it appears to be due to improper design; management; and utilization of the airspace. Are we going to have to splatter some airplanes over North Scottsdale before we stop hearing from Phoenix ATC that there is nothing they can do? UPDATE: Further investigation has revealed that we likely were not in the Class B airspace yet at the time of the RA. The VFR conflict traffic was climbing clear of the Class B and Phoenix Approach failed to provide separation from this traffic. Phoenix needs to quit whining that there is nothing they can do to provide separation from VFR traffic for arrivals from the north and start to develop and implement a protected arrival corridor for KSDL. Under present circumstances; it is just a matter of time before we have a midair over north Scottsdale.




Synopsis: Pilot reports of RA and airspace/traffic problems associated with the Class Bravo airspace at Phoenix.