Date: 201604
Local time of day: 0001-0600
Location: S56.TRACON, UT
Light: Night
Aircraft: Small Transport
Operating under: Part 91
Flight plan: VFR
Mission: Skydiving
Flight phase: Climb
Airspace: Class E S56
ATC / advisory: TRACON S56
Second aircraft: Light Transport
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Distraction; Situational Awareness; Communication Breakdown
Second reporter function: Traffic Management
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Company Policy; Procedure; Human Factors; Equipment / Tooling
Primary problem: Procedure

Narrative: I was working the Heart Sector during one of our busier arrival banks into SLC. I was working Aircraft X climbing for a jump. Aircraft X was pointed out to Lake; the departure sector; and Bear; the arrival sector. As Aircraft X was southbound climbing out of about 12;000 I noticed a primary target moving quickly off of SLC. We often times see reflections and false targets; initially that's what I assumed this was. I still called the traffic at about 8 miles and advised Aircraft X; it was moving fast and possibly a false target.After the track remained consistent I called traffic again. Then the final time I called the traffic it was passing right in front of Aircraft X with 2.7 miles. As soon as it started to cross it tagged up as Aircraft Y out of FL208 on a K tag. I turned to ask the K Controller what was going on right when the Tower called them and said that Aircraft Y had not tagged up on departure and what to do with them. So what had happen was the Aircraft Y departed without a transponder on; and the Tower forgot about them until the Aircraft Y asked the Tower what they were supposed to do. Luckily it was a fast climbing aircraft and was well above jump when the targets were close. This could have gone a lot worse than it did.We have an Airport Surface Detection Equipment (ASDE) X at SLC. The Tower should know whether the transponder is operative while the aircraft is taxiing. I looked at the ASDE replay; and there was no tag on the aircraft while taxiing or departure roll. They never switched him to departure. On the radar side of things; the departure strip did print; this is our rolling call. However; we do not have a requirement to use strips; so the Lake Controller is not required to look at it. Had they noticed the rolling call; they could have inquired as to the status of the aircraft.


Second narrative: Aircraft Y's data block acquired at FL203 climbing on the NSIGN4 departure. Until that point they were a primary target that nobody saw including the On the Job Training Instructor (OJTI) and Developmental training at that position. SLC Tower apparently had forgot that they cleared the aircraft for takeoff and never observed the aircraft acquire on radar as required by our local order. There was a VFR Aircraft X maneuvering just to the North of where they acquired and had it been anything other than Aircraft Y they would have been in very close proximity. This could have had a very bad turnout and pretty much optimizes the Swiss Cheese Model.[I recommend] some kind of a technique that draws their attention to the fact that the aircraft has been cleared for takeoff; but has not been shipped to the Departure Controller.


Synopsis: Four Controllers reported on a loss of separation with a VFR and IFR aircraft. The IFR aircraft did not have its transponder on and SLC Tower Controller did not advise the pilot. Aircraft departed and climbed through VFR aircraft's protected airspace and was not noticed until passing the VFR aircraft.