Conflict between jetstream 3200 and B727 on approach to iad.

Attributes
ACN	437788
Time
Date	199905
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : iad.airport
State Reference	VA
Altitude	msl single value : 2000
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : iad.tracon
Operator	common carrier : air carrier
Make Model Name	Jetstream 32
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	approach : traffic pattern approach : circling arrival : vfr arrival : on vectors
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : iad.tracon
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : vacating altitude
Route In Use	approach : circling approach : visual approach : traffic pattern arrival : vfr
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : cfi pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 300 flight time total : 4800 flight time type : 800
ASRS Report	437788
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Events
Anomaly	conflict : airborne less severe non adherence : far
Independent Detector	aircraft equipment : tcas other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance
Miss Distance	horizontal : 500 vertical : 1000
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Given 280 degree vector for runway 19L at iad. Never cleared for visual. Coming from the barin transition, as we crossed the runway 19L localizer, my first officer tried to query the approach controller, but due to excessive radio chatter, was unable. Shortly after that, the TCASII went off and I saw a B727 on a visual for runway 19R off the right side and slightly higher. I banked hard left and descended approximately 500 ft. We avoided collision and were then vectored back around for runway 19R visual. We had been following a B757. Distance behind the B757 was right at the minimum limit. Thus, I had been busy with making sure our spacing was adequate. The controller forgot about us, and never cleared us for the visual for runway 19L. If the frequency hadn't been so damned busy, this could have been avoided. All distances are approximated by first officer (low time).

Original NASA ASRS Text

Title: CONFLICT BTWN JETSTREAM 3200 AND B727 ON APCH TO IAD.

Narrative: GIVEN 280 DEG VECTOR FOR RWY 19L AT IAD. NEVER CLRED FOR VISUAL. COMING FROM THE BARIN TRANSITION, AS WE CROSSED THE RWY 19L LOC, MY FO TRIED TO QUERY THE APCH CTLR, BUT DUE TO EXCESSIVE RADIO CHATTER, WAS UNABLE. SHORTLY AFTER THAT, THE TCASII WENT OFF AND I SAW A B727 ON A VISUAL FOR RWY 19R OFF THE R SIDE AND SLIGHTLY HIGHER. I BANKED HARD L AND DSNDED APPROX 500 FT. WE AVOIDED COLLISION AND WERE THEN VECTORED BACK AROUND FOR RWY 19R VISUAL. WE HAD BEEN FOLLOWING A B757. DISTANCE BEHIND THE B757 WAS RIGHT AT THE MINIMUM LIMIT. THUS, I HAD BEEN BUSY WITH MAKING SURE OUR SPACING WAS ADEQUATE. THE CTLR FORGOT ABOUT US, AND NEVER CLRED US FOR THE VISUAL FOR RWY 19L. IF THE FREQ HADN'T BEEN SO DAMNED BUSY, THIS COULD HAVE BEEN AVOIDED. ALL DISTANCES ARE APPROXIMATED BY FO (LOW TIME).

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.