Narrative:

Local charlotte ground control cleared us to 'expedite across runway 23 at A4, left onto taxiway M, hold short of taxiway F.' we proceeded to expedite across runway 23. Upon reaching the other side of runway 23, we saw the taxiway B indicating that we were on taxiway B. We were not given definitive taxi instructions via taxiway B or M2, to join taxiway M. We saw no conflict in joining taxiway M via M2. Without stopping, we made a left turn onto the high speed M2, to intercept taxiway M. Upon turning onto M2 high speed, the ground controller told us to 'hold your position,' and we complied. After approximately 2 mins, we were given instructions to continue our taxi. The tower received a ground surveillance warning, indicating we were not clear of the runway. As a result, the tower issued a go around clearance to the air carrier landing. At no point were we turning back onto the runway. It is our opinion that by continuing to hold our position as instructed, we were held in a position that would set off a conflict warning. Had we been cleared to continue straight ahead on M2, to clear the runway hold short lines, we believe that the warning would not have occurred. Additionally, this situation could have been avoided if the clearance had included taxiway B. Future occurrences at this intersection of A4 runway 23 and taxiway B might be avoided if A4 was reidented as taxiway B. Making this change would minimize confusion when crossing runway 23 at this intersection. It would also be consistent with the other txwys that cross runway 23 including txwys D, C, right, G, F, and east.

Google
 

Original NASA ASRS Text

Title: A TAXIING C560 IS HELD ON A TXWY NEAR RWY 23 WHICH CREATED A TFC CONFLICT WITH A LNDG ACFT AT CLT, NC.

Narrative: LCL CHARLOTTE GND CTL CLRED US TO 'EXPEDITE ACROSS RWY 23 AT A4, L ONTO TXWY M, HOLD SHORT OF TXWY F.' WE PROCEEDED TO EXPEDITE ACROSS RWY 23. UPON REACHING THE OTHER SIDE OF RWY 23, WE SAW THE TXWY B INDICATING THAT WE WERE ON TXWY B. WE WERE NOT GIVEN DEFINITIVE TAXI INSTRUCTIONS VIA TXWY B OR M2, TO JOIN TXWY M. WE SAW NO CONFLICT IN JOINING TXWY M VIA M2. WITHOUT STOPPING, WE MADE A L TURN ONTO THE HIGH SPD M2, TO INTERCEPT TXWY M. UPON TURNING ONTO M2 HIGH SPD, THE GND CTLR TOLD US TO 'HOLD YOUR POS,' AND WE COMPLIED. AFTER APPROX 2 MINS, WE WERE GIVEN INSTRUCTIONS TO CONTINUE OUR TAXI. THE TWR RECEIVED A GND SURVEILLANCE WARNING, INDICATING WE WERE NOT CLR OF THE RWY. AS A RESULT, THE TWR ISSUED A GAR CLRNC TO THE ACR LNDG. AT NO POINT WERE WE TURNING BACK ONTO THE RWY. IT IS OUR OPINION THAT BY CONTINUING TO HOLD OUR POS AS INSTRUCTED, WE WERE HELD IN A POS THAT WOULD SET OFF A CONFLICT WARNING. HAD WE BEEN CLRED TO CONTINUE STRAIGHT AHEAD ON M2, TO CLR THE RWY HOLD SHORT LINES, WE BELIEVE THAT THE WARNING WOULD NOT HAVE OCCURRED. ADDITIONALLY, THIS SIT COULD HAVE BEEN AVOIDED IF THE CLRNC HAD INCLUDED TXWY B. FUTURE OCCURRENCES AT THIS INTXN OF A4 RWY 23 AND TXWY B MIGHT BE AVOIDED IF A4 WAS REIDENTED AS TXWY B. MAKING THIS CHANGE WOULD MINIMIZE CONFUSION WHEN XING RWY 23 AT THIS INTXN. IT WOULD ALSO BE CONSISTENT WITH THE OTHER TXWYS THAT CROSS RWY 23 INCLUDING TXWYS D, C, R, G, F, AND E.

Data retrieved from NASA's ASRS site as of July 2007 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.