Narrative:

Aircraft X drone departed from efd airport with aircraft Z chase plane both VFR. I assumed responsibility for the san jac position while aircraft X and Z were east of efd airport at 025 MSL. The aircraft request to climb to 035; then 055; then 075 and proceeded outbound to the south; southeast on a profile routing. I pulled up the requested lost link w-zzz procedure in my overhead database and activated the map overlay on my display. The aircraft were pointed to intra-facility sectors via automation and then verbally pointed out to houston center off-shore sector. The aircraft had indicated that could maintain radio communications throughout his mission profile so elected to keep him on my frequency for a little longer. I asked the pilot if he was only going to climb to 095 as published in the profile. He replied affirmative. Prior to reaching point 9 on the route; I terminated radar services with the aircraft X and Z flight; instructing them to remain on their current beacon codes and to advise me when they were inbound back to efd airport. I later briefed the relieving controller of the situation and didn't think anything of it. The next day I was told that the aircraft X had climbed as high as FL280 and at some point came in close proximity to aircraft Y on departure. The chase plane had remained below 095 as published. Apparently the uas operators from efd had forwarded their weekly schedule to both houston TRACON and center. The schedule reflected the climb to flight levels on the appropriate day and time. The schedule was disseminated to the front line supervisors; however the controllers at the position were never briefed by the supervisor that the altitudes would be non-standard. Better dissemination of information to the actual controllers working the operation by both management and by the operator while on frequency. I definitely would have handed the aircraft off to houston center had I known their intention was to climb above 095 feet.

Google
 

Original NASA ASRS Text

Title: I90 Controller reported failure of facility to brief Controllers on tactical activities resulted in a UAV altitude deviation and conflict.

Narrative: Aircraft X drone departed from EFD airport with Aircraft Z chase plane both VFR. I assumed responsibility for the San Jac position while Aircraft X and Z were east of EFD airport at 025 MSL. The aircraft request to climb to 035; then 055; then 075 and proceeded outbound to the south; southeast on a profile routing. I pulled up the requested lost link W-ZZZ procedure in my overhead database and activated the map overlay on my display. The aircraft were pointed to intra-facility sectors via automation and then verbally pointed out to Houston Center off-shore sector. The aircraft had indicated that could maintain radio communications throughout his mission profile so elected to keep him on my frequency for a little longer. I asked the pilot if he was only going to climb to 095 as published in the profile. He replied affirmative. Prior to reaching point 9 on the route; I terminated radar services with the Aircraft X and Z flight; instructing them to remain on their current beacon codes and to advise me when they were inbound back to EFD airport. I later briefed the relieving controller of the situation and didn't think anything of it. The next day I was told that the Aircraft X had climbed as high as FL280 and at some point came in close proximity to Aircraft Y on departure. The chase plane had remained below 095 as published. Apparently the UAS operators from EFD had forwarded their weekly schedule to both Houston TRACON and Center. The schedule reflected the climb to flight levels on the appropriate day and time. The schedule was disseminated to the Front Line Supervisors; however the Controllers at the position were never briefed by the Supervisor that the altitudes would be non-standard. Better dissemination of information to the actual Controllers working the operation by both management and by the operator while on frequency. I definitely would have handed the aircraft off to Houston Center had I known their intention was to climb above 095 feet.

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.