Narrative:

We were taxiing to runway 28 when ground told us to turn right at echo, join the outer, cross runway 22, hold short of runway 28. Both pilots confirmed the instruction with each other and made the turn at echo which put us facing a southwest runway which we both thought was runway 22. We did not see any signs indicating that the runway was in fact runway 28. 1/2 way across the runway we realized we were crossing the wrong runway. Bwi has a lot of construction going on which is changing the normal taxi rtes. The area we crossed runway 28 has 3 runways crossing each other making it difficult to distinguish one from another. Another factor involved was a lack of rest for both crew members. I had just come off a 16 day vacation which I spent on the west coast. Because my body was still adjusted to west coast time, I was unable to get to sleep until about XA00 O'clock am. I then had a 0b15 get up to make the 0c40 show. My copilot's wife (a flight attendant) came home about XX00 waking him. He was unable to get back to sleep until about XA00. Supplemental information from acn 285904: factors that contributed to our confusion included recent and ongoing construction on txwys and runways, recent change in airport signs, distraction of running checklist (my head was down for the right turn onto echo taxiway), and confusion of following air carrier a (who was taxiing for runway 33L which was not broadcast on ATIS as a departure runway). We had just flown in from iad and landed on runway 33L. This flight was from bwi to iad. Also, contributing was question over our airport diagram as we both questioned (right before the incident/incursion) the validity of our chart, as it appeared new txwys had been constructed. Chart date was aug/xx/94, I don't recall seeing the runway 28 sign at the echo intersection, although it might probably be there. No one had to abort a takeoff or go around as the result of our action. Moral of the story -- when in doubt, stop the aircraft, get further actions by ATC or ask for progressive instructions!

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC TAXIED ACROSS WRONG RWY.

Narrative: WE WERE TAXIING TO RWY 28 WHEN GND TOLD US TO TURN R AT ECHO, JOIN THE OUTER, CROSS RWY 22, HOLD SHORT OF RWY 28. BOTH PLTS CONFIRMED THE INSTRUCTION WITH EACH OTHER AND MADE THE TURN AT ECHO WHICH PUT US FACING A SW RWY WHICH WE BOTH THOUGHT WAS RWY 22. WE DID NOT SEE ANY SIGNS INDICATING THAT THE RWY WAS IN FACT RWY 28. 1/2 WAY ACROSS THE RWY WE REALIZED WE WERE XING THE WRONG RWY. BWI HAS A LOT OF CONSTRUCTION GOING ON WHICH IS CHANGING THE NORMAL TAXI RTES. THE AREA WE CROSSED RWY 28 HAS 3 RWYS XING EACH OTHER MAKING IT DIFFICULT TO DISTINGUISH ONE FROM ANOTHER. ANOTHER FACTOR INVOLVED WAS A LACK OF REST FOR BOTH CREW MEMBERS. I HAD JUST COME OFF A 16 DAY VACATION WHICH I SPENT ON THE WEST COAST. BECAUSE MY BODY WAS STILL ADJUSTED TO WEST COAST TIME, I WAS UNABLE TO GET TO SLEEP UNTIL ABOUT XA00 O'CLOCK AM. I THEN HAD A 0B15 GET UP TO MAKE THE 0C40 SHOW. MY COPLT'S WIFE (A FLT ATTENDANT) CAME HOME ABOUT XX00 WAKING HIM. HE WAS UNABLE TO GET BACK TO SLEEP UNTIL ABOUT XA00. SUPPLEMENTAL INFO FROM ACN 285904: FACTORS THAT CONTRIBUTED TO OUR CONFUSION INCLUDED RECENT AND ONGOING CONSTRUCTION ON TXWYS AND RWYS, RECENT CHANGE IN ARPT SIGNS, DISTR OF RUNNING CHKLIST (MY HEAD WAS DOWN FOR THE R TURN ONTO ECHO TXWY), AND CONFUSION OF FOLLOWING ACR A (WHO WAS TAXIING FOR RWY 33L WHICH WAS NOT BROADCAST ON ATIS AS A DEP RWY). WE HAD JUST FLOWN IN FROM IAD AND LANDED ON RWY 33L. THIS FLT WAS FROM BWI TO IAD. ALSO, CONTRIBUTING WAS QUESTION OVER OUR ARPT DIAGRAM AS WE BOTH QUESTIONED (RIGHT BEFORE THE INCIDENT/INCURSION) THE VALIDITY OF OUR CHART, AS IT APPEARED NEW TXWYS HAD BEEN CONSTRUCTED. CHART DATE WAS AUG/XX/94, I DON'T RECALL SEEING THE RWY 28 SIGN AT THE ECHO INTXN, ALTHOUGH IT MIGHT PROBABLY BE THERE. NO ONE HAD TO ABORT A TKOF OR GAR AS THE RESULT OF OUR ACTION. MORAL OF THE STORY -- WHEN IN DOUBT, STOP THE ACFT, GET FURTHER ACTIONS BY ATC OR ASK FOR PROGRESSIVE INSTRUCTIONS!

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.