PDA

View Full Version : Swarm of bees grounds UK aircraft


SinBin
25th May 2007, 15:10
Apparently a Palmair 737 out of EGHH suffered a bee strike!!

http://news.bbc.co.uk/1/hi/england/dorset/6691851.stm

Richard Taylor
25th May 2007, 15:26
Engine surge an hour after flying through them!

visibility3miles
26th May 2007, 15:12
OK, maybe this will end up on JetBlast.....
http://news.bbc.co.uk/2/hi/uk_news/england/dorset/6691851.stm

Last Updated: Friday, 25 May 2007, 13:11 GMT 14:11 UK

Almost 200 passengers found themselves stranded at Bournemouth Airport for 11 hours after their plane turned back after flying into a swarm of bees.

The Palmair Boeing 737, bound for Faro in Portugal, took off from Bournemouth at 0810 BST on Thursday.

But after flying into the swarm the pilot experienced an engine surge an hour later and returned the aircraft to the UK for checks.

Engineers ruled it was unsafe to fly and another plane took off at 1915 BST.

old,not bold
26th May 2007, 15:48
This event reveals serious shortcomings in the training of aircrew, if we read between the lines of the report in todays Times newspaper.

It turns out that, after experiencing some power surges, and then after a short silence a loud bang, the pilot was instructed to return to BOH using only one engine. He came on the radio to tell passengers that, in simple terms, something akin to a carburetor failure had occurred, and that they would go back to BOH.

This raises several questions;

1. Why did the pilot have to be instructed on what to do, ie return to BOH using only one engine? Are pilots not trained to make such decisions?

2. Why did the pilot not know that he is provided with a PA system? There was no need to use the radio, and, for that matter no guarantee that every passenger would have one switched on to listen with. This is a Health & Safety issue as well as a training issue.

3. Finally, I realise that in these straightened times airlines such as Palmair have to keep their costs down. But a little technical training for the pilot would have meant that he would have known immediately that a swarm of bees could not have affected the carburetter on his jet; any fool knows that they could not possibly have got through the airfilter.

8846
26th May 2007, 16:13
OK OnB I'm going to suspend my disbelief here and imagine that you have written a serious post.... I may come to regret this....

Aircrew often make decisions in consultation with company ground staff of an operational nature - i.e. which airfield the company would prefer them to divert to when a 'situation' develops. The company does not tell them which engine to shut down or any other such thing. The final call rests with the crew or, more specifically, the captain.

A swarm of bees is going to have to be pretty bloody dense to affect a JET engine which DOES NOT have a carburettor. I think this explanation was offered as an analogy which might have made more sense to passengers.

Our friends in the media are occasionally(?) particularly inept at writing aircraft related stories with any sort of technical accuracy. I can almost always get a good laugh out of reading a journalist's interpretation of any flight-related story. Of particular comic value was the unforgettable piece in the Times some years ago where a journalist attempted to describe the dangerous effects of flying near thunderstorms. The principal cause of dangerous height loss on final approach in the vicinity of thunderstorms was attributed to the weight of water built up on the wings from the rain....

The stuff written in the papers isn't for us as flight crew, more for the general public, but it wouldn't hurt to get it a bit more 'right' now and again.

At this rate we'll have passengers peering into CFM56s looking for the K&N air filters...!:ok:

ChristiaanJ
26th May 2007, 16:42
8846,
OnB has been around here a bit longer than you... give him some slack :)

From the newspaper article:
"It is believed the plane's engines ingested the bees while flying over Bournemouth but this did not cause problems until later into the flight."

About an hour later, it seems.
What baffles me, seriously, is how they established any kind of "cause and effect" relationship between the two events.

An engine surge or flame-out at the moment of the encounter I could have believed. But a few remaining bee carcasses causing an engine surge an hour later? Pull the other one, it's got bells on.

ChristiaanJ
26th May 2007, 16:56
Why did the pilot not know that he is provided with a PA system?OnB,
I very much doubt that the PA system, as being totally non-essential, is on the PalmAir MEL.

old,not bold
26th May 2007, 16:56
Oh dear.....

It was meant as an ironic comment on the report! Saturday afternoon and all that.

BOAC
26th May 2007, 17:03
o,nb - it was not wasted:) Did the paper say that the a/c would definitely need a 'B' check?

slipper1
26th May 2007, 17:03
Laugh, I nearly wet myself!! well done old not bold, you actually got someone to bite !!! It was extremely lucky the passengers were listening out on frequency at the time, otherwise they would have thought they had arrived at destination!
Ps: Maybe the pilot had fitted an induction kit to make it go faster (or sound louder), and had removed the airfilter?

ChristiaanJ
26th May 2007, 17:14
.... a swarm of bees could not have affected the carburetter on his jetOnB,
Being old is not ALWAYS an advantage... You obviously have NO experience with them new FADEC-controlled carburettors.

20,000 bees in the air-fuel mix would have upset the scheduling no end, but it would have taken some time to recalculate the PSJ parameters, hence the surge occurring later.

old,not bold
26th May 2007, 17:27
ChristiaanJ; I acknowledge the technical purity of your suggestion, not bad for a radio man, but I'll go with slipper's go-faster mod as the more likely explanation.

You know what these new young pilots are like, speed, speed speed, it's all they think about.

It's the start of the slippery slope of course; next it's ecstasy, then who knows......?

old,not bold
26th May 2007, 17:30
BOAC, Sir;

No, I don't think so, but I wish it had!

Danny
26th May 2007, 21:03
Gentlemen and ladies, there's already a 'corny joke' thread of this incident in JB. Just click here (http://www.pprune.org/forums/showthread.php?t=277558). This is being merged into the original thread on this topic which was started yesterday and will stay to see if there's any technical info on this incident worthy of review or discussion here. :ugh:

ChristiaanJ
26th May 2007, 21:12
Danny,
Just looked at the linked topic and nearly had a "wet monitor" moment.
But it would be interesting to know what really happened..... before the urban legend "Bees Bring Down Airliner" gets fully entrenched.

The Grim EPR
27th May 2007, 06:56
Don’t shoot me down gentlemen, this is my first post and I am a mere SLF. I believe what happened was more along these lines.

The aircraft encountered the bees shortly after take off whilst climbing to FL70. The flight deck window went darker (with what I am going to describe as ‘bee juice’ – not a technical term). There was a momentary change in engine note. Coincidently, the aircraft levelled off at FL70 as previously instructed by ATC.

When cleared to climb again and the power was increased, the engine began to surge. The captain elected to return to Bournemouth, but was currently over the max landing weight. As there was no emergency situation, the aircraft was flown until the landing weight was within limits.

The engine was not shut down in flight. Total time block to block was around 55 minutes I believe.

Upon arrival at BOH the aircraft was inspected, the engine was boroscoped and the flap assembly cleaned and checked (the aircraft was apparently black with the ‘bee juice’ I mentioned earlier. The aircraft was taken for an air test (with no passengers obviously). It was found that at some power settings there were still surges / bangs.

The engine was inspected and boroscoped again, no blades were found to have been damaged. The engineers changed the engine and I believe that the incident engine has been sent away to be stripped down.

Apparently it is has proved to be extremely difficult to get the black staining off the aircraft…

tribekey
27th May 2007, 09:20
And just to add a few FACTS. On departure there was no mention of any problem from the pilot to atc. the aircraft climbed out of FL70about 15 miles south of eghh. The pilot indicated he wanted to return to eghh when the aircraft was about 50 miles south of eghh. the pilot mentioned there had been an engine surge but was not declaring an emergency. there was not an engine shut down, aircraft landed on both.

yeoman
27th May 2007, 11:12
As someone whose expertise regarding jet engines is pretty much confined to "spin it, chuck fuel in, set fire to it, go flying", is it possible that such a large concentration of reasonably sized insects could have blocked probes etc in the intake and upset the FADEC or similar TMS or whatever?

lomapaseo
27th May 2007, 13:33
As someone whose expertise regarding jet engines is pretty much confined to "spin it, chuck fuel in, set fire to it, go flying", is it possible that such a large concentration of reasonably sized insects could have blocked probes etc in the intake and upset the FADEC or similar TMS or whatever?

FADECS are typically programed to synthensize missing parameters from the aircraft like inlet probes. However it might (outside of my experience) be possible for bee juice to screw up internal engine probes that set the bleed operation for accel conditions. This certainly sounds like a one-off to me and the outcome was well managed.

RichT
27th May 2007, 19:19
Just to explain why the engine didn't surge until an hour after the bee strike. Palmair use EAC 737-200s it is probable that the bees managed to fly in front of the JT8Ds for an hour until they got tired.

lomapaseo
28th May 2007, 04:11
Just to explain why the engine didn't surge until an hour after the bee strike. Palmair use EAC 737-200s it is probable that the bees managed to fly in front of the JT8Ds for an hour until they got tired.

well forget about FADECs and bee juice problems. Come to think of it I would forget about the surge as well

India Four Two
29th May 2007, 11:35
Slight thread creep, but fits in with this topic :)

I42

http://i30.photobucket.com/albums/c309/india42/Beeinpitottube.jpg

rdmallows
29th May 2007, 16:53
Is it true that they buzzed the tower so engineers could have a closer inspection before the approach was made?

ChristiaanJ
29th May 2007, 17:07
LOL, marshmallow.....

However, India Four Two might have a point?
Could a really dense swarm have caused a right royal jelly mess in the various pressure sensing ports?

vegit8
1st Jun 2007, 20:13
Hi everyone.
Have joined this forum having read the threads on the bee strike.

I was seated in 5a and I beleive the problem was with the port engine.
I do not come from an aviation background but I have 20 years experience as a firefighter and a good general understanding on mechanics and a feel for when things are "not quite right"..

On take off I thought I heard a noise that was unsual, my initial reaction was that the underbelly had scraped the runway as the pilot pulled the stick back and the nose wheel lifted.

I know this is probably impossible but thats what went through my mind.

We climbed normally and the flight was uneventful until after the channel islands.
As we aproached the Brest peninsula there was a series of loud bangs. The plane vibrated noticibly. I thought it felt like the cargo hatch was banging.

Everyone fell silent and the aircrew looked decidely edgy.

There was no announcement and the plane continued at the same speed and altitude.
The stewardess contacted the filght deck using the internal phone.

About 2-3 minutes later the same thing happened again.
This time the engines were throttled back and airspeed dropped.

The stewardess made an announcement and the seat belt lights came on.

about a minute later the captain came on the tannoy and said that there had been an engine malfunction and that we were returning to bournemouth.

We banked quite quickly and the engine note was significantly less (on my side of the plane).

We flew directly back to BOH without any circling as suggested previously and made a very soft landing without any reverse thrust used at all.

There were no emergency vehicles stood by and the landing was probably one of the better ones I have experienced recently, nothing like the ryanair method which seems to be hit the runway as hard as possible and then brakes and loads of reverse thrust.

Once back at the terminal we were advised to remain seated whilst an initial assesment was made. After about 20 minutes we were disembarked. The rest is history.

We took off at 09:15 ish (not 08:15 as reported) and landed at 10:25 the whole flight lasting almost 1 hour.

I hope this helps you guys

Regards

Geoff