Narrative:

Initial clearance was heading FM. Arena for runway 35R. In the next 5 min we received several headings and altitude changes finally shooting an approach to runway 31R. My complaint is that the controller was so busy that we were unable to confirm the various clrncs. Without any clearance verification he switched us to another frequency for the approach to runway 31R. It was apparent that several other flts were having similar difficulties. The workload should not be so heavy that clrncs cannot be read back. Ord, atl, lga, sfo, lax do not seem to have these problems. Dfw routinely does. Why?

Google
 

Original NASA ASRS Text

Title: RPTR COMPLAINT OF RECEIVING TOO MANY AMENDED CLRNC HDG ALT CHANGE WITHOUT HAVING THE CHANCE FOR CLRNC ACKNOWLEDGED READBACK HEARBACK. FREQ CONGESTION.

Narrative: INITIAL CLRNC WAS HEADING FM. ARENA FOR RWY 35R. IN THE NEXT 5 MIN WE RECEIVED SEVERAL HDGS AND ALT CHANGES FINALLY SHOOTING AN APCH TO RWY 31R. MY COMPLAINT IS THAT THE CTLR WAS SO BUSY THAT WE WERE UNABLE TO CONFIRM THE VARIOUS CLRNCS. WITHOUT ANY CLRNC VERIFICATION HE SWITCHED US TO ANOTHER FREQ FOR THE APCH TO RWY 31R. IT WAS APPARENT THAT SEVERAL OTHER FLTS WERE HAVING SIMILAR DIFFICULTIES. THE WORKLOAD SHOULD NOT BE SO HVY THAT CLRNCS CANNOT BE READ BACK. ORD, ATL, LGA, SFO, LAX DO NOT SEEM TO HAVE THESE PROBS. DFW ROUTINELY DOES. WHY?

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.