Narrative:

On 7/sat/91, I was the captain on flight atl-roa. We were cruising at FL230 when atl center handed us off from 134.55 to 132.9. The new controller then gave us a crossing restriction of 35 NM southwest of roa at and maintain 1000 ft. I initiated an immediate descent at 3000-4000 FPM but still could not make the crossing restriction since we started the descent at 49 NM southwest of roa. It appears that 134.55 is supposed to start the descent before the handoff to 132.9, but they either forgot or let the next controller start the descent. In any event, the result is an uncomfortable descent rate that is totally unnecessary and still cannot be accomplished. This situation has been going on for over a yr and has happened to me personally 5 times. This is my second NASA report on the same problem.

Google
 

Original NASA ASRS Text

Title: ARC LTT ALTDEV UNDERSHOT XING RESTRICTION NOT MET DUE TO LATE CLRNC FROM ARTCC. RPTR CLAIMS THIS IS A RECURRENT EVENT IN THIS AREA.

Narrative: ON 7/SAT/91, I WAS THE CAPT ON FLT ATL-ROA. WE WERE CRUISING AT FL230 WHEN ATL CENTER HANDED US OFF FROM 134.55 TO 132.9. THE NEW CTLR THEN GAVE US A XING RESTRICTION OF 35 NM SW OF ROA AT AND MAINTAIN 1000 FT. I INITIATED AN IMMEDIATE DSCNT AT 3000-4000 FPM BUT STILL COULD NOT MAKE THE XING RESTRICTION SINCE WE STARTED THE DSCNT AT 49 NM SW OF ROA. IT APPEARS THAT 134.55 IS SUPPOSED TO START THE DSCNT BEFORE THE HDOF TO 132.9, BUT THEY EITHER FORGOT OR LET THE NEXT CTLR START THE DSCNT. IN ANY EVENT, THE RESULT IS AN UNCOMFORTABLE DSCNT RATE THAT IS TOTALLY UNNECESSARY AND STILL CANNOT BE ACCOMPLISHED. THIS SITUATION HAS BEEN GOING ON FOR OVER A YR AND HAS HAPPENED TO ME PERSONALLY 5 TIMES. THIS IS MY SECOND NASA RPT ON THE SAME PROBLEM.

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.