If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
Pilot Handling Skills
From SKYbrary Wiki
Pilot handling skills can be equated to manual flying skills.
Manual Flying Skills are typically thought of as pure core flying skills, where manoeuvres are flown solely by reference to raw data obtained from the heading, airspeed, attitude, altitude and vertical speed instruments, and without the use of technology such as auto-throttles, auto-pilot, flight director or any other flight management system. This might extend as far as requiring manual trim inputs and navigation using basic systems.
Pilot Handling Skills will include all the above manual flying skills, but may also relate to combinations of manual flying, speed and directional control together with combinations of automatic speed and direction control and guidance. Such combinations may occur through pilot preference, operational or procedural requirements, or when some automated systems are no longer functioning.
Whereas commercial airline pilots may once have been assessed wholly on their manual flying (aircraft handling) skills, nowadays pilot assessment is predominantly based on Systems and Crew Management, where management of the automated systems and maintenance of situational awareness replace many of the traditional flying skills.
Pilots require handling skills in a variety of situations including:
- Visual approaches
- Circling approaches
- Instrument approaches (some precision and all non-precision)
- Missed Approach
- Reaction to ACAS/TAWS
- Recovery from unusual aircraft attitudes
- Rejected take-offs
- All phases of flight where aircraft flight control, management and navigation systems malfunctions dictate
There are many arguments suggesting that commercial airline pilot handling (flying) skills have become eroded since the growth in popularity of fly-by-wire, glass-cockpit, fully automated, system-designed aircraft. One could add to this the routine nature of many flight operations, the growth in controlled airspace and widespread availability of Instrument Landing Systems (ILS). Pilots flying with commercial airlines will typically only fly manually for the first and last few minutes of each flight. If a pilot logs 900 hours in a single year, fewer than 5 hours may involve manual flying. Also, more and more pilots flying today have never experienced an Industry where flying manually was, or is, the norm, unlike older pilots where these skills became “hard-wired”. This can further dilute the overall levels of pilot handling skills within an airline.
The majority of fatal, and non-fatal accidents, continue to occur during landing and go-around phases of flight, and loss of control (in-flight) continues to be the predominant category of fatal accidents. Other areas of safety concern, for the Industry, include unstabilised approaches, runway excursions, heavy landings, tail-scrapes, level-busts, and engine and airframe exceedance of parameters. Each of these phases of flight and accident categories (above) would appear to involve pilot handling skills. Whilst it would be wrong to identify lack of manual flying skills as the cause to all of these, especially where loss of situational awareness, system malfunction, environmental factors and poor Crew Resource Management (CRM) were involved, it nonetheless does indicate that effectively applied pilot handling skills may help prevent accidents and reduce the consequences of errors.
Therefore, any arguments suggesting that commercial airline pilot handling (flying) skills have become eroded should be examined seriously.
The increased sophistication and use of automation has improved safety by reducing the workload on pilots, allowing them greater capacity and time to make forward judgements and decisions as well as “manage” better the aircraft systems and crew. Pilots learn to fly (i.e. their core manual flying skills) by correcting aircraft flight parameters based on their predictions to a projected forward goal – i.e. straight and level flight, or touchdown. However, with multiple levels of automation and flight modes it is very difficult for pilots to predict what the consequences of various failures will be in every given situation. Part of the necessary response to automation failures is to apply manual flying (handling) skills. Increased reliance on automation by flight crews has created a risk that crewmembers may no longer have the skills required to react appropriately to either failures in automation. Therefore, operators should ensure that training programmes include means and standards to be met regarding the interaction of human performance and limitations with changes to the normal operation of the automation.
Training and Practice
Basic flying training is predominantly focused on manual handling and becoming proficient in core flying skills. By the time a pilot completes professional training the emphasis is on system and crew management. During a pilot’s professional career as a commercial airline pilot he/she will be required to demonstrate regularly proficiency in certain handling skills, and under certain conditions, i.e. conducting a safe take-off with the loss of one engine, or, flying an ILS approach to go-around at decision height, also with one engine inoperative.
It is important for airlines to monitor the skill levels of pilot handling, perhaps through flight data monitoring programmes and line flying and simulator observations; then to use this feedback to adjust training syllabi. It is also important for airlines to integrate automation use and degradation into training to reflect operational conditions involving manual handling skills – automation not just a theoretical subject.
It may be necessary to provide pilots with additional flight simulator training specifically aimed at addressing pilot handling skills deficiencies.
Accidents & Incidents
Events in the SKYbrary database which include Manual Handling as a contributory factor:
- A109, vicinity London Heliport London UK, 2013 (On 16 January 2013, an Augusta 109E helicopter positioning by day on an implied (due to adverse weather conditions) SVFR clearance collided with a crane attached to a tall building under construction. It and associated debris fell to street level and the pilot and a pedestrian were killed and several others on the ground injured. It was concluded that the pilot had not seen the crane or seen it too late to avoid whilst flying by visual reference in conditions which had become increasingly challenging. The Investigation recommended improvements in the regulatory context in which the accident had occurred.)
- A140, vicinity Tehran Mehrabad Iran, 2014 (On 10 August 2014, one of the engines of an Antonov 140-100 departing Tehran Mehrabad ran down after V1 and prior to rotation. The takeoff was continued but the crew were unable to keep control and the aircraft stalled and crashed into terrain near the airport. The Investigation found that a faulty engine control unit had temporarily malfunctioned and that having taken off with an inappropriate flap setting, the crew had attempted an initial climb with a heavy aircraft without the failed engine propeller initially being feathered, with the gear remaining down and with the airspeed below V2.)
- A306, East Midlands UK, 2011 (On 10 January 2011, an Air Atlanta Icelandic Airbus A300-600 on a scheduled cargo flight made a bounced touchdown at East Midlands and then attempted a go around involving retraction of the thrust reversers after selection out and before they had fully deployed. This prevented one engine from spooling up and, after a tail strike during rotation, the single engine go around was conducted with considerable difficulty at a climb rate only acceptable because of a lack of terrain challenges along the climb out track.)
- A306, Yerevan Armenia, 2015 (On 17 May 2015, an Airbus A300-600 crew descended their aircraft below the correct vertical profile on a visual daytime approach at Yerevan and then landed on a closed section of the runway near the displaced runway threshold. The Investigation found that the crew had failed to review relevant AIS information prior to departing from Tehran and had not been expecting anything but a normal approach and landing. The performance of the Dispatcher in respect of briefing and the First Officer in respect of failure to adequately monitor the Captain's flawed conduct of the approach was highlighted.)
- A306, vicinity Nagoya Japan, 1994 (On 26 April 1994, the crew of an Airbus A300-600 lost control of their aircraft on final approach to Nagoya and the aircraft crashed within the airport perimeter. The Investigation found that an inadvertent mode selection error had triggered control difficulties which had been ultimately founded on an apparent lack understanding by both pilots of the full nature of the interaction between the systems controlling thrust and pitch on the aircraft type which were not typical of most other contemporary types. It was also concluded that the Captain's delay in taking control from the First Officer had exacerbated the situation.)
- A306, vicinity New York JFK, 2001 (On 12 November 2001, an Airbus A300-600 encountered mild wake turbulence as it climbed after departing New York JFK to which the First Officer responded with a series of unnecessary and excessive control inputs involving cyclic full-deflection rudder pedal inputs. Within less than 7 seconds, these caused detachment of the vertical stabiliser from the aircraft resulting in loss of control and ground impact with a post crash fire. The Investigation concluded that elements of the company pilot training process and the design of the A300-600 rudder system had contributed to this excessive use of the rudder and its consequences.)
- A30B, en-route, Bristol UK, 2000 (On 27 June 2000 an Airbus A300-600 being operated by American Airlines on a scheduled passenger service from London Heathrow to New York JFK was being flown manually in the day VMC climb and approaching FL220 when a loud bang was heard and there was a simultaneous abrupt disturbance to the flight path. The event appeared to the flight crew to have been a disturbance in yaw with no obvious concurrent lateral motion. Although following the disturbance, the aircraft appeared to behave normally, the aircraft commander decided to return to London Heathrow rather than commence a transatlantic flight following what was suspected to have been an un-commanded flight control input. An uneventful return was made followed by an overweight landing 50 minutes after take off.)
- A310, Irkutsk Russia, 2006 (On 8 July 2006, S7 Airlines A310 overran the runway on landing at Irkutsk at high speed and was destroyed after the Captain mismanaged the thrust levers whilst attempting to apply reverse only on one engine because the flight was being conducted with one reverser inoperative. The Investigation noted that the aircraft had been despatched on the accident flight with the left engine thrust reverser de-activated as permitted under the MEL but also that the previous two flights had been carried out with a deactivated right engine thrust reverser.)
- A310, Khartoum Sudan, 2008 (On 10 June 2008, a Sudan Airways Airbus A310 made a late night touchdown at Khartoum and the actions of the experienced crew were subsequently unable to stop the aircraft, which was in service with one thrust reverser inoperative and locked out, on the wet runway. The aircraft stopped essentially intact some 215 metres beyond the runway end after overrunning on smooth ground but a fuel-fed fire then took hold which impeded evacuation and eventually destroyed the aircraft.)
- A310, Ponta Delgada Azores Portugal, 2013 (On 2 March 2013, the crew of an Airbus A310 mishandled a night tailwind touchdown at Ponta Delgada after a stabilised ILS approach had been flown and, after an initial bounce, the pitch was increased significantly and the main landing gear was fully compressed during the subsequent touchdown resulting in a tail strike and substantial related structural damage. The mishandling was attributed to deviation from the recommended 'light bounce' recovery technique. The absence of an instrument approach to the reciprocal (into wind) direction of the runway was noted and a recommendation that an RNAV procedure be made available was made.)
- A310, vicinity Abidjan Ivory Coast, 2000 (On 30 January 2000, an Airbus 310 took off from Abidjan (Ivory Coast) at night bound for Lagos, Nigeria then Nairobi, Kenya. Thirty-three seconds after take-off, the airplane crashed into the Atlantic Ocean, 1.5 nautical miles south of the runway at Abidjan Airport. 169 persons died and 10 were injured in the accident.)
- A310, vicinity Moroni Comoros, 2009 (On 29 June 2009, an Airbus A310-300 making a dark-night visual circling approach to Moroni crashed into the sea and was destroyed. The Investigation found that the final impact had occurred with the aircraft stalled and in the absence of appropriate prior recovery actions and that this had been immediately preceded by two separate GWPS 'PULL UP' events. It was concluded that the attempted circling procedure had been highly unstable with the crew's inappropriate actions and inactions probably attributable to their becoming progressively overwhelmed by successive warnings and alerts caused by their poor management of the aircraft's flight path.)
- Automatic Flight - A Guide for Controllers
- Flight Control Laws
- Flying a Manual Go-around
- Go-around Execution
- Line Oriented Flight Training
- Recovery from Unusual Aircraft Attitudes
- Aircraft Loss of Control: Causal Factors and Mitigation Challenges, by S. R. Jacobson, NASA, 2010
- LOC-I Prevention: Beyond the Control of Pilots, IATA, 1st Edition, 2015
- ^ a b Flight Safety Foundation Increased Reliance on Automation May Weaken Pilots’ Skills for Managing System Failures.
- ^ Boeing Statistical Summary of Commercial Jet Airplane Accidents 1959 – 2012
- ^ EASA Annual Safety Review 2012
- ^ Airbus Flight Operations Briefing Note: Preventing Tailstrike at Landing.
- ^ Airbus Flight Operations briefing Note: Preventing Tailstrike at Takeoff.
- ^ A332, en-route, Atlantic Ocean, 2009
- ^ EASA Automation Policy: Bridging Design and Training Principles. Version of 14 January 2013.