37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1466236 |
Time | |
Date | 201707 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZLC.ARTCC |
State Reference | UT |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute Instructor |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
There is a large force exercise (lfe). The stationary altrv (altitude reservation) is set for 14;000 to 17;900. The NOTAM for this altrv was filed for xb:00 to xf:00. The paperwork and agreement for the lfe was to activate the altrv at xb:30. Cowboy called the area on the phone and requested the airspace (including the altrv) 45 minutes early. Xa:45. I informed the supervisor (who I believe was not in charge of the area at the time; but was in the area not on sector) that the airspace was not NOTAM'd below FL180 and that we could not release it. She scoffed at me and continued to allow the coordination to continue. The airspace was released to cowboy control at xa:45. I took the sector soon after my concerns for the rules and the safety of the flying public were disregarded.aircraft X called for VFR flight following soon after I took the sector. My trainee informed the aircraft that his route of flight wasn't going to be allowed because of the altrv. The pilot questioned us and asked for the NOTAM number. The embarrassing thing is that had our facility complied with the very clear times printed on the NOTAM available to us; as federal regulation requires; the aircraft would have been clear of the altrv before activation. Additionally; the jurisdiction of the airspace released in the altrv (again; 14;000 to 17;900) didn't belong to ZLC. Mountain home RAPCON had been given the airspace underlying that altrv 16;000 and below. It became evident to us on the sector that mountain home RAPCON had not been notified of the release of airspace to a military radar unit when they called to request additional airspace (FL230 and below). This whole fiasco had no business in the NAS. It has become clear to me that if the military asks for airspace; I must allow them to use it regardless of NOTAM status; airspace jurisdiction; or safety to the flying public. When I confronted the supervisor about the discrepancy in ZLC's actions and federal regulation; the response I received made it clear that I was in the wrong. I will now train any incoming controllers that releasing airspace to the military is of utmost importance. I will also urge and explain to my coworkers that this is how it works. We are not to follow federal regulations if it at all imposes an inconvenience or delay to a military entity.
Original NASA ASRS Text
Title: ZLC Center Controller reported that an altitude reservation was started earlier than planned which caused an aircraft to have to alter its route.
Narrative: There is a Large Force Exercise (LFE). The stationary ALTRV (Altitude Reservation) is set for 14;000 to 17;900. The NOTAM for this ALTRV was filed for XB:00 to XF:00. The paperwork and agreement for the LFE was to activate the ALTRV at XB:30. Cowboy called the area on the phone and requested the airspace (including the ALTRV) 45 minutes early. XA:45. I informed the supervisor (who I believe was not in charge of the area at the time; but was in the area not on sector) that the airspace was not NOTAM'd below FL180 and that we could not release it. She scoffed at me and continued to allow the coordination to continue. The airspace was released to Cowboy Control at XA:45. I took the sector soon after my concerns for the rules and the safety of the flying public were disregarded.Aircraft X called for VFR flight following soon after I took the sector. My trainee informed the aircraft that his route of flight wasn't going to be allowed because of the ALTRV. The pilot questioned us and asked for the NOTAM number. The embarrassing thing is that had our facility complied with the very clear times printed on the NOTAM available to us; as Federal Regulation requires; the aircraft would have been clear of the ALTRV before activation. Additionally; the jurisdiction of the airspace released in the ALTRV (again; 14;000 to 17;900) didn't belong to ZLC. Mountain Home RAPCON had been given the airspace underlying that ALTRV 16;000 and below. It became evident to us on the sector that Mountain Home RAPCON had not been notified of the release of airspace to a Military Radar Unit when they called to request additional airspace (FL230 and below). This whole fiasco had no business in the NAS. It has become clear to me that if the military asks for airspace; I must allow them to use it regardless of NOTAM status; airspace jurisdiction; or safety to the flying public. When I confronted the supervisor about the discrepancy in ZLC's actions and federal regulation; the response I received made it clear that I was in the wrong. I will now train any incoming controllers that releasing airspace to the military is of utmost importance. I will also urge and explain to my coworkers that this is how it works. We are not to follow federal regulations if it at all imposes an inconvenience or delay to a military entity.
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.