As a former ATC type guy for 38 years, including some of those years at the world’s busiest airports at the time, I’m personally declaring this a total non event. Although there is a “technical” requirement to protect the runway regardless of how, in you wildest dreams there is no safety issue at the moment, these type events happen all the time…both by pilots, AND also by controllers. You’ve all either done them or had it done to you if you’ve been involved in this for a while. I know I’ve sure seen and done both in my 60+ years of aviation. Harrison ended up crossing the runway at the very far west end of the runway and the nearest aircraft was way, way back up towards the east end of the runway, over half a mile. Technically wrong, I guess, if anyone is watching. But the only other aircraft would have had eventually to run off the end of the 3600 foot runway to hit Harrison, and only if Harrison had stopped in the middle of the runway while crossing.
Now, the controller…or ATC. Harrison said, '“holding short of 25”. The controller then commited a big controller technique error by prefacing his desire for Harrison to Hold Short with the word “CONTINUE” That is a “no no” in the controller world if you do not wish someone to do something. A pilot hears continue, many times that is exactly what he/she will do. (The word “cleared” should never be used either except for takeoff and landing).
Now about communications. It is always the controller’s requirement to hear readbacks and correct them if necessary, not the pilot’s fault for reading back incorrectly (even though some pilots do have their head up their, well you know, when they should be listening up better). Our form of communications does not insure what the controller says will always be heard correctly. Controller responsibility is to insure what he/she says is understood either by readback or observing actions.
And…the radio is no time to be doing “head butting” whether it is done by the pilot or controller. So the controller’s , “you need to listen up” is totally not necessary for a professional controller to speak…or it’s just muscle flexing.
This event at a busy facility would have been an absolute non event. Somebody did an “I’m gonna tell on you” somehow. And last thing…as a controller I used to always say to my cohorts, “If you live (work) in a glass house, do not throw stones”…unless you think you will be the only controller in ATC to lead a life of ATC perfection.
And, the controller again…he heard Harrison say he was crossing. Well, did the controller do anything correctly to prevent this “technical” issue from happening, no. The controller should have, if he observed Harrison still not compromising the hold short lines, said, “Negative! Hold Short! Hold Short! Acknowledge!” That would have resolved the issue. Or if Harrison had already crossed the lines (although there was no safety issue at all) the controller, to cover his ass should have told the other aircraft to “Go Around, traffic is crossing the far end of the runway” That would have corrected it technically. An non issue! Now…back to my cup of coffee.