 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLC center controller reported an airspace violation due to incorrect display showing times and altitude for a restricted area.
| Attributes | |
| ACN | 1624795 |
| Time | |
| Date | 201903 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZLC.ARTCC |
| State Reference | UT |
| Aircraft 1 | |
| Make Model Name | A330 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR WAATS 5 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 9 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was descending to cross knole at 170 on the WAATS5 arrival within the confines of the south uttr [utah testing and training range]. The south uttr was displayed active 100 and below and the weather message agreed. Clover controller called and asked if we knew the airspace was active 999 and below? The 40 controller asked if it was currently active and clover confirmed it had been active for a while. Clover reluctantly stated; 'well; I guess point out approved.' when this was brought to management's attention; it was blown off. I doubt a report was filed on this event due to the ZLC management double standard and constant sweeping under the rug. Every time I have seen the south uttr active 999 and below it is due to live missile launches. Loss of life could have occurred due to this oversight. Every person that handles airspace needs some sort of recurrent training on a consistent basis. The ball is dropped nearly every day. Clearly what we are doing is not working. This was not the only airspace that was entered incorrectly at the time; or range was active but not displayed.
Original NASA ASRS Text
Title: ZLC Center Controller reported an airspace violation due to incorrect display showing times and altitude for a restricted area.
Narrative: Aircraft X was descending to cross KNOLE at 170 on the WAATS5 arrival within the confines of the south UTTR [Utah Testing and Training Range]. The south UTTR was displayed active 100 and below and the weather message agreed. Clover Controller called and asked if we knew the airspace was active 999 and below? The 40 Controller asked if it was currently active and Clover confirmed it had been active for a while. Clover reluctantly stated; 'Well; I guess point out approved.' When this was brought to management's attention; it was blown off. I doubt a report was filed on this event due to the ZLC management double standard and constant sweeping under the rug. Every time I have seen the south UTTR active 999 and below it is due to live missile launches. Loss of life could have occurred due to this oversight. Every person that handles airspace needs some sort of recurrent training on a consistent basis. The ball is dropped nearly every day. Clearly what we are doing is not working. This was not the only airspace that was entered incorrectly at the time; or range was active but not displayed.
Data retrieved from NASA's ASRS site 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.