Narrative:

We were cleared the visual approach runway 35; track the localizer in to zzzzz. It is an offset localizer. The zzzzz fix is not in the FMS. It is about 2 NM from the end of the runway at approximately 700 feet. At 1300 feet AGL the 'track the localizer to zzzzz' dropped out of my brain and I prioritized to the stabilized approach criteria. I told the first officer to start moving to the center line of the runway so we could be lined up by 1000 feet. As we did so; tower told us to come back right to get back on the localizer. He asked us if we could see the traffic to our left for runway 34R. I could not see the traffic. In the later phone call with the approach controller; he said it was an rj that was behind us and that they were keeping us in sight. After a few moments of tracking the localizer; tower cleared us to go ahead and come left to line up with the runway. We landed without incident. There is a note on the green page to not do the maneuver we did and that stabilized approach criteria could be deviated from because of the offset approach. We did brief from the missed app/rejected landing table on page 10-7E but completely missed the paragraphs about the visual approach to 35 on 10-7C. While there are contributing factors to this deviation; the bottom line is that had we been more thorough in our reading and briefing of the green pages; this event never would have happened. A large contributing factor to this was that; at altitude; we did not brief a visual to runway 35. I have never flown an approach to runway 35 and have always thought of it as the runway they use for the rj's. We were briefed and up to speed for the 34's. Further; kind of late in the arrival; the controller cleared us to a fix to intercept the localizer for 'ILS 35'. We could not find that in our jepps; so I told her that all we had was the localizer type directional aid (lda) for 35. She said ok cleared to intercept the localizer for the lda. And so commenced a rushed briefing followed by the runway change items on the checklist.the best thing that can be done to prevent this from happening again is to have a FMS fix at zzzzz. A note on the flight plan for ZZZ that give pilots a heads up for runway 35 might also be appropriate. On a personal note; at top of descent I felt completely up to speed. It was a beautiful VFR day and 'I assumed' that of course we would be landing on one of the 34's. There is just so substitute for skepticism and a complete thorough briefing.

Google
 

Original NASA ASRS Text

Title: B757 flight crew was cleared for a visual approach; but to track the offset localizer. In an attempt to satisfy stabilized approach criteria; the pilot flying deviated off the localizer in order to align with the runway prior to 1000 feet (which is not required on an offset approach). This deviation caused a conflict with an aircraft on an adjacent runway. When prompted by ATC; the crew rejoined the localizer and landed uneventfully.

Narrative: We were cleared the visual approach Runway 35; track the localizer in to ZZZZZ. It is an offset localizer. The ZZZZZ fix is not in the FMS. It is about 2 NM from the end of the runway at approximately 700 feet. At 1300 feet AGL the 'track the localizer to ZZZZZ' dropped out of my brain and I prioritized to the Stabilized Approach criteria. I told the First Officer to start moving to the center line of the runway so we could be lined up by 1000 feet. As we did so; Tower told us to come back right to get back on the localizer. He asked us if we could see the traffic to our left for Runway 34R. I could not see the traffic. In the later phone call with the Approach controller; he said it was an RJ that was behind us and that they were keeping us in sight. After a few moments of tracking the localizer; Tower cleared us to go ahead and come left to line up with the runway. We landed without incident. There is a note on the Green page to not do the maneuver we did and that Stabilized Approach criteria could be deviated from because of the offset approach. We did brief from the Missed App/Rejected landing table on page 10-7E but completely missed the paragraphs about the Visual Approach to 35 on 10-7C. While there are contributing factors to this deviation; the bottom line is that had we been more thorough in our reading and briefing of the Green pages; this event never would have happened. A large contributing factor to this was that; at altitude; we did not brief a visual to Runway 35. I have never flown an approach to Runway 35 and have always thought of it as the runway they use for the RJ's. We were briefed and up to speed for the 34's. Further; kind of late in the arrival; the controller cleared us to a fix to intercept the localizer for 'ILS 35'. We could not find that in our Jepps; so I told her that all we had was the Localizer Type Directional Aid (LDA) for 35. She said OK cleared to intercept the localizer for the LDA. And so commenced a rushed briefing followed by the runway change items on the checklist.The best thing that can be done to prevent this from happening again is to have a FMS fix at ZZZZZ. A note on the Flight Plan for ZZZ that give pilots a heads up for Runway 35 might also be appropriate. On a personal note; at Top of Descent I felt completely up to speed. It was a beautiful VFR day and 'I assumed' that of course we would be landing on one of the 34's. There is just so substitute for skepticism and a complete thorough briefing.

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.