Date: 201507
Local time of day: 1201-1800
Location: ZMA.ARTCC, FL
Weather elements / visibility: Rain; Thunderstorm
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turboprop Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class G ZMA
ATC / advisory: Center ZMA
Second aircraft: Large Transport
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Communication Breakdown; Distraction; Workload; Troubleshooting; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Airspace Structure; Company Policy; Weather; Human Factors; Procedure
Primary problem: Weather

Narrative: I was working as an On the Job Training Instructor (OJTI) on the D-Side at Sector 66 & 67 combined. We had severe weather on the west side of our sector; with the military restricted airspace (R2901) active in the center of the state. This was also including PLACID MOAs (East: 070-FL230 West: 70-150) active as well. The weather was very dynamic and moving around significantly throughout the day. At numerous points throughout the day; the R-Side controller advised the Front Line Manager (FLM); that the aircraft were deviating extremely close to the active military airspace.At one point; the weather and the military airspace were approximately 5-8 miles separated. We advised our FLM and Traffic Management Unit (TMU) that we weren't able to work any arrivals through that hole anymore; but they kept insisting that they had only 'one more plane'. Each time; it was only 1 more plane. There were numerous departures (3 or 4?) and several arrivals (5+?) that came through this hole with deviations. Towards the middle of the session; Aircraft Y was assigned a heading adjacent the extreme precipitation. He was approximately 1 mile from the precipitation; at the most. [Aircraft X] was also vectored along the edge of the precipitation.This is an extremely difficult situation that we're put in; because of our supervisors and TMU. This situation is dangerous because we keep advising the FLM that aircraft either 1) Don't want to go through the hole we're vectoring them through; which means they end up violating the MOAs or Restricted airspace; or 2) We're at severe risk to experience turbulence and possibly end up with structure damage or injuries.We are instructed through numerous CBI's to keep aircraft 'at least 20 miles from thunderstorms' to avoid their effects; but we constantly are instructed by TMU and management that we have to 'use the hole' on the scope.We're (Everglades controllers) are continually set up for failure in these situations. Two years ago; a Pilatus crashed in our airspace because of IMC conditions and deviating around extreme precipitation. The pilot was inexperienced; but was deviating for extreme weather none-the-less. The aircraft only stopped arriving through this hole after I reached out to surrounding sectors and was able to coordinate something through Jacksonville Center; essentially taking TMU out of the loop. I have attached an rough image of what the sector looked like; including the normal arrival and departures; and where these aircraft were arriving and departing.We need to address weather deviations in Miami Center. Too often we're forced in putting aircraft a mile east; though; or right on top of the weather; because our limited airspace and the lack of cooperation from management/TMU. This is dangerous; and will lead to injuries or damage to aircraft.




Synopsis: ZMA Controller reports of conflicting information from TMU and Management about vectoring aircraft close to or through weather. Controller describes a scenario where two aircraft are close to weather and the impact it may have on the flights.