Narrative:

We were given a crossing restriction from center to cross 10 east of ATR at FL180. We programmed that and the PF started an early descent for the restriction due to turbulence. We were below the descent path descending at 1;000 FPM. The controller then amended the clearance and told us to maintain our current descent rate and to descend to 16;000 feet. The PF put in 16;000 feet in the altitude window and hit altitude intervention. I queried the controller if 1;000 FPM would be okay with them and the controller replied yes.after we crossed over ATR; the controller asked us why we had not made the previous restriction and I replied they had given us a new altitude of 16;000 feet therefore canceling out the previous restriction. Controller explained to me that was the reason for instructing to maintain our current rate of descent to 16;000 feet. I then explained that we had started down early and were below the computed descent flight path and that was the reason I had queried if 1;000 FPM would be okay.controller then said that they had really needed the previous 18;000 restriction; but luckily we were near no other aircraft at the time. I then calmly and professionally (the controller was also by the way); explained that if they really needed the restriction that it would have been better to just tell us to 'cross 10 east of ATR at or below FL180 and then descend to and maintain 16;000 feet.' the controller then said not to worry about the event and said nothing would come of it. A different controller later handed us off to the next sector.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737-700 Captain reported failing to meet a crossing restriction after misunderstanding an ATC clearance.

Narrative: We were given a crossing restriction from Center to cross 10 east of ATR at FL180. We programmed that and the PF started an early descent for the restriction due to turbulence. We were below the descent path descending at 1;000 FPM. The Controller then amended the clearance and told us to maintain our current descent rate and to descend to 16;000 feet. The PF put in 16;000 feet in the altitude window and hit altitude intervention. I queried the Controller if 1;000 FPM would be okay with them and the Controller replied yes.After we crossed over ATR; the Controller asked us why we had not made the previous restriction and I replied they had given us a new altitude of 16;000 feet therefore canceling out the previous restriction. Controller explained to me that was the reason for instructing to maintain our current rate of descent to 16;000 feet. I then explained that we had started down early and were below the computed descent flight path and that was the reason I had queried if 1;000 FPM would be okay.Controller then said that they had really needed the previous 18;000 restriction; but luckily we were near no other aircraft at the time. I then calmly and professionally (the Controller was also by the way); explained that if they really needed the restriction that it would have been better to just tell us to 'cross 10 east of ATR at or below FL180 and then descend to and maintain 16;000 feet.' The Controller then said not to worry about the event and said nothing would come of it. A different Controller later handed us off to the next sector.

Data retrieved from NASA's ASRS site 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.