![]()  | 
            37000 Feet | Browse and search NASA's Aviation Safety Reporting System  | 
            
                
  | 
        
| Attributes | |
| ACN | 1480551 | 
| Time | |
| Date | 201709 | 
| Local Time Of Day | 0601-1200 | 
| Place | |
| Locale Reference | ZZZ.ARTCC | 
| State Reference | US | 
| Environment | |
| Flight Conditions | VMC | 
| Light | Daylight | 
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER/LR | 
| Operating Under FAR Part | Part 121 | 
| Flight Phase | Cruise | 
| Flight Plan | IFR | 
| Person 1 | |
| Function | Captain Pilot Not Flying  | 
| Qualification | Flight Crew Air Transport Pilot (ATP) | 
| Person 2 | |
| Function | First Officer Pilot Flying  | 
| Qualification | Flight Crew Air Transport Pilot (ATP) | 
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types  | 
Narrative:
In level cruise flight at FL320 on the arrival; received a clearance from ATC to descend to FL300; leaving FL310 turn right 30 degrees; 'south' turns for spacing. I read back the instructions and we initiated the descent and turn.approximately 30;400 ft; ATC issued instructions to climb to FL320. I inquired the climb instructions and ATC confirmed the altitude. I asked if he still needed the 30 degree right turn; and he issued instructions to go direct to a VOR; reaching FL320. We complied; and I reported when level and direct to the VOR. Shortly after; we noticed [a regional jet] check in on frequency. The first officer and I discussed what happened; and we both agreed we heard our call sign and flight number when issued the descent and turn. We believe the controller meant to issue those instructions to [the regional jet]; as he gave them similar instructions shortly after they checked in. I wanted to file this report; in case I did make a read back error and accepted a clearance for another aircraft. ATC did not make any issue of it and we continued on. Threats were unawareness of a similar sounding call sign and the potential for a read back error. Although we believe we were in compliance with ATC instructions; an uas (undesired aircraft state) occurred as it required a change in altitude and direction.
Original NASA ASRS Text
Title: The flight crew of an Embraer reported that due to similar call signs they complied with instructions from ATC for a different aircraft.
Narrative: In level cruise flight at FL320 on the arrival; received a clearance from ATC to descend to FL300; leaving FL310 turn right 30 degrees; 'S' turns for spacing. I read back the instructions and we initiated the descent and turn.Approximately 30;400 FT; ATC issued instructions to climb to FL320. I inquired the climb instructions and ATC confirmed the altitude. I asked if he still needed the 30 degree right turn; and he issued instructions to go direct to a VOR; reaching FL320. We complied; and I reported when level and direct to the VOR. Shortly after; we noticed [a regional jet] check in on frequency. The First Officer and I discussed what happened; and we both agreed we heard our call sign and flight number when issued the descent and turn. We believe the controller meant to issue those instructions to [the regional jet]; as he gave them similar instructions shortly after they checked in. I wanted to file this report; in case I did make a read back error and accepted a clearance for another aircraft. ATC did not make any issue of it and we continued on. Threats were unawareness of a similar sounding call sign and the potential for a read back error. Although we believe we were in compliance with ATC instructions; an UAS (Undesired Aircraft State) occurred as it required a change in altitude and direction.
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.