Date: 201606
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Second aircraft: Helicopter
Reporter organization: Government
Reporter function: Other / Unknown
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Troubleshooting; Situational Awareness; Distraction
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I am reporting today because when I arrived back form break I witnessed a very unsafe operation followed by a runway incursion by a coworker who has continually had several runway incursions and routinely does unsafe operations at ZZZ. (Controller has already had this exact runway incursion situation where Controller changed someone to runway 25R with someone landing simultaneously on the crossing runway 19R runway in the recent past.)My role in this situation was to relieve this Local 1 controller from the Local 1 position I was not actually on a position yet.When I arrived upstairs I looked out the window to see Aircraft X angled on a very unstable approach on a 2 1/2 mile final to runway 25L. The LC1 controller (LC) had the aircraft doing an extreme S turn for spacing but didn't request it until Aircraft X was very late and low in the aircraft's approach to get it. Then Controller asked the pilot to change to the parallel runway on a mile and a half final which was also unsafe choice instead of executing standard go around instructions. I observed the assist controller point to the aircraft landing on the crossing runway; Aircraft Y; and he advised Controller not to change Aircraft X's runway there wasn't enough spacing and could result in sending Aircraft Y around. LC argued responding 'I have the spacing I got this I'm landing'. Even the Local 2 controller advised Controller he had Aircraft Y on a 2 mile final and it would not work. Again Controller argued with fellow controller and said aircraft was landing. Controller then hit the runway intersecting device light before Aircraft X had even put all of its wheels down on the runway which was an illegal operation like that made it ok. Controller did not issue exiting instructions to the Aircraft X prior to giving the green light to the other local controller so he could land. Against local procedures and against the 7110.65. Aircraft X was clearly still loudly hitting the brakes down runway 25R when the crossing runway Aircraft Y crossed landing threshold.It was a poor decision to S turn the aircraft on such a short final and a poor decision to offer him the parallel runway. Controller had several more experienced controllers advising that it WAS NOT GOING TO WORK and yet Controller argued with each one of them; displaying a very poor attitude and going against their recommendations.I have personally witnessed this individual have 3 runway incursions (even more that I haven't been witness to) within the last year and each time Controller's allowed to return to working position right away and does not receive any remedial training prior to returning to position and continues to make poor decisions the rest of the day and week.I recommend that management provide training and guidance before Controller is allowed to return to working primary local positions and continuing with runway incursions; bad judgments and bad attitude.




Synopsis: Tower Controller reported a loss separation that could have been avoided if the Local Controller would have listened to others in the cab. Converging runway operation was done incorrectly causing an unsafe situation. Reporter questioned the Local Controller's training.