A B757-200 crew reported an FMC route entry error leading to a track deviation after takeoff. The cr...

Attributes
ACN	879251
Time
Date	201003
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Flying
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 17500 Flight Crew Type 2200
Person 2
Function	Pilot Not Flying First Officer
Experience	Flight Crew Last 90 Days 200 Flight Crew Total 15000 Flight Crew Type 3000
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

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.

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of April 2012 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.

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.