Runway incursion by a gii PIC when a taxi clearance was misunderstood for clearing across runway 25L...

Attributes
ACN	601733
Time
Date	200312
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	agl single value : 0
Environment
Flight Conditions	Mixed
Light	Night
Aircraft 1
Controlling Facilities	tower : lax.tower
Operator	common carrier : air taxi
Make Model Name	Gulfstream II
Operating Under FAR Part	Part 135
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : lax.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Navigation In Use	ils localizer & glide slope : 25l
Flight Phase	descent : approach landing : go around
Route In Use	approach : instrument precision
Person 1
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : flight engineer pilot : cfi pilot : atp
Experience	flight time last 90 days : 170 flight time total : 9500 flight time type : 900
ASRS Report	601733
Person 2
Affiliation	company : air taxi
Function	flight crew : first officer
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : clearance non adherence : far non adherence : required legal separation
Resolutory Action	controller : issued new clearance controller : separated traffic flight crew : executed go around
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I requested ground control for clearance to taxi from FBO to runway 25L. Lax ground control cleared me to taxi to runway 25L and hold short of taxiway F, ILS procedures were in effect. While holding short of taxiway F, I understood lax tower to clear me to taxi onto taxiway F and then hold short of runway 25R. Prior to taxiing onto taxiway F, I saw on approach an aircraft on final for either runway 25L or runway 25R. Therefore, I believed that the controller wanted me to taxi expeditiously across runway 25L to runway 25R, since a safe distance seemed to be available. I then proceeded to taxi onto taxiway F and across runway 25L towards runway 25R to hold short of runway 25R. Since ILS procedures were in effect, I did not expect tower to have me taxi onto taxiway F and hold short of runway 25L when an aircraft was in the process of landing and executing the ILS approach for runway 25L if the landing aircraft was too close. The tower then ordered the landing aircraft to go around.

Original NASA ASRS Text

Title: RWY INCURSION BY A GII PIC WHEN A TAXI CLRNC WAS MISUNDERSTOOD FOR CLRING ACROSS RWY 25L AT LAX, CA.

Narrative: I REQUESTED GND CTL FOR CLRNC TO TAXI FROM FBO TO RWY 25L. LAX GND CTL CLRED ME TO TAXI TO RWY 25L AND HOLD SHORT OF TXWY F, ILS PROCS WERE IN EFFECT. WHILE HOLDING SHORT OF TXWY F, I UNDERSTOOD LAX TWR TO CLR ME TO TAXI ONTO TXWY F AND THEN HOLD SHORT OF RWY 25R. PRIOR TO TAXIING ONTO TXWY F, I SAW ON APCH AN ACFT ON FINAL FOR EITHER RWY 25L OR RWY 25R. THEREFORE, I BELIEVED THAT THE CTLR WANTED ME TO TAXI EXPEDITIOUSLY ACROSS RWY 25L TO RWY 25R, SINCE A SAFE DISTANCE SEEMED TO BE AVAILABLE. I THEN PROCEEDED TO TAXI ONTO TXWY F AND ACROSS RWY 25L TOWARDS RWY 25R TO HOLD SHORT OF RWY 25R. SINCE ILS PROCS WERE IN EFFECT, I DID NOT EXPECT TWR TO HAVE ME TAXI ONTO TXWY F AND HOLD SHORT OF RWY 25L WHEN AN ACFT WAS IN THE PROCESS OF LNDG AND EXECUTING THE ILS APCH FOR RWY 25L IF THE LNDG ACFT WAS TOO CLOSE. THE TWR THEN ORDERED THE LNDG ACFT TO GO AROUND.

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.

Runway incursion by a gii PIC when a taxi clearance was misunderstood for clearing across runway 25L at lax, ca.