Narrative:

Aircraft X checked in; and was cleared for RNAV zulu runway 35R approach. Pilot read back approach clearance correctly I slowed aircraft to 190 KTS to keep separation as aircraft X was in trail of two other aircraft on [rnp] approaches. Winds were strong out of the south at altitude and needed to control speeds on the downwind and base legs of the approaches. It appeared aircraft X was turned in to join the final and so I instructed aircraft X to contact tower on 133.3. The pilot replied with 'verify runway 35R' at which point I stated 'yes; runway 35R and recognized that the aircraft was heading due west bound and not turning onto the final. The controller next to me (working flight radar 1) had two aircraft and it appeared that aircraft X was now going to conflict with both of those aircraft; so he issued traffic and was able to get aircraft X in sight. I then reached out to aircraft X and instructed the pilot to turn due northbound to try and avoid a conflict with the aircraft on runway 34R. The flight radar 1 controller issued traffic again and once aircraft X was in the turn - I instructed him to climb to get out of the way. Then re-vectored pilot for visual approach to runway 35R.aircraft y- aircraft that was on final for runway 35L was issued traffic and saw aircraft X. Due to aircraft's TCAS; pilot had to initiate a rapid descent which contributed to the aircraft being much lower than aircraft X. If pilot is confused; they need to clarify which runway well before the position the aircraft was in. I observed aircraft X on a heading turning in; when in reality they turned more westerly after questioning which runway they were going to. Not sure why a pilot would think they were going to cross over 2 different finals to go to a runway on the west side of the airport...; which appeared to be what they were doing.procedural: we have maps that show the exact RNAV path that each aircraft is supposed to be flying depending on which runway they are going to - there are slight variations with the turns to join the finals depending on which runway is assigned - and had I been working with this map displayed (although this is not a requirement) I would definitely have noticed that aircraft X was not turning in to the correct runway. I will be working with this map displayed on my scope from now on. This should probably become a requirement for all controllers.

Related reports:

Google
 

Original NASA ASRS Text

Title: Denver Approach Controller and four pilots reported that an aircraft went through assigned final course causing an airborne conflict with two other aircrafts.

Narrative: Aircraft X checked in; and was cleared for RNAV Zulu Runway 35R approach. Pilot read back approach clearance correctly I slowed aircraft to 190 KTS to keep separation as Aircraft X was in trail of two other aircraft on [RNP] approaches. Winds were strong out of the south at altitude and needed to control speeds on the downwind and base legs of the approaches. It appeared Aircraft X was turned in to join the final and so I instructed Aircraft X to contact tower on 133.3. The pilot replied with 'Verify Runway 35R' at which point I stated 'Yes; Runway 35R and recognized that the aircraft was heading due west bound and not turning onto the final. The controller next to me (working Flight Radar 1) had two aircraft and it appeared that Aircraft X was now going to conflict with both of those aircraft; so he issued traffic and was able to get Aircraft X in sight. I then reached out to Aircraft X and instructed the pilot to turn due northbound to try and avoid a conflict with the aircraft on Runway 34R. The Flight Radar 1 controller issued traffic again and once Aircraft X was in the turn - I instructed him to climb to get out of the way. Then re-vectored pilot for visual approach to Runway 35R.Aircraft Y- aircraft that was on final for Runway 35L was issued traffic and saw Aircraft X. Due to aircraft's TCAS; pilot had to initiate a rapid descent which contributed to the aircraft being much lower than Aircraft X. If pilot is confused; they need to clarify which runway well before the position the aircraft was in. I observed Aircraft X on a heading turning in; when in reality they turned more westerly after questioning which runway they were going to. Not sure why a pilot would think they were going to cross over 2 different finals to go to a runway on the west side of the airport...; which appeared to be what they were doing.Procedural: We have maps that show the exact RNAV path that each aircraft is supposed to be flying depending on which runway they are going to - there are SLIGHT variations with the turns to join the finals depending on which runway is assigned - and had I been working with this map displayed (although this is not a requirement) I would definitely have noticed that Aircraft X was not turning in to the correct runway. I will be working with this map displayed on my scope from now on. This should probably become a requirement for all controllers.

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.