ZHU center controller reported an unsafe situation when a military aircraft went no radio and a carr...

Narrative:

I was training on 59/93 with multiple complex military operations including crystal/amraam and AR614. Aircraft Y flashed at me from 56. I took the handoff and aircraft Y checked on requesting AR614. I told him to maintain block FL230-FL240 and I put in FL270 as a hard altitude and flashed him at sector 76 because they clear participating aircraft into AR614. 76 took the handoff and I gave aircraft Y [a] frequency. He requested UHF so I gave him UHF. 76 called on the landline and asked me to try aircraft Y again because he did not check in. I tried aircraft Y again and gave him a different UHF. 76 called back again requesting communications with aircraft Y and aircraft Y was no longer on my frequency. The AR614 block is FL250-FL270.I took a handoff on aircraft X from 56 going to mexico requesting FL360 and climbed him to FL240. 76 called me and said he still has not had aircraft Y check in on his frequency. I tried to contact aircraft Y and did not get a reply. We tried him several times. Aircraft Y was orbiting south of AR614 at FL240. We had to give aircraft X a 180 heading immediately and a descent to FL190. We had to contact aircraft Y on guard frequency for him to come back up on 59 frequency.the aircraft operating in AR614 should take VHF frequency change. Aircraft Y should have reported back [to] frequency if no response on 76 frequency. AR614 has been a long standing issue in 59 airspace. It is located in a major corridor and 59 does not clear aircraft into the tract. The departure procedures from sat approach should be through rocksprings airspace since they are the ones to own AR614. Corpus acts as a middle man in the procedures outlined for AR614 which leaves room for error because if 76 doesn't take the handoff then we are stuck with a high performance jet orbiting in the corridor and we can only climb him to FL240 which is also the bottom of the high sectors airspace stratum.the amount of military operations that we have to deal with on a day to day basis along with heavy commercial traffic can result in unsafe situations. The amount of military operations is a burden to the controllers that have to work it since we are required to bend over backwards for them and they keep requesting more and more. There needs to be better procedures; airspace design; and a limit to military operations in order to assure the safety of the NAS (national airspace system).

Original NASA ASRS Text

Title: ZHU Center Controller reported an unsafe situation when a military aircraft went No Radio and a carrier had to be vectored away from the No Radio aircraft.

Narrative: I was training on 59/93 with multiple complex military operations including Crystal/Amraam and AR614. Aircraft Y flashed at me from 56. I took the handoff and Aircraft Y checked on requesting AR614. I told him to maintain block FL230-FL240 and I put in FL270 as a hard altitude and flashed him at Sector 76 because they clear participating aircraft into AR614. 76 took the handoff and I gave Aircraft Y [a] frequency. He requested UHF so I gave him UHF. 76 called on the landline and asked me to try Aircraft Y again because he did not check in. I tried Aircraft Y again and gave him a different UHF. 76 called back again requesting communications with Aircraft Y and Aircraft Y was no longer on my frequency. The AR614 block is FL250-FL270.I took a handoff on Aircraft X from 56 going to Mexico requesting FL360 and climbed him to FL240. 76 called me and said he still has not had Aircraft Y check in on his frequency. I tried to contact Aircraft Y and did not get a reply. We tried him several times. Aircraft Y was orbiting south of AR614 at FL240. We had to give Aircraft X a 180 heading immediately and a descent to FL190. We had to contact Aircraft Y on guard frequency for him to come back up on 59 frequency.The aircraft operating in AR614 should take VHF frequency change. Aircraft Y should have reported back [to] frequency if no response on 76 frequency. AR614 has been a long standing issue in 59 airspace. It is located in a major corridor and 59 does not clear aircraft into the tract. The departure procedures from SAT approach should be through Rocksprings airspace since they are the ones to own AR614. Corpus acts as a middle man in the procedures outlined for AR614 which leaves room for error because if 76 doesn't take the handoff then we are stuck with a high performance jet orbiting in the corridor and we can only climb him to FL240 which is also the bottom of the high sectors airspace stratum.The amount of military operations that we have to deal with on a day to day basis along with heavy commercial traffic can result in unsafe situations. The amount of military operations is a burden to the controllers that have to work it since we are required to bend over backwards for them and they keep requesting more and more. There needs to be better procedures; airspace design; and a limit to military operations in order to assure the safety of the NAS (National Airspace System).

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	1614326
Time
Date	201901
Local Time Of Day	1201-1800
Place
Locale Reference	ZHU.ARTCC
State Reference	TX
Environment
Light	Daylight
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Fighting Falcon F16
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Developmental
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

ZHU center controller reported an unsafe situation when a military aircraft went no radio and a carrier had to be vectored away from the no radio aircraft.