Narrative:

I am reporting to make a suggestion for reducing confusion in an airport hot spot. No deviation and no runway incursion occurred; but there was come confusion at the intersection. We were cleared from the terminal to taxi via taxiway G and taxiway east to runway 19R at taxiway V. After turning onto taxiway east; I was unsure of whether to continue ahead on taxiway east to cross runway 25R (I had missed taxiway V while turning onto taxiway east); so I brought the aircraft to a stop to check. While stopping; ground called to confirm that we were holding short of runway 19R/intersection V. Ground stated we had missed the taxiway V turn; but full length runway 19R was available and cleared us to taxi to runway 19R full length. The aircraft never crossed the line for runway 25R until after accepting the second clearance from the controller to taxi full length runway 19R. After being cleared across runway 25R on taxiway east; we were cleared for takeoff for runway 19R full length (tlr performance had already been set up for full length runway 19R). A possible runway 25R incursion was avoided both because I stopped the aircraft as soon as I became uncertain about crossing another runway and an alert ground controller was also on the lookout for potential problems. For the runway 19R/intersection V departure; if you're coming from taxiway G; you should never really make a turn onto taxiway east; you just cross it when transitioning to taxiway V. My suggestion would be to issue this taxi clearance as 'taxi via taxiway G and taxiway V to runway 19R for intersection V departure.' omitting 'echo' from the taxi clearance and plan makes sense because you never really use taxiway east. With the taxiways g-e-V clearance; once you've completed a turn onto taxiway east; then you've already missed taxiway V. Neither taxiway G nor taxiway V cross runway 25R; so close adherence to a gold-victor taxi plan would greatly reduce the risk of a runway 25R incursion at taxiway east. Contributing to the confusion was the fact that another aircraft (an airbus) had already taxied full length on taxiway east. I had read the latest mke memo and the blue page; but these memos make more reference to the runway 25L/31 hot spot and the latest 2 of the 3 memos did not mention the runway 19R/intersection V hot spot; though I see that the back of the airport diagram describes it perfectly. I mistook the latest information to be fully descriptive of all of the hot spot risks in mke and it turns out there are multiple areas of difficulty. In the future; I will include in the brief the specific risks identified on the diagram for every hot spot in the taxi plan. I will interpret intersection departures (for my plane or another) as a trigger for extra caution for taxi and situational awareness. When in use; the fact of the intersection departure deserves highlighting during performance and departure brief (at the gate) as well as takeoff brief (during taxi) so as to reinforce the plan that this won't be a full length departure.

Google
 

Original NASA ASRS Text

Title: An air carrier pilot suggests that when Ground Control clears aircraft from the terminal for a takeoff at Runway 19R Intersection V; the clearance not include Taxiway E because that can lead to an aircraft missing Taxiway V and incurring Runway 25R.

Narrative: I am reporting to make a suggestion for reducing confusion in an airport Hot Spot. No deviation and no runway incursion occurred; but there was come confusion at the intersection. We were cleared from the terminal to taxi via Taxiway G and Taxiway E to Runway 19R at Taxiway V. After turning onto Taxiway E; I was unsure of whether to continue ahead on Taxiway E to cross Runway 25R (I had missed Taxiway V while turning onto Taxiway E); so I brought the aircraft to a stop to check. While stopping; Ground called to confirm that we were holding short of Runway 19R/Intersection V. Ground stated we had missed the Taxiway V turn; but full length Runway 19R was available and cleared us to taxi to Runway 19R full length. The aircraft never crossed the line for Runway 25R until after accepting the second clearance from the Controller to taxi full length Runway 19R. After being cleared across Runway 25R on Taxiway E; we were cleared for takeoff for Runway 19R full length (TLR performance had already been set up for full length Runway 19R). A possible Runway 25R incursion was avoided both because I stopped the aircraft as soon as I became uncertain about crossing another runway and an alert Ground Controller was also on the lookout for potential problems. For the Runway 19R/Intersection V departure; if you're coming from Taxiway G; you should never really make a turn onto Taxiway E; you just cross it when transitioning to Taxiway V. My suggestion would be to issue this taxi clearance as 'taxi via Taxiway G and Taxiway V to Runway 19R for intersection V departure.' Omitting 'Echo' from the taxi clearance and plan makes sense because you never really use Taxiway E. With the Taxiways G-E-V clearance; once you've completed a turn onto Taxiway E; then you've already missed Taxiway V. Neither Taxiway G nor Taxiway V cross Runway 25R; so close adherence to a Gold-Victor taxi plan would greatly reduce the risk of a Runway 25R incursion at Taxiway E. Contributing to the confusion was the fact that another aircraft (an Airbus) had already taxied full length on Taxiway E. I had read the latest MKE memo and the blue page; but these memos make more reference to the Runway 25L/31 Hot Spot and the latest 2 of the 3 memos did not mention the Runway 19R/Intersection V Hot Spot; though I see that the back of the airport diagram describes it perfectly. I mistook the latest information to be fully descriptive of all of the Hot Spot risks in MKE and it turns out there are multiple areas of difficulty. In the future; I will include in the brief the specific risks identified on the diagram for every Hot Spot in the taxi plan. I will interpret intersection departures (for my plane or another) as a trigger for extra caution for taxi and situational awareness. When in use; the fact of the intersection departure deserves highlighting during performance and departure brief (at the gate) as well as takeoff brief (during taxi) so as to reinforce the plan that this won't be a full length departure.

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