Narrative:

What happened: we had clearance to cross ric at FL230. We crossed at FL245 (nottingham 3 arrival to bwi). How was problem discovered: controller gave a further descent clearance near the VOR, then said the previous restrictions still applies. Now it was too late. What actions were taken: none, except to try to increase rate of descent. What factors contributed: 1) had not flown in almost 2 months. 2) first officer and jumpseat rider did not notice or mention fact that we were not going to make restriction. 3) autoflt system and FMC -- used capture prompt in an attempt to be smooth 5 mi from actual top of descent point. Autoflt system did not capture the path descent as it should have. Do not know why (probably programming error) yet I am very knowledgeable about FMC. 4) ATC did not query our slow descent. Why did situation occur: 1) PIC failed to observe, verify, and use manual backup confirmation of required flight path angle. 2) lack of recent experience. 3) crew did not work together as we should have even though a 'team concept' briefing was used prior to flight (communication breakdown). Suggestions: 1) more emphasis on crew concept (back me up). 2) more flying to stay current. 3) verify, verify, verify. ATC could help by giving a lower expected clearance earlier this would allow the pilots to have better situational awareness. Try to include a note on the STAR if this is a usual traffic control factor.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR MISSES XING RESTRICTION ON DSCNT.

Narrative: WHAT HAPPENED: WE HAD CLRNC TO CROSS RIC AT FL230. WE CROSSED AT FL245 (NOTTINGHAM 3 ARR TO BWI). HOW WAS PROB DISCOVERED: CTLR GAVE A FURTHER DSCNT CLRNC NEAR THE VOR, THEN SAID THE PREVIOUS RESTRICTIONS STILL APPLIES. NOW IT WAS TOO LATE. WHAT ACTIONS WERE TAKEN: NONE, EXCEPT TO TRY TO INCREASE RATE OF DSCNT. WHAT FACTORS CONTRIBUTED: 1) HAD NOT FLOWN IN ALMOST 2 MONTHS. 2) FO AND JUMPSEAT RIDER DID NOT NOTICE OR MENTION FACT THAT WE WERE NOT GOING TO MAKE RESTRICTION. 3) AUTOFLT SYS AND FMC -- USED CAPTURE PROMPT IN AN ATTEMPT TO BE SMOOTH 5 MI FROM ACTUAL TOP OF DSCNT POINT. AUTOFLT SYS DID NOT CAPTURE THE PATH DSCNT AS IT SHOULD HAVE. DO NOT KNOW WHY (PROBABLY PROGRAMMING ERROR) YET I AM VERY KNOWLEDGEABLE ABOUT FMC. 4) ATC DID NOT QUERY OUR SLOW DSCNT. WHY DID SIT OCCUR: 1) PIC FAILED TO OBSERVE, VERIFY, AND USE MANUAL BACKUP CONFIRMATION OF REQUIRED FLT PATH ANGLE. 2) LACK OF RECENT EXPERIENCE. 3) CREW DID NOT WORK TOGETHER AS WE SHOULD HAVE EVEN THOUGH A 'TEAM CONCEPT' BRIEFING WAS USED PRIOR TO FLT (COM BREAKDOWN). SUGGESTIONS: 1) MORE EMPHASIS ON CREW CONCEPT (BACK ME UP). 2) MORE FLYING TO STAY CURRENT. 3) VERIFY, VERIFY, VERIFY. ATC COULD HELP BY GIVING A LOWER EXPECTED CLRNC EARLIER THIS WOULD ALLOW THE PLTS TO HAVE BETTER SITUATIONAL AWARENESS. TRY TO INCLUDE A NOTE ON THE STAR IF THIS IS A USUAL TFC CTL FACTOR.

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.