37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1335035 |
Time | |
Date | 201602 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Widebody Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
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) 7 |
Person 2 | |
Function | Oceanic Enroute |
Qualification | Air Traffic Control Developmental |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X and aircraft Y were coming out of ZLA; a radar/oceanic transition sector into oakland oceanic. Both aircraft were assigned flight level 300. Aircraft X was routed ficky direct 28n130w. Aircraft Y was routed ficky foots flity. They had 8 minutes longitudinal (10 minutes minimum separation) and approximately 30 miles lateral (50 miles minimum separation). The aircraft were slightly diverging; but not enough for the 15 degree rule. I told the ZLA controller to route aircraft Y direct flity. This would take the aircraft north of ficky/foots and enter non radar airspace with 70 miles separation from aircraft X. The ZLA controller put the route in the machine; I approved the direct routing; and it cleared up the conflict on my screen.after coming back from break; my relieving controller advised me that aircraft Y reported over foots which was no longer being probed by atop instead of direct flity on the route I had previously coordinated. After conforming the position report with aircraft Y; he immediately issued a clearance to gain another form of separation.it appears that the aircraft never received the reroute clearance that I had coordinated with the controller.controllers need to follow through with clearances that are coordinated; keep the routing in the machine up to date; and follow sops. The aircraft could not have been in flat track before radar termination as he was off the route in the machine by about 40 miles.
Original NASA ASRS Text
Title: An Oceanic Controller coordinated a route change for an aircraft they were receiving in their sector. The transferring Controller failed to issue the new route.
Narrative: Aircraft X and aircraft Y were coming out of ZLA; a radar/oceanic transition sector into Oakland Oceanic. Both aircraft were assigned Flight Level 300. Aircraft X was routed FICKY direct 28N130W. Aircraft Y was routed FICKY FOOTS FLITY. They had 8 minutes longitudinal (10 minutes minimum separation) and approximately 30 miles lateral (50 miles minimum separation). The aircraft were slightly diverging; but not enough for the 15 degree rule. I told the ZLA controller to route aircraft Y direct FLITY. This would take the aircraft north of FICKY/FOOTS and enter non radar airspace with 70 miles separation from aircraft X. The ZLA controller put the route in the machine; I approved the direct routing; and it cleared up the conflict on my screen.After coming back from break; my relieving controller advised me that aircraft Y reported over FOOTS which was no longer being probed by ATOP instead of direct FLITY on the route I had previously coordinated. After conforming the position report with aircraft Y; he immediately issued a clearance to gain another form of separation.It appears that the aircraft never received the reroute clearance that I had coordinated with the controller.Controllers need to follow through with clearances that are coordinated; keep the routing in the machine up to date; and follow SOPs. The aircraft could not have been in FLAT track before radar termination as he was off the route in the machine by about 40 miles.
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.