B737-500
Air Traffic Control Fully Certified
Situational Awareness
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Weather; Procedure
There was a line of moderate to extreme precipitation that stretched across the northern part of the sector. Aircraft were deviating along with the departures that were coming off of MCO that were also deviating. During this time I was giving OJT to my Trainee and it got to the point where I had to eventually take over. Palm Beach Approach kept putting us in and out of hold because their final was saturated and they were also very busy. When they did open back up they wanted 20 miles in trail. This caused me to put a Gulfstream; a PBI lander on a 270 degree heading and giving him a descent to 15;000 FT. A short time later I had a B737 come off of MCO he was heading east for weather. His destination was towards the southeast. Right around this time is when I had to take over for my trainee. As soon as I saw these two aircraft on a converging course I didn't have time to use altitude because I needed 2;000 FT separation because the altimeters were below 29.92. I turned the B737 to a heading of 180. And I put the Gulfstream on a heading of 360. By then the conflict alert went off. I think there should have been better pre-planning between management and TMU. I think if we would have had better in-trail or more spacing I think this could have been prevented; taking into consideration the line of weather that was stretching across the state.
ZMA Controller experienced a loss of separation event when traffic and weather introduced complications difficult to overcome; the reporter listing the lack of pre-planning between management and the TMU as a causal factor.