 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZMP controller reports of a restricted area not being posted hot. This caused many aircraft to possibly deviate into the airspace.
| Attributes | |
| ACN | 1192179 |
| Time | |
| Date | 201408 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZMP.ARTCC |
| State Reference | MN |
| Environment | |
| Light | Daylight |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
R4202 airspace did not turn on automatically on the radar scope. Numerous aircraft were through that airspace all day; and it is unknown if any were in an unsafe situation; but they went through an active restricted area all morning long; and nobody caught it until xa:00 local. One possible reason that nobody in area 1 caught the error is because we were extremely busy and short staffed; during [a nearby aviation event]; and everyone was focused on separating aircraft and probably forgot to look at the schedule sheet. If there's anything that proves we were short-staffed; this is it. As soon as a d-side was put in that sector (1st time all morning; there wasn't staffing available for a d-side earlier); the sector noticed it after that. This provs having a second set of eyes are helpful; and area 1 needs to be staffed correctly to mitigate these errors.the mos scheduler should have responsibility to make sure all the airspace's are scheduled correctly in the computer. Staff area 1 correctly to mitigate these types of errors.
Original NASA ASRS Text
Title: ZMP Controller reports of a Restricted Area not being posted Hot. This caused many aircraft to possibly deviate into the airspace.
Narrative: R4202 airspace did not turn on automatically on the radar scope. Numerous aircraft were through that airspace all day; and it is unknown if any were in an unsafe situation; but they went through an active restricted area all morning long; and nobody caught it until XA:00 local. One possible reason that nobody in Area 1 caught the error is because we were extremely busy and short staffed; during [a nearby aviation event]; and everyone was focused on separating aircraft and probably forgot to look at the schedule sheet. If there's anything that proves we were short-staffed; this is it. As soon as a D-Side was put in that sector (1st time all morning; there wasn't staffing available for a D-Side earlier); the sector noticed it after that. This provs having a second set of eyes Are helpful; and Area 1 needs to be staffed correctly to mitigate these errors.The MOS scheduler should have responsibility to make sure all the airspace's are scheduled correctly in the computer. Staff Area 1 correctly to mitigate these types of errors.
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.