 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-700 flight crew reported on incorrect frequency on approach resulting in go-around.
| Attributes | |
| ACN | 1662618 |
| Time | |
| Date | 201907 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 424 Flight Crew Type 18000 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown |
Narrative:
We were on final approach to runway xxl in ZZZ and were told to 'contact tower now;' without being given a frequency. Normally; when we switch frequencies; we are given the frequency to switch to. We switched to the tower and were cleared to land; and told we were number one for [runway] xxl. As we were about to start down on the glideslope; we were told to cancel our approach and to climb and maintain 5;000 feet and track the localizer; by the final monitor; which was selected on radio two. The first officer immediately acknowledged the clearance; and I turned off the autopilot; and began a climb to 5;000 feet and tracked the localizer outbound. The final monitor repeated his instructions and demanded we reply. The first officer switched to the monitor frequency to ensure he heard us and told him we were complying. Afterward; there was discussion on why he didn't hear our response; and we found that we had the wrong tower frequency programmed for the runway in use; so the final monitor couldn't hear us. We were confused; because we had checked in with the tower and they cleared us to land; so we couldn't understand why the monitor couldn't hear us.when told to call the tower; the controllers should also state the frequency; especially when doing prm (precision runway monitor) approaches. We should have done a better job of verifying the frequency in the high workload environment.
Original NASA ASRS Text
Title: B737-700 flight crew reported on incorrect frequency on approach resulting in go-around.
Narrative: We were on final approach to Runway XXL in ZZZ and were told to 'contact Tower now;' without being given a frequency. Normally; when we switch frequencies; we are given the frequency to switch to. We switched to the Tower and were cleared to land; and told we were number one for [Runway] XXL. As we were about to start down on the glideslope; we were told to cancel our approach and to climb and maintain 5;000 feet and track the localizer; by the final monitor; which was selected on radio two. The First Officer immediately acknowledged the clearance; and I turned off the autopilot; and began a climb to 5;000 feet and tracked the LOC outbound. The final monitor repeated his instructions and demanded we reply. The First Officer switched to the monitor frequency to ensure he heard us and told him we were complying. Afterward; there was discussion on why he didn't hear our response; and we found that we had the wrong Tower frequency programmed for the runway in use; so the final monitor couldn't hear us. We were confused; because we had checked in with the Tower and they cleared us to land; so we couldn't understand why the monitor couldn't hear us.When told to call the Tower; the controllers should also state the frequency; especially when doing PRM (Precision Runway Monitor) approaches. We should have done a better job of verifying the frequency in the high workload environment.
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.