37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1151785 |
Time | |
Date | 201402 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BUF.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | EMB ERJ 135 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Component | |
Aircraft Component | ILS/VOR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe |
Narrative:
Localizer signal unreliable/intermittent. On approach into buf; we received an intermittent and unreliable signal for runway 05. We acknowledged the NOTAM that coupled approaches were not allowed for the ILS 05. The first officer hand flew the approach as we intercepted the localizer; 5 miles outside of zobso. At 3 miles outside of zobso; our CDI showed a red X; indicating that we lost the signal. After about 2 seconds; it came back and we recaptured and continued the approach. Moments later at zobso; we lost localizer signal again. This time I conferred with first officer and said we should consider abandoning the approach and try something else. He concurred and we told ATC of our issues of the signal reception. He stated the current weather and pointed out the airport to us; that we can continue visually. We discussed our options; saw the airport straight ahead and continued our approach visually. I monitored the localizer signal as we continued. The signal was lost two more times and when we did receive the signal; it swung back and forth in an unreliable manner. After landing; we relayed to the tower that we had issues with the localizer signal. The airplane was not written-up as we had used the localizer at lga 22 and cle 24L and it worked correctly. This localizer signal has a history of issues. I have written previous reports for grr 26L; lga 04. Another localizer with reliability issues is lex 22.
Original NASA ASRS Text
Title: EMB-135 Captain finds the localizer for Runway 05 at BUF to be unacceptable even though it is NOTAMed to prohibit coupled approaches. Other airport localizers are cited as not being well received by aircraft that he flies.
Narrative: Localizer signal unreliable/intermittent. On approach into BUF; we received an intermittent and unreliable signal for Runway 05. We acknowledged the NOTAM that coupled approaches were not allowed for the ILS 05. The First Officer hand flew the approach as we intercepted the LOC; 5 miles outside of ZOBSO. At 3 miles outside of ZOBSO; our CDI showed a red X; indicating that we lost the signal. After about 2 seconds; it came back and we recaptured and continued the approach. Moments later at ZOBSO; we lost LOC signal again. This time I conferred with First Officer and said we should consider abandoning the approach and try something else. He concurred and we told ATC of our issues of the signal reception. He stated the current weather and pointed out the airport to us; that we can continue visually. We discussed our options; saw the airport straight ahead and continued our approach visually. I monitored the LOC signal as we continued. The signal was lost two more times and when we did receive the signal; it swung back and forth in an unreliable manner. After landing; we relayed to the tower that we had issues with the localizer signal. The airplane was not written-up as we had used the localizer at LGA 22 and CLE 24L and it worked correctly. This LOC signal has a history of issues. I have written previous reports for GRR 26L; LGA 04. Another LOC with reliability issues is LEX 22.
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.