Phx local controller assigns departing B350 an altitude below MVA due to a B757 on go around.

Attributes
ACN	513313
Time
Date	200105
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : phx.airport
State Reference	AZ
Altitude	msl single value : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Bonanza 35
Operating Under FAR Part	Part 91
Flight Phase	climbout : initial
Route In Use	departure : other published ifr departure
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : p50.tracon
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Phase	landing : go around
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Experience	controller limited radar : 10 controller time certified in position1 : 1.5
ASRS Report	513313
Person 2
Affiliation	other
Function	flight crew : single pilot
Events
Anomaly	airspace violation : entry non adherence : required legal separation non adherence : published procedure
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	controller : issued new clearance controller : separated traffic flight crew : executed go around flight crew : took precautionary avoidance action
Miss Distance	horizontal : 6000 vertical : 500
Supplementary
Problem Areas	ATC Human Performance Airspace Structure
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Deviation

Narrative:

I was working local north at phx and had just launched a slow climbing king air off runway 26 when the final controller coordinated a go around with an air carrier Y B757. The finals controller was very busy and unkeyed after she coordinated the go around. I was trying to tell the finals controller about the king air off the departure end. I then tried to coordinate with the arrival coordinator and then the RC2 -- the overall TRACON coordinator and no one was available or responding. The air carrier Y (B757) did not come over to the tower frequency as required in the LOA. The only option that I had to keep the aircraft separated was to stop the king air at 2500 ft MSL since the B757 was at 3000 ft. In doing this, the king air was vectored below the 2800 ft MVA. This event happened on may/tue/01 and I was told that no error happened. When I returned from vacation on may/thu/01, I was informed that it was an operational deviation.

Original NASA ASRS Text

Title: PHX LCL CTLR ASSIGNS DEPARTING B350 AN ALT BELOW MVA DUE TO A B757 ON GAR.

Narrative: I WAS WORKING LCL N AT PHX AND HAD JUST LAUNCHED A SLOW CLBING KING AIR OFF RWY 26 WHEN THE FINAL CTLR COORDINATED A GAR WITH AN ACR Y B757. THE FINALS CTLR WAS VERY BUSY AND UNKEYED AFTER SHE COORDINATED THE GAR. I WAS TRYING TO TELL THE FINALS CTLR ABOUT THE KING AIR OFF THE DEP END. I THEN TRIED TO COORDINATE WITH THE ARR COORDINATOR AND THEN THE RC2 -- THE OVERALL TRACON COORDINATOR AND NO ONE WAS AVAILABLE OR RESPONDING. THE ACR Y (B757) DID NOT COME OVER TO THE TWR FREQ AS REQUIRED IN THE LOA. THE ONLY OPTION THAT I HAD TO KEEP THE ACFT SEPARATED WAS TO STOP THE KING AIR AT 2500 FT MSL SINCE THE B757 WAS AT 3000 FT. IN DOING THIS, THE KING AIR WAS VECTORED BELOW THE 2800 FT MVA. THIS EVENT HAPPENED ON MAY/TUE/01 AND I WAS TOLD THAT NO ERROR HAPPENED. WHEN I RETURNED FROM VACATION ON MAY/THU/01, I WAS INFORMED THAT IT WAS AN OPDEV.

Data retrieved from NASA's ASRS site as of July 2007 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.