Narrative:

Climbing out of dulles. Captain flying, I was working radios. Had clearance to 37000'. Passed ood. I was busy taking FMC fix for FMC overwater accuracy check. Asked by ATC what last clearance was. Replied, 'expedite climb through FL350.' noticed rbv had been entered in fix page of FMC with abeam line indicated. Captain remarked rbv was not in legs page. Captain told me to request direct ack as LNAV magenta line indicated that was next waypoint. Requested direct ack from ATC. They came back with, 'turn left to 360. Traffic at 1 O'clock, 6-7 mi. You may have violated adjacent airspace.' controller then gave us the phone number of quality assurance. Saw traffic at approximately 1-1:30 O'clock. Altitude difficult to determine as we were in a turn to 360 degrees. Cross checked legs page with cfp. Cfp read ood, J42, rbv, J62, ack. Legs and route pages at that time read direct ack. Corrected route page to read J62 ack. ATC then cleared us direct to rbv. Leveled at FL370 at about this time. I suspect that one of 2 things could possibly have caused this route excursion. First, the FMC could have dropped the rbv waypoint. When checking the route of flight from iad-cdg before activating/executing, the HSI display of dashed blue line ended at WPT02 (4OW). After activating/executing, the magenta line appeared for the entire route of flight. We wrote up this item in the log book as well as one other FMC squawk concerning the departure/arrival page. The crew on the next leg also wrote up 2 entirely different squawks on the FMC. The second possibility was that I loaded the FMC incorrectly, missing the rbv waypoint, and the captain did not catch it on his xchk. He did say that he recalls seeing J42 and J62 during his check.

Related reports:

Google
 

Original NASA ASRS Text

Title: WDB ADVANCED COCKPIT, PROGRAMMED IAD-CDG. ACFT FAILED TO FOLLOW CLEARED ROUTE ON CLIMB. REASON UNKNOWN.

Narrative: CLBING OUT OF DULLES. CAPT FLYING, I WAS WORKING RADIOS. HAD CLRNC TO 37000'. PASSED OOD. I WAS BUSY TAKING FMC FIX FOR FMC OVERWATER ACCURACY CHK. ASKED BY ATC WHAT LAST CLRNC WAS. REPLIED, 'EXPEDITE CLB THROUGH FL350.' NOTICED RBV HAD BEEN ENTERED IN FIX PAGE OF FMC WITH ABEAM LINE INDICATED. CAPT REMARKED RBV WAS NOT IN LEGS PAGE. CAPT TOLD ME TO REQUEST DIRECT ACK AS LNAV MAGENTA LINE INDICATED THAT WAS NEXT WAYPOINT. REQUESTED DIRECT ACK FROM ATC. THEY CAME BACK WITH, 'TURN LEFT TO 360. TFC AT 1 O'CLOCK, 6-7 MI. YOU MAY HAVE VIOLATED ADJACENT AIRSPACE.' CTLR THEN GAVE US THE PHONE NUMBER OF QUALITY ASSURANCE. SAW TFC AT APPROX 1-1:30 O'CLOCK. ALT DIFFICULT TO DETERMINE AS WE WERE IN A TURN TO 360 DEGS. CROSS CHKED LEGS PAGE WITH CFP. CFP READ OOD, J42, RBV, J62, ACK. LEGS AND ROUTE PAGES AT THAT TIME READ DIRECT ACK. CORRECTED ROUTE PAGE TO READ J62 ACK. ATC THEN CLRED US DIRECT TO RBV. LEVELED AT FL370 AT ABOUT THIS TIME. I SUSPECT THAT ONE OF 2 THINGS COULD POSSIBLY HAVE CAUSED THIS ROUTE EXCURSION. FIRST, THE FMC COULD HAVE DROPPED THE RBV WAYPOINT. WHEN CHKING THE ROUTE OF FLT FROM IAD-CDG BEFORE ACTIVATING/EXECUTING, THE HSI DISPLAY OF DASHED BLUE LINE ENDED AT WPT02 (4OW). AFTER ACTIVATING/EXECUTING, THE MAGENTA LINE APPEARED FOR THE ENTIRE ROUTE OF FLT. WE WROTE UP THIS ITEM IN THE LOG BOOK AS WELL AS ONE OTHER FMC SQUAWK CONCERNING THE DEP/ARR PAGE. THE CREW ON THE NEXT LEG ALSO WROTE UP 2 ENTIRELY DIFFERENT SQUAWKS ON THE FMC. THE SECOND POSSIBILITY WAS THAT I LOADED THE FMC INCORRECTLY, MISSING THE RBV WAYPOINT, AND THE CAPT DID NOT CATCH IT ON HIS XCHK. HE DID SAY THAT HE RECALLS SEEING J42 AND J62 DURING HIS CHK.

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