Narrative:

While taxiing for departure first officer informed me we didn't have data (field/runway analysis for requested runway), which really surprised me because we had just landed on the same runway (28). At that time it became apparent that flight crew communication was very poor. Ground informed us that indeed we had taxied to runway 28, our original request, and that if we could make a 180 degree turn we could cross runway 1/19 and make a left for new (runway 1) departure runway. Ground was very helpful, professional and polite, after reaching the correct runway for departure I, as PIC, took a few moments to brief the new hire, first officer, with all of the CRM tact and skill I could muster that I felt he and I were not paying enough attention to ATC instructions, and we would not do any more checklists while taxiing, which is SOP. I feel the combination of anew first officer and new destination for me was very hard work although WX was good, I elected to fly, as PF, in retrospect, I would have had him fly. One suggestion for improvement, fos and capts should have to complete some training before going into new cities, or something similar to proving runs be carried out with 2 capts initially into new cities. Callback conversation with reporter revealed the following information: this was first time into altitude for PIC and first officer. Runway data for that aircraft on runway 28 was not yet given to flcs of that type aircraft. It was legal for them to land on 28, but they did not know that at the time. Reporter was PIC and says he got very upset when first officer told him they did not have the data. Stopped taxi short of runway 1/19 and asked for runway 1 assignment for takeoff. Tower controller changed runway to runway 1 but PIC, still thinking runway 28 for some reason, taxied across runway 1 instead of making right turn on taxiway 'a'. Says no conflicting traffic and ATC did not pursue the incident. Tower cleared them to recross runway 1 to get back on correct taxiway. First officer was new to company and type aircraft.

Related reports:

Google
 

Original NASA ASRS Text

Title: UNAUTHORIZED RWY CROSSING BY COMMUTER.

Narrative: WHILE TAXIING FOR DEP FO INFORMED ME WE DIDN'T HAVE DATA (FIELD/RWY ANALYSIS FOR REQUESTED RWY), WHICH REALLY SURPRISED ME BECAUSE WE HAD JUST LANDED ON THE SAME RWY (28). AT THAT TIME IT BECAME APPARENT THAT FLC COM WAS VERY POOR. GND INFORMED US THAT INDEED WE HAD TAXIED TO RWY 28, OUR ORIGINAL REQUEST, AND THAT IF WE COULD MAKE A 180 DEG TURN WE COULD CROSS RWY 1/19 AND MAKE A L FOR NEW (RWY 1) DEP RWY. GND WAS VERY HELPFUL, PROFESSIONAL AND POLITE, AFTER REACHING THE CORRECT RWY FOR DEP I, AS PIC, TOOK A FEW MOMENTS TO BRIEF THE NEW HIRE, FO, WITH ALL OF THE CRM TACT AND SKILL I COULD MUSTER THAT I FELT HE AND I WERE NOT PAYING ENOUGH ATTN TO ATC INSTRUCTIONS, AND WE WOULD NOT DO ANY MORE CHKLISTS WHILE TAXIING, WHICH IS SOP. I FEEL THE COMBINATION OF ANEW FO AND NEW DEST FOR ME WAS VERY HARD WORK ALTHOUGH WX WAS GOOD, I ELECTED TO FLY, AS PF, IN RETROSPECT, I WOULD HAVE HAD HIM FLY. ONE SUGGESTION FOR IMPROVEMENT, FOS AND CAPTS SHOULD HAVE TO COMPLETE SOME TRAINING BEFORE GOING INTO NEW CITIES, OR SOMETHING SIMILAR TO PROVING RUNS BE CARRIED OUT WITH 2 CAPTS INITIALLY INTO NEW CITIES. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THIS WAS FIRST TIME INTO ALT FOR PIC AND FO. RWY DATA FOR THAT ACFT ON RWY 28 WAS NOT YET GIVEN TO FLCS OF THAT TYPE ACFT. IT WAS LEGAL FOR THEM TO LAND ON 28, BUT THEY DID NOT KNOW THAT AT THE TIME. RPTR WAS PIC AND SAYS HE GOT VERY UPSET WHEN FO TOLD HIM THEY DID NOT HAVE THE DATA. STOPPED TAXI SHORT OF RWY 1/19 AND ASKED FOR RWY 1 ASSIGNMENT FOR TKOF. TWR CTLR CHANGED RWY TO RWY 1 BUT PIC, STILL THINKING RWY 28 FOR SOME REASON, TAXIED ACROSS RWY 1 INSTEAD OF MAKING R TURN ON TAXIWAY 'A'. SAYS NO CONFLICTING TFC AND ATC DID NOT PURSUE THE INCIDENT. TWR CLRED THEM TO RECROSS RWY 1 TO GET BACK ON CORRECT TAXIWAY. FO WAS NEW TO COMPANY AND TYPE ACFT.

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.