S46 TRACON controller reported a loss of separation due to confusing coordination and complex airspa...

Narrative:

Aircraft X was executing a go around due to a possible bird strike on the preceding arrival. I turned aircraft X back into a downwind; and manually coordinated with final that he was level at 3000 feet due to aircraft Y crossing the airport westbound at 4000 feet. Finals would need to climb aircraft X when he was clear of traffic to ensure separation with the bfi final at 2200 feet. I called the traffic to aircraft X and turned him northbound into the downwind. I coordinated a point out off of the landline to the bfi arrival controller on aircraft X. At the same time I was doing the manual point out; I saw aircraft Y appeared to be in a descent. I turned aircraft X to a 250 heading; asked him to expedite; and displayed his data block on the satellite controller's scope. I called satellite and asked them to turn their traffic northbound.the complexity around seatac and boeing creates a number of problems. Aircraft Y had been displayed but not pointed out to the arrival D controller. It is not clear if they had been pointed out to finals; and satellite had assumed the aircraft had been pointed out; giving him control for descent. I don't have a specific airspace recommendation. The satellite controller had told me later he thought aircraft X was a departure; not a go around; and would be climbing above his traffic.

Original NASA ASRS Text

Title: S46 TRACON Controller reported a loss of separation due to confusing coordination and complex airspace between adjacent airports.

Narrative: Aircraft X was executing a go around due to a possible bird strike on the preceding arrival. I turned Aircraft X back into a downwind; and manually coordinated with final that he was level at 3000 feet due to Aircraft Y crossing the airport westbound at 4000 feet. Finals would need to climb Aircraft X when he was clear of traffic to ensure separation with the BFI final at 2200 feet. I called the traffic to Aircraft X and turned him northbound into the downwind. I coordinated a point out off of the landline to the BFI arrival controller on Aircraft X. At the same time I was doing the manual point out; I saw Aircraft Y appeared to be in a descent. I turned Aircraft X to a 250 heading; asked him to expedite; and displayed his data block on the satellite controller's scope. I called satellite and asked them to turn their traffic northbound.The complexity around SEATAC and Boeing creates a number of problems. Aircraft Y had been displayed but not pointed out to the Arrival D controller. It is not clear if they had been pointed out to finals; and satellite had assumed the aircraft had been pointed out; giving him control for descent. I don't have a specific airspace recommendation. The satellite controller had told me later he thought Aircraft X was a departure; not a go around; and would be climbing above his traffic.

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.

Attributes
ACN	1683273
Time
Date	201909
Local Time Of Day	1801-2400
Place
Locale Reference	S46.TRACON
State Reference	WA
Aircraft 1
Make Model Name	Medium Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 11.0
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

S46 TRACON controller reported a loss of separation due to confusing coordination and complex airspace between adjacent airports.