Date: 201810
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
Second aircraft: B737-800
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi; In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Issued New Clearance; Flight Crew Rejected Takeoff; Flight Crew Returned To Gate
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Half of our airport in under construction. This has led to complicated taxi routes and more runway crossings than necessary. We are using mainly one runway and having to hit gaps with most of our departures and arrivals. An Airport vehicle was inspecting the runway for a bird strike. I had a Aircraft X on a four mile final and I observed  the Airport Vehicle clearing the runway; which was confirmed on frequency. I cleared Aircraft Y for takeoff with traffic on a four mile final. Ground control had told Aircraft X to 'Continue via Charlie; cross Runway 28.' The pilot read this back correctly. Aircraft X; I observed at a high rate a of speed continuing on Juliet; not turning onto Charlie to cross the active runway 1R while Aircraft Y was rolling to depart. Cab coordinator; Ground control and I on local control acted quickly. I transmitted 'STOP; STOP; STOP!' on frequency; first calling the [transposed call signs] but then used the correct call sign quickly 'Aircraft Y STOP STOP STOP!'Aircraft Y stopped prior to runway 10/28; I sent the aircraft on final around; and Aircraft X stopped before his nose wheel crossed the hold short markings of 1R. Because of the tower teams quick reactions a runway incursion or tragic event did not happen. The supervisor put [a report] in stating fault in the controllers. He inputted his opinion that with the Ground controller not saying 'Turn right on Charlie' that it was a main contributing factor to the pilots error. Also; I did not say 'Abort Takeoff' which the correct phraseology is 'Cancel takeoff' and that I did not issue the brasher statement and only gave the phone number. The [reports] are for facts; not opinions. Ground control is not required to say left; right or straight ahead.In the 7110.65 it also states you can use plain language to get your point across and 'Stop; stop; stop;' will get everyone's' attention. He also put the aircraft was at V1 rotation. This is incorrect. Aircraft Y was told to stop near C3 and stopped prior to Runway 10/28 which is before taxiway Juliet where the Aircraft X was attempting to cross. Runway 10/28 from Runway 1R is less than 2000 feet. How the supervisor worded the [report] places fault in the controllers when this was a pilot deviation. It is a sad thing when your 'Superiors' throw you under the bus instead of saying; you did your job and averted a potentially devastating situation. Controllers did our job. This is terrible management that we have to work under everyday by the same offenders.


Second narrative: We were cleared for takeoff. At approximately 65 knots; Tower instructed us to reject the takeoff and stop the aircraft. We did the rejected takeoff procedure; pulled off the runway; and completed the brake cooling requirements. No extra brake cooling was needed. Tower advised us it was due to a possible runway incursion. We notified Dispatch. Due to the rejected takeoff; we had less fuel on board than the minimum fuel for takeoff on our release. We returned to the gate; refueled; and departed uneventfully.


Synopsis: Local Controller and an air carrier Captain reported a runway incursion resulted in the departure flight crew rejecting take-off.