37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 682176 |
Time | |
Date | 200512 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : cmh.airport |
State Reference | OH |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : cmh.tower |
Operator | common carrier : air carrier |
Make Model Name | MD-88 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : takeoff roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 90 flight time total : 3300 flight time type : 700 |
ASRS Report | 682176 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : company policies |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : rejected takeoff |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Aircraft |
Narrative:
The flight was routinely dispatched from the gate and all checklists and procedures were accomplished in accordance with established procedures. It was my leg and during the takeoff briefing I stated that we would be using runway 28L because; at 10000 ft long; it was longer than runway 28R (8000 ft available) and the taxi distance from the spot where we would deice was essentially the same. The captain said he wanted to use runway 28R but gave no operational reason why. The aircraft weight and balance summary data supported either runway. After deicing; we completed the remaining checklists and were cleared for takeoff. I assumed control of the aircraft on the roll as the captain completed the alignment and I advanced the throttles towards takeoff power. I immediately noticed that the #2 engine EPR gauge arc bug did not move and the digital display was frozen at 1.06. The other engine instruments on both the #1 and #2 engines indicated properly and there was no adverse yaw as both engines accelerated to near takeoff thrust. I verbalized the indicator malfunction. The captain did not respond. Because the engagement parameters were out of limits; I did not call for 'autothrottles on.' for backgnd information; it should be noted that normally during an MD88 autothrottle takeoff; there is a call of 'EPR xx' after they are engaged followed by at 60 KIAS 'clamp.' knowing that I would not get those calls without the autothrottles on; I again verbalized the EPR indicator malfunction. The captain did not respond. Upon reaching 80 KIAS the captain did not make the required call of '80 KTS; engine instruments checked.' I then stated '80 KIAS; engine instruments not checked. Check out the #2 EPR gauge. Do you want to continue the takeoff; captain?' at that time the captain stated 'I have the aircraft' and retarded the throttles to idle. He did not verbalize 'abort' as required by company operations specifications. I then visually verified he was on the controls; relinquished control of the aircraft; and noted the airspeed; it was approximately 85 KIAS at this time. Note that digital fdr information later verified the aircraft reached a maximum airspeed of 87 KIAS during the sequence. The captain did not deploy the thrust reversers as per the company operations specifications rejected takeoff procedure. For this reason; the spoilers did not deploy and the rejected takeoff brakes did not automatically engage. I then reached to manually deploy the spoilers. The captain prevented my hand from actuating them and said 'no. We don't need them.' he then began gradual braking. I told him that the rejected takeoff procedure calls for spoilers and reverse thrust and that the aircraft was not properly configured. The captain ignored me and continued to brake gradually in idle thrust. I monitored runway remaining and our deceleration rate. I was not comfortable with the fact that rejected takeoff procedures were not being used; the rate of deceleration or that the aircraft was not properly configured for the rejected takeoff. I considered overriding the captain by initiating harder braking from my side and again trying to deploy the spoilers and thrust reversers. Not long after considering that action; perhaps a few seconds; I determined that the aircraft would stop in the remaining runway and elected not to take additional action or attempt to assume control of the aircraft for fear that such action would compound the situation. As we were decelerating; the captain said; and I quote; 'tell the tower we are discontinuing the takeoff.' I complied with his order but; after yrs of practicing established procedure which is now ingrained habit; radioed to tower that we were and I quote 'aborting the takeoff.' I then made a PA telling the passenger to remain seated and to stand by for instructions. The captain never brought the aircraft to a complete stop on the runway. Instead he taxied clear at the second to last taxiway (taxiway E5) and stopped the aircraft. I told tower that no assistance was required and that we would be returning to the gate to check out an indicator malfunction. Tower cleared us to parking. The captain then proceeded to strike the throttles repeatedly and angrily shouted at me because I did not say 'discontinuing the takeoff.' he went on to say words to the effect that the FAA and NTSB would now become involved with the situation since I used the word 'abort.' the captain then started to taxi the aircraft onto parallel taxiway east. Because the captain had not spoken to the flight attendants yet; I called to ensure that passenger were not only seated but also had not attempted to evacuate/evacuation using the overwing emergency exits. Note that the MD88 has no indicator lights for those doors and as such; crew coordination is critical to safety. I also made an additional PA to the passenger and briefly explained the reason for the abort. I reminded them to remain seated until the 'fasten seatbelt' sign was extinguished after pulling in to the gate I then asked the captain if we could consult the QRH for guidance. He said no. I then asked him if I could consult the operational data manual brake energy section and observe any limitations. Note that this action is directed by the rejected takeoff procedure. He said no. I again stated that rejected takeoff procedure calls for that; and he answered with 'run the after landing checklist.' he also told me to make no more calls to ATC; the flight attendants; or the passenger without first obtaining his permission. I complied with the order and kept an eye on the brake temperature gauge. The brakes stayed below 200 degrees throughout the subsequent operation as well during the time spent at the gate. Note that at temperatures greater than 300 degrees the fuse plugs may melt. Peak temperatures are usually reached 20-30 mins after the event. The captain taxied into parking uneventfully and the aircraft was secured using normal procedures and checklists. Flight dispatch control and maintenance were notified and the event was entered into the aircraft logbook. It should be noted that I attempted to engage the captain afterwards to debrief the rejected takeoff. Just as I have done throughout my aviation career; I was open to candid conversation and hoped to gain a better understanding of the events that took place so that I could mature as an aviator. During the discussion; the captain said that the decision not to comply with the established rejected takeoff procedures was 'at his discretion' and I was incorrect to attempt to deploy the spoilers. He justified his employment of gradual braking as a means not to inconvenience the passenger by 'throwing them against their seatbelts.' he also criticized my communications with ATC; the flight attendants; and the passenger. To his credit; he apologized for losing his temper in the cockpit. After some reflection on the event; self-evaluation of my performance; and listening to the captain's justification for not following established procedures; I made the decision to remove myself from the rotation. During more than 15 yrs of flying crew aircraft; I have never had to do this. I well understand the multifaceted dynamics of this event. In the bigger picture; this was a rejected takeoff due to an engine instrument malfunction. It should have been a low speed abort. Instead; for reasons known only to the captain; it became an abort above 80 KTS. Further; established rejected takeoff procedures were not followed by the captain and he physically prevented me from executing my first officer duties as directed by company procedure. To our favor; the event occurred during day VMC on a dry runway in an aircraft that was not at maximum gross weight. Had conditions been less than optimal; the outcome may not have been as favorable. It should further be noted that this event occurred during my first rotation since completing recurrent training. I left there with not only a positive evaluation; but with confidence in my procedural knowledge as well as my ability to perform effectively in any emergency to include rejected takeoffs. Recommendations: the core of this event is a CRM issue. This should have been a slow speed abort below 40 KIAS due to an EPR gauge malfunction that the first officer spotted at throttle up. Instead; it became a high speed abort when the captain failed to make a timely abort decision. Further; for reasons only known to him; the captain deliberately chose not to follow company procedure. He also verbally and physically prevented the first officer from doing his duties during a rejected takeoff. During the debrief; the captain incorrectly stated that the employment of those procedures is at his discretion. Company operations specifications are clear: any rejected above 80 KIAS is a high speed abort and the rejected takeoff procedure will be used. To prevent this in the future; I recommend that the industry establish memory recall procedures (ie; 'bold face') for rejected takeoffs above 80 KIAS. In the stress of an emergency; habit patterns ingrained through training are what save the day. Eliminating the 'gray area' eliminates indecision as well as mitigates poor decisions. This event clearly started outside of the cockpit. The vast majority of the correspondence from senior flight operations management has not been to stress operational safety but rather addressing the need for additional employee pay cuts. At the time of the incident; the future of the solvency of the carrier is very much in question. I believe the pressure outside of the cockpit directly contributed to the errors made inside of it. Management should be setting the tone for safety; not negotiating a concessionary compensation package directly with the line pilot via flight operations communications channels.
Original NASA ASRS Text
Title: MD88 ABORTS TKOF WHEN EPR INDICATOR FAILS. DISPUTE OVER PROPER TECHNIQUE ENSUES BTWN CAPT AND FO.
Narrative: THE FLT WAS ROUTINELY DISPATCHED FROM THE GATE AND ALL CHKLISTS AND PROCS WERE ACCOMPLISHED IN ACCORDANCE WITH ESTABLISHED PROCS. IT WAS MY LEG AND DURING THE TKOF BRIEFING I STATED THAT WE WOULD BE USING RWY 28L BECAUSE; AT 10000 FT LONG; IT WAS LONGER THAN RWY 28R (8000 FT AVAILABLE) AND THE TAXI DISTANCE FROM THE SPOT WHERE WE WOULD DEICE WAS ESSENTIALLY THE SAME. THE CAPT SAID HE WANTED TO USE RWY 28R BUT GAVE NO OPERATIONAL REASON WHY. THE ACFT WT AND BAL SUMMARY DATA SUPPORTED EITHER RWY. AFTER DEICING; WE COMPLETED THE REMAINING CHKLISTS AND WERE CLRED FOR TKOF. I ASSUMED CTL OF THE ACFT ON THE ROLL AS THE CAPT COMPLETED THE ALIGNMENT AND I ADVANCED THE THROTTLES TOWARDS TKOF PWR. I IMMEDIATELY NOTICED THAT THE #2 ENG EPR GAUGE ARC BUG DID NOT MOVE AND THE DIGITAL DISPLAY WAS FROZEN AT 1.06. THE OTHER ENG INSTS ON BOTH THE #1 AND #2 ENGS INDICATED PROPERLY AND THERE WAS NO ADVERSE YAW AS BOTH ENGS ACCELERATED TO NEAR TKOF THRUST. I VERBALIZED THE INDICATOR MALFUNCTION. THE CAPT DID NOT RESPOND. BECAUSE THE ENGAGEMENT PARAMETERS WERE OUT OF LIMITS; I DID NOT CALL FOR 'AUTOTHROTTLES ON.' FOR BACKGND INFO; IT SHOULD BE NOTED THAT NORMALLY DURING AN MD88 AUTOTHROTTLE TKOF; THERE IS A CALL OF 'EPR XX' AFTER THEY ARE ENGAGED FOLLOWED BY AT 60 KIAS 'CLAMP.' KNOWING THAT I WOULD NOT GET THOSE CALLS WITHOUT THE AUTOTHROTTLES ON; I AGAIN VERBALIZED THE EPR INDICATOR MALFUNCTION. THE CAPT DID NOT RESPOND. UPON REACHING 80 KIAS THE CAPT DID NOT MAKE THE REQUIRED CALL OF '80 KTS; ENG INSTS CHKED.' I THEN STATED '80 KIAS; ENG INSTS NOT CHKED. CHK OUT THE #2 EPR GAUGE. DO YOU WANT TO CONTINUE THE TKOF; CAPT?' AT THAT TIME THE CAPT STATED 'I HAVE THE ACFT' AND RETARDED THE THROTTLES TO IDLE. HE DID NOT VERBALIZE 'ABORT' AS REQUIRED BY COMPANY OPS SPECS. I THEN VISUALLY VERIFIED HE WAS ON THE CTLS; RELINQUISHED CTL OF THE ACFT; AND NOTED THE AIRSPD; IT WAS APPROX 85 KIAS AT THIS TIME. NOTE THAT DIGITAL FDR INFO LATER VERIFIED THE ACFT REACHED A MAX AIRSPD OF 87 KIAS DURING THE SEQUENCE. THE CAPT DID NOT DEPLOY THE THRUST REVERSERS AS PER THE COMPANY OPS SPECS REJECTED TKOF PROC. FOR THIS REASON; THE SPOILERS DID NOT DEPLOY AND THE REJECTED TKOF BRAKES DID NOT AUTOMATICALLY ENGAGE. I THEN REACHED TO MANUALLY DEPLOY THE SPOILERS. THE CAPT PREVENTED MY HAND FROM ACTUATING THEM AND SAID 'NO. WE DON'T NEED THEM.' HE THEN BEGAN GRADUAL BRAKING. I TOLD HIM THAT THE REJECTED TKOF PROC CALLS FOR SPOILERS AND REVERSE THRUST AND THAT THE ACFT WAS NOT PROPERLY CONFIGURED. THE CAPT IGNORED ME AND CONTINUED TO BRAKE GRADUALLY IN IDLE THRUST. I MONITORED RWY REMAINING AND OUR DECELERATION RATE. I WAS NOT COMFORTABLE WITH THE FACT THAT REJECTED TKOF PROCS WERE NOT BEING USED; THE RATE OF DECELERATION OR THAT THE ACFT WAS NOT PROPERLY CONFIGURED FOR THE REJECTED TKOF. I CONSIDERED OVERRIDING THE CAPT BY INITIATING HARDER BRAKING FROM MY SIDE AND AGAIN TRYING TO DEPLOY THE SPOILERS AND THRUST REVERSERS. NOT LONG AFTER CONSIDERING THAT ACTION; PERHAPS A FEW SECONDS; I DETERMINED THAT THE ACFT WOULD STOP IN THE REMAINING RWY AND ELECTED NOT TO TAKE ADDITIONAL ACTION OR ATTEMPT TO ASSUME CTL OF THE ACFT FOR FEAR THAT SUCH ACTION WOULD COMPOUND THE SIT. AS WE WERE DECELERATING; THE CAPT SAID; AND I QUOTE; 'TELL THE TWR WE ARE DISCONTINUING THE TKOF.' I COMPLIED WITH HIS ORDER BUT; AFTER YRS OF PRACTICING ESTABLISHED PROC WHICH IS NOW INGRAINED HABIT; RADIOED TO TWR THAT WE WERE AND I QUOTE 'ABORTING THE TKOF.' I THEN MADE A PA TELLING THE PAX TO REMAIN SEATED AND TO STAND BY FOR INSTRUCTIONS. THE CAPT NEVER BROUGHT THE ACFT TO A COMPLETE STOP ON THE RWY. INSTEAD HE TAXIED CLR AT THE SECOND TO LAST TXWY (TXWY E5) AND STOPPED THE ACFT. I TOLD TWR THAT NO ASSISTANCE WAS REQUIRED AND THAT WE WOULD BE RETURNING TO THE GATE TO CHK OUT AN INDICATOR MALFUNCTION. TWR CLRED US TO PARKING. THE CAPT THEN PROCEEDED TO STRIKE THE THROTTLES REPEATEDLY AND ANGRILY SHOUTED AT ME BECAUSE I DID NOT SAY 'DISCONTINUING THE TKOF.' HE WENT ON TO SAY WORDS TO THE EFFECT THAT THE FAA AND NTSB WOULD NOW BECOME INVOLVED WITH THE SIT SINCE I USED THE WORD 'ABORT.' THE CAPT THEN STARTED TO TAXI THE ACFT ONTO PARALLEL TXWY E. BECAUSE THE CAPT HAD NOT SPOKEN TO THE FLT ATTENDANTS YET; I CALLED TO ENSURE THAT PAX WERE NOT ONLY SEATED BUT ALSO HAD NOT ATTEMPTED TO EVAC USING THE OVERWING EMER EXITS. NOTE THAT THE MD88 HAS NO INDICATOR LIGHTS FOR THOSE DOORS AND AS SUCH; CREW COORD IS CRITICAL TO SAFETY. I ALSO MADE AN ADDITIONAL PA TO THE PAX AND BRIEFLY EXPLAINED THE REASON FOR THE ABORT. I REMINDED THEM TO REMAIN SEATED UNTIL THE 'FASTEN SEATBELT' SIGN WAS EXTINGUISHED AFTER PULLING IN TO THE GATE I THEN ASKED THE CAPT IF WE COULD CONSULT THE QRH FOR GUIDANCE. HE SAID NO. I THEN ASKED HIM IF I COULD CONSULT THE OPERATIONAL DATA MANUAL BRAKE ENERGY SECTION AND OBSERVE ANY LIMITATIONS. NOTE THAT THIS ACTION IS DIRECTED BY THE REJECTED TKOF PROC. HE SAID NO. I AGAIN STATED THAT REJECTED TKOF PROC CALLS FOR THAT; AND HE ANSWERED WITH 'RUN THE AFTER LNDG CHKLIST.' HE ALSO TOLD ME TO MAKE NO MORE CALLS TO ATC; THE FLT ATTENDANTS; OR THE PAX WITHOUT FIRST OBTAINING HIS PERMISSION. I COMPLIED WITH THE ORDER AND KEPT AN EYE ON THE BRAKE TEMP GAUGE. THE BRAKES STAYED BELOW 200 DEGS THROUGHOUT THE SUBSEQUENT OP AS WELL DURING THE TIME SPENT AT THE GATE. NOTE THAT AT TEMPS GREATER THAN 300 DEGS THE FUSE PLUGS MAY MELT. PEAK TEMPS ARE USUALLY REACHED 20-30 MINS AFTER THE EVENT. THE CAPT TAXIED INTO PARKING UNEVENTFULLY AND THE ACFT WAS SECURED USING NORMAL PROCS AND CHKLISTS. FLT DISPATCH CTL AND MAINT WERE NOTIFIED AND THE EVENT WAS ENTERED INTO THE ACFT LOGBOOK. IT SHOULD BE NOTED THAT I ATTEMPTED TO ENGAGE THE CAPT AFTERWARDS TO DEBRIEF THE REJECTED TKOF. JUST AS I HAVE DONE THROUGHOUT MY AVIATION CAREER; I WAS OPEN TO CANDID CONVERSATION AND HOPED TO GAIN A BETTER UNDERSTANDING OF THE EVENTS THAT TOOK PLACE SO THAT I COULD MATURE AS AN AVIATOR. DURING THE DISCUSSION; THE CAPT SAID THAT THE DECISION NOT TO COMPLY WITH THE ESTABLISHED REJECTED TKOF PROCS WAS 'AT HIS DISCRETION' AND I WAS INCORRECT TO ATTEMPT TO DEPLOY THE SPOILERS. HE JUSTIFIED HIS EMPLOYMENT OF GRADUAL BRAKING AS A MEANS NOT TO INCONVENIENCE THE PAX BY 'THROWING THEM AGAINST THEIR SEATBELTS.' HE ALSO CRITICIZED MY COMS WITH ATC; THE FLT ATTENDANTS; AND THE PAX. TO HIS CREDIT; HE APOLOGIZED FOR LOSING HIS TEMPER IN THE COCKPIT. AFTER SOME REFLECTION ON THE EVENT; SELF-EVALUATION OF MY PERFORMANCE; AND LISTENING TO THE CAPT'S JUSTIFICATION FOR NOT FOLLOWING ESTABLISHED PROCS; I MADE THE DECISION TO REMOVE MYSELF FROM THE ROTATION. DURING MORE THAN 15 YRS OF FLYING CREW ACFT; I HAVE NEVER HAD TO DO THIS. I WELL UNDERSTAND THE MULTIFACETED DYNAMICS OF THIS EVENT. IN THE BIGGER PICTURE; THIS WAS A REJECTED TKOF DUE TO AN ENG INST MALFUNCTION. IT SHOULD HAVE BEEN A LOW SPD ABORT. INSTEAD; FOR REASONS KNOWN ONLY TO THE CAPT; IT BECAME AN ABORT ABOVE 80 KTS. FURTHER; ESTABLISHED REJECTED TKOF PROCS WERE NOT FOLLOWED BY THE CAPT AND HE PHYSICALLY PREVENTED ME FROM EXECUTING MY FO DUTIES AS DIRECTED BY COMPANY PROC. TO OUR FAVOR; THE EVENT OCCURRED DURING DAY VMC ON A DRY RWY IN AN ACFT THAT WAS NOT AT MAX GROSS WT. HAD CONDITIONS BEEN LESS THAN OPTIMAL; THE OUTCOME MAY NOT HAVE BEEN AS FAVORABLE. IT SHOULD FURTHER BE NOTED THAT THIS EVENT OCCURRED DURING MY FIRST ROTATION SINCE COMPLETING RECURRENT TRAINING. I LEFT THERE WITH NOT ONLY A POSITIVE EVALUATION; BUT WITH CONFIDENCE IN MY PROCEDURAL KNOWLEDGE AS WELL AS MY ABILITY TO PERFORM EFFECTIVELY IN ANY EMER TO INCLUDE REJECTED TKOFS. RECOMMENDATIONS: THE CORE OF THIS EVENT IS A CRM ISSUE. THIS SHOULD HAVE BEEN A SLOW SPD ABORT BELOW 40 KIAS DUE TO AN EPR GAUGE MALFUNCTION THAT THE FO SPOTTED AT THROTTLE UP. INSTEAD; IT BECAME A HIGH SPD ABORT WHEN THE CAPT FAILED TO MAKE A TIMELY ABORT DECISION. FURTHER; FOR REASONS ONLY KNOWN TO HIM; THE CAPT DELIBERATELY CHOSE NOT TO FOLLOW COMPANY PROC. HE ALSO VERBALLY AND PHYSICALLY PREVENTED THE FO FROM DOING HIS DUTIES DURING A REJECTED TKOF. DURING THE DEBRIEF; THE CAPT INCORRECTLY STATED THAT THE EMPLOYMENT OF THOSE PROCS IS AT HIS DISCRETION. COMPANY OPS SPECS ARE CLR: ANY REJECTED ABOVE 80 KIAS IS A HIGH SPD ABORT AND THE REJECTED TKOF PROC WILL BE USED. TO PREVENT THIS IN THE FUTURE; I RECOMMEND THAT THE INDUSTRY ESTABLISH MEMORY RECALL PROCS (IE; 'BOLD FACE') FOR REJECTED TKOFS ABOVE 80 KIAS. IN THE STRESS OF AN EMER; HABIT PATTERNS INGRAINED THROUGH TRAINING ARE WHAT SAVE THE DAY. ELIMINATING THE 'GRAY AREA' ELIMINATES INDECISION AS WELL AS MITIGATES POOR DECISIONS. THIS EVENT CLRLY STARTED OUTSIDE OF THE COCKPIT. THE VAST MAJORITY OF THE CORRESPONDENCE FROM SENIOR FLT OPS MGMNT HAS NOT BEEN TO STRESS OPERATIONAL SAFETY BUT RATHER ADDRESSING THE NEED FOR ADDITIONAL EMPLOYEE PAY CUTS. AT THE TIME OF THE INCIDENT; THE FUTURE OF THE SOLVENCY OF THE CARRIER IS VERY MUCH IN QUESTION. I BELIEVE THE PRESSURE OUTSIDE OF THE COCKPIT DIRECTLY CONTRIBUTED TO THE ERRORS MADE INSIDE OF IT. MGMNT SHOULD BE SETTING THE TONE FOR SAFETY; NOT NEGOTIATING A CONCESSIONARY COMPENSATION PACKAGE DIRECTLY WITH THE LINE PLT VIA FLT OPS COMS CHANNELS.
Data retrieved from NASA's ASRS site as of January 2009 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.