37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1326768 |
Time | |
Date | 201601 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZLA.ARTCC |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Getting ready for our flight I got to the airplane and started planning. Because I was the pm on this leg; I was going to let the first officer (first officer) set up the FMS. I did in fact enter the 'canned' route and the flight number on the first page of the route page. I did not look any further; as we still did not have the pre departure clearance. I got out my surface tablet and entered the filed route in the jepp app. While I was doing that the first officer came in and started loading the box. We received the pre departure clearance and I remember him commenting that the route was different. He began to fix the routing (canned route vs cleared route). Once we started taxiing out things got busy.we had planned on departing 28L. Just as we started to turn the corner to hold short; tower instructed us to cross 28L and hold short of 28R. As we crossed the left; the first officer was making the changes in to box and loaded the proper runway and reloaded the departure procedure. I confirmed the change and we were given a takeoff clearance with traffic on an 8 mile final. Everything was going normally and we were given a couple of vectors for our climb; and eventually told to go direct to loshn intersection. We complied. This is where the problem came in. I had not verified the flight plan for the enroute portion. When we changed the departure runway before takeoff apparently the FMS reverted back to part of the canned route. After loshn we were cleared to pmd. In the FMS the fixes were loshn; ave; pmd.while enroute; I began to visit with our jump seater; and just as we were getting to loshn I looked at the map; and noticed the turn to ave. I remember thinking that that looked like an 'odd' turn; but did not verify it against the release or pre departure clearance. Needless to say; we made the turn toward ave and was then contacted by ATC asking about our routing. He then re-cleared us to pmd. As I began to review what had happened; it became obvious that I had neglected to verify the proper routing after we made changes to the FMS on the ground; and never went with my gut feeling that the turn looked odd. The next controller gave us a phone number to call. I contacted lax center. I explained to them what had happened. He did mention that la center was having this problem occur quite often; and that it was not only on our airline that was making this mistake; but other companies also; and that they are trying to discover the root of the problem. He assured me that there was no loss of separation; and that our course deviation did not affect anyone else.
Original NASA ASRS Text
Title: A late change of runway in the FMC resulted in changing the cruise routing of the flight. This was at first not known to the crew. Center comments that this is a recurring event.
Narrative: Getting ready for our flight I got to the airplane and started planning. Because I was the PM on this leg; I was going to let the First Officer (FO) set up the FMS. I did in fact enter the 'canned' route and the flight number on the first page of the RTE page. I did not look any further; as we still did not have the PDC. I got out my Surface tablet and entered the filed route in the JEPP App. While I was doing that the FO came in and started loading the box. We received the PDC and I remember him commenting that the route was different. He began to fix the routing (canned route vs cleared route). Once we started taxiing out things got busy.We had planned on departing 28L. Just as we started to turn the corner to hold short; tower instructed us to cross 28L and hold short of 28R. As we crossed the left; the FO was making the changes in to box and loaded the proper runway and reloaded the departure procedure. I confirmed the change and we were given a takeoff clearance with traffic on an 8 mile final. Everything was going normally and we were given a couple of vectors for our climb; and eventually told to go direct to LOSHN intersection. We complied. This is where the problem came in. I had not verified the flight plan for the enroute portion. When we changed the departure runway before takeoff apparently the FMS reverted back to part of the canned route. After LOSHN we were cleared to PMD. In the FMS the fixes were LOSHN; AVE; PMD.While enroute; I began to visit with our jump seater; and just as we were getting to LOSHN I looked at the map; and noticed the turn to AVE. I remember thinking that that looked like an 'odd' turn; but did not verify it against the release or PDC. Needless to say; we made the turn toward AVE and was then contacted by ATC asking about our routing. He then re-cleared us to PMD. As I began to review what had happened; it became obvious that I had neglected to verify the proper routing after we made changes to the FMS on the ground; and never went with my gut feeling that the turn looked odd. The next controller gave us a phone number to call. I contacted LAX Center. I explained to them what had happened. He did mention that LA Center was having this problem occur quite often; and that it was not only on our airline that was making this mistake; but other companies also; and that they are trying to discover the root of the problem. He assured me that there was no loss of separation; and that our course deviation did not affect anyone else.
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.