Narrative:

Second flight of the day using a new aircraft. The aircraft had some MEL's that made the typical checklist non-standard. Complied with the new checks and pushed the aircraft off the gate. Ran all normal checklist and began taxi for runway 34R. I am nearly 100% certain that the autofeather was armed during the after start checklist. On the taxi out we were given a runway change. At that time my first officer updated her FMS and leaned over and updated my FMS with the new runway. It is my belief that the autofeather may have been deselected at this point by accident. The taxi continued to the runway with checklist and no event. It was the first officer's flight leg. I taxied onto the runway when cleared for takeoff and transferred controls to the first officer. She pushed the power levers forward and I watched for to power to be set. It was at this point that I realized that the autofeather was not armed. I took control of the aircraft at approx. 50-65 knots and aborted the takeoff. We taxied clear of the runway and took a moment to verify that all the systems were set appropriately for departure. We then taxied back to the runway and departed without any further incidence. I made it a point to debrief my first officer with regards to the abort and my beliefs on how it possibly happened.during my debrief I explained to the first officer that setting runways in FMS can be performed on the one side and cross-filled to the other side. This would prevent accidental selection of another system. I also believe that being sure to cross check that all systems are set right is very key to ensuring that the aircraft can be flown without issue.

Google
 

Original NASA ASRS Text

Title: Dash 8-400 flight crew reported they started takeoff roll with autofeather not armed; possibly as a result of F/O accidentally bumping the switch during FMC programming. Takeoff was rejected.

Narrative: Second flight of the day using a new aircraft. The aircraft had some MEL's that made the typical checklist non-standard. Complied with the new checks and pushed the aircraft off the gate. Ran all normal checklist and began taxi for runway 34R. I am nearly 100% certain that the autofeather was armed during the after start checklist. On the taxi out we were given a runway change. At that time my FO updated her FMS and leaned over and updated my FMS with the new runway. It is my belief that the autofeather may have been deselected at this point by accident. The taxi continued to the runway with checklist and no event. It was the FO's flight leg. I taxied onto the runway when cleared for Takeoff and transferred controls to the FO. She pushed the power levers forward and I watched for TO power to be set. It was at this point that I realized that the autofeather was not armed. I took control of the aircraft at approx. 50-65 knots and aborted the Takeoff. We taxied clear of the runway and took a moment to verify that all the systems were set appropriately for departure. We then taxied back to the runway and departed without any further incidence. I made it a point to debrief my FO with regards to the abort and my beliefs on how it possibly happened.During my debrief I explained to the FO that setting runways in FMS can be performed on the one side and cross-filled to the other side. This would prevent accidental selection of another system. I also believe that being sure to cross check that all systems are set right is very key to ensuring that the aircraft can be flown without issue.

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