An air carrier crew reported how a call sign similarity hear and read back error caused them to enter an active runway after a Company aircraft had been cleared for takeoff.
Synopsis
An air carrier crew reported how a call sign similarity hear and read back error caused them to enter an active runway after a Company aircraft had been cleared for takeoff.
Narrative
We were told to taxi cross 12L and 17 and hold short 12R at Hobby. There was traffic on final about 5 miles out and both the Captain and I thought we heard our Company # fly heading 220 cleared for takeoff. I responded heading 220 Runway 12R cleared for takeoff Company #. The Captain started moving forward and we had a quick conversation about the heading of 220 and that it seemed strange for our runway so I called to confirm the heading. Tower said that clearance was for a similar Company call sign and he asked if we crossed the hold short line. The Captain responded yes and told the Tower we could continue on to 12R and make an immediate turn onto 17 and come back to the hold short line to 12R. The Controller said this would be fine and we complied. To sum up what happened; we both believed the Controller was trying to get us out before the traffic on final and we were anticipating an immediate departure. With the call signs so close and the timing of the call; we thought we heard our flight number.
Second reporter narrative
Since I had crossed the runway hold line I continued onto 12R then a quick left on to Runway 4 then another quick left on to Taxiway E. As we were maneuvering; the clearance was clarified. The takeoff clearance was for Company # on Runway 22. We were Company #. To add to the callsign confusion; there was yet another jet flight # on final to Runway 12R.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.