Near midair collision in TCA B airspace.

Attributes
ACN	283844
Time
Date	199409
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : iad
State Reference	VA
Altitude	msl bound lower : 5000 msl bound upper : 8000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : iad tracon : ord
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Flight Plan	VFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 220 flight time total : 24136 flight time type : 15000
ASRS Report	283844
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	conflict : nmac non adherence : far other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified other controllera
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 0 vertical : 500
Supplementary
Primary Problem	ATC Human Performance
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

While being vectored by iad approach control for landing on runway 1L at iad we were cleared from 8000-5000 ft and issued VFR traffic at 6500 ft at 12 O'clock. As we descended we got a TCASII RA which we responded to as we visually located the light aircraft. I transmitted on ATC frequency. Flight company and number responding to a TCASII RA. No response from controller. Later controller transmitted 'did somebody call.' I responded we did and instead of descending as cleared the reason for us to climb and further RA has been satisfied. I was appalled at the ATC supervisors response on the telephone when he said the light aircraft was VFR outside the TCA and they were legal. My point was why did they turn us straight at the aircraft when they knew he was there, legal or not? Solution to problem is change ATC procedures or leak these many incidents to the news media. In reality TCASII has provided a new element to this ongoing problem because of aircraft maneuvering unexpected by ATC. Frequency too busy anymore for immediate communications and forward flight attendant and passenger very concerned because they can hear TCASII warnings.

Original NASA ASRS Text

Title: NMAC IN TCA B AIRSPACE.

Narrative: WHILE BEING VECTORED BY IAD APCH CTL FOR LNDG ON RWY 1L AT IAD WE WERE CLRED FROM 8000-5000 FT AND ISSUED VFR TFC AT 6500 FT AT 12 O'CLOCK. AS WE DSNDED WE GOT A TCASII RA WHICH WE RESPONDED TO AS WE VISUALLY LOCATED THE LIGHT ACFT. I TRANSMITTED ON ATC FREQ. FLT COMPANY AND NUMBER RESPONDING TO A TCASII RA. NO RESPONSE FROM CTLR. LATER CTLR TRANSMITTED 'DID SOMEBODY CALL.' I RESPONDED WE DID AND INSTEAD OF DSNDING AS CLRED THE REASON FOR US TO CLB AND FURTHER RA HAS BEEN SATISFIED. I WAS APPALLED AT THE ATC SUPVRS RESPONSE ON THE TELEPHONE WHEN HE SAID THE LIGHT ACFT WAS VFR OUTSIDE THE TCA AND THEY WERE LEGAL. MY POINT WAS WHY DID THEY TURN US STRAIGHT AT THE ACFT WHEN THEY KNEW HE WAS THERE, LEGAL OR NOT? SOLUTION TO PROB IS CHANGE ATC PROCS OR LEAK THESE MANY INCIDENTS TO THE NEWS MEDIA. IN REALITY TCASII HAS PROVIDED A NEW ELEMENT TO THIS ONGOING PROB BECAUSE OF ACFT MANEUVERING UNEXPECTED BY ATC. FREQ TOO BUSY ANYMORE FOR IMMEDIATE COMS AND FORWARD FLT ATTENDANT AND PAX VERY CONCERNED BECAUSE THEY CAN HEAR TCASII WARNINGS.

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.