WYIA

New Member
Feb 19, 2009
228
0
UK - Leeds
INCIDENTS LOG

I thought a thread should be started that logs all incidents involving LBA flights, for topical discussion & input relating to the events.

Anything from a technical fault leading to a diversion or PAN, aborted take off, go around, tyre burst, diversion to another airport due to a problem and again any of the above affecting a Leeds flight down route.

Aside from relying on our sources at the airport and airlines you can also see a daily log of all incidents relating to aircraft in the world on "The Aviation Herald" website. avherald.com

Give it a try, you can refine your search to Leeds Bradford or say Jet2 for a run down of all incidents relating to the airport or that airline. Remember that it is a public forum and you do get comments on it from pilots as well as the public and the information on it is not always quite accurate. Still a very interesting website!
 
INCIDENT
KL1551
AMS-LBA
16.11.10

A Fokker 70 registration PH-KZM was making an approach when the pilots aborted the attempt due to low visibility.

On climb out from the go around the aircraft developed several fault alerts and apparent control issues caused by a Stabiliser Jam.

The aircraft levelled off and the crew worked through emergency checklists. A decision was made to divert to Manchester for better weather conditions and a longer runway.

A PAN was called by the pilots and the aircraft made an emergency landing into Manchester approximately 30 minutes after the initial go around at Leeds Bradford.

Passengers onboard the flight said they had a briefing from the cabin crew and had to assume the brace position for landing as a precaution.

The landing at Manchester was uneventful and after a check by the fire service the aircraft was able to taxi to a parking position without further assistance.

Passengers disembarked normally and continued their journey to Leeds by road.
 
But why just for LBA?
 
TheLocalYokel said:
But why just for LBA?

It seems like a good idea for a thread. There's no reason why we can't start similar threads in our other airport forums. ;)
 
Last edited by a moderator:
Sorry, I misread the intention.

I thought it was to be a stand-alone forum outside the LBA section.
 
REPORT###REPORT###

jet2.com B733 at Chambery on Feb 7th 2010, EGPWS alert during ILS approach



A jet2.com Boeing 737-300, registration G-CELC performing flight LS-451 from Leeds,EN (UK) to Chambery (France) with 103 passengers and 6 crew, was on approach to Chambery with the intention to perform an ILS approach to runway 18 but circle to land on runway 36. The first officer was pilot flying. The aircraft passed the initial approach fix when ATC advised the crew that winds were from 360 degrees at 7 knots and asked whether the crew could accept a landing on runway 18. The captain replied that if the wind remained the same they could. The aircraft was then cleared for the approach. The aircraft left the hold at the initial approach fix at an altitude of 6500 feet in instrument meteorologic conditions and proceeded according to the published approach procedure with the autopilot engaged. After the CY VOR had been selected for most of the approach the captain selected CY ILS and found it indicating normally indicating a DME of 13nm. At DME 12 at an altitude of 5000 feet the autopilot captured the localizer, at DME 11 the VS mode of the autopilot activated and the aircraft began to descend at 2200 fpm. The captain noticed the loss of ILS information on his electronic attitude indicator (EADI) and looked across to see whether the first officer's indications were still there. They appeared to be, so he looked down at the AUTO/MAN selection switch for the navigation frequency to determine whether the correct frequency was set, recycled the switch and the ILS indications returned to view. ATC contacted the aircraft with a frequency change instruction, the captain acknowledged, but before he completed the frequency change he noticed that the airplane was below the glideslope and descending in excess of 2000 fpm. The commander queried the first officer "are you happy", the first officer replied he was not and initiated a go-around. At that time an EGPWS "TERRAIN TERRAIN PULL UP" alert activated. The captain called positive climb, the gear was selected up, and the aircraft climbed through 6000 feet at an pitch angle in excess of 20 degrees nose up and 110 KIAS. The first officer lowered the nose to accelerate, the crew set course for the CY NDB being uncertain of their position and the reliability of their other navigation systems. The captain queried ATC about the serviceability of the ILS and was assured the ILS was serviceable. The crew subsequently performed a second approach and completed a safe landing.

The AAIB released their bulletin reporting that the operator had provided a comprehensive brief for Chambery including the note: "Beware of possible false glide-path indications. The glide path should not be used until within 12.1 DME CY."

THe airplane had a flight management system installed without GPS. An EGPWS was installed which provided its own GPS source. The GLIDESLOPE alert is active below 1000 feet radar altitude and with the landing gear extended.

Usually an ILS approach is being flown with the autopilot in approach mode, however, if a circling is to follow the ILS approach, the manufacturer recommends to use the VOR/LOC (lateral) and VS (vertical) modes. The operator had adopted this recommendation as standard operating procedure.

The investigation had a complete recording of the flight data recorder and the EGPWS recording of the terrain alert, however the cockpit voice recorder capable of storing 2 hours had been overwritten during the return flight.

The flight data recorder showed that the airplane had levelled at 5000 feet with the autopilot in ALT and VOR/LOC mode. The autopilot captured the localizer from the right doing a gentle turn. At 11DME the vertical channel was changed to VS, at that point the airplane was about 850 feet below the glideslope, the airplane started to descend at 2200 fpm. About 10 seconds later the captain's localizer and glideslope were briefly shown not computed indicating the raw data were no longer available or not reliable, the DME showed 10.5nm which was accurate. During the further descend the captain's localizer and glideslope were shown not computed two more brief times.

The airplane was approaching the airport from the north requiring the aircraft to fly over the ridge of high ground to the east of Lake Bourget. As the airplane descended the terrain closure rate progressively increased to 6000 fpm. When the airplane descended through 1125 feet the EGPWS level 2 terrain alert activated. At the same time the autopilot was disengaged and a go-around was initiated - due to recording rates it could not be determined whether the go-around was initiated prior to or after the EGPWS alert. The minimum terrain clearance was 1112 feet. The aircraft reached a maximum nose up attitude of 32.7 degrees shortly after the EGPWS alert, the minimum airspeed was 109 KIAS, the aircraft stabilized at a climb rate of 3800 fpm.

During the subsequent approach and landing no further anomalies were recorded in the localizer, glideslope and DME data.

The first officer reported in post flight interviews, that the aircraft had intercepted the localizer satisfactority however he had noticed the DME on the ILS was intermittent. Flaps 15 were selected and the gear was extended. He saw the glideslope pointer rapidly move down the scale and in response selected VS and selected a descent rate he intended to be 1200 fpm. He recollected that the captain remarked "it's operating in the reverse sense", he took it to mean the localizer indication. He expanded his VOR/ILS display and observed the beam bar was slightly offset. The first officer commented that this action briefly distracted him from monitoring the descent profile.

The first officer recalled that he caught a glimpse of a mountain through a gap in the cloud, noticed that the airplane was way below the glideslope at a high rate of descent, he heard the commander say "are you happy" and disconnected the autopilot and commenced a manual go-around without selecting TOGA as he thought they were above 2000 feet with TOGA being unavailable. When he heard the EGPWS he increased the pitch angle to as much as possible. After the airplane climbed clear of the cloud he levelled to accelerate before continuing to climb to FL090. He commented that the control column needed a strong push to recover the airplane to level flight.

The captain said in post flight interviews that the landing runway was to be deicided once visual contact was established. After selecting the ILS frequency he saw the airplane was established on the localizer though slow in acquiring the center line, he called "12 DME with descent at 8.9" aiming to remind the first officer about the descent point. After passing 11.7 DME his ILS indications were gone and ILS fail flags appeared in view, there was no DME indication. He checked the first officers instruments where the indications were still present. He then recycled the AUTO/MAN switch after which the ILS and DME indications re-appeared. His attention then returned to the flight instruments and he recalled the airplane was descending at a high rate and was below the glideslope. He questioned the first officer who in turn initated a go-around.

The AAIB analysed that there was no evidence of any signal interruption or failure on the CY ILS or DME. The aircraft's navigational equipment was found serviceable when tested after landing. The reason for the first loss of the commander's localizer, glideslope and DME indication could not be determined. However, the second and third period of "not computed" signals were probably the captain's actions to recycle the AUTO/MAN switch.

While the commander's attention was diverted to the ILS display problem the first officer initiated a descent at an excessive rate before the aircraft had reached the final approach fix. The commander remained unaware of that descent profile until his attention returned to monitoring the flight profile, he questioned the situation, the discrepancy was acknowledged and the first officer initiated a go-around. The terrain clearance never reduced below 1100 feet.
 
INCIDENT
5.2.11

KL1540
FK70

Returned back to LBA shortly after departure with a serious technical issue, yet to be disclosed.
Awaiting further details regarding the incident.
 
Hi

Dont know if anyone knows about this as its not been reported yet on here, At about about 17:15 GMT this evening (Thursday 24/02/11) a light Aircraft registered G-GDEF ran-off the runway and closed the airfield for a short while.

The said aircraft in the incident was reported as been a Robin DR400/120 Piper which belongs to a Mrs J Shackleton from Oxenhope. All person's onboard were reportedly ok.

The airport was reopened by about 17:40. A Jet2.com Boeing 737-300, G-CELB and Eastern Airways, Jetstream 41 G-MAJI had to both go into the LBA overhead hold. Meanwhile flybe.com, Dash 8-Q400, G-FLBF was on the taxiway awaiting back-track for take-off.
 
Also this morning a Jet 2 boeing 737-300 took off operating I believe the 271 service and had a failure of all the co-pilots instruments. He held for around 45 mins south of the field before making an approach and landing on runway 32.
He held at 4000 ft and his Sbs altitude only showed 1000 ft. Probably an air data computer no 2 failure or similar event.
 
Ls185 - LBA to Malaga - 18/5/2011

Today's flight left 75 minutes late, has circled over Cheshire for an hour and looks to be coming back to LBA. Any news?
 
Re: Ls185 - LBA to Malaga - 18/5/2011

Now had a text from someone who was on the flight - quite hairy stuff. Only one engine, circled to burn off fuel, had to do a no flaps high speed landing at MAN with full emergency procedures in place.
 
Thank you for the information wingwalker

It will all come out in the wash once the report is filed. The old no flaps landing is not uncommon. Generally speaking airlines will opt for the longer runway because of the high speed landing involved.

An Airtours Boeing 757 had taken off from Manchester in fog a few years back and the pilot opted for LBA because a CAT III was out of the question at Manchester. The flight landed safely but used every last metre of the runway.
 
As a result, at around 1210pm this afternoon (18th) G-CELJ departed MAN to AGP as LS185A. I am not sure whether it was flying passengers to AGP or whether it was to just pick up passengers waiting in AGP, but I'm sure people will be able to add details to this as they become available.
 
the aircraft i believe was G-CELS, it was operating the AGP 185 as you've already menstioned, it pushed back just after 0800 but came back on stand with APU genarator problems, as it had to start engine 1 on stand, The issue was then resolved and it was on it's way. There were two aircraft on the ground at LBA, they could have quiet easily done an aircraft swap, but as you say it diverted to MAN
 
Multiflight’s, Beech 76, G-OADY blocked Leeds/Bradford Airports runway 32 for just over an hour this morning after suffering a nose wheel collapse on landing at 10:04. The runway was reopened at around 11:10.

There are now some delays expected on flights for the reminder of the day. 1x Flybe Dash 8-Q400, G-FLBD diverted to Manchester inbound on the BE731 from Belfast City.

Source: http://www.bbc.co.uk/news/uk-england-leeds-14958957

Leeds Bradford airport: Plane lands with wheel problem

_55426739_55425849.jpg

The plane was towed off the runway

Two people, including the pilot, have walked away from a light aircraft which landed at Leeds Bradford International Airport with reported nose wheel problems.

The aircraft landed safely at 10:04 BST on Saturday.

A fire crew was on stand-by but was not needed.

A spokesperson said the runway was closed but was due to reopen. The spokesperson said the closure was not expected to affect other flights.
 

Upload Media

Upgrade Your Account

Subscribe to help support your favourite forum and in return we'll remove all our advertisements. Your contribution will help to pay for things like site maintenance, domain name renewals and annual server charges.



Forums4aiports
Subscribe

NEW - Profile Posts

A week off work done which resulted in 6 day trips , 50 miles walked and only 2500 photos, Going to work is more of a holiday as I tended to be out of my flat an hour earlies in my week off and back for after 8pm
according to some people, you only need 1 day in each of the Yorkshire Dales, North Wales and Lake District "to have seen it all". Which is why its minibus tour number 3 this year of the Yorkshire Dales for me on 16th October. Different routes and different things to see each tour.
Apologies for any issues today, I was planning on updating the site but sadly something went wrong so the upgrade has been postponed. Apologies again for any inconvenience caused.
Aviador wrote on JENNYJET's profile.
Thank you for your kind donation to our running costs Jenny.
I've done 2 minibus tours with Mountain Goat this week. Monday was North York Moors with over 600 photos and today High Adventure in the Lakes with 750. photos. Slightly snap happy.
I've asked Gareth Southgate for the winning lottery numbers. He said 1, 2, 3, 4, 5 and 6

Trending Hashtags

Advertisement

Back
Top Bottom
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.