Narrative:

Fll to pit using FMC navigation was asked to cross a point approximately (I lost my notes concerning the incident, otherwise I would give all the exact numbers) 25 mi southeast of elkins intersection at an altitude of FL240. The captain built the crossing restriction in the fix page correctly. When putting this descent point in the legs page, he was confused as to where to put it in respect to the waypoints prior to elkins intersection. After he put it in and while I was verifying its accuracy, center (ZDC, I believe) asked if we were going to be able to make the restriction. I said something like no. When I was looking at the legs page, I saw that the position he had put in the FMC had 180 degree out heading to what it should have been and the distance to the elkins VOR said 0. I was trying to bring this discrepancy up to someone who had acted as a flight instructor to me for 3 days. Actually, with the clearance and timing, we should have started down as it was given as we were quite close to the proper descent point when we received the clearance, even if he had put it in correctly. Supplemental information from acn 254195: this situation resulted from 3 crew errors: 1) my first priority was data entry rather than situational awareness. 2) I entered the crossing fix incorrectly into the legs page, and 3) my first officer did not detect my data entry error before I executed the command. Xchking data entry before execution is company policy and part of my cockpit briefing.

Related reports:

Google
 

Original NASA ASRS Text

Title: ERROR ADMITTED IN FLC DEV FROM CLRNC. ALT XING RESTRICTION NOT MADE. ROLE REVERSAL IN THAT PIC, THE PF, OPERATED THE CDU INPUTS. OPPOSED TO ACR PROC WHERE THE PNF DOES THAT WITH PF OPERATING THE MODE CTL PANEL, FLT GUIDANCE CTL PANEL FOR CHANGES.

Narrative: FLL TO PIT USING FMC NAV WAS ASKED TO CROSS A POINT APPROX (I LOST MY NOTES CONCERNING THE INCIDENT, OTHERWISE I WOULD GIVE ALL THE EXACT NUMBERS) 25 MI SE OF ELKINS INTXN AT AN ALT OF FL240. THE CAPT BUILT THE XING RESTRICTION IN THE FIX PAGE CORRECTLY. WHEN PUTTING THIS DSCNT POINT IN THE LEGS PAGE, HE WAS CONFUSED AS TO WHERE TO PUT IT IN RESPECT TO THE WAYPOINTS PRIOR TO ELKINS INTXN. AFTER HE PUT IT IN AND WHILE I WAS VERIFYING ITS ACCURACY, CTR (ZDC, I BELIEVE) ASKED IF WE WERE GOING TO BE ABLE TO MAKE THE RESTRICTION. I SAID SOMETHING LIKE NO. WHEN I WAS LOOKING AT THE LEGS PAGE, I SAW THAT THE POS HE HAD PUT IN THE FMC HAD 180 DEG OUT HDG TO WHAT IT SHOULD HAVE BEEN AND THE DISTANCE TO THE ELKINS VOR SAID 0. I WAS TRYING TO BRING THIS DISCREPANCY UP TO SOMEONE WHO HAD ACTED AS A FLT INSTRUCTOR TO ME FOR 3 DAYS. ACTUALLY, WITH THE CLRNC AND TIMING, WE SHOULD HAVE STARTED DOWN AS IT WAS GIVEN AS WE WERE QUITE CLOSE TO THE PROPER DSCNT POINT WHEN WE RECEIVED THE CLRNC, EVEN IF HE HAD PUT IT IN CORRECTLY. SUPPLEMENTAL INFO FROM ACN 254195: THIS SIT RESULTED FROM 3 CREW ERRORS: 1) MY FIRST PRIORITY WAS DATA ENTRY RATHER THAN SITUATIONAL AWARENESS. 2) I ENTERED THE XING FIX INCORRECTLY INTO THE LEGS PAGE, AND 3) MY FO DID NOT DETECT MY DATA ENTRY ERROR BEFORE I EXECUTED THE COMMAND. XCHKING DATA ENTRY BEFORE EXECUTION IS COMPANY POLICY AND PART OF MY COCKPIT BRIEFING.

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