Air carrier flight crew reports TCAS RA at 6000 feet on vectors for ILS runway 19R at dca near fdk.

Attributes
ACN	785327
Time
Date	200805
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dca.airport
State Reference	DC
Altitude	msl single value : 6000
Aircraft 1
Controlling Facilities	tracon : pct.tracon tower : zzz.tower
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer only : 19r
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : pct.tracon
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 180 flight time total : 12000 flight time type : 8000
ASRS Report	785327
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 200 flight time total : 14500 flight time type : 385
ASRS Report	785327
Events
Anomaly	altitude deviation : excursion from assigned altitude conflict : airborne less severe
Independent Detector	aircraft equipment : tcas other controllera
Resolutory Action	controller : issued advisory flight crew : took evasive action
Supplementary
Problem Areas	Flight Crew Human Performance Airspace Structure ATC Human Performance
Primary Problem	Ambiguous

Narrative:

At 6000 ft on vectors to visual approach to iad runway 19R in the vicinity of fdk; we were instructed by ATC to turn from a heading of 090 degrees to a 150 degree heading to join the runway 19R localizer. This was after a number of vectors by the TRACON; including 1 across the localizer. Just prior to intercept; we received a TCAS climb RA for traffic at our 3 O'clock position and 500 ft below us and apparently climbing. I initiated an aggressive pitch up to follow the guidance (2000 FPM up). We cleared the conflict within a few seconds. We were previously advised of the traffic at our 1 O'clock position on a previous 150 degree vector but the controller turned us left to a 090 degree heading before we could spot it visually. The controller then turned us back to the 150 degree heading (seemingly right at the traffic) and the conflict occurred. Based on the chatter on the frequency and the actions and language of the controller; it was obvious she was at or beyond her capacity to be situationally aware. The controller was overworked in my opinion. In the future; I will be even more vigilant when it appears the controller is at capacity; especially with this TRACON.

Original NASA ASRS Text

Title: ACR FLT CREW REPORTS TCAS RA AT 6000 FEET ON VECTORS FOR ILS RWY 19R AT DCA NEAR FDK.

Narrative: AT 6000 FT ON VECTORS TO VISUAL APCH TO IAD RWY 19R IN THE VICINITY OF FDK; WE WERE INSTRUCTED BY ATC TO TURN FROM A HDG OF 090 DEGS TO A 150 DEG HDG TO JOIN THE RWY 19R LOC. THIS WAS AFTER A NUMBER OF VECTORS BY THE TRACON; INCLUDING 1 ACROSS THE LOC. JUST PRIOR TO INTERCEPT; WE RECEIVED A TCAS CLB RA FOR TFC AT OUR 3 O'CLOCK POS AND 500 FT BELOW US AND APPARENTLY CLBING. I INITIATED AN AGGRESSIVE PITCH UP TO FOLLOW THE GUIDANCE (2000 FPM UP). WE CLRED THE CONFLICT WITHIN A FEW SECONDS. WE WERE PREVIOUSLY ADVISED OF THE TFC AT OUR 1 O'CLOCK POS ON A PREVIOUS 150 DEG VECTOR BUT THE CTLR TURNED US L TO A 090 DEG HDG BEFORE WE COULD SPOT IT VISUALLY. THE CTLR THEN TURNED US BACK TO THE 150 DEG HDG (SEEMINGLY RIGHT AT THE TFC) AND THE CONFLICT OCCURRED. BASED ON THE CHATTER ON THE FREQ AND THE ACTIONS AND LANGUAGE OF THE CTLR; IT WAS OBVIOUS SHE WAS AT OR BEYOND HER CAPACITY TO BE SITUATIONALLY AWARE. THE CTLR WAS OVERWORKED IN MY OPINION. IN THE FUTURE; I WILL BE EVEN MORE VIGILANT WHEN IT APPEARS THE CTLR IS AT CAPACITY; ESPECIALLY WITH THIS TRACON.

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