Narrative:

My first officer and myself were cleared to taxi to runway 17 from our gate at the terminal. During the taxi phase we went over our before taxi checklist and inadvertently taxied across runway 17 (which was active). The tower informed us of our mistake and we got a clearance to cross runway 17 and to taxi to runway 17 for takeoff. The main reason for the incursion was not being familiar with the layout of the wilmington airport and being preoccupied with the checklist. The way to correct the problem is to be familiar with the airport by having the layout open to reference for taxi before any checklist is being performed. During the time of the incursion, there was not any air traffic around the airport at all, so there was no conflict with other aircraft.

Related reports:

Google
 

Original NASA ASRS Text

Title: A COMMUTER FLC INADVERTENTLY TAXIED ONTO AN ACTIVE RWY. THE ATCT LCL CTLR INTERVENED AND CLRED THE CREW TO CROSS THE RWY, THEN TAXI TO THE DEP END OF THE SAME RWY.

Narrative: MY FO AND MYSELF WERE CLRED TO TAXI TO RWY 17 FROM OUR GATE AT THE TERMINAL. DURING THE TAXI PHASE WE WENT OVER OUR BEFORE TAXI CHKLIST AND INADVERTENTLY TAXIED ACROSS RWY 17 (WHICH WAS ACTIVE). THE TWR INFORMED US OF OUR MISTAKE AND WE GOT A CLRNC TO CROSS RWY 17 AND TO TAXI TO RWY 17 FOR TKOF. THE MAIN REASON FOR THE INCURSION WAS NOT BEING FAMILIAR WITH THE LAYOUT OF THE WILMINGTON ARPT AND BEING PREOCCUPIED WITH THE CHKLIST. THE WAY TO CORRECT THE PROB IS TO BE FAMILIAR WITH THE ARPT BY HAVING THE LAYOUT OPEN TO REF FOR TAXI BEFORE ANY CHKLIST IS BEING PERFORMED. DURING THE TIME OF THE INCURSION, THERE WAS NOT ANY AIR TFC AROUND THE ARPT AT ALL, SO THERE WAS NO CONFLICT WITH OTHER 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.