37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 200177 |
Time | |
Date | 199201 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : oth |
State Reference | OR |
Altitude | msl bound lower : 37000 msl bound upper : 37000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zse |
Operator | other |
Make Model Name | Military Transport |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller military : 2 controller non radar : 2 controller radar : 8 |
ASRS Report | 200177 |
Person 2 | |
Affiliation | government : faa |
Function | oversight : supervisor |
Qualification | controller : radar |
Experience | controller non radar : 8 controller radar : 6 |
ASRS Report | 200008 |
Events | |
Anomaly | non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Narrative:
Due to radio failures, 2 sectors were combined on 1 position, adjacent to my position of control. The controller was working approximately 25 aircraft, and there were 6 people crowded around the sector. In the confusion, I forgot to check an airspace boundary, and cleared the mac aircraft on a new routing, which took him through military released airspace. It had been approved by the next controller, who also was unaware of the airspace release, and was not discovered until 200 mi later, on descent with the next controller. The airspace was not being used at the time, but had been released 1 hour prior to aircraft departure to operate in it. Supplemental information from acn 200008: the problem was an oversight, but I believe the oversight was caused by a major distraction. The controllers involved were distracted by 1) severe WX, and 2) heavy workload in the sector on the immediate right, there was a frequency failure which caused 2 sectors to be combined on 1 and that 1 was very busy. The sector which had the deviation was trying to provide assistance to the busy sector.
Original NASA ASRS Text
Title: MIL ACFT INADVERTENTLY CLRED THROUGH MIL RELEASED AIRSPACE WITHOUT AUTHORIZATION.
Narrative: DUE TO RADIO FAILURES, 2 SECTORS WERE COMBINED ON 1 POS, ADJACENT TO MY POS OF CTL. THE CTLR WAS WORKING APPROX 25 ACFT, AND THERE WERE 6 PEOPLE CROWDED AROUND THE SECTOR. IN THE CONFUSION, I FORGOT TO CHK AN AIRSPACE BOUNDARY, AND CLRED THE MAC ACFT ON A NEW ROUTING, WHICH TOOK HIM THROUGH MIL RELEASED AIRSPACE. IT HAD BEEN APPROVED BY THE NEXT CTLR, WHO ALSO WAS UNAWARE OF THE AIRSPACE RELEASE, AND WAS NOT DISCOVERED UNTIL 200 MI LATER, ON DSCNT WITH THE NEXT CTLR. THE AIRSPACE WAS NOT BEING USED AT THE TIME, BUT HAD BEEN RELEASED 1 HR PRIOR TO ACFT DEP TO OPERATE IN IT. SUPPLEMENTAL INFO FROM ACN 200008: THE PROBLEM WAS AN OVERSIGHT, BUT I BELIEVE THE OVERSIGHT WAS CAUSED BY A MAJOR DISTR. THE CTLRS INVOLVED WERE DISTRACTED BY 1) SEVERE WX, AND 2) HVY WORKLOAD IN THE SECTOR ON THE IMMEDIATE R, THERE WAS A FREQ FAILURE WHICH CAUSED 2 SECTORS TO BE COMBINED ON 1 AND THAT 1 WAS VERY BUSY. THE SECTOR WHICH HAD THE DEV WAS TRYING TO PROVIDE ASSISTANCE TO THE BUSY SECTOR.
Data retrieved from NASA's ASRS site as of July 2007 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.