Narrative:

We were presented with a special use area for a rocket launch on the boi 179/020; 1NM radius. A crj was inbound to boi from the southwest. The controller on the sector vectored the aircraft west of the rocket launch area; and handed him off to boi approach. The boi controller immediately called and asked why we flew the crj right through the area of the rocket launch. Our controller said; 'I didn't; I vectored him west.' the boi controller then inquired what we were showing for the launch area; and our controller replied; 'the boi 179/020.' the boi controller informed us that they were showing the area as the boi 197/020. We asked where they got their information and they said it came directly from the poc of the user group. The controller then got me involved as the flm. I went to the military desk and asked the stmc (supervisor; traffic management specialist) if he had any information on this and was told that the waiver on file to be protected as the boi 179/020; however when the user group called to coordinate; they did ask for the boi 197/020. The stmc in flow took the waiver to the ZLC airspace office and asked them for clarification. They said that the waiver was a 'typo' and that the correct fix was the boi 197/020. The stmc then told the individual in the airspace office that they needed to correct the waiver. When the information sheet came to the floor today for implementation; it still contained the erroneous fix. As a result of the correction not being made; our controller vectored an aircraft into the launch area and right into harms way. At the point of penetration; the aircraft was at 15;000 and the airspace to be protected was FL200. Fortunately no incident occurred between the aircraft and the rocket. Recommendation: accountability for the airspace department; particularly in an instance where an error has been brought to their attention and they choose to not correct the error.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZLC controllers described airspace entry event; noting the information prepared by the procedures staff and posted at the sector was not accurate; causing the entry into the rocket launch area.

Narrative: We were presented with a special use area for a rocket launch on the BOI 179/020; 1NM radius. A CRJ was inbound to BOI from the southwest. The Controller on the sector vectored the aircraft west of the rocket launch area; and handed him off to BOI APCH. The BOI Controller immediately called and asked why we flew the CRJ right through the area of the rocket launch. Our Controller said; 'I didn't; I vectored him west.' The BOI Controller then inquired what we were showing for the launch area; and our Controller replied; 'The BOI 179/020.' The BOI Controller informed us that they were showing the area as the BOI 197/020. We asked where they got their information and they said it came directly from the POC of the user group. The Controller then got me involved as the FLM. I went to the military desk and asked the STMC (Supervisor; Traffic Management Specialist) if he had any information on this and was told that the waiver on file to be protected as the BOI 179/020; however when the user group called to coordinate; they did ask for the BOI 197/020. The STMC in flow took the waiver to the ZLC Airspace office and asked them for clarification. They said that the waiver was a 'typo' and that the correct fix was the BOI 197/020. The STMC then told the individual in the airspace office that they needed to correct the waiver. When the information sheet came to the floor today for implementation; it still contained the erroneous fix. As a result of the correction not being made; our Controller vectored an aircraft into the launch area and right into harms way. At the point of penetration; the aircraft was at 15;000 and the airspace to be protected was FL200. Fortunately no incident occurred between the aircraft and the rocket. Recommendation: accountability for the Airspace Department; particularly in an instance where an error has been brought to their attention and they choose to not correct the error.

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.