Narrative:

After blockout, aircraft developed mechanical. We positioned our aircraft on a terminal ramp with engines running while waiting for maintenance personnel, to respond to radio calls. After resolving maintenance problem, it was decided to continue with flight. While still parked, captain was talking to ground on communication #1 about WX in the area while first officer was sending message to company via ACARS while simultaneously on communication #2 talking with local maintenance personnel. At some point, captain asked ground to continue taxi to runway 25 (rfd) and apparently did not realize first officer was still on communication #2 not listening and preoccupied with typing message on ACARS. With head down, first officer did not realize aircraft was under movement towards active runway. Captain taxied aircraft towards what appeared to be taxiway F but actually ended up being an active runway. First officer lifted head up and noticed runway edge markings approaching and requested immediate stop. At this point aircraft was protruding past the hold line and encroaching on runway 25. We notified ground and was given back taxi instructions as there were no aircraft using the runway or in the vicinity. Factors included: poor taxiway markings, light rain, crew not working together, fatigue (7 hour 30 min block flying night). Captain thought that taxi lights ahead were the entrance to taxiway F. In fact, in that portion of ramp area there are no lights signifying other edge of taxiway F.

Related reports:

Google
 

Original NASA ASRS Text

Title: B757 CAPT MISTAKENLY STARTED TAXIING ONTO ACTIVE RWY AFTER GND HOLDING WHEN FO LOOKED UP AND NOTICED MISTAKE AND CALLED FOR STOPPING THE ACFT BEFORE IT WENT ONTO THE RWY. AFTER NOTIFYING GND CTL OF THEIR ERROR, THEY WERE GIVEN BACK-TAXI INSTRUCTIONS ON THE RWY.

Narrative: AFTER BLOCKOUT, ACFT DEVELOPED MECHANICAL. WE POSITIONED OUR ACFT ON A TERMINAL RAMP WITH ENGS RUNNING WHILE WAITING FOR MAINT PERSONNEL, TO RESPOND TO RADIO CALLS. AFTER RESOLVING MAINT PROB, IT WAS DECIDED TO CONTINUE WITH FLT. WHILE STILL PARKED, CAPT WAS TALKING TO GND ON COM #1 ABOUT WX IN THE AREA WHILE FO WAS SENDING MESSAGE TO COMPANY VIA ACARS WHILE SIMULTANEOUSLY ON COM #2 TALKING WITH LCL MAINT PERSONNEL. AT SOME POINT, CAPT ASKED GND TO CONTINUE TAXI TO RWY 25 (RFD) AND APPARENTLY DID NOT REALIZE FO WAS STILL ON COM #2 NOT LISTENING AND PREOCCUPIED WITH TYPING MESSAGE ON ACARS. WITH HEAD DOWN, FO DID NOT REALIZE ACFT WAS UNDER MOVEMENT TOWARDS ACTIVE RWY. CAPT TAXIED ACFT TOWARDS WHAT APPEARED TO BE TXWY F BUT ACTUALLY ENDED UP BEING AN ACTIVE RWY. FO LIFTED HEAD UP AND NOTICED RWY EDGE MARKINGS APCHING AND REQUESTED IMMEDIATE STOP. AT THIS POINT ACFT WAS PROTRUDING PAST THE HOLD LINE AND ENCROACHING ON RWY 25. WE NOTIFIED GND AND WAS GIVEN BACK TAXI INSTRUCTIONS AS THERE WERE NO ACFT USING THE RWY OR IN THE VICINITY. FACTORS INCLUDED: POOR TXWY MARKINGS, LIGHT RAIN, CREW NOT WORKING TOGETHER, FATIGUE (7 HR 30 MIN BLOCK FLYING NIGHT). CAPT THOUGHT THAT TAXI LIGHTS AHEAD WERE THE ENTRANCE TO TXWY F. IN FACT, IN THAT PORTION OF RAMP AREA THERE ARE NO LIGHTS SIGNIFYING OTHER EDGE OF TXWY F.

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.