Narrative:

Autofeather did not arm when power set for takeoff (approximately 78%). Torque advanced to 80%. Autofeather still did not arm. Checked that button was in proper position. Aborted takeoff at approximately 70 KTS ground speed without incident. Off runway, set parking brake. Per poh, reset autofeather button, advanced power, and autofeather armed at approximately 65% torque. Attempted another takeoff. Autofeather armed normally and takeoff continued as normal. New alert bulletin to our fom states that any malfunction prior to takeoff should be written up as a discrepancy and reported to maintenance. Since this occurred in the takeoff phase, I feel it is a gray area as to whether I should have written up the discrepancy or if I was following procedure to reset and attempt again.

Related reports:

Google
 

Original NASA ASRS Text

Title: A DO328 REJECTED TKOF AT 70 KTS DUE TO THE AUTOFEATHER SYS FAILING TO ARM. RETESTED SYS AND SECOND TKOF NORMAL.

Narrative: AUTOFEATHER DID NOT ARM WHEN PWR SET FOR TKOF (APPROX 78%). TORQUE ADVANCED TO 80%. AUTOFEATHER STILL DID NOT ARM. CHKED THAT BUTTON WAS IN PROPER POS. ABORTED TKOF AT APPROX 70 KTS GND SPD WITHOUT INCIDENT. OFF RWY, SET PARKING BRAKE. PER POH, RESET AUTOFEATHER BUTTON, ADVANCED PWR, AND AUTOFEATHER ARMED AT APPROX 65% TORQUE. ATTEMPTED ANOTHER TKOF. AUTOFEATHER ARMED NORMALLY AND TKOF CONTINUED AS NORMAL. NEW ALERT BULLETIN TO OUR FOM STATES THAT ANY MALFUNCTION PRIOR TO TKOF SHOULD BE WRITTEN UP AS A DISCREPANCY AND RPTED TO MAINT. SINCE THIS OCCURRED IN THE TKOF PHASE, I FEEL IT IS A GRAY AREA AS TO WHETHER I SHOULD HAVE WRITTEN UP THE DISCREPANCY OR IF I WAS FOLLOWING PROC TO RESET AND ATTEMPT AGAIN.

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.