Narrative:

Nov/wed/01 at yip. Several exchanges with clearance, sic communicating, to obtain clearance and also several exchanges with ground control for taxi instructions. I understood that we were to taxi via runway 9L for departure runway 27R. This, however, turned out to be in error. I was to taxi via runway 9L for departure on runway 23R. No parallel txwys exist, so must taxi on a runway with pre taxi checks and programming FMS. Taxied across threshold end of runway 23R&left, thus, a runway incursion situation. Ground control informed that I had taxied across active runways. Stated that I thought that I was cleared for taxi for a runway 27R departure (was actually runway 23R). Was asked to do 180 degree turn when ready for takeoff. Was cleared to depart on runway 23L. At unfamiliar airports, especially with less than usual runway/taxiway layouts, maybe clarify instructions an additional time so that inadvertent incursions can be reduced. Supplemental information from acn 530457: I was told to program all the waypoints into the FMS. While doing this, my head was down and inside. The next thing that happened was I heard ground calling and asking if we were on ground control frequency. The PIC responded with 'yes.' the controller then said we had taxied across an active runway. I discussed incident with aviation department head. From now on, aircraft does not move until FMS is programmed -- period. If at unfamiliar airport, ask for progressive taxi unless completely sure of airport taxi diagram. Would suggest that if ground control observes an aircraft approaching a runway at night and the aircraft was to have turned onto a taxiway prior to the runway, it seems as though they could issue a question call, notwithstanding the undisputed fact that it is the aircraft crew's responsibility to do a correct taxi operation.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN LTT CREW, TAXIING FOR TKOF AT YIP, CROSSED 2 PARALLEL RWYS WITHOUT CLRNC.

Narrative: NOV/WED/01 AT YIP. SEVERAL EXCHANGES WITH CLRNC, SIC COMMUNICATING, TO OBTAIN CLRNC AND ALSO SEVERAL EXCHANGES WITH GND CTL FOR TAXI INSTRUCTIONS. I UNDERSTOOD THAT WE WERE TO TAXI VIA RWY 9L FOR DEP RWY 27R. THIS, HOWEVER, TURNED OUT TO BE IN ERROR. I WAS TO TAXI VIA RWY 9L FOR DEP ON RWY 23R. NO PARALLEL TXWYS EXIST, SO MUST TAXI ON A RWY WITH PRE TAXI CHKS AND PROGRAMMING FMS. TAXIED ACROSS THRESHOLD END OF RWY 23R&L, THUS, A RWY INCURSION SIT. GND CTL INFORMED THAT I HAD TAXIED ACROSS ACTIVE RWYS. STATED THAT I THOUGHT THAT I WAS CLRED FOR TAXI FOR A RWY 27R DEP (WAS ACTUALLY RWY 23R). WAS ASKED TO DO 180 DEG TURN WHEN READY FOR TKOF. WAS CLRED TO DEPART ON RWY 23L. AT UNFAMILIAR ARPTS, ESPECIALLY WITH LESS THAN USUAL RWY/TXWY LAYOUTS, MAYBE CLARIFY INSTRUCTIONS AN ADDITIONAL TIME SO THAT INADVERTENT INCURSIONS CAN BE REDUCED. SUPPLEMENTAL INFO FROM ACN 530457: I WAS TOLD TO PROGRAM ALL THE WAYPOINTS INTO THE FMS. WHILE DOING THIS, MY HEAD WAS DOWN AND INSIDE. THE NEXT THING THAT HAPPENED WAS I HEARD GND CALLING AND ASKING IF WE WERE ON GND CTL FREQ. THE PIC RESPONDED WITH 'YES.' THE CTLR THEN SAID WE HAD TAXIED ACROSS AN ACTIVE RWY. I DISCUSSED INCIDENT WITH AVIATION DEPT HEAD. FROM NOW ON, ACFT DOES NOT MOVE UNTIL FMS IS PROGRAMMED -- PERIOD. IF AT UNFAMILIAR ARPT, ASK FOR PROGRESSIVE TAXI UNLESS COMPLETELY SURE OF ARPT TAXI DIAGRAM. WOULD SUGGEST THAT IF GND CTL OBSERVES AN ACFT APCHING A RWY AT NIGHT AND THE ACFT WAS TO HAVE TURNED ONTO A TXWY PRIOR TO THE RWY, IT SEEMS AS THOUGH THEY COULD ISSUE A QUESTION CALL, NOTWITHSTANDING THE UNDISPUTED FACT THAT IT IS THE ACFT CREW'S RESPONSIBILITY TO DO A CORRECT TAXI OP.

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.