Narrative:

R2310 requires a NOTAM to be issued 60 hours in advance of use. Mos position submitted a request to prc AFSS on the evening of dec. Xath for the issuance of a NOTAM that would be listed on the FAA naimes NOTAM web site from 12/xb/09 to the end of the NOTAM at 12/xe/09. As is SOP; the tmc specialist on duty that evening faxed a copy of all of the requested arizona notams to prc AFSS so that the prc specialist can type the NOTAM verbatim. The tmc then checks the accuracy of the NOTAM when it is printed out on the strip printer. On 12/xd/09 fhu tower called me at the mos position to notify me that he had noticed that the naimes NOTAM page was showing that R2310 was going to be active in the fhu area. Since R2310 is approximately 120 NM from fhu that specialist realized there was a problem. I investigated the naimes NOTAM page. You can search for a NOTAM 3 ways on the home page: location; NOTAM number; or radius of a NAVAID. Fhu had searched for local notams and found R2310. I searched via facility (ZAB) as well as by radius search of iwa and did not find R2310 notamed. In fact; R2310 was showing inactive via the radius search of iwa when it had in fact been in use for more that 7 hours. The only place it was showing as in use was by checking fhu notams. That is the reason that I can not know if R2310 was violated by a non-flight following aircraft. Without reviewing the radar data for those 8+ hours there is no way to tell. I pulled the original fax out of the 15 day file to ascertain whether or not there was a glitch in the NOTAM page; the special use airspace management page; the program that we used to produce the NOTAM request page; or the NOTAM itself. I had to determine that before I could call and have prc issue an immediate NOTAM to cover the remainder to the period that was in use. The notams that come off of the strip printer should match exactly the fax. The fax of the R2310A request read '2310A xc xx:00 xd xl:00 iwa' the NOTAM that prc AFSS typed in was 'fhu 12/033 fhu airspace R2310A act wef 0912xa1400-0912xb0100.' I believe what happened was that the prc specialist probably used some type of recall button as the NOTAM she/he issued before that was 'fhu 12/032 fhu airspace R2303A/B/C........' I then faxed the incorrect NOTAM and the correct request to prc AFSS and called the supervisor so that they could issue an immediate NOTAM for the remainder of the active period. I recommend:1. Train the mos specialists to check that the tie-in navid that AFSS issues is the same as the one that mos tmc faxes match....to be honest I wasn't trained to and didn't check in the past. Most do not check the navid just that the dates and times are accurate.2. Train AFSS specialists to use caution when using a recall feature and to also use #1.3. Adapt AFSS equipment to give an error message when the tie-in navid does not match the restricted airspace

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAB Traffic Management Specialist detects a restricted airspace use NOTAM is improperly constructed by Flight Service and thus improperly disseminated.

Narrative: R2310 requires a NOTAM to be issued 60 hours in advance of use. MOS position submitted a request to PRC AFSS on the evening of Dec. XAth for the issuance of a NOTAM that would be listed on the FAA NAIMES NOTAM web site from 12/XB/09 to the end of the NOTAM at 12/XE/09. As is SOP; the TMC specialist on duty that evening faxed a copy of all of the requested Arizona NOTAMs to PRC AFSS so that the PRC specialist can type the NOTAM verbatim. The TMC then checks the accuracy of the NOTAM when it is printed out on the strip printer. On 12/XD/09 FHU Tower called me at the MOS position to notify me that he had noticed that the NAIMES NOTAM page was showing that R2310 was going to be active in the FHU area. Since R2310 is approximately 120 NM from FHU that specialist realized there was a problem. I investigated the NAIMES NOTAM page. You can search for a NOTAM 3 ways on the home page: location; NOTAM number; or radius of a NAVAID. FHU had searched for local NOTAMs and found R2310. I searched via facility (ZAB) as well as by radius search of IWA and did not find R2310 NOTAMed. In fact; R2310 was showing inactive via the radius search of IWA when it had in fact been in use for more that 7 hours. The only place it was showing as in use was by checking FHU NOTAMs. That is the reason that I can not know if R2310 was violated by a non-flight following aircraft. Without reviewing the radar data for those 8+ hours there is no way to tell. I pulled the original fax out of the 15 day file to ascertain whether or not there was a glitch in the NOTAM page; the Special Use Airspace Management page; the program that we used to produce the NOTAM request page; or the NOTAM itself. I had to determine that before I could call and have PRC issue an immediate NOTAM to cover the remainder to the period that was in use. The NOTAMs that come off of the strip printer should match exactly the fax. The fax of the R2310A request read '2310A XC xx:00 XD xl:00 IWA' The NOTAM that PRC AFSS typed in was 'FHU 12/033 FHU AIRSPACE R2310A ACT WEF 0912XA1400-0912XB0100.' I believe what happened was that the PRC specialist probably used some type of recall button as the NOTAM she/he issued before that was 'FHU 12/032 FHU AIRSPACE R2303A/B/C........' I then faxed the incorrect NOTAM and the correct request to PRC AFSS and called the supervisor so that they could issue an immediate NOTAM for the remainder of the active period. I recommend:1. Train the MOS specialists to check that the tie-in NAVID that AFSS issues is the same as the one that MOS TMC faxes match....to be honest I wasn't trained to and didn't check in the past. Most do not check the NAVID just that the dates and times are accurate.2. Train AFSS specialists to use caution when using a recall feature and to also use #1.3. Adapt AFSS equipment to give an error message when the tie-in NAVID does not match the Restricted Airspace

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.