B737 captain reports a near midair collision with VFR traffic during visual ILS approach. The traffi...

Narrative:

[We were] cleared for the visual approach to runway 23R at destination. Approach control advised VFR traffic; 10 o'clock; 5 miles; 500 ft above you has you in sight and is maintaining visual separation. We reported that we had the traffic on TCAS but not visually. Approach responded that 'he has you in sight and is maintaining visual separation. He will pass above and behind your aircraft. Maintain best forward speed; you are number one'. Approaching the glide slope; the TCAS target started descending. I informed the first officer (pilot flying) that it appeared the traffic was attempting to 'duck under' our flight path; rather than pass overhead; as instructed. I got a visual on the aircraft at the same time we received a TA from the aircraft. Within seconds; we received an RA to climb. We leveled our approach; maintained visual with the traffic as he passed under us by approximately 200 ft.[issue was due to] reliance of ATC to allow a VFR pilot to be the only one responsible for separation in class bravo airspace. If both aircraft cannot maintain visual separation; in this case we did not initially see the other aircraft; perhaps a vector away from the potential conflict could have been issued; even though the weather was VMC.

Original NASA ASRS Text

Title: B737 Captain reports a NMAC with VFR traffic during visual ILS approach. The traffic was pointed out and expected to maintain altitude 500 FT above the B737 but started descending causing a TCAS RA.

Narrative: [We were] cleared for the visual approach to Runway 23R at destination. Approach Control advised VFR traffic; 10 o'clock; 5 miles; 500 FT above you has you in sight and is maintaining visual separation. We reported that we had the traffic on TCAS but not visually. Approach responded that 'he has you in sight and is maintaining visual separation. He will pass above and behind your aircraft. Maintain best forward speed; you are number one'. Approaching the glide slope; the TCAS target started descending. I informed the First Officer (pilot flying) that it appeared the traffic was attempting to 'duck under' our flight path; rather than pass overhead; as instructed. I got a visual on the aircraft at the same time we received a TA from the aircraft. Within seconds; we received an RA to CLIMB. We leveled our approach; maintained visual with the traffic as he passed under us by approximately 200 FT.[Issue was due to] reliance of ATC to allow a VFR pilot to be the only one responsible for separation in Class Bravo airspace. If both aircraft cannot maintain visual separation; in this case we did not initially see the other aircraft; perhaps a vector away from the potential conflict could have been issued; even though the weather was VMC.

Data retrieved from NASA's ASRS site as of July 2013 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	998240
Time
Date	201203
Local Time Of Day	1801-2400
Place
Locale Reference	IND.Airport
State Reference	IN
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Person 1
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Conflict NMAC
Miss Distance	Horizontal 0 Vertical 200

B737 captain reports a near midair collision with VFR traffic during visual ILS approach. The traffic was pointed out and expected to maintain altitude 500 ft above the B737 but started descending causing a TCAS RA.