DHC8 Captain reports rejecting the takeoff when autofeather does not arm. The Autofeather system is tested at Maintenance Controls' direction and found functional; the following takeoff was uneventful. The Logbook was found to contain multiple write-ups of the same event all solved by the crew preforming an Autofeather test.
Synopsis
DHC8 Captain reports rejecting the takeoff when autofeather does not arm. The Autofeather system is tested at Maintenance Controls' direction and found functional; the following takeoff was uneventful. The Logbook was found to contain multiple write-ups of the same event all solved by the crew preforming an Autofeather test.
Narrative
Once cleared for takeoff; we conducted our Takeoff Final Items checklist; and I centered the aircraft on the runway. I applied power to the engines and brought the torque up to our assigned setting of approximately 90 percent. After several seconds; and at an approximate airspeed of 40 KIAS; the First Officer stated 'THE AUTOFEATHER DID NOT ARM.' After a quick visual confirmation of the AUTOFEATHER switch; I also noted that it had; in fact; not armed. I called out 'ABORT; ABORT; ABORT;' while immediately rejecting the takeoff by retarding the power levers to DISC and applying toe-brake pressure. I then contacted ATC and told them that we had rejected the takeoff due to a system malfunction; and stated that we did not need any special assistance. I then wrote up the discrepancy into the Maintenance Log; and contacted Dispatch and notified them of the event. Dispatch made note of it; and transferred us to Maintenance Control; where I then spoke to the mechanic on duty. After explaining the event in full to him; he directed us to conduct a test on the AUTOFEATHER system. We conducted this test in accordance with his instructions; and the system tested satisfactory (the AUTOFEATHER ARM light illuminated upon bringing the torque levels to a takeoff power setting). The mechanic then instructed me as to what to insert into the 'Corrective Action' block of the Maintenance Log. I inserted all of the information as directed by him; and signed the block with my name and pilot number; and also printed his name in the block as well per his request. He informed me that it was now satisfactory and safe to attempt another takeoff. I was then transferred back to Dispatch; with whom I then obtained an amended release. After receiving the amended release; checking the current fuel status; and updating the passengers and operations of our status; we conducted our pre-taxi checklist and pre-takeoff checklists and successfully attempted a second takeoff. In the Maintenance Logbook; I observed that this particular AUTOFEATHER problem had been written up multiple times within the previous 11 days by multiple pilots; including an entry from the previous day of our event. Each one of these write-ups was 'resolved' in the same manner (performing this AUTOFEATHER test after rejecting a takeoff; and having the PIC sign it off). This seems to be a reoccurring problem on this particular aircraft.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.