F11 controller described a conflict event when failing to hear the pilots initial heading report whi...

Narrative:

I was working stn/stv with a couple departures and practice approaches into sfb. A PA-44 was doing practice approaches to runway 9L; when he went missed; I noticed he was northwest bound. I called sfb and questioned what he was doing; they said he was turning to heading 050. That put him in my downwind but I had no traffic. I had a SR20 depart a few minutes before that also on a bad heading. So after I identified the PA-44; an A330 was calling. I told the A330 to 'ident' and was looking for the flm/controller in charge to have them call the tower to see what was going on up there. When the flm came over he said are you ok with those two; I looked and the A330 was turning; I tried to turn him back but then I decided west was better and went back to the west. Separation was lost between the A330 and the PA-44. The A330 checked in turning to a heading of 280 and I didn't hear it. I was also advised by flm that the tower assigned the A330 a 280 heading. Recommendation; I should have heard the check-in turning to a 280 heading; that was when I was calling for the flm. Tower has to be careful with headings.

Original NASA ASRS Text

Title: F11 Controller described a conflict event when failing to hear the pilots initial heading report which was issued in error by the SFB Controller.

Narrative: I was working STN/STV with a couple departures and practice approaches into SFB. A PA-44 was doing practice approaches to Runway 9L; when he went missed; I noticed he was northwest bound. I called SFB and questioned what he was doing; they said he was turning to HDG 050. That put him in my downwind but I had no traffic. I had a SR20 depart a few minutes before that also on a bad heading. So after I identified the PA-44; an A330 was calling. I told the A330 to 'ident' and was looking for the FLM/CIC to have them call the Tower to see what was going on up there. When the FLM came over he said are you ok with those two; I looked and the A330 was turning; I tried to turn him back but then I decided west was better and went back to the west. Separation was lost between the A330 and the PA-44. The A330 checked in turning to a heading of 280 and I didn't hear it. I was also advised by FLM that the Tower assigned the A330 a 280 heading. Recommendation; I should have heard the check-in turning to a 280 heading; that was when I was calling for the FLM. Tower has to be careful with headings.

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

Attributes
ACN	1123009
Time
Date	201310
Local Time Of Day	1801-2400
Place
Locale Reference	F11.TRACON
State Reference	FL
Aircraft 1
Make Model Name	PA-44 Seminole/Turbo Seminole
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	SR20
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

F11 controller described a conflict event when failing to hear the pilots initial heading report which was issued in error by the sfb controller.