Date: 201707
Local time of day: 1201-1800
Location: HPN.Airport, NY
Flight conditions: VMC
Weather elements / visibility: Cloudy
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower HPN
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Fractional
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe
Detector: Automation Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Separated Traffic; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Human Factors

Narrative: After cleared for the ILS approach to Runway 16 at HPN; we heard the tower call another aircraft and told him he was 2 in trail of our aircraft. That lead us to believe he was behind us by 2 miles. On very short final; like at the point we started our round out above the runway numbers; the controller said to exit Runway 11 and to expedite; no need to acknowledge. I did not answer at that point and we had to use our brakes and some thrust reverser to slow down enough to turn off at Runway 11. As we started our left turn; I heard the tower tell the aircraft that I thought was behind us to go around. I said out loud that she put him too close if he caught up to us. It wasn't until we cleared the runway and the FO stopped the aircraft and he said the aircraft that went around was on Runway 11. I could not believe the controller had an aircraft landing on a runway that we used to get off of. Tom called the tower on the landline and talked to the supervisor.I believe the tower made a bad decision and didn't use good communication techniques to advise us of the traffic using a crossing runway. I don't believe we would have done anything differently except I would go around if I knew traffic was that close to us on landing. It was poor judgement and bad communication by the tower and I believe they know that. Luckily there was no problem for anyone; but this report would not be written if better judgment was used by the tower. We are human and make some errors and she stayed on top of hers by telling the other aircraft to go around.


Second narrative: Upon landing on Runway 16 at HPN; the tower controller (who had a strong Latin accent) radioed the crew to 'do not acknowledge; exit Runway 16 at Runway 11; for landing traffic.' the crew complied; and turned left at the crossing runway (Runway 11). The tower then told the aircraft landing on Runway 11 to 'Go around.' The crew taxied the aircraft off of Runway 11 and then to the ramp without incident. The captain telephoned the tower after parking the aircraft; and was informed that the tower controller had meant to say 'Expedite through Runway 11 for landing traffic.' That is not what the crew heard! Tower apologized for the miscommunication; and the Captain apologized for the miscommunication. Captain was informed that no further action was needed; or would be taken.I feel this was an error on the towers part in clearing another aircraft to land on a crossing runway so close to our landing rollout. We were in a critical landing phase and had to make a decision quickly. I do not know that I would have done anything different considering the instructions I was given. The crew believed that there was an aircraft landing behind us on Runway 11 and that we needed to exit the active runway quickly to prevent the following aircraft from having to 'Go Around!' This would be the logical assumption; however; not today.


Synopsis: Business jet flight crew reported they followed HPN Tower's instruction to exit Runway 16 onto Runway 11 while another aircraft was on final approach for Runway 11.