Narrative:

Sat approach had several departures in succession on the Hubee1. A F2TH was a departure behind a CRJ2 aircraft; a notoriously slow climber. I made a point out to sector 50 and called sat approach to climb F2TH to FL230 and to get above the CRJ2. Sat approach appeared to have been vectoring their departures around some arrival traffic and they were well north of their departure route. I received communications with the CRJ2 which was now about 10NM in front of F2TH. I called approach to ask if F2TH was turning back to the departure route and was told he was doing it now. Sat approach called me back and said they had lost communication with F2TH still on a north eastbound heading climbing to FL230. I called sector 50 to let them know F2TH was currently NORDO and asked if any additional point outs were required; as my scope map did not depict sector 50's north boundary. He told me that F2TH was getting close to sector 96; then he said 'let me take care of this'; which I interpreted to mean he would call sector 96. I informed my supervisor of the NORDO situation and to coordinate with anyone necessary. Sat approach called me to tell me they had re-established communications with F2TH and were turning him south to errad intersection to join the departure. I called sector 96 to inform them of such. Sector 96 seemed surprised and showed me some traffic descending out of FL260 for sat. At this point I was still not talking to F2TH and he was level at FL230 turning southbound. He finally checked on my frequency and I called sector 96 to let them know I was talking to F2TH and what would he like me to do with the aircraft. Sector 96 told me to assign F2TH heading 080 and put the aircraft on his frequency. Separation was never lost; but as I didn't have those sector boundaries depicted; as they are not on my map. I don't know what areas F2TH may or may not have violated. I found out later that sector 50 had had another situation going on at the same time and this may have led to some confusion. Sector 50 did not appear to have a d-side at the time. Apart from having more complete maps; and maps that are easier to decipher; there's not much to recommend as this resulted from an aircraft going NORDO.

Related reports:

Google
 

Original NASA ASRS Text

Title: A possible airspace incursion occurred when a SAT departure aircraft was NORDO and coordination efforts with adjacent sectors was less than clear and complete.

Narrative: SAT Approach had several departures in succession on the Hubee1. A F2TH was a departure behind a CRJ2 aircraft; a notoriously slow climber. I made a point out to Sector 50 and called SAT Approach to climb F2TH to FL230 and to get above the CRJ2. SAT Approach appeared to have been vectoring their departures around some arrival traffic and they were well north of their departure route. I received communications with the CRJ2 which was now about 10NM in front of F2TH. I called Approach to ask if F2TH was turning back to the departure route and was told he was doing it now. SAT Approach called me back and said they had lost communication with F2TH still on a north eastbound heading climbing to FL230. I called Sector 50 to let them know F2TH was currently NORDO and asked if any additional point outs were required; as my scope map did not depict Sector 50's north boundary. He told me that F2TH was getting close to Sector 96; then he said 'let me take care of this'; which I interpreted to mean he would call Sector 96. I informed my Supervisor of the NORDO situation and to coordinate with anyone necessary. SAT Approach called me to tell me they had re-established communications with F2TH and were turning him south to ERRAD Intersection to join the departure. I called Sector 96 to inform them of such. Sector 96 seemed surprised and showed me some traffic descending out of FL260 for SAT. At this point I was still not talking to F2TH and he was level at FL230 turning southbound. He finally checked on my frequency and I called Sector 96 to let them know I was talking to F2TH and what would he like me to do with the aircraft. Sector 96 told me to assign F2TH heading 080 and put the aircraft on his frequency. Separation was never lost; but as I didn't have those sector boundaries depicted; as they are not on my map. I don't know what areas F2TH may or may not have violated. I found out later that Sector 50 had had another situation going on at the same time and this may have led to some confusion. Sector 50 did not appear to have a D-Side at the time. Apart from having more complete maps; and maps that are easier to decipher; there's not much to recommend as this resulted from an aircraft going NORDO.

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