37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1601518 |
Time | |
Date | 201812 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZMA.ARTCC |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Total 25000 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Over zqa; evidently we turned outbound on the zqa transition to zbv vs. Direct zbv. The assigned route was to join the arrival at zbv. ATC directed us to correct course and proceed direct to zbv. During loading of the route in FMS; selecting the STAR; zqa was the only transition which included zbv. Because of the discontinuity created by selecting that transition; now 2 zqa's and 2 zbv's existed. I believe I may have incorrectly placed the transition point; thereby loading the transition instead. I suspect the route check was acceptable because it was consistent with the transition. During a subsequent phone call to ATC; we were advised that numerous others; including several airlines and general aviation; have been doing the same since the recent route/airway changes have been implemented. In our case; if this is what happened; I believe the duplicate zqa and zbv fixes and all of their associated points loaded by selecting the transition; the similar identifiers (zqa/zbv); as well as the transition point being only available by selecting the zqa transition; may have created the confusion during the loading and subsequent 'clean up' of the route in the FMS.
Original NASA ASRS Text
Title: B737 Captain reported enroute clearance deviation due to FMC loading procedural error.
Narrative: Over ZQA; evidently we turned outbound on the ZQA transition to ZBV vs. direct ZBV. The assigned route was to join the arrival at ZBV. ATC directed us to correct course and proceed direct to ZBV. During loading of the route in FMS; selecting the STAR; ZQA was the only transition which included ZBV. Because of the discontinuity created by selecting that transition; now 2 ZQA's and 2 ZBV's existed. I believe I may have incorrectly placed the transition point; thereby loading the transition instead. I suspect the route check was acceptable because it was consistent with the transition. During a subsequent phone call to ATC; we were advised that numerous others; including several airlines and general aviation; have been doing the same since the recent route/airway changes have been implemented. In our case; if this is what happened; I believe the duplicate ZQA and ZBV fixes and all of their associated points loaded by selecting the transition; the similar identifiers (ZQA/ZBV); as well as the transition point being only available by selecting the ZQA transition; may have created the confusion during the loading and subsequent 'clean up' of the route in the FMS.
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.