Large transport taxied onto active runway while taxiing for takeoff. Runway incursion.

Attributes
ACN	294682
Time
Date	199501
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bwi
State Reference	MD
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : msp
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
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 : 200 flight time total : 10000 flight time type : 2500
ASRS Report	294682
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : atp
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : became reoriented other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After pushback flight was given taxi instructions to runway 33 to cross runway 28. Outbound, ground said that runway 28 was available for takeoff and we elected it with instructions to cross runway 22 en route via outer. At the 'south' turn turning to parallel runway 28, I picked up runway 22 identify sign with the turn but followed the yellow taxi line that crossed runway 28 toward runway 33 takeoff end. Saw air carrier B taking position on runway 33 and followed, entering runway 28. Ground advised that we were heading to runway 33 as we crossed runway 28 by mistake and ask if we could use runway 33. We confirmed. We were in the process of doing checklist and confirming weights. Both captain and first officer checked both ways and 'reported' no traffic to each other before crossing the wrong runway. Same barricade on the left were noted prior to turn to cross runway 28. Controller did not seem concerned, probably because there was no conflicting traffic. Taxi instructions were clear but disorientation occurred due to checklist and perhaps air carrier B ahead taking off on runway 33. Seemed 'logical' to follow, because of the intersection of 3 runways near that point 'hold short instruction probably better than 'taxi to!' captain had not been to bwi for quite a while!

Original NASA ASRS Text

Title: LGT TAXIED ONTO ACTIVE RWY WHILE TAXIING FOR TKOF. RWY INCURSION.

Narrative: AFTER PUSHBACK FLT WAS GIVEN TAXI INSTRUCTIONS TO RWY 33 TO CROSS RWY 28. OUTBOUND, GND SAID THAT RWY 28 WAS AVAILABLE FOR TKOF AND WE ELECTED IT WITH INSTRUCTIONS TO CROSS RWY 22 ENRTE VIA OUTER. AT THE 'S' TURN TURNING TO PARALLEL RWY 28, I PICKED UP RWY 22 IDENT SIGN WITH THE TURN BUT FOLLOWED THE YELLOW TAXI LINE THAT CROSSED RWY 28 TOWARD RWY 33 TKOF END. SAW ACR B TAKING POS ON RWY 33 AND FOLLOWED, ENTERING RWY 28. GND ADVISED THAT WE WERE HEADING TO RWY 33 AS WE CROSSED RWY 28 BY MISTAKE AND ASK IF WE COULD USE RWY 33. WE CONFIRMED. WE WERE IN THE PROCESS OF DOING CHKLIST AND CONFIRMING WTS. BOTH CAPT AND FO CHKED BOTH WAYS AND 'RPTED' NO TFC TO EACH OTHER BEFORE XING THE WRONG RWY. SAME BARRICADE ON THE L WERE NOTED PRIOR TO TURN TO CROSS RWY 28. CTLR DID NOT SEEM CONCERNED, PROBABLY BECAUSE THERE WAS NO CONFLICTING TFC. TAXI INSTRUCTIONS WERE CLR BUT DISORIENTATION OCCURRED DUE TO CHKLIST AND PERHAPS ACR B AHEAD TAKING OFF ON RWY 33. SEEMED 'LOGICAL' TO FOLLOW, BECAUSE OF THE INTXN OF 3 RWYS NEAR THAT POINT 'HOLD SHORT INSTRUCTION PROBABLY BETTER THAN 'TAXI TO!' CAPT HAD NOT BEEN TO BWI FOR QUITE A WHILE!

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.