37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1572982 |
Time | |
Date | 201808 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 250 Flight Crew Type 2364 |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 240 Flight Crew Total 16540 Flight Crew Type 4936 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
While climbing out of ZZZ on the RNAV departure; just as we passed the zzzzz intersection; the aircraft began to turn towards the next fix in the sequence. I am not sure if ZZZZZ1 was actually in the FMC at the time or not; but shortly after we began our turn; ATC told us that it looked like we missed ZZZZZ1 by about 6 miles. Still in the turn; I looked down at the FMC and saw that our previous fix showed zzzzz with ZZZZZ3 as the fix we were turning towards. The departure calls for zzzzz. ZZZZZ1. ZZZZZ2. ZZZZZ3. I replied with it looks like our previous fix was zzzzz and we are turning towards ZZZZZ3. The controller said we should be going to ZZZZZ1; but that it was ok. He instructed us to just go direct to ZZZZZ3. There was no further issue.I loaded the FMC with what was on our [flight plan]; prior to receiving our clearance. When I input the departure; I selected runway xxr then the departure then the transition. I checked the route for discontinuities; but I did not check each point on the departure. When we received our clearance from the FMC ATC feature; there was a new route prompt; but the route was the same that we were filed. The captain selected the load feature from the FMC and had to reload the departure. He said that he did it the same way that I did; but this happened during my walk around. I did review the clearance in the cpdlc (controller pilot datalink communications) and saw that the new route was actually our filed route.I am kind of at a loss as to how this can happen; given that we loaded it the way we always do. Obviously; had I checked each individual fix; I would have caught the problem. If we load the departure from the FMC correctly; I don't see how 2 fixes end up missing. We would have to physically delete them. If there were a discontinuity; and we closed it incorrectly; in this case it should have also deleted ZZZZZ3. That was not the case. ZZZZZ1 was a bypass fix on our departure and the turn was pretty significant; but even if the FMC sequenced an early turn; we should have seen ZZZZZ1 or ZZZZZ2 as our previous fix. It bothers me because I feel like the route was loaded the way we always load routes. I just want to be sure that it is not some FMC issue causing this to happen.there was an [company bulletin] that specifically said the 737 is now authorized to do this departure.
Original NASA ASRS Text
Title: B737 flight crew reported a Course Deviation due to several waypoints dropping out of the FMC after CPDLC clearance revision.
Narrative: While climbing out of ZZZ on the RNAV departure; just as we passed the ZZZZZ intersection; the aircraft began to turn towards the next fix in the sequence. I am not sure if ZZZZZ1 was actually in the FMC at the time or not; but shortly after we began our turn; ATC told us that it looked like we missed ZZZZZ1 by about 6 miles. Still in the turn; I looked down at the FMC and saw that our previous fix showed ZZZZZ with ZZZZZ3 as the fix we were turning towards. The departure calls for ZZZZZ. ZZZZZ1. ZZZZZ2. ZZZZZ3. I replied with it looks like our previous fix was ZZZZZ and we are turning towards ZZZZZ3. The controller said we should be going to ZZZZZ1; but that it was OK. He instructed us to just go direct to ZZZZZ3. There was no further issue.I loaded the FMC with what was on our [flight plan]; prior to receiving our clearance. When I input the departure; I selected runway XXR then the departure then the transition. I checked the route for discontinuities; but I did not check each point on the departure. When we received our clearance from the FMC ATC feature; there was a new route prompt; but the route was the same that we were filed. The Captain selected the load feature from the FMC and had to reload the departure. He said that he did it the same way that I did; but this happened during my walk around. I did review the clearance in the CPDLC (Controller pilot Datalink Communications) and saw that the new route was actually our filed route.I am kind of at a loss as to how this can happen; given that we loaded it the way we always do. Obviously; had I checked each individual fix; I would have caught the problem. If we load the departure from the FMC correctly; I don't see how 2 fixes end up missing. We would have to physically delete them. If there were a discontinuity; and we closed it incorrectly; in this case it should have also deleted ZZZZZ3. That was not the case. ZZZZZ1 was a bypass fix on our departure and the turn was pretty significant; but even if the FMC sequenced an early turn; we should have seen ZZZZZ1 or ZZZZZ2 as our previous fix. It bothers me because I feel like the route was loaded the way we always load routes. I just want to be sure that it is not some FMC issue causing this to happen.There was an [company bulletin] that specifically said the 737 is now authorized to do this departure.
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.