Narrative:

I was relieving the radar controller. Controller covered all required items including aircraft status. A B737 was on frequency with standard restriction to cross ZZZ at FL190. Briefing over; I sat down and observed the B737 crossing ZZZ level at FL230. At that moment; the B737 announced on frequency that they would not make the restriction at ZZZ; but that they would miss it by 3 or 4 miles. The controller I relieved had not yet left the area; and confirmed that the B737 had checked on with the crossing restriction. The pilot of the B737 then made several transmissions asking if that had been a problem; are we all set here; are you going to file paperwork because if you are then we will; and so on. They missed the restriction by several more than just 3 or 4 miles.I read the recent briefing sheet that stated that crossing restrictions were the shared responsibility of pilots and controllers; and I disagree. A crossing restriction is issued by the controller to ensure that; at some future time or place; the altitude of a specific aircraft will be known; so that other tasks; such as concentrating on other separation scenarios developing in the sector; can be accomplished. Many pilots now 'hang it up' so they can perform 'flight idle descents' to an assigned crossing restriction; so it is not unusual for an aircraft to appear high; to a controller; for a particular restriction. Short of questioning each aircraft that has been issued a restriction if they are planning on complying with a restriction (and this does not assure compliance either); I do not see how a controller could manage a moderately busy sector; and thus; my opinion remains unchanged that an acknowledged crossing restriction; for which the controller has assured a good readback; is the sole responsibility of the flight crew. I have no recommendation on how to prevent a re-occurrence of this event. Until there are consequences for the offending flight crews; restrictions will continue to be ignored; and the results may prove to be ugly and newsworthy.

Google
 

Original NASA ASRS Text

Title: ARTCC Controller reported an air carrier missed a crossing restriction; then discussed who was responsible.

Narrative: I was relieving the Radar Controller. Controller covered all required items including aircraft status. A B737 was on frequency with standard restriction to cross ZZZ at FL190. Briefing over; I sat down and observed the B737 crossing ZZZ level at FL230. At that moment; the B737 announced on frequency that they would not make the restriction at ZZZ; but that they would miss it by 3 or 4 miles. The Controller I relieved had not yet left the area; and confirmed that the B737 had checked on with the crossing restriction. The pilot of the B737 then made several transmissions asking if that had been a problem; are we all set here; are you going to file paperwork because if you are then we will; and so on. They missed the restriction by several more than just 3 or 4 miles.I read the recent briefing sheet that stated that crossing restrictions were the shared responsibility of pilots and controllers; and I disagree. A crossing restriction is issued by the controller to ensure that; at some future time or place; the altitude of a specific aircraft will be known; so that other tasks; such as concentrating on other separation scenarios developing in the sector; can be accomplished. Many pilots now 'hang it up' so they can perform 'flight idle descents' to an assigned crossing restriction; so it is not unusual for an aircraft to appear high; to a controller; for a particular restriction. Short of questioning each aircraft that has been issued a restriction if they are planning on complying with a restriction (and this does not assure compliance either); I do not see how a controller could manage a moderately busy sector; and thus; my opinion remains unchanged that an acknowledged crossing restriction; for which the controller has assured a good readback; is the sole responsibility of the flight crew. I have no recommendation on how to prevent a re-occurrence of this event. Until there are consequences for the offending flight crews; restrictions will continue to be ignored; and the results may prove to be ugly and newsworthy.

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