If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
Take Off Stall
|Category:||Loss of Control|
A stall which occurs immediately after an aircraft attempts to get airborne. When it occurs following rotation at or near the applicable Vr, it may be attributable to an unintended attempt to take off without the appropriate wing configuration set or because the necessary thrust has not been set.
Other possible origins of a take off stall are an attempt to get airborne with frozen deposits on the airframe, especially the wings - which is covered in the separate article "Aircraft Ground De/Anti-Icing", where an aircraft is not actually loaded in the manner described on the certified and accepted load and trim sheet, when an encounter with negative wind shear occurs or due to aircraft system malfunctions
Prevention and Recovery
The main means of preventing such occurrences is the effective use of Normal Checklists. The primary means of alerting pilots to an aircraft status, including but not limited to a wing configuration, which is not within the range approved for take off and stated in the aircraft AFM limitations, is the Take Off Warning System (TOWS), sometimes called the Take Off Configuration Warning System (TOCWS). This system often forms part of a wider system of crew alerting on modern aircraft but will always include an audible alert.
In some cases, it may be possible for a pilot to retain control of an aircraft which gets airborne with an incorrect configuration, but neither ground awareness nor simulator training for such a scenario is a regulatory requirement. Whilst the Stall Warning System is likely to be activated as soon as the aircraft is sensed as being in flight mode, the QRH memory drills applicable to recovery from an incipient stall are not immediately applicable to the circumstance where at least a modest rate of climb is likely to be required.
Relevant Regulatory Requirements
Aircraft design certification currently detailed under FAR 25.703 and EASA CS 25.703 is based upon the principles first brought into effect in FAA Part 25 on 1 March 1978 in AL25-42 and in JAR 25 on 1 January 1979 in AL5. Prior to these standards, there was no such requirement. The requirements were and remain the same and the background to their current version is described in FAA AC 25.703-1.
The key change from the initial specification, in which TOWS were acceptable if designed as single channel systems with only limited built in monitoring, was the 1993 recognition that the safety level of these systems should be increased so as to classify them as essential. This was achieved by requiring system design in accordance with FAA AC 25.1309-1A and its EASA counterpart, AMC 25.1309 because of a recognition that a inoperative TOWS should be regarded as having a severe effect on safety, TOWS activation on western built aircraft currently in service is thereby rarely false and can be generated only during the initial part of the take off roll. System design is also required to include immediate annunciation to the flight crew should a system failure be identified or if an interruption to necessary electrical power occurs.
The current certification requirement, which extends the provisions of paragraph 1309 to certification of TOWS under paragraph 703, covers the majority of aircraft types or has been voluntarily accepted in the case of some older types still in production based on type certificates which predate the more stringent design criteria. However, ‘grandfather rights’ still affect the TOWS design installed on some older aircraft, including most notably in terms of the world fleet size, the Douglas DC9 and MacDonnell Douglas MD series derivatives.
In operational terms, the original exclusion of TOWS from both FAA and JAR / EASA MMELs has been sustained so that release to service / despatch with the TOWS inoperative is not permitted. However, there is currently no universal regulatory requirement for a TOWS operational check to be carried out before every flight even though such a practice is quite common.
It should also be noted that in respect of the content of Crew Checklists, there is no requirement under EU OPS for them to be specifically approved, although the Operations Manual which contains checklists are subject to approval as a whole. The overall approval of an Operation will include an acceptance of the way checklists are used as well as focusing particular attention paid to any differences that exist between the ones used and the equivalent aircraft manufacturer’s standard versions. Under the FAA System, checklists must be approved under FAR 121.315and are expected to take available guidance material into account to obtain that approval, so that the effect is similar to the European approach.
According to the 1978 preamble to AL25-42 to the FAR which introduced TOWS, the system was originally introduced to serve as a “back up for the checklist, particularly in unusual situations, e.g. where the checklist is interrupted or the takeoff delayed”. In many documented investigations of accidents and serious incidents relating to take off stall, the TOWS has, for various reasons, been inoperative at the same time as crew discipline in relation to checklists has been poor.
In many instances, the actual crew response to a stall protection system activation at Vr has been to add thrust rather than reject the take off. Since Vr can never be less than V1 for Performance ‘A’ aeroplanes and is almost always quite a lot higher, this “instinctive” response is one which needs to be at least discussed during training. This response is of particular concern given that in almost all documented cases, the Stall Protection System has generated a warning as soon as the aircraft has sensed flight mode, which can be sensed from the nose landing gear raised at rotation.
Normal checklists used with sufficient discipline and in accordance with effective SOPs can ensure that pilots remain appropriately focussed on their prioritised tasks by removing the risks associated with divided attention and with any effects arising from stress, whether of self-generated or external origin, or fatigue. Most checklists are read from a hard copy or a screen and require a specific response from either PF or the PM but on screen checklists with an aural readout based on manual sequencing by the PM do exist.
Take-off stall events attributed to attempts to take off without setting the flaps / slats to an approved take off position invariably involve the omission of the checklist item(s) relating to that action, usually due to the interruption of a checklist prior to its completion. This problem has been partially attributed to a general absence of effective CRM and flight crew discipline but has also been indirectly related to variation in the SOP for the selection of take off flap depending on the earliest and latest times they should be selected in relation to push back and/or taxi out towards the runway. An additional complication may exist in respect of any on-stand or remotely-sited ground de/anti-icing, which may require a delay in wing configuration compared to normal procedures. This may justify an additional checklist to follow completion of such a de/anti-icing treatment or rely on the subsequent pre take off checklist.
All on-screen checklists have the advantage that any deferred items can be highlighted which, given the variable SOPs for deployment and checking of flaps/slats sometime between the completion of engine start and arrival at the departure runway, has proved extremely useful.
Effective CRM is obviously a major factor in the effective use of Check Lists.
Stall Awareness Training
In the absence of any regulatory requirement, most operators limit any attention given to crew awareness of this issue to ground school and consider that the primary focus should be on avoiding the situation by creating the right attitude to SOP compliance.
Relevant Precursor Events detectable by suitably configured OFDM programmes include the absence of a prescribed pre fight test of the TOWS system, all recorded activations of the TOWS system and any change to flap settings when a departing aircraft is lined up on the take off runway. In the absence of OFDM data, a suitable safety culture may facilitate the raising of ASRs after instances of late configuration which can contain - or allow the gathering of - useful information about how lapses in the application of SOP have arisen
Relevant Precursor Observations may include LOSA observations relating to pre flight checking of the TOWS system and use of checklists and especially with respect to deferred or temporarily overlooked items. They may also be available from recurrent training records if relevant trends in respect of checklist use and standards of crew cooperation are available and appropriately collated. Any unserviceability of TOWS systems should also be tracked to ensure that functional reliability is high and recognised by flight crew as such.
Accident and Serious Incident Examples
Over a long period, a number of fatal accidents and ‘near misses’ involving take off stall have occurred. They have included the following:
- DH8A, en-route SSE of Madang, Papua New Guinea, 2011 (On 13 October 2011, the Captain of a Bombardier DHC8-100 manually flying a low power, steep descent in an attempt to get below cloud to be able to see the destination aerodrome inadvertently allowed the speed to increase sufficiently to trigger an overspeed warning. In response, the power levers were rapidly retarded and both propellers entered the ground range and oversped. As a result, one engine was damaged beyond use and the other could not be unfeathered. A forced landing was made following which the aircraft caught fire. All three crew members but only one of the 29 passengers survived.)
- MD82, Detroit MI USA, 1987 (On 16 August 1987, an MD-82 being operated by Northwest Airlines on a scheduled passenger flight from Detroit MI to Phoenix AZ failed to get properly airborne in day VMC and, after damaging impact with obstacles within the airport perimeter after climbing to a maximum height of just under 40 ft, impacted the ground causing the destruction of the aircraft by impact forces and a subsequent fire. All but one of the 157 occupants were killed with the single survivor suffering serious injury. On the ground, 2 people were killed, 2 more seriously injured and 4 more suffered minor injury with several buildings vehicles and structures damaged or destroyed.)
- MD82, Madrid Barajas Spain, 2008 (On 20 August 2008, an MD82 aircraft operated by Spanair took off from Madrid Barajas Airport with flaps and slats retracted; the incorrect configuration resulted in loss of control, collision with the ground, and the destruction of the aircraft.)
- MD83, Lanzarote Spain, 2007 (On 5 June 2007, a McDonnell Douglas MD83 being flown by Austrian charter operator MAP on a flight from Lanzarote to Barcelona failed to follow a normal trajectory after take off in day VMC and developed violent roll oscillations. As speed increased, this stopped and a return to land was made without further event. Takeoff from Lanzarote had been unintentionally made without the flaps/slats being set to the required position.)
- A333, Chicago O'Hare IL USA, 2013 (On 5 March 2013, the aft-stationed cabin crew of an Airbus A330-300 being operated by Lufthansa on a scheduled international passenger flight from Chicago O'Hare to Munich advised the flight crew after the night normal visibility take-off that they had heard "an unusual noise" during take-off. Noting that nothing unusual had been heard in the flight deck and that there were no indications of any abnormal system status, the Captain decided, after consulting Company maintenance, that the flight should be completed as planned. The flight proceeded uneventfully but on arrival in Munich, it became clear that the aircraft had sustained "substantial damage" due to a tail strike on take-off and was unfit for flight.)
- CRJ9, San Sebastian Spain, 2013 (On 25 October 2013, the crew of a Bombardier CRJ 900 made an unstable visual daytime approach to San Sebastian which culminated in a hard landing of sufficient severity to trigger an inspection in accordance with the AMM. The inspection did not occur and the aircraft made a further revenue flight before the hard landing was reported and substantial landing gear damage was discovered. The unstable approach at a Category 'C' airport was found to have been flown by the First Officer contrary to applicable regulatory requirements.)
- B733, vicinity Montpelier, France 2011 (On 10 January 2011, a Europe Airpost Boeing 737-300 taking off from Montpelier after repainting had just rotated for take off when the leading edge slats extended from the Intermediate position to the Fully Extended position and the left stick shaker was activated as a consequence of the reduced stalling angle of attack. Initial climb was sustained and soon afterwards, the slats returned to their previous position and the stick shaker activation stopped. The unexpected configuration change was attributed to paint contamination of the left angle of attack sensor, the context for which was inadequate task guidance.)
- B732, Medan Indonesia, 2005 (On 5 September 2005, a Boeing 737-200 being operated by Mandala Airlines on a scheduled domestic passenger flight from Medan, Indonesia to Jakarta failed to become properly airborne during the attempted take off from from runway 23 in day VMC and, after failing to remain airborne, overran the end of the runway at speed finally coming to a stop outside the airport perimeter. The aircraft was destroyed by impact forces and a subsequent fire and 100 of the 117 occupants were killed and 15 seriously injured. The aircraft collided with residential property, vehicles and various other obstructions and as a result a further 49 people on the ground were killed and a further 26 seriously injured.)
- E190, Amsterdam Netherlands, 2014 (On 1 October 2014, an Embraer 190 made a very hard landing at Amsterdam after the flight crew failed to recognise that the aircraft had not been configured correctly for the intended automatic landing off the Cat 1 ILS approach being flown. They were slow to respond when no automatic flare occurred. The Investigation was unable to fully review why the configuration error had occurred or why it had not been subsequently detected but the recent type conversion of both the pilots involved was noted.)
- CRJ2, en-route, east of Barcelona Spain, 2006 (On 27 July 2006, a Bombardier CRJ200 being operated by Air Nostrum on a scheduled passenger flight from Barcelona to Basel, Switzerland in night VMC, suffered a sudden left hand engine failure and an associated engine fire when passing FL235 some 14 minutes after take off. An air turn back was made with indications of engine fire continuing until just three minutes before landing. An evacuation using the right hand exits was ordered by the Captain as soon as the aircraft had come to a stop and had been promptly actioned with the RFFS in attendance. There were no injuries to the 48 occupants during the evacuation and the only damage was to the affected engine.)
- BE20, vicinity Stapleford UK, 2015 (On 3 October 2015, the pilot of a Beech Super King Air on a business flight lost control in IMC shortly after take-off and the aircraft subsequently impacted terrain at high speed. The Investigation concluded on the balance of probabilities that pilot medical incapacitation was likely to have occurred. It was noted that the aircraft had not been fitted with TAWS nor was it required to be but it was found that alerting from such a system would have increased the chances of the only passenger, another professional pilot, successfully taking over and three corresponding Safety Recommendations were made.)
- A321, vicinity Singapore, 2010 (On 27 May 2010 an Airbus A321-200 being operated by Australian operator JetStar on a passenger flight from Darwin to Singapore continued an initial approach at destination in day VMC with the aircraft inappropriately configured before a late go around was commenced which was also flown in a configuration contrary to prescribed SOPs. A subsequent second approach proceeded to an uneventful landing. There were no unusual or sudden manoeuvres during the event and no injuries to the occupants.)
- FAA AC 25-22 (2000) "Certification of Transport Airplane Mechanical Systems" includes the current rule text and a summary of some aspects of the AMC guidance provided in AC 25.703-1, the current version of TOWS design requirements, on pps 8-9.
- FAA AC 25.703-1 "Take Off Configuration Warning Systems (1993)" provides AMC guidance material.
- Airbus FOBN on Takeoff and Departure Operations: "Response to Stall Warning Activation at Takeoff"
- NASA Ames Research Center: "Human Factors of Flight-Deck Checklists: The Normal Checklist" - Degani & Wiener (1990)
- Aircraft Loss-of-Control Accident Analysis, C. Belcastro and J. Foster, NASA, 2010.