Narrative:

Planned to land on runway 28R in fll. At 10 miles; and 6000 ft; tower requested that we land on 28L. First officer had already run data for both runways so we agreed. I had read the company briefing [in the weather] packet; but misinterpreted the information to restrict our takeoff not landing. After we passed 100 ft we received a GPWS alert. We were almost on the runway so we continued to land uneventfully. Of course this is when we realized that we had made a mistake and referenced the weather packet again to find our error. The best way to prevent this in future is to remove the data for that runway from the opc. If the data was not there we would not have tried to land on 28L.

Google
 

Original NASA ASRS Text

Title: The flight crew of a B737NG was switched to and landed on Runway 28L at FLL after failing to recall a company restriction to not do so. They received a nuisance GPWS alert just at touchdown.

Narrative: Planned to land on RWY 28R in FLL. At 10 miles; and 6000 FT; Tower requested that we land on 28L. First Officer had already run data for both RWYS so we agreed. I had read the Company briefing [in the weather] packet; but misinterpreted the information to restrict our takeoff not landing. After we passed 100 FT we received a GPWS alert. We were almost on the runway so we continued to land uneventfully. Of course this is when we realized that we had made a mistake and referenced the weather packet again to find our error. The best way to prevent this in future is to remove the data for that runway from the OPC. If the data was not there we would not have tried to land on 28L.

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.