4
Flight Operations Communications 06/05/2015 Hangar Talk Delta Confidential and Proprietary Page 1 of 4 June 5, 2015 Previous Hangar Talk and Flight Standards Update articles are available via the “Line Lessons/Safety” link on the Flight Ops DeltaNet site. Introduction Hangar Talk is both about lessons learned and a confirmation of our professionalism. As professionals, we utilize our experiences to mitigate both the anticipated and unanticipated threats. As high achievers, many of us tend to internalize these issues. So our challenge is to share our experiences and our personal stories so that we can learn from each other—especially those situations that turned out to be a little more difficult than we might have anticipated. This month’s Hangar Talk is about to two exceptional crews. Both crews utilized their outstanding stick and rudder proficiency, combined with excellent CRM and TEM skills to manage two very unique and complex non-normals. B-717 ATL-SAV: Electrical Failure This first event occurred during daylight IMC conditions. The First Officer was a new hire on his first OE rotation. The Atlanta departure weather was reported as obscured with 3,000’ RVR. Weather throughout the entire southeast was very similar. The logbook indicated that on the previous flight the right generator had failed during the takeoff roll resulting in a low speed RTO. On that previous flight after returning to the gate, the right electrical generator was placed on MEL and subsequently re- dispatched utilizing the left generator and the APU. That flight was completed uneventfully. (This aircraft also had a second MEL item for inoperative auto-spoilers). Except for the extra time needed to review the MEL procedures, preflight, ground ops, and taxi-out were routine. With the RVR above the 1,600’ First Officer minimums, the Line Check Pilot permitted the new hire First Officer to be the Pilot Flying (PF). The takeoff was normal. Still in IMC conditions, climbing through 8,000’ the crew reported hearing a loud thud. Concurrent with the thud, both flight directors biased out of view and the autopilot and autothrottles disconnected. As the assigned PF, the new hire First Officer immediately assumed manual control of the jet. Because his Primary Flight Display (PFD) had failed, the First Officer was flying cross-cockpit using the Captain’s flight instruments. In fact, three of the six display units were blank. All had failed except the Captain’s PFD, ND, and Primary Engine Display. The Captain declared an emergency, elected to climb to 14,000’ anticipating being above the clouds (which was not the case) and began to assess the source of the multiple failures. The Engine and Alert Display (EAD) displayed several fault messages, some of which were continuously disappearing and reappearing. Constant clicking and clunking noises occurred in the background. Since the First Officer had lost both his PFD and ND, the Captain wisely took over PF duties. The Captain later reported that his PFD had remained steady, but his flight director repeatedly cycled in and out-of-view. He then asked the First Officer to begin to find the appropriate QRH procedure while he coordinated Hangar Talk June 2015

Hangar Talk - June 2015contentz.mkt932.com/lp/19805/176198/Hangar Talk - June 2015.pdfMD-88 DTW-ATL: Jammed Elevator on Takeoff The second event involves a MD-88 departing from Detroit

  • Upload
    others

  • View
    7

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Hangar Talk - June 2015contentz.mkt932.com/lp/19805/176198/Hangar Talk - June 2015.pdfMD-88 DTW-ATL: Jammed Elevator on Takeoff The second event involves a MD-88 departing from Detroit

Flight Operations Communications 06/05/2015 Hangar Talk Delta Confidential and Proprietary Page 1 of 4

June 5, 2015

Previous Hangar Talk and Flight Standards Update articles are available via the “Line Lessons/Safety” link on the Flight Ops DeltaNet site.

Introduction

Hangar Talk is both about lessons learned and a confirmation of our professionalism. As professionals, we utilize our experiences to mitigate both the anticipated and unanticipated threats. As high achievers, many of us tend to internalize these issues. So our challenge is to share our experiences and our personal stories so that we can learn from each other—especially those situations that turned out to be a little more difficult than we might have anticipated.

This month’s Hangar Talk is about to two exceptional crews. Both crews utilized their outstanding stick and rudder proficiency, combined with excellent CRM and TEM skills to manage two very unique and complex non-normals.

B-717 ATL-SAV: Electrical Failure

This first event occurred during daylight IMC conditions. The First Officer was a new hire on his first OE rotation. The Atlanta departure weather was reported as obscured with 3,000’ RVR. Weather throughout the entire southeast was very similar. The logbook indicated that on the previous flight the right generator had failed during the takeoff roll resulting in a low speed RTO. On that previous flight after returning to the gate, the right electrical generator was placed on MEL and subsequently re-dispatched utilizing the left generator and the APU. That flight was completed uneventfully. (This aircraft also had a second MEL item for inoperative auto-spoilers).

Except for the extra time needed to review the MEL procedures, preflight, ground ops, and taxi-out were routine. With the RVR above the 1,600’ First Officer minimums, the Line Check Pilot permitted the new hire First Officer to be the Pilot Flying (PF). The takeoff was normal.

Still in IMC conditions, climbing through 8,000’ the crew reported hearing a loud thud. Concurrent with the thud, both flight directors biased out of view and the autopilot and autothrottles disconnected.

As the assigned PF, the new hire First Officer immediately assumed manual control of the jet. Because his Primary Flight Display (PFD) had failed, the First Officer was flying cross-cockpit using the Captain’s flight instruments. In fact, three of the six display units were blank. All had failed except the Captain’s PFD, ND, and Primary Engine Display.

The Captain declared an emergency, elected to climb to 14,000’ anticipating being above the clouds (which was not the case) and began to assess the source of the multiple failures. The Engine and Alert Display (EAD) displayed several fault messages, some of which were continuously disappearing and reappearing. Constant clicking and clunking noises occurred in the background. Since the First Officer had lost both his PFD and ND, the Captain wisely took over PF duties. The Captain later reported that his PFD had remained steady, but his flight director repeatedly cycled in and out-of-view. He then asked the First Officer to begin to find the appropriate QRH procedure while he coordinated

Hangar Talk

June 2015

Page 2: Hangar Talk - June 2015contentz.mkt932.com/lp/19805/176198/Hangar Talk - June 2015.pdfMD-88 DTW-ATL: Jammed Elevator on Takeoff The second event involves a MD-88 departing from Detroit

Flight Operations Communications 06/05/2015 Hangar Talk Delta Confidential and Proprietary Page 2 of 4

the emergency and possible divert options with ATC. Hand flying, communicating with ATC, coordinating the divert options and keeping the Flight Attendants informed made for a very busy cockpit. Next, the crew needed to make sense of the multiple status messages and determine what QRH procedure was appropriate to reference first.

The malfunction was clearly electrical, but with rapidly changing EAD messages and multiple display failures, the source of the problem was certainly not obvious.

The Captain ascertained that the continuous cycling of EAD messages had occurred because the main electrical buses were being repeatedly powered and unpowered. The Captain determined the core issue was with the right AC bus. The Captain directed his First Officer, with assistance from the jumpseat pilot, to accomplish the RIGHT GENERATOR OFF procedure.

After completing the RIGHT GENERATOR OFF QRH procedure, the Captain’s Flight Director and display units two and three returned to normal operation. All the First Officer’s displays remained blank. For some unexplained reason, multiple EAD messages continued to disappear and reappear with the exception of the auto-trim system, which was completely inoperative.

Although it appeared that the left generator remained on-line and the APU was still operating normally, the Captain noticed that the Emergency Power light was illuminated. This indicated that the main aircraft battery was being discharged. The 717 battery will provide standby power for approximately one hour.

At this point the Captain directed the First Officer to conduct the ENG FADEC ALTN QRH procedure and review the list of equipment available on emergency power to prepare for the possibility of further electrical failures.

Faced with the uncertain electrical condition, no autopilots, low visibility conditions throughout the Southeast, and an OE new hire pilot in the right seat, the Captain decided it was time to determine where to land. Coordinating with ATC and the OCC and informing the Flight Attendants and the passengers, the decision was made to return to ATL.

The N-A-T-S brief included that this would be a hand-flown, raw data, ILS approach to ATL Rwy 9R. Tower reported RVR was 2,600’. The approach and landing were uneventful. The Aircraft Rescue and Fire Fighting (ARFF) vehicles were dismissed after an external inspection was completed.

Maintenance replaced the following components: the right generator, left power conversion distribution contactor, left generator contactor, right generator relay, right bus tie and the electrical power control unit. A verification flight was then conducted with no abnormalities noted, and the aircraft was returned to service.

MD-88 DTW-ATL: Jammed Elevator on Takeoff

The second event involves a MD-88 departing from Detroit. The pilots had already flown two legs on this aircraft, the logbook was “clean” and there was no history of any flight control malfunctions. The daytime weather was VFR with 10 miles of visibility.

During the takeoff roll at approximately 110-120 knots (Vr was 141 knots), the Captain (who was PF), felt the aircraft pitch up prior to any elevator input. Due to the high speed and rapid acceleration, the Captain elected to continue the takeoff.

During liftoff the pitch up became excessive requiring forward yoke pressure and nose down trim to maintain a reasonable pitch attitude. The landing gear retracted normally. During initial climb, continued forward yoke pressure and additional nose down trim was needed to accelerate the aircraft. The aircraft felt very tail heavy. The Captain elected to retract the flaps and slats. After doing so, he reported that the flight controls began to feel “mushy” and the aircraft began to buffet. The Captain accelerated 250 knots and climbed to 9,000’. After he leveled off, he transferred control of the aircraft to the First Officer to confirm his assessment of the flight control problem. The First Officer confirmed that something was definitely abnormal.

Recognizing the potential seriousness of the situation, the Captain resumed control of the aircraft and asked the First Officer to declare an emergency. ATC provided vectors back towards Detroit and told them to maintain 9,000 feet. The Captain briefed the Flight Attendants on the intercom declaring a yellow emergency and not to expect an evacuation. The crew requested a 20 mile final to allow them the time to run all the required checklists and check aircraft controllability as they incrementally extended the flaps and slats. Prior to joining final, the First Officer made a PA to the passengers explaining the situation and informing them that they would land shortly.

Page 3: Hangar Talk - June 2015contentz.mkt932.com/lp/19805/176198/Hangar Talk - June 2015.pdfMD-88 DTW-ATL: Jammed Elevator on Takeoff The second event involves a MD-88 departing from Detroit

Flight OperHangar Ta

As the apressure precautioneeded bwere uneand ARFFgate and loaded air

The post eyebolt hare controbut were were obse

The FleetSeptembeaircraft rethe castlewould not

Two ensu

• CFl

• Te• A• R

in• Pr• Pu• D

2

Discussio

• Dai

• Nti

• Barse

• Tbo

rations Commulk

ircraft sloweand almost fn, the Captaoth hands to

eventful. AfteF personnel i requested arcraft.

flight inspectad come loosolled by trim unable to locerved.

t Managemeer 2014 (threceived a core nut cotter t have backed

re this type o

onducted a lorida and Meech Ops execdded secondaevised the e

nspected resented a Saublished a Te

Delta Tech Op015. They re

on

During both evircraft. Both ceither non-nme, used theoth crews dire you mainetting during hese two creoth flights lan

unications

ed, the Captfull nose dowain briefed th fly. Except f

er landing, thnspected thea load audit

tion reveled sse and jamm tabs and cancate the asso

ent Team revee months brrosion inspecpin was neved off.

of event neve

high priorityexico. No othcutives visitedary inspectioelevator “wo

afety Presentech Ops advisps Quality Aseported confi

vents the pilocrews prioritiormal situat

eir resources,isplayed excetaining your the various ews displayednded uneven

Delta Co

ain noted thn trim, similahe First Officfor the extremhe First Officee aircraft andbelieving th

something enmed the right

n operate indociated cotter

viewed the before this evction that reqer installed.

er recurs, De

y safety insper defects wed both facilitins

orks cards” t

tation at thessory notice hissurance Safdence that th

ots did not haized aircraft cion was fully, weighed theeptional man stick and ruphases of fligd exceptionatfully.

Correcinstalled

pin

onfidential and

hat the aircrar to the inpucer to be premely abnormer made a PAd reported noeir abnorma

ntirely differe elevator in adependently.)r pin. The lef

aircraft histovent), at a Dquired the reHad the cott

lta Tech Ops

ection at there noted. ies

to require m

se maintenanighlighting thfety Inspectohis type of er

ave a clear pcontrol. (”Aviy covered byeir options annual flying skudder skills? ght?) l professiona

ctly cotter

d Proprietary

raft requireduts required iepared to coal control inpA instructingo anomalies.l could have

ent. The rightan up position) Mechanics ft elevator wa

ory beginninDelta supervmoval of the ter pin been

:

is and other

multiple sign

nce stations inhe event ors conductedrror will not b

icture of exaiate, navigate any one QR

nd were delibkills. During Do you kno

alism and exp

substantial immediately ontrol the thputs, the appg passengers The flight c

e resulted fro

t elevator pown. (The left alocated the sas inspected

ng from Januvised mainten elevators. Itproperly inst

r Delta supe

-offs of wor

n Florida and

d a follow-upbe repeated.

ctly what wae, communicaRH procedureerate with thlower worklo

ow the basic

pertise. Beca

06/05Page

nose down after takeoffrottles in cas

proach and la to remain screw taxied tom an impro

wer boost cyand right elevsecuring castl and no anom

uary 1, 201nance stationt is suspectedtalled, the ey

rvised faciliti

rk completed

Mexico

p audit this s

s wrong withate”). e. They took heir decisionsoad opportunc pitch and p

ause of their

Missin

5/2015 3 of 4

yoke . As a se he nding eated to the operly

linder vators le nut malies

4. In n, the d that yebolt

ies in

d and

spring

h their

their . nities, power

skills

ng eyebolt

Page 4: Hangar Talk - June 2015contentz.mkt932.com/lp/19805/176198/Hangar Talk - June 2015.pdfMD-88 DTW-ATL: Jammed Elevator on Takeoff The second event involves a MD-88 departing from Detroit

Flight OperHangar Ta

The Flight

Fly safely

Captain EDirector –

Bill Captain BDirector –

rations Commulk

t Crew Traini

y,

Ed Sternstein – Flight Stand

Bill Klein – Flight Safet

unications

ng Manuals (

dards

ty

Delta Co

(FCTM) on all

onfidential and

fleets provid

d Proprietary

des the followwing guidance

06/05Page

e:

5/2015 4 of 4