Narrative:

Clt approach, left downwind runway 36L in turn to base leg. Turning to heading 090 ft altitude 3600 ft assigned by ATC. About the 210 degree radial of the clt VOR. About the 12 DME point. 2 to 3 NM's north of rock hill/york co airport. VFR conditions. During left turn to 090 degreee heading, traffic appeared on TCAS ii screen at about the 11 O'clock position. Rotating clockwise on the screen to the 2 O'clock position as we rolled out. Our airspeed was 170 KTS assigned. This caused a high angle of attack in the turn causing the view out the forward window to be somewhat blocked. Did not see the other aircraft until we rolled out as it passed off our 3 O'clock position. Traffic appeared to be heading west bound. -300 ft below. Traffic was just inside the 2.5 NM ring on TCASII screen with 5 NM range selected. We received only an RA. Never received a TA. RA commanded a climb. We climbed 200 ft (3800 MSL) before 'clear of conflict' occurred. TCASII traffic was showing -300 ft on screen. Note: the floor of class 'B' airspace in clt in this area is 3600 ft. Clt approach routinely puts us at 3600 ft when being vectored for runway 36L. If VFR traffic is flying under the class 'B' at 3500 ft there is no vertical separation. We have no protection from VFR traffic. Class 'B' airspace needs to be lowered farther out from airport. When traffic increases so does the length of the final. Callback conversation with reporter revealed the following information: captain stated that the controller did issue a TA, but far too late to be of any use. Well after the TCASII had issued the RA. Reporter turned in a report to the company, but did not hold out much hope for any resolution from that source. The captain stated that next time into clt a call will be made to the TRACON supervisor regarding this issue. Captain recommends that clt approach control should raise the altitude in that area to 4000 ft vs the now used 3600 ft.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737-300 FLC HAVE A POTENTIAL CONFLICT WITH AN UNKNOWN ACFT FLYING AT THE BASE OF THE CLASS B AIRSPACE 12 NM SW OF CLT.

Narrative: CLT APCH, LEFT DOWNWIND RWY 36L IN TURN TO BASE LEG. TURNING TO HDG 090 FT ALT 3600 FT ASSIGNED BY ATC. ABOUT THE 210 DEGREE RADIAL OF THE CLT VOR. ABOUT THE 12 DME POINT. 2 TO 3 NM'S N OF ROCK HILL/YORK CO ARPT. VFR CONDITIONS. DURING L TURN TO 090 DEGREEE HDG, TFC APPEARED ON TCAS II SCREEN AT ABOUT THE 11 O'CLOCK POS. ROTATING CLOCKWISE ON THE SCREEN TO THE 2 O'CLOCK POS AS WE ROLLED OUT. OUR AIRSPEED WAS 170 KTS ASSIGNED. THIS CAUSED A HIGH ANGLE OF ATTACK IN THE TURN CAUSING THE VIEW OUT THE FORWARD WINDOW TO BE SOMEWHAT BLOCKED. DID NOT SEE THE OTHER ACFT UNTIL WE ROLLED OUT AS IT PASSED OFF OUR 3 O'CLOCK POS. TFC APPEARED TO BE HDG W BOUND. -300 FT BELOW. TFC WAS JUST INSIDE THE 2.5 NM RING ON TCASII SCREEN WITH 5 NM RANGE SELECTED. WE RECEIVED ONLY AN RA. NEVER RECEIVED A TA. RA COMMANDED A CLB. WE CLBED 200 FT (3800 MSL) BEFORE 'CLR OF CONFLICT' OCCURRED. TCASII TFC WAS SHOWING -300 FT ON SCREEN. NOTE: THE FLOOR OF CLASS 'B' AIRSPACE IN CLT IN THIS AREA IS 3600 FT. CLT APCH ROUTINELY PUTS US AT 3600 FT WHEN BEING VECTORED FOR RWY 36L. IF VFR TFC IS FLYING UNDER THE CLASS 'B' AT 3500 FT THERE IS NO VERTICAL SEPARATION. WE HAVE NO PROTECTION FROM VFR TFC. CLASS 'B' AIRSPACE NEEDS TO BE LOWERED FARTHER OUT FROM ARPT. WHEN TFC INCREASES SO DOES THE LENGTH OF THE FINAL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: CAPT STATED THAT THE CTLR DID ISSUE A TA, BUT FAR TOO LATE TO BE OF ANY USE. WELL AFTER THE TCASII HAD ISSUED THE RA. RPTR TURNED IN A RPT TO THE COMPANY, BUT DID NOT HOLD OUT MUCH HOPE FOR ANY RESOLUTION FROM THAT SOURCE. THE CAPT STATED THAT NEXT TIME INTO CLT A CALL WILL BE MADE TO THE TRACON SUPVR REGARDING THIS ISSUE. CAPT RECOMMENDS THAT CLT APCH CTL SHOULD RAISE THE ALT IN THAT AREA TO 4000 FT VS THE NOW USED 3600 FT.

Data retrieved from NASA's ASRS site as of July 2007 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.