A first officer reported that sfo changed the departure during taxi and because of task saturation t...

Narrative:

The event itself was a rejected takeoff on runway 1R of sfo. It occurred when the takeoff roll commenced and the warning system of the airplane alerted us to the fact that configuration was not set properly for takeoff. Tower was notified and we exited the runway to the right. Company was called by the captain to inform them and to make sure proper procedure was followed. Once all proper checklists were completed a new takeoff clearance was obtained and the flight proceeded normally. During night operations in sfo as we started to taxi to the runway which would be one of the 28 runways; ATC decided to switch runways to the 1's and give us a new clearance. We started preparing the aircraft for the new clearance and the captain asked me (the first officer) to determine what the amount of tailwind we would have on this takeoff to make sure we would not violate the maximum 10 KT tailwind requirement. As I worked on this we continued to taxi. Since we were the first to be given the new clearance and we were task saturated we made it to the runway without having completing the taxi check as normal. Without having called for the taxi check; the before takeoff check was called for and completed; and we were immediately cleared for takeoff. Right after the power addition for takeoff we got the aural takeoff warning letting us know that the flaps and autopilot were not configured for takeoff. An immediate rejected takeoff was performed. Make sure that regardless of the situation; all checklists and procedures have been completed. Even if this involves a delay and taxi off to the side to complete if necessary. Do not let ATC push us into going when we are not ready. Be especially vigilant when things happen outside of the normal flow of things. Always take a quick look around to verify proper configuration before takeoff power is added.

Original NASA ASRS Text

Title: A First Officer reported that SFO changed the departure during taxi and because of task saturation the crew failed to configure the aircraft for takeoff resulting in a rejected takeoff.

Narrative: The event itself was a rejected takeoff on Runway 1R of SFO. It occurred when the takeoff roll commenced and the warning system of the airplane alerted us to the fact that configuration was not set properly for takeoff. Tower was notified and we exited the runway to the right. Company was called by the Captain to inform them and to make sure proper procedure was followed. Once all proper checklists were completed a new takeoff clearance was obtained and the flight proceeded normally. During night operations in SFO as we started to taxi to the runway which would be one of the 28 runways; ATC decided to switch runways to the 1's and give us a new clearance. We started preparing the aircraft for the new clearance and the Captain asked me (the First Officer) to determine what the amount of tailwind we would have on this takeoff to make sure we would not violate the maximum 10 KT tailwind requirement. As I worked on this we continued to taxi. Since we were the first to be given the new clearance and we were task saturated we made it to the runway without having completing the taxi check as normal. Without having called for the Taxi Check; the Before Takeoff Check was called for and completed; and we were immediately cleared for takeoff. Right after the power addition for takeoff we got the aural takeoff warning letting us know that the flaps and autopilot were not configured for takeoff. An immediate rejected takeoff was performed. Make sure that regardless of the situation; all checklists and procedures have been completed. Even if this involves a delay and taxi off to the side to complete if necessary. Do not let ATC push us into going when we are not ready. Be especially vigilant when things happen outside of the normal flow of things. Always take a quick look around to verify proper configuration before takeoff power is added.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	1012050
Time
Date	201205
Local Time Of Day	1201-1800
Place
Locale Reference	SFO.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Person 1
Function	Pilot Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Procedural Published Material / Policy

A first officer reported that sfo changed the departure during taxi and because of task saturation the crew failed to configure the aircraft for takeoff resulting in a rejected takeoff.