Narrative:

I was working local control (local control) in multi-sensor mode. Radar was being lost at a 2-3 mile final. About 15-20 minutes after being on position; aircraft X checks in on a right base for runway 10R. I cleared aircraft X to land runway 10R. Aircraft Y; calls up ready to depart runway 10L. I lost aircraft X on radar. I asked him to say position. Aircraft X reported to be on a two mile final. My controller in charge and I start looking for him out the window. We both got aircraft X in sight; it appeared he was lined up for runway 10R. I told aircraft X that traffic is departing runway 10L. He acknowledged. I cleared aircraft Y for takeoff runway 10L. At that moment I realized that aircraft X was landing runway 10L. Aircraft Y keyed up and said he was going to delay his takeoff because someone was landing runway 10L. I cancelled his takeoff clearance. At that point aircraft X apologized and I told him possible pilot deviation and gave him the phone number. I continued on position for about another hour and a half. The supervisor came up and issued me paperwork to fill out a statement. He said he had reviewed the tapes and then started debating about whether I was in the right or the wrong for about 5-10 minutes. This event happened because we have parallel runways 700 ft apart. It is extremely hard to distinguish what runway aircraft are lined up for. Another factor that led to this error is that we were in multi-sensor mode and I didn't have radar coverage to aid me. The pilot was also at fault for landing on the wrong runway. If this event were to happen again; I could wait until aircraft X is on the ground before launching someone from another runway. I could also reiterate if the pilot has the numbers for runway 10R in sight.

Related reports:

Google
 

Original NASA ASRS Text

Title: PBI Local Controller reported a pilot landed on a parallel runway in error which a departing aircraft did not enter because that pilot saw the approaching aircraft. The parallel runways are 700 feet apart so the Controller could not see the aircraft's track deviation visually and the Tower radar lost traffic inside a 2-3 mile final.

Narrative: I was working Local Control (LC) in multi-sensor mode. Radar was being lost at a 2-3 mile final. About 15-20 minutes after being on position; Aircraft X checks in on a right base for runway 10R. I cleared Aircraft X to land runway 10R. Aircraft Y; calls up ready to depart runway 10L. I lost Aircraft X on radar. I asked him to say position. Aircraft X reported to be on a two mile final. My CIC and I start looking for him out the window. We both got Aircraft X in sight; it appeared he was lined up for runway 10R. I told Aircraft X that traffic is departing runway 10L. He acknowledged. I cleared Aircraft Y for takeoff runway 10L. At that moment I realized that Aircraft X was landing runway 10L. Aircraft Y keyed up and said he was going to delay his takeoff because someone was landing runway 10L. I cancelled his takeoff clearance. At that point Aircraft X apologized and I told him possible pilot deviation and gave him the phone number. I continued on position for about another hour and a half. The supervisor came up and issued me paperwork to fill out a statement. He said he had reviewed the tapes and then started debating about whether I was in the right or the wrong for about 5-10 minutes. This event happened because we have parallel runways 700 ft apart. It is extremely hard to distinguish what runway aircraft are lined up for. Another factor that led to this error is that we were in multi-sensor mode and I didn't have radar coverage to aid me. The pilot was also at fault for landing on the wrong runway. If this event were to happen again; I could wait until Aircraft X is on the ground before launching someone from another runway. I could also reiterate if the pilot has the numbers for Runway 10R in sight.

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.