Narrative:

Aircraft X called inbound from the southeast requesting to land on the north runway (runway 7L) for north parking. He was told to make right traffic for runway 7R. There was aircraft Y already in the pattern making right traffic for runway 7R doing touch-and-goes. Aircraft Y was instructed to follow aircraft X in right traffic. The coordination was made with the local north controller for aircraft X to land on runway 7L and to continue in right traffic. Aircraft X was instructed to continue right traffic and change to runway 7L; the readback was correct. Aircraft X was told to contact the north local controller on 120.2. Aircraft Y was cleared for touch and go on runway 7R and in a separate transmission the traffic on right base for runway 7L (aircraft X) was issued and traffic was reported in sight. I observed aircraft X turning final and it appeared from that distance that they were aligned for runway 7L. Upon a scan of my runway a short time later I observed an aircraft touching down on my runway that did not resemble the paint scheme that I am familiar with on aircraft Y. I did not have any other aircraft on my board as aircraft Y was number one in my sequence. I quickly scanned up towards my final and saw that aircraft Y was on approximately one-half mile final. I quickly coordinated on the line to the north controller that they could exit my runway with aircraft X so they knew that I was aware of their aircraft. Aircraft X continued down the runway to taxiway B9 because they wanted north parking. Due to this long landing roll out there was not sufficient spacing for aircraft Y to do their touch and go so that aircraft was instructed to go around while they were still on final. The go around was executed without incident and normal operations resumed from this point. I'm not sure what else we could improve on to prevent this from happening. I observed aircraft X turning final and it appeared from my view that it looked like they were north of the 7R centerline. I could not hear what the north controller's frequency was like; however; it seems as if a correct instruction and readback for a landing on runway 7L occurred. I issued traffic to aircraft Y and since they had the other aircraft in sight they did not put themselves in any potential direct conflict which could have made this situation more significant. This allowed for enough spacing to be created on final that even in the event that one aircraft landed on the wrong runway; there was still more than plenty of time to react and avoid an incident. I am not sure what would cause a pilot requesting a certain runway; and being given the runway they suggested; to land on the runway that they did not want to land on in the first place.

Related reports:

Google
 

Original NASA ASRS Text

Title: DVT Local Controllers reported an aircraft landed on the wrong runway. An aircraft on final approach was sent around as a result.

Narrative: Aircraft X called inbound from the southeast requesting to land on the north runway (runway 7L) for north parking. He was told to make right traffic for Runway 7R. There was Aircraft Y already in the pattern making right traffic for runway 7R doing touch-and-goes. Aircraft Y was instructed to follow Aircraft X in right traffic. The coordination was made with the local north controller for Aircraft X to land on Runway 7L and to continue in right traffic. Aircraft X was instructed to continue right traffic and change to runway 7L; the readback was correct. Aircraft X was told to contact the north local controller on 120.2. Aircraft Y was cleared for touch and go on Runway 7R and in a separate transmission the traffic on right base for Runway 7L (Aircraft X) was issued and traffic was reported in sight. I observed Aircraft X turning final and it appeared from that distance that they were aligned for runway 7L. Upon a scan of my runway a short time later I observed an aircraft touching down on my runway that did not resemble the paint scheme that I am familiar with on Aircraft Y. I did not have any other aircraft on my board as Aircraft Y was number one in my sequence. I quickly scanned up towards my final and saw that Aircraft Y was on approximately one-half mile final. I quickly coordinated on the line to the north controller that they could exit my runway with Aircraft X so they knew that I was aware of their aircraft. Aircraft X continued down the runway to taxiway B9 because they wanted north parking. Due to this long landing roll out there was not sufficient spacing for Aircraft Y to do their touch and go so that aircraft was instructed to go around while they were still on final. The go around was executed without incident and normal operations resumed from this point. I'm not sure what else we could improve on to prevent this from happening. I observed Aircraft X turning final and it appeared from my view that it looked like they were north of the 7R centerline. I could not hear what the north controller's frequency was like; however; it seems as if a correct instruction and readback for a landing on runway 7L occurred. I issued traffic to Aircraft Y and since they had the other aircraft in sight they did not put themselves in any potential direct conflict which could have made this situation more significant. This allowed for enough spacing to be created on final that even in the event that one aircraft landed on the wrong runway; there was still more than plenty of time to react and avoid an incident. I am not sure what would cause a pilot requesting a certain runway; and being given the runway they suggested; to land on the runway that they did not want to land on in the first place.

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.