Narrative:

Told to cross groat at 17;000 ft. Short of groat got the dreaded call; 'are you going to make it?' had set the altitude in the FMC as a restriction; but didn't dial down the MCP altitude knob; so top of descent came and went unnoticed. ATC gave us relief 'ok; just descend to 17;000 ft.' we hurried down; making the crossing at 17;700 ft instead of 17;000 ft. It's easy to get distracted programming the FMC and to forget to put the new altitude restriction in the MCP window. I don't have an easy answer. Part of it is our weird half automated/half not automated operating procedures. I'll start always selecting the MCP window first.

Google
 

Original NASA ASRS Text

Title: Cleared to cross an intersection at 17000 FT MSL; flight crew of B737NG failed to set altitude in MCP altitude window and thus did not begin descent in a timely fashion. Reporter cites inconsistent VNAV SOP and lack of familiarity with programming the FMC.

Narrative: Told to cross GROAT at 17;000 FT. Short of GROAT got the dreaded call; 'Are you going to make it?' Had set the altitude in the FMC as a restriction; but didn't dial down the MCP altitude knob; so Top of Descent came and went unnoticed. ATC gave us relief 'OK; just descend to 17;000 FT.' We hurried down; making the crossing at 17;700 FT instead of 17;000 FT. It's easy to get distracted programming the FMC and to forget to put the new altitude restriction in the MCP window. I don't have an easy answer. Part of it is our weird half automated/half not automated operating procedures. I'll start always selecting the MCP window first.

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.