Flight crew of an air carrier light transport aircraft inadvertently transgressed a parallel runway ...

Attributes
ACN	242506
Time
Date	199305
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lax
State Reference	CA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	ground other : taxi landing other
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	other
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 3367 flight time type : 1141
ASRS Report	242506
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 25 flight time total : 2350 flight time type : 30
ASRS Report	242659
Events
Anomaly	conflict : ground critical incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact none taken : insufficient time
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 5000 vertical : 0
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On may/xx/93 we were on our way to bullhead city, az (P06) from farmington, NM, on a maintenance flight. About 1/2 way to bullhead city our company reached us and told us to continue on to lax. Upon reaching lax and landing on runway 25L I stated to the tower controller that we were unfamiliar and needed to know which way to turn off the runway for the terminal. The controller told us to take the next right high speed exit. As we started to turn, he came back and told us to expedite to the next left reverse high speed because of traffic short final behind us. Up until this point my first officer had control of the airplane. I took the airplane from him and started to power up a bit to expedite to the next left reverse high speed, which appeared to be 1000-2000 ft down the runway. As we were expediting the controller told us instead to take the next right high speed and hold short of runway 25R due to the fact that the traffic behind us was now on very short final. I acknowledged and started to turn right on the high speed exit which we were almost adjacent to. I put the airplane in full beta, got on the brakes and did stop well short of the runway. I believe we stopped prior to the hold bars, however, the controller had the aircraft departing runway 25R abort its takeoff and then told us to continue across runway 25R and into parking. We had informed the controller that we were unfamiliar and in return were told 3 different exit instructions 3 different times. This, coupled with finally having to expedite onto a high speed exit that ended abruptly at the parallel runway, contributed to the problem. In trying to accommodate us, the controller only added to the confusion. We did our best to accommodate him and to clear the runway as soon as possible, aware that we had traffic landing somewhere behind us. Perhaps we both should have paid more attention to the fact that we were at an unfamiliar, busy airport, and required extra time and handling.

Original NASA ASRS Text

Title: FLC OF AN ACR LTT ACFT INADVERTENTLY TRANSGRESSED A PARALLEL RWY DURING ROLLOUT AFTER LNDG ON THE OTHER PARALLEL RWY CAUSING ANOTHER ACFT TO BE ABORTED BY ATC FOR SAFETY PRECAUTIONS.

Narrative: ON MAY/XX/93 WE WERE ON OUR WAY TO BULLHEAD CITY, AZ (P06) FROM FARMINGTON, NM, ON A MAINT FLT. ABOUT 1/2 WAY TO BULLHEAD CITY OUR COMPANY REACHED US AND TOLD US TO CONTINUE ON TO LAX. UPON REACHING LAX AND LNDG ON RWY 25L I STATED TO THE TWR CTLR THAT WE WERE UNFAMILIAR AND NEEDED TO KNOW WHICH WAY TO TURN OFF THE RWY FOR THE TERMINAL. THE CTLR TOLD US TO TAKE THE NEXT R HIGH SPD EXIT. AS WE STARTED TO TURN, HE CAME BACK AND TOLD US TO EXPEDITE TO THE NEXT L REVERSE HIGH SPD BECAUSE OF TFC SHORT FINAL BEHIND US. UP UNTIL THIS POINT MY FO HAD CTL OF THE AIRPLANE. I TOOK THE AIRPLANE FROM HIM AND STARTED TO PWR UP A BIT TO EXPEDITE TO THE NEXT L REVERSE HIGH SPD, WHICH APPEARED TO BE 1000-2000 FT DOWN THE RWY. AS WE WERE EXPEDITING THE CTLR TOLD US INSTEAD TO TAKE THE NEXT R HIGH SPD AND HOLD SHORT OF RWY 25R DUE TO THE FACT THAT THE TFC BEHIND US WAS NOW ON VERY SHORT FINAL. I ACKNOWLEDGED AND STARTED TO TURN R ON THE HIGH SPD EXIT WHICH WE WERE ALMOST ADJACENT TO. I PUT THE AIRPLANE IN FULL BETA, GOT ON THE BRAKES AND DID STOP WELL SHORT OF THE RWY. I BELIEVE WE STOPPED PRIOR TO THE HOLD BARS, HOWEVER, THE CTLR HAD THE ACFT DEPARTING RWY 25R ABORT ITS TKOF AND THEN TOLD US TO CONTINUE ACROSS RWY 25R AND INTO PARKING. WE HAD INFORMED THE CTLR THAT WE WERE UNFAMILIAR AND IN RETURN WERE TOLD 3 DIFFERENT EXIT INSTRUCTIONS 3 DIFFERENT TIMES. THIS, COUPLED WITH FINALLY HAVING TO EXPEDITE ONTO A HIGH SPD EXIT THAT ENDED ABRUPTLY AT THE PARALLEL RWY, CONTRIBUTED TO THE PROB. IN TRYING TO ACCOMMODATE US, THE CTLR ONLY ADDED TO THE CONFUSION. WE DID OUR BEST TO ACCOMMODATE HIM AND TO CLR THE RWY ASAP, AWARE THAT WE HAD TFC LNDG SOMEWHERE BEHIND US. PERHAPS WE BOTH SHOULD HAVE PAID MORE ATTN TO THE FACT THAT WE WERE AT AN UNFAMILIAR, BUSY ARPT, AND REQUIRED EXTRA TIME AND HANDLING.

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.

Flight crew of an air carrier light transport aircraft inadvertently transgressed a parallel runway during rollout after landing on the other parallel runway causing another aircraft to be aborted by ATC for safety precautions.