 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
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.
| Attributes | |
| ACN | 1344089 |
| Time | |
| Date | 201604 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | S56.TRACON |
| State Reference | UT |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Small Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Light Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | SID NSIGN4 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
| Person 2 | |
| Function | Traffic Management |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
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.
Original NASA ASRS Text
Title: 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.
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.
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.