Narrative:

While operating aircraft X into ZZZ on a program flight using the company X abc callsign we landed on runway xxl and received the normal 'left at taxiway 1; cross runway yr; hold short runway yl' instructions from tower after landing around xa:30Z. Upon approaching runway yr we heard over the radio '[muffled] XXX#ca [callsign] cross-runway yl on taxiway 1 and taxiway 2 to park.' the PIC; who was pilot not flying (PNF); hesitated with a read back because the call sign was slightly muffled due to radio static; but the instructions and cadence made sense that they were for us; since we were the only aircraft on taxiway 1 in that position to follow the instructions. So he read them back and I the sic and ip (acting as pilot flying doing training in new aircraft) continued to cross yl and continued taxiway 2 to park.upon parking and getting out of the aircraft [and] the more I thought about it the more something seemed off. [I found out] tower did use the wrong callsign; they used the company Y ca [callsign]; as company Y ca cross yl and taxiway 1 to park.'contributing to this situation was the crew fatigue and us not being 100% on our game. Also; the controller had a high workload as he appeared to be working both tower and ground control positions.although the instructions were most likely for us as our callsign was somewhat similar this scenario brought up a lot of other important facts to point out. We as a crew should never assume a runway crossing instruction is for us unless our call sign is 100% specifically used without a question. If we had any doubts about the instruction; we should have stopped and ask for clarification prior to proceeding.as for the tower controller; he was working both ground and tower; which makes for a high workload; as ZZZ was experiencing a traffic push at that time and he was getting busy. His misspeaking could have caused an incident or incursion. Lucky for us company Y ca landed 30 minutes prior to this incident taking place. It is possible the controller had an old strip lying around or just had that specific call sign on his mind. In any case; ATC should consider increasing staffing levels and not having a single controller work both tower and ground positions; except during very low traffic levels. Air traffic loads have increased significantly from the covid lows experienced several months ago.

Related reports:

Google
 

Original NASA ASRS Text

Title: Flight crew reported crossing a runway; taxiing to parking; while not sure if the clearance instructions were for them due to Tower muffling the callsign.

Narrative: While operating Aircraft X into ZZZ on a program flight using the Company X ABC callsign we landed on Runway XXL and received the normal 'Left at Taxiway 1; cross Runway YR; hold short Runway YL' instructions from Tower after landing around XA:30Z. Upon approaching Runway YR we heard over the radio '[muffled] XXX#CA [callsign] cross-Runway YL on Taxiway 1 and Taxiway 2 to park.' The PIC; who was Pilot Not Flying (PNF); hesitated with a read back because the call sign was slightly muffled due to radio static; but the instructions and cadence made sense that they were for us; since we were the only aircraft on Taxiway 1 in that position to follow the instructions. So he read them back and I the SIC and IP (acting as Pilot Flying doing training in new aircraft) continued to cross YL and continued Taxiway 2 to park.Upon parking and getting out of the aircraft [and] the more I thought about it the more something seemed off. [I found out] Tower did use the wrong callsign; they used the Company Y CA [callsign]; as Company Y CA cross YL and Taxiway 1 to park.'Contributing to this situation was the crew fatigue and us not being 100% on our game. Also; the Controller had a high workload as he appeared to be working both Tower and Ground Control positions.Although the instructions were most likely for us as our callsign was somewhat similar this scenario brought up a lot of other important facts to point out. We as a crew should never assume a runway crossing instruction is for us unless our call sign is 100% specifically used without a question. If we had any doubts about the instruction; we should have stopped and ask for clarification prior to proceeding.As for the Tower Controller; he was working both Ground and Tower; which makes for a high workload; as ZZZ was experiencing a traffic push at that time and he was getting busy. His misspeaking could have caused an incident or incursion. Lucky for us Company Y CA landed 30 minutes prior to this incident taking place. It is possible the Controller had an old strip lying around or just had that specific call sign on his mind. In any case; ATC should consider increasing staffing levels and not having a single Controller work both Tower and Ground positions; except during very low traffic levels. Air traffic loads have increased significantly from the COVID lows experienced several months ago.

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.