Medium Large Transport
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (mon) 6
Communication Breakdown; Distraction; Workload; Situational Awareness; Time Pressure
ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Rejected Takeoff; General Flight Cancelled / Delayed
Human Factors; Procedure
I was working Local Control north flow; taxiway closures making K8; Y; EG; and EF the only crossing points for Runway 35L; Land and Hold Short Operations (LAHSO) not available due to wet runway; arrivals to Runway 35C coordinated at 5 miles; between 3-4 miles at the threshold. FLM was standing next to me giving me advice on how to run/cross arrival traffic. This in addition to all the closures and attempting to cross aircraft across Runway 35C between arrivals without being able to use LAHSO proved a distraction which led me to miss Aircraft X which was inside the Converging Runway Operations (CRO) Arrival Departure Window (ADW) for Runway 31R. I issued a takeoff clearance to Aircraft X; which the Front Line Manager (FLM) immediately told me to cancel. I cancelled the takeoff clearance for Aircraft X twice; and believed he had understood the cancellation because the aircraft appeared stationary. I then cancelled the takeoff clearance a total of 2 more times before the pilot finally rejected takeoff near Taxiway B. Aircraft X ended up taxiing back for departure without incident.I recommend that the FLM during periods of busy traffic to not try to 'coach' the controller; and while they are monitoring to look out for incorrect read backs. The FLM was giving suggestions regarding my traffic that I took to be instructions; which led to a loss of situational awareness and the issuance of an incorrect heading. If the FLM is going to be involved; I would prefer they work as an assist; keeping up the pad and listening for read backs; vs giving instructions that end up becoming a distraction to the controller. In my opinion the FLM would be better used as an actual assist during busy periods; if they are going to be that involved with Local Control's traffic; if not acting as an assist; they should stay out and only offer input in the case of a pilot error that the controller hasn't corrected.
Cleared for takeoff on Runway 35L with the First Officer flying. Started takeoff roll; called thrust set; prior to 80 knots Tower instructed us to stop our takeoff and rescinded our takeoff clearance. We exchanged aircraft control and exited the runway. We stopped on Taxiway M after exiting the runway to the east as directed. We reviewed the requirements in part 1. I called the Maintenance Operations and Duty Manager (MOD) and sought advice. He agreed that we were clear to go. We decided to continue and return to the runway as the reject had happened below 80 knots. Brake temperatures were normal; reaccomplished checklists. Departed without incident.Tower told us that there was an aircraft in conflict on approach to Runway 31R and apparently did not consider that prior to giving us takeoff clearance.Both Ground and Tower were very busy. I think this was a mistake made by hurrying in the Tower. No harm no foul.
DFW Local Controller and flight crew reported a rejected takeoff due to ATC cancelling takeoff clearance for traffic.