LJ35 flight crew crosses PDT runway 29 before recognizing error.

Attributes
ACN	488503
Time
Date	200010
Place
Locale Reference	airport : pdt.airport
State Reference	OR
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Learjet 35
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	ground : taxi ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : atp pilot : commercial pilot : instrument
Experience	flight time last 90 days : 25 flight time total : 9500 flight time type : 2000
ASRS Report	488503
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Qualification	pilot : atp pilot : multi engine
Experience	flight time total : 170 flight time type : 170
ASRS Report	488668
Events
Anomaly	incursion : runway non adherence : clearance non adherence : published procedure non adherence : far
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was PIC, PNF. During taxi to runway 29, I was programming route into FMS while sic was taxiing from left seat. We were cleared to runway 29. My head was down and sic said 'are we clear to cross this runway?' I didn't think he could mean the active runway and thought he was referring to an intersecting runway. I said we were clear to cross. A moment later, I had a strange feeling about his question and looked up as we were just starting to cross runway 29. We continued across and I immediately notified the tower of what had happened. They cleared us for takeoff and we departed. There were no other aircraft operating in the airport's airspace, and no risk of collision occurred. I later asked the sic if he knew that was the active runway. He said 'yes' but thought we were supposed to cross and hold short on the other side. I reviewed taxi procedures from the aim with him. As PIC, I should have given more attention to the taxi situation and less to programming the FMS at that time.

Original NASA ASRS Text

Title: LJ35 FLC CROSSES PDT RWY 29 BEFORE RECOGNIZING ERROR.

Narrative: I WAS PIC, PNF. DURING TAXI TO RWY 29, I WAS PROGRAMMING RTE INTO FMS WHILE SIC WAS TAXIING FROM L SEAT. WE WERE CLRED TO RWY 29. MY HEAD WAS DOWN AND SIC SAID 'ARE WE CLR TO CROSS THIS RWY?' I DIDN'T THINK HE COULD MEAN THE ACTIVE RWY AND THOUGHT HE WAS REFERRING TO AN INTERSECTING RWY. I SAID WE WERE CLR TO CROSS. A MOMENT LATER, I HAD A STRANGE FEELING ABOUT HIS QUESTION AND LOOKED UP AS WE WERE JUST STARTING TO CROSS RWY 29. WE CONTINUED ACROSS AND I IMMEDIATELY NOTIFIED THE TWR OF WHAT HAD HAPPENED. THEY CLRED US FOR TKOF AND WE DEPARTED. THERE WERE NO OTHER ACFT OPERATING IN THE ARPT'S AIRSPACE, AND NO RISK OF COLLISION OCCURRED. I LATER ASKED THE SIC IF HE KNEW THAT WAS THE ACTIVE RWY. HE SAID 'YES' BUT THOUGHT WE WERE SUPPOSED TO CROSS AND HOLD SHORT ON THE OTHER SIDE. I REVIEWED TAXI PROCS FROM THE AIM WITH HIM. AS PIC, I SHOULD HAVE GIVEN MORE ATTN TO THE TAXI SIT AND LESS TO PROGRAMMING THE FMS AT THAT TIME.

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.