37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1605578 |
Time | |
Date | 201812 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | BOI.TRACON |
State Reference | ID |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 16 |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
Aircraft X; was on a base for the ILS runway 12 at bzn. There were 4 other aircraft being vectored for the ILS at the time. The bzn sector utilizes three radar feeds (qsi; bzn; qva) and is fused. An error message appeared in the stars status area that both qsi and bzn radars had failed. In addition; all of the frequencies for the sector failed as well. There is no 121.5/243.0 available at this sector. As soon as I realized what had happened; I broadcast on the emergency backup frequency for 118.97 and issued aircraft X a vector to join the localizer even though I had lost radar on the target. The terrain rises north and east of the localizer and the MVA is 8300. Aircraft X was at 7600. I attempted several times to relay through other aircraft but all the frequencies had failed. I called bzn ATCT and the controller stated that aircraft X was on their frequency and was 30 seconds from joining the localizer. I asked bzn for a position from aircraft X and the tower stated 4 miles from manni and established on the localizer. I then cleared the aircraft for the ILS runway 12 approach.there was a known issue throughout the building with no internet for reports; no way to obtain NOTAMS or no indication that this issue may affect the radar feed at this sector. If known; I could have assigned non radar separation to all of the arrivals to ensure a loss of radar would have little effect except efficiency.
Original NASA ASRS Text
Title: Boise TRACON Controller reported losing radio and radar contact on an aircraft inbound to an airport in mountainous terrain.
Narrative: Aircraft X; was on a base for the ILS Runway 12 at BZN. There were 4 other aircraft being vectored for the ILS at the time. The BZN sector utilizes three radar feeds (QSI; BZN; QVA) and is FUSED. An error message appeared in the STARS status area that both QSI and BZN radars had failed. In addition; all of the frequencies for the sector failed as well. There is NO 121.5/243.0 available at this sector. As soon as I realized what had happened; I broadcast on the emergency backup frequency for 118.97 and issued Aircraft X a vector to join the localizer even though I had lost radar on the target. The terrain rises north and east of the localizer and the MVA is 8300. Aircraft X was at 7600. I attempted several times to relay through other aircraft but all the frequencies had failed. I called BZN ATCT and the controller stated that Aircraft X was on their frequency and was 30 seconds from joining the localizer. I asked BZN for a position from Aircraft X and the tower stated 4 miles from MANNI and established on the localizer. I then cleared the aircraft for the ILS Runway 12 approach.There was a known issue throughout the building with no internet for reports; no way to obtain NOTAMS or no indication that this issue may affect the radar feed at this sector. If known; I could have assigned non radar separation to all of the arrivals to ensure a loss of radar would have little effect except efficiency.
Data retrieved from NASA's ASRS site 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.