Narrative:

The lev sector has two additional airspace boundaries drawn on the scope to depict a tfr and an advisory area. These areas are used by aircraft at and below 3000 feet to assist in the oil spill in the gulf of mexico. The southern boundaries of these areas parallel the lev and oceanic northern boundary. I accepted a hand off of aircraft X from the oceanic sector; (sector 72). Aircraft X was at FL340; northbound on A6262 ro hrv. Previous aircraft were deviating around hrv due to weather. Aircraft X checked on my frequency at FL340 with a request. I responded with 'aircraft X; houston center; expect direct irw in 5 miles; if your request is other than that; go ahead'. Direct irw would avoid the weather around hrv. Aircraft X asked for FL360. I told him to expect FL360 in 5 miles. I was looking at the boundary of the oil spill tfr and not the lev/oceanic boundary. When aircraft X crossed the tfr boundary; I cleared him direct irw; climb and maintain FL360. I was also working a oil spill support aircraft that was holding east and west in sector 72 airspace; south of my airspace. That aircraft was south of the lev/oceanic boundary; but north of the tfr boundary. When aircraft X crossed the tfr boundary; he was in the area the oil spill support aircraft was holding; which may have led me to believe aircraft X was in my airspace. Recommendation; eliminate the temporary boundaries we are placing on our scopes for the oil spill. The only aircraft we control in those areas are offshore helicopters; and they have permission to enter and traverse the area. We do not clear any other aircraft in or out of the tfr's. We are looking at several boundaries; and did lead to confusion in my case. Several other controllers have stated they almost did the same thing. The mistake was mine; but it would not have happened if I did not have these extra boundaries on my scope.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZHU controller described a TFR airspace incursion event claiming the addition of the temporary boundary marking on the facility's RADAR displays are confusing an unnecessary.

Narrative: The LEV sector has two additional airspace boundaries drawn on the scope to depict a TFR and an Advisory area. These areas are used by aircraft at and below 3000 feet to assist in the oil spill in the Gulf of Mexico. The southern boundaries of these areas parallel the LEV and Oceanic northern boundary. I accepted a hand off of Aircraft X from the Oceanic Sector; (Sector 72). Aircraft X was at FL340; northbound on A6262 RO HRV. Previous aircraft were deviating around HRV due to weather. Aircraft X checked on my frequency at FL340 with a request. I responded with 'Aircraft X; Houston Center; expect direct IRW in 5 miles; if your request is other than that; go ahead'. Direct IRW would avoid the weather around HRV. Aircraft X asked for FL360. I told him to expect FL360 in 5 miles. I was looking at the boundary of the Oil Spill TFR and not the LEV/Oceanic boundary. When Aircraft X crossed the TFR boundary; I cleared him direct IRW; climb and maintain FL360. I was also working a oil spill support aircraft that was holding east and west in Sector 72 airspace; south of my airspace. That aircraft was south of the LEV/Oceanic boundary; but North of the TFR boundary. When Aircraft X crossed the TFR boundary; he was in the area the oil spill support aircraft was holding; which may have led me to believe Aircraft X was in my airspace. Recommendation; eliminate the temporary boundaries we are placing on our scopes for the oil spill. The only aircraft we control in those areas are offshore helicopters; and they have permission to enter and traverse the area. We do not clear any other aircraft in or out of the TFR's. We are looking at several boundaries; and did lead to confusion in my case. Several other controllers have stated they almost did the same thing. The mistake was mine; but it would not have happened if I did not have these extra boundaries on my scope.

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.