Narrative:

Training session on valley radar; a BE20 was a special military flight already airborne maneuvering around mfe at 050 ft. After about 20 minutes so I observed no data block or target in the area he should have been in. I made a broadcast for the BE20 and received no response. I reached out to ZHU vct sector and asked if they observed the BE20's beacon code in that general area where he might have been. I explained that I had lost communication and target information with that aircraft and asked if they would protect 050 and below for him. The controller observed the beacon code and said they would protect. With continued coordination with that sector; I asked if they would broadcast out to see if the BE20 was on their frequency. After several attempts on frequency and on guard frequency; I was still not able to get a hold of the aircraft. ZHU called back and also advised that they had no luck. I advised my supervisor of the situation and in about 10 to 15 minutes the BE20 was checking in on my frequency. Coordination was accomplished with ZHU to resolve the situation and aircraft landed safely. Being that the aircraft was a military 'special' flight the controllers are not to really question the operation. Therefore these aircraft go about their business without question and limited communication. The NORDO aspect of this situation happens more often than not. I believe this set of 'special operations' flights; this one included; is supposed to cancel IFR flight if they leave valley airspace. Have the aircraft fly under VFR rules and only IFR when weather is prohibiting.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRP Controller described a NORDO/lost RADAR event involving an IFR 'Special Military Operations' aircraft; the reporter recommending these aircraft operate under VFR rules when weather conditions permit.

Narrative: Training session on Valley RADAR; a BE20 was a special military flight already airborne maneuvering around MFE at 050 FT. After about 20 minutes so I observed no Data Block or target in the area he should have been in. I made a broadcast for the BE20 and received no response. I reached out to ZHU VCT Sector and asked if they observed the BE20's beacon code in that general area where he might have been. I explained that I had lost communication and target information with that aircraft and asked if they would protect 050 and below for him. The controller observed the beacon code and said they would protect. With continued coordination with that sector; I asked if they would broadcast out to see if the BE20 was on their frequency. After several attempts on frequency and on guard frequency; I was still not able to get a hold of the aircraft. ZHU called back and also advised that they had no luck. I advised my supervisor of the situation and in about 10 to 15 minutes the BE20 was checking in on my frequency. Coordination was accomplished with ZHU to resolve the situation and aircraft landed safely. Being that the aircraft was a military 'special' flight the controllers are not to really question the operation. Therefore these aircraft go about their business without question and limited communication. The NORDO aspect of this situation happens more often than not. I believe this set of 'Special Operations' flights; this one included; is supposed to cancel IFR flight if they leave Valley airspace. Have the aircraft fly under VFR rules and only IFR when weather is prohibiting.

Data retrieved from NASA's ASRS site as of July 2013 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.