jb747
Enthusiast
- Joined
- Mar 9, 2010
- Posts
- 12,850
After the "loud bang" did you commence the descent immediately or did you run through other procedures first ?
There was a extremely loud bang. Basically a dull thud, like door being slammed. The aircraft rocked and rolled a little (not far, a few degrees), and the autopilot disconnected. The FO had been flying the sector, and he grabbed the controls. First thought from both of us was that an engine had 'let go'. I looked inside to see which engine, and I distinctly remember all four showing a nice stable 1.57 EPR. At this point there had been no warnings (other than the autopilot, which had been cancelled). A short period later (one second, five seconds, I have no idea), the EICAS came up with "DOOR 2 RIGHT". Basically that's an impossibility, as the doors are physically larger than the hole they are seated in, but obviously something had happened. I started to pull up the synoptic display for the doors, but before I could do so, I saw the cabin pressurisation data "pop up" on the upper EICAS. This is normally hidden, but appears automatically if the cabin exceeds 10,000 feet.
At this point, without understanding the how or why, I realised that we were having a depressurisation event, and I yelled 'depressurisation, masks on'. The checklist consists of only a few items, and they are done from memory. Mask, communications (can we talk to each other), isolation valves are closed (one possible cause of a depressurisation is a duct leak, and that will isolate it), passenger oxygen on. 22 seconds after the bang, with the FO still manually flying (he'd tried to engage an autopilot again, but without success), I pulled the thrust levels to idle, and selected the speed brakes up. I also selected 10,000 feet and flight level change on the MCP (even without the autopilot that commands the flight director).
I declared a Mayday as we left our cruise altitude. We still didn't really know what was happening, but it couldn't be good. Another airline transmitted right over the top of my call!..so I did it again, and a Cathay flight came up, relayed the message, and told everyone else to shut up.
Bernie (FO) had the aircraft in a nice stable descent. Looking back at the EICAS, it was now alive with messages, most of which made no sense. Failures generally have some sort of relationship to each other, but many of these were from totally unrelated systems. Looking at the cabin, it had totally depressurised. I decided to reopen the isolation valves, as closed they shut down one of the packs. The problem obviously wasn't the duct, so whilst a third pack wasn't going to make much difference, it couldn't hurt. About now, a couple of messages appeared, warning us of low crew and passenger oxygen pressure. Whilst it might sound callous, I wasn't concerned about the passenger oxygen, as we were already doing all we could, and the worst that would happen (in the very short term I was considering) is that someone might have a sleep. The crew oxygen was ominous though, because if we had a sleep, with the autopilot disengaged, things probably wouldn't go well. Because of that, we elected to accelerate by about 20 knots (normally with a structural issue, you come down at the speed things happened or less). The synoptic for both systems was showing about 50 psi, which looked like a valid reading (it goes blank when not valid, or sensor u/s), and was nothing like the 1800 psi that's normally shown.
Somewhere around here I just wound the heading bug in the direction of Manila.
Looking inside again, because the messages made so little sense, I pulled up the raw data for the major systems...engines, hydraulics, electrics..and all seemed reasonable. I was particularly interested in the #3 engine, as whatever had happened was near it.
At some point Bernie gave the autopilots another go, and this time the L system engaged.
Approaching 10,000 feet the cabin crew were told to 'commence their follow up duties'. At this point we had some feedback from the cabin...which was more or less, 'nobody has been hurt, the door is shut, and there is a hole in the floor'.
We obviously had a few things happening. We had to tidy up the EICAS / checklists as best we could. We were obviously diverting, and whilst initial decision was Manila, we had to look at that again, and get ourselves set up to actually do it. And we needed to get the aircraft weight down to something reasonable. So, having skimmed through the checklist and taken care of what looked immediately important, we moved on to the fuel dump, and planning for the landing. I gave my checklist to the SO, and got him to look again at all of the messages, so see if there was anything we could resolve (actually, nothing was ever corrected...).
I was still happy having Bernie flying the aircraft as it left me free to manage the failures, and to set up our arrival. Unfortunately, part of the failures had frozen my CDU (the box the access the FMC though) so it became necessary to take over from Bernie so that he could do the programming. His side was reluctant too, but he eventually got it to accept Manila.
At this point, the nasty part of the event was essentially over. We still had a number of issues that could affect the landing (autobrakes, and antiskid), plus we weren't sure what the flaps would do, but basically we had a aircraft that was behaving, and which we could land. We elected not to fly in cloud any more than we had to simply because our flight instruments had degraded and we were now operating on one single source of air data. That pretty much chose the runway for us, as 24 Manila required an ILS approach in rain, whilst 06 was clear and we could approach visually.
We continued the fuel dump to well below max landing weight. With no anti skid we didn't want any excess weight. The dump was secured by the SO at just over 20 miles to run, and about 30 tonnes remaining. Landing itself was quite normal. There was a quite noticeable 'burble' through the elevator (disturbed air flow?), but nothing of consequence. Stopped about 3/4 of the way down the runway.