Narrative:

Our flight was on the shine 5 arrival to charlotte, nc. We were cleared direct to flabb intersection. We were at FL330 and ZTL cleared us to cross flabb at FL290. The captain then set FL290 in the FMC and on the flight mode panel. The captain then proceeded to locate and brief the approach to charlotte. About 4 NM from flabb, atlanta called us and asked us why we were still at FL330. At that point we expedited our descent in an attempt to make our crossing restr. Over flabb intersection we were at approximately FL305 while continuing our descent to FL290. We reached our assigned altitude 3-4 NM beyond flabb. It then occurred to us what went wrong. The altitude was set correctly in the FMC and on the fmp, but we did not verify that the altitude capture setting was armed. Further a 90 KT tailwind exacerbated the situation. Another possible contributing factor was the lack of flight crew rest on the preceding overnight. I estimate our total sleep to have been about 6 1/2 hours that night. Supplemental information from acn 326870: we received a crossing restr clearance while discussing what type of approach we would likely get in clt. I set up the crossing restr in the FMC, dialed in the new altitude (FL190) in the altitude alerter, but didn't pull the altitude set knob to arm the descent mode. Company altitude awareness procedures call for both pilots to point to the altitude alerter setting and to the new altitude as it appears (if the set knob is pulled) on the primary flight display. Apparently we missed verifying the new altitude was indicating on the pfd.

Google
 

Original NASA ASRS Text

Title: AN FK10 FLC FAILED TO BEGIN THE DSCNT FOR A XING RESTR WHILE ON A STAR. THE FMC AND THE FLT MODE PANEL WERE SET, BUT THE ALT CAPTURE SETTING WAS NOT ARMED AND HAD NOT BEEN VERIFIED ON THE PRIMARY FLT DISPLAY. ALT XING RESTR NOT MET.

Narrative: OUR FLT WAS ON THE SHINE 5 ARR TO CHARLOTTE, NC. WE WERE CLRED DIRECT TO FLABB INTXN. WE WERE AT FL330 AND ZTL CLRED US TO CROSS FLABB AT FL290. THE CAPT THEN SET FL290 IN THE FMC AND ON THE FLT MODE PANEL. THE CAPT THEN PROCEEDED TO LOCATE AND BRIEF THE APCH TO CHARLOTTE. ABOUT 4 NM FROM FLABB, ATLANTA CALLED US AND ASKED US WHY WE WERE STILL AT FL330. AT THAT POINT WE EXPEDITED OUR DSCNT IN AN ATTEMPT TO MAKE OUR XING RESTR. OVER FLABB INTXN WE WERE AT APPROX FL305 WHILE CONTINUING OUR DSCNT TO FL290. WE REACHED OUR ASSIGNED ALT 3-4 NM BEYOND FLABB. IT THEN OCCURRED TO US WHAT WENT WRONG. THE ALT WAS SET CORRECTLY IN THE FMC AND ON THE FMP, BUT WE DID NOT VERIFY THAT THE ALT CAPTURE SETTING WAS ARMED. FURTHER A 90 KT TAILWIND EXACERBATED THE SIT. ANOTHER POSSIBLE CONTRIBUTING FACTOR WAS THE LACK OF FLC REST ON THE PRECEDING OVERNIGHT. I ESTIMATE OUR TOTAL SLEEP TO HAVE BEEN ABOUT 6 1/2 HRS THAT NIGHT. SUPPLEMENTAL INFO FROM ACN 326870: WE RECEIVED A XING RESTR CLRNC WHILE DISCUSSING WHAT TYPE OF APCH WE WOULD LIKELY GET IN CLT. I SET UP THE XING RESTR IN THE FMC, DIALED IN THE NEW ALT (FL190) IN THE ALT ALERTER, BUT DIDN'T PULL THE ALT SET KNOB TO ARM THE DSCNT MODE. COMPANY ALT AWARENESS PROCS CALL FOR BOTH PLTS TO POINT TO THE ALT ALERTER SETTING AND TO THE NEW ALT AS IT APPEARS (IF THE SET KNOB IS PULLED) ON THE PRIMARY FLT DISPLAY. APPARENTLY WE MISSED VERIFYING THE NEW ALT WAS INDICATING ON THE PFD.

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.