 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew report that after a revised clearance was received and loaded in the flight computer; a missing waypoint caused a track deviation.
| Attributes | |
| ACN | 1539850 |
| Time | |
| Date | 201805 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | PCT.TRACON |
| State Reference | VA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Next Generation Undifferentiated |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Pilot Not Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 484 Flight Crew Type 990 |
| Person 2 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 446 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Climbing on the terpz 6.ottto departure; ATC advised that we were tracking 'slightly north of course just a few miles after terpz waypoint.' as pm (pilot monitoring); I replied that we were flying the ottto transition; and after checking our legs page against the chart; it was evident that the aircraft was tracking from terpz direct to ottto; skipping the fix foxhl. The missing fix caused a slight deviation of a few degrees to the north of course.at the gate; we received a cdplc (controller-pilot data link communications) clearance and a subsequent revision. The revision did not contain an actual change in routing but in order to 'accept' the clearance the 'load' key must be executed. The cdplc free text revision per a screen shot from my phone indicated the route.when I pressed the load function; the terpz 6.ottto did not load at all; just the routing to the destination. I manually loaded the new departure in concurrence with the captain. We agreed the route matched the clearance and the release. We briefed the departure normally and it from my recollection it matched the chart. After the event on route page 2; we again loaded the departure to diagnose the cause of foxhl missing from our legs page. Each time terpz 6.ottto was selected foxhl indeed populated. We were both left confused as ottto only populated when the ottto transition was selected. Ottto was the active fix when ATC queried our position.
Original NASA ASRS Text
Title: B737 flight crew report that after a revised clearance was received and loaded in the flight computer; a missing waypoint caused a track deviation.
Narrative: Climbing on the TERPZ 6.OTTTO Departure; ATC advised that we were tracking 'slightly north of course just a few miles after TERPZ waypoint.' As PM (Pilot Monitoring); I replied that we were flying the OTTTO transition; and after checking our LEGS page against the chart; it was evident that the aircraft was tracking from TERPZ direct to OTTTO; skipping the fix FOXHL. The missing fix caused a slight deviation of a few degrees to the north of course.At the gate; we received a CDPLC (Controller-Pilot Data Link Communications) Clearance and a subsequent revision. The revision did not contain an actual change in routing but in order to 'ACCEPT' the clearance the 'LOAD' key must be executed. The CDPLC free text revision per a screen shot from my phone indicated the route.When I pressed the LOAD function; the TERPZ 6.OTTTO did not load at all; just the routing to the destination. I manually loaded the new departure in concurrence with the Captain. We agreed the route matched the clearance and the release. We briefed the departure normally and it from my recollection it matched the chart. After the event on ROUTE page 2; we again loaded the departure to diagnose the cause of FOXHL missing from our LEGS page. Each time TERPZ 6.OTTTO was selected FOXHL indeed populated. We were both left confused as OTTTO only populated when the OTTTO transition was selected. OTTTO was the active fix when ATC queried our position.
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.