 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A320 first officer described an un-stabilized approach that resulted when the flying captain had previously hard tuned 110.9 for the ILS of the departure airport in the FMC rad/navigation page and forgot about it. The arrival airport used the same frequency for the ILS being flown but the autopilot would not capture the localizer until the frequency was retuned. A go-around was initiated.
| Attributes | |
| ACN | 1380480 |
| Time | |
| Date | 201608 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | ILS/VOR |
| Person 1 | |
| Function | Pilot Not Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 180 Flight Crew Total 8000 Flight Crew Type 1062 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
ZZZ1 has a complex departures procedure which requires extensive briefing. A portion of the departure procedure is predicated around using the localizer frequency which is 110.9. I wasn't aware; but the captain had also hard tuned 110.9 into the rad/nav page. We also had to deal with ATC reroutes to our flight plan because of weather in ZZZ.we briefed the approach and started our descent. In the descent we were very busy deviating around weather. On downwind; my pfd displayed 110.9 which is the ILS frequency for the runway assigned. Once turning base the ILS identified on my pfd was showing the correct four letter identifier and 110.9; and I announced 'ZZZZ localizer 110.9 identified.' we were told to maintain 2000 until established and cleared for the ILS. The captain armed the localizer and it displayed as armed on the pfd. However; the autopilot did not capture the localizer. At this time we were in visual conditions. We noticed the error and turned back towards the localizer; and at the same time ATC queried our position. The captain noticed the frequency was wrong; and we were able to correct the mistake by clearing the rad/nav page. ZZZZ localizer loaded in the rad/nav page and we were able to rejoin the localizer. However; the distractions caused us to be above the glide slope and fast. The captain attempted to configure and slow the aircraft while on the approach. Above 1000 feet he called for flaps full. I told him I was unable because we were too fast. At 1000 feet he called for flaps full again and I told him we were above the flaps full speed. I also stated we are probably going to need to go around. At 500 feet we caught sight of the runway but were still high; fast; and not fully configured. I called for the go around. The captain agreed and executed a go around recovering from our errors.we cleaned up the aircraft; briefed; and returned back for another ILS. The ILS was executed to a full stop landing.
Original NASA ASRS Text
Title: A320 First Officer described an un-stabilized approach that resulted when the flying Captain had previously hard tuned 110.9 for the ILS of the departure airport in the FMC RAD/NAV page and forgot about it. The arrival airport used the same frequency for the ILS being flown but the autopilot would not capture the LOC until the frequency was retuned. A go-around was initiated.
Narrative: ZZZ1 has a complex departures procedure which requires extensive briefing. A portion of the departure procedure is predicated around using the localizer frequency which is 110.9. I wasn't aware; but the captain had also hard tuned 110.9 into the Rad/Nav page. We also had to deal with ATC reroutes to our flight plan because of weather in ZZZ.We briefed the approach and started our descent. In the descent we were very busy deviating around weather. On downwind; my PFD displayed 110.9 which is the ILS frequency for the runway assigned. Once turning base the ILS identified on my PFD was showing the correct four letter identifier and 110.9; and I announced 'ZZZZ Localizer 110.9 identified.' We were told to maintain 2000 until established and cleared for the ILS. The captain armed the LOC and it displayed as armed on the PFD. However; the autopilot did not capture the localizer. At this time we were in visual conditions. We noticed the error and turned back towards the localizer; and at the same time ATC queried our position. The captain noticed the frequency was wrong; and we were able to correct the mistake by clearing the Rad/Nav page. ZZZZ Localizer loaded in the Rad/Nav page and we were able to rejoin the localizer. However; the distractions caused us to be above the glide slope and fast. The captain attempted to configure and slow the aircraft while on the approach. Above 1000 feet he called for flaps full. I told him I was unable because we were too fast. At 1000 feet he called for flaps full again and I told him we were above the flaps full speed. I also stated we are probably going to need to go around. At 500 feet we caught sight of the runway but were still high; fast; and not fully configured. I called for the Go Around. The captain agreed and executed a Go Around recovering from our errors.We cleaned up the Aircraft; briefed; and returned back for another ILS. The ILS was executed to a full stop landing.
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.