DH8C and unidented aircraft had TCASII RA in rdu class east airspace.

Attributes
ACN	528056
Time
Date	200110
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : rdu.airport
State Reference	NC
Altitude	msl bound lower : 6000 msl bound upper : 7000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : rdu.tracon
Operator	common carrier : air carrier
Make Model Name	Dash 8-300
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : rdu.tracon
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : multi engine pilot : instrument pilot : commercial
Experience	flight time last 90 days : 230 flight time total : 2800 flight time type : 1800
ASRS Report	528056
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne critical non adherence : far non adherence : published procedure non adherence : required legal separation
Independent Detector	aircraft equipment : tcas other flight crewa other flight crewb
Resolutory Action	controller : issued alert controller : issued new clearance flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Filed route for flight was clt-HUG5.gippr-sdz-buzzy.BUZZY5-rdu. Checked on with rdu approach at 9000 ft. After passing buzzy, we were assigned a heading. In a separate, subsequent clearance we heard the controller give us a descent to 6000 ft. Captain read back clearance and we began descent to 6000 ft. I believe the controller called traffic for us which we located. We then noticed another target on the TCASII which seemed to be a threat. I slowed my descent, then leveled off, then began a climb to respond to an RA from the TCASII. As I began the climb, the controller issued a traffic alert to us. After the RA was over and straight and level flight had resumed, the controller informed us that he was working another flight on a separate frequency. (Frequencys were set up so we could hear all of the controller's xmissions, but only the replies that were given on our frequency.)

Original NASA ASRS Text

Title: DH8C AND UNIDENTED ACFT HAD TCASII RA IN RDU CLASS E AIRSPACE.

Narrative: FILED RTE FOR FLT WAS CLT-HUG5.GIPPR-SDZ-BUZZY.BUZZY5-RDU. CHKED ON WITH RDU APCH AT 9000 FT. AFTER PASSING BUZZY, WE WERE ASSIGNED A HDG. IN A SEPARATE, SUBSEQUENT CLRNC WE HEARD THE CTLR GIVE US A DSCNT TO 6000 FT. CAPT READ BACK CLRNC AND WE BEGAN DSCNT TO 6000 FT. I BELIEVE THE CTLR CALLED TFC FOR US WHICH WE LOCATED. WE THEN NOTICED ANOTHER TARGET ON THE TCASII WHICH SEEMED TO BE A THREAT. I SLOWED MY DSCNT, THEN LEVELED OFF, THEN BEGAN A CLB TO RESPOND TO AN RA FROM THE TCASII. AS I BEGAN THE CLB, THE CTLR ISSUED A TFC ALERT TO US. AFTER THE RA WAS OVER AND STRAIGHT AND LEVEL FLT HAD RESUMED, THE CTLR INFORMED US THAT HE WAS WORKING ANOTHER FLT ON A SEPARATE FREQ. (FREQS WERE SET UP SO WE COULD HEAR ALL OF THE CTLR'S XMISSIONS, BUT ONLY THE REPLIES THAT WERE GIVEN ON OUR FREQ.)

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.