Narrative:

At sdf, we briefed a taxi route to runway 17R via taxiway F, to hold short of runways 29 and 17R, then via txwys G and B to runway 17R. (We were immediately adjacent to taxiway F and the intersection of runways 17R and 29. Taxiway F runs parallel to runway 29, except at where it appears to also turn 90 degrees and run perpendicular to runway 29.) the busy ground controller issued us instructions to hold short of runway 17R on taxiway F. We exited the ramp and turned 45 degrees right onto taxiway F, and stopped well before the runways. We were then cleared to cross runway 17R 'without delay,' which the first officer read back. Before we were able to get underway, the controller said, 'oh, you are not on taxiway F,' and told us to also cross runway 29 without delay and continue taxi to runway 17R. We do not believe a runway incursion occurred in this case, but there was obviously a difference in where we were and where the ground controller expected us to be. Fortunately, he recognized this before it could become a problem and issued us another clearance. Although we maintain that we were on taxiway F, it appears that the controller expected us to be on taxiway F heading southeast holding short of runway 17R. From our prebrief, we expected to cross the runway intxns of runways 17R and 29 at taxiway F heading northeast. There was some doubt as to which taxiway F he wanted us on, which is why we held well short of the runways on taxiway F to allow us to go either way on taxiway F. Frequency congestion and takeoff preparations complicated clarification. This area should be depicted as a runway incursion 'hot spot.' the area can be confusing, and the taxi diagram is not much help. For example, there is no letter to designate the taxiway name at the approach end of runway 11. It seems that taxiway F wraps around the corner to cross at the runway intersection. At most other airports, parallel taxiway names are different than the 90 degree crossing taxiway names. Not so at sdf. This non-standard nomenclature adds confusion. Depiction of taxiway lettering further complicates this issue. Frequently, it is not clear which taxiway is which, without using the process of elimination. For example, the 'B' just south of runway 11 and east of runway 17R appears to refer to the east/west taxiway. However, it evidently is referring to the north/south taxiway. There is no other 'B' associated with this north/south taxiway. There are 2 other 'B's,' but they refer to the east/west 90 degree runway crossing txwys at either end of the parallel. This lends to confusion. Is there not a better way to depict taxiway names on a chart? Although in this situation, I donT' believe we had a runway incursion, it was due to the controller's heads up call that may have prevented one. A more complete briefing of the crew, to include possible alternate taxi rtes, and what instructions could be expected to differentiate between the use of which taxiway F, could also have helped prevent this occurrence. Improved taxi diagrams would be a great aid in minimizing confusion to help prevent runway incursions.

Google
 

Original NASA ASRS Text

Title: B727-200 POSITIONING TO CROSS RWY 17R ON TXWY F IS RECOGNIZED BY SDF GND CTL AS INCORRECT. FLT CREW POSITIONED FACING RWY 11. RPTR QUESTIONS CHART AND ARPT SIGNAGE.

Narrative: AT SDF, WE BRIEFED A TAXI RTE TO RWY 17R VIA TXWY F, TO HOLD SHORT OF RWYS 29 AND 17R, THEN VIA TXWYS G AND B TO RWY 17R. (WE WERE IMMEDIATELY ADJACENT TO TXWY F AND THE INTXN OF RWYS 17R AND 29. TXWY F RUNS PARALLEL TO RWY 29, EXCEPT AT WHERE IT APPEARS TO ALSO TURN 90 DEGS AND RUN PERPENDICULAR TO RWY 29.) THE BUSY GND CTLR ISSUED US INSTRUCTIONS TO HOLD SHORT OF RWY 17R ON TXWY F. WE EXITED THE RAMP AND TURNED 45 DEGS R ONTO TXWY F, AND STOPPED WELL BEFORE THE RWYS. WE WERE THEN CLRED TO CROSS RWY 17R 'WITHOUT DELAY,' WHICH THE FO READ BACK. BEFORE WE WERE ABLE TO GET UNDERWAY, THE CTLR SAID, 'OH, YOU ARE NOT ON TXWY F,' AND TOLD US TO ALSO CROSS RWY 29 WITHOUT DELAY AND CONTINUE TAXI TO RWY 17R. WE DO NOT BELIEVE A RWY INCURSION OCCURRED IN THIS CASE, BUT THERE WAS OBVIOUSLY A DIFFERENCE IN WHERE WE WERE AND WHERE THE GND CTLR EXPECTED US TO BE. FORTUNATELY, HE RECOGNIZED THIS BEFORE IT COULD BECOME A PROB AND ISSUED US ANOTHER CLRNC. ALTHOUGH WE MAINTAIN THAT WE WERE ON TXWY F, IT APPEARS THAT THE CTLR EXPECTED US TO BE ON TXWY F HDG SE HOLDING SHORT OF RWY 17R. FROM OUR PREBRIEF, WE EXPECTED TO CROSS THE RWY INTXNS OF RWYS 17R AND 29 AT TXWY F HDG NE. THERE WAS SOME DOUBT AS TO WHICH TXWY F HE WANTED US ON, WHICH IS WHY WE HELD WELL SHORT OF THE RWYS ON TXWY F TO ALLOW US TO GO EITHER WAY ON TXWY F. FREQ CONGESTION AND TKOF PREPARATIONS COMPLICATED CLARIFICATION. THIS AREA SHOULD BE DEPICTED AS A RWY INCURSION 'HOT SPOT.' THE AREA CAN BE CONFUSING, AND THE TAXI DIAGRAM IS NOT MUCH HELP. FOR EXAMPLE, THERE IS NO LETTER TO DESIGNATE THE TXWY NAME AT THE APCH END OF RWY 11. IT SEEMS THAT TXWY F WRAPS AROUND THE CORNER TO CROSS AT THE RWY INTXN. AT MOST OTHER ARPTS, PARALLEL TXWY NAMES ARE DIFFERENT THAN THE 90 DEG XING TXWY NAMES. NOT SO AT SDF. THIS NON-STANDARD NOMENCLATURE ADDS CONFUSION. DEPICTION OF TXWY LETTERING FURTHER COMPLICATES THIS ISSUE. FREQUENTLY, IT IS NOT CLR WHICH TXWY IS WHICH, WITHOUT USING THE PROCESS OF ELIMINATION. FOR EXAMPLE, THE 'B' JUST S OF RWY 11 AND E OF RWY 17R APPEARS TO REFER TO THE E/W TXWY. HOWEVER, IT EVIDENTLY IS REFERRING TO THE N/S TXWY. THERE IS NO OTHER 'B' ASSOCIATED WITH THIS N/S TXWY. THERE ARE 2 OTHER 'B'S,' BUT THEY REFER TO THE E/W 90 DEG RWY XING TXWYS AT EITHER END OF THE PARALLEL. THIS LENDS TO CONFUSION. IS THERE NOT A BETTER WAY TO DEPICT TXWY NAMES ON A CHART? ALTHOUGH IN THIS SIT, I DONT' BELIEVE WE HAD A RWY INCURSION, IT WAS DUE TO THE CTLR'S HEADS UP CALL THAT MAY HAVE PREVENTED ONE. A MORE COMPLETE BRIEFING OF THE CREW, TO INCLUDE POSSIBLE ALTERNATE TAXI RTES, AND WHAT INSTRUCTIONS COULD BE EXPECTED TO DIFFERENTIATE BTWN THE USE OF WHICH TXWY F, COULD ALSO HAVE HELPED PREVENT THIS OCCURRENCE. IMPROVED TAXI DIAGRAMS WOULD BE A GREAT AID IN MINIMIZING CONFUSION TO HELP PREVENT RWY INCURSIONS.

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.