Narrative:

At FL290, approximately 10 NM southwest of ekn, clearance was received to cross 30 NM southwest of mgw at FL240. PNF acknowledged clearance and PF entered restriction in FMC. (Flight was operating in VNAV and LNAV modes of autoplt.) after entry in FMC, PF noticed a 'bypass' annunciation in FMC routing in association with the entry of '30 southwest of mgw' fix. This was due to improper entry of this fix between mgw and 'roton' intersection. As opposed to where it really was, between ekn and 'tygar' intersection. PF was attempting to resolve this problem when it became apparent that initiation of descent was necessary to meet restriction. PF attempted to use vertical speed to initiate descent but aircraft remained at FL290. It was then noticed that altitude 'set' window was still at FL290, disallowing autoplt to descend. Altitude was reset to FL240, descent was initiated concurrent with inquiry from center as to ability to meet restriction. We responded 'unable' and flight was given a 50 degree right turn, presumably to avoid a potential conflict. At FL250, flight was cleared direct mgw to resume routing. This situation occurred because of PF's failure to follow his own SOP in such a circumstance which is to 1) reset altitude, 2) make a quick determination if aircraft is near the required descent point and initiate a descent using vertical speed or level change if necessary, 3) make appropriate entries in FMC and use VNAV for descent if appropriate. PF did these out of sequence and became distracted by an FMC irregularity, thus overshooting descent point.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN MLG ACR MISSED A XING ALT.

Narrative: AT FL290, APPROX 10 NM SW OF EKN, CLRNC WAS RECEIVED TO CROSS 30 NM SW OF MGW AT FL240. PNF ACKNOWLEDGED CLRNC AND PF ENTERED RESTRICTION IN FMC. (FLT WAS OPERATING IN VNAV AND LNAV MODES OF AUTOPLT.) AFTER ENTRY IN FMC, PF NOTICED A 'BYPASS' ANNUNCIATION IN FMC ROUTING IN ASSOCIATION WITH THE ENTRY OF '30 SW OF MGW' FIX. THIS WAS DUE TO IMPROPER ENTRY OF THIS FIX BTWN MGW AND 'ROTON' INTXN. AS OPPOSED TO WHERE IT REALLY WAS, BTWN EKN AND 'TYGAR' INTXN. PF WAS ATTEMPTING TO RESOLVE THIS PROBLEM WHEN IT BECAME APPARENT THAT INITIATION OF DSCNT WAS NECESSARY TO MEET RESTRICTION. PF ATTEMPTED TO USE VERT SPD TO INITIATE DSCNT BUT ACFT REMAINED AT FL290. IT WAS THEN NOTICED THAT ALT 'SET' WINDOW WAS STILL AT FL290, DISALLOWING AUTOPLT TO DSND. ALT WAS RESET TO FL240, DSCNT WAS INITIATED CONCURRENT WITH INQUIRY FROM CTR AS TO ABILITY TO MEET RESTRICTION. WE RESPONDED 'UNABLE' AND FLT WAS GIVEN A 50 DEG R TURN, PRESUMABLY TO AVOID A POTENTIAL CONFLICT. AT FL250, FLT WAS CLRED DIRECT MGW TO RESUME ROUTING. THIS SITUATION OCCURRED BECAUSE OF PF'S FAILURE TO FOLLOW HIS OWN SOP IN SUCH A CIRCUMSTANCE WHICH IS TO 1) RESET ALT, 2) MAKE A QUICK DETERMINATION IF ACFT IS NEAR THE REQUIRED DSCNT POINT AND INITIATE A DSCNT USING VERT SPD OR LEVEL CHANGE IF NECESSARY, 3) MAKE APPROPRIATE ENTRIES IN FMC AND USE VNAV FOR DSCNT IF APPROPRIATE. PF DID THESE OUT OF SEQUENCE AND BECAME DISTRACTED BY AN FMC IRREGULARITY, THUS OVERSHOOTING DSCNT POINT.

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.