 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Zan center controller reported an aircraft entered a non-radar sector on a route that did not ensure separation from other traffic.
| Attributes | |
| ACN | 1504768 |
| Time | |
| Date | 201712 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZAN.ARTCC |
| State Reference | AK |
| Aircraft 1 | |
| Make Model Name | B777 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Oceanic |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute Oceanic |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 9 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Much like several of my previous reports aircraft X was entering the sector non-radar without 3 different controllers recognizing it would potentially conflict with traffic along its route. We got lucky yet again and there happened to be no traffic. This was a particularly hard to catch routing as his first strip posting was a fix that is a very uncommon posting for non-radar traffic.I amend my suggestion on how to fix this. A better plan than all the fixes on the boundary is to send the controller a update that the next sector has accepted coordination on aircraft X just as it does outbound. This would make the situation very hard to occur. We have discussed this solution at the facility with good responses. I was hoping that you could help generate momentum at the facility leadership level to get this done as soon as possible.
Original NASA ASRS Text
Title: ZAN Center Controller reported an aircraft entered a non-radar sector on a route that did not ensure separation from other traffic.
Narrative: Much like several of my previous reports Aircraft X was entering the sector non-radar without 3 different controllers recognizing it would potentially conflict with traffic along its route. We got lucky yet again and there happened to be no traffic. This was a particularly hard to catch routing as his first strip posting was a fix that is a very uncommon posting for non-radar traffic.I amend my suggestion on how to fix this. A better plan than all the fixes on the boundary is to send the Controller a update that the next sector has accepted coordination on Aircraft X just as it does outbound. This would make the situation very hard to occur. We have discussed this solution at the facility with good responses. I was hoping that you could help generate momentum at the facility leadership level to get this done ASAP.
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.