37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1545855 |
Time | |
Date | 201805 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | EGGX.ARTCC |
State Reference | FO |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Person 2 | |
Function | First Officer Relief Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Total 15000 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
The clearance we received from shanwick for our oceanic crossing contained an altitude change; which was noted at the bottom of the clearance. It also had contained a new exit point that we initially did not pick up on. After receiving the clearance; I sent dispatch a message about the altitude change. They sent us new M14's and also did not pick up on the fact that the exit point had changed. The first officer and I started the process of reviewing the clearance comparing the points on the clearance to the points of the flight plan. My first officer had not flown the north atlantic in a while so we had a discussion on how both of us are required to bring all the points down to the scratch pad to expand the coordinates to check for errors. We did not catch the exit point change. About this time; shanwick sent us the routine message to confirm route. We sent the route as was loaded. Shanwick responded with a message to check exit point. That is when we picked up on the exit point change. Route was corrected and the flight continued.while I am embarrassed and regret this happened; I am glad the system of checks and balances was in place. The fact that there was an altitude change as well as only an exit point change started the process. Another contributing factor was the discussion we had about how to check the route. This took much longer than normal. Also; usually as soon as we get our oceanic clearance we get a message from dispatch as well about the changes. They sent new flight logs; but also missed the oceanic exit point change. While we did check the route as per SOP; I mistakenly did not pick up on the exit point change. Entirely my fault; and I guess the only excuse is that I saw what I expected to see; not what I should have seen. I am glad the system worked and that shanwick caught the error. There was never a navigation error as it was the exit point of the oceanic track that was wrong and we had just logged on with shanwick cpdlc (controller-pilot data link communications) and were entering the track when the event happened.our airline has a great north atlantic guide that I use for every crossing. Even with the guide and using the standard operating procedures and failed to note the exit point change. Pure human error.
Original NASA ASRS Text
Title: Air carrier flight crew reported not noticing that the exit point of the Oceanic track clearance had changed.
Narrative: The clearance we received from Shanwick for our Oceanic crossing contained an altitude change; which was noted at the bottom of the clearance. It also had contained a new exit point that we initially did not pick up on. After receiving the clearance; I sent dispatch a message about the altitude change. They sent us new M14's and also did not pick up on the fact that the exit point had changed. The First Officer and I started the process of reviewing the clearance comparing the points on the clearance to the points of the flight plan. My First Officer had not flown the North Atlantic in a while so we had a discussion on how both of us are required to bring all the points down to the scratch pad to expand the coordinates to check for errors. We did not catch the exit point change. About this time; Shanwick sent us the routine message to confirm route. We sent the route as was loaded. Shanwick responded with a message to check exit point. That is when we picked up on the exit point change. Route was corrected and the flight continued.While I am embarrassed and regret this happened; I am glad the system of checks and balances was in place. The fact that there was an altitude change as well as ONLY an exit point change started the process. Another contributing factor was the discussion we had about how to check the route. This took much longer than normal. Also; usually as soon as we get our Oceanic Clearance we get a message from Dispatch as well about the changes. They sent new flight logs; but also missed the oceanic exit point change. While we did check the route as per SOP; I mistakenly did not pick up on the exit point change. Entirely my fault; and I guess the only excuse is that I saw what I expected to see; not what I should have seen. I am glad the system worked and that Shanwick caught the error. There was never a navigation error as it was the exit point of the Oceanic Track that was wrong and we had just logged on with Shanwick CPDLC (Controller-Pilot Data Link Communications) and were entering the track when the event happened.Our airline has a great North Atlantic guide that I use for every crossing. Even with the guide and using the Standard Operating Procedures and failed to note the exit point change. Pure human error.
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.