 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZDV controller reports of opening up a position and not having the correct information displayed on eram (enroute automation modernization). No one entered information into the computer that a certain airspace was going to be hot. An aircraft was in the hot airspace. Controller thought it was the front line managers duty to enter this information.
| Attributes | |
| ACN | 1285986 |
| Time | |
| Date | 201508 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZDV.ARTCC |
| State Reference | CO |
| Environment | |
| Light | Dawn |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
It was first thing in the morning and we were opening sectors. I opened sector 28; 29; 30; 39; 46; 47. I was also getting a d-side at the time and told him to call me to listen into the briefing I was getting. After I opened those sectors another controller took the 29; 30; 46 airspace. I was briefed that R2601 was active FL349 and below. When I tried to display this airspace on my scope I could not. The controller on the other sector informed me I could not display it because it was not activated in eram (enroute automation modernization). He then went and turned it on in eram. Because it was not activated there were no alerts in uret (user request evaluation tool) and the airspace was not being displayed on high altitude scopes. There was also some confusion as my d-side briefed sector 29; 30; 46 opening. Once we got the restricted airspace activated in eram I noticed aircraft X in sector 30's airspace was in R2601 and informed the other sector. When airspace is going hot first thing in the morning a supervisor should be responsible to make sure it is activated in eram.
Original NASA ASRS Text
Title: ZDV Controller reports of opening up a position and not having the correct information displayed on ERAM (Enroute Automation Modernization). No one entered information into the computer that a certain airspace was going to be hot. An Aircraft was in the hot airspace. Controller thought it was the Front Line Managers duty to enter this information.
Narrative: It was first thing in the morning and we were opening sectors. I opened sector 28; 29; 30; 39; 46; 47. I was also getting a D-side at the time and told him to call me to listen into the briefing I was getting. After I opened those sectors another controller took the 29; 30; 46 airspace. I was briefed that R2601 was active FL349 and below. When I tried to display this airspace on my scope I could not. The controller on the other sector informed me I could not display it because it was not activated in ERAM (Enroute Automation Modernization). He then went and turned it on in ERAM. Because it was not activated there were no alerts in URET (User Request Evaluation Tool) and the airspace was not being displayed on high altitude scopes. There was also some confusion as my D-side briefed sector 29; 30; 46 opening. Once we got the restricted airspace activated in ERAM I noticed Aircraft X in sector 30's airspace was in R2601 and informed the other sector. When airspace is going hot first thing in the morning a supervisor should be responsible to make sure it is activated in ERAM.
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.