Date: 201409
Local time of day: 0001-0600
Location: ONT.Airport, CA
Light: Night
Aircraft: Widebody; Low Wing; 3 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Other under tow
Airspace: Class C ONT
ATC / advisory: Tower ONT
Second aircraft: Small Transport
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Confusion; Communication Breakdown; Troubleshooting; Workload
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During the time of the event I was working ground control; there was training on local control; and a supervisor working the desk. Aircraft X requested push back and tow clearance to the guard ramp. I had no traffic on ground control so I approved the tow. A few minutes after I approved the tow a CFR [Call For Release] strip printed from the FDIO [Flight Data Input/Output] so I went to update the SIA [System Information Area]. At this time Aircraft X was established on taxiway Sierra and approaching Foxtrot from west to east. While I was updating the SIA the Local Controller (LC) turned Aircraft Y off runway 26L at Foxtrot. There was no traffic following Aircraft Y on final and there was only Aircraft Z holding short of runway 26L for departure.There was no imminent reason why the LC couldn't have either turned Aircraft Y of the runway at the end at taxiway Sierra or took the aircraft to the north side of the airport. The LC also admitted he saw the aircraft under tow and still turned the aircraft off at taxiway foxtrot. The trainer had his back turned to the west and was facing east and didn't see the aircraft under tow. I believe because the majority of the time [we] turn aircraft of at taxiway Foxtrot especially Aircraft Y type; neither the trainer or the supervisor was on alert and both of them had there backs turned. During the time I was updating the board Aircraft Y called for taxi to parking. When I looked up; Aircraft Y was on taxiway foxtrot short of taxiway Sierra facing south. I immediately reached out to Aircraft X and instructed them to hold position. I informed both LC and the supervisor of the impeding situation. I looked at locals traffic to see if maybe we could turn Aircraft Y back onto the runway to avoid Aircraft X but LC had already cleared Aircraft Z for takeoff. Concurrently; Aircraft X read back 'Roger; hold short of foxtrot.' I immediately responded negative; hold position. Aircraft X kept moving and pushed passed foxtrot and held short of foxtrot on the east side. When Aircraft X passed foxtrot; Aircraft X's wing passed above Aircraft Y. Aircraft Y reported on frequency that the Aircraft X's wing cleared her aircraft by only 3 feet. I informed the supervisor who was also monitoring ground and local frequencies; and I asked her to file an MOR. The supervisor told me a MOR did not need to be filed. I also asked the supervisor if I needed to file a report and she said no because this was not a reportable event. Two days later the supervisor informed me that she had to file an MOR and that I should file a report. I informed her that at the time I didn't realize that there was a runway incursion because Aircraft Z departed and Aircraft Y was not pass the hold bars. She said there was no runway incursion because Aircraft Y crossed the runway edge (white line) and the aircraft is small enough to fit between the runway edge and taxiway Sierra. I would recommend that all parties involved would pay closer attention to the operation as a whole. I believe that the problem was created by LC. Had the trainer been paying attention; I believe he would have instructed the trainee to turn the aircraft off at the end reference Aircraft X and there wouldn't have been an issue at all.




Synopsis: ONT Tower Controller describes a situation where an aircraft under tow was told to stop; but reads back different instructions. As a result; the aircraft ended up being towed over a smaller aircraft and missing it by three feet.