Narrative:

Center called to say we had missed a crossing restriction at FL220 at ric VOR. We were maintaining FL240 as previously cleared. We believe center never issued, nor did we ever acknowledge a clearance to cross richmond at any other altitude other than FL240. Controller subsequently referred to us in another clearance as flight abc, when in fact we were flight xabc. Perhaps an earlier incorrect call was instrumental in the misunderstanding. It seems to be occurring more and more often, that ATC issues clrncs and in the pressure to handle other aircraft the controllers do not wait for readback from the one they had just issued a clearance too. Again, I suspect that this was the cause for this reported incident.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLT CREW OF ACR LGT IS ACCUSED OF MISSING THEIR CROSSING RESTRICTION AT FL220 WHEN THEY WERE PREVIOUSLY CLEARED TO CRUISE AT FL240. REPORTER SUSPECTS HEARBACK PROBLEM.

Narrative: CENTER CALLED TO SAY WE HAD MISSED A XING RESTRICTION AT FL220 AT RIC VOR. WE WERE MAINTAINING FL240 AS PREVIOUSLY CLRED. WE BELIEVE CENTER NEVER ISSUED, NOR DID WE EVER ACKNOWLEDGE A CLRNC TO CROSS RICHMOND AT ANY OTHER ALT OTHER THAN FL240. CTLR SUBSEQUENTLY REFERRED TO US IN ANOTHER CLRNC AS FLT ABC, WHEN IN FACT WE WERE FLT XABC. PERHAPS AN EARLIER INCORRECT CALL WAS INSTRUMENTAL IN THE MISUNDERSTANDING. IT SEEMS TO BE OCCURRING MORE AND MORE OFTEN, THAT ATC ISSUES CLRNCS AND IN THE PRESSURE TO HANDLE OTHER ACFT THE CTLRS DO NOT WAIT FOR READBACK FROM THE ONE THEY HAD JUST ISSUED A CLRNC TOO. AGAIN, I SUSPECT THAT THIS WAS THE CAUSE FOR THIS RPTED INCIDENT.

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.