![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1759658 |
| Time | |
| Date | 202009 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Climbing to 160 on the zzzzz departure we were given a radio handoff to ZZZ TRACON and either we had put the wrong frequency in; or were given the incorrect one; but we tried to establish communication with the controller who we could clearly hear speaking. The controller came back to our check in with; 'everybody listen up...I'm working a bunch of frequencies; and have like 20 aircraft all trying to reach me. Just ident and I'll get back to all of you shortly.' so we sent an ident; and waited. After a few minutes; we queried again. The calls went unanswered. We waited a few more minutes; still at 160 on the departure; and tried again. This time we received the response; 'aircraft at 160; ident and I'll call you in a few minutes.' so we did. After an eternity; we finally demanded a specific call sign response; to which the controller told us we were on the wrong frequency and go back to previous one. So we did; to which the controller then gave us the correct one. The new controller was advised by us of the frequency error. Cause - over worked controller; lack of cpdlc to guarantee correct frequency; and controller using non-standard phraseology when answering radio calls. Suggestion - widespread use of cpdlc for handoffs; and controllers adhering to correct phraseology when addressing check-ins to a frequency.
Original NASA ASRS Text
Title: Air carrier Captain reported checking in and hearing the Controller tell everybody to stand by. They continued on assigned heading and altitude; finally being told they were on the wrong frequency. Controller reportedly was working multiple frequencies.
Narrative: Climbing to 160 on the ZZZZZ departure we were given a radio handoff to ZZZ TRACON and either we had put the wrong frequency in; or were given the incorrect one; but we tried to establish communication with the Controller who we could clearly hear speaking. The Controller came back to our check in with; 'Everybody listen up...I'm working a bunch of frequencies; and have like 20 aircraft all trying to reach me. Just ident and I'll get back to all of you shortly.' So we sent an ident; and waited. After a few minutes; we queried again. The calls went unanswered. We waited a few more minutes; still at 160 on the departure; and tried again. This time we received the response; 'Aircraft at 160; ident and I'll call you in a few minutes.' So we did. After an eternity; we finally demanded a specific call sign response; to which the Controller told us we were on the wrong frequency and go back to previous one. So we did; to which the Controller then gave us the correct one. The new Controller was advised by us of the frequency error. Cause - Over worked Controller; lack of CPDLC to guarantee correct frequency; and Controller using non-standard phraseology when answering radio calls. Suggestion - Widespread use of CPDLC for handoffs; and controllers adhering to correct phraseology when addressing check-ins to a frequency.
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.