Narrative:

I was running behind from taking the position. The relieved controller forgot to climb an edf departure out of 5;000' when traffic was no longer a factor but and mvas were a factor. He also cleared the traffic on a course prohibited by the LOA with zan; which required coordination. Several F22s were recovering on the ILS to runway 6 at edf because of weather and I had a few departures. I released air carrier X off runway 32 behind the F22s on final to runway 6 at edf. At least 10-miles existed between those F22s and succeeding flight of 2/F22s. The tower launched air carrier X late; and I didn't realize it until it was too late to turn the arrival flight across the localizer due to conflicting runway 7L arrivals at anc. I issued air carrier X traffic to the flight who responded 'radar contact'; not an approved form of separation. At the same time; when I would normally stop air carrier X at 2;000' and the arriving flight at 3;000' and take it over the localizer then vector for another approach; a VFR C207 was approaching the runway 32 SID corridor at 1;700'; conflicting with air carrier X. Another sector called across the room that it was providing visual separation from air carrier X; but I expected that the pilot figured that air carrier X would not stop at 2;000' and a near midair collision or worse could result. When I saw the C207 turn toward the north; I issued heading 320 to air carrier X; but I may have already lost separation with the inbound flight. I chose the lesser risk; the inbound flight wasn't going to collide with a radar identified target; but the C207 might have either collided with air carrier X or been forced into the terrain by its wake. Recommendation; place more responsibility on anc tower to refrain from launching departures when they're late. I could have issued inbound traffic as part of the release of air carrier X. I could have restricted the departure to pass not more than 5-miles behind the preceding F22s; but that would only result in anc tower being responsible if separation was lost and not prevented an unsafe situation. I could have climbed the inbounds to 5;000'; but that would likely have taken too long since it was already configured; slowing; and flying the ILS approach. I could have refused the release request for air carrier X or told anc tower to take it to runway 7L for departure; which I did later with a C130 because I still had F22s inbound to edf. Provide training to anc tower to be more efficient with departures when edf arrivals are a factor; and to call and advise A11 that the aircraft will not be able to depart as released. Modify A11's sops. I could have asked for help.

Related reports:

Google
 

Original NASA ASRS Text

Title: A11 controller experienced a loss of separation event shortly after assuming the position between an military arrival flight to EDF Runway 6 and ANC Runway 32 departure traffic. The reporter listed a number of distracting factors that contributed to the event.

Narrative: I was running behind from taking the position. The relieved controller forgot to climb an EDF departure out of 5;000' when traffic was no longer a factor but and MVAs were a factor. He also cleared the traffic on a course prohibited by the LOA with ZAN; which required coordination. Several F22s were recovering on the ILS to Runway 6 at EDF because of weather and I had a few departures. I released Air Carrier X off Runway 32 behind the F22s on final to Runway 6 at EDF. At least 10-miles existed between those F22s and succeeding flight of 2/F22s. The Tower launched Air Carrier X late; and I didn't realize it until it was too late to turn the arrival flight across the localizer due to conflicting Runway 7L arrivals at ANC. I issued Air Carrier X traffic to the flight who responded 'RADAR contact'; not an approved form of separation. At the same time; when I would normally stop Air Carrier X at 2;000' and the arriving flight at 3;000' and take it over the localizer then vector for another approach; a VFR C207 was approaching the Runway 32 SID corridor at 1;700'; conflicting with Air Carrier X. Another sector called across the room that it was providing visual separation from Air Carrier X; but I expected that the pilot figured that Air Carrier X would not stop at 2;000' and a NMAC or worse could result. When I saw the C207 turn toward the north; I issued heading 320 to Air Carrier X; but I may have already lost separation with the inbound flight. I chose the lesser risk; the inbound flight wasn't going to collide with a RADAR identified target; but the C207 might have either collided with Air Carrier X or been forced into the terrain by its wake. Recommendation; place more responsibility on ANC Tower to refrain from launching departures when they're late. I could have issued inbound traffic as part of the release of Air Carrier X. I could have restricted the departure to pass not more than 5-miles behind the preceding F22s; but that would only result in ANC Tower being responsible if separation was lost and not prevented an unsafe situation. I could have climbed the inbounds to 5;000'; but that would likely have taken too long since it was already configured; slowing; and flying the ILS approach. I could have refused the release request for Air Carrier X or told ANC Tower to take it to Runway 7L for departure; which I did later with a C130 because I still had F22s inbound to EDF. Provide training to ANC Tower to be more efficient with departures when EDF arrivals are a factor; and to call and advise A11 that the aircraft will not be able to depart as released. Modify A11's SOPs. I could have asked for help.

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.