Date: 201910
Local time of day: 1201-1800
Location: HPN.Airport, NY
Flight conditions: VMC
Light: Dusk
Aircraft: Challenger 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach; Landing
Airspace: Class D HPN
ATC / advisory: Tower HPN
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Procedure; Human Factors; Airspace Structure
Primary problem: Aircraft

Narrative: While on approach the local area was saturated with both VFR and IFR traffic. The vectors to the approach to landing phase continued normally with us slowing our airspeed and configuring the aircraft earlier at the request of Approach. There were numerous heading changes and we were told that we were number four for the airport; number three initially. There were numerous aircraft on Tower and the frequency was congested. While on approach; we observed the aircraft in front of us land and exit. We then observed another aircraft land on the intersecting runway and clear the intersection of the two runways so we continued the approach to landing as we were now number one for the airport. We were fully configured; stabilized; and had a visual on the runway. At approximately 600 ft. we received a Traffic Alert. Both myself as Pilot Flying and the Pilot Monitoring looked up and tried to acquire the traffic that had triggered the traffic alert. It was difficult due to the time of day with our heading northwest and the sun just off of our left side but in less than an estimated two seconds we both visually acquired the traffic which was approximately 200 ft. above us and directly in front of us at less than one quarter mile laterally. It was a high-wing single engine aircraft that was flying a visual traffic pattern and was in the left downwind for the intersecting runway. Due to the location and proximity of the traffic that we had now visually acquired; we had zero options for avoidance other than to continue a descent. Climbing was out of the question and banking to avoid at less than what was now an estimated 400 ft. was not an option either. I initiated a momentary descent below the PAPI in an order to increase vertical separation from the traffic. I leveled off momentarily to recapture the PAPI and having maintained a visual with the runway I continued and landed without further incident. After clearing the runway; I requested the Pilot Monitoring ask Ground Control for a phone number to the Tower Cab. After shutdown and postflight I did call the Tower Cab regarding the issue and requested that they advise aircraft of traffic that will be overflying final approach paths. I would classify this as a loss of separation due to lack of communication from the controlling facility. Due to the phase of flight we had no good options and only one poor option that we undertook in order to increase separation.Traffic that is landing should be notified of aircraft that are in the pattern for an intersecting runway and if they're expected to overfly another aircraft in the course of their pattern work. This was a loss of separation incident that left us no options.




Synopsis: Challenger 300 Captain on short final reported taking evasive action to avoid traffic crossing their course.