Narrative:

This event could be described as an inadvertent use of runway 4/22 in bwi to taxi out to the active runway 28. We pushed out of the gate and received instructions to 'taxi to runway 28.' so, we used taxiway east to taxiway P with the intent to continue on taxiway U out to runway 28. However, taxiway U was closed (we missed that on the ATIS). So, by that time, the airplane was on runway 4/22 and we made a left turn down runway 4/22 to taxiway C and then out to runway 28. I advised ground of our predicament, and while it was not a dangerous situation, it certainly highlighted our lack of situational awareness in and around a confusing complex of txwys/runways. Runway 4/22 was not being used for takeoffs and lndgs. Runway 33L/right was configured for landing, runway 28 configured for takeoff.

Google
 

Original NASA ASRS Text

Title: B737 CREW TAXIES ON RWY WITHOUT CLRNC AT BWI.

Narrative: THIS EVENT COULD BE DESCRIBED AS AN INADVERTENT USE OF RWY 4/22 IN BWI TO TAXI OUT TO THE ACTIVE RWY 28. WE PUSHED OUT OF THE GATE AND RECEIVED INSTRUCTIONS TO 'TAXI TO RWY 28.' SO, WE USED TXWY E TO TXWY P WITH THE INTENT TO CONTINUE ON TXWY U OUT TO RWY 28. HOWEVER, TXWY U WAS CLOSED (WE MISSED THAT ON THE ATIS). SO, BY THAT TIME, THE AIRPLANE WAS ON RWY 4/22 AND WE MADE A L TURN DOWN RWY 4/22 TO TXWY C AND THEN OUT TO RWY 28. I ADVISED GND OF OUR PREDICAMENT, AND WHILE IT WAS NOT A DANGEROUS SIT, IT CERTAINLY HIGHLIGHTED OUR LACK OF SITUATIONAL AWARENESS IN AND AROUND A CONFUSING COMPLEX OF TXWYS/RWYS. RWY 4/22 WAS NOT BEING USED FOR TKOFS AND LNDGS. RWY 33L/R WAS CONFIGURED FOR LNDG, RWY 28 CONFIGURED 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.