Narrative:

Inbound to tncm; crossed slugo intersection at FL120 (transition level FL065) encountered extreme frequency congestion on juliana approach; instructed to slow to 210 KIAS. Requested descent and instructed to maintain FL120 and enter holding at gabul intersection with no other information provided. Extreme volume of radio traffic prevented further instruction. Turned direct gabul and entered standard holding inbound to gabul on the 347 degree bearing to (if/IAF) avaki depicted on the RNAV (gnss) rw 10 approach; 12-1. Corporate jet entering slugo instructed to maintain FL130 indicating 800 feet above us passed opposite direction within 2 NM inside at the apex of our north holding turn; no TCAS alert. Suspect they'd transitioned their altimeters (local 30.03) at FL180 instead of the prescribed FL065. They entered holding above us; so we maintained position 180 degrees out/opposite in our hold. Another aircraft entered from slugo at FL120 on course direct sxm and I could see on TCAS that he was proceeding inside of our depicted holding pattern at our altitude at our 4 o'clock position as we proceeded on a 167 degree track to gabul. Juliana approach issued instruction for that aircraft to 'turn immediately to 110 degrees.' I could see that our right turn outbound from gabul would place us in direct conflict with that aircraft's path; so instructed first officer PF to make a left turn at gabul and transmitted forcefully that we were turning left in holding to avoid traffic conflict at our altitude. Controller responded with vector east and descent clearance. Subsequent vectors to approach and an otherwise uneventful landing. Traffic and frequency congestion today was absolutely epic. Traffic poured in from slugo and was instructed to hold at gabul; which places these aircraft's holding track in direct conflict with last received routing clearance from san juan of slugo direct juliana. Suggest an arrival plan be devised which allows holding be assigned at an intermediate fix that eliminates conflicting tracks with aircraft arriving over slugo; and that this plan be depicted for aircrew. Further; that complete holding instructions be transmitted by juliana approach.

Google
 

Original NASA ASRS Text

Title: B737 Captain experiences traffic and frequency congestion of absolutely epic proportions upon entering TNCM airspace. Holding instructions are not complete and at least one aircraft is holding with the wrong altimeter setting. The reporter uses his own initiative to avoid an aircraft passing through the holding pattern at the same altitude; before ATC takes notice and issues vectors to separate the aircraft. Reporter suggests better planning and more holding fixes further from the airport are in order.

Narrative: Inbound to TNCM; crossed SLUGO intersection at FL120 (transition level FL065) encountered extreme frequency congestion on Juliana Approach; instructed to slow to 210 KIAS. Requested descent and instructed to maintain FL120 and enter holding at GABUL intersection with no other information provided. Extreme volume of radio traffic prevented further instruction. Turned direct GABUL and entered standard holding inbound to GABUL on the 347 degree bearing to (IF/IAF) AVAKI depicted on the RNAV (GNSS) RW 10 approach; 12-1. Corporate jet entering SLUGO instructed to maintain FL130 indicating 800 feet above us passed opposite direction within 2 NM inside at the apex of our north holding turn; no TCAS alert. Suspect they'd transitioned their altimeters (local 30.03) at FL180 instead of the prescribed FL065. They entered holding above us; so we maintained position 180 degrees out/opposite in our hold. Another aircraft entered from SLUGO at FL120 on course direct SXM and I could see on TCAS that he was proceeding inside of our depicted holding pattern at our altitude at our 4 o'clock position as we proceeded on a 167 degree track to GABUL. Juliana Approach issued instruction for that aircraft to 'turn immediately to 110 degrees.' I could see that our right turn outbound from GABUL would place us in direct conflict with that aircraft's path; so instructed FO PF to make a left turn at GABUL and transmitted forcefully that we were turning left in holding to avoid traffic conflict at our altitude. Controller responded with vector east and descent clearance. Subsequent vectors to approach and an otherwise uneventful landing. Traffic and frequency congestion today was absolutely epic. Traffic poured in from SLUGO and was instructed to hold at GABUL; which places these aircraft's holding track in direct conflict with last received routing clearance from San Juan of SLUGO direct Juliana. Suggest an arrival plan be devised which allows holding be assigned at an intermediate fix that eliminates conflicting tracks with aircraft arriving over SLUGO; and that this plan be depicted for aircrew. Further; that complete holding instructions be transmitted by Juliana Approach.

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.