Narrative:

Took off from sdf runway 35L at XA15L, cleared to 5000 ft heading 330 degrees. Next heading was 300 degrees in climb. Handed off to departure control. Cleared to 7000 ft, heading 270 degrees. At this point, we were climbing through 5000 ft, turning to 270 degrees, when TCASII called 'traffic.' I observed target on TCASII at 1 O'clock position and less than 1 mi, no altitude tag. I increased bank angle in the left turn to 45 degrees, which prompted 'bank angle' callouts. Then got RA to descend. Lowered nose and descended to 5000 ft on 270 degree heading, exceeding 300 KTS. Reduced thrust and extended speed brakes, slowing to 250 KTS. Clear of conflict, we were turned to 230 degrees to intercept our course and climb to 7000 ft. First officer had several communications with ATC during conflict. As we got the TCASII RA, ATC advised 'pop-up' VFR traffic, 1 O'clock position, less than 1/2 mi at 6000 ft, then changed it to altitude unknown (he may have been reading our altitude at 6000 ft). First officer reported we were responding to a TCASII RA. We never saw the conflict aircraft, as we were in and out of a layer of clouds. This is the second time this exact scenario has happened to me, flying a B767 off of runway 35L from sdf and climbing through 5000 ft into a conflict. Supplemental information from acn 571369: at approximately 5500 ft TCASII RA directed an immediate descent. Having flown out of ksdf on a regular basis, I've observed traffic conflicts often without warning from ATC. Often times, we find out that ATC knew of the traffic, but did not call it out to us. This problem has been with sdf approach/departure. The TCASII alert was vital to the safe resolution.

Related reports:

Google
 

Original NASA ASRS Text

Title: B767-300 FLC INITIATE TCASII EVASIVE MANEUVER AS SDF DATA CTLR ISSUES TA. FLC STATES SDF INCONSISTENT WITH TA ISSUANCE.

Narrative: TOOK OFF FROM SDF RWY 35L AT XA15L, CLRED TO 5000 FT HDG 330 DEGS. NEXT HDG WAS 300 DEGS IN CLB. HANDED OFF TO DEP CTL. CLRED TO 7000 FT, HDG 270 DEGS. AT THIS POINT, WE WERE CLBING THROUGH 5000 FT, TURNING TO 270 DEGS, WHEN TCASII CALLED 'TFC.' I OBSERVED TARGET ON TCASII AT 1 O'CLOCK POS AND LESS THAN 1 MI, NO ALT TAG. I INCREASED BANK ANGLE IN THE L TURN TO 45 DEGS, WHICH PROMPTED 'BANK ANGLE' CALLOUTS. THEN GOT RA TO DSND. LOWERED NOSE AND DSNDED TO 5000 FT ON 270 DEG HDG, EXCEEDING 300 KTS. REDUCED THRUST AND EXTENDED SPD BRAKES, SLOWING TO 250 KTS. CLR OF CONFLICT, WE WERE TURNED TO 230 DEGS TO INTERCEPT OUR COURSE AND CLB TO 7000 FT. FO HAD SEVERAL COMS WITH ATC DURING CONFLICT. AS WE GOT THE TCASII RA, ATC ADVISED 'POP-UP' VFR TFC, 1 O'CLOCK POS, LESS THAN 1/2 MI AT 6000 FT, THEN CHANGED IT TO ALT UNKNOWN (HE MAY HAVE BEEN READING OUR ALT AT 6000 FT). FO RPTED WE WERE RESPONDING TO A TCASII RA. WE NEVER SAW THE CONFLICT ACFT, AS WE WERE IN AND OUT OF A LAYER OF CLOUDS. THIS IS THE SECOND TIME THIS EXACT SCENARIO HAS HAPPENED TO ME, FLYING A B767 OFF OF RWY 35L FROM SDF AND CLBING THROUGH 5000 FT INTO A CONFLICT. SUPPLEMENTAL INFO FROM ACN 571369: AT APPROX 5500 FT TCASII RA DIRECTED AN IMMEDIATE DSCNT. HAVING FLOWN OUT OF KSDF ON A REGULAR BASIS, I'VE OBSERVED TFC CONFLICTS OFTEN WITHOUT WARNING FROM ATC. OFTEN TIMES, WE FIND OUT THAT ATC KNEW OF THE TFC, BUT DID NOT CALL IT OUT TO US. THIS PROB HAS BEEN WITH SDF APCH/DEP. THE TCASII ALERT WAS VITAL TO THE SAFE RESOLUTION.

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.