Cpr jet PIC taxies onto active runway at aus, thinking it is a parallel taxiway. Runway assignment h...

Attributes
ACN	364549
Time
Date	199703
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : aus
State Reference	TX
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Light Transport
Flight Phase	ground other : taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	climbout : takeoff
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 160 flight time total : 7000 flight time type : 52
ASRS Report	364549
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : clearance non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course flight crew : exited adverse environment flight crew : became reoriented
Consequence	Other
Miss Distance	horizontal : 4000 vertical : 500
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

The event was a runway incursion onto an active runway which was mistaken for a parallel taxiway. The chain of events leading to the incursion began when our passenger arrived. One passenger's family had been in a critical automatic accident in tyler, tx, (only 180 mi from austin). I agreed to drop him off on our way to lexington, ky, (our planned destination). After re-filing flight plans, I was anxious to get underway. Although we both felt rushed, I briefed the first officer not to hurry because we needed to get our passenger to tyler safely. I should have heeded my own advice. I began taxiing on the FBO ramp towards taxiway a. Austin local was working ground control also and was quite busy. We received taxi instructions for an inadequate runway (due to our takeoff weight). We then had to request another runway for takeoff with subsequent taxi instructions. By the time the last instructions were given I was crossing the taxiway I was supposed to make a right turn onto. I unintentionally turned right onto an active runway after crossing the aforementioned taxiway. I believed I was turning onto a parallel taxiway. The runway was small in width and knowing we were assigned a larger runway, I associated this smaller runway for a taxiway. Adding to my confusion was a lack of airport signs clearly marking txwys and runways hold short position. I do not recall seeing any hold short signs or markings on the taxiway. This confusion most likely resulted because the first officer and I were trying to figure out the taxi instructions while still moving. An airplane had just departed as we nosed onto the runway. I quickly taxied clear of the runway after realizing our predicament and proceeded normally thereafter. Anxiousness to get our passenger to tyler, ground and local on the same frequency and inadequate runway and taxiway markings contributed to this event. In the future, the best course of action would be to remain stationary until all taxi instructions are received and the airport layout is analyzed and understood.

Original NASA ASRS Text

Title: CPR JET PIC TAXIES ONTO ACTIVE RWY AT AUS, THINKING IT IS A PARALLEL TXWY. RWY ASSIGNMENT HAD BEEN CHANGED AND CTLR WAS WORKING 2 POS. PIC HAD A CERTAIN LEVEL OF ANXIETY REGARDING PAX ON BOARD.

Narrative: THE EVENT WAS A RWY INCURSION ONTO AN ACTIVE RWY WHICH WAS MISTAKEN FOR A PARALLEL TXWY. THE CHAIN OF EVENTS LEADING TO THE INCURSION BEGAN WHEN OUR PAX ARRIVED. ONE PAX'S FAMILY HAD BEEN IN A CRITICAL AUTO ACCIDENT IN TYLER, TX, (ONLY 180 MI FROM AUSTIN). I AGREED TO DROP HIM OFF ON OUR WAY TO LEXINGTON, KY, (OUR PLANNED DEST). AFTER RE-FILING FLT PLANS, I WAS ANXIOUS TO GET UNDERWAY. ALTHOUGH WE BOTH FELT RUSHED, I BRIEFED THE FO NOT TO HURRY BECAUSE WE NEEDED TO GET OUR PAX TO TYLER SAFELY. I SHOULD HAVE HEEDED MY OWN ADVICE. I BEGAN TAXIING ON THE FBO RAMP TOWARDS TXWY A. AUSTIN LCL WAS WORKING GND CTL ALSO AND WAS QUITE BUSY. WE RECEIVED TAXI INSTRUCTIONS FOR AN INADEQUATE RWY (DUE TO OUR TKOF WT). WE THEN HAD TO REQUEST ANOTHER RWY FOR TKOF WITH SUBSEQUENT TAXI INSTRUCTIONS. BY THE TIME THE LAST INSTRUCTIONS WERE GIVEN I WAS XING THE TXWY I WAS SUPPOSED TO MAKE A R TURN ONTO. I UNINTENTIONALLY TURNED R ONTO AN ACTIVE RWY AFTER XING THE AFOREMENTIONED TXWY. I BELIEVED I WAS TURNING ONTO A PARALLEL TXWY. THE RWY WAS SMALL IN WIDTH AND KNOWING WE WERE ASSIGNED A LARGER RWY, I ASSOCIATED THIS SMALLER RWY FOR A TXWY. ADDING TO MY CONFUSION WAS A LACK OF ARPT SIGNS CLRLY MARKING TXWYS AND RWYS HOLD SHORT POS. I DO NOT RECALL SEEING ANY HOLD SHORT SIGNS OR MARKINGS ON THE TXWY. THIS CONFUSION MOST LIKELY RESULTED BECAUSE THE FO AND I WERE TRYING TO FIGURE OUT THE TAXI INSTRUCTIONS WHILE STILL MOVING. AN AIRPLANE HAD JUST DEPARTED AS WE NOSED ONTO THE RWY. I QUICKLY TAXIED CLR OF THE RWY AFTER REALIZING OUR PREDICAMENT AND PROCEEDED NORMALLY THEREAFTER. ANXIOUSNESS TO GET OUR PAX TO TYLER, GND AND LCL ON THE SAME FREQ AND INADEQUATE RWY AND TXWY MARKINGS CONTRIBUTED TO THIS EVENT. IN THE FUTURE, THE BEST COURSE OF ACTION WOULD BE TO REMAIN STATIONARY UNTIL ALL TAXI INSTRUCTIONS ARE RECEIVED AND THE ARPT LAYOUT IS ANALYZED AND UNDERSTOOD.

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.

Cpr jet PIC taxies onto active runway at aus, thinking it is a parallel taxiway. Runway assignment had been changed and controller was working 2 position. PIC had a certain level of anxiety regarding passenger on board.