The flight crew taxied the DC9 contrary to ground control instructions.

Attributes
ACN	326143
Time
Date	199601
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bhm
State Reference	AL
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	DC-9 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground other : 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 : 60 flight time total : 17800 flight time type : 9000
ASRS Report	326143
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 16000 flight time type : 3000
ASRS Report	326693
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
Airport	other physical facility

Narrative:

Runway incursion of runway 18/36 while taxiing for full length of runway 23 at birmingham, al. Ground clearance was to taxi to runway 23 via txwys a and A5. Approaching taxiway A5 the first officer switched to tower and reminded me (captain) that the takeoff data was based on full length. I incorrectly started taxiing down taxiway north. I realized my mistake and the first officer agreed. I called the tower and told them where I was, I had made a mistake, and could I turn left on runway 18/36 to get up to runway 23. The tower asked if I was on runway 18/36 yet and I told them I was just coming on to the runway (we, the crew had cleared both ways and there was no traffic on the runway or on final for runway 18/36). Tower said to proceed across runway 18/36 on taxiway north and go back to ground control. Ground control told us to make a 180 degree in the ramp, go back out taxiway north to taxiway A5. We went back to taxiway A5, checked the takeoff numbers manually in the book for an intersection takeoff from taxiway A5 with approximately 8000 ft of runway. I determined we were legal so we took off from the intersection at taxiway A5 for runway 23. Comments: runway 23 was the primary runway, no gars or traffic conflicts occurred on runway 18/36. I notified the tower of my mistake and was in radio contact with the tower and under their directions to continue across their secondary (but active) runway 18/36. Total exposure time on runway 18/36 was about 5 seconds. Since most aircraft using runway 23 takeoff from taxiway A5 no 'hold short of runway 18/36' instructions were given since my incorrectly starting down taxiway north to use full length of runway 23 was non-standard. Recommendations: when ground issues taxi clearance they say 'cleared to runway 23 intersection departure via txwys a and A5. Runway length from taxiway A5 is 8000 ft.' birmingham put up a large sign at entrance to taxiway north from taxiway a saying 'restr taxiway' or some other notation so no one else will use taxiway north to get to full length of runway 23 for takeoff.

Original NASA ASRS Text

Title: THE FLC TAXIED THE DC9 CONTRARY TO GND CTL INSTRUCTIONS.

Narrative: RWY INCURSION OF RWY 18/36 WHILE TAXIING FOR FULL LENGTH OF RWY 23 AT BIRMINGHAM, AL. GND CLRNC WAS TO TAXI TO RWY 23 VIA TXWYS A AND A5. APCHING TXWY A5 THE FO SWITCHED TO TWR AND REMINDED ME (CAPT) THAT THE TKOF DATA WAS BASED ON FULL LENGTH. I INCORRECTLY STARTED TAXIING DOWN TXWY N. I REALIZED MY MISTAKE AND THE FO AGREED. I CALLED THE TWR AND TOLD THEM WHERE I WAS, I HAD MADE A MISTAKE, AND COULD I TURN L ON RWY 18/36 TO GET UP TO RWY 23. THE TWR ASKED IF I WAS ON RWY 18/36 YET AND I TOLD THEM I WAS JUST COMING ON TO THE RWY (WE, THE CREW HAD CLRED BOTH WAYS AND THERE WAS NO TFC ON THE RWY OR ON FINAL FOR RWY 18/36). TWR SAID TO PROCEED ACROSS RWY 18/36 ON TXWY N AND GO BACK TO GND CTL. GND CTL TOLD US TO MAKE A 180 DEG IN THE RAMP, GO BACK OUT TXWY N TO TXWY A5. WE WENT BACK TO TXWY A5, CHKED THE TKOF NUMBERS MANUALLY IN THE BOOK FOR AN INTXN TKOF FROM TXWY A5 WITH APPROX 8000 FT OF RWY. I DETERMINED WE WERE LEGAL SO WE TOOK OFF FROM THE INTXN AT TXWY A5 FOR RWY 23. COMMENTS: RWY 23 WAS THE PRIMARY RWY, NO GARS OR TFC CONFLICTS OCCURRED ON RWY 18/36. I NOTIFIED THE TWR OF MY MISTAKE AND WAS IN RADIO CONTACT WITH THE TWR AND UNDER THEIR DIRECTIONS TO CONTINUE ACROSS THEIR SECONDARY (BUT ACTIVE) RWY 18/36. TOTAL EXPOSURE TIME ON RWY 18/36 WAS ABOUT 5 SECONDS. SINCE MOST ACFT USING RWY 23 TKOF FROM TXWY A5 NO 'HOLD SHORT OF RWY 18/36' INSTRUCTIONS WERE GIVEN SINCE MY INCORRECTLY STARTING DOWN TXWY N TO USE FULL LENGTH OF RWY 23 WAS NON-STANDARD. RECOMMENDATIONS: WHEN GND ISSUES TAXI CLRNC THEY SAY 'CLRED TO RWY 23 INTXN DEP VIA TXWYS A AND A5. RWY LENGTH FROM TXWY A5 IS 8000 FT.' BIRMINGHAM PUT UP A LARGE SIGN AT ENTRANCE TO TXWY N FROM TXWY A SAYING 'RESTR TXWY' OR SOME OTHER NOTATION SO NO ONE ELSE WILL USE TXWY N TO GET TO FULL LENGTH OF RWY 23 FOR TKOF.

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.