Takeoff aborted after EICAS system alerts crew to the fact that the flaps were not set for takeoff.

Attributes
ACN	311610
Time
Date	199507
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : slc
State Reference	UT
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : takeoff ground other : taxi other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 150 flight time total : 4500 flight time type : 300
ASRS Report	311610
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	flight crew : rejected takeoff other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were departing runway 34 at slc. The captain was making the takeoff. When he advanced the throttles for takeoff the master warning light illuminated and the warning horn sounded. The EICAS screen showed a 'flaps' warning. We quickly determined that the flaps were fully retracted. We had started rolling, but I estimate our speed never exceeded 25 KTS. The captain decided to reject the takeoff, and we rolled to taxiway H3. I notified the tower of our rejected takeoff and they told us to exit the runway at H3. We taxied back and made a normal departure. Clearly, we forgot to set the flaps for takeoff. It is our company procedure for the captain to call for the first officer to set takeoff flaps as we exit the ramp. He failed to do so. It is also our procedure for the captain to call for the 'before takeoff checklist' immediately after the PF gives the takeoff briefing. He failed to do so. It is the first officer's responsibility to back the captain up and make sure that the flaps were set. I failed to do so. Our ramp is very close to the departure end of the runway, so we were kind of rushing to get ready for departure. I feel that the main factors in this mistake were the captain's failure to follow standard procedures, and my failure to back him up.

Original NASA ASRS Text

Title: TKOF ABORTED AFTER EICAS SYS ALERTS CREW TO THE FACT THAT THE FLAPS WERE NOT SET FOR TKOF.

Narrative: WE WERE DEPARTING RWY 34 AT SLC. THE CAPT WAS MAKING THE TKOF. WHEN HE ADVANCED THE THROTTLES FOR TKOF THE MASTER WARNING LIGHT ILLUMINATED AND THE WARNING HORN SOUNDED. THE EICAS SCREEN SHOWED A 'FLAPS' WARNING. WE QUICKLY DETERMINED THAT THE FLAPS WERE FULLY RETRACTED. WE HAD STARTED ROLLING, BUT I ESTIMATE OUR SPD NEVER EXCEEDED 25 KTS. THE CAPT DECIDED TO REJECT THE TKOF, AND WE ROLLED TO TXWY H3. I NOTIFIED THE TWR OF OUR REJECTED TKOF AND THEY TOLD US TO EXIT THE RWY AT H3. WE TAXIED BACK AND MADE A NORMAL DEP. CLRLY, WE FORGOT TO SET THE FLAPS FOR TKOF. IT IS OUR COMPANY PROC FOR THE CAPT TO CALL FOR THE FO TO SET TKOF FLAPS AS WE EXIT THE RAMP. HE FAILED TO DO SO. IT IS ALSO OUR PROC FOR THE CAPT TO CALL FOR THE 'BEFORE TKOF CHKLIST' IMMEDIATELY AFTER THE PF GIVES THE TKOF BRIEFING. HE FAILED TO DO SO. IT IS THE FO'S RESPONSIBILITY TO BACK THE CAPT UP AND MAKE SURE THAT THE FLAPS WERE SET. I FAILED TO DO SO. OUR RAMP IS VERY CLOSE TO THE DEP END OF THE RWY, SO WE WERE KIND OF RUSHING TO GET READY FOR DEP. I FEEL THAT THE MAIN FACTORS IN THIS MISTAKE WERE THE CAPT'S FAILURE TO FOLLOW STANDARD PROCS, AND MY FAILURE TO BACK HIM UP.

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.