![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 973407 |
| Time | |
| Date | 201110 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain |
| Person 2 | |
| Function | First Officer |
| Events | |
| Anomaly | Deviation - Procedural Clearance |
Narrative:
In cruise at FL330 we were given a frequency change to 132.22. I inadvertently dialed in 133.22. When checking in with the next controller we were given and read back a climb to FL350. Shortly there after we were given a frequency change to 132.22. When checking in with the controller we were given a descent to FL340 and queried our last assigned altitude. We were instructed to call center upon arrival. The flight continued to our destination and arrived normally. After landing; I contacted center who informed me that we had contacted center on 133.22 in error. What we did not hear was aircraft Y check on seconds before. The controller inadvertently assigned aircraft X FL350 instead of aircraft Y. We had checked onto the wrong frequency at precisely the wrong time. Suggestions; if a clearance seems odd; you should question ATC about the clearance.
Original NASA ASRS Text
Title: Air Carrier changing to the wrong frequency was issued a climb only to discover later the climb was for a company aircraft with a similar flight number.
Narrative: In cruise at FL330 we were given a frequency change to 132.22. I inadvertently dialed in 133.22. When checking in with the next controller we were given and read back a climb to FL350. Shortly there after we were given a frequency change to 132.22. When checking in with the controller we were given a descent to FL340 and queried our last assigned altitude. We were instructed to call Center upon arrival. The Flight continued to our destination and arrived normally. After landing; I contacted Center who informed me that we had contacted Center on 133.22 in error. What we did not hear was Aircraft Y check on seconds before. The controller inadvertently assigned Aircraft X FL350 instead of Aircraft Y. We had checked onto the wrong frequency at precisely the wrong time. Suggestions; if a clearance seems odd; you should question ATC about the clearance.
Data retrieved from NASA's ASRS site as of April 2012 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.