B734, Lahore Pakistan, 2015
From SKYbrary Wiki
On 3 November 2015, a Boeing 737-400 (AP-BJO) being operated by Shaheen Air International on a scheduled domestic passenger flight from Karachi to Lahore as NL-142 landed off an unstabilised non-precision approach at Lahore in day IMC and both main landing gear assemblies collapsed as it departed the side of the runway. An emergency evacuation followed and none of the 121 occupants were injured during the excursion or the subsequent evacuation but the aircraft sustained extensive damage.
An Investigation was carried out by the Pakistan Safety Investigation Board (SIB). The FDR and CVR were recovered from the aircraft and their data successfully downloaded. It was noted that the 59 year-old Captain, who had been PF for the accident flight, had accumulated 19,302 hours total flying experience of which the 4,859 hours on type had included 3719 hours in command. The 34 year-old First Officer had 2,076 hours total flying experience of which 410 hours were on type.
It was established that both pilots had reported late for duty prior to the departure from Karachi, the rostered report time being 90 minutes prior to the scheduled flight departure time (STD). The First Officer arrived ahead of the Captain and obtained operational briefing and the weather for Lahore which showed that it was below the minimum RVR for the available approaches at that time although with an improvement forecast. The Captain arrived 45 minutes before the STD. A NOTAM obtained by the First Officer stated that the main runway at Lahore (36R) was not available due to work to upgrade the ILS and instead a VOR/DME approach was available on runway 36L. It was found that this information was not accorded the appropriate degree of pre-flight attention by the crew.
After takeoff, the flight climbed to its planned cruising altitude of FL 330. Before the top of descent, the latest destination weather was obtained and included a visibility of 1,200 metres, which was below the minimum of 1,600 metres required for the available VOR/DME approach by a Category ‘C’ aeroplane. In the expectation that the weather would improve, the approach brief was conducted for that approach and on transfer to Lahore ACC, the Captain instructed the First Officer to request initial positioning to a 10 mile final for closed runway 36R, apparently because he was planning to follow the ILS procedure for runway 36R and then break off after becoming visual with the runway to land on runway 36L - a non-standard procedure. Lahore ACC declined this request and confirmed that the visibility was still below that required for the available VOR/DME approach.
Before changing to Lahore APP, the Captain told the First Officer to request the RNAV approach for runway 36R despite the fact that the aircraft was not in compliance with the mandatory navigation equipment for RNAV approaches and the Operator had “issued necessary instructions in this regard”. Soon afterwards, the First Officer had to point out that the Captain had selected runway 18L instead of runway 36L on the FMGC and the CVR data from this time indicated that the Captain was having difficulty “identifying / reading and feeding the correct arrival procedure due to loss of concentration” and that thereafter, the First Officer had been “continuously prompting the Captain for decision making”. It was also noted that the First Officer was not fully familiar with the conversion of prevailing visibility to RVR and had calculated that the 1,200 metre visibility converted to an RVR of 1,800 metres when in fact the two were the same due to the high standard of approach lighting on runway 36L and that the Captain did correct this.
On checking in with Lahore APP, the controller noted that the aircraft was to the right of track and queried this. The CVR record disclosed that prior to the First Officer’s reply, the Captain had “quickly asked him to tell ATC that they were following the RNAV procedure for runway 36L”. The controller acknowledged this and instructed them to make a corresponding position report whilst continuing descent as cleared to FL 070. The Controller made no mention of her previous clearance for a VOR/DME approach to runway 36L. Thereafter, the prescribed RNAV procedure was followed but remained between 2,000 and 2,500 feet above the procedure vertical profile. To increase the rate of descent, Flaps-1, 2 and 5 were selected “in quick succession” but the speed brakes were not used. The APP controller asked if they intended to continue the approach or would discontinue it due to being high and the Captain “immediately prompted the First Officer to respond that they would continue” and the First Officer replied “affirmative, we can make it”. The First Officer proposed using the speedbrakes to regain the correct vertical profile and the CVR recorded his response in an exhausted voice which it was considered was an “indication that he was unable to cope with the difficult situation”.
As the aircraft reached an approach procedure waypoint located 9.7 nm from the runway 36L threshold, it was at 5,400ft with 180 KCAS and the radar controller, observing this, cautioned that they should have been at 3,000 feet and advised them to continue at their discretion, confirmed the missed approach procedure as climb in runway heading and instructed them to contact TWR. Immediately after this, the Captain disengaged the AP and increased the rate of descent to between 2,000 and 3,500 fpm which increased the speed beyond that for the now-deployed Flap 30. It was concluded that by this time “the approach had become unstabilised and warranted a go around”. The First Officer reset the Flight Directors in anticipation of a go round but the approach was continued. As the aircraft passed 4.6 nm from the runway threshold, it was at 1,200 feet agl with 170 KCAS but still without runway visual reference. It was found that, contrary to their request for and approval of an RNAV approach, the Captain was actually making a VOR/DME approach for which the required minimum visibility was not available. A landing clearance was given by TWR and acknowledged. Passing 460 feet agl, the runway was not in sight and the speed was 14 knots above Vref. The VOR/DME procedure MDA was 1,100 feet QNH, equivalent to an MDH of 388 feet. Then, just before the auto callout of “Minimums”, the First Officer sighted the runway towards the right of track, took over the controls and asked the Captain to inform ATC that runway was in sight. FDR data recorded that the aircraft temporarily levelled off in the vicinity of the MDA for approximately 7 seconds as a turn to the right was made. Descent with the First Officer as PF then continued with an erratic rate of descent until the Captain sighted the runway at approximately 150 feet aal and took over control from the First Officer but failed to properly align the aircraft with the runway centreline and as the auto callout of 100 feet occurred, the First Officer “forcibly took over the controls in order to land the aircraft” with the Captain reportedly unaware that he was still holding his control column despite repeated calls from the First Officer to desist.
The throttles were retarded to idle and touchdown occurred 1,400 feet past the threshold on the left half of the runway initially on the right main gear only with both pilots still holding the controls whilst the First Officer made the landing. After an earlier increase in thrust whilst the aircraft had briefly levelled after the First Officer had seen the runway and initially taken control, the recorded touchdown airspeed was 174 knots, 40 knots above the Vref. The speed brakes had been armed and were automatically deployed after which there was a bounce and left main gear touched hard followed by shimmy and the whole left main gear assembly braking off from the airframe. The thrust reversers were deployed and wheel braking commenced but due to the high drag generated by the rubbing of the left engine cowling on the runway surface, the right main gear also collapsed due to overload as the aircraft departed the runway onto soft ground. As this happened, the fuselage was left resting on both engines and nose gear which remained intact and continued to skid on the soft surface for approximately 2,450 metres before finally coming to a stop located 2,530 metres from the threshold and 60 metres from the centreline of the 46 metre-wide runway.
Once the aircraft had stopped, the Captain did not ask the First Officer to run the engine shutdown and passenger evacuation Checklists and this was done by the First Officer. Although the aircraft fuselage remained intact, it was damaged on the right side of the tail section where, fortuitously, the seats were not occupied. In addition to the detachment of both main landing gear assemblies, the wing structure adjacent to the main landing gear attachment points was extensively damaged as were both engines as a direct consequence of landing gear assembly detachment.
Blood samples were taken from both pilots after the accident and the results of those given by the Captain showed a blood alcohol level of 83 mg/dl compared to a threshold for impairment of the central nervous system of 50 mg/dl. It was concluded that this may have contributed to “judgmental errors as evident” and that the measured blood lactate level of 70 mg /dl could be interpreted as indicative of “fatigue due to increased stress” since the normal level is 4.5 - 23 mg/dl. There were no abnormal findings in the medical investigation report on the First Officer.
- EDITOR’S NOTE: At the time of this accident there were no prescribed limits for pilot blood alcohol level in Pakistan and no further reference was made to this finding by the Investigation.
No firm evidence was found that any prior lack of airworthiness had directly contributed to the excursion and the high speed landing itself was found to have created a loading on the left main gear assembly of “approximately its design limit level” with the right main gear then collapsing due to overload stresses resulting from the left main gear collapse as it too departed the runway. However, in the case of the left main gear, it was suspected that its collapse may have been the consequence of more than the specified limits of play in the linkages of shimmy damper mechanism which would have induced torsional vibrations in the assembly. These would have hastened the failure of the shimmy damper altogether and the resultant “torsional excitation” in the gear assembly due to free pivoting of the wheels along the vertical axis would then have caused its complete collapse. Although not proved to be contributory, the Operator’s Maintenance Schedule in respect of shimmy damper and linkages during ‘C’ Checks was found not to include requirements for enhanced frequency checks in the light of recommendations contained in an applicable Boeing Service Letter.
The Investigation formally recorded the Cause of the accident as follows:
- The flight crew landing the aircraft after an unstabilised approach (high ground speed and incorrect flight path).
- The low sink rate of the left main landing gear as it touched down and the probable presence of more than the specified limits of play in the linkages of the shimmy damper mechanism. This situation led to torsional vibrations / breakage of the shimmy damper after touchdown. The resultant torsional excitation experienced by the assembly due to free pivoting of the wheels along the vertical axis (then) caused the complete collapse of the left main landing gear.
- The right main landing gear then collapsed due to overload as the aircraft moved onto an unprepared surface.
Fifteen Safety Recommendations were made as follows:
- that Shaheen Air International should ensure implementation of Crew Reporting time as approved by the Flight Standards Directorate in the Shaheen Air International Operational Manual Part A (Edition II Ch-7 p.10 para 7.7.)
- that the Pakistan CAA should study and issue clear policy providing guidelines on delaying departure or rescheduling of flights in case of marginal weather at departing / destination aerodrome keeping in view the trend of weather deterioration or improvement.
- that the Pakistan CAA should issue necessary instructions to all operators in Pakistan to emphasise that their aircrew must read and understand NOTAMs in pre flight brief and utilise the information in NOTAMs in their flight planning.
- that All Aircraft Operators should encourage their aircrew to make in-flight decisions to divert to an alternate aerodrome in the event that the planned destination aerodrome weather falls below the minimum required.
- that the Pakistan CAA should ensure that Alcohol / Drugs spot checks of all aircrew operating in Pakistan are carried out as mentioned in PCAA ANO-002-XXAM-1.0, which was not being done regularly prior to this occurrence.
- that All Operators in Pakistan should advise their pilots to mutually brief in detail any alternative procedure, especially landing, which may have become essential during flight under specific circumstances.
- that the Pakistan CAA should carry out a study and issue necessary instructions regarding disengagement of autopilot for correcting of approach parameters. This aspect is to be viewed in conjunction with OEM recommended procedures and overall safety of aircraft.
- that the Pakistan CAA should issue necessary instructions to all operators to make their airline doctors / flight surgeons more effective. All sickness of aircrew must be reported to airline doctors / flight surgeons and proper record keeping is to be ensured in accordance with PCAA ANO-001-XXAM-2.0.
- that All Operators should ensure implementation of their Selection and Recruitment Policy, especially verification of licences and educational / experience certificates, which was not followed during the induction of the Captain of the investigated flight.
- that the Pakistan CAA should issue necessary instructions to all Boeing 737 operators in Pakistan to follow the landing technique given in Boeing Flight Crew Training Manual (FCTM), Chapter 6.
- that Shaheen Air International should ensure that the Captain and First Officer involved undergo CRM refresher training as lack of CRM in the entire sequence of events is evident.
- that Shaheen Air International should perform a one-time check of the “Torsion Links Apex Joint” and conduct a “Torsional Free Play Check” in accordance with the applicable Aircraft Maintenance Manual (AMM) (AMM) and perform necessary adjustment/rectification as required. (This recommendation was implemented by the operator during process of SIB investigation).
- that All Operators of Boeing 737-100 / 200 / 300 / 400 / 500 variants should conduct a review of Boeing Service Letter 737-SL-32-057E for implementation of the recommended enhanced frequency of maintenance on Shimmy Damper and associated linkages.
- that the Pakistan CAA should review its existing airworthiness procedures to ensure that all operators perform necessary technical reviews of non-mandatory manufacturer’s instructions/service letters and implement any required measures especially if they are intended to rectify problems in the area covered by the subject instructions/service letters.
- that All Boeing 737-400 flight crews should be briefed to adhere to Boeing-recommended procedures & landing technique to ensure effectiveness of shimmy damper mechanism.
The Final Report was published on 27 September 2017.