B737-700 crew lost communication with approach controller at bwi.

Attributes
ACN	515816
Time
Date	200106
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bwi.airport
State Reference	MD
Altitude	msl single value : 11000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : bwi.tracon tracon : dca.tracon
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Route In Use	arrival star : ott.ott5
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Experience	flight time last 90 days : 200 flight time total : 9000 flight time type : 200
ASRS Report	515816
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact other
Supplementary
Problem Areas	Aircraft ATC Facility
Primary Problem	Ambiguous

Narrative:

We were descending on the nottingham 5 arrival to bwi at our last cleared altitude of 11000 from washington approach. Traffic was at 10000 ft, so we were held high. After 1-2 mins we thought approach should have cleared us lower, so I queried washington approach and got no response. I switched to communication #2 and still got no response. I even tried baltimore approach on 119.7 with no response. I tried washington approach again on communication #1 and finally had radio contact. Washington approach told us to turn to a 360 degree heading and contact bwi approach on 117.7. Baltimore approach descended us to 6000 ft then 3000 ft. We saw the airport and landed using standard approach and landing procedures. Washington approach said there may be a stuck microphone on the frequency and it may be us. I told them we did not think it was us. I am not sure why the frequency was dead, but it sure did happen at a busy time on arrival. I think we did take appropriate action to re-establish radio communication by switching radio and frequencys.

Original NASA ASRS Text

Title: B737-700 CREW LOST COM WITH APCH CTLR AT BWI.

Narrative: WE WERE DSNDING ON THE NOTTINGHAM 5 ARR TO BWI AT OUR LAST CLRED ALT OF 11000 FROM WASHINGTON APCH. TFC WAS AT 10000 FT, SO WE WERE HELD HIGH. AFTER 1-2 MINS WE THOUGHT APCH SHOULD HAVE CLRED US LOWER, SO I QUERIED WASHINGTON APCH AND GOT NO RESPONSE. I SWITCHED TO COM #2 AND STILL GOT NO RESPONSE. I EVEN TRIED BALTIMORE APCH ON 119.7 WITH NO RESPONSE. I TRIED WASHINGTON APCH AGAIN ON COM #1 AND FINALLY HAD RADIO CONTACT. WASHINGTON APCH TOLD US TO TURN TO A 360 DEG HDG AND CONTACT BWI APCH ON 117.7. BALTIMORE APCH DSNDED US TO 6000 FT THEN 3000 FT. WE SAW THE ARPT AND LANDED USING STANDARD APCH AND LNDG PROCS. WASHINGTON APCH SAID THERE MAY BE A STUCK MIKE ON THE FREQ AND IT MAY BE US. I TOLD THEM WE DID NOT THINK IT WAS US. I AM NOT SURE WHY THE FREQ WAS DEAD, BUT IT SURE DID HAPPEN AT A BUSY TIME ON ARR. I THINK WE DID TAKE APPROPRIATE ACTION TO RE-ESTABLISH RADIO COM BY SWITCHING RADIO AND FREQS.

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.