B737 Undifferentiated or Other Model
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 2.5
Distraction; Confusion; Communication Breakdown
ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Executed Go Around / Missed Approach
Human Factors; Procedure
Aircraft X was on approach to ANC Runway 15 talking to ANC Local Control (LC). Aircraft Y was cleared for departure Runway 15 prior to Aircraft X. Separation was unable to be maintained by this runway sequence and Aircraft X went around as Aircraft Y was departing. ANC LC called South Radar and advised that Aircraft X was going around and coordinated a 250 heading. Aircraft X and Aircraft Y tags were over lapping (no green between) and both aircraft Mode C's indicated 010 (no altitude separation) when ANC LC shipped both aircraft to departure frequencies. Aircraft X came over on the North Radar frequency and Aircraft Y on South Radar. Aircraft X came over to the wrong frequency per the SOP. No coordination was made with TRACON advising visual separation being applied and from the radar view; it did not appear that any form separation was being applied.This individual's lack of controlling ability is a systemic issue at ANC Tower that affects A11 and airports air traffic. ANC management is well aware of this person's negligence and apathy to the NAS's overall goals. ANC management should be held accountable for this individual's inability to control air traffic as they are choosing to ignore a problematic employee instead of dealing with an apparent working place problem. Expeditious flow and safety were both overlooked in this operation. During a critical phase of flight; both aircraft were forced into unsafe vertical and lateral proximities with traffic. Decertification; Training on local procedures; standard separation requirements and good judgment; Training on the 7110.65; and relocation.
Landing Runway 15 and departing Runway 15 and 25R. I cleared Aircraft X to land Runway 15. When Aircraft X was on a 3.5 mile final I cleared Aircraft Y for takeoff no delay. Aircraft Y did not takeoff fast enough and I had to send Aircraft X around.  Aircraft Y was then airborne on the ANC6 Departure and I told Aircraft X to turn right heading 220. I coordinated with the TRACON a heading of 250 for Aircraft X and it was approved. I told Aircraft X to now turn heading 250 and as I saw him turning I switched him to Departure on 118.6. Aircraft Y was also turning on the ANC6 departure which is a heading 200. He apologized for not departing fast enough. In my opinion they were on diverging courses so I switched Aircraft Y to Departure. Separation was reestablished. There was plenty of spacing for Aircraft Y to depart prior to Aircraft X arrival. Aircraft Y did not fly a no delay departure as instructed which produced the loss of separation. Go-arounds are inevitable in aviation. It would have helped if the pilot followed instructions in this situation. I also had a Supervisor behind me that was not helpful and proceeded to yell at me instead of help with coordination and procedures. I then felt embarrassed and belittled which caused additional stress to the situation. There needs to be more positive action and team work from our managers and help to improve controller moral not damage it. In my opinion I had both aircraft in sight and was maintaining visual separation and in my opinion they were on diverging courses which is why I switched the aircraft to departure frequency.
Numerous reports of a go-around caused by the departure of an aircraft that didn't roll as fast as the Local Controller anticipated.