A B757-200 crew reported an FMC route entry error leading to a track deviation after takeoff. The crew was late to the airport; rushed and the Captain reported fatigue. The incorrect intersection name in the FMC had two different locations.

Date: 2010-03 · Aircraft: B757-200 · Phase: climb

Anomalies: aircraft-equipment-problem-less-severe|deviation-track-heading-all-types|deviation-discrepancy-procedural-published-material-policy

Synopsis

A B757-200 crew reported an FMC route entry error leading to a track deviation after takeoff. The crew was late to the airport; rushed and the Captain reported fatigue. The incorrect intersection name in the FMC had two different locations.

Narrative

I programmed the FMC with the route and failed to notice that I had put in the incorrect intersection; same name but different location. The FMC did not give an indication for insufficient fuel for the route even though the intersection programmed increased route distance beyond fuel capabilities. The remainder of the route was programmed correctly. We were given a 270 heading on initial climb to 3;000 FT. Departure cleared us the first intersection and we turned to the wrong heading to go direct to it. ATC then cleared us back to heading to 270 and then to next intersection without comment. I did not sleep well the previous night. I had eaten breakfast and worked out at the gym. Transportation to the airport was delayed and TSA was slow to clear me into the airport. I was late to flight operations and Management interrupted my flight planning with a call asking where I was. I had a long walk to the gate and I found when I arrived at the airplane the First Officer had not picked up the slack with the FMC and I rushed through the FMC programming. The First Officer failed to notice the programming error.

Second reporter narrative

The van was late. They wanted the flight out ASAP. We both felt rushed. It was also the end of a 3 day trip with 2 days of very early shows. On climb out we were being vectored then given direct an intersection and then a frequency change. The magenta line went way off to the right. Started the turn right then we both thought it didn't look right. Requested direct the next intersection on the new frequency then had a vector given to the left. We put the first intersection into the fix page and found we turned the wrong way. Turns out it was the correct name but wrong intersection entered in the route.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.