Narrative:

I was working the pima and willy position combined. This requires the controller to monitor a very large portion of airspace. The flm advised me that aircraft X would be departing from gateway airport for surveillance operations 5-10 miles west of phoenix sky harbor at 10;500. The flm advised me that aircraft X was issued beacon code. Gateway fct called to verify that I knew about aircraft X and that he had already received a beacon code. I observed a data block indicating aircraft X climbing through 5800 in the class bravo airspace; 3 miles west of gateway airport. I called aircraft X to see if he was on my frequency and aircraft X answered stating they were with me 3 north of gateway at 6000. Aircraft X was still in a climb and heading directly towards the phoenix sky harbor departures; departing runway 7L. I advised aircraft X he was in the class bravo airspace without a clearance and to turn left immediately heading 210 and to identify. I observed the identify and radar identified aircraft X and coordinated with santan position since aircraft X had already penetrated their airspace. I then transferred communications of aircraft X to santan. While this was occurring I had an astra jet on a heading to vector him over sky harbor for scottsdale airport at 4000; per the P50 SOP. The biltmore controller called me to ask if the astra was turning since he observed the aircraft still on a northwesterly heading. I quickly made a point out with the verde position but I believe the astra came closer than the 1.5 miles required with adjacent airspace. Vectoring aircraft over sky harbor is always a problem because if anything comes up it is difficult to remain 1.5 miles away from adjacent airspace. I also was delaying with an aircraft climbing with a TCAS alert; C500; at 4000 over chandler airport; inbound to gateway; with VFR known traffic at 3500 and traffic was issued. The perfect storm! I believe that assignment of a VFR beacon code to an aircraft still on the ground contributed to this event. This may have lead aircraft X to think that he could climb on course through the bravo airspace without calling phoenix TRACON. Based on staffing pima and willy should have been split.

Related reports:

Google
 

Original NASA ASRS Text

Title: P50 Controller described Class B incursion event involving a special operations aircraft; noting issuance of a beacon code prior to takeoff may have led the pilot to believe a Class B entry clearance was approved.

Narrative: I was working the Pima and Willy position combined. This requires the Controller to monitor a very large portion of airspace. The FLM advised me that Aircraft X would be departing from Gateway airport for surveillance operations 5-10 miles West of Phoenix Sky Harbor at 10;500. The FLM advised me that Aircraft X was issued beacon code. Gateway FCT called to verify that I knew about Aircraft X and that he had already received a beacon code. I observed a data block indicating Aircraft X climbing through 5800 in the Class Bravo airspace; 3 miles West of Gateway airport. I called Aircraft X to see if he was on my frequency and Aircraft X answered stating they were with me 3 North of Gateway at 6000. Aircraft X was still in a climb and heading directly towards the Phoenix Sky Harbor departures; departing Runway 7L. I advised Aircraft X he was in the Class Bravo airspace without a clearance and to turn left immediately heading 210 and to IDENT. I observed the IDENT and RADAR identified Aircraft X and coordinated with Santan position since Aircraft X had already penetrated their airspace. I then transferred communications of Aircraft X to Santan. While this was occurring I had an Astra jet on a heading to vector him over Sky Harbor for Scottsdale Airport at 4000; per the P50 SOP. The Biltmore Controller called me to ask if the Astra was turning since he observed the aircraft still on a Northwesterly heading. I quickly made a point out with the Verde position but I believe the Astra came closer than the 1.5 miles required with adjacent airspace. Vectoring aircraft over Sky Harbor is always a problem because if anything comes up it is difficult to remain 1.5 miles away from adjacent airspace. I also was delaying with an aircraft climbing with a TCAS alert; C500; at 4000 over Chandler airport; inbound to Gateway; with VFR known traffic at 3500 and traffic was issued. The Perfect Storm! I believe that assignment of a VFR beacon code to an aircraft still on the ground contributed to this event. This may have lead Aircraft X to think that he could climb on course through the Bravo airspace without calling Phoenix TRACON. Based on staffing Pima and Willy should have been split.

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.