Narrative:

During WX avoidance in bos area, received frequency change. Short time after checking in on new frequency, WX avoidance complete, asked for instructions direct next fix or a heading. No response. Frequency very busy. Turned onto original flight plan track to next waypoint. Controller then asked if we were on 180 degree heading as instructed on initial contact. Replied that we did not hear or acknowledged any heading on initial contact. (I believe that heading would have also turned us into WX we were avoiding.) problem arose during very busy on the new frequency and I don't think controller was listening closely to readbacks from aircraft. I find this occurring more frequently, especially with handoff to next controller. The frequency given by controller is read back incorrectly and not challenged.

Google
 

Original NASA ASRS Text

Title: FLC OF A CANADAIR REGIONAL JET, CL65, DID NOT HEAR A HDG GIVEN BY CTLR AFTER REQUESTING ONE FOR A DIRECT COURSE DUE TO FREQ CONGESTION.

Narrative: DURING WX AVOIDANCE IN BOS AREA, RECEIVED FREQ CHANGE. SHORT TIME AFTER CHKING IN ON NEW FREQ, WX AVOIDANCE COMPLETE, ASKED FOR INSTRUCTIONS DIRECT NEXT FIX OR A HDG. NO RESPONSE. FREQ VERY BUSY. TURNED ONTO ORIGINAL FLT PLAN TRACK TO NEXT WAYPOINT. CTLR THEN ASKED IF WE WERE ON 180 DEG HDG AS INSTRUCTED ON INITIAL CONTACT. REPLIED THAT WE DID NOT HEAR OR ACKNOWLEDGED ANY HDG ON INITIAL CONTACT. (I BELIEVE THAT HDG WOULD HAVE ALSO TURNED US INTO WX WE WERE AVOIDING.) PROB AROSE DURING VERY BUSY ON THE NEW FREQ AND I DON'T THINK CTLR WAS LISTENING CLOSELY TO READBACKS FROM ACFT. I FIND THIS OCCURRING MORE FREQUENTLY, ESPECIALLY WITH HDOF TO NEXT CTLR. THE FREQ GIVEN BY CTLR IS READ BACK INCORRECTLY AND NOT CHALLENGED.

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.