Narrative:

Late point out to the adjacent sector; 65. I also filed another report with [another aircraft]; following aircraft X to trv for holding. Issued aircraft X published holding (left turns) instructions at trv; where I already had 4 other aircraft in holding. Aircraft X was northeast of trv so they flew over trv; made left turn north and then head back to trv to establish the holding pattern. Due to their altitude and proximity of trv to the adjacent sector; aircraft X's turn took them into sector 65's airspace and the point out was not accomplished until the aircraft was on the sector boundary. Factors leading to this event: 1. Holding mia traffic for vip movement; holding indefinite and high workload with holding aircraft trying to calculate fuel without an adequate efc time. 2. A couple of holding aircraft decided to divert due to fuel which required a lot of vectors around the holding stack for descent. 3. Fll arrival; fisel; closed for weather and had to reroute via stoop pbi fll; which requires spelling of fix to all aircraft and expediting descent to get them below holding stack; and become a conflict with pbi arrivals increasing the need for vectors to descend the pbi arrivals. 4. Weather to the east of our sector (in sector 01) forced pbi departures to be handed off to us. 5. Zappa/vally dta's (departure transition area) (dtas to the east of fll) closed for weather; adjacent sector (whom we violated) working them via hedly/arkes dta which means they parallel the sector boundary; hand off to us climbing and we have control for turn to the east; almost impossible due to holding stack; a few aircraft were at orl before I could turn them to a heading of 090 to get them to the atlantic routes (ar).this is a common scenario for the hobee sector (02). Whether we're holding for vip or weather. More awareness by the supervisor and tmu to prevent the sector from getting chaotic. Instead of forcing the planes back over the ars; reroute eligible aircraft over land via omn crg and keep them out of hobee and ensure there is in trail for them out the dtas. Pbi arrivals over omn should be forced to FL300 or below; LOA stated they will be at FL360 or below but FL360 is owned by the ultra-high sector above hobee; apolo (17) so often there is a delay in hand off/frequency change making it difficult to descend them though the holding stack and sequencing with the fll reroute.

Google
 

Original NASA ASRS Text

Title: ZMA Center Controller reported an airspace violation due to lack of a timely point out and the close proximity of a holding pattern to the adjacent sector's airspace.

Narrative: Late point out to the adjacent sector; 65. I also filed another report with [another aircraft]; following Aircraft X to TRV for holding. Issued Aircraft X published holding (left turns) instructions at TRV; where I already had 4 other aircraft in holding. Aircraft X was northeast of TRV so they flew over TRV; made left turn north and then head back to TRV to establish the holding pattern. Due to their altitude and proximity of TRV to the adjacent sector; Aircraft X's turn took them into sector 65's airspace and the point out was not accomplished until the aircraft was on the sector boundary. Factors leading to this event: 1. Holding MIA traffic for VIP movement; holding indefinite and high workload with holding aircraft trying to calculate fuel without an adequate EFC time. 2. A couple of holding aircraft decided to divert due to fuel which required a lot of vectors around the holding stack for descent. 3. FLL arrival; FISEL; closed for weather and had to reroute via STOOP PBI FLL; which requires spelling of fix to all aircraft and expediting descent to get them below holding stack; and become a conflict with PBI arrivals increasing the need for vectors to descend the PBI arrivals. 4. Weather to the east of our sector (in sector 01) forced PBI departures to be handed off to us. 5. ZAPPA/VALLY DTA's (Departure Transition Area) (DTAs to the east of FLL) closed for weather; adjacent sector (whom we violated) working them via HEDLY/ARKES DTA which means they parallel the sector boundary; hand off to us climbing and we have control for turn to the east; almost impossible due to holding stack; a few aircraft were at ORL before I could turn them to a heading of 090 to get them to the Atlantic Routes (AR).This is a common scenario for the HOBEE sector (02). Whether we're holding for VIP or weather. More awareness by the supervisor and TMU to prevent the sector from getting chaotic. Instead of forcing the planes back over the ARs; reroute eligible aircraft over land via OMN CRG and keep them out of HOBEE and ensure there is in trail for them out the DTAs. PBI arrivals over OMN should be forced to FL300 or below; LOA stated they will be at FL360 or below but FL360 is owned by the ultra-high sector above HOBEE; APOLO (17) so often there is a delay in hand off/frequency change making it difficult to descend them though the holding stack and sequencing with the FLL reroute.

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