Narrative:

Our aircraft was cleared to takeoff from ord, followed by a right turn to a 010 degree heading after departure. We complied with the clearance. Tower then instructed us, 'on a heading of 010 degrees contact departure on 125.00.' the tower controller had restated a heading that we had already received in the takeoff clearance. I had been anticipating a turn to the right. So I believed that I had heard tower controller issue us a turn to a 040 degree heading and contact departure. I acknowledged the tower's instruction without a readback. I then contacted the departure controller and told him that we were climbing out of 2200 ft for 5000 ft and in a right turn to 040 degree heading. The departure controller acknowledged with 'radar contact, climb and maintain 6000 ft.' the departure controller did not catch our heading change readback to 040 degrees because he did not issue the heading change and didn't expect it. Later in the climb out departure asked us our heading today. I replied with 'they assigned us 040 degrees,' which I believed they had. Departure then instructed us to turn to 070 degrees. The problem arose when tower restated a heading that we had already been issued. I anticipated a right turn, and I read back the believed heading change to the departure controller, who was not expecting it. In the future ATC instruction should be read back to the issuing controller and not to the next assigned controller. Supplemental information from acn 331706: we were anticipating fairly rapid turns to the east as is typical leaving O'hare heading towards elx. Somehow we had 040 degrees in our head. How could it possibly happen? An ATR cleared for takeoff on runway 32R just prior to us was given an immediate right to 040 degrees, and when ord tower gave us the handoff to departure on 125.0 and restated the heading of 010 degrees (we were already well established on 010 degrees) this could have triggered us believing we were instructed to turn to 040 degrees. Tower restating a previously issued heading I feel is a little unusual.

Google
 

Original NASA ASRS Text

Title: FK10 FLC TURNS TO WRONG HDG AFTER DEP WHEN INCORRECTLY HEARING CLRNC.

Narrative: OUR ACFT WAS CLRED TO TKOF FROM ORD, FOLLOWED BY A R TURN TO A 010 DEG HDG AFTER DEP. WE COMPLIED WITH THE CLRNC. TWR THEN INSTRUCTED US, 'ON A HDG OF 010 DEGS CONTACT DEP ON 125.00.' THE TWR CTLR HAD RESTATED A HDG THAT WE HAD ALREADY RECEIVED IN THE TKOF CLRNC. I HAD BEEN ANTICIPATING A TURN TO THE R. SO I BELIEVED THAT I HAD HEARD TWR CTLR ISSUE US A TURN TO A 040 DEG HDG AND CONTACT DEP. I ACKNOWLEDGED THE TWR'S INSTRUCTION WITHOUT A READBACK. I THEN CONTACTED THE DEP CTLR AND TOLD HIM THAT WE WERE CLBING OUT OF 2200 FT FOR 5000 FT AND IN A R TURN TO 040 DEG HDG. THE DEP CTLR ACKNOWLEDGED WITH 'RADAR CONTACT, CLB AND MAINTAIN 6000 FT.' THE DEP CTLR DID NOT CATCH OUR HDG CHANGE READBACK TO 040 DEGS BECAUSE HE DID NOT ISSUE THE HDG CHANGE AND DIDN'T EXPECT IT. LATER IN THE CLBOUT DEP ASKED US OUR HDG TODAY. I REPLIED WITH 'THEY ASSIGNED US 040 DEGS,' WHICH I BELIEVED THEY HAD. DEP THEN INSTRUCTED US TO TURN TO 070 DEGS. THE PROB AROSE WHEN TWR RESTATED A HDG THAT WE HAD ALREADY BEEN ISSUED. I ANTICIPATED A R TURN, AND I READ BACK THE BELIEVED HDG CHANGE TO THE DEP CTLR, WHO WAS NOT EXPECTING IT. IN THE FUTURE ATC INSTRUCTION SHOULD BE READ BACK TO THE ISSUING CTLR AND NOT TO THE NEXT ASSIGNED CTLR. SUPPLEMENTAL INFO FROM ACN 331706: WE WERE ANTICIPATING FAIRLY RAPID TURNS TO THE E AS IS TYPICAL LEAVING O'HARE HEADING TOWARDS ELX. SOMEHOW WE HAD 040 DEGS IN OUR HEAD. HOW COULD IT POSSIBLY HAPPEN? AN ATR CLRED FOR TKOF ON RWY 32R JUST PRIOR TO US WAS GIVEN AN IMMEDIATE R TO 040 DEGS, AND WHEN ORD TWR GAVE US THE HDOF TO DEP ON 125.0 AND RESTATED THE HDG OF 010 DEGS (WE WERE ALREADY WELL ESTABLISHED ON 010 DEGS) THIS COULD HAVE TRIGGERED US BELIEVING WE WERE INSTRUCTED TO TURN TO 040 DEGS. TWR RESTATING A PREVIOUSLY ISSUED HDG I FEEL IS A LITTLE UNUSUAL.

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.