 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Takeoff confign warning light came on as the airspeed approached V1. The flight crew aborted the takeoff successfully. No mention was made regarding what caused the takeoff warning to activate.
| Attributes | |
| ACN | 323690 |
| Time | |
| Date | 199512 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : bgr |
| State Reference | ME |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : cmh |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : takeoff other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 210 flight time total : 7500 flight time type : 5000 |
| ASRS Report | 323690 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | aircraft equipment problem : critical |
| Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
| Resolutory Action | flight crew : rejected takeoff |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Aircraft |
| Air Traffic Incident | other |
Narrative:
I was taking off runway 33 in bgr from intersection K, 8100 ft remaining. We were accelerating down the runway. My first officer calling 'V' but not '1' when we had a confign warning come on. Condition levers were then pushed up to extinguish warning but unsuccessful. First officer called abort, abort, abort. And I decided to abort as I had ample runway remaining. Normal braking was required to stop aircraft and deep reverse was not needed. The reason I am reporting this incident is V1 might have been exceeded. In the future it would probably be better to just continue the takeoff rather than taking a chance of exceeding V1 which in turn could put the airplane in a more jeopardizing position.
Original NASA ASRS Text
Title: TKOF CONFIGN WARNING LIGHT CAME ON AS THE AIRSPD APCHED V1. THE FLC ABORTED THE TKOF SUCCESSFULLY. NO MENTION WAS MADE REGARDING WHAT CAUSED THE TKOF WARNING TO ACTIVATE.
Narrative: I WAS TAKING OFF RWY 33 IN BGR FROM INTXN K, 8100 FT REMAINING. WE WERE ACCELERATING DOWN THE RWY. MY FO CALLING 'V' BUT NOT '1' WHEN WE HAD A CONFIGN WARNING COME ON. CONDITION LEVERS WERE THEN PUSHED UP TO EXTINGUISH WARNING BUT UNSUCCESSFUL. FO CALLED ABORT, ABORT, ABORT. AND I DECIDED TO ABORT AS I HAD AMPLE RWY REMAINING. NORMAL BRAKING WAS REQUIRED TO STOP ACFT AND DEEP REVERSE WAS NOT NEEDED. THE REASON I AM RPTING THIS INCIDENT IS V1 MIGHT HAVE BEEN EXCEEDED. IN THE FUTURE IT WOULD PROBABLY BE BETTER TO JUST CONTINUE THE TKOF RATHER THAN TAKING A CHANCE OF EXCEEDING V1 WHICH IN TURN COULD PUT THE AIRPLANE IN A MORE JEOPARDIZING POS.
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.