37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 841817 |
Time | |
Date | 200907 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | CZYZ.Airport |
State Reference | ON |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Experience | Flight Crew Last 90 Days 280 Flight Crew Total 20000 Flight Crew Type 3525 |
Person 2 | |
Function | First Officer Pilot Not Flying |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 9900 Flight Crew Type 3400 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Navigation deviation 1) this is the route taken from rlse 2 and loaded into the FMC on the ground in bos: bos mht syr J63 ehman yxu pmm.... 2) this is the pre departure clearance received from bos clearance: bos mht syr J63 ehman yxu J16 bae.... Revised segment: none 3) after passing yxu toronto center inquired as to what our next fix was. We discovered then that the route ATC had on file was the route filed with rlse 1. 4) dispatcher; upon inquiry with bos; learned that bos clearance had not updated the rlse 2 routing. Hence we received the original rlse 1 routing via pre departure clearance. Both crewmembers had checked the first part of the routing; which was the same in both routes; noted the no revised segment comment on the pre departure clearance and assumed we were good to go. Toronto center made it known otherwise; when after passing yxu and proceeding toward pmm rather than J16 bae. The mistake was corrected and the remainder of the rlse 1 route; which ATC had on file; was loaded into the FMC and flown. You can see this was a real sand trap. The only way we could have possibly caught the mistake was to have reviewed the routing in its entirety
Original NASA ASRS Text
Title: Flight crew chronicles confused clearance routing event when filed clearance; issued PDC clearance and ATC understood routing did not coincide leading to an unexpected course.
Narrative: Navigation deviation 1) this is the route taken from RLSE 2 and loaded into the FMC on the ground in BOS: BOS MHT SYR J63 EHMAN YXU PMM.... 2) This is the PDC received from BOS clearance: BOS MHT SYR J63 EHMAN YXU J16 BAE.... Revised segment: None 3) after passing YXU Toronto Center inquired as to what our next fix was. We discovered then that the route ATC had on file was the route filed with RLSE 1. 4) Dispatcher; upon inquiry with BOS; learned that BOS Clearance had not updated the RLSE 2 routing. Hence we received the original RLSE 1 routing via PDC. Both crewmembers had checked the first part of the routing; which was the same in both routes; noted the no revised segment comment on the PDC and assumed we were good to go. Toronto Center made it known otherwise; when after passing YXU and proceeding toward PMM rather than J16 BAE. The mistake was corrected and the remainder of the RLSE 1 route; which ATC had on file; was loaded into the FMC and flown. You can see this was a real sand trap. The only way we could have possibly caught the mistake was to have reviewed the routing in its entirety
Data retrieved from NASA's ASRS site as of April 2012 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.