Narrative:

While on arrival into bwi; ATC changed runways from 33L to 15R and gave us a vector. About 10 miles out; we were cleared to 'fly heading 180 and join the localizer' for 15R. On autopilot; we selected 180 heading and VOR/localizer. The aircraft captured a localizer signal and starting turning east. It was apparent on the nd (navigation display) that it was not capturing the proper course. We deselected VOR/localizer and used heading select to go back to a 180 heading. I looked at the ILS identification on the pfd and crosschecked it against my ILS chart; but the ids did not match. The airport had neglected to change the localizer (same frequency) from 33R to 15L (the identification was for 33L). We picked up the airport visually; and were cleared for the visual.then; once on the visual; I started to configure and was showing all white on the PAPI for 15R. I started to descend a bit; but felt low. I asked the captain if he too saw all white; and he did. We referenced the VNAV on the nd it showed us about 200 ft low; which matched what I felt we were seeing out the window. We made a slight correction; and followed the VNAV down to the runway. The papis showed all white all the way to the ground; even though we felt we were on proper glidepath; if not a tad low; with about a 650 fpm descent all the way down. We reported both the localizer and the PAPI to bwi ground. Potomac approach and bwi need better coordination during runway change to ensure that the localizer is changed properly for the active runway. Not sure what to do about the PAPI; but it needs fixing.after landing; our gate was occupied; so we were cleared to join T abeam terminal C. We thought we'd joined T; but ground said 'you're on a; no problem; make a right on T short of east.' as we taxied back; we realized what had happened. Where T and a split; there is confusing signage on the ground in bwi. There is an arrow pointing left to 'join T' but what it really needs to say is 'straight'. We took the (harder) left and joined a by accident. Change the painted signage on the ground to indicate 'straight' to stay on T instead of a left turn.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 First Officer reports being switched to Runway 15R during arrival but ATC forgets to activate the localizer for Runway 15R. During the approach the PAPI shows all white even when low on the approach path. ATC is advised. After landing a taxiway incursion occurs which the First Officer believes is the result of an improperly placed arrow on the taxiway.

Narrative: While on arrival into BWI; ATC changed runways from 33L to 15R and gave us a vector. About 10 miles out; we were cleared to 'fly heading 180 and join the Localizer' for 15R. On autopilot; we selected 180 heading and VOR/LOC. The aircraft captured a Localizer signal and starting turning east. It was apparent on the ND (Navigation Display) that it was not capturing the proper course. We deselected VOR/LOC and used Heading Select to go back to a 180 heading. I looked at the ILS ID on the PFD and crosschecked it against my ILS chart; but the IDs did not match. The airport had neglected to change the Localizer (same frequency) from 33R to 15L (the ID was for 33L). We picked up the airport visually; and were cleared for the visual.Then; once on the visual; I started to configure and was showing all white on the PAPI for 15R. I started to descend a bit; but felt low. I asked the Captain if he too saw all white; and he did. We referenced the VNAV on the ND it showed us about 200 ft low; which matched what I felt we were seeing out the window. We made a slight correction; and followed the VNAV down to the runway. The PAPIs showed all white all the way to the ground; even though we felt we were on proper glidepath; if not a tad low; with about a 650 fpm descent all the way down. We reported both the LOC and the PAPI to BWI ground. Potomac Approach and BWI need better coordination during runway change to ensure that the LOC is changed properly for the active runway. Not sure what to do about the PAPI; but it needs fixing.After landing; our gate was occupied; so we were cleared to join T Abeam terminal C. We thought we'd joined T; but Ground said 'You're on A; no problem; make a right on T short of E.' As we taxied back; we realized what had happened. Where T and A split; there is confusing signage on the ground in BWI. There is an arrow pointing left to 'join T' but what it really needs to say is 'straight'. We took the (harder) left and joined A by accident. Change the painted signage on the ground to indicate 'straight' to stay on T instead of a left turn.

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.