A corporate pilot reported a traffic alert with a cessna that was being vectored; while on a visual ...

Attributes
ACN	1458046
Time
Date	201706
Local Time Of Day	1201-1800
Place
Locale Reference	NCT.TRACON
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Climb
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 50 Flight Crew Total 8000 Flight Crew Type 600
Events
Anomaly	ATC Issue All Types Conflict NMAC Deviation - Altitude Overshoot Deviation - Procedural Clearance
Miss Distance	Horizontal 0 Vertical 300

Narrative:

On initial descent into rno from the north for a landing on runway 34R; we are vectored to 200 heading and given a hard altitude of 10000 ft to avoid a cessna 172 that is being vectored south east to climb so he can avoid a fire west of reno. The cessna is told to climb on a heading of 140 and maintain 8500 ft this vector crosses the arrival area for both runway 34L and 34R. When we are asked if we can accept a visual approach we say yes and we are cleared for the visual 34R with the restriction of maintaining 9100 ft until on final for 34R to prevent a conflict with the cessna; which is not showing any altitude on our TCAS. The pilot flying begins his base turn and we get a traffic alert; while scanning of the cessna the PF descended slightly and is now at 8900 ft while interception final approach and the cessna passes below us at about 300 ft.root cause was the cessna being vectored across the final approach course instead of down the west side of the airport which would have kept him clear of arriving aircraft. Additional factor was our aircraft being cleared for a visual approach and then given the 9100 ft restriction until on final; not a standard procedure and an altitude that was not a standard altitude.

Original NASA ASRS Text

Title: A Corporate pilot reported a traffic alert with a Cessna that was being vectored; while on a visual approach into RNO.

Narrative: On initial descent into RNO from the north for a landing on RWY 34R; we are vectored to 200 HDG and given a hard altitude of 10000 ft to avoid a Cessna 172 that is being vectored south east to climb so he can avoid a fire west of Reno. The Cessna is told to climb on a HDG of 140 and maintain 8500 ft this vector crosses the arrival area for both RWY 34L and 34R. When we are asked if we can accept a visual approach we say yes and we are cleared for the visual 34R with the restriction of maintaining 9100 ft until on final for 34R to prevent a conflict with the Cessna; which is not showing any altitude on our TCAS. The pilot flying begins his base turn and we get a traffic alert; while scanning of the Cessna the PF descended slightly and is now at 8900 ft while interception final approach and the Cessna passes below us at about 300 ft.Root cause was the Cessna being vectored across the final approach course instead of down the west side of the airport which would have kept him clear of arriving aircraft. Additional factor was our aircraft being cleared for a visual approach and then given the 9100 ft restriction until on final; not a standard procedure and an altitude that was not a standard altitude.

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.

A corporate pilot reported a traffic alert with a cessna that was being vectored; while on a visual approach into rno.