Falcon 2000
Conflict NMAC
Flight Crew Took Evasive Action
Airspace Structure; Procedure
Second in Command (SIC) was Pilot Flying (PF). On arrival into TEB from the north on V489. Cleared direct to UNVIL and descending through 3;600 feet to 3;000 feet. ATC was task saturated. Received Monitor VS RA for climbing traffic at 12 o'clock 2 miles 500 below. We stopped our descent. Changed to Climb RA. Began to climb and called ATC; reported RA and climbing to 4;000 feet. ATC then reported traffic and told us to 'Climb; climb now'. Comm frequency was very congested. We climbed to about 4;000 feet and RA shifted to adjust vertical speed but the traffic was still climbing. We again received a climb RA. The traffic was 300 feet right under us and climbing. We continued up to about 4;800 feet before receiving clear of conflict. We reported clear and descending to 3;000 feet and received a vector for the ILS 19. We never saw the traffic.If controller had a way to block out or override incoming transmissions so that he could get a warning out.
It was a tough situation to avoid. We were being vectored at low altitude presumably to remain clear of the traffic for LGA and EWR. That puts us down with a lot of VFR traffic. I don't think ATC gave us any heads up traffic notice but they may have done so and been stepped on. Perhaps the approach sectors should be smaller for each individual controller. Perhaps the controller's comm transmitter should be powerful enough to block out other aircraft's transmitters.
DA-2000 flight crew reported an NMAC on arrival into TEB; citing airspace structure; frequency congestion; and controller workload as contributing.