Narrative:

I was captain on aircraft X from dtw to lga on sep/xa/99. We were flying the milton 3 arrival at 12000 ft and had been assigned to cross beuty as published at 10000 ft. We had entered this crossing and all others prior to top of descent. The descent had been normal with the autoplt on and being operated in VNAV and LNAV. We leveled at 12000 ft to cross vibes as published and reset the cruise altitude to 12000 ft to get a new top of descent point for the crossing restr at beuty. I verified that we were in VNAV and LNAV and monitored the instruments for the arrival. The aircraft started a descent at the top of descent point. We had descended about 500 ft when the aircraft came out of VNAV for no known reason. I selected VNAV again and my descent page showed that we were on profile and my altitude range arc agreed. I had selected a larger than normal scale on the HSI to see the remainder of the arrival. I felt that the aircraft would have a tough time making the remainder of the descent in the distance remaining and selected flight level change to 10000 ft. While I was selecting speed brakes to increase the descent rate, I checked the first officer's progress page and it did show we were high for the crossing at beuty. I crossed the beuty intersection approximately 500 ft high and there were no conflicts. I have flown the B757 for many yrs and have seen many glitches but I have not experienced this one before. I do know that the B757 cuts all crossing restrs very close and you have very little time to correct any problems once they occur. In the future, I will rely on a smaller scale for a better feeling of the distance remaining to the next fix. I will also make a practice of using the information on the first officer's progress page to back up the information on my descent page and HSI. I feel that if I had caught this just a little earlier I would have made the restr.

Google
 

Original NASA ASRS Text

Title: B757 CREW MISSES XING RESTR.

Narrative: I WAS CAPT ON ACFT X FROM DTW TO LGA ON SEP/XA/99. WE WERE FLYING THE MILTON 3 ARR AT 12000 FT AND HAD BEEN ASSIGNED TO CROSS BEUTY AS PUBLISHED AT 10000 FT. WE HAD ENTERED THIS XING AND ALL OTHERS PRIOR TO TOP OF DSCNT. THE DSCNT HAD BEEN NORMAL WITH THE AUTOPLT ON AND BEING OPERATED IN VNAV AND LNAV. WE LEVELED AT 12000 FT TO CROSS VIBES AS PUBLISHED AND RESET THE CRUISE ALT TO 12000 FT TO GET A NEW TOP OF DSCNT POINT FOR THE XING RESTR AT BEUTY. I VERIFIED THAT WE WERE IN VNAV AND LNAV AND MONITORED THE INSTS FOR THE ARR. THE ACFT STARTED A DSCNT AT THE TOP OF DSCNT POINT. WE HAD DSNDED ABOUT 500 FT WHEN THE ACFT CAME OUT OF VNAV FOR NO KNOWN REASON. I SELECTED VNAV AGAIN AND MY DSCNT PAGE SHOWED THAT WE WERE ON PROFILE AND MY ALT RANGE ARC AGREED. I HAD SELECTED A LARGER THAN NORMAL SCALE ON THE HSI TO SEE THE REMAINDER OF THE ARR. I FELT THAT THE ACFT WOULD HAVE A TOUGH TIME MAKING THE REMAINDER OF THE DSCNT IN THE DISTANCE REMAINING AND SELECTED FLT LEVEL CHANGE TO 10000 FT. WHILE I WAS SELECTING SPD BRAKES TO INCREASE THE DSCNT RATE, I CHKED THE FO'S PROGRESS PAGE AND IT DID SHOW WE WERE HIGH FOR THE XING AT BEUTY. I CROSSED THE BEUTY INTXN APPROX 500 FT HIGH AND THERE WERE NO CONFLICTS. I HAVE FLOWN THE B757 FOR MANY YRS AND HAVE SEEN MANY GLITCHES BUT I HAVE NOT EXPERIENCED THIS ONE BEFORE. I DO KNOW THAT THE B757 CUTS ALL XING RESTRS VERY CLOSE AND YOU HAVE VERY LITTLE TIME TO CORRECT ANY PROBS ONCE THEY OCCUR. IN THE FUTURE, I WILL RELY ON A SMALLER SCALE FOR A BETTER FEELING OF THE DISTANCE REMAINING TO THE NEXT FIX. I WILL ALSO MAKE A PRACTICE OF USING THE INFO ON THE FO'S PROGRESS PAGE TO BACK UP THE INFO ON MY DSCNT PAGE AND HSI. I FEEL THAT IF I HAD CAUGHT THIS JUST A LITTLE EARLIER I WOULD HAVE MADE THE RESTR.

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.