Air carrier vectored on localizer runway 19R for visual approach; entered thin cloud layer and was u...

Narrative:

Runway 19C closed at iad. We are vectored to runway 19R. Told to join 19R localizer (but not cleared for any approach) from about 4000 feet on about a 10 mile final. Slowing and configuring; ATC tells us to descend to 2000 feet approximately 7 miles out and call the airport. ATC never specifies that we are to plan a visual; but keeps asking us to report airport in sight. The 2000 feet altitude they assign puts us smack in a thin cloud layer they don't realize has moved over approach path. At this altitude we can neither see the airport nor intercept the GS as we are above it the whole time. For unknown reasons; ATC will not clear us for an ILS nor will they assign a lower altitude than 2000 feet; they just keep asking for visual acquisition; which never happens. This progresses until we realize that we are too far above the GS for a stabilized approach and we begin our own go-around. ATC becomes quite overloaded and never: 1)issues us a go-around 2)issues an approach clearance (visual or instrument) or lower altitude 3)instructs us to call tower even though we are only about 3 miles from airport. ATC is also quite slow in giving us go-around vectors/altitudes and we find ourselves flying uncomfortably low at 2000 feet over the airport for quite some time. On our subsequent approach; there are spacing speed problems still going on and yet another company plane ahead of us is issued a go-around. Our go-around caught us by surprise and was less than stellar. Being that we never caught the GS and thus selected a go-around altitude; when we executed the go-around there was no altitude set to capture; so the nose simply pitched up and blasted on high; but ATC never issued a new altitude other than to 2000 feet; so we had to override the climb immediately disconnect everything and haul back to 2000 feet. Very challenging.

Original NASA ASRS Text

Title: Air carrier vectored on LOC Runway 19R for visual approach; entered thin cloud layer and was unable to see the airport; absent an ILS clearance elects to initiate a go around; reporters questioned ATC handling.

Narrative: Runway 19C closed at IAD. We are vectored to Runway 19R. Told to join 19R LOC (but not cleared for any approach) from about 4000 feet on about a 10 mile final. Slowing and configuring; ATC tells us to descend to 2000 feet approximately 7 miles out and call the airport. ATC never specifies that we are to plan a visual; but keeps asking us to report airport in sight. The 2000 feet altitude they assign puts us smack in a thin cloud layer they don't realize has moved over approach path. At this altitude we can neither see the airport nor intercept the GS as we are above it the whole time. For unknown reasons; ATC will not clear us for an ILS nor will they assign a lower altitude than 2000 feet; they just keep asking for visual acquisition; which never happens. This progresses until we realize that we are too far above the GS for a stabilized approach and we begin our own go-around. ATC becomes quite overloaded and never: 1)Issues us a go-around 2)Issues an approach clearance (visual or instrument) or lower altitude 3)Instructs us to call tower even though we are only about 3 miles from airport. ATC is also quite slow in giving us go-around vectors/altitudes and we find ourselves flying uncomfortably low at 2000 feet over the airport for quite some time. On our subsequent approach; there are spacing speed problems still going on and yet another company plane ahead of us is issued a go-around. Our go-around caught us by surprise and was less than stellar. Being that we never caught the GS and thus selected a go-around altitude; when we executed the go-around there was no altitude set to capture; so the nose simply pitched up and blasted on high; but ATC never issued a new altitude other than to 2000 feet; so we had to override the climb immediately disconnect everything and haul back to 2000 feet. Very challenging.

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

Attributes
ACN	845622
Time
Date	200907
Local Time Of Day	0001-0600
Place
Locale Reference	IAD.Airport
State Reference	DC
Environment
Flight Conditions	Marginal
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Person 1
Function	Pilot Flying Captain
Experience	Flight Crew Last 90 Days 220 Flight Crew Total 15000 Flight Crew Type 5200
Person 2
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 8000 Flight Crew Type 1000
Events
Anomaly	ATC Issue All Types Inflight Event / Encounter Unstabilized Approach

Air carrier vectored on localizer runway 19R for visual approach; entered thin cloud layer and was unable to see the airport; absent an ILS clearance elects to initiate a go around; reporters questioned ATC handling.