Misleading clearance from boi local controller causes near runway incursion by B737-300 flight crew.

Attributes
ACN	730574
Time
Date	200703
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : boi.airport
State Reference	ID
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 259 flight time type : 259
ASRS Report	730574
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 272 flight time type : 2014
ASRS Report	730467
Events
Anomaly	non adherence : clearance other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance
Supplementary
Problem Areas	Airport Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Approaching departure end of runway 10L at boi we were cleared to taxi across runway 10L on taxiway J and cleared for takeoff on runway 10R. One aircraft on about 6 mi final for runway 10L. As I made the turn on the taxiway at the approach end of runway 10L to taxi across runway 10L; I glanced down at the chart page and noticed that there is no way to taxi across runway 10L to runway 10R at the approach end of runway 10L. About the same time; the first officer started to say something about 'this isn't juliet;' so I immediately stopped the aircraft. We were still short of the hold short line; but unable to turn around to get back on taxiway J without entering runway 10L to do so. I advised tower of this. He switched the landing aircraft to runway 10R and cleared us to take off on runway 10L. This situation could have been avoided if the tower controller had said; 'taxi across the approach end of runway 10L;' and not; 'across the runway on juliet.' we did not cross the hold short line but came very close. More precise and standard terminology by tower controller.

Original NASA ASRS Text

Title: MISLEADING CLRNC FROM BOI LCL CTLR CAUSES NEAR RWY INCURSION BY B737-300 FLT CREW.

Narrative: APCHING DEP END OF RWY 10L AT BOI WE WERE CLRED TO TAXI ACROSS RWY 10L ON TXWY J AND CLRED FOR TKOF ON RWY 10R. ONE ACFT ON ABOUT 6 MI FINAL FOR RWY 10L. AS I MADE THE TURN ON THE TXWY AT THE APCH END OF RWY 10L TO TAXI ACROSS RWY 10L; I GLANCED DOWN AT THE CHART PAGE AND NOTICED THAT THERE IS NO WAY TO TAXI ACROSS RWY 10L TO RWY 10R AT THE APCH END OF RWY 10L. ABOUT THE SAME TIME; THE FO STARTED TO SAY SOMETHING ABOUT 'THIS ISN'T JULIET;' SO I IMMEDIATELY STOPPED THE ACFT. WE WERE STILL SHORT OF THE HOLD SHORT LINE; BUT UNABLE TO TURN AROUND TO GET BACK ON TXWY J WITHOUT ENTERING RWY 10L TO DO SO. I ADVISED TWR OF THIS. HE SWITCHED THE LNDG ACFT TO RWY 10R AND CLRED US TO TAKE OFF ON RWY 10L. THIS SITUATION COULD HAVE BEEN AVOIDED IF THE TWR CTLR HAD SAID; 'TAXI ACROSS THE APCH END OF RWY 10L;' AND NOT; 'ACROSS THE RWY ON JULIET.' WE DID NOT CROSS THE HOLD SHORT LINE BUT CAME VERY CLOSE. MORE PRECISE AND STANDARD TERMINOLOGY BY TWR CTLR.

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