 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Oceanic center controller reported they did not receive updates for a flight entering their airspace non-radar.
| Attributes | |
| ACN | 1586296 |
| Time | |
| Date | 201810 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZAN.ARTCC |
| State Reference | AK |
| Aircraft 1 | |
| Make Model Name | Widebody Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 11.0 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
This was a near identical problem as my previous dozen or so reports. The flight progress strip was flat in a radar bay with zero indication that it would enter the sector non radar. A strip scan caught the mistake and I made needed corrections. There were multiple aircraft on the airway that is 50 miles north and parallel to the center boundaries. Luckily (again) there was inadvertent separation standards (vertical and longitudinal). Nothing positive. When atop's (advance technology and oceanic procedures) receives a flight plan entering anchorage center; oakland center atop could be programed to immediately send a message to anchorage center of a revised altitude at the aircraft's current altitude; creating an update in fdp (flight data processing) that oakland center revised the altitude. Use this or any of the other suggestions I or anyone else has made to improve the safety of this operation. The round of crew briefings anchorage center leadership decided might mitigate this situation has not from my observations been effective as evidence from conversations I have had with other operational personnel.
Original NASA ASRS Text
Title: Oceanic Center Controller reported they did not receive updates for a flight entering their airspace non-radar.
Narrative: This was a near identical problem as my previous dozen or so reports. The flight progress strip was flat in a radar bay with zero indication that it would enter the sector non radar. A strip scan caught the mistake and I made needed corrections. There were multiple aircraft on the airway that is 50 miles north and parallel to the Center boundaries. Luckily (again) there was inadvertent separation standards (vertical and longitudinal). Nothing positive. When ATOP's (Advance Technology and Oceanic Procedures) receives a flight plan entering Anchorage Center; Oakland Center ATOP could be programed to immediately send a message to Anchorage Center of a revised altitude at the aircraft's current altitude; creating an update in FDP (Flight Data Processing) that Oakland Center revised the altitude. Use this or any of the other suggestions I or anyone else has made to improve the safety of this operation. The round of crew briefings Anchorage Center leadership decided might mitigate this situation has not from my observations been effective as evidence from conversations I have had with other operational personnel.
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.