Narrative:

Aircraft X after landing on runway 22L in lft; we were given taxi instructions by the tower controller to take J; then B; cross 11; hold short of 22R. We crossed 11; and then held short of 22R as instructed. We sat there for a short time waiting for a crossing clearance; but the tower didn't say anything. There were no aircraft on final for either 22R or 4L; and there were literally no other aircraft on any taxiways; so the captain prompted the controller and asked if we could cross 22R. The controller immediately said; 'cross 22R/4L;' but he left off a call sign. So I asked if that transmission was for aircraft X. He immediately responded by saying; 'affirmative; cross 22R/4L [company name] (then some other call sign that wasn't ours).' as soon as we had heard 'affirmative' and 'cross 22R/4L' we had slowly started to roll across the hold lines; but we stopped as soon as the wrong call sign was said (our nose was across the hold lines at this point). I queried the controller and asked him to confirm that the crossing clearance was indeed for aircraft X; and he said that it was. So we continued to cross and proceeded to the ramp with no further issues. The controller had nothing further to say. We wanted to file the as soon as possible because of the fact that we had crossed the hold line prior to hearing our actual call sign (even though it was clearly intended for us; and I think the controller just got our numbers mixed up with the flight that was still parked at one of the jetways). As I mentioned; there were literally no other aircraft on any of the taxiways.threats: controller not using the call sign to begin the radio transmission; instead; putting it at the end. Error: we started to roll as soon as we heard; 'affirmative; cross 22R/4L.' undesired state: being across the hold line until we got the call sign issue worked out. I'm always quite cautious about making sure the correct callsign is used and all instructions are correct over the radio. That being said; as soon as the controller responded to our direct question with the; 'affirmative; cleared to cross 22R/4L' part; I knew he was talking to us. Still we must always make sure to hear the correct callsign before following controller instructions. In this case; the controller was indeed talking to us and made a mistake using the wrong call sign; but I realize that in some instances; that may not be the case. So we must always pay attention to the call sign.

Google
 

Original NASA ASRS Text

Title: Pilot at LFT airport reports of bad communication procedures at the airport that they thought almost caused them to be part of a runway incursion.

Narrative: Aircraft X after landing on Runway 22L in LFT; we were given taxi instructions by the Tower Controller to take J; then B; cross 11; hold short of 22R. We crossed 11; and then held short of 22R as instructed. We sat there for a short time waiting for a crossing clearance; but the Tower didn't say anything. There were no aircraft on final for either 22R or 4L; and there were literally no other aircraft on any taxiways; so the Captain prompted the Controller and asked if we could cross 22R. The Controller immediately said; 'Cross 22R/4L;' but he left off a call sign. So I asked if that transmission was for Aircraft X. He immediately responded by saying; 'Affirmative; cross 22R/4L [Company Name] (then some other call sign that wasn't ours).' As soon as we had heard 'affirmative' and 'cross 22R/4L' we had slowly started to roll across the hold lines; but we stopped as soon as the wrong call sign was said (our nose was across the hold lines at this point). I queried the Controller and asked him to confirm that the crossing clearance was indeed for Aircraft X; and he said that it was. So we continued to cross and proceeded to the ramp with no further issues. The Controller had nothing further to say. We wanted to file the ASAP because of the fact that we had crossed the hold line prior to hearing our actual call sign (even though it was clearly intended for us; and I think the Controller just got our numbers mixed up with the flight that was still parked at one of the jetways). As I mentioned; there were literally no other aircraft on any of the taxiways.Threats: Controller not using the call sign to begin the radio transmission; instead; putting it at the end. Error: We started to roll as soon as we heard; 'Affirmative; cross 22R/4L.' Undesired state: Being across the hold line until we got the call sign issue worked out. I'm always quite cautious about making sure the correct callsign is used and all instructions are correct over the radio. That being said; as soon as the Controller responded to our direct question with the; 'Affirmative; cleared to cross 22R/4L' part; I knew he was talking to us. Still we must always make sure to hear the correct callsign before following Controller instructions. In this case; the Controller was indeed talking to us and made a mistake using the wrong call sign; but I realize that in some instances; that may not be the case. So we must always pay attention to the call sign.

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.