 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An airbus flight crew encountered a false localizer intercept when cleared for the ILS runway 9 at mem.
| Attributes | |
| ACN | 1005449 |
| Time | |
| Date | 201204 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | MEM.Airport |
| State Reference | TN |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Airbus Industrie Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | ILS/VOR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Track / Heading All Types |
Narrative:
We were on the tammy arrival and were directed to proceed to budee (IAF for ILS runway 09). En route to budee (about 10-15 miles from the fix) we were assigned to intercept the localizer to runway 9 and report the field in sight. Selected VOR/localizer on fcp; shortly thereafter the aircraft started turning right and showed localizer captured. As pilot not flying I told the captain it was a false capture and to roll out. He selected heading sel and we corrected back to budee. We selected localizer when closer to budee and it responded correctly. I informed ATC of a false localizer intercept and they passed on that information to the following aircraft. When our automation failed us; we saw the deviation and deautomated to comply with clearance. We nonetheless turned off course to the right (approximately 20 degrees) due to the time necessary to detect the error and correct the automation.I have spoken with other pilots about runway 9 false localizer intercepts. One other pilot indicated that this has happened to him and he suggested it had to do with tunica airport. Primary prevention should be proper inspection of ground localizer equipment. If tunica is affecting approaches to runway 9 we should be able to fix that from a ground based NAVAID standpoint. It wouldn't hurt to add a warning to the approach plate if this continues to occur.
Original NASA ASRS Text
Title: An Airbus flight crew encountered a false localizer intercept when cleared for the ILS Runway 9 at MEM.
Narrative: We were on the Tammy Arrival and were directed to proceed to BUDEE (IAF for ILS Runway 09). En route to BUDEE (about 10-15 miles from the fix) we were assigned to intercept the localizer to Runway 9 and report the field in sight. Selected VOR/LOC on FCP; shortly thereafter the aircraft started turning right and showed LOC captured. As pilot not flying I told the Captain it was a false capture and to roll out. He selected HDG SEL and we corrected back to BUDEE. We selected LOC when closer to BUDEE and it responded correctly. I informed ATC of a false localizer intercept and they passed on that information to the following aircraft. When our automation failed us; we saw the deviation and deautomated to comply with clearance. We nonetheless turned off course to the right (approximately 20 degrees) due to the time necessary to detect the error and correct the automation.I have spoken with other pilots about Runway 9 false localizer intercepts. One other pilot indicated that this has happened to him and he suggested it had to do with Tunica Airport. Primary prevention should be proper inspection of ground localizer equipment. If Tunica is affecting approaches to Runway 9 we should be able to fix that from a ground based NAVAID standpoint. It wouldn't hurt to add a warning to the approach plate if this continues to occur.
Data retrieved from NASA's ASRS site as of July 2013 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.