Narrative:

According to the fll ATIS, the WX was scattered clouds at 800 ft, broken at 2500 ft, visibility 10 mi, temperature 20 degrees C (68 degrees F) wind 340 degrees at 9 KTS. The normal runway used by air carrier's is runway 9L/27R. Runway 9R/27L is too short for air carrier's and is used by GA aircraft only. Runway 9L/27R was closed for resurfacing, a process which would take about 2 weeks. Runway 13/31 was the active runway due to the closure of runway 9L. Runway 13/31 is 6000 ft long, and normally not used by air carrier's due to its relatively short length and because of noise abatement concerns. There is a published localizer approach to runway 13, which is the preferred runway when runway 9L is not available. We flew downwind at 4000 ft, west of the airport. Abeam the airport, mia approach control told us to expect a visual approach, and asked if we had the airport in sight at our 9 O'clock position, 3 mi. I told approach control that there was a broken layer of clouds below us that was blocking our view of ft lauderdale, except for occasional sightings between the clouds. Approach told us to continue downwind heading 130 degrees, and that they would vector us onto approximately a 10 mi final approach. Since air carrier's rarely use runway 31, there were no commercial approach plates for that runway in our book bag. However, the FMS did have an 'RNAV 31' approach in the computer. To enhance situational awareness, I selected the RNAV 31 FMS approach and activated it as a back-up to our visual approach. I also tuned and idented the localizer for runway 13, which was operating, despite the fact that runway 31 was in use, not runway 13. The localizer, although giving a back course presentation, was still useful for situational awareness. Throughout our descending base leg, and during the first few hundred ft of descent on final approach the airport was not visible, due to the broken layer of clouds. After we descended underneath the clouds at 2500 ft, I told ATC that we were now below the clouds. My intention was that ATC understood that we could now continue to fll on a visual approach. However, ATC cleared us for a 'GPS approach' to runway 31. I acknowledged by responding 'air carrier X, roger, cleared for the approach.' we completed a normal visual approach and touchdown, using the FMS RNAV 31 presentation and backcourse localizer for situational awareness. Flight operations was concerned about the legality of responding 'cleared for the approach' to ATC when they cleared us for a 'GPS approach' instead of specifically stating 'negative, we don't have approach charts for a GPS approach, but we can do a visual approach.' I told flight operations that I had stated that we were 'below the clouds,' meaning that were capable of performing a visual approach. However, I realize that technically, we were probably cleared for a 'GPS approach' by ATC, and that I should have been more specific in making ATC aware that we were executing a visual approach, since we didn't have a commercial approach chart for a GPS approach. The lesson learned is to be more specific when communicating with ATC, for both potential safety of flight reasons and for complying with technical legalities.

Google
 

Original NASA ASRS Text

Title: B757 FLT CREW LNDG FLL EXPRESSED CONCERN FOR COMPLETING A VISUAL APCH WHEN ATC ISSUED A GPS APCH CLRNC.

Narrative: ACCORDING TO THE FLL ATIS, THE WX WAS SCATTERED CLOUDS AT 800 FT, BROKEN AT 2500 FT, VISIBILITY 10 MI, TEMP 20 DEGS C (68 DEGS F) WIND 340 DEGS AT 9 KTS. THE NORMAL RWY USED BY ACR'S IS RWY 9L/27R. RWY 9R/27L IS TOO SHORT FOR ACR'S AND IS USED BY GA ACFT ONLY. RWY 9L/27R WAS CLOSED FOR RESURFACING, A PROCESS WHICH WOULD TAKE ABOUT 2 WKS. RWY 13/31 WAS THE ACTIVE RWY DUE TO THE CLOSURE OF RWY 9L. RWY 13/31 IS 6000 FT LONG, AND NORMALLY NOT USED BY ACR'S DUE TO ITS RELATIVELY SHORT LENGTH AND BECAUSE OF NOISE ABATEMENT CONCERNS. THERE IS A PUBLISHED LOC APCH TO RWY 13, WHICH IS THE PREFERRED RWY WHEN RWY 9L IS NOT AVAILABLE. WE FLEW DOWNWIND AT 4000 FT, W OF THE ARPT. ABEAM THE ARPT, MIA APCH CTL TOLD US TO EXPECT A VISUAL APCH, AND ASKED IF WE HAD THE ARPT IN SIGHT AT OUR 9 O'CLOCK POS, 3 MI. I TOLD APCH CTL THAT THERE WAS A BROKEN LAYER OF CLOUDS BELOW US THAT WAS BLOCKING OUR VIEW OF FT LAUDERDALE, EXCEPT FOR OCCASIONAL SIGHTINGS BTWN THE CLOUDS. APCH TOLD US TO CONTINUE DOWNWIND HDG 130 DEGS, AND THAT THEY WOULD VECTOR US ONTO APPROX A 10 MI FINAL APCH. SINCE ACR'S RARELY USE RWY 31, THERE WERE NO COMMERCIAL APCH PLATES FOR THAT RWY IN OUR BOOK BAG. HOWEVER, THE FMS DID HAVE AN 'RNAV 31' APCH IN THE COMPUTER. TO ENHANCE SITUATIONAL AWARENESS, I SELECTED THE RNAV 31 FMS APCH AND ACTIVATED IT AS A BACK-UP TO OUR VISUAL APCH. I ALSO TUNED AND IDENTED THE LOC FOR RWY 13, WHICH WAS OPERATING, DESPITE THE FACT THAT RWY 31 WAS IN USE, NOT RWY 13. THE LOC, ALTHOUGH GIVING A BACK COURSE PRESENTATION, WAS STILL USEFUL FOR SITUATIONAL AWARENESS. THROUGHOUT OUR DSNDING BASE LEG, AND DURING THE FIRST FEW HUNDRED FT OF DSCNT ON FINAL APCH THE ARPT WAS NOT VISIBLE, DUE TO THE BROKEN LAYER OF CLOUDS. AFTER WE DSNDED UNDERNEATH THE CLOUDS AT 2500 FT, I TOLD ATC THAT WE WERE NOW BELOW THE CLOUDS. MY INTENTION WAS THAT ATC UNDERSTOOD THAT WE COULD NOW CONTINUE TO FLL ON A VISUAL APCH. HOWEVER, ATC CLRED US FOR A 'GPS APCH' TO RWY 31. I ACKNOWLEDGED BY RESPONDING 'ACR X, ROGER, CLRED FOR THE APCH.' WE COMPLETED A NORMAL VISUAL APCH AND TOUCHDOWN, USING THE FMS RNAV 31 PRESENTATION AND BACKCOURSE LOC FOR SITUATIONAL AWARENESS. FLT OPS WAS CONCERNED ABOUT THE LEGALITY OF RESPONDING 'CLRED FOR THE APCH' TO ATC WHEN THEY CLRED US FOR A 'GPS APCH' INSTEAD OF SPECIFICALLY STATING 'NEGATIVE, WE DON'T HAVE APCH CHARTS FOR A GPS APCH, BUT WE CAN DO A VISUAL APCH.' I TOLD FLT OPS THAT I HAD STATED THAT WE WERE 'BELOW THE CLOUDS,' MEANING THAT WERE CAPABLE OF PERFORMING A VISUAL APCH. HOWEVER, I REALIZE THAT TECHNICALLY, WE WERE PROBABLY CLRED FOR A 'GPS APCH' BY ATC, AND THAT I SHOULD HAVE BEEN MORE SPECIFIC IN MAKING ATC AWARE THAT WE WERE EXECUTING A VISUAL APCH, SINCE WE DIDN'T HAVE A COMMERCIAL APCH CHART FOR A GPS APCH. THE LESSON LEARNED IS TO BE MORE SPECIFIC WHEN COMMUNICATING WITH ATC, FOR BOTH POTENTIAL SAFETY OF FLT REASONS AND FOR COMPLYING WITH TECHNICAL LEGALITIES.

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.