If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
B735, vicinity London Heathrow UK, 2007
From SKYbrary Wiki
|On 7 June 2007, a Boeing 737-500 operated by LOT Polish Airlines, after daylight takeoff from London Heathrow Airport lost most of the information displayed on Electronic Flight Instrument System (EFIS). The information in both Electronic Attitude Director Indicator (EADI) and Electronic Horizontal Situation Indicators (EHSI) disappeared because the flight crew inadvertently mismanaged the Flight Management System (FMS). Subsequently the crew had difficulties both in maintaining the aircraft control manually using the mechanical standby instruments and communicating adequately with ATC due to insufficient language proficiency. Although an emergency situation was not declared, the ATC realized the seriousness of the circumstances and provided discrete frequency and a safe return after 27 minutes of flight was achieved.|
|Actual or Potential
|Air-Ground Communication, Human Factors, Loss of Control|
|Operator||LOT Polish Airlines|
|Type of Flight||Public Transport (Passenger)|
|Origin||London Heathrow Airport|
|Intended Destination||Warsaw/Okęcie Frédéric Chopin Airport|
|Take off Commenced||Yes|
|ICL / ENR|
|Location - Airport|
|Airport vicinity||London Heathrow Airport|
Data use error,
Procedural non compliance
|Tag(s)||Degraded flight instrument display,|
Flight Management Error
|Damage or injury||No|
|Causal Factor Group(s)|
On 7 June 2007, a Boeing 737-500 operated by LOT Polish Airlines, after daylight takeoff from London Heathrow Airport lost most of the information displayed on Electronic Flight Instrument System (EFIS). The information in both Electronic Attitude Director Indicator (EADI) and Electronic Horizontal Situation Indicators (EHSI) disappeared because the flight crew inadvertently mismanaged the Flight Management System (FMS). Subsequently the crew had difficulties both in maintaining the aircraft control manually using the mechanical standby instruments and communicating adequately with ATC due to insufficient language proficiency. Although an emergency situation was not declared, the ATC realized the seriousness of the circumstances and provided discrete frequency and a safe return after 27 minutes of flight was achieved.
[After landing at London Heathrow (LHR), and] during the turnround, the pilots carried out a ‘fast realignment’ procedure for the two Inertial Reference Systems (IRSs)*, which required a ground position to be entered. This was done by the co-pilot on the Flight Management Computer (FMC) Control Display Unit (CDU) using the commercial chart Stand 114 position as the reference. However, although the value of the co-ordinates entered was correct, the longitude was entered as East instead of West. The longitude co-ordinate was thus entered […] 33.5 nm to the east of the actual aircraft position.
[…] The co‑pilot was the handling pilot. Immediately after takeoff, at 1009 hrs, the pilots noticed that there was almost no information on their EHSIs and EADIs; they described the displays as ‘blank’ [See Figure 1].
Approximately 40 seconds after takeoff, the aircraft entered cloud at around 1,500 ft aal and the co-pilot had no option but to fly using the standby attitude indicator and standby compass for attitude and heading reference; the airspeed and altitude indications were unaffected. The autopilots were not available but autothrottle remained available and in use.
As the aircraft climbed through an altitude of 3,000 ft, the commander contacted London Terminal Control North East (TCNE) Departures […] and advised that the aircraft had a ‘navigation problem’.
The controller asked if the aircraft was able to fly a heading of 055° and the commander replied that they could. The heading was assigned and the commander was instructed to maintain 6,000 ft. However, after about 30 seconds, the controller called [the aircraft] and advised that the aircraft appeared to be tracking north.
The reply from the commander was unintelligible and the controller said he would call the aircraft back. The controller now dealt with several other aircraft before calling [the aircraft] again. He advised the commander that the aircraft was tracking northwest and instructed him to ‘FLY A HEADING OF ZERO FIVE ZERO DEGREES THAT’LL BE A RIGHT TURN OF APPROXIMATELY 90 DEGREES’. [The crew] acknowledged the instruction but, a minute later, the controller noticed the aircraft was tracking approximately west. At this stage there were a number of exchanges between [the crew] and the controller in which it was apparent that the commander, who was making the radio calls, was not able to understand some of the instructions.
The controller then asked for the crew’s intentions and, after another exchange, the commander decided to return to LHR. Heading and altitude instructions were given. The altitude instructions were complied with and gradually the aircraft began to follow the headings […].
[…] the controller handed [the aircraft] over to a dedicated controller on a discrete frequency. The new controller issued heading instructions and asked the crew if they were able to fly an ILS; the commander replied that they could. Further heading instructions, together with altitude and speed instructions were given. Altitude and speed were complied with but the aircraft continued to respond to heading instructions slowly and erratically. The controller attempted to vector the aircraft to the west on a heading of 260°, to allow for an extended final approach track, but the aircraft maintained a heading of south and cut across the localiser course for Runway 09L at 90°. The commander then reported that he had “GLIDESLOPE ONLY, NO DIRECTION”. The controller asked the crew to turn left on to a northerly heading, which was achieved, and then on to a heading of 060°, to intercept the localiser. However, the aircraft continued to fly north and again passed through the localiser at 90°; the commander again reported that he had “NO DIRECTION ONLY GLIDESLOPE”.
The controller now advised [the crew] that he would give radar vectors until visual contact with the runway was established. He issued ‘start and stop’ turn instructions and a further descent clearance. […] the commander reported “RUNWAY IS THE GROUND IN SIGHT” and was cleared for a visual approach to Runway, 09L. However, the controller noticed that the aircraft continued to track to the south of the airfield and asked the commander to confirm that they were approaching Runway 09L. The commander replied it was not in sight and, a moment later, that he was now visual for Runway 09L. […] the controller issued a landing clearance for Runway 09L. In the meantime, the ATC Ground Supervisor became concerned that the aircraft appeared as though it might be landing on Runway 09R, and asked for the traffic to be cleared from the runway. […] the aircraft landed on Runway 09L and taxied to a parking stand.
In Difficulties experienced by the pilots section, the Bulletin states:
The pilots appeared confused by what had occurred and had to fly the aircraft in IMC using only the standby instruments for heading and attitude reference. Pilots of modern EFIS equipped aircraft do not routinely fly their aircraft using a basic instrument presentation and without a map display. When suddenly presented with such a situation, pilots will need time to adapt their instrument scan and a higher level of crew co-ordination to enable them to conduct a safe instrument approach.
The commander also had some difficulty with comprehending and communicating with ATC. At the time, his workload was high and he was under stress, both factors which would have contributed to his problem.
When the co-pilot realised that the normal heading and attitude references were not available, he quickly reverted to using the standby instruments. The commander decided that the co-pilot should continue to fly the aircraft to allow himself extra capacity to manage the failure. After takeoff, with the aircraft in a climbing attitude and about to enter cloud, visual references would have been limited. The standby attitude instrument is small and located on the left side of the flight deck, making it difficult to use from the co-pilot’s side. The heading reference was obtained from the standby compass, an instrument which is relatively easy to read in straight and level flight but difficult in turns. To turn onto a specific heading it is generally necessary to use a timed turn technique. Furthermore, because the compass card is vertically mounted, the direction of turn is often misinterpreted. This was demonstrated when, for the first few heading instructions from ATC, the aircraft turned in the opposite direction. In contrast, the normal instruments were available for altitude and speed, and instructions relating to these were complied with throughout.
During the flight the pilots continued to have difficulty in complying with heading instructions and were not able to fly the aircraft to intercept the ILS course to Runway 09L. To attempt an intercept with the navigation system in this degraded configuration, without direct heading reference, would require a high level of crew co-ordination. In fact, because of the non‑compliance with the heading instructions, the aircraft crossed the ILS course at 90°, which would have made the task of intercepting it almost impossible. The pilots had little idea of their position and, after a few minutes, they were entirely dependent on ATC for their navigation. ILS DME range information was available but the pilots were offered no information from ATC, other than track miles to run, about their geographical location. It would have helped their situational awareness if their location relative to the airport and updated weather information had been given to them.
[…] The departure controller at LHR already had a high workload at the time this incident started and the declared ‘navigation problem’ was more severe than he anticipated. He stated afterwards that, if the pilot had said there was an ‘instrument problem’, then his own response might have been different. Furthermore, the aircraft did not declare a MAYDAY, even when asked specifically if there were any other problems.
[…] While the aircraft was being vectored, it was getting nearer to the airport and was descending, under ATC instructions, without following any recognised procedure. This was an undesirable situation and was only resolved because visual contact was established by the pilots. The situation arose because ATC did not initially understand the nature of the aircraft’s problem; this was compounded by the difficulty of obtaining information from the pilots because of their limited command of English. The commander did not declare a MAYDAY, so the aircraft was not treated as an ‘emergency’ aircraft. However, it should have been possible for ATC to have recognised earlier that the aircraft was not able to comply with instructions, even if the pilots appeared to think otherwise, and to have treated it as though a MAYDAY had been declared.
The AAIB bulletin provides the following conclusion:
A fairly simple error in the pre-flight procedure of entering the aircraft’s position into the IRS went undetected and led to a serious incident. Better cross-checking procedures, either when initially entering data or by conducting a check of the entered route against that displayed on the map, would have prevented the situation from developing.
This incident demonstrates how reliant pilots may become upon the FMS, and how essential it is to ensure that the system is provided with accurate data.
The Bulletin produces several Safety Actions addressed to the operator and the ANSP. See Further Reading - AAIB Bulletin 6/2008, page 32).
Because these actions have already been initiated by the organisations concerned, no Safety recommendations are made.
Notes of the SKYbrary editor:
*The IRSs provide attitude, heading, acceleration, vertical speed, ground speed, track, present position and wind data to the aircraft systems. For the incident aircraft, the IRSs are the only source of attitude and heading information, with the exception of the standby instruments.
See the AAIB Bulletin 6/2008 in Further Reading for more details on IRSs initialisation, alignment and comparison tests.
- AGC - Emergency Communications; Cross-Checking Process; Non-Standard Phraseology; Work in progress:English Language Proficiency Requirements; Accidents and Serious Incidents Reports: AGC
- LOC - Loss of Control; Bank Angle Awareness;
- HF - Crew Resource Management (CRM); Active Listening in ATC; Line Oriented Flight Training (LOFT);
- For the full report of this Serious Incident see the relevant extract taken from Bulletin 6/2008 - EW/C2007/06/02 published by AAIB - UK.