 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZOB controller reported a recurring lack and method of coordination for scheduling moas.
| Attributes | |
| ACN | 1517165 |
| Time | |
| Date | 201802 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZOB.ARTCC |
| State Reference | OH |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | No Aircraft |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 25 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
Working the lan/fnt right position; I noticed 3 military proposals filed to R5201 in ZMP airspace. In the remarks of the flight plans it indicated they would be also be using the steelhead MOA; which is in my airspace. I did not have any information about a pending steelhead MOA. I asked the controller in charge to check; which he did with our military desk. They said that the steelhead MOA was not scheduled. ZMP is the controlling facility for this airspace. Within a few minutes of this answer the steelhead MOA displayed on my radar scope in pending status. I called the ZMP controller for verification; and he told me that the steelhead was going 'hot' in just a few minutes. Fortunately I did not have aircraft currently in the airspace.this was not the first time there has been a communication and coordination issue regarding the military airspace; but in my opinion this was the worst and could have easily led to non-participating aircraft in an active military airspace.since there are multiple centers (ZMP; ZOB; ZAU and czyz); multiple approach controls; and many VFR aircraft that fly in that area I think a review is needed of how this airspace is scheduled and the information sent out. This also affects how the airspace is cancelled or ended early; which also needs to be coordinated better are there redundant systems in place so that confusion won't happen?
Original NASA ASRS Text
Title: ZOB Controller reported a recurring lack and method of coordination for scheduling MOAs.
Narrative: Working the LAN/FNT R position; I noticed 3 military proposals filed to R5201 in ZMP airspace. In the remarks of the flight plans it indicated they would be also be using the Steelhead MOA; which is in my airspace. I did not have any information about a pending Steelhead MOA. I asked the CIC to check; which he did with our military desk. They said that the Steelhead MOA was not scheduled. ZMP is the controlling facility for this airspace. Within a few minutes of this answer the Steelhead MOA displayed on my radar scope in pending status. I called the ZMP controller for verification; and he told me that the Steelhead was going 'hot' in just a few minutes. Fortunately I did not have aircraft currently in the airspace.This was not the first time there has been a communication and coordination issue regarding the military airspace; but in my opinion this was the worst and could have easily led to non-participating aircraft in an active military airspace.Since there are multiple Centers (ZMP; ZOB; ZAU and CZYZ); multiple approach controls; and many VFR aircraft that fly in that area I think a review is needed of how this airspace is scheduled and the information sent out. This also affects how the airspace is cancelled or ended early; which also needs to be coordinated better Are there redundant systems in place so that confusion won't happen?
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.