 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLC supervisor described an incorrect restricted area posting event indicating the present procedure of utilizing two separate forms for posting is confusing and leads to mistakes as reported.
| Attributes | |
| ACN | 891752 |
| Time | |
| Date | 201006 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZLA.ARTCC |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Person 1 | |
| Function | Supervisor / CIC |
| Person 2 | |
| Function | Supervisor / CIC |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
The mos; military operations specialist; received release of restricted area airspace and forwarded it to the area in an incorrect release sheet. In this case R2501 real time changes are written on a 'released at or above' sheet and then given to the area. The mos incorrectly gave me a 'hot at or below' worksheet. The R2501 was hot; aob (at or below) 160 and was posted in the area as being released aoa (at or above) 160. There are 2 separate worksheets for the real time release of military airspace; there is the 'hot at or below' or the 'released at or above'. The problem is that when you are given a worksheet for a specific military airspace we make the assumption that it is on the correct worksheet. I do not expect the R2501 airspace to be posted on a 'hot at or below' worksheet; therefore all I saw was the altitude and posted it as being released AOA160 (R2501 is always posted on a 'released at or above worksheet). I posted the airspace incorrectly; it should have been posted as released aoa 170.there were no airspace deviations in this incident and I did report the incident. There should be only 1 sheet that reflects the status of real time changes; this would avoid the incorrect posting of airspace. Recommendation; for consistency; there should only be 1 worksheet for the release of military airspace. Having 2 separate worksheets allows for human error to incorrectly annotate releases.
Original NASA ASRS Text
Title: ZLC Supervisor described an incorrect restricted area posting event indicating the present procedure of utilizing two separate forms for posting is confusing and leads to mistakes as reported.
Narrative: The MOS; Military Operations Specialist; received release of restricted area airspace and forwarded it to the area in an incorrect release sheet. In this case R2501 real time changes are written on a 'released at or above' sheet and then given to the area. The MOS incorrectly gave me a 'Hot at or below' worksheet. The R2501 was hot; AOB (at or below) 160 and was posted in the area as being released AOA (at or above) 160. There are 2 separate worksheets for the real time release of military airspace; there is the 'hot at or below' or the 'released at or above'. The problem is that when you are given a worksheet for a specific military airspace we make the assumption that it is on the correct worksheet. I do not expect the R2501 airspace to be posted on a 'hot at or below' worksheet; therefore all I saw was the altitude and posted it as being released AOA160 (R2501 is always posted on a 'released at or above worksheet). I posted the airspace incorrectly; it should have been posted as released AOA 170.There were no airspace deviations in this incident and I did report the incident. There should be only 1 sheet that reflects the status of real time changes; this would avoid the incorrect posting of airspace. Recommendation; for consistency; there should only be 1 worksheet for the release of military airspace. Having 2 separate worksheets allows for human error to incorrectly annotate releases.
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.