Narrative:

The flight was running late due to the inbound flight arriving late and multiple fuel system placards requiring the flight crew to monitor the fueling process. I was the captain for this flight but sitting in the right seat observing and checking out a new captain. This requires me to check everything to ensure all items/events are accomplished safely and correctly. Cleveland was using runway 23L&right. The ATIS reported using runway 23L for lndgs and runway 23R for takeoff. This made the taxi out very short. I was running the checklist, talking to ground, then tower which had cleared us for takeoff on runway 23L while taxiing to the runway. We had briefed for a takeoff on runway 23R so a quick brief for runway 23L was in progress when we made it to runway 23L. We entered the runway 28/23L intersection from taxiway J. I was aware of the turn required for takeoff on runway 23L and noticed him making a left turn and mentally checked this off while finishing the takeoff checklist and ensuring all the checklist items were accomplished. I was also distracted by having to manually verify our takeoff weight using the fuel slip since our fuel gauges were not operational. The new captain ran up the engines and I checked the settings and was comfortable with the engine power. Takeoff power was set and the takeoff roll began. I normally look down and verify the aircraft heading prior to initiating (or allowing the initiation of) the takeoff roll. This was inadvertently not accomplished. The new captain had not completed the turn to runway 23L but had instead initiated takeoff on runway 28. A sharp tower controller called us and informed us while we were still in our takeoff roll. I called for and initiated an abort at about 100 KTS. We were lucky there was no traffic conflict even though we crossed runway 23R during this roll. Red faced, we back taxied to runway 23R (per tower instructions) this time and tower cleared us for an uneventful takeoff. This could have been a disaster had anything else gone wrong. I allowed myself to load up to the point I dropped 1 small self check which allowed a very big mistake, this will not happen again. All items will be accomplished prior to taking the runway so I can be heads up and in the real world instead of heads down and unaware. Supplemental information from acn 254158: operationally, many things contributed to my mistake. Rushed is the best word to describe error. But the big item here is the fact that if I had not allowed myself to be rushed, it never would have happened.

Google
 

Original NASA ASRS Text

Title: UNAUTH TKOF RWY IN A NIGHT OP AT CLE. TRAINING IN PROGRESS. TKOF ABORTED.

Narrative: THE FLT WAS RUNNING LATE DUE TO THE INBOUND FLT ARRIVING LATE AND MULTIPLE FUEL SYS PLACARDS REQUIRING THE FLC TO MONITOR THE FUELING PROCESS. I WAS THE CAPT FOR THIS FLT BUT SITTING IN THE R SEAT OBSERVING AND CHKING OUT A NEW CAPT. THIS REQUIRES ME TO CHK EVERYTHING TO ENSURE ALL ITEMS/EVENTS ARE ACCOMPLISHED SAFELY AND CORRECTLY. CLEVELAND WAS USING RWY 23L&R. THE ATIS RPTED USING RWY 23L FOR LNDGS AND RWY 23R FOR TKOF. THIS MADE THE TAXI OUT VERY SHORT. I WAS RUNNING THE CHKLIST, TALKING TO GND, THEN TWR WHICH HAD CLRED US FOR TKOF ON RWY 23L WHILE TAXIING TO THE RWY. WE HAD BRIEFED FOR A TKOF ON RWY 23R SO A QUICK BRIEF FOR RWY 23L WAS IN PROGRESS WHEN WE MADE IT TO RWY 23L. WE ENTERED THE RWY 28/23L INTXN FROM TXWY J. I WAS AWARE OF THE TURN REQUIRED FOR TKOF ON RWY 23L AND NOTICED HIM MAKING A L TURN AND MENTALLY CHKED THIS OFF WHILE FINISHING THE TKOF CHKLIST AND ENSURING ALL THE CHKLIST ITEMS WERE ACCOMPLISHED. I WAS ALSO DISTRACTED BY HAVING TO MANUALLY VERIFY OUR TKOF WT USING THE FUEL SLIP SINCE OUR FUEL GAUGES WERE NOT OPERATIONAL. THE NEW CAPT RAN UP THE ENGS AND I CHKED THE SETTINGS AND WAS COMFORTABLE WITH THE ENG PWR. TKOF PWR WAS SET AND THE TKOF ROLL BEGAN. I NORMALLY LOOK DOWN AND VERIFY THE ACFT HDG PRIOR TO INITIATING (OR ALLOWING THE INITIATION OF) THE TKOF ROLL. THIS WAS INADVERTENTLY NOT ACCOMPLISHED. THE NEW CAPT HAD NOT COMPLETED THE TURN TO RWY 23L BUT HAD INSTEAD INITIATED TKOF ON RWY 28. A SHARP TWR CTLR CALLED US AND INFORMED US WHILE WE WERE STILL IN OUR TKOF ROLL. I CALLED FOR AND INITIATED AN ABORT AT ABOUT 100 KTS. WE WERE LUCKY THERE WAS NO TFC CONFLICT EVEN THOUGH WE CROSSED RWY 23R DURING THIS ROLL. RED FACED, WE BACK TAXIED TO RWY 23R (PER TWR INSTRUCTIONS) THIS TIME AND TWR CLRED US FOR AN UNEVENTFUL TKOF. THIS COULD HAVE BEEN A DISASTER HAD ANYTHING ELSE GONE WRONG. I ALLOWED MYSELF TO LOAD UP TO THE POINT I DROPPED 1 SMALL SELF CHK WHICH ALLOWED A VERY BIG MISTAKE, THIS WILL NOT HAPPEN AGAIN. ALL ITEMS WILL BE ACCOMPLISHED PRIOR TO TAKING THE RWY SO I CAN BE HEADS UP AND IN THE REAL WORLD INSTEAD OF HEADS DOWN AND UNAWARE. SUPPLEMENTAL INFORMATION FROM ACN 254158: OPERATIONALLY, MANY THINGS CONTRIBUTED TO MY MISTAKE. RUSHED IS THE BEST WORD TO DESCRIBE ERROR. BUT THE BIG ITEM HERE IS THE FACT THAT IF I HAD NOT ALLOWED MYSELF TO BE RUSHED, IT NEVER WOULD HAVE HAPPENED.

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.