Narrative:

I contacted departure at 500' MSL after departing bfm. Departure advised that he was going to take me out 'a little wide' before he turned me on course. My on course heading was 030. I was instructed to turn left to 080, which I repeated to him, and proceeded to do so. Between 2000' and 3000' MSL (2 mins after my initial turn to 080) the controller began speaking so frantically that I could not understand what he was saying. I heard him refer to company aircraft and realized that he was referring to me. I responded to him asking if that was meant for atx X, (my proper call sign). He instructed me very frantically to 'turn to 180, opp direction, same altitude, 2 mi. I turned immediatley to the heading. I continued the flight and figured the controller must have had traffic that he had forgotten to warn me about, or traffic that must have unexpectedly appeared on radar. As I left his airspace he requested to have my name. I feel that 2 things could have been done on the part of the controller that would have eliminated this entire mishap. Upon takeoff, he could have been more specific about why he was taking me 'a little wide'. If I was aware that the reason was traffic, I would have had a better clue as to why he got frantic all of a sudden. When the controller noticed there was a sep problem between me and the other aircraft, he should have stayed a little more calm instead of speaking so fast as to have no one understand what he was saying and to rush himself into calling me by the wrong call sign. His communication at this point only wasted more time.

Related reports:

Google
 

Original NASA ASRS Text

Title: SMT X HAD LESS THAN STANDARD SEPARATION FROM ACFT Y. SYSTEM ERROR.

Narrative: I CONTACTED DEP AT 500' MSL AFTER DEPARTING BFM. DEP ADVISED THAT HE WAS GOING TO TAKE ME OUT 'A LITTLE WIDE' BEFORE HE TURNED ME ON COURSE. MY ON COURSE HDG WAS 030. I WAS INSTRUCTED TO TURN L TO 080, WHICH I REPEATED TO HIM, AND PROCEEDED TO DO SO. BTWN 2000' AND 3000' MSL (2 MINS AFTER MY INITIAL TURN TO 080) THE CTLR BEGAN SPEAKING SO FRANTICALLY THAT I COULD NOT UNDERSTAND WHAT HE WAS SAYING. I HEARD HIM REFER TO COMPANY ACFT AND REALIZED THAT HE WAS REFERRING TO ME. I RESPONDED TO HIM ASKING IF THAT WAS MEANT FOR ATX X, (MY PROPER CALL SIGN). HE INSTRUCTED ME VERY FRANTICALLY TO 'TURN TO 180, OPP DIRECTION, SAME ALT, 2 MI. I TURNED IMMEDIATLEY TO THE HDG. I CONTINUED THE FLT AND FIGURED THE CTLR MUST HAVE HAD TFC THAT HE HAD FORGOTTEN TO WARN ME ABOUT, OR TFC THAT MUST HAVE UNEXPECTEDLY APPEARED ON RADAR. AS I LEFT HIS AIRSPACE HE REQUESTED TO HAVE MY NAME. I FEEL THAT 2 THINGS COULD HAVE BEEN DONE ON THE PART OF THE CTLR THAT WOULD HAVE ELIMINATED THIS ENTIRE MISHAP. UPON TKOF, HE COULD HAVE BEEN MORE SPECIFIC ABOUT WHY HE WAS TAKING ME 'A LITTLE WIDE'. IF I WAS AWARE THAT THE REASON WAS TFC, I WOULD HAVE HAD A BETTER CLUE AS TO WHY HE GOT FRANTIC ALL OF A SUDDEN. WHEN THE CTLR NOTICED THERE WAS A SEP PROB BTWN ME AND THE OTHER ACFT, HE SHOULD HAVE STAYED A LITTLE MORE CALM INSTEAD OF SPEAKING SO FAST AS TO HAVE NO ONE UNDERSTAND WHAT HE WAS SAYING AND TO RUSH HIMSELF INTO CALLING ME BY THE WRONG CALL SIGN. HIS COM AT THIS POINT ONLY WASTED MORE TIME.

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.