Narrative:

While working the biltmore sector air carrier X went around and climbed through the satellite corridor airspace. After talking to the final controller it became evident that air carrier X was having software difficulties and sped up to 320 knots on a 5 mile final; unsure and with no time to coordinate the final controller scanned ahead in the corridor and saw that it was clear and determined that the best course of action would be to climb air carrier X to an altitude above tower departures and above the MVA. So the final controller climbed the go around to 6;000. He thought about starting a turn; but it is actually best he didn't as this would have been more of a conflict with the traffic he didn't see 15 north southbound in my sky at 5;000. In hindsight and after talking with the final controller I stated that I thought that the best thing would have been to just switch the arrival to the tower so that they; who are trained in go arounds; could coordinate with the departure controller. However; a straight shot over the top of phx at air carrier X's high speed was in actuality the best course of action short of shipping the arrival to the tower as it was clear and any turns would have put air carrier X in the biltmore transition corridor for a longer time. The arrival coordinator came over and coordinated the go around with me and I was watching the traffic; and while the words point out approved never came out of my mouth it was in effect very similar as I was watching the traffic and providing separation from it with what little traffic I had (a VFR citation 13NM north of the airport southbound at 5;000 who had the A320 in sight when they were still 6 miles apart and 600 feet vertically.) recommendation; some sort of simulation training or SOP for final controllers to know what to do in such events. I think the final controller would agree.

Related reports:

Google
 

Original NASA ASRS Text

Title: P50 controller described airspace incursion event when aircraft on final; experiencing equipment difficulties; went around with airspeed and altitude deviations that resulted in an uncoordinated airspace entry.

Narrative: While working the Biltmore Sector Air Carrier X went around and climbed through the satellite corridor airspace. After talking to the Final Controller it became evident that Air Carrier X was having software difficulties and sped up to 320 knots on a 5 mile final; unsure and with no time to coordinate the Final Controller scanned ahead in the corridor and saw that it was clear and determined that the best course of action would be to climb Air Carrier X to an altitude above Tower departures and above the MVA. So the Final Controller climbed the go around to 6;000. He thought about starting a turn; but it is actually best he didn't as this would have been more of a conflict with the traffic he didn't see 15 north southbound in my sky at 5;000. In hindsight and after talking with the Final Controller I stated that I thought that the best thing would have been to just switch the arrival to the Tower so that they; who are trained in go arounds; could coordinate with the Departure Controller. However; a straight shot over the top of PHX at Air Carrier X's high speed was in actuality the best course of action short of shipping the arrival to the Tower as it was clear and any turns would have put Air Carrier X in the Biltmore transition corridor for a longer time. The Arrival Coordinator came over and coordinated the go around with me and I was watching the traffic; and while the words point out approved never came out of my mouth it was in effect very similar as I was watching the traffic and providing separation from it with what little traffic I had (a VFR Citation 13NM north of the airport southbound at 5;000 who had the A320 in sight when they were still 6 miles apart and 600 feet vertically.) Recommendation; some sort of simulation training or SOP for final controllers to know what to do in such events. I think the Final Controller would agree.

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.