You are browsing the archive for: May 2010
28 May 2010

British Airways Flight 038

On 17 January 2008, British Airways Flight 38 crash-landed short of the runway at Heathrow Airport. At the time, the newspapers were filled with mad speculation about the cause of the accident, ranging from computer failures, bird strikes, electronic glitches, low quality fuel and wind shear.

Within two days I had had enough of the media frenzy. I wrote about the incident with some frustration at the time:

Fear of Landing » Crash-landing at Heathrow : Just the Facts, Please

There is a lot of speculation going on in the press and, worse, a lot of speculation being presented as fact. The words “Absolute nonsense!” have become a frequent sound in our household as we read the articles in the popular press. I know accident reports aren’t everyone’s thing, but in the interests of understanding what happened, here is a quick run-down , based on the initial report.

Following an uneventful flight from Beijing, China, the aircraft was established on an ILS approach to Runway 27L at London Heathrow.

Nothing out of the ordinary until the final approach: that is the plane has already done its initial descent. The stewerdesses are buckled up and the plane is coming in to land. This is the hectic bit of the flight. A pilot friend of ours jokes that he gets paid for hours of boredom with a little bit of excitement at the beginning and the end. Some of the newspaper reports seem to almost imply that planes land themselves as they bandy about terms like Instrument Landing System and auto-thrust. Planes can land themselves in certain circumstances but it’s rough, we still prefer real people to put the planes onto the ground. It really is a safe assumption that the pilots would be giving the situation their full attention.

Initially the approach progressed normally, with the Autopilot and Autothrottle engaged, until the aircraft was at a height of approximately 600 ft and 2 miles from touch down.

At 600 feet they would be forty seconds away from anticipated touchdown. Then, something went wrong.

At approximately 600 ft and 2 miles from touch down, the Autothrottle demanded an increase in thrust from the two engines but the engines did not respond.

This is the loss of power: equivalent to putting your foot down and your car not accelerating.

Following further demands for increased thrust from the Autothrottle, and subsequently the flight crew moving the throttle levers, the engines similarly failed to respond.

The pilots immediately realised there was a problem and manually pushed the levers and got the same effect: no power.

Forty seconds is not a lot of time to make decisions and the ones we are hearing about in the press seem to have been sensible. Put the auxiliary power on. Don’t mess about with changing control, let the co-pilot land. Keep the plane in the air for as long as possible. Get the damn plane clear of the road.

The aircraft stopped on the very beginning of the paved surface of Runway 27L.

It seems likely that, given the time they had to make a decision, the pilots simply focused on getting that plane to the runway. They didn’t but they made it to the ground and cleared the perimeter fence: well done! There’s not a lot of options when you are in a 777 with no power, 600 feet above the ground.

The big question is: Why did the power fail? Any comment on that is complete speculation at the moment: the only information so far is why it didn’t.

[Read the full article]

The Air Accidents Investigation Branch (AAIB) released its final report a few months ago and I was remiss in not reporting back. But now we finally have the specifics of what happened and a logical view of the cause.

The AAIB has determined that the loss of power (specifically a reduction in thrust) was caused by a restricted fuel flow to both engines.

Speculation at the time included the possibility that there was water in the fuel, since the lack of response from the engine was consistent with fuel starvation but it was clear that the plane had fuel. They now believe that the restrictions were caused by ice in the fuel feed pipes.

Note FOHE is the Fuel Oil Heat Exchanger.

1/2010 G-YMMM – Conclusions

The investigation identified the following probable causal factors that led to the fuel flow restrictions:
1) Accreted ice from within the fuel system released, causing a restriction to the engine fuel flow at the face of the FOHE, on both of the engines.
2) Ice had formed within the fuel system, from water that occurred naturally in the fuel, whilst the aircraft operated with low fuel flows over a long period and the localised fuel temperatures were in an area described as the ‘sticky range’.
3) The FOHE, although compliant with the applicable certification requirements, was shown to be susceptible to restriction when presented with soft ice in a high concentration, with a fuel temperature that is below -10°C and a fuel flow above flight idle.
4) Certification requirements, with which the aircraft and engine fuel systems had to comply, did not take account of this phenomenon as the risk was unrecognised at that time.

Point 4 is important as it clarifies that there were no certification safety requirements missing from the aircraft.

Boeing have confirmed that they have taken steps to help prevent fuel restrictions caused by ice in the fuel, although the circumstances that led to the situation are described as unique.

A large number of the recommendations from the AAIB are focused on safety in the event of a crash, based on the results of this incident where there was insufficient time to brief the cabin crew. Most of the passengers were not aware of any issue until the plane was on the ground.

It’s good news that we understand more about ice and have conclusive studies about some of the rarer conditions in which it can appear. Still, not quite as exciting as the popular press seemed to be hoping for at the time, eh? Searching for additional details for this blog post, I noticed a rather subdued reaction to the results, especially in contrast with the original frenzy.

Oh well, mustn’t grumble.

21 May 2010

Unbelievable

A collection of aviation links that I honestly shouldn’t be amused by, but I am. Sometimes you just have to laugh.


JetBlue Pilot Threatens To Crash Plane Leaving From Boston If Girlfriend Doesn’t Reconcile – wbztv.com

The pilot, who has not been identified, was taken into custody at Logan for allegedly sending an email to his girlfriend in which he said if they did not reconcile their relationship, he was going to crash the plane.

The officer was questioned by the FBI at the airport, and taken to a Boston hospital for a psychiatric evaluation.

I know it isn’t really funny but the response on PPRuNe was classic:
JetBlue Pilot Threatens To Crash Plane – PPRuNe Forums

The TSA / FAA / Government knee-jerk reaction to this will be great!

“Pilots Banned From Having Significant Others”


Also found on PPRuNe: Multiple bird strike and how not to handle it:

I was shouting at the computer as I watched this. By the end, I was banging my head against the keyboard. Simply unbelievable.


Cockpit Conversation: Simple Security

I thought this was clever for straightforward access.

It allows visiting pilots to get into the lounge without fuss while offering a clear signal to non-pilots that this is a restricted area. No, it won’t keep anyone out who seriously wants to get in but stops it from being treated as a free-for-all.


And this is an oldie but a goodie: Pouring ice tea while flying inverted:

I’ve seen this clip before but it never ceases to make me smile.


If you are looking for a more serious collection of links, take a look at last week’s post on Golf Hotel Whiskey: Best of the Web.

14 May 2010

Aircraft Collides into Car in North Weald

North Weald Perimeter RoadFire Crew at North WealdLast Sunday I heard about a surprising incident at North Weald, one of my favourite airfields and the location where the Saratoga is currently parked and waiting for me to pay it some attention.

It seems that this Aero AT-3 was coming into land when something went wrong.

The main runway was closed for a drag-racing event. Runway 13 was open and in use. It seems the aircraft initiated a go-around and then began descending – for reasons unknown – near the Squadron on the perimeter road. It was here that he ran into the Volvo pulling away from the Squadron. He rear-ended the car and both vehicles burst into flames. The Volvo occupants were able to exit the car and drag the pilot out of the aircraft.

Fire crews were on site for the drag race and were able to react immediately.

Incident Report
Incident No: 9155
Date: 09-05-2010
Time: 14:25
Details: Aircraft and car alight

Address: North Weald Airfield, Merlin Way, North Weald

Attendance: 2 x Epping, 1 x Ongar, 1 x Harlow

Crews are working with North Weald Airfield’s volunteer fire crew to tackle a blaze involving an aircraft and a car. The volunteers were fortunately at the airfield to provide cover to a drag race event so were immediately on hand when the accident happened.

At 14:50 hrs, firefighters report that they one main jet and foam are being used to extinguish the blaze – 50 per cent of the car, a Volvo X60. and 50 per cent of the aircraft – a two seater single engine AT3 – are alight.

Crews are assisting Ambulance paramedics in dealing with one casualty – a man, who is believed to have been piloting the aircraft. No details relating to the extent of his injuries are available at this time but they are believed to be serious and he was taken to hospital.
The incident was dealt with by 15:09 hrs.

A fire service spokeman at the scene said: “An onlooker who saw the incident told us that the plane appeared to come into land but immediately took off again, banking over the top of a hanger before coming back to try a second landing and clipping the back of a brand new Volvo with two people inside who were driving out of the airfield.”

Station Officer Len Cleary, the officer in charge, said: “The pilot was lucky. It appears that the two people in the car brought him clear of the fire after the collision.

“It is not clear at this stage whether the incident was caused by mechanical failure or human error.

“The volunteer fire team acted swiftly to cover the scene with a blanket of foam so when we arrived the fire was under control.

“We have now scaled back our investigation but may return to the scene should the Civil Aviation Authority deem an investigation necessary.”

Here is a photograph of the Cockpit of Aero AT-3 G-UKAT by David Moth before the accident.

Photograph by David Moth

This is what it looks like now:

The accident photographs are courtesy of the Essex County Fire and Rescue Services Incident Image Library.

There’s a little more information on this post on the Flyer Forums message board from an eye-witness.

Aircraft and car incident at North Weald

I arrived at NW on Sunday disappointed to find that the main runway was shut for drag racing, and that they were using RWY13 with a wind of about 04012KT (according to EGSS METARs) which put it about on the x-wind limit for my aircraft. I was therefore keeping a good look out on the other traffic seeing how they were coping with the x-wind on the shorter runway, I’d never used RWY13 before and there is quite a dip in it too.

Having been to give my aircraft a check, I was walking along the taxiway which runs infront of the squadron and looked up just as the aircraft was climbing out (I wasn’t looking in time to see if it had taken off or was going around, so cannot end the speculation on that point I’m afraid). At approx 150ft and in line with the taxiway intersection, the aircraft entered a rather sharp left turn through approx 90 degrees, pointing toward me (North) for a few seconds, and possibly still climbing but difficult to tell now from this angle. It continued this left turn, angle of bank appearing to get steeper and aircraft now descending, almost over the top of the squadron at this point. The turn continued and descent was quite rapid by this point, and by the time the aircraft had gone behind the squadron out of sight it was now pointing South, perpendicular again with RWY13. A second or so later I heard the bang, and once I’d gone round the corner observed that the aircraft had hit the Volvo somewhere on it’s right side, as it was driving away from the squadron area.

The Air Accidents Investigation Branch (AAIB) have already been to the site as a part of their investigation. I’ll add a link to the sidebar when the report comes out but by all accounts, the pilot is lucky to have escaped with his life.

07 May 2010

November 666 Echo X-ray, Do You Read?

(Something from the archives: a 2008 post about Air Traffic Service Units in the UK and my native ability to talk too much. I’ll be back with fresh content next week.)

Air/Ground Radio Airfields with A/G Radio offer an information service with a radio operator who are not licensed and not under close CAA supervision. They identify themselves by saying the airfield name followed by the word radio. It could just be a guy on a mobile radio with no other support. They will offer a basic information service and report known traffic to you.

“Enstone, this is November 666 Echo X-ray.”

No response. I frowned.

“Enstone Radio, this is November 666 Echo X-ray, radio check.”

It had been a chaotic day and we were late leaving. And now that finally everyone was bundled up into the plane and ready to go, the youngster on the radio wasn’t responding. Technically, I didn’t have to request permission to start but it’s generally the polite thing to do. The last time I flew from this airfield, the chap called me just as I was entering the runway to let my know my son had left his bookbag in the cafeteria. Service like that is invaluable and so I didn’t like to risk upsetting anyone but it was frustrating to be sitting here waiting on someone who’d walked away from the mike.

I called a third time, no response. Had he gone for a cup of tea or what? Cliff frowned at me and I shrugged. I decided to try once more. This fourth call elicited a response: a confused voice came back over the radio.

“Are you talking to me?”

I winced. Who was playing with the radio, for god’s sake? That’s when Cliff’s mum piped up from the backseat.

“I don’t understand why you are saying Enstone Radio,” she said.

I started to snap back an answer when it sunk in. We were at Bembridge on the Isle of Wight. I’d been flying in and out of Enstone the previous week and we’d be landing there today but right now? We weren’t talking to them.

“Bembridge, this is November 666 Echo X-ray, request, uh … geography check.”

I could hear the relieved laughter as he responded. “November 666 Echo X-ray, confirmed, you are parked just outside of my window.”

“Thanks for that. Request start.”

“Nothing to affect,” he told me and we were finally on our way.

Flight Information Service Airfields with FIS are an information air traffic support unit staffed by licensed Flight Information Service Officers. They identify themselves by saying the airfield name followed by the word Information. Their function is to assist pilots to operate safely by offering a traffice service and helping with information regarding weather and aerodrome details.

The tricky thing about Information stations is how they let you know what you should be doing without ever actually telling you what to do.

“Shobdon, this is November 666 Echo X-ray, inbound to you.”

“November 666 Echo X-ray, this is Shobdon Information, go ahead.”

“November 666 Echo X-ray is a PA32 inbound to you, I’m looking to join the circuit downwind for runway 09, right hand.”

The response was immediate. “November 666 Echo X-ray we have three in the circuit, recommend an overhead join.”

I had already descended to 1,300 feet, too low for the manoeuvre that he was referring to, flying over the runway and then descending on the dead side. I also couldn’t see the point, I was perfectly set up to simply turn right and join the circuit in another mile.

He repeated the call. “November 666 Echo X-ray, recommend an overhead join.”

As I continued towards the airfield, I felt frustrated and confused: the advice that the Officer was giving me didn’t make sense. I didn’t like to argue with him, however, and I had to admit it wouldn’t make that much difference to me.

“November 666 Echo X-ray is climbing to 2,300 feet for overhead join.”

A moment later, it suddenly clicked. I was saying Runway 09 but I had been heading for the join for Runway 27, that is, the same runway going the opposite direction. I couldn’t possibly join downwind from my present position which is why he wanted me up and out of the way of his traffic.

I went overhead and joined downwind from a sensible position, much to the relief of Shobdon Information.

Air Traffic Control Airfields with an ATC service have an active control tower staffed by air traffic controllers and are under close CAA supervision. Only ATC are authorised to issue clearances. They identify themselves by saying the airfield name followed by their function (Ground, Tower, Approach, Director, Radar). They offer a variety of services including control, flight information and traffic.

The flight from Guernsey to Alderney was only notable in its simplicity: it took longer to get everyone into the plane than it did to make the journey. Only as we landed did it get hectic.

“Backtrack and exit at Alpha.”

I always feel a faint Top Gun thrill at phrases like that which sound so complicated but I now know are simple. “Wilco” I said with a knowing nod.

Except that having spun the plane around, I couldn’t find Alpha. There was a bit of a turn-in on my right but it disappeared into grass and with the wet weather I was worried about taking a wrong turn and getting stuck in the mud. I grabbed for my plate with a map of the airfield.

“Turn right,” said an impatient voice on the radio. “And expedite, I’ve got another one coming in.” Two planes at the airfield at once, this must be a veritable traffic jam by Alderney standards. I bit my lip and turned the plane right onto the grass and paused.

“Carry on,” said the voice again. “Straight ahead, between the two markers. I take it you’ve never been here before?”

“Affirm,” I said in my best professional pilot voice. Followed by “Sorry,” blowing away any semblance of radio competence.

“Just carry on straight. And expedite!”

Finally the map and the ground in front of me clicked into place, I wondered if the air traffic controller could see the small light bulb appearing over the cockpit as I made my way to the parking area. I had just chosen a nice easy spot to park when the voice came back.

“Pull forward to the blue markers, then face south and then west.”

I frowned as I pulled forward, was he trying to make it difficult?

“Which way is south,” I hissed at Cliff as I fumbled to get the map out again.

“Turn left,” he said. I turned then tried to picture a map in my head. If I am facing south then I’m looking towards Texas. California is west and on my right. Got it! I opened my eyes and looked around. “So west is to the right now, right?”

Cliff sighed at me. “Just use the Directional Indicator?”

I blushed and turned the plane until the DI pointed west.

“Just park there,” said the voice. The other plane had landed and radio silence descended. It would probably be at least an hour before they see any further traffic. I shut the engine down.

Military Air Traffic Zones It goes without saying that you should be unfailingly polite to any controller who has fighter jets to back him up. In the UK, the pilot should contact the controller either 15 nautical miles or 5 minutes flying time from a military boundary, whichever is sooner, requesting penetration. To enter the central area (Aerodrome Traffic Zone) you must receive permission and comply with the controller’s instructions.

My first run-in with the military was actually in France.

We had landed at an airfield for refuelling but they were having technical difficulties and informed us that they would not be able to offer fuel for the rest of the day. A quick glance at book showed us another airfield on route that listed AVGAS 100L and so we jumped into the plane and went straight there, plotting the route as we went.

“Cognac, this is November 666 Echo X-ray.”

“November 666 Echo X-ray, pass your message.”

“November 666 Echo X-ray is a PA32 inbound to you, currently 20 miles to your NW at 4,000 feet, request airfield information and joining instructions.”

There was a brief pause.

“November 666 Echo X-ray can you state your intentions.”

“We’re inbound to you for refuelling.”

“November 666 Echo X-ray are you aware that this is a military airfield?”

“Oh. Uh, no. Negative. I was not aware.”

“November 666 Echo X-ray I say again, can you state your intentions?”

I bit my lip but silence seemed likely to get a missile aimed in my direction.

“Er, I intend to ask your advice on where we could go for refuelling in the local area?”

The controller was perfectly friendly about it, verifying that I was not in an emergency before recommending that I fly direct to Angouleme and even offering me a heading and a flight information service directly to the airfield. Anything, I guess, to keep me out of his zone.

Using the radio professionally has become an essential requirement in the modern aviation environment. Radio provides the interface between you and others, especially the Air Traffic Service Unit (ATSU) whose frequency you are using. You will make life more comfortable for yourself (and others) if you can use the radio efficiently.

The Air Pilot’s Manual: Radiotelephony for the Private Pilot’s Licence

When I first started my PPL, I was told that I had a real knack for using the radio. Getting my radio licence was the easiest part of the entire training. Little did I know that in the meantime, I would manage to mess up speaking to every different type of Air Traffic Service Unit in existence.