Flight crew of a B737-300 is unable to receive ILS indications on approach into slc in IMC. Reassigned approach to parallel runway but unable to get an indication on that ILS either. A missed approach is executed for vectors to the VOR approach.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	386492
Time
Date	199711
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : slc
State Reference	UT
Altitude	msl bound lower : 10000 msl bound upper : 10000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : slc
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 180 flight time total : 7000 flight time type : 1700
ASRS Report	386492
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	other
Consequence	Other Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

We were being vectored on a dogleg 310 degree heading to intercept the runway 34R ILS at slc. With both VHF navigation radios tuned to the proper ILS frequency, we were unable to receive an identify on either radio and there were localizer and GS off flags on both HSI's. We advised the approach controller, who was busy, that we were not receiving the ILS and he told us to stand by. We tuned one navigation radio to the slc VOR and turned to a 340 degree heading which we believed would keep us clear of the wasatch mountains (which we were painting on the radar). The approach controller then advised us that the runway 34R ILS was operative and gave us a heading to intercept the runway 34L ILS. Since we also were unable to receive the runway 34L ILS, we terminated the approach and received vectors back around for the VOR approach to runway 34R and an uneventful landing. Observations: had I studied the VOR approach as a backup initially I could have transitioned to it immediately. This was the first time that neither VHF navigation radio would not receive the ILS in my experience.

Original NASA ASRS Text

Title: FLC OF A B737-300 IS UNABLE TO RECEIVE ILS INDICATIONS ON APCH INTO SLC IN IMC. REASSIGNED APCH TO PARALLEL RWY BUT UNABLE TO GET AN INDICATION ON THAT ILS EITHER. A MISSED APCH IS EXECUTED FOR VECTORS TO THE VOR APCH.

Narrative: WE WERE BEING VECTORED ON A DOGLEG 310 DEG HDG TO INTERCEPT THE RWY 34R ILS AT SLC. WITH BOTH VHF NAV RADIOS TUNED TO THE PROPER ILS FREQ, WE WERE UNABLE TO RECEIVE AN IDENT ON EITHER RADIO AND THERE WERE LOC AND GS OFF FLAGS ON BOTH HSI'S. WE ADVISED THE APCH CTLR, WHO WAS BUSY, THAT WE WERE NOT RECEIVING THE ILS AND HE TOLD US TO STAND BY. WE TUNED ONE NAV RADIO TO THE SLC VOR AND TURNED TO A 340 DEG HDG WHICH WE BELIEVED WOULD KEEP US CLR OF THE WASATCH MOUNTAINS (WHICH WE WERE PAINTING ON THE RADAR). THE APCH CTLR THEN ADVISED US THAT THE RWY 34R ILS WAS OPERATIVE AND GAVE US A HDG TO INTERCEPT THE RWY 34L ILS. SINCE WE ALSO WERE UNABLE TO RECEIVE THE RWY 34L ILS, WE TERMINATED THE APCH AND RECEIVED VECTORS BACK AROUND FOR THE VOR APCH TO RWY 34R AND AN UNEVENTFUL LNDG. OBSERVATIONS: HAD I STUDIED THE VOR APCH AS A BACKUP INITIALLY I COULD HAVE TRANSITIONED TO IT IMMEDIATELY. THIS WAS THE FIRST TIME THAT NEITHER VHF NAV RADIO WOULD NOT RECEIVE THE ILS IN MY EXPERIENCE.

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.