Date: 201708
Local time of day: 1801-2400
Location: HPN.Airport, NY
Aircraft: Challenger 300
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Flight phase: Landing
ATC / advisory: Tower HPN
Second aircraft: DA40 Diamond Star
Reporter organization: Government
Reporter function: Local; Trainee
Reporter qualification: Air Traffic Control Developmental
Human factors: Time Pressure; Situational Awareness; Distraction
Second reporter function: Flight Data / Clearance Delivery; Supervisor / CIC
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: In-flight; Taxi
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was training on Local Control; during a busy VFR Friday afternoon. I started falling behind and the On the Job Training Instructor took over the frequency. I continued to assist by managing the strip-board and making rolling calls. Aircraft Y was landing RWY 11; with Aircraft X landing shortly thereafter on RWY 16. Aircraft Y types are normally very slow; with short landing distances; usually able to exit TWY F (1;200 feet); and at most to reach taxi speed and hold short of RWY 16 (2;500 feet). With this preceding experience; it was anticipated that Aircraft Y would be clear of RWY 11 or given taxi-speed hold instructions prior to Aircraft X occupying RWY 16. While Aircraft Y's approach and touchdown appeared normal; it continued down the runway at a higher than expected speed. Aircraft Y advised it was unable to make TWY L (2;500 feet; just prior to the RWY 16 hold line). Aircraft X was able to slow and exit before the RWY intersection. Aircraft Y was able to exit TWY H; inside the RWY intersection.Always have a plan in the event aircraft to not perform the way you expect them to; which still ensures separation. Land and Hold Short Operations; go-around; turns for re-sequencing are a few of the tools one could use.


Second narrative: I was working Clearance/Flight Data and Controller In Charge when the incident occurred. The tower controller gave Aircraft Y a landing clearance with hold short instructions for Runway 11. Aircraft Y accepted the landing clearance but never read back the hold short instructions. During that time the volume of traffic was high and pilots were stepping on each other to either check in or to ask about their sequence. Aircraft X was on final for runway 16. Both aircraft landed and Aircraft Y on runway 11 and Aircraft X on runway 16. Once Aircraft Y was on taxi speed the controller instructed to hold short of the other runway where Aircraft X was also at taxi speed. Aircraft Y replied unable and went passed the hold short lines and immediately the controller asked Aircraft X if he was able to hold short of Runway 11. Aircraft X was able to exit the runway before the intersection. Unfortunately we work at an airport that people are not accustomed to waiting therefore are constantly asking why the delays; what sequence are they in regards to other airplanes either in front or at the adjacent taxiway etc. complicating and increasing the work load because we now have to give an estimate of time while there are other VFR pilots inbound that need to be radar identified.


Synopsis: HPN controllers reported an unsafe operation when a landing aircraft was asked to hold short of an intersecting runway and could not resulting in a ground conflict.