Narrative:

I was conducting training on the local 1 position. I observed the trainee enquire about what was going on with aircraft X/BE36 who hadn't call but was in our airspace 3.5 nne of ftw. Aircraft X checked in 2 north of the airport landing RY34. The trainee instructed aircraft X to widen out their right downwind for RY34. Aircraft X flew through the departure corridor of RY34 and entered the left downwind at which time the trainee enquired as to what aircraft X was doing. The only traffic involved was aircraft Y ahead on the downwind for RY35 of aircraft X and aircraft Z on a 2 mile final. The trainee pointed out aircraft Z on a 2 mile final for RY34 to follow and to continue downwind. The trainee issued touch and go clearance on RY35 to aircraft Y and again issued sequence to aircraft X to follow aircraft Z now on a mile final. Aircraft X indicated they were turning base but there was traffic on a mile final. The trainee informed aircraft X that that was aircraft Z he was to follow. Aircraft X acknowledged sequence to follow aircraft Z; who was doing a touch and go on RY34. A uas pilot called indicating they were one minute from their operations and the trainee acknowledged and requested to advise when terminating operations. The trainee along with myself scanned to ensure runway spacing was adequate (which there was) with aircraft Z doing a touch and go and aircraft X who appeared to be on a half mile final lined up with the RY34. My trainee and I scanned RY35 to check the location of aircraft Y which caused us to turn away from RY34. I updated my pad when my trainee; who turned to check where aircraft X was before me; mentioned 'did that bonanza just land on taxiway alpha!' at which point I looked and observed aircraft X rolling out on taxiway alpha north of alpha six. My trainee advised aircraft X twice to hold position that he had just landed on taxiway alpha and of possible pilot deviation. The trainee then switched aircraft X to ground control and informed aircraft X they would give the phone number to call.this is not the first time a pilot has mistaken taxiway alpha for a runway. Since the construction of taxiway alpha this has occurred. The facility and the airport have tried to solve this problem from renaming 16L/34R and 16R/34L to 16/34 and 17/35; to painting 'T a X I west a Y' on taxiway alpha; to placing large ' X's ' off each end of taxiway alpha; to conducting pilot briefings; informing pilots who question which one is the runway that 'it's the one with the square end' and it still happens. In this case and I believe every other case; nothing was on taxiway alpha when this occurs.I'm not sure there is much else we can do to keep a pilot from landing on a taxiway that look just like a runway.

Related reports:

Google
 

Original NASA ASRS Text

Title: FTW Tower Local Instructor and Developmental reported an aircraft landed on a taxiway instead of the runway.

Narrative: I was conducting training on the Local 1 position. I observed the trainee enquire about what was going on with Aircraft X/BE36 who hadn't call but was in our airspace 3.5 NNE of FTW. Aircraft X checked in 2 north of the airport landing RY34. The trainee instructed Aircraft X to widen out their right downwind for RY34. Aircraft X flew through the departure corridor of RY34 and entered the left downwind at which time the trainee enquired as to what Aircraft X was doing. The only traffic involved was Aircraft Y ahead on the downwind for RY35 of Aircraft X and Aircraft Z on a 2 mile final. The trainee pointed out Aircraft Z on a 2 mile final for RY34 to follow and to continue downwind. The trainee issued touch and go clearance on RY35 to Aircraft Y and again issued sequence to Aircraft X to follow Aircraft Z now on a mile final. Aircraft X indicated they were turning base but there was traffic on a mile final. The trainee informed Aircraft X that that was Aircraft Z he was to follow. Aircraft X acknowledged sequence to follow Aircraft Z; who was doing a touch and go on RY34. A UAS pilot called indicating they were one minute from their operations and the trainee acknowledged and requested to advise when terminating operations. The trainee along with myself scanned to ensure runway spacing was adequate (which there was) with Aircraft Z doing a touch and go and Aircraft X who appeared to be on a half mile final lined up with the RY34. My trainee and I scanned RY35 to check the location of Aircraft Y which caused us to turn away from RY34. I updated my pad when my trainee; who turned to check where Aircraft X was before me; mentioned 'did that bonanza just land on taxiway alpha!' at which point I looked and observed Aircraft X rolling out on taxiway alpha north of alpha six. My trainee advised Aircraft X twice to hold position that he had just landed on taxiway alpha and of possible pilot deviation. The trainee then switched Aircraft X to ground control and informed Aircraft X they would give the phone number to call.This is not the first time a pilot has mistaken taxiway alpha for a runway. Since the construction of taxiway alpha this has occurred. The facility and the airport have tried to solve this problem from renaming 16L/34R and 16R/34L to 16/34 and 17/35; to painting 'T A X I W A Y' on taxiway alpha; to placing large ' X's ' off each end of taxiway alpha; to conducting pilot briefings; informing pilots who question which one is the runway that 'IT'S THE ONE WITH THE SQUARE END' and it still happens. In this case and I believe every other case; NOTHING was on taxiway alpha when this occurs.I'm not sure there is much else we can do to keep a pilot from landing on a taxiway that look just like a runway.

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.