37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1366433 |
Time | |
Date | 201606 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZNY.ARTCC |
State Reference | NY |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Gulfstream V / G500 / G550 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | A330 |
Operating Under FAR Part | Part 129 |
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) 0.9 |
Person 2 | |
Function | Oceanic Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
At the time that I took over the sector; the sector que was already filled with many flight plans from gander control that all had routing issues due to gander putting in the wrong track information. I had to spend a lot of time rerouting aircraft because the routes sent to us were not correct. I received a call from gander about a flight that they couldn't send over and had to be done manually. I took the information and looked at the route and saw that they were filed from gander to my oceanic to moncton center and back down to my oceanic again. I moved the route over to the right column and fixed it. But then I clicked accept manual instead of negotiate manual. That saved the previous route and didn't save the new route that I had gander issue the aircraft. At the time I was made aware that I had possibly been involved in the loss of separation between two aircraft both at 40000 feet.slowing down and making sure that the blue data is same as what was coordinated. Also having shanwick and gander control's not truncate routings. If they take them off of their original track to tie them back into a point on their routing after landfall fix. That will reduce the reroutes that need to be given and mistakes.
Original NASA ASRS Text
Title: ZNY ARTCC Controller aircraft on an oceanic track routing was issued a new route. The new route was not entered into the system and a conflict with another aircraft resulted.
Narrative: At the time that I took over the sector; the sector que was already filled with many flight plans from Gander Control that all had routing issues due to Gander putting in the wrong track information. I had to spend a lot of time rerouting aircraft because the routes sent to us were not correct. I received a call from Gander about a flight that they couldn't send over and had to be done manually. I took the information and looked at the route and saw that they were filed from Gander to my oceanic to Moncton center and back down to my oceanic again. I moved the route over to the right column and fixed it. But then I clicked accept manual instead of negotiate manual. That saved the previous route and didn't save the new route that I had gander issue the aircraft. At the time I was made aware that I had possibly been involved in the loss of separation between two aircraft both at 40000 feet.Slowing down and making sure that the blue data is same as what was coordinated. Also having Shanwick and Gander Control's not truncate routings. If they take them off of their original track to tie them back into a point on their routing after landfall fix. That will reduce the reroutes that need to be given and mistakes.
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.