Narrative:

Pbi ATIS reported 6 scattered, 47 scattered, 60 scattered, 10 mi plus visibility, localizer back course runway 27R in use. About 5 mi south of keach FAF, the controller turned and cleared us for the VOR runway 31 approach, which we weren't set up for. We tuned our vors, and approach course which, initially, showed us on course. We began our descent to FAF altitude. Winds, or whatever, fully displaced our course so we initiated a map around 1200 ft. At the same time the controller called our 'low altitude alert' and issued a missed approach clearance. We followed the map instructions, followed by the localizer back course runway 27R and landed. Contributing factors: 1) ATIS: indicated VFR conditions at the field when a major WX system was passing over the field. 2) communications: we were never told of the VOR runway 31 approach until final turn. Supplemental information from acn 296993: on vector for runway 27R localizer back course to pbi and within 4 mi of same fix, controller cleared us for VOR runway 31 approach. I used raw data source since time did not allow for a FMS set up. We experienced a speed variation of plus or minus 15 KTS at 200-300 ft to runway 27R. Time was a problem and the confusion as to correct runway while on a vector compounded the problem because of our proximity to inbound course. Also, other aircraft were given runway 31 VOR approach, this is the reason I had the chart out, but the lack of communications by approach did not allow for proper preparations.

Related reports:

Google
 

Original NASA ASRS Text

Title: A FLC UNDERSTOOD THAT THEY WERE ON A VECTOR FOR AN APCH WHICH THEY DID NOT RECEIVE. THEY COMPLIED WITH THE 'NEW' APCH ON RAW DATA, BUT FAILED TO MAINTAIN RADIAL INBOUND, AND CTLR CALLED 'LOW ALT ALERT.'

Narrative: PBI ATIS RPTED 6 SCATTERED, 47 SCATTERED, 60 SCATTERED, 10 MI PLUS VISIBILITY, LOC BC RWY 27R IN USE. ABOUT 5 MI S OF KEACH FAF, THE CTLR TURNED AND CLRED US FOR THE VOR RWY 31 APCH, WHICH WE WEREN'T SET UP FOR. WE TUNED OUR VORS, AND APCH COURSE WHICH, INITIALLY, SHOWED US ON COURSE. WE BEGAN OUR DSCNT TO FAF ALT. WINDS, OR WHATEVER, FULLY DISPLACED OUR COURSE SO WE INITIATED A MAP AROUND 1200 FT. AT THE SAME TIME THE CTLR CALLED OUR 'LOW ALT ALERT' AND ISSUED A MISSED APCH CLRNC. WE FOLLOWED THE MAP INSTRUCTIONS, FOLLOWED BY THE LOC BC RWY 27R AND LANDED. CONTRIBUTING FACTORS: 1) ATIS: INDICATED VFR CONDITIONS AT THE FIELD WHEN A MAJOR WX SYS WAS PASSING OVER THE FIELD. 2) COMS: WE WERE NEVER TOLD OF THE VOR RWY 31 APCH UNTIL FINAL TURN. SUPPLEMENTAL INFO FROM ACN 296993: ON VECTOR FOR RWY 27R LOC BACK COURSE TO PBI AND WITHIN 4 MI OF SAME FIX, CTLR CLRED US FOR VOR RWY 31 APCH. I USED RAW DATA SOURCE SINCE TIME DID NOT ALLOW FOR A FMS SET UP. WE EXPERIENCED A SPD VARIATION OF PLUS OR MINUS 15 KTS AT 200-300 FT TO RWY 27R. TIME WAS A PROB AND THE CONFUSION AS TO CORRECT RWY WHILE ON A VECTOR COMPOUNDED THE PROB BECAUSE OF OUR PROX TO INBOUND COURSE. ALSO, OTHER ACFT WERE GIVEN RWY 31 VOR APCH, THIS IS THE REASON I HAD THE CHART OUT, BUT THE LACK OF COMS BY APCH DID NOT ALLOW FOR PROPER PREPARATIONS.

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