Small Transport; Low Wing; 2 Turboprop Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 1.6
Situational Awareness; Communication Breakdown; Distraction; Confusion
ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Separated Traffic
Procedure
During this situation; the Biltmore Sector at P50 did not initiate the flash to hand an aircraft off until the aircraft on the edge of SDL Tower Class D airspace. While this was happening; I had Aircraft Y on final and Aircraft Z turning approximately a 3 mile base turn for a touch and go. I did not observe the inbound Aircraft X on the STARS display because the alfa numerics were not visible; and I did not observe the 'B' tag; which is designated to the Biltmore Sector; until the controller at P50 called to initiate a manual handoff. At the time he called he apologized for the late flash; I said I could not take that because of pattern traffic; and gave my operating initials and came off the line. A few seconds later Aircraft X came over to my frequency stating he was cleared for the visual approach. I gave the aircraft the sequence to follow Aircraft Z on final. Subsequently Aircraft X closure rate on the Aircraft Z resulted in me having to send Aircraft X around. I called back to the P50 controller and asked if he had just switched the aircraft and he said he did against my decision stating that I could not accept the aircraft. This is becoming a recurrent problem facing SDL Tower and puts us in a severely disabling position while dealing with our heightened seasonal traffic that is taking place now. A new Letter of Agreement was just put into effect. This LOA mandates that SDL tower must accept the data transfer for an IFR inbound aircraft regardless of current traffic volume whether it be IFR/VFR. This is not feasible with the traffic volume we can have during the winter months. If we do not accept the data transfer as management requires; P50 will make a quick shout over the shout line and switch the aircraft. At SDL we are a training facility and have numerous 'green' controllers who are susceptible to adverse situations by this mandate. It must be retracted.  Additionally it is very misunderstood at SDL how this is only called a data transfer and not a handoff; and how another facility can get away with one aircraft entering another controllers airspace if they do not accept the handoff.
SDL Local Controller reports of a attempted handoff late from P50. SDL Controller advises he's unable handoff due to other traffic. Minutes later the aircraft is on his frequency cleared for a visual approach. SDL Controller had to send an aircraft around due to the overtake from the un-handed off aircraft. A new LOA went into place 3 days prior.