Narrative:

Departed phx to jfk and was talking to ZAB. I was the PF. The aircraft speed was 280 KTS (had it back for turbulence). Center called us and gave us instructions to turn to a heading of 160 degrees. We complied and then he asked what our speed was. The first officer replied that we were at 280 KTS. He then said we were instructed to maintain 250 KTS. Neither one of us remember hearing this speed restr at any time. We do not know at this time whether he actually did give us the speed restr and we did not hear it or he just thought he gave us the restr. The problem here is controller 'say back.' if a controller gives us a speed restr and we don't acknowledge it, he is not required to question whether we actually heard it or not. I feel this practice is not conducive to safety. There could have been an near midair collision because we were not at the speed he thought we were at. I always read back the instructions as procedure dictates. I know it takes extra time for a controller to acknowledge my readback and frequencys are becoming so congested with the increasing traffic, that this new procedure is a way of cutting down on the amount of time it takes per transmission, but this is a band-aid for the real problem. Callback conversation with reporter revealed the following information: reporter advised the flight crew discussed this situation in detail and neither could remember ATC assigning a speed restr any way along the route prior to being challenged by ZAB. The reporter advised he understood the importance for clearance readback, and was advised by analyst ATC's requirement to confirm and correct pilot readbacks as necessary.

Google
 

Original NASA ASRS Text

Title: ZAB CHALLENGES A320 FLC'S ENRTE SPD.

Narrative: DEPARTED PHX TO JFK AND WAS TALKING TO ZAB. I WAS THE PF. THE ACFT SPD WAS 280 KTS (HAD IT BACK FOR TURB). CTR CALLED US AND GAVE US INSTRUCTIONS TO TURN TO A HDG OF 160 DEGS. WE COMPLIED AND THEN HE ASKED WHAT OUR SPD WAS. THE FO REPLIED THAT WE WERE AT 280 KTS. HE THEN SAID WE WERE INSTRUCTED TO MAINTAIN 250 KTS. NEITHER ONE OF US REMEMBER HEARING THIS SPD RESTR AT ANY TIME. WE DO NOT KNOW AT THIS TIME WHETHER HE ACTUALLY DID GIVE US THE SPD RESTR AND WE DID NOT HEAR IT OR HE JUST THOUGHT HE GAVE US THE RESTR. THE PROB HERE IS CTLR 'SAY BACK.' IF A CTLR GIVES US A SPD RESTR AND WE DON'T ACKNOWLEDGE IT, HE IS NOT REQUIRED TO QUESTION WHETHER WE ACTUALLY HEARD IT OR NOT. I FEEL THIS PRACTICE IS NOT CONDUCIVE TO SAFETY. THERE COULD HAVE BEEN AN NMAC BECAUSE WE WERE NOT AT THE SPD HE THOUGHT WE WERE AT. I ALWAYS READ BACK THE INSTRUCTIONS AS PROC DICTATES. I KNOW IT TAKES EXTRA TIME FOR A CTLR TO ACKNOWLEDGE MY READBACK AND FREQS ARE BECOMING SO CONGESTED WITH THE INCREASING TFC, THAT THIS NEW PROC IS A WAY OF CUTTING DOWN ON THE AMOUNT OF TIME IT TAKES PER XMISSION, BUT THIS IS A BAND-AID FOR THE REAL PROB. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ADVISED THE FLC DISCUSSED THIS SIT IN DETAIL AND NEITHER COULD REMEMBER ATC ASSIGNING A SPD RESTR ANY WAY ALONG THE RTE PRIOR TO BEING CHALLENGED BY ZAB. THE RPTR ADVISED HE UNDERSTOOD THE IMPORTANCE FOR CLRNC READBACK, AND WAS ADVISED BY ANALYST ATC'S REQUIREMENT TO CONFIRM AND CORRECT PLT READBACKS AS NECESSARY.

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.