A CLRNC LIMIT IS EXCEEDED ARRIVING AT FREEPORT; BAHAMAS FOLLOWED BY MUCH CONFUSION DURING THE SUBSEQUENT APCH TO THE ARPT.
Synopsis
A CLRNC LIMIT IS EXCEEDED ARRIVING AT FREEPORT; BAHAMAS FOLLOWED BY MUCH CONFUSION DURING THE SUBSEQUENT APCH TO THE ARPT.
Narrative
INBOUND TO FREEPORT; BAHAMAS ON BR65V; ZMA GAVE US A CLRNC LIMIT OF RAPPS INTXN. THEN; DURING OUR DSCNT; WE WERE TOLD TO CROSS RAPPS AT 7000 FT. ABOUT 8 MI FROM RAPPS; GOING THROUGH 10000 FT; ZMA TOLD US TO STOP DSCNT AND MAINTAIN 9000 FT. THEN ZMA CHANGED THAT CLRNC AND TOLD US TO MAINTAIN 10000 FT. WE STARTED TO REVERSE OUR DSCNT AND CLB BACK TO 10000 FT. THEN ZMA CHANGED THE CLRNC AGAIN TO DSND TO 9000 FT. UP TO THIS POINT; WE DID NOT KNOW WHY THE ALT CLRNC HAD BEEN CHANGED. THEN; LISTENING TO THE FREQ; WE HEARD OF NEARBY TFC LEVEL AT 8500 FT. ZMA NEVER DIRECTLY TOLD US OF THIS TFC. ALL THIS WAS OCCURRING AS ZMA WAS IN THE PROCESS OF HANDING US OFF TO GRAND BAHAMA APCH. THERE WAS FREQ CONGESTION AND IT TOOK SOME TIME TO MAKE CONTACT WITH GRAND BAHAMA APCH; WHICH DOES NOT HAVE RADAR COVERAGE IN THIS AREA. MEANWHILE; I HAD FORGOTTEN ABOUT RAPPS BEING A CLRNC LIMIT AND FLEW PAST IT. I FORGOT IF ZMA EVER TOLD US RADAR SVC WAS TERMINATED. GRAND BAHAMA APCH ASKED US OUR POS AFTER ESTABLISHING CONTACT. WE GAVE OUR POS PAST RAPPS INTXN WHICH JOGGED MY MEMORY OF THE CLRNC LIMIT. GRAND BAHAMA APCH DID NOT SEEM DISTURBED WE HAD FLOWN PAST IT; NOR DID THEY EVER INDICATE THIS EVENT CAUSED A CONFLICT. HOWEVER; THEY DID REMIND US WE HAD NOT RPTED RAPPS TO THEM ON CONTACT. WE CONTINUED INBOUND ON BR65V AND RECEIVED A DSCNT TO 7000 FT. THERE IS NO ATIS INFO AT FREEPORT AND WE ASKED APCH WHICH RWY WAS ACTIVE AT THE FIELD. THE ANSWER WAS RWY 24; WHICH WAS NOT THE RWY WE HAD EXPECTED AND SET UP IN OUR FMS. (RWY 6 IS THE PREFERENTIAL RWY AT FREEPORT.) AS WE STARTED REPROGRAMMING OUR FMS FOR RWY 24; APCH ASKED FOR OUR DME POS OFF FREEPORT VOR. I REPLIED 12 DME AND WAS IMMEDIATELY TOLD TO ENTER A 12 DME ARC. I WAS NOT TOLD WHICH DIRECTION TO ARC AND INITIALLY STARTED TO ARC TO THE W WHICH WAS THE WRONG DIRECTION FOR RWY 24. APCH THEN CLRED US FOR A VOR APCH TO RWY 24. I REALIZED QUICKLY THE ARC NEEDED TO BE TO THE E AND REVERSED COURSE BEFORE I HAD ESTABLISHED THE ARC TO THE W. AT THE SAME TIME; WE WERE TRYING TO TELL APCH WE NEEDED CLRNC FOR THE RNAV RWY 24 APCH. OUR ACFT IS NOT CERTIFIED FOR VOR APCHS. THE RNAV RWY 24 APCH DOES NOT INCLUDE AN ARC AND THE 12 DME ARC WOULD NOT POS US ON THE APCH SEGMENT AT AN IAF. WE TRIED TO EXPLAIN THIS TO THE APCH CTLR BUT HE SEEMED CONFUSED ABOUT OUR RNAV RWY 24 REQUEST. INSTEAD; HE NEVER GAVE US THE RNAV RWY 24 APCH CLRNC; BUT INSTEAD TOLD US TO CONTACT TWR. WE CONTACTED TWR AND WE REQUESTED CLRNC TO GIGNE WAYPOINT; WHICH IS AN IAF FOR THE RNAV RWY 24 APCH. TWR INSTEAD CLRED US TO THE BAAMA WAYPOINT (ANOTHER IAF FOR THE RNAV RWY 24). BY THIS TIME; WE WERE VFR. WE PROCEEDED TO BAAMA AND EXECUTED THE APCH TO AN UNEVENTFUL LNDG. SUMMARY AND RECOMMENDATION: CHANGING ALT CLRNCS; SEARCHING FOR VFR TFC; A LATE CTR HDOF TO APCH AND FREQ CONGESTION CONTRIBUTED TO MY FAILURE TO REMEMBER THE RAPPS CLRNC LIMIT. I WILL AVOID THIS IN THE FUTURE BY PROGRAMMING A HOLD INTO THE FMS WHENEVER I RECEIVE A CLRNC LIMIT. I CAN EASILY DELETE THE HOLD WHEN FURTHER CLRNC IS RECEIVED. ALSO; GRAND BAHAMA APCH NEEDS TO BE FAMILIAR WITH RNAV APCHS.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.