F100 crew had runway incursion on taxi out at clt.

Attributes
ACN	493481
Time
Date	200011
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : clt.airport
State Reference	NC
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Fokker 100
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 160 flight time total : 10000 flight time type : 700
ASRS Report	493481
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 3500 flight time type : 700
ASRS Report	493480
Events
Anomaly	incursion : runway non adherence : clearance non adherence : company policies non adherence : far non adherence : published procedure other anomaly other
Independent Detector	other controllera other flight crewa other flight crewb
Resolutory Action	controller : issued alert none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Received clearance to taxi to spot and expect runway 18L. Taxied to spot, then turned right onto taxiway G. I confirmed with the first officer that runway 5/23 and its approach areas were clear. Proceeded across runway 23. Total absence of any other traffic lured us to continue to cross. Ground controller asked us where we were going. It was at that point that we realized what we had done. To our knowledge, ATC had no traffic or diversions caused by our crossing. Our crossing of runway 5/23, rather than taxiing to runway 18L, was unintentional. ATC was using runway 36R earlier, although the most important contributing factor was that when taxiing to spot, takeoff is usually on runway 36R. Generally, when using runway 18L, taxi instructions are to taxi to another spot.

Original NASA ASRS Text

Title: F100 CREW HAD RWY INCURSION ON TAXI OUT AT CLT.

Narrative: RECEIVED CLRNC TO TAXI TO SPOT AND EXPECT RWY 18L. TAXIED TO SPOT, THEN TURNED R ONTO TXWY G. I CONFIRMED WITH THE FO THAT RWY 5/23 AND ITS APCH AREAS WERE CLR. PROCEEDED ACROSS RWY 23. TOTAL ABSENCE OF ANY OTHER TFC LURED US TO CONTINUE TO CROSS. GND CTLR ASKED US WHERE WE WERE GOING. IT WAS AT THAT POINT THAT WE REALIZED WHAT WE HAD DONE. TO OUR KNOWLEDGE, ATC HAD NO TFC OR DIVERSIONS CAUSED BY OUR XING. OUR XING OF RWY 5/23, RATHER THAN TAXIING TO RWY 18L, WAS UNINTENTIONAL. ATC WAS USING RWY 36R EARLIER, ALTHOUGH THE MOST IMPORTANT CONTRIBUTING FACTOR WAS THAT WHEN TAXIING TO SPOT, TKOF IS USUALLY ON RWY 36R. GENERALLY, WHEN USING RWY 18L, TAXI INSTRUCTIONS ARE TO TAXI TO ANOTHER SPOT.

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.