B737 on approach to iad encounters helicopter traffic while on ILS approach.

Attributes
ACN	607125
Time
Date	200402
Day	Wed
Place
Locale Reference	airport : iad.airport
State Reference	VA
Altitude	msl single value : 2000
Aircraft 1
Controlling Facilities	tracon : pct.tracon
Operator	common carrier : air carrier
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : n/a
Flight Phase	descent : approach
Route In Use	approach : instrument precision
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : pct.tracon
Operator	other
Make Model Name	S-70 Black Hawk/Night Hawk/Sea Hawk
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff cruise : level
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	607125
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : airborne less severe
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airspace Structure Flight Crew Human Performance ATC Human Performance
Primary Problem	Ambiguous

Narrative:

While on final passing 2000 ft and cleared for approach into iad, a black hawk progressed in the opposite direction of our aircraft in a climb, apparently climbing on the reverse of the ILS -- both course and altitude. The TCASII was the original indicator of the other aircraft. I saw the helicopter through the HUD and it was lined up in the sight of the HUD and on the centerline and glide path of the approach. As we neared and watched, the helicopter made a left turn (to our right) and passed to our right at very close proximity. An actual distance between aircraft was too difficult to determine but much too close for an approach under close control by the approach control. We initially notified the approach control of the other aircraft and were told 'roger.' then when the pass was too close for comfort, I told the controller 'it was too close for comfort and the incident needs to be reported.' the controller said again 'roger.' not sure of the exact words, but no explanation was given or reason for the other aircraft. No explanation of any sort was given as to why the other aircraft was there or if the controller had any knowledge of the other aircraft. This is not a reasonable situation anywhere in this country and in particular in the washington area.

Original NASA ASRS Text

Title: B737 ON APCH TO IAD ENCOUNTERS HELI TFC WHILE ON ILS APCH.

Narrative: WHILE ON FINAL PASSING 2000 FT AND CLRED FOR APCH INTO IAD, A BLACK HAWK PROGRESSED IN THE OPPOSITE DIRECTION OF OUR ACFT IN A CLB, APPARENTLY CLBING ON THE REVERSE OF THE ILS -- BOTH COURSE AND ALT. THE TCASII WAS THE ORIGINAL INDICATOR OF THE OTHER ACFT. I SAW THE HELI THROUGH THE HUD AND IT WAS LINED UP IN THE SIGHT OF THE HUD AND ON THE CTRLINE AND GLIDE PATH OF THE APCH. AS WE NEARED AND WATCHED, THE HELI MADE A L TURN (TO OUR R) AND PASSED TO OUR R AT VERY CLOSE PROX. AN ACTUAL DISTANCE BTWN ACFT WAS TOO DIFFICULT TO DETERMINE BUT MUCH TOO CLOSE FOR AN APCH UNDER CLOSE CTL BY THE APCH CTL. WE INITIALLY NOTIFIED THE APCH CTL OF THE OTHER ACFT AND WERE TOLD 'ROGER.' THEN WHEN THE PASS WAS TOO CLOSE FOR COMFORT, I TOLD THE CTLR 'IT WAS TOO CLOSE FOR COMFORT AND THE INCIDENT NEEDS TO BE RPTED.' THE CTLR SAID AGAIN 'ROGER.' NOT SURE OF THE EXACT WORDS, BUT NO EXPLANATION WAS GIVEN OR REASON FOR THE OTHER ACFT. NO EXPLANATION OF ANY SORT WAS GIVEN AS TO WHY THE OTHER ACFT WAS THERE OR IF THE CTLR HAD ANY KNOWLEDGE OF THE OTHER ACFT. THIS IS NOT A REASONABLE SIT ANYWHERE IN THIS COUNTRY AND IN PARTICULAR IN THE WASHINGTON AREA.

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.