Medium Transport; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 2
Confusion; Workload
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Procedure; Weather
While working the radar position on Sector 05; we were feeding Miami Approach all of the arrivals through one fix.  Every single airport in Miami Approach's airspace was being fed through the FAMIN ATA due to weather.  Aircraft X was level at 100 and Approach had the handoff with communication.  I had initially vectored Aircraft Y northbound due to the overtake he had on Aircraft X.  I waited till we had about 10 miles in between the aircraft and then proceeded to clear Aircraft Y inbound towards CURSO to cross CURSO at 100 and 210 knots.  I noticed that Aircraft Y was catching Aircraft X and I tried to stop him at 110 but he had already descended through 110.  I verified that he had reduced to 210 knots and proceeded to ship him to Approach.  At this time separation was less than 5 miles but approach was already talking to Aircraft X and I am uncertain of what type of rule they were using to separate the two aircraft.  My Supervisor told me that Approach might have been using a legal vector in order to maintain their separation standards. Everytime that there is weather over the SSCOT and JINGL arrivals; the procedure is to send all of the arrivals to the FAMIN ATA.  All of the aircraft have to cross the same fix at the same altitude and we pretty much have an air show every time trying to sequence 4 arrivals into 1.  Most of the time during the summer months; we not only get the arrivals from the north but we also get the arrivals from the east coast and then we have to try and sequence 6 arrivals in through 1 fix.  I always hear everybody complaining about this; but nothing has ever been done to remedy this situation.  Maybe we can incorporate a different procedure so that one controller doesn't have to be overloaded with this type of workload. There is more than enough space in approach to at least make another ATA for situations like these.  As far as the overtake with Aircraft Y and Aircraft X; if I wouldn't had been so busy trying to sequence all the arrivals; I would have shipped Aircraft Y as soon as they took the handoff and their would be no doubt in mind that approach was using some type of divergence rule to separate the aircraft.
ZMA Controller reports of traffic being funneled over one fix causing an operational error issue to speed differences.