Air carrier pilot reports FMC anomalies departing iad caused a track deviation and an altitude overs...

Narrative:

During preflight first officer entered data into FMC and verified route; distance and fuel at destination. Captain checked route and the rest of ground operation was normal. Blues was first fix. Initial heading assigned was 230. After hand off to departure we were cleared to climb to 13;000 and direct blues. First officer line selected blues from 2L to 1L. Dashed line was a right turn and he confirmed and executed. At this time he set 13;000 in MCP and performed after takeoff check. We the inadvertently turned to heading 335 following magenta line. Now climbing through 10;000 feet approach asked us our heading. We replied 335 and he directed us to turn left to 230 and confirm blues intersection first officer checked FMC and blues was at 1L; but distance was 6034 NM and insufficient fuel was displayed on FMC. First officer reentered blues and it now showed 12 NM. During the turn to 230 the captain climbed to 13;220 ft. Level at 13;000 ft we were given multiple vectors and finally told to proceed to ramay. We verified ramay and proceeded direct. First officer verified entire route to the destination. A few minutes later an insufficient fuel prompt came on again. First officer found that iad was now on the rt. Pg 1 as destination. First officer changed destination and again checked the route. All fixes were correct. Upon reaching FL340; first officer noticed only 3 leg pages and checked the route. He found the entire arrival into ZZZ was gone. First officer again entered arrival and checked all waypoints. Suspect navigation database or FMC problem. Crew verified all fixes with raw data to their destination. Remainder of flight was uneventful. To note; route; distance and fuel were confirmed on ground and during 40 minutes of ground operations FMC appeared normal and 'no insufficient fuel' ever came on. Only after airborne with blues selected to 1L did it come on.

Original NASA ASRS Text

Title: Air carrier pilot reports FMC anomalies departing IAD caused a track deviation and an altitude overshoot. After reloading the route the arrival dropped out. After reloading the arrival the FMC functions as designed for the remainder of the flight.

Narrative: During preflight First Officer entered data into FMC and verified route; distance and fuel at destination. Captain checked route and the rest of ground operation was normal. BLUES was first fix. Initial heading assigned was 230. After hand off to departure we were cleared to climb to 13;000 and direct BLUES. First Officer line selected BLUES from 2L to 1L. Dashed line was a right turn and he confirmed and executed. At this time he set 13;000 in MCP and performed after takeoff check. We the inadvertently turned to heading 335 following magenta line. Now climbing through 10;000 feet approach asked us our heading. We replied 335 and he directed us to turn left to 230 and confirm BLUES intersection First Officer checked FMC and BLUES was at 1L; but distance was 6034 NM and insufficient fuel was displayed on FMC. First Officer reentered BLUES and it now showed 12 NM. During the turn to 230 the Captain climbed to 13;220 FT. Level at 13;000 FT we were given multiple vectors and finally told to proceed to RAMAY. We verified RAMAY and proceeded direct. First Officer verified entire route to the destination. A few minutes later an insufficient fuel prompt came on again. First Officer found that IAD was now on the Rt. pg 1 as destination. First Officer changed destination and again checked the route. All fixes were correct. Upon reaching FL340; First Officer noticed only 3 leg pages and checked the route. He found the entire arrival into ZZZ was gone. First Officer again entered arrival and checked all waypoints. Suspect navigation database or FMC problem. Crew verified all fixes with raw data to their destination. Remainder of flight was uneventful. To note; route; distance and fuel were confirmed on ground and during 40 minutes of ground operations FMC appeared normal and 'No Insufficient Fuel' ever came on. Only after airborne with BLUES selected to 1L did it come on.

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.

Attributes
ACN	849536
Time
Date	200908
Local Time Of Day	0601-1200
Place
Locale Reference	IAD.Airport
State Reference	DC
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Direct
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Not Flying
Experience	Flight Crew Last 90 Days 200 Flight Crew Total 10000 Flight Crew Type 1700
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Track / Heading All Types

Air carrier pilot reports FMC anomalies departing iad caused a track deviation and an altitude overshoot. After reloading the route the arrival dropped out. After reloading the arrival the FMC functions as designed for the remainder of the flight.