Citation flight crew reported flying a visual approach aligning to the wrong runway resulting in a go around and landing safely on the second approach.
Synopsis
Citation flight crew reported flying a visual approach aligning to the wrong runway resulting in a go around and landing safely on the second approach.
Narrative
On the evening of Day 0 myself (pilot flying (PF)) and Captain (pilot monitoring (PM)) were given a go around as we approach Boston Logan International Airport; which resulted in a Possible pilot deviation. To begin; we left ZZZ at approximately airborne time of XA:35 and proceeded on route to BOS. Prior to intersection MERIT; we received a reroute to join Robuc3 Arrival; fly present heading with vectors to RUIZE; expect Runway 27. As pilot flying; my Captain (PM); proceeded to Load the Flight Management system with the arrival; and backed it up with the ILS to Runway 27. Once he has done that and verified all fixes; shortly after we were cleared direct RUIZE AND Descend via the arrival; which we did. Just shortly after intersection KRANN we were given a heading of 050 Degrees to fly and expect Runway 32. We requested to stay on the present Runway 27 because we had already briefed and were expecting Runway 27; but was told unless its operational reason we needed to switch to Runway 32. Which we were fine with; as pilot flying; my Captain quickly changed the runway configurations and verified our performance for landing on Runway 32 and loaded RNAV (GPS) 32. Once he completed that; I transferred controls to my Captain and began briefing the new runway assignment and approach. As I did so; we both agreed that the RNAV APPROACH to Runway 32 Final CRS 331 does not align with the runway heading of 321 degrees. We were both in agreement and understanding that we will need to side step in order to get align with Runway 32. However; as we were vectored and turned toward the airport environment we had the runway in sight that we thought was Runway 32 due to the lighting system of Runway 33L and the fact it was dusk created a misconception and 32 seemed not properly lit due to Runway 33L being so bright. Runway 32 was not seen from our angle on approach which allowed us to think 33L was the correct runway at this time. Due to this and being 10 NM; we couldn't manage to see Runway 32 in the dusk approach and the fact it was hazy. Once we turned and had the Environment in sight we were cleared for the visual; of which I proceeded to get myself aligned with the runway which in mind we thought was Runway 32. As we approach the runway approximately 2 NM away; we noticed someone was on the runway; due to their Nav lights and Anti collisions flickering. At this time; both the Captain and I realized we were aligned with the wrong runway and was about to let ATC know; however they requested for us to go around before we could say anything; Which we proceeded to do so. After executing the Go around; we were vectored back around for the same approach; this time the runway lights were more profound due to it being night fall and Runway 32 lights were more illuminated as before which allowed us to land on the intended runway. Had Runway 33L lights have been less intensified; I do believe this issue would have been avoided due to us being able to see the dim runway lights on 32. Going forward; the Captain and I have learned a valuable lesson over an easy mistake to be made. In the future; our briefing will be more methodical about runway selection and airport layout. Making sure we emphasize the importance of the runway and runway's lighting system as well if there are any other runways near each other that can be mistaken for the runway intended to be used. I do apologize for any inconvenience this may have caused in the flow of traffic or anyone involved. This has been a well lesson learned.
Second reporter narrative
[Report narrative contained no additional information.]
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.