Narrative:

While taxiing out for takeoff eastbound on taxiway north, the tower cleared us for takeoff prior to reaching taxiway V. (Runway 26L was in use.) the captain then called for below the line, and as the checklist was being performed, we taxied into position on runway 26R. Upon completion of the checklist, the thrust levers were advanced, and the captain requested takeoff power to be set. As we started rolling, the tower called to cancel our takeoff and advised us that we were on a closed runway. The captain closed the thrust levers and braked, allowing us to turn off onto the next available taxiway. (The airspeed never reached 60 KTS.) the tower advised the captain that no actions would be taken on his part. We then taxied back for a normal takeoff on runway 26L. There was a lighted X on a stand on the approach end of runway 26R. Aircraft landing would see it quickly. However, unless you were looking to the left (east) you would not notice this runway being closed. Another factor contributing to this event is that runway 26R is the normal runway for takeoff when westerly departures are in use. I feel that the 'X' would have better visibility and effectiveness if it were placed on the runway so that it would be visible to both departing as well as landing aircraft. Supplemental 579515: the tower cleared us for takeoff. We also heard an aircraft being cleared to land, so we felt we needed to expedite our takeoff. My attention was diverted between the landing aircraft and performing the 'below the line items.' I inadvertently turned on runway 26R and started our takeoff roll. Tower noticed our mistake and notified us runway 26R was closed. We turned off the next taxiway and returned to runway 26L for a normal takeoff and departure. Tower said there was no problem and nothing was going to be reported. Contributing factors: it was dusk, and visibility was reduced. Receiving a takeoff clearance on the taxiway well before the hold short area of both runways. My paying too much attention to the landing aircraft and not wanting to delay our takeoff roll.

Google
 

Original NASA ASRS Text

Title: WRONG RWY TKOF ATTEMPTED ON A CLOSED RWY BY A B737-200 FLT CREW AT ONT, CA.

Narrative: WHILE TAXIING OUT FOR TKOF EBOUND ON TXWY N, THE TWR CLRED US FOR TKOF PRIOR TO REACHING TXWY V. (RWY 26L WAS IN USE.) THE CAPT THEN CALLED FOR BELOW THE LINE, AND AS THE CHKLIST WAS BEING PERFORMED, WE TAXIED INTO POS ON RWY 26R. UPON COMPLETION OF THE CHKLIST, THE THRUST LEVERS WERE ADVANCED, AND THE CAPT REQUESTED TKOF PWR TO BE SET. AS WE STARTED ROLLING, THE TWR CALLED TO CANCEL OUR TKOF AND ADVISED US THAT WE WERE ON A CLOSED RWY. THE CAPT CLOSED THE THRUST LEVERS AND BRAKED, ALLOWING US TO TURN OFF ONTO THE NEXT AVAILABLE TXWY. (THE AIRSPD NEVER REACHED 60 KTS.) THE TWR ADVISED THE CAPT THAT NO ACTIONS WOULD BE TAKEN ON HIS PART. WE THEN TAXIED BACK FOR A NORMAL TKOF ON RWY 26L. THERE WAS A LIGHTED X ON A STAND ON THE APCH END OF RWY 26R. ACFT LNDG WOULD SEE IT QUICKLY. HOWEVER, UNLESS YOU WERE LOOKING TO THE L (E) YOU WOULD NOT NOTICE THIS RWY BEING CLOSED. ANOTHER FACTOR CONTRIBUTING TO THIS EVENT IS THAT RWY 26R IS THE NORMAL RWY FOR TKOF WHEN WESTERLY DEPS ARE IN USE. I FEEL THAT THE 'X' WOULD HAVE BETTER VISIBILITY AND EFFECTIVENESS IF IT WERE PLACED ON THE RWY SO THAT IT WOULD BE VISIBLE TO BOTH DEPARTING AS WELL AS LNDG ACFT. SUPPLEMENTAL 579515: THE TWR CLRED US FOR TKOF. WE ALSO HEARD AN ACFT BEING CLRED TO LAND, SO WE FELT WE NEEDED TO EXPEDITE OUR TKOF. MY ATTN WAS DIVERTED BTWN THE LNDG ACFT AND PERFORMING THE 'BELOW THE LINE ITEMS.' I INADVERTENTLY TURNED ON RWY 26R AND STARTED OUR TKOF ROLL. TWR NOTICED OUR MISTAKE AND NOTIFIED US RWY 26R WAS CLOSED. WE TURNED OFF THE NEXT TXWY AND RETURNED TO RWY 26L FOR A NORMAL TKOF AND DEP. TWR SAID THERE WAS NO PROB AND NOTHING WAS GOING TO BE RPTED. CONTRIBUTING FACTORS: IT WAS DUSK, AND VISIBILITY WAS REDUCED. RECEIVING A TKOF CLRNC ON THE TXWY WELL BEFORE THE HOLD SHORT AREA OF BOTH RWYS. MY PAYING TOO MUCH ATTN TO THE LNDG ACFT AND NOT WANTING TO DELAY OUR TKOF ROLL.

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.