 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Controller reported using a configuration that did not show an airspace that was open. Controller thought airspace was closed and had an airspace violation.
| Attributes | |
| ACN | 1743769 |
| Time | |
| Date | 202005 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 12 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
I relieved my fellow controller; they informed me during the briefing that ZZZ approach (ZZZ) was open. I sat down and applied my mid configuration settings. My mid configuration settings default to ZZZ airspace not being depicted because typically when we work the mid shift; ZZZ is closed. I forgot to show that the airspace was open on my scope. I had an IFR aircraft; aircraft X; westbound and 080. I checked the routing on aircraft X and it was good so I tried to initiate a handoff to ZZZ1 approach which was still about 60 miles away. The handoff failed; I assumed it failed because the aircraft was too far from ZZZ1's boundary. I didn't look into it any further. Because I tried to initiate the handoff to ZZZ1; the aircraft's auto handoff was inhibited and ended up flying about one mile into ZZZ airspace without a handoff until I received a call from ZZZ asking if I was talking with aircraft X. I said yes; and proceeded to hand off the aircraft and ship them to ZZZ.during this pandemic I should have changed my mid configuration settings to default to showing ZZZ open. We are on a mid configuration more often due to low volume and if I had been depicting ZZZ airspace I would not have forgotten that they were open and I would have sent the handoff to them before violating their airspace.
Original NASA ASRS Text
Title: Controller reported using a configuration that did not show an airspace that was open. Controller thought airspace was closed and had an airspace violation.
Narrative: I relieved my fellow Controller; they informed me during the briefing that ZZZ Approach (ZZZ) was open. I sat down and applied my mid configuration settings. My mid configuration settings default to ZZZ airspace not being depicted because typically when we work the Mid shift; ZZZ is closed. I forgot to show that the airspace was open on my scope. I had an IFR aircraft; Aircraft X; westbound and 080. I checked the routing on Aircraft X and it was good so I tried to initiate a handoff to ZZZ1 Approach which was still about 60 miles away. The handoff failed; I assumed it failed because the aircraft was too far from ZZZ1's boundary. I didn't look into it any further. Because I tried to initiate the handoff to ZZZ1; the aircraft's auto handoff was inhibited and ended up flying about one mile into ZZZ airspace without a handoff until I received a call from ZZZ asking if I was talking with Aircraft X. I said yes; and proceeded to hand off the aircraft and ship them to ZZZ.During this pandemic I should have changed my mid configuration settings to default to showing ZZZ open. We are on a mid configuration more often due to low volume and if I had been depicting ZZZ airspace I would not have forgotten that they were open and I would have sent the handoff to them before violating their airspace.
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.