37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1085707 |
Time | |
Date | 201304 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | DA50 Super Star |
Operating Under FAR Part | Part 135 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 40 Flight Crew Total 1700 Flight Crew Type 40 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
The following is a situation I was involved in as a first officer of a jet aircraft as the non flying pilot. The situation took place at a very busy controlled airport within the us. I was somewhat new to the aircraft being flown.during initial startup we noticed the engine fuel computer light was on. We taxied to the maintenance hangar where the mechanics addressed the issue. About an hour later; the captain yelled for me to get the passengers. The question immediately came to my mind of why he was in such a hurry. This captain always had a way of making me feel rushed. Engines were running when I returned to the airplane with the passengers; which concerned me along with the speed and pressure he was again putting me under during the checklist. Once we began to taxi I noticed the fuel computer light was flashing. This didn't concern me since he told me that he discussed the issue with maintenance. While completing the checklist as we continued to taxi; I noticed the fuel light stopped flashing and had turned solid. I asked the captain three separate times; 'are you sure we can take off with that light on?' his first response was; 'yes.' I had serious doubts about the light so I continued to question him. His second response was; 'the mechanic told me it was okay to continue because he called the manufacture and they had stated it was a full deec.' again; his third response was; 'yes.' once the captain powered up the airplane on the takeoff roll; the engine number 2 fail light came on. I immediately called; 'abort!' the captain failed to respond. I called an abort a second time and he continued to ignore me. I was in shock that the captain would completely ignore such a call. Shortly after takeoff I told the captain; 'we need to return to the airport.' as if he had been frozen; after several seconds he agreed and we started the checklist to return for landing. We didn't declare an emergency; but the fire trucks were dispatched. As a precaution the ground equipment followed us to the ramp. Once we landed; he immediately turned to me and said; 'stay in the cockpit and don't talk to anyone.'after having a few days to think about this; I am confident in the knowledge I had of the system and light. With the captain's constant pressure and speed; I now realize that he was trying to deceive me about the system. I was not present for all the conversations with the mechanic; so I took his word.I didn't take any further action due to my trust in the captain. Once I called the abort and he ignored me; I lost that trust. When an airplane is rolling down the runway at speed; I don't think it's safe for the crew to fight over the flight controls. After reading into the systems in question; I now know that my first gut instinct was correct. Throughout my career as a pilot; I have never had a captain disregard my fears and concerns. A few days have past and I continue to think about all the things that could have been handled differently. I feel confident in my actions and am very pleased with how calm I was able to remain after the captain would not abort. Instead of loosing myself; I was able to start completing checklists and communicate our return to the airport. In our return for landing the captain was getting more and more angry. I was the only one calm in the cockpit during that very critical phase of flight. As in many situations it could have been much better or much worse. This was a major learning experience.
Original NASA ASRS Text
Title: Falcon 50 First Officer reports a takeoff with the center engine fuel computer light on. When the thrust is advanced the engine 2 fail light comes on and the First Officer calls for a reject which is ignored. Once safely airborne the Captain agrees to return for maintenance.
Narrative: The following is a situation I was involved in as a First Officer of a jet aircraft as the non flying pilot. The situation took place at a very busy controlled airport within the US. I was somewhat new to the aircraft being flown.During initial startup we noticed the engine fuel computer light was on. We taxied to the maintenance hangar where the mechanics addressed the issue. About an hour later; the Captain yelled for me to get the passengers. The question immediately came to my mind of why he was in such a hurry. This Captain always had a way of making me feel rushed. Engines were running when I returned to the airplane with the passengers; which concerned me along with the speed and pressure he was AGAIN putting me under during the checklist. Once we began to taxi I noticed the fuel computer light was flashing. This didn't concern me since he told me that he discussed the issue with Maintenance. While completing the checklist as we continued to taxi; I noticed the fuel light stopped flashing and had turned solid. I asked the Captain three separate times; 'Are you sure we can take off with that light on?' His first response was; 'Yes.' I had serious doubts about the light so I continued to question him. His second response was; 'The mechanic told me it was okay to continue because he called the manufacture and they had stated it was a full DEEC.' Again; his third response was; 'Yes.' Once the Captain powered up the airplane on the takeoff roll; the Engine Number 2 fail light came on. I immediately called; 'ABORT!' The Captain failed to respond. I called an abort a second time and he continued to ignore me. I was in shock that the Captain would completely ignore such a call. Shortly after takeoff I told the Captain; 'We need to return to the airport.' As if he had been frozen; after several seconds he agreed and we started the checklist to return for landing. We didn't declare an emergency; but the fire trucks were dispatched. As a precaution the ground equipment followed us to the ramp. Once we landed; he immediately turned to me and said; 'Stay in the cockpit and don't talk to anyone.'After having a few days to think about this; I am confident in the knowledge I had of the system and light. With the Captain's constant pressure and speed; I now realize that he was trying to deceive me about the system. I was not present for all the conversations with the mechanic; so I took his word.I didn't take any further action due to my trust in the Captain. Once I called the abort and he ignored me; I lost that trust. When an airplane is rolling down the runway at speed; I don't think it's safe for the crew to fight over the flight controls. After reading into the systems in question; I now know that my first gut instinct was correct. Throughout my career as a pilot; I have never had a Captain disregard my fears and concerns. A few days have past and I continue to think about all the things that could have been handled differently. I feel confident in my actions and am very pleased with how calm I was able to remain after the Captain would not abort. Instead of loosing myself; I was able to start completing checklists and communicate our return to the airport. In our return for landing the Captain was getting more and more angry. I was the only one calm in the cockpit during that very critical phase of flight. As in many situations it could have been much better or much worse. This was a major learning experience.
Data retrieved from NASA's ASRS site as of July 2013 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.