CL300 captain reported ATC failed to provide separation with traffic requiring evasive action; vecto...

Narrative:

Approaching teb on ILS 19/circle 24. Good VFR. Outside tuggs told to slow to minimum practical speed (vref+-10). Hand flying. Told to square the turns in the pattern following a VFR G5 on the left downwind. Did not see the G5. Started to turn base and saw the G5 within 2 miles; base to final. We told tower it would not work and were given a 090 heading (1;000 feet MSL) I quickly displayed terrain on my display as we were headed into downtown nyc. We were then given a 170 heading and asked if we still had the field I sight (yes; but not in a position to land) we were cleared to land. We asked for a left turn around to give us spacing but that was denied. We turned right (45 degrees of bank) and was now facing a falcon about a mile away. We said that wouldn't work and we're asked what we were going to do. We suggested the falcon go around which he did; climbing and turning to avoid us. We were cleared to land and landed (definitely unstable approach). We asked for the tower phone number and found out the controller had been relieved shortly after this incident. Normally traffic flows into teb very smoothly. Everyone is on the same page and the coming from the same approach. Why a G5 was allowed to do VFR patterns on the opposite side of the field baffles me. Our flight could have easily ended in disaster. Our TCAS was inhibited for landing so we only had a vague pictorial view of what was going on. We were vectored toward an area of many obstacles at an altitude less than 1000' AGL. We were cleared to land with an airplane one mile away from us approaching the same runway. All our maneuvering was done with full flaps and gear down. We were unaware of the falcon until we were turned into his flight path. In hindsight we should have done a modified go around behind the G5; climbed to pattern altitude and flown right traffic. Teb tower can't ever let this happen again.

Original NASA ASRS Text

Title: CL300 Captain reported ATC failed to provide separation with traffic requiring evasive action; vectored dangerously close to obstacles; and situated aircraft on an unstable approach.

Narrative: Approaching TEB on ILS 19/circle 24. Good VFR. Outside TUGGS told to slow to minimum practical speed (Vref+-10). Hand flying. Told to square the turns in the pattern following a VFR G5 on the left downwind. Did not see the G5. Started to turn base and saw the G5 within 2 miles; Base to final. We told Tower it would not work and were given a 090 heading (1;000 feet MSL) I quickly displayed terrain on my display as we were headed into downtown NYC. We were then given a 170 heading and asked if we still had the field I sight (yes; but not in a position to land) we were cleared to land. We asked for a left turn around to give us spacing but that was denied. We turned right (45 degrees of bank) and was now facing a Falcon about a mile away. We said that wouldn't work and we're asked what we were going to do. We suggested the Falcon go around which he did; climbing and turning to avoid us. We were cleared to land and landed (definitely unstable approach). We asked for the Tower phone number and found out the controller had been relieved shortly after this incident. Normally traffic flows into TEB very smoothly. Everyone is on the same page and the coming from the same approach. Why a G5 was allowed to do VFR patterns on the opposite side of the field baffles me. Our flight could have easily ended in disaster. Our TCAS was inhibited for landing so we only had a vague pictorial view of what was going on. We were vectored toward an area of many obstacles at an altitude less than 1000' AGL. We were cleared to land with an airplane one mile away from us approaching the same runway. All our maneuvering was done with full flaps and gear down. We were unaware of the Falcon until we were turned into his Flight path. In hindsight we should have done a modified go around behind the G5; climbed to pattern altitude and flown RIGHT traffic. TEB Tower can't ever let this happen again.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	1555144
Time
Date	201806
Local Time Of Day	0601-1200
Place
Locale Reference	TEB.Airport
State Reference	NJ
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Challenger 300
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Gulfstream V / G500 / G550
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Flight Plan	VFR
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach

CL300 captain reported ATC failed to provide separation with traffic requiring evasive action; vectored dangerously close to obstacles; and situated aircraft on an unstable approach.