Narrative:

Working paine/boeing sectors combined at paine scope. Pae ATC had requested release on aircraft X utilizing the automated 'F13' function. Aircraft Y was already cleared and on a practice RNAV approach to runway 16R. Pae ATC activated the shoutline and informed me that aircraft X was 'my control;' which I acknowledged but hadn't figured out why they had specifically called over. At that time aircraft Y was on a mile and a half final and I did not consider that pae ATC would have launched the departure in front of the practice approach. Almost immediately after the coordination; aircraft X tagged up on my scope and it became clear to me why pae ATC had coordinated. I radar identified aircraft X and issued a turn immediately in an attempt to establish some form of separation between aircraft X and aircraft Y (who at this point was tagging up on the go from their option). Aircraft Y advised traffic in sight on initial contact and I issued an immediate turn away from aircraft Y. I subsequently asked aircraft Y what instructions pae ATC had issued them regarding the preceding traffic. Aircraft Y indicated that they were informed of the traffic and cleared low approach. I specifically asked if pae ATC had instructed them to maintain visual separation and aircraft Y responded that they had not.pae ATC is responsible for initial IFR separation of successive departures. Had I processed more quickly the situation that was developing; I would have instructed pae ATC to issue a turn to aircraft X. The tower controller clearly understood that the situation was not going to work; but their coordination should have been for a turn instead of offering control of aircraft X. As the departure controller; I can only work to recover and re-established standard separation; which I believe I did as quickly as I could once I comprehended the situation that had developed.

Google
 

Original NASA ASRS Text

Title: Seattle TRACON Controller reported an operational error due to Tower releasing an aircraft for departure too close to an arrival who had been cleared for the option.

Narrative: Working Paine/Boeing sectors combined at Paine scope. PAE ATC had requested release on Aircraft X utilizing the automated 'F13' function. Aircraft Y was already cleared and on a practice RNAV approach to Runway 16R. PAE ATC activated the shoutline and informed me that Aircraft X was 'My control;' which I acknowledged but hadn't figured out why they had specifically called over. At that time Aircraft Y was on a mile and a half final and I did not consider that PAE ATC would have launched the departure in front of the practice approach. Almost immediately after the coordination; Aircraft X tagged up on my scope and it became clear to me why PAE ATC had coordinated. I radar identified Aircraft X and issued a turn immediately in an attempt to establish some form of separation between Aircraft X and Aircraft Y (who at this point was tagging up on the go from their option). Aircraft Y advised traffic in sight on initial contact and I issued an immediate turn away from Aircraft Y. I subsequently asked Aircraft Y what instructions PAE ATC had issued them regarding the preceding traffic. Aircraft Y indicated that they were informed of the traffic and cleared low approach. I specifically asked if PAE ATC had instructed them to maintain visual separation and Aircraft Y responded that they had not.PAE ATC is responsible for initial IFR separation of successive departures. Had I processed more quickly the situation that was developing; I would have instructed PAE ATC to issue a turn to Aircraft X. The Tower controller clearly understood that the situation was not going to work; but their coordination should have been for a turn instead of offering control of Aircraft X. As the Departure Controller; I can only work to recover and re-established standard separation; which I believe I did as quickly as I could once I comprehended the situation that had developed.

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