Narrative:

We were on the RNAV arrival; and were initially told to expect the ILS xxr with a 15 mile final. We requested an arrival on [runway] xyl due to proximity to parking and were told that it would be unable. I had manually pre-tuned both localizer frequencies for [runway] xxr (in active) and [runway] xyl (in standby) in preparation for either approach.on the downwind leg; descending to an assigned 3;000 feet; approach said they could offer us [runway] xyl if we were able to 'expedite down to 3;600 feet.' my copilot; in an unfortunate non-standard fashion; stated that we would be able to accept an expedited descent. However; my copilot failed to read back that we were now to still descend to 3;000 ft and expedite down through 3;600 feet; as we had understood the clearance to mean. The last clearance limit we had received was descend to 3;000 feet; and the controllers request was that we 'expedite to 3;600 feet' not 'descend and maintain 3;600 feet.'we passed through 3;600 feet and at approximately 3;300 feet; the controller admonished us stating that we were supposed to maintain 3;600 feet; and to level off immediately. This took us by surprise; since our clearance limit had been 3;000 feet. We leveled off at 3;000 feet and were then given a traffic call for aircraft inbound on the ILS xxr. We started to receive vectors for [runway] xyl; and it was becoming more clear that we were being vectored in very tight and high. I reminded my copilot to please update the approach and runway to [runway] xyl in the FMS; as I was slowly beginning to lose situational awareness.we then received a turn to intercept to localizer on [runway] xyl. I looked down and the box was now incorrectly set for [runway] xyr. I quickly noted to my copilot that the incorrect runway had been set again and to change it. I had remembered that I had pre-tuned the localizer frequency into NAV1; so I switched my nav data from FMS to raw data; and picked up the localizer. We still had not yet been cleared for the approach and were high on the glideslope. I told my copilot we would need lower in order to accept the approach. Approach then immediately cleared us for the approach and told us to contact ZZZ tower.upon checking in with ZZZ tower; they queried if we were confirmed lined up for runway xyl. Being IMC; I noted that I had a centered localizer and had just caught the glideslope; and my FMS was showing runway xyl. However; I failed to notice that when the copilot accidentally selected [runway] xyr in the FMS; the system had autotuned to that localizer frequency; dumping out the xyl one I had previously manually pre-tuned. Once the copilot had corrected the error in the box; I had already selected raw data and it would not auto-tune to the new xyl frequency in this mode. This resulted in us displaying xyl on our nav screens with xyr localizer frequency tuned.we broke out of the clouds at 900 feet; and I immediately recognized we were lined up for [runway] xyr and not [runway] xyl. At this point; ZZZ tower advised it also appeared we were lined up for the incorrect runway and issued us a go-around instruction. My copilot noted that we were in process of lining up for [runway] xyl; and then confirmed that we were still cleared to land on [runway] xyl. The issue appears to have started snow balling with the query by ATC about our clearance to descend to 3;000 feet. The instructions to expedite were given in a non-standard fashion; and my copilot's response was also non-standard. This led to confusion in the cockpit. The tight turn just outside the FAF; last minute runway change; and mistakes loading the approach appropriately in the FMS resulted in us lining up on the xyr localizer even though our FMS was displaying xyl. There was a breakdown in communication with approach; and [also] between both crew members.upon landing; ZZZ tower requested that we call them on the landline and discuss. I spoke with personnel at ZZZ tower; [we] reviewed the entire approach; including how we mistakenly lined up for [runway] xyr. I told him I felt that we were given a series of quick changes and poor clearances on a very congested frequency. This led to us making a series of poor decisions and unfortunate mistakes. I could feel us slowly slipping behind the airplane; and I should have just broken off the approach entirely and requested new sequencing. Going forward; company sops; including using correct radio phraseology; and confirming changes in the FMS before executing them need to be reiterated and reinforced.

Google
 

Original NASA ASRS Text

Title: CL604 flight crew reported that mistakes loading the approach appropriately in the FMS resulted in lining up on the right localizer even though their FMS was displaying the left.

Narrative: We were on the RNAV arrival; and were initially told to expect the ILS XXR with a 15 mile final. We requested an arrival on [Runway] XYL due to proximity to parking and were told that it would be unable. I had manually pre-tuned both localizer frequencies for [Runway] XXR (in active) and [Runway] XYL (in standby) in preparation for either approach.On the downwind leg; descending to an assigned 3;000 feet; Approach said they could offer us [Runway] XYL if we were able to 'expedite down to 3;600 feet.' My copilot; in an unfortunate non-standard fashion; stated that we would be able to accept an expedited descent. However; my copilot failed to read back that we were now to still descend to 3;000 ft and expedite down through 3;600 feet; as we had understood the clearance to mean. The last clearance limit we had received was descend to 3;000 feet; and the controllers request was that we 'expedite to 3;600 feet' not 'descend and maintain 3;600 feet.'We passed through 3;600 feet and at approximately 3;300 feet; the controller admonished us stating that we were supposed to maintain 3;600 feet; and to level off immediately. This took us by surprise; since our clearance limit had been 3;000 feet. We leveled off at 3;000 feet and were then given a traffic call for aircraft inbound on the ILS XXR. We started to receive vectors for [Runway] XYL; and it was becoming more clear that we were being vectored in very tight and high. I reminded my copilot to please update the approach and runway to [Runway] XYL in the FMS; as I was slowly beginning to lose situational awareness.We then received a turn to intercept to localizer on [Runway] XYL. I looked down and the box was now incorrectly set for [Runway] XYR. I quickly noted to my copilot that the incorrect runway had been set again and to change it. I had remembered that I had pre-tuned the localizer frequency into NAV1; so I switched my nav data from FMS to raw data; and picked up the localizer. We still had not yet been cleared for the approach and were high on the glideslope. I told my copilot we would need lower in order to accept the approach. Approach then immediately cleared us for the approach and told us to contact ZZZ Tower.Upon checking in with ZZZ Tower; they queried if we were confirmed lined up for Runway XYL. Being IMC; I noted that I had a centered localizer and had just caught the glideslope; and my FMS was showing Runway XYL. However; I failed to notice that when the copilot accidentally selected [Runway] XYR in the FMS; the system had autotuned to that localizer frequency; dumping out the XYL one I had previously manually pre-tuned. Once the copilot had corrected the error in the box; I had already selected raw data and it would not auto-tune to the new XYL frequency in this mode. This resulted in us displaying XYL on our nav screens with XYR localizer frequency tuned.We broke out of the clouds at 900 feet; and I immediately recognized we were lined up for [Runway] XYR and not [Runway] XYL. At this point; ZZZ Tower advised it also appeared we were lined up for the incorrect runway and issued us a go-around instruction. My copilot noted that we were in process of lining up for [Runway] XYL; and then confirmed that we were still cleared to land on [Runway] XYL. The issue appears to have started snow balling with the query by ATC about our clearance to descend to 3;000 feet. The instructions to expedite were given in a non-standard fashion; and my copilot's response was also non-standard. This led to confusion in the cockpit. The tight turn just outside the FAF; last minute runway change; and mistakes loading the approach appropriately in the FMS resulted in us lining up on the XYR localizer even though our FMS was displaying XYL. There was a breakdown in communication with Approach; and [also] between both crew members.Upon landing; ZZZ Tower requested that we call them on the landline and discuss. I spoke with personnel at ZZZ Tower; [we] reviewed the entire approach; including how we mistakenly lined up for [Runway] XYR. I told him I felt that we were given a series of quick changes and poor clearances on a very congested frequency. This led to us making a series of poor decisions and unfortunate mistakes. I could feel us slowly slipping behind the airplane; and I should have just broken off the approach entirely and requested new sequencing. Going forward; Company SOPs; including using correct radio phraseology; and confirming changes in the FMS before executing them need to be reiterated and reinforced.

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.