Narrative:

Multiple military flights were recovering to hif simultaneously. Military airspace was active to the south and departures off of slc were climbing to the northwest leaving limited options for vectoring for spacing. Two flights were NORDO leaving even less time to descend the stack under the departing slc traffic. One flight went NORDO a few miles from S56 boundary when I attempted to turn the flight to the south for their descent. He continued on his present course into S56 airspace and coordination was not achieved until the boundary. We found out later that he had switched to S56 frequency on his own. One of the trailing flights had originally been coordinated on a descent into slc. A subsequent call was made by the radar assist to coordinate a turn to the south for spacing. We have been informed that we may not have had control for descent on the aircraft even though this was coordinated on the initial call to clover; so I am including this in my report.the recovery process itself basically had no plan and no information was given on how the aircraft would need to arrive to hif. We were told by clover control in the middle of the recovery that hif didn't want them recovering over widoe; but by that point it was too late to make any changes. The departure from hif went fine because there was built in spacing between flights after their departures. On recovery no spacing was provided and no pre-approved routing was discussed between involved sectors; clover; and hif. If this had been planned prior to the mission; the recovery would have been a non-factor with slc departing traffic.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZLC Controller was working military aircraft recovering from their airspace to their destination. No coordination was accomplished ahead of time specifying routes or altitudes for the aircraft. One of the flights was NORDO and entered TRACON airspace without a handoff.

Narrative: Multiple military flights were recovering to HIF simultaneously. Military airspace was active to the south and departures off of SLC were climbing to the Northwest leaving limited options for vectoring for spacing. Two flights were NORDO leaving even less time to descend the stack under the departing SLC traffic. One flight went NORDO a few miles from S56 boundary when I attempted to turn the flight to the south for their descent. He continued on his present course into S56 airspace and coordination was not achieved until the boundary. We found out later that he had switched to S56 frequency on his own. One of the trailing flights had originally been coordinated on a descent into SLC. A subsequent call was made by the Radar Assist to coordinate a turn to the south for spacing. We have been informed that we may not have had control for descent on the aircraft even though this was coordinated on the initial call to Clover; so I am including this in my report.The recovery process itself basically had no plan and no information was given on how the aircraft would need to arrive to HIF. We were told by Clover Control in the middle of the recovery that HIF didn't want them recovering over WIDOE; but by that point it was too late to make any changes. The departure from HIF went fine because there was built in spacing between flights after their departures. On recovery no spacing was provided and no pre-approved routing was discussed between involved sectors; Clover; and HIF. If this had been planned prior to the mission; the recovery would have been a non-factor with SLC departing 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.