A B737-300 crew aborted the takeoff roll because the flaps were up. After engine start; they were di...

Attributes
ACN	811410
Time
Date	200811
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : takeoff roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 250 flight time type : 2100
ASRS Report	811410
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 251 flight time type : 150
ASRS Report	811416
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : non compliance with mel maintenance problem : improper maintenance non adherence : far non adherence : published procedure non adherence : company policies
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : rejected takeoff
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We pushed back from the gate. After tug/towbar disconnect; we ran our flows and found the yaw damper light illuminated when we pressed the annunciator panel. We turned our attention to the QRH and ran the procedure to the light. We were unsuccessful in getting the yaw damper to stay on. We elected to continue after reviewing the MEL and agreed that the flight had been initiated by taxi and we would complete the MEL in ZZZ1. ZZZ ATC gave us a short taxi to runway xxr instead of our planned runway xxl. I hurriedly checked the performance data and changed the departure runway in the box to check fixes for the RNAV departure. We were cleared for takeoff; and upon advancing the thrust levers; the takeoff warning horn sounded. We immediately rejected; cleared the runway; and ran the rejected takeoff checklist. We realized that after dealing with the yaw damper issue that interrupted our flows; I never set the flaps and we never ran a taxi checklist. Therefore; flaps 5 degrees were never set; and in our hurried state we never realized our error until the takeoff warning horn had sounded. We taxied back for takeoff and had an uneventful flight to ZZZ1. We notified dispatch and maintenance control of the yaw damper once en route to ZZZ1. The untimely distraction with the yaw damper and our hurriedness caused us to completely forget the taxi checklist. The timeliness of the distraction and the lack of attention to details and neglect of the primary QRH memory item for all sits allowed us to totally mis-set the flaps. The takeoff warning horn was certainly a save for us. Supplemental information from acn 811416: there was no one in front of us so we were cleared for takeoff as soon as we approached the runway. When we began to push the thrust levers forward; the takeoff warning horn sounded. We aborted at about 15-20 KTS; taxied off; ran the QRH; and set the flaps for takeoff.

Original NASA ASRS Text

Title: A B737-300 CREW ABORTED THE TAKEOFF ROLL BECAUSE THE FLAPS WERE UP. AFTER ENGINE START; THEY WERE DISTRACTED BY A YAW DAMPER FAILURE AND DID NOT COMPLETE THE TAXI CHECKLIST.

Narrative: WE PUSHED BACK FROM THE GATE. AFTER TUG/TOWBAR DISCONNECT; WE RAN OUR FLOWS AND FOUND THE YAW DAMPER LIGHT ILLUMINATED WHEN WE PRESSED THE ANNUNCIATOR PANEL. WE TURNED OUR ATTN TO THE QRH AND RAN THE PROC TO THE LIGHT. WE WERE UNSUCCESSFUL IN GETTING THE YAW DAMPER TO STAY ON. WE ELECTED TO CONTINUE AFTER REVIEWING THE MEL AND AGREED THAT THE FLT HAD BEEN INITIATED BY TAXI AND WE WOULD COMPLETE THE MEL IN ZZZ1. ZZZ ATC GAVE US A SHORT TAXI TO RWY XXR INSTEAD OF OUR PLANNED RWY XXL. I HURRIEDLY CHKED THE PERFORMANCE DATA AND CHANGED THE DEP RWY IN THE BOX TO CHK FIXES FOR THE RNAV DEP. WE WERE CLRED FOR TKOF; AND UPON ADVANCING THE THRUST LEVERS; THE TKOF WARNING HORN SOUNDED. WE IMMEDIATELY REJECTED; CLRED THE RWY; AND RAN THE RTO CHKLIST. WE REALIZED THAT AFTER DEALING WITH THE YAW DAMPER ISSUE THAT INTERRUPTED OUR FLOWS; I NEVER SET THE FLAPS AND WE NEVER RAN A TAXI CHKLIST. THEREFORE; FLAPS 5 DEGS WERE NEVER SET; AND IN OUR HURRIED STATE WE NEVER REALIZED OUR ERROR UNTIL THE TKOF WARNING HORN HAD SOUNDED. WE TAXIED BACK FOR TKOF AND HAD AN UNEVENTFUL FLT TO ZZZ1. WE NOTIFIED DISPATCH AND MAINT CTL OF THE YAW DAMPER ONCE ENRTE TO ZZZ1. THE UNTIMELY DISTR WITH THE YAW DAMPER AND OUR HURRIEDNESS CAUSED US TO COMPLETELY FORGET THE TAXI CHKLIST. THE TIMELINESS OF THE DISTR AND THE LACK OF ATTN TO DETAILS AND NEGLECT OF THE PRIMARY QRH MEMORY ITEM FOR ALL SITS ALLOWED US TO TOTALLY MIS-SET THE FLAPS. THE TKOF WARNING HORN WAS CERTAINLY A SAVE FOR US. SUPPLEMENTAL INFO FROM ACN 811416: THERE WAS NO ONE IN FRONT OF US SO WE WERE CLRED FOR TKOF AS SOON AS WE APCHED THE RWY. WHEN WE BEGAN TO PUSH THE THRUST LEVERS FORWARD; THE TKOF WARNING HORN SOUNDED. WE ABORTED AT ABOUT 15-20 KTS; TAXIED OFF; RAN THE QRH; AND SET THE FLAPS FOR TKOF.

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

A B737-300 crew aborted the takeoff roll because the flaps were up. After engine start; they were distracted by a yaw damper failure and did not complete the taxi checklist.