Narrative:

While inbound for landing at the regional airport; I was handed over to tower by ellsworth approach control. I checked in and was advised I was number 2 for landing on runway 14. A king air was approximately 6 miles to the north of the airport inbound. I was approximately 6-7 miles northwest of the airport at that time. My observer and I identified the inbound king air; and noting the major differences in airspeed between the two aircraft; began our approach to final for runway 14 to allow separation between his landing and runway departure; and ours. Apparently there was some miscommunication between the tower controller and me; as he became irate and advised me to pick up an easterly heading to intercept a straight in for runway 14. I advised him that I would correct to a heading of 090 until aligned with runway 14. There was a fairly strong wind flow out of the south which was allowing for a major crab angle for approach to landing. There was plenty of distance between the king air and my aircraft; as he was down and clear well before my touchdown on runway 14. I had been operating out of the airport all day long and had not had any conflicts prior to this. This was the same tower operator I had communicated with for the entire day. I made the drop off of my observer and departed but neglected to reset my transponder to the VFR code. I subsequently was advised of this by the tower controller; and corrected it prior to departing his airspace. I thanked him for his assistance for the day and proceeded uneventfully; VFR in VMC. I believe this was a minor miscommunication between the tower and I. In the future; I will attempt to clarify this with the controller.

Related reports:

Google
 

Original NASA ASRS Text

Title: C206 pilot reports apparent misunderstanding with RAP Tower Controller after sighting King Air traffic to follow. Controller issued a heading to intercept final in an irate tone.

Narrative: While inbound for landing at the regional airport; I was handed over to tower by Ellsworth approach control. I checked in and was advised I was number 2 for landing on Runway 14. A King Air was approximately 6 miles to the north of the airport inbound. I was approximately 6-7 miles northwest of the airport at that time. My observer and I identified the inbound King Air; and noting the major differences in airspeed between the two aircraft; began our approach to final for Runway 14 to allow separation between his landing and runway departure; and ours. Apparently there was some miscommunication between the tower controller and me; as he became irate and advised me to pick up an easterly heading to intercept a straight in for Runway 14. I advised him that I would correct to a heading of 090 until aligned with Runway 14. There was a fairly strong wind flow out of the south which was allowing for a major crab angle for approach to landing. There was plenty of distance between the King Air and my aircraft; as he was down and clear well before my touchdown on Runway 14. I had been operating out of the airport all day long and had not had any conflicts prior to this. This was the same tower operator I had communicated with for the entire day. I made the drop off of my observer and departed but neglected to reset my transponder to the VFR code. I subsequently was advised of this by the tower controller; and corrected it prior to departing his airspace. I thanked him for his assistance for the day and proceeded uneventfully; VFR in VMC. I believe this was a minor miscommunication between the tower and I. In the future; I will attempt to clarify this with the controller.

Data retrieved from NASA's ASRS site as of April 2012 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.