Narrative:

Handed off from paris controller (who had a thick accent.) what I understood and read back was '...contact brussels on 125.6'. The pilot flying thought he heard 125.0. Because the controller didn't correct my read back I checked in with brussels on 125.6 the controller acknowledged immediately (leading us to believe that 125.6 was the correct frequency) and what I heard and thought he said was 'descend to FL180'. The pilot flying heard the same and initiated a descent to FL180. I read back 'leaving FL230 for FL180.' as we were descending the controller queried us and asked if we had started our descent. I replied 'affirmative; descending through FL220 for 180'. Controller then said to reset transponder as he showed us still at FL250.realizing something wasn't right I instructed the pilot flying to push altitude hold. The controller realized something wasn't right at the same time and asked for our position and whether we were on 125.6. Controller told us to maintain FL215 and explained he thought we were [another company flight]; who subsequently checked on to the frequency moments later at FL250. The controller said there was no conflict and handed us off to 125.0 (maastricht; I think). It was very hard to discern the difference between [the flight numbers].english not primary language of controller. Controller not speaking slowly and concisely. My failure to resolve immediately with the paris controller the discrepancy between what I heard and what the first officer (first officer) heard (125.6 vs 125.0). Internationally it's sometimes a group effort to discern clearances. In this case it didn't work because the controller on the wrong frequency was expecting an aircraft with a similar call sign.reminding controllers to speak clearer and slower with foreign crews. Any time there is a discrepancy; immediately resolve it before continuing.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier flight crew reported an altitude deviation in European airspace when they took a clearance to descend intended for another aircraft with a similar call sign. Flight crew also stated language barrier issues contributed to the event.

Narrative: Handed off from Paris Controller (who had a thick accent.) What I understood and read back was '...contact Brussels on 125.6'. The pilot flying thought he heard 125.0. Because the Controller didn't correct my read back I checked in with Brussels on 125.6 The Controller acknowledged immediately (leading us to believe that 125.6 was the correct frequency) and what I heard and thought he said was 'descend to FL180'. The pilot flying heard the same and initiated a descent to FL180. I read back 'leaving FL230 for FL180.' As we were descending the Controller queried us and asked if we had started our descent. I replied 'affirmative; descending through FL220 for 180'. Controller then said to reset transponder as he showed us still at FL250.Realizing something wasn't right I instructed the pilot flying to push altitude hold. The Controller realized something wasn't right at the same time and asked for our position and whether we were on 125.6. Controller told us to maintain FL215 and explained he thought we were [another company flight]; who subsequently checked on to the frequency moments later at FL250. The Controller said there was no conflict and handed us off to 125.0 (Maastricht; I think). It was very hard to discern the difference between [the flight numbers].English not primary language of Controller. Controller not speaking slowly and concisely. My failure to resolve immediately with the Paris Controller the discrepancy between what I heard and what the FO (First Officer) heard (125.6 vs 125.0). Internationally it's sometimes a group effort to discern clearances. In this case it didn't work because the Controller on the wrong frequency was expecting an aircraft with a similar call sign.Reminding Controllers to speak clearer and slower with foreign crews. Any time there is a discrepancy; immediately resolve it before continuing.

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.