Dash8 flight crew reports rejected takeoff after First Officer notices auto feather is not armed during the takeoff roll.
Synopsis
Dash8 flight crew reports rejected takeoff after First Officer notices auto feather is not armed during the takeoff roll.
Narrative
The event began while sitting. During the final boarding process (completing weight and balance form); the APU failed twice requiring a GPU to be attached. Current conditions were 31 degrees Celsius as reported by the ATIS. The flight deck was approximately 5-10 degrees warmer with little to no air flow. The push back was performed. Once the engines were started; I performed the after start flow. The captain called for the checklist and we responded as appropriate. We then requested taxi and were given the short taxi to Runway. All checklists preformed were normal. We were immediately cleared for take off as we were crossing from the ramp into the taxiway. Torque was 90% with no specials for the runway. On the take off roll; the Captain advanced the throttles with out holding the brakes until 50% power to verify auto feather armed. I noticed the auto feather not arming and called 'reject; reject; reject' to Tower. The speed was 90 kts. We notified them that no assistance was required and that we would like to taxi to the hard stand to contact Maintenance/Dispatch. Both the Captain and I believe that due to the circumstances that occurred during the boarding process such as the multiple failures of the APU; the hot flight deck; and the quick taxi to the runway; that we did not truly give the focus that the checklist required in actually verifying some of the data. Both he and I believe that this was a chain reaction of little things that ended up building. Both the Captain and I agreed that during my after start flow; when I had pressed the auto feather select button; the button did not fully engage.
Second reporter narrative
During the take-off roll the First Officer noticed during his engine instrument scan that the auto feather was not armed. During the after start flow the First Officer did not properly select the auto feather on; and during the after start checklist I did not properly verify that the auto feather was selected. I also forgot during the first take-off to hold the brakes and apply Torque to 50% and verify that the auto feather was armed per SOP. The take-off was aborted; the Tower was notified; the passengers were briefed and Dispatch and Maintenance notified. To avoid this scenario in the future; I will try not to be distracted by heat and be more vigilant during short taxis. The after start flow and checklist are adequate IF properly adhered to. This was my first departure in over 2 months in a 300 in which the temperature was over 29C; I should have reviewed the proper procedure.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.