 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The takeoff of a BE02 was aborted when it appeared that the autofeather system was not armed on 1 engine. The afx annunciator below the torque gauge did not illuminate during takeoff, but then operated normally in a follow-up check. The flight departed and this reporter was later questioned why he did not consult dispatch prior to departing.
| Attributes | |
| ACN | 359412 |
| Time | |
| Date | 199701 |
| Day | Thu |
| Local Time Of Day | 0001 To 0600 |
| Place | |
| Locale Reference | airport : den |
| State Reference | CO |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Beech 1900 |
| Operating Under FAR Part | Part 135 |
| Navigation In Use | Other |
| Flight Phase | climbout : takeoff other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 200 flight time total : 4000 flight time type : 600 |
| ASRS Report | 359412 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : rejected takeoff other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Aircraft |
| Air Traffic Incident | other |
Narrative:
During the takeoff roll on runway 25 at den, the left afx annunciator failed to illuminate. This indicates the autofeather system may not be properly armed. As captain, I instructed the first officer to abort the takeoff. We taxied clear of the runway and re-armed the autofeather. During a full power run- up immediately after clearing the runway, all autofeather annunciators tested normal. A subsequent takeoff was made with normal indications. The problem may have been an intermittent afx annunciator. Callback conversation with reporter revealed the following information: this BE02 captain felt it unnecessary to return to the gate, yet received some questions from his company's dispatch. This reporter's company operates larger equipment on a part 121 certificate which follows the co-authority/authorized rules.
Original NASA ASRS Text
Title: THE TKOF OF A BE02 WAS ABORTED WHEN IT APPEARED THAT THE AUTOFEATHER SYS WAS NOT ARMED ON 1 ENG. THE AFX ANNUNCIATOR BELOW THE TORQUE GAUGE DID NOT ILLUMINATE DURING TKOF, BUT THEN OPERATED NORMALLY IN A FOLLOW-UP CHK. THE FLT DEPARTED AND THIS RPTR WAS LATER QUESTIONED WHY HE DID NOT CONSULT DISPATCH PRIOR TO DEPARTING.
Narrative: DURING THE TKOF ROLL ON RWY 25 AT DEN, THE L AFX ANNUNCIATOR FAILED TO ILLUMINATE. THIS INDICATES THE AUTOFEATHER SYS MAY NOT BE PROPERLY ARMED. AS CAPT, I INSTRUCTED THE FO TO ABORT THE TKOF. WE TAXIED CLR OF THE RWY AND RE-ARMED THE AUTOFEATHER. DURING A FULL PWR RUN- UP IMMEDIATELY AFTER CLRING THE RWY, ALL AUTOFEATHER ANNUNCIATORS TESTED NORMAL. A SUBSEQUENT TKOF WAS MADE WITH NORMAL INDICATIONS. THE PROB MAY HAVE BEEN AN INTERMITTENT AFX ANNUNCIATOR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THIS BE02 CAPT FELT IT UNNECESSARY TO RETURN TO THE GATE, YET RECEIVED SOME QUESTIONS FROM HIS COMPANY'S DISPATCH. THIS RPTR'S COMPANY OPERATES LARGER EQUIP ON A PART 121 CERTIFICATE WHICH FOLLOWS THE CO-AUTH RULES.
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.