B757-200
Flight Crew Air Transport Pilot (ATP)
Fatigue; Situational Awareness; Human-Machine Interface
Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Flight Crew Became Reoriented; Flight Crew Rejected Takeoff
Human Factors
As we were cleared for taxi; we received a runway change from 01L to 01R. We queried the controller over this change; as our previous departure from LAS involved the same change; but was followed by a late change back to RWY 01L. The controller indicated that 01R was the correct runway. I changed the departure in the FMC; verified performance for the new runway; and entered new takeoff speeds. We taxied around some construction on the way to runway 01R. We were cleared for takeoff; and taxied onto the runway. We completed the 'below the line' portion of the checklist. Captain called for standard power; and we noticed that the auto throttles were not advancing the throttles. The throttles were manually advanced slightly more; and the takeoff warning horn sounded. We realized the aircraft had not been properly configured. Speed was approx. 15-20 knots when we realized the mistake. We cleared the runway; configured the aircraft; completed the before takeoff checklist. Subsequent takeoff was uneventful. This was the third leg of the night; and thirteenth night leg of the trip. We were tired. The runway change; and the discussion with controller and ourselves concerning the possibility of a late change back to original runway. Got out of normal flow pattern. Long; slow taxi around construction. Increased attention to detail. Double or triple checking items after changes. Making sure flow pattern disruptions are mitigated properly.
During taxi from ramp the ground controller advised us of a runway change from 1L to 1R. We asked for confirmation on taxi out because the same thing happened two days earlier when they switched takeoff runways twice. The First Officer (FO) made the changes in the FMS and we taxied to the runway. We approached runway 1R and we were cleared for takeoff. We did the before takeoff checklist 'below the line' and proceeded to start our takeoff. When I pushed the 'Thrust switch' it did not advance the power; I pushed the power up a little more and we got the takeoff warning. I stopped the takeoff roll and cleared the runway. We had failed to configure the airplane for takeoff. The power did not advance to takeoff power and the EPR didn't exceed 1.2. Max speed on the runway was 20 knots. We then configured for takeoff and completed the takeoff checklist. Tower cleared us for takeoff and we took off and proceeded to destination.We were on the 5th night of night flying on our 13th leg. We got out of our normal routine with the runway change and the experience two nights earlier; when they changed the takeoff runway twice. We questioned the controller and he assured us the change was correct. Being tired and distracted was a contributing factor for me forgetting to call for configuring the aircraft. I know the FO was also tired and normally he would have caught my mistake. We even completed the 'below the line' part of our takeoff checklist and it did not cause us to realize our mistake of not configuring the aircraft. More attention to detail and double check everything; especially when your regular routine is disrupted. Fatigue is a big factor when working through night hub turns. We have to realize the insidious effects fatigue has on performance and try to compensate for it or when to admit we are too tired to fly. I know we were capable of flying that last leg. Fatigue will cause us to make more mistakes; we have to more vigilant when we are tired.
B757 flight crew reports forgetting to configure their aircraft prior to attempting takeoff; due to distractions and fatigue. The takeoff warning horn sounds and the takeoff is rejected.