Narrative:

I was the pm on a flight [to ZZZ]. After receiving vectors to the airport in ZZZ; and being placed on a right downwind; we were given a descent to 2500; and told to expect a short visual approach to runway xyl. We had the airport in sight; and began to configure. The controller have us our short base vectors and cleared us for the visual. We were configured and stable by 1000 feet. I observed the localizer begin to come in; and observed the first officer (first officer) flying a comfortable; stable approach; so I focused my attention more outside than inside as we turned a tight base to final. Once on final; I resumed my inside scan and noticed that we appeared well below the glideslope; but visual cues outside appeared normal. I looked back outside as we descended through about 300 feet and noticed 'xyc' on the pavement. My first officer noticed the numbers at the same time; and we realized we were lined up for the center runway. We executed a go around and followed tower instructions to climb to 3000 and turn to a 290 heading. Tower never made mention (presumably hadn't noticed) our error.the departure controller asked us the reason for the go around; and I felt (1) we were too busy at the moment to go into the full story and (2) it wasn't appropriate to broadcast our error over the frq; so I told him we were not stable. He apologized for the short approach; to which I assured him it wasn't his fault. A few minutes later; I did tell him we were lined up for the wrong runway; as I didn't feel it was appropriate to mislead him either.threats: we were given a short visual approach to the left runway from a right downwind. The approach end of runway xyc is about a mile closer than the approach end of runway xyl; and from a relatively low; close in base leg; we did not see it; and mistook the center for the left. Errors: obviously lining up on the center runway instead of the left runway was an error. Not recognizing the error sooner than 300 feet was part of the problem. We definitely had a confirmation bias when descending down final; as even though the GS was above us; we seemed to reason it away. The error was trapped; however; as we confirmed the correct runway by use of the runway markings.this was an eye-opening; one-off event for me. I've never lined up with the wrong runway in my 16 1/2 years here; and I've been to ZZZ countless times. In fact; we were doing this ZZZ turn after our ZZZ overnight the previous night. I consider myself very familiar with that airport; having gone there for a decade and a half. As the pm; I was obviously not as vigilant as was necessary to prevent such an error.

Related reports:

Google
 

Original NASA ASRS Text

Title: The Captain of a regional jet reported lining up on the wrong runway at an airport with multiple parallel runways. The error was discovered at approximately 300 feet above the ground and a missed approach was executed.

Narrative: I was the PM on a flight [to ZZZ]. After receiving vectors to the airport in ZZZ; and being placed on a Right Downwind; we were given a descent to 2500; and told to expect a short visual approach to Runway XYL. We had the airport in sight; and began to configure. The controller have us our short base vectors and cleared us for the visual. We were configured and stable by 1000 feet. I observed the localizer begin to come in; and observed the First Officer (FO) flying a comfortable; stable approach; so I focused my attention more outside than inside as we turned a tight base to final. Once on final; I resumed my inside scan and noticed that we appeared well below the glideslope; but visual cues outside appeared normal. I looked back outside as we descended through about 300 feet and noticed 'XYC' on the pavement. My FO noticed the numbers at the same time; and we realized we were lined up for the center runway. We executed a Go Around and followed tower instructions to climb to 3000 and turn to a 290 heading. Tower never made mention (presumably hadn't noticed) our error.The departure controller asked us the reason for the Go Around; and I felt (1) we were too busy at the moment to go into the full story and (2) it wasn't appropriate to broadcast our error over the frq; so I told him we were not stable. He apologized for the short approach; to which I assured him it wasn't his fault. A few minutes later; I did tell him we were lined up for the wrong runway; as I didn't feel it was appropriate to mislead him either.Threats: We were given a short visual approach to the left runway from a right downwind. The approach end of Runway XYC is about a mile closer than the approach end of Runway XYL; and from a relatively low; close in base leg; we did not see it; and mistook the Center for the Left. Errors: Obviously lining up on the Center runway instead of the Left runway was an error. Not recognizing the error sooner than 300 feet was part of the problem. We definitely had a confirmation bias when descending down final; as even though the GS was above us; we seemed to reason it away. The error was trapped; however; as we confirmed the correct runway by use of the runway markings.This was an eye-opening; one-off event for me. I've never lined up with the wrong runway in my 16 1/2 years here; and I've been to ZZZ countless times. In fact; we were doing this ZZZ turn after our ZZZ overnight the previous night. I consider myself VERY familiar with that airport; having gone there for a decade and a half. As the PM; I was obviously not as vigilant as was necessary to prevent such an error.

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.