Date: 201605
Local time of day: 1201-1800
Location: FTW.Airport, TX
Light: Daylight
Aircraft: Bonanza 36
Flight plan: VFR
Flight phase: Landing
Airspace: Class D FTW
ATC / advisory: Tower FTW
Second aircraft: Small Aircraft
Reporter organization: Government
Reporter function: Local; Instructor
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Training / Qualification; Situational Awareness; Distraction
Second reporter function: Trainee
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Airport; Human Factors
Primary problem: Airport

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.


Second narrative: I was training on Local 1 when Aircraft X entered the Class D airspace from the northeast proceeding southwest. Aircraft X was instructed to join the right downwind for runway 34 and to widen his leg on the downwind. Aircraft X acknowledged the instructions; but continued towards a left downwind and crossed north of FTW midfield. Aircraft X was given number two in sequence for runway 34; issued traffic on Aircraft Y on base for the runway 35 and Aircraft Z two mile final; and instructed to continue on the downwind. Aircraft X advised that he did not have Aircraft Z insight; but will turn base to follow the aircraft ahead and to the left on final. Aircraft X was advised that the traffic insight was Aircraft Z that he needed to follow and was issued a landing clearance. Aircraft X was advised again that he was number two in sequence for the runway and to turn behind and follow Aircraft Z. Aircraft X acknowledged all instructions and appeared to be established on the final for runway 34. Drone [pilot] called FTW Tower with a one minute notification until launch time. I acknowledged the Drone's transmission and then advised the CIC that drone operations would be begin in one minute. I looked back out the window to see Aircraft X to appear slightly high for runway 34 as he was going to execute a long landing. Initially; I couldn't tell if he was aligned with runway 34 or taxiway Alpha. Just before Aircraft X came in contact with the surface I realized that Aircraft X was aligned with taxiway Alpha and not runway 34. I scanned taxiway Alpha to ensure no one was taxing and stated out loud that Aircraft X landed on taxiway Alpha and asked Ground Control to stop any aircraft taxing to Alpha. I instructed Aircraft X to stop/hold his position and that there had been a possible pilot deviation and asked Aircraft X if he had the number to call the tower. Aircraft X brought the plane to a stop and asked me to repeat what I said. I informed Aircraft X of a possible pilot deviation and that he had landed on taxiway Alpha. Aircraft X was instructed to call the tower upon parking and to contact Ground Control for taxi instructions to parking. Brighter; bolder markings to label Taxiway Alpha to distinguish it from Runway 16/34. A yellow letter 'A' in the run up areas or at each end of Taxiway Alpha that is big enough to see from the sky can be used to distinguish/label Taxiway Alpha.


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