Showing posts with label CRM. Show all posts
Showing posts with label CRM. Show all posts

Saturday, March 27, 2021

Military and Commercial Aviation - A View, Mine!

The last paragraph of an article that I have read so beautifully described everything that I too wish to state, based on my limited experience in commercial aviation, as also based solely on my perceptions. The paragraph is reproduced below.

At last I understood what true professionalism is. Being a pilot isn't all seat-of-the-pants flying and glory. It's self- discipline, practice, study, analysis and preparation. It's precision. If you can't keep the gauges where you want them with everything free and easy, how can you keep them there when everything goes wrong.

As a pilot with the IAF, I always considered the commercial licensed pilots as lesser mortals, who got the best of things, while we had to make do with what we had, even though, I felt that our job was more demanding. An example...

May 1984, Op Meghdoot, we were the 1st fighter sqn to land in Leh. We were put up, 2 to a room, with no running water in the bathroom, and with water stored in an empty tar drum outside the rooms & night temperatures of -6*C. We had a kerosene bukhari in the room but there was no legal supply of kerosene, as the supply was only authorised until 31 March. We were given 2 metal buckets to fill our washing needs from the tar drum outside, which was replenished twice a day by a bowser. Electricity was from a captive generator, if I remember right. We used to fill our bucket with water at night, and insert our bazooka (a wooden stick with a heater coil wrapped around it) in it at night, as the water would freeze at night. Get up in the morning, put the bazooka switch on & do all the ablutions/bathing with that 1 bucket. Life was good, we flew in the valleys, helicopter trip to Siachen glacier, with halts at Siala & Bilafondla, & being served warm orange juice laced with rum by our faujis on the glacier, at 17000'/ -55*C. However, we still envied the 5-star treatment of our commercial counterparts.

2006, I get my CPL and start my commercial flying with Blue Dart. I am sent to Johannesburg for my sim; boarding/ lodging in a 5-star resort & all travel plans, ticketing, etc done by the operations department. I feel like a son-in-law of the company. 3 weeks of ground school, and the sim session starts thereafter. I find that the instructor is being too fussy about the procedural aspects. Having 3200 hours on different types of aircraft as a pilot with the Air Force gives one an attitude of 'seen that, done that'. Finally clear the sim. Now the company wants me to fly some hours on the jump seat, followed by a few hours with a qualified co-pilot on the jump seat, while I fly as the u/t co-pilot. Finally, I get ‘released’ as a co-pilot. All I am initially permitted to do is walk around (external checks), checklist, get weather on ATIS, calculate speeds, set the speeds, R/T calls, and callout clear while taxiing, speeds on take-off, heights, checks & complete the navigation log. This seemed like pretty boring & mundane stuff for someone who had handled fast jets in varied terrains, heights & speeds in many different roles/ exercises, all demanding high levels of skill.

At Blue Dart, we operated only by night. As I commenced my line flying, I realised that there were no supervisors to brief/ see us off; a dispatcher would give us the weather, flight plan, fuel and communications briefing, handover two bags full of documents; the Captain was at liberty to ask for additional fuel, if he desired, depending on weather or congestion at destination. At the aircraft, the AME would be available for any queries. For any issues with the aircraft the Captain was required to consult the book on ‘go/ no go’ criteria. In short, it was the Captain who was required to take all decisions, and this becomes even more stark once the door is locked from inside; the Captain becomes wholly responsible for the duration of the flight of this living habitat, which has every possible thing that a mini township has; people, electricity, plumbing, galley, communications, sewerage, fire & safety systems, etc, in addition to the aircraft systems of hydraulics, engines, pneumatics, air conditioning, etc. In the ground classes you learn about regulations, weather, R/T, navigation, log keeping, CRM, technical, FDTL, etc. During the school, one aims to pass the exam, not realising that this is the only data that would be of help to take professional decisions, as there is no help available once the door is locked; it is just you, your crew, and your licence. This is much unlike the Air Force where the whole organisation is organised to provide backup to the launch, execution, and recovery of every sortie. Here there are multiple organisations; each with a professional, a licensed person, providing services, as per their licence, be it the flight crew, Met, ATC, AME, etc.

I started to fly in June; the monsoons had started to set in. Landing in to Mumbai at around midnight, with the aircraft wipers going at max speed, and the turbulence over the ghats never deterred the Captain to continue on the auto pilot coupled ILS, with me calling out the speeds and with nothing visible in front except blasts of rain hitting violently against the windshield. We flew the B-737-200, where-in the autopilot was cleared only upto and above 500’. The localiser and glide slope needles are stuck, right angles to each other. I callout 500’ – Captain disconnects autopilot and holds the needles at right angles while continuing with the approach to land. On my call ‘minimums’, he would call landing, if he had the visual cues to land, which are specified in the regulations, or plan a missed approach, briefing for which was already done prior to commencement of descent. Every flight was a steep learning experience for me; in spite of my 3200 hours of flying experience, there were many things that were new to me. Many a night we flew through a wall of towering Cbs, with lightening all around; the weather radar would help us find a gap, ATC would clear our detours, & we would squeeze through the gap. Latest weather at destination, weather at most likely diversions, as the route progressed were sought, fuel consumption/ fuel remaining were closely monitored. Flying to the absolute limits was the norm with balanced field length RTOW, V-speed calculations, before every flight.

I remember one night; I had a Captain who was in his mid-twenties, on a four leg flight from Chennai to Delhi, via Hyderabad, Mumbai, & Ahmedabad. We were rolling for take-off at about midnight, with full load; I had called 100 kts, and was in the process of calling out V1, when there was a loud bang on the windscreen and a burning smell in the cockpit. All I heard from the Captain was ‘Continuing’. We rotated, checked engine parameters, all was normal, and he decided to continue to Mumbai. Got the engine checked at Mumbai, and found no damage, as the bird had most likely gone through the fan stage, as generally happens. This incident highlighted the quick decision making required at that stage of flight, a delay of 1” to abort at that stage could have the aircraft about 220 yds in the overrun area, if I remember my calculations right, after about 14 years now.

Considering my experience, I had thought I would be ready to sit on the left seat after completing 100 hours as co-pilot, as required by the company Operations Manual. I did not feel competent to even ask my Chief Pilot for the same, on completion of the regulatory 100 hours in the right seat. The variables, monsoons, the total responsibility was all new and a bit disconcerting. Flying from 9 pm to about 8 am taught one the practical lessons on fatigue, window of Circadian low, and importance of following the FDTL, in letter and spirit. 5-star stays no longer looked like comfort, but a basic need to be able to perform in an environment highly dependent on good decision making by the crew, with minimal oversight from anyone else in the organisation; backups of SFS, Flt Cdr, Sqn Cdr, COO, ATC, Met, SUs, etc are not the norm. It is you and your licence. An example….

Our company bought an aircraft from China. A crew was detailed to go and fly it in. The Captain went up to the CEO and told him to change the crew, as both crew members had never been to China before. The CEO replied that no one in the company had been there, & so there was limited choice. Besides, he said that you have an ATPL, & you are well qualified to undertake this task. Matter ended. The crew brought the aircraft from China.

Having operated as a co-pilot only, in commercial aviation, I am sure there are better qualified commercial pilots in this group to comment on what I am going to say. My experience of about one year in commercial aviation taught me that as the name suggests commercial aviation is all about making money and is basically geared for that in terms of organisation. Being a public service, it is highly regulated and has licenced nearly every critical component that makes up civil aviation. Each person is a professional in his own field, and so are the flight crew. The Captain carries the can for each flight and for every decision made. Others assist him within the ambit of their licence; decision making rests solely with the Captain, with minimal supervisory oversight. The IAF on the other hand is a national asset; the whole nation pays for its upkeep, & also depends on it to provide national security. The Air Force organisation stands solidly behind every sortie that gets airborne; there are supervisory oversights at every stage, in peace. Risk is inherent, and is accepted as part of mission accomplishment. In commercial aviation, safety is paramount, and understandably so. In IAF, skills are paramount; commercial aviation is more procedural, not that skills are not important. Both have their strengths and are equally demanding in their respective ways. It took me an exposure to commercial aviation to understand this simple fact, which used to sometimes come up in our crew room conversations.

After having taught CRM and human factors, I can safely say that one’s reality is based on one’s perception, which is totally dependent on one’s ‘experiences’ & ‘learning’ in life. Looking at the same facts, two individuals will perceive the same situation differently because of the above. I am now convinced that each has a role and has created an organisation/ structure/ systems/ procedures to meet that role. Both are right and have their strengths. One is not better or worse. Commercial aviation has gained tremendously with the inflow of Air Force pilots in terms of developing good training ethos, teamwork, leadership – the strong points of the IAF. I am convinced that the Hudson river ditching was perfect, largely because Captain Sully was an ex-USAF pilot. His actions, communications, & decision making were exemplary, as were his skills, and after ditching, so was his concern for each of his crew and passengers. The IAF would gain equally if they interact more with the civil aviation in terms of procedures, rules, etc. The two are vital components of a nation’s airpower and would both benefit with closer interaction that will eventually lead to a healthy transfer of their inherent strengths.

Friday, May 6, 2016

SHUTTING DOWN THE ‘GOOD’ (WRONG) ENGINE


BRITISH MIDLANDS FLIGHT 092: 08 JAN 1989: BOEING 737 – 400


SYNOPSIS

Flight 092 left London for Belfast at 19:52h with a crew of 8, and 118 passengers on board. While climbing through FL283 moderate to severe vibration that was accompanied by ingress of smoke and fumes in to the flight deck were felt, as also fluctuations in the engine parameters of the No. 1 engine. Investigations revealed that these were the result of one of the outer panel of one of the no. 1 engine fan blades getting detached in flight, causing a series of compressor stalls that lead to airframe shuddering.

Believing the No. 2 engine had suffered damage, the crew throttled it back. The shuddering stopped, leading the flight crew to believe that their actions were correct, and they thus shut down the No 2 engine. The No. 1 engine operated normally after the initial severe vibrations, and during the descent in to East Midlands, the diversionary airfield.

The flight was cleared for an approach on to runway 27. The instrument approach on No. 1 engine continued normally, although with a high level of vibrations from the live engine. At 900 feet, 2.4nm from the runway, no. 1 engine suddenly suffered a reduction in power followed by a fire warning on this engine. Attempts to restart No. 2 engine were not successful. As the speed fell below 125 knots, the stick shaker activated and the aircraft struck trees at a speed of 115 knots. The aircraft continued and impacted the western carriageway of the M1 motorway 10 m lower and came to rest against the wooded embankment, 900 m short of the runway.

39 passengers died in the accident, and 8 more died later due to the injuries sustained. Of the remaining 79 occupants, 74 suffered serious injuries.

(Image Courtesy: Google Images: Aerial view of Crash site)


PROBABLE CAUSE

The operating crew shut down the No 2 engine after a fan blade had fractured in the No 1 engine. This engine subsequently suffered a major thrust loss due to secondary fan damage after power had been increased during the final approach to land.

The following factors contributed to the incorrect response of the flight crew

1. The combination of heavy engine vibration, noise, shuddering and an associated smell of fire were outside their training and experience.

2. They reacted to the initial engine problem prematurely and in a way that was contrary to their training. (Either pilot does not remember having noticed the engine parameters like N1, EGT, N2 or Oil Pressures of the engines before throttling back No. 2 engine).

3. They did not assimilate the indications on the engine instrument display before they throttled back the No. 2 engine. (The crew’s familiarity of the newly introduced EIS on the B 737-400 variant could have been a factor. The Captain had 23 hours and the first officer had 53 hours on the B 737-400. Both were given a 1day training session on the EIS, as there was no flight simulator available with the EIS. The variants before the B737-400 had the normal electro-mechanical engine instruments).

4. As the No 2 engine was throttled back, the noise and shuddering associated with the surging of the No 1 engine ceased, persuading them that they had correctly identified the defective engine. (The Auto Throttle system was disengaged while bringing No. 2 engine throttle back to idling. This led to manual control of the engines, and No. 1 engine fuel flow settled as per the prevailing engine conditions, rather than as demanded by the auto throttle to maintain flight parameters).


5. They were not informed of the flames which had emanated from the No.1 engine and which had been observed by many on board, including 3 cabin attendants in the aft cabin. (Inadequate communications between flight and cabin crew – a CRM issue that is greatly emphasised now).

Wednesday, June 26, 2013

STANDARD OPERATING PROCEDURES AND SAFE OPERATIONS

Introduction      What are Standard Operating Procedures (SOPs)? A letter by the US Federal Aviation Administration (FAA) aptly answered this question where in it was stated that, “SOPs are written, tested procedures that are applied uniformly and consistently within an organization and involve all aspects of flight, both normal and non-normal”. It further stated that “SOPs are widely recognized as a basic element of safe aviation operations”. Safety is one of the pre-requisites for mission accomplishment in aviation, and thus the importance of SOPs can never be under estimated.

Design of SOPs

The aircraft manufacturer provides the initial SOPs for the aircraft based on lessons learned from previous operating experience; analyses performed during design; experience gained during development and certification flight testing; and also experience from the route-proving program. These manufacturer-provided SOPs are adopted without change by an aviation organisation, or these are used as the basis for the development of customized SOPs that promote standardisation across the different aircraft fleets in service at the organisation. Company SOPs so developed reflect the organisation’s operating and training philosophies. Thus, SOPs represent the collective wisdom of the aviation community on how operations could be conducted safely.

To ensure safety, training and operations need to be consistent, implying that training and operations should both be conducted as per the SOPs. This can only happen if everyone in the organisation is convinced of the need to follow SOPs. Bringing about this awareness places a great responsibility on the flying supervisory staff.  Instructors and check airman of the operator are required to ensure that crews are made aware of the reasons for SOPs; are trained as per the SOPs, and are also required to enforce the same during routine line operations.

SOPs published by the operator normally include expected procedures that would be utilised during the flight profiles that are used by the operator, including pre & post flight procedures. SOPs lay down the most effective and efficient procedure to execute any task safely. New procedures need to be added to the SOPs, and redundant ones modified/ deleted based on requirements, and also based on experiences gained by the aviation community. To undertake this task, review of SOPs should be an ongoing task, ideally accomplished with suitable feedback from the end user, the flight crew.

All of this is done with an aim of ensuring safe aviation operations. It is now abundantly clear that safety is not dependant only on the training of the crew, but also on good crew coordination as well as optimum crew performance (or good CRM). This can best be ensured if the crew has a shared mental model of each task that is being undertaken. SOPs provide that vital link that can effectively ensure this shared mental model between crew members, with the least communications, because when every crew member is following SOPs, he/ she is aware of what needs to be done; when it needs to be done; and by whom.

To ensure that every crew member follows the SOPs, these procedures should be clear, comprehensive, and readily available to the flight crew members. In addition the crew members should be aware and convinced of the need to follow the SOPs. All this sounds logical but a study of aircraft incidents and accidents indicates that some of these have been caused due to the crew not following the SOPs.

Operational and Human Factors Involved in Deviations from SOPs

To ensure effective compliance with SOPs, it is important to understand why pilots intentionally or inadvertently deviate from the SOPs. In most cases of deviation from SOPs, the procedure that was followed in place of the published procedure seemed appropriate to the crew, for the prevailing situation, considering the information available in the cockpit at the time. However, it was later found that it was either inappropriate, or at best suboptimal. Experts cite the following factors and conditions as making it more likely that a deviation from SOPs will occur. Awareness of these factors can influence adherence to SOPs and may also be useful in developing corresponding prevention strategies.

  • ·         Corporate culture (e.g., the absence of company management’s clear commitment to SOPs and standardization; double standard practices)
  • ·         Ineffective or unclear company policies (e.g., regarding schedules, costs, go around, diversion, crew duty time, etc.)
  • ·         Inadequate awareness/ knowledge of, or failure to understand the procedure, or action (e.g., quality of wording or phrasing; procedure or action being perceived as inappropriate)
  • ·         Insufficient emphasis on strict adherence to SOPs during routine training and checks.
  • ·         Insufficient vigilance (e.g., due to fatigue)
  • ·       Distractions (e.g., due to cockpit activity)
  • ·         Interruptions (e.g., due to ATC communication)
  • ·         Task saturation resulting in fixation/ degraded multi-tasking ability or task overload leading to reduced attention.
  • ·         Incorrect management of priorities (e.g., lack of or incorrect decision-making model for time-critical situations)
  • ·         Incorrect CRM techniques, especially the absence of cross-checking, crew coordination or effective backup
  • ·         Personal desires or constraints (e.g., personal schedule, press-on-itis)
  • ·         Complacency or Over confidence


An Effective SOP

An effective SOP would need the active collaboration of all stake holders, at the formulation as well as the implementation stages. The following factors should thus be considered for creating effective SOPs: -

  •  All crew members should be aware of the reasons for the procedure, and should also be convinced of the need to follow the same. It is a known fact that when flight crew members are so convinced, then they are more likely to follow the procedure, and also offer valuable feedback to improve upon an existing procedure, or  introduce a new relevant procedure.
  •   All crew members should hold the belief that the procedure is appropriate to the stated flight situation, and would cover all the likely eventualities. This should be reinforced during effective training sessions conducted by the operator’s flight instructors/ check pilots.
  •  The procedure should clearly lay down what needs to be done, by whom (PF/ PM), and when it is to be done. Each crew’s responsibilities would thus be clearly delineated.
  •  The senior supervisors should set an example through word, and more importantly through their deeds that SOPs are to be followed. Any shortcomings/ misgivings about the procedure that are pointed out by the line crew should be discussed and remedial action initiated, if considered appropriate; otherwise the crew member should be provided feedback of the reason why the suggestion is not considered worthy of implementation.

 It has been seen that many a times SOPs are not consistently implemented, in that double standards are practiced by the crew and these are also condoned by the instructors/ check pilots/ managers. Flight crews follow the SOPs during training and check rides, but do it their own way during routine line operations. When this kind of a situation exists, it is an indication that the SOP is either not practical or effective for some reason. The reason for the deviation should thus be investigated and remedial action initiated.

Summary


Safety in aviation continues to depend on good crew performance. Good crew performance, in turn, is founded on standard operating procedures that are clear, comprehensive, and readily available to the flight crew. Development of SOPs is most effective when done by collaboration, using the best resources available including the end-users themselves, the flight crew. Once developed, effective SOPs should be consistently enforced during training as well as during line operations and ineffective SOPs should be continually reviewed and renewed. Double standards should not be permitted.

Thursday, May 30, 2013

PILOTS AND COMMUNICATIONS

Aircraft Operations and Communications

An aircraft comes in to regular flight operations only once it has been accorded regulatory approval, the whole purpose of which is aimed at providing an error free product. However, latent errors can still be present. The recent Boeing 787 battery snafu that led to the world wide fleet being grounded is a case in point. Even when the approval process ensures an error free aircraft, there are still chances of errors creeping in during regular flight operations because each individual aircraft is tended to by a large number of diverse groups. These errors can be prevented and safety & efficiency can be ensured only if all these diverse groups work as a team, which can only happen when there is adequate co-ordination between, and within, the various groups, viz. the flight crew, cabin crew, dispatch, Air Traffic Control, maintenance personnel, and others directly or indirectly connected with the safe operation of the flight. Communications is that vital link that helps in ensuring good co-ordination between all of these different agencies. Thus understanding communications is important for anyone connected with aviation, and more importantly for the flight deck crew, they being aviation’s last line of defence to prevent any mishap from happening.

Communication is a two way process, in which a message is sent out from the sender to the receiver; the receiver gives feedback; and this process continues in a loop until the same meaning is shared between the sender and the receiver. The message can be sent either verbally in the form of oral or written communications or through non verbal means like body language, gestures, postures, face & eye expressions, touch, etc. Communication is a concept that has been variously defined in text books. These definitions essentially characterise communications in terms of two basic issues, which are: -  

·         First, communication entails the transfer of information (facts, opinions, ideas, feelings, instructions, commands, etc.)  from the sender to the receiver
·         And second, communication entails the transfer of meaning from the sender to the receiver

Effective Communications

Communications are useful only when they are effective, in that the transfer of information from the sender to the receiver should lead to the same meaning being shared by each of them, at the completion of the transaction(s). This can only happen when the sender and receiver are both active participants in the process and thus entails a responsibility not only on the sender to obtain or elicit feedback in order to determine whether or not the communication was effective but also on the receiver, who is responsible to provide honest feedback. Or in other words, effective communication is a two way process, and is only effective when the desired understanding or action takes place. In the fatal Air India Express accident at Mangalore, the First Officer had thrice communicated to the Commander to go around, but no go around action was initiated by the Commander during the approach and touchdown phase. Would this communication be considered effective? In this paper we would only focus on effective communication between the flight deck crew.

Communications and Crew Resource Management

Effective communication between flight deck crew members is an essential tool for achieving technical, procedural, and also crew resource management objectives. The communication process amongst the flight deck crew fulfils many important functions. Research shows that these functions include:

·         The most obvious being the transfer of information in the form of checklists, logs, R/T, etc.
·         Interpersonal/ team relationships that are crucial in any highly effective team, primarily because humans are emotional, in addition to being rational beings
·         Working towards shaping predictable behaviour and expectations from the other crew members, through the medium of briefings and critiques
·         It helps the crew to develop a shared mental model about the location, spatial orientation, environment, aircraft systems, time and fuel; thereby enhancing situational awareness
·         It allows individual crew members to become aware of problems and to contribute effectively to the problem solving and decision-making process on the flight deck
·         It helps the efficient and effective management of the flight with optimum use of available resources, including the crew, through planning, implementing/ revising & monitoring the tasks; the environment; and the crew.

These functions are all crucial for safe and efficient flight operations and underpin the important role of communications on the flight deck. Research has shown that each message can have different content, depending on the circumstances. These circumstances could be whether we communicate face to face, or under high workload conditions, or on R/T, or through written messages or through gestures.

Face to Face Communications

In this kind of a situation, the message content is dependent just 7% on the spoken words. The major part of the message content is conveyed by the tone employed while speaking (38%); and on the non verbal aspects of communications (55%) like body language, eye & facial expressions, postures etc. The flight deck crew would encounter this situation when they come face to face on arrival at the dispatch and also during low workload periods, as in a long cruise on autopilot. It is important to remember that in such a situation, words of the sender convey very little meaning to the receiver, if they are not backed by the right tone and the non verbal cues. The message communicated during this interaction would be stored and all future interactions on the flight deck would take place keeping the sense of the stored communications in mind.

Pre-Flight Brief:  Face to face communications normally include a pre flight brief. A good pre-flight brief is very important because it effectively touches nearly every function of communications that are enumerated above. Open questions, like ‘how is this weather likely to impact our flight? Why do you think so?’ by the Commander can draw in the other crew members into giving valuable inputs that should be incorporated in the plan, if feasible. This gives the crew a sense of ownership and would also send a very positive message, which would lead to a very effective team that is motivated to optimum individual, as well as team performance. The Commander has a major role to play in setting the tone, but the crew members also need to live up to the transactional analysis dictum of ‘I am OK, you are OK’. This can only happen if the crew members believe/ are made to believe that they have an important role to play in the safe and efficient conduct of the flight. This can happen if all crew members are encouraged to participate in the communication process, and more importantly are listened to, and treated like trained professionals having a vital role to play during the flight. Operating from the adult ego state would be desirable but depending on the experience of the crew it may need to switch between the adult and the nurturing parent/ natural child ego states too, at times. Crossed and other damaging ego states should be avoided under all circumstances.

High workload situations

The contents of the message change completely in a high work load situation, like during a take-off, landing or during non normal situations. Here words convey 55% of the meaning; the tone of the words spoken another 38%, and body language just the balance 7%. This tells us that it is most important to use standard phraseology with the correct intonation and sense of urgency during these situations. Standard phraseology has the advantage of brevity with accuracy, as both the sender and receiver are on the same page instantly. This however, does not rule out the need to give feedback, read back and hear back, as appropriate. High workload situations are most prone to the use of leading questions, wherein the need for quick answers overrides all else, but these are also the situations when these are most dangerous. Leading questions under such situations are thus best avoided. The analysis of a number of aircraft accidents indicate an increasing number of leading questions leading up to the accident. Leading questions generally are an indicator of a loss of situational awareness. 

Communications on R/T, Intercom or Telephone

In such a situation the content of the message is conveyed 55% through the spoken words and the balance 45% through the intonation, speed and clarity of the spoken words. Standard phraseology is vital in this situation along with feedback, read back and hear back. In case of any disruptions in any of the messages, it is important to retransmit/ seek a clarification instead of assuming, as was the case in the tragic Tenerife accident. Choice of words in verbal communications has significant safety implications. In order to minimise potential ambiguities and other variances in aviation, there are certain standard rules regarding which words, phrases or other elements need to be used for communicating. As an example, ICAO phraseology requires that the word ‘departure’ is used instead of ‘take-off’ in all cases, except for the actual take-off itself. It also requires all clearances, heading, altitudes, runways etc. to be read-back by the crew, as also hear back by the ATC. This was introduced to enhance safety following many cases where messages were misinterpreted/ read back incorrectly.

Written communications

90% of the meaning is conveyed through words or symbols in written communications, with only the balance 10% through the tone of the message. This implies that the choice and use of words and symbols are critical in written communications, like in SOPs, checklists, let down charts, etc. This is even more so in the modern day cockpits with EFIS; the choice of symbols, colours, updating of the databases, etc. become even more critical as there is no dynamic feedback available in the cockpit that can prevent misconceptions/ misrepresentations from leading to an untoward incident. Updation date of the database should be checked before every flight by the crew to ensure that the database is current. The initiator of the written communications should be able to unambiguously create the message in such a way that clearly conveys the intended meaning. It is the responsibility of the crew also to clarify every written communication and get it rectified in case the words and symbols, etc. are perceived differently from what they are intended to convey. Latent errors in written communications are possible and should be eliminated for safe operations.

Gestures

This form of communication is routinely used in aviation while marshalling an aircraft, and demands that each signal should convey a common understanding to the sender as well as the receiver. Since aviation is an international profession, all the hand signals have been standardised and should be used to prevent chances of misunderstanding. Non standard signals should be avoided.

Accent free English Language for Communications

As discussed above, words are important in almost all forms of communications barring gestures, but even more so on R/T, intercom or telephone and also during high workload situations. The message conveyed is affected by the language employed, the individual accents, pronunciation, vocabulary and grammatical styles. Investigations in to a number of accidents brought home the requirement for a common language for the flight crew in which they should be reasonably proficient to ensure effective communications. ICAO thus recommended through SARPs that language testing should be undertaken to ensure proficiency.  Indian DGCA has implemented this recommendation vide a CAR in Section 7 titled, “English for Aviation Language - Training, Assessment, Test and Certification”.   This CAR lays down the six skill areas in which the crew need to be proficient, and tested. These areas include pronunciation, structure, vocabulary, fluency, comprehension and interactions. Six levels of competency have been identified, and crew have to attain a minimum of Level 4 to operate. The aim of this requirement is to make communications possible, and effective. Crew would still come across individual variations, and should be sensitive to this fact and thus ensure that these variations do not hinder effective communications.

Communications, Workload and Situational Awareness

It is a known fact that human cognitive resources are limited and are shared between current reasoning processes and actions. Communications also consume mental resources. This fact needs to be clearly understood and internalised to ensure that one is sensitive to the workload on the flight deck before initiating/ responding to communications or before interrupting communications already underway, for some other task. We have all experienced situations wherein an increased workload tended to shorten our sentences, as also reduce their numbers, thus increasing the chances of communication errors. The most relevant example is the execution of the ‘Before take-off checklist’. Invariably this gets interrupted by the ATC that is ready to give out the departure clearance. It is best to ask the ATC to standby and complete the checklist before taking down the clearance or take down the clearance and then re-initiate the checklist from the beginning to ensure that both of these crucial tasks are not interrupted, thus making them prone to errors.


Similarly, a person absorbed in a difficult or unfamiliar task like in an emergency situation is less likely to understand what someone is saying to them. It is always best to wait until the task is completed, or stabilised before interrupting them. It is difficult to continue with a demanding task while at the same time communicating effectively. Leading questions at such times can be disastrous, as the person may respond verbally without paying attention, due to lack of mental resources available at his/ her disposal. Please be aware that under conditions of excessive workload, one of the first signs of degraded situational awareness is a loss of the ability to listen in. Since communications consume limited mental resources, to conserve on these, communications should be restricted to task oriented only during the critical phases of flight when sterile cockpit is called for. This ensures that communications are not distracting the crew during periods of anticipated high workload and helps the crew maintain situational awareness.

Friday, April 19, 2013

AIR INDIA EXPRESS ACCIDENT AT MANGALORE: 22 MAY 2010

(Adapted from Flight Safety Foundation website)

The outbound flight IX-811 of Air India Express between Mangalore and Dubai was uneventful and landed at Dubai at 01:14 IST. The airplane was serviced and refuelled. The same flight crew operated the return leg from Dubai to Mangalore as flight IX-812. The airplane taxied out for departure at 02:36 IST. 

Take-off, climb and cruise were uneventful. During the flight, there was no conversation between the two pilots for about 1:40 hours because the Captain was asleep. The First Officer was making all the radio calls.
The aircraft reported position at IGAMA at 05:33 hours IST and was advised to expect an ILS DME Arc approach to Mangalore. At about 130 miles from Mangalore, the First Officer requested descent clearance, which was denied by the Mangalore Area Controller, who was using standard procedural control to ensure safe separation with other air traffic. The flight was advised to call at 80 DME. At 05:46 IST, the flight reported 80 DME, as instructed by Mangalore Area Control. The aircraft was cleared to 7000 ft. The aircraft commenced descent at 77 DME from Mangalore at 05:47 IST. The visibility reported was 6 km.

Mangalore airport has a table top runway, best described by AIP India as, "Aerodrome located on hilltop. Valleys 200ft to 250ft immediately beyond paved surface of Runway." Owing to the surrounding terrain, Air India Express had made a special qualification requirement that only the PIC shall carry out the take- off and landing. The Captain on the accident flight had made a total of 16 landings in the past at this airport and the First Officer had operated as a Co-pilot on 66 flights at this airport.

While the aircraft had commenced descent, there was no recorded conversation regarding the mandatory preparation for descent and landing briefing as stipulated in the SOP. After the aircraft was at about 50 miles and descending out of FL 295, the conversation between the two pilots indicated that an incomplete approach briefing had been carried out. At about 25 nm from DME and descending through FL 184, the Mangalore Area Controller cleared the aircraft to continue descent to 2900 ft. At this stage, the First Officer requested, if they could proceed directly to Radial 338 and join the 10 DME Arc. Throughout the descent profile and DME Arc Approach for ILS 24, the aircraft was much higher than normally expected altitudes. The aircraft was handed over by the Mangalore Area Controller to ATC Tower at 05:52 IST. The Tower controller, thereafter, asked the aircraft to report established on 10 DME Arc for ILS Runway 24. By now the yawning by the First Officer recorded on the CVR indicated that even he was showing signs of tiredness. This flight was operating in WOCL (Window of Circadian Low). On having reported 10 DME Arc, the ATC Tower had asked the aircraft to report when established on ILS.

It appears that the Captain had realised that the aircraft altitude was higher than normal and had selected Landing Gear 'DOWN' at an altitude of approximately 8,500 ft with speed brakes still deployed in Flight Detent position, so as to increase the rate of descent. As indicated by the DFDR, the aircraft continued to be high and did not follow the standard procedure of intercepting the ILS Glide Path at the correct intercept altitude. This incorrect procedure led to the aircraft being at almost twice the altitude as compared to a Standard ILS Approach.

During approach, the CVR indicated that the Captain had selected Flaps 40 degrees and completed the Landing Check List. At 06:03 hours IST at about 2.5 DME, the Radio Altimeter had alerted an altitude of 2500 ft. This was immediately followed by the First Officer saying "It is too high" and "Runway straight down". In reply, the Captain had exclaimed "Oh my god". At this moment, the Captain had disconnected the Auto Pilot and simultaneously increased the rate of descent considerably to establish on the desired approach path. At this stage, the First Officer had queried "Go around?" To this query from the First Officer, the Captain had called out "Wrong loc .. ... localiser .. ... glide path".  

The First Officer had given a second call to the Captain for "Go around" followed by "Unstabilised". However, the First Officer did not appear to take any action, to initiate a Go Around. Having acquired the runway visually and to execute a landing, it appears that the Captain had increased the rate of descent to almost 4000 ft per minute. Due to this, there were numerous warnings from EGPWS for 'SINK RATE' and 'PULL UP'. On their own, the pilots did not report having established on ILS Approach.

Instead, the ATC Tower had queried the same. To this call, the Captain had forcefully prompted the First Officer to give a call of "Affirmative". The Tower controller gave landing clearance thereafter and also indicated "Winds calm". The aircraft was high on approach and touched down on the runway, much farther than normal.

The aircraft had crossed the threshold at about 200 ft / IAS in excess of 160 kt, against the target of 50 ft and 144 kts for this landing weight. Despite the EGPWS warnings and calls from the First Officer to go around, the Captain had persisted with the approach in unstabilised conditions. Short of touchdown, there was yet another (Third) call from the First Officer, "Go around captain...We don't have runway left". However, the Captain had continued with the landing and the final touchdown was about 5200 ft from the threshold of runway 24, leaving approximately 2800 ft of remaining paved surface.

The Captain had selected Thrust Reversers soon after touchdown. Within 6 seconds of applying brakes, the Captain had initiated a 'Go Around', in contravention of Boeing SOP. The aircraft overshot the runway including the strip of 60 metres. After overshooting the runway and strip, the aircraft continued into the Runway End Safety Area (RESA) of 90 metres. Soon after which the right wing impacted the localiser antenna structure located further at 85 metres from the end of RESA. Thereafter, the aircraft hit the boundary fence and fell into a gorge.

(Image Courtesy: ARKarthik.com

CAUSE OF THE ACCIDENT

Direct

The Court of Inquiry determines that the cause of this accident was Captain's failure to discontinue the 'unstabilised approach' and his persistence in continuing with the landing, despite three calls from the First Officer to 'go around' and a number of warnings from EGPWS.

Contributing Factors to the Accident

1.            In spite of availability of adequate rest period prior to the flight, the Captain was in prolonged sleep during flight, which could have led to sleep inertia. As a resu lt of relatively short period of time between his awakening and the approach, it possibly led to impaired judgment. This aspect might have got accentuated while flying in the Window of Circadian Low (WOCL).

2.            In the absence of Mangalore Area Control Radar (MSSR), due to unserviceability, the aircraft was given descent at a shorter distance on DME as compared to the normal. However, the flight crew did not plan the descent profile properly, resulting in remaining high on approach.

3.            Probably in view of ambiguity in various instructions empowering the 'copilot' to initiate a 'go around ', the First Officer gave repeated calls to this effect, but did not take over the controls to actually discontinue the ill-fated approach.

Sunday, March 31, 2013

HELIOS AIRWAYS FLIGHT 522: 14 AUG 2005


(From Flight Safety Foundation)

Brief Description

Helios' Boeing 737-300 underwent maintenance on the night prior to the accident. The pressurization system was checked, but after completion of the tests the Pressurization Mode Selector (PMS) was reportedly left in the "Manual" position instead of the "Auto" mode. In manual mode the crew had to manually open or close the outflow valves in order to control the cabin pressure. The outflow valves were one-third in the open position which meant that the cabin would not pressurize after takeoff. The PMS mode was apparently not noted during the pre-departure checks by the crew.

In the morning the 737 was to operate Flight 522 from Larnaca to Prague, Czech Republic with an intermediate stop at Athens, Greece. The flight departed Larnaca at 09:07 for the leg to Athens with a planned flying time of 1 hour and 23 minutes. As the airplane climbed over the Mediterranean the cabin altitude alert horn sounded. This occurred as the 737 passed through an altitude of 10,000 feet. Cabin altitude is usually held around 8,000 feet. The crew possibly thought it was an erroneous takeoff configuration warning because the sound is identical. Then, at 14,000 feet, the oxygen masks automatically deployed and a master caution light illuminated in the cockpit. Because of a lack of cooling air another alarm activated, indicating a temperature warning for the avionics bay.

The German captain and the Cypriot co-pilot tried to solve the problem but encountered some problems communicating with each other. They contacted the Helios´ maintenance base to seek advice. The engineer told that they needed to pull the circuit breaker to turn off the alarm. The radio contact ended as the aircraft climbed through 28 900 ft. The circuit breaker was located in a cabinet behind the captain. The captain got up from his seat to look for the circuit breaker. The crews were not wearing their oxygen masks as their mindset and actions were determined by the preconception that the problems were not related to the lack of cabin pressure.

As the airplane was still climbing the lack of oxygen seriously impaired the flight crew. The captain probably became unconscious when he was trying to find the circuit breaker. The first officer was still in his seat when he also became unconscious. Because the plane's autopilot was programmed for FL340 the Boeing continued to climb until leveling out at that altitude some 19 minutes after takeoff. At 09:37 the 737 entered the Athens FIR but no R/T contact was established with the flight. Over Rodos at about 09:52 the airplane entered the UL995 airway. At 10:21 the airplane passed the KEA VOR, which is located about 28 nm south of the Athens airport. The airplane then passed the Athens Airport and subsequently entered the KEA VOR holding pattern at 10:38. All efforts by Greek air traffic controllers to contact the pilots were futile. Around 11:00 two Greek F-16 fighter planes were scrambled from the Néa Anghialos air base. At 11:24, during the sixth holding pattern, the F-16's intercepted the airliner. The F-16 pilots reported that they were not able to observe the captain, while the first officer seemed to be unconscious and slumped over the controls.
At 11:49, the F-16's reported a person not wearing an oxygen mask entering the cockpit and occupying the captain's seat. The F-16 pilot tried to attract his attention without success. At 11:50, the left engine flamed out due to fuel depletion and the aircraft started descending. At 11:54, two Mayday messages were recorded on the CVR. At 12:00, the right engine also flamed out at an altitude of approximately 7100 feet. The aircraft continued descending rapidly and impacted hilly terrain.

The same Boeing 737 had, suffered a loss of cabin pressure on December 20, 2004 during a flight from Warsaw to Larnaca. Three passengers needed medical treatment after landing in Larnaca. This incident was caused by a leaking door seal of the right hand rear door.

Direct Causes

1. Non-recognition that the cabin pressurization mode selector was in the MAN (manual) position during the performance of the:
a) Preflight procedure;
b) Before Start checklist; and
c) After Takeoff checklist.

2. Non-identification of the warnings and the reasons for the activation of the warnings (cabin altitude warning horn, passenger oxygen masks deployment indication, Master Caution), and continuation of the climb.

3. Incapacitation of the flight crew due to hypoxia, resulting in continuation of the flight via the flight management computer and the autopilot, depletion of the fuel and engine flameout, and impact of the aircraft with the ground.

Latent Causes

1. The Operator’s deficiencies in organization, quality management and safety culture, documented diachronically as findings in numerous audits.

2. The Regulatory Authority’s diachronic inadequate execution of its oversight responsibilities to ensure the safety of operations of the airlines under its supervision and its inadequate responses to findings of deficiencies documented in numerous audits.

3. Inadequate application of Crew Resource Management (CRM) principles by the flight crew.

4. Ineffectiveness and inadequacy of measures taken by the manufacturer in response to previous pressurization incidents in the particular type of aircraft, both with regard to modifications to aircraft systems as well as to guidance to the crews.

Contributing Factors to the Accident

1. Omission of returning the pressurization mode selector to AUTO after un-scheduled maintenance on the aircraft.

2. Lack of specific procedures (on an international basis) for cabin crew procedures to address the situation of loss of pressurization, passenger oxygen masks deployment, and continuation of the aircraft ascent (climb).

3. Ineffectiveness of international aviation authorities to enforce implementation of corrective action plans after relevant audits.

Saturday, February 2, 2013

COULD THIS ACCIDENT BE PREVENTED?


Helios' Boeing 737-300 underwent maintenance on the night prior to the accident. The pressurization system was checked, but after completion of the tests the Pressurization Mode Selector (PMS) was reportedly left in the "Manual" position instead of the "Auto" mode. In manual mode the crew had to manually open or close the outflow valves in order to control the cabin pressure. The outflow valves were one-third in the open position which meant that the cabin would not pressurize after takeoff. The PMS mode was apparently not noted during the pre-departure checks by the crew.

In the morning the 737 was to operate Flight 522 from Larnaca to Prague, Czech Republic with an intermediate stop at Athens, Greece. The flight departed Larnaca at 09:07 for the leg to Athens with a planned flying time of 1 hour and 23 minutes. As the airplane climbed over the Mediterranean the cabin altitude alert horn sounded. This occurred as the 737 passed through an altitude of 10,000 feet. Cabin altitude is usually held around 8,000 feet. The crew possibly thought it was an erroneous takeoff configuration warning because the sound is identical. Then, at 14,000 feet, the oxygen masks automatically deployed and a master caution light illuminated in the cockpit. Because of a lack of cooling air another alarm activated, indicating a temperature warning for the avionics bay.

The German captain and the Cypriot co-pilot tried to solve the problem but encountered some problems communicating with each other. They contacted the Helios´ maintenance base to seek advice. The engineer told that they needed to pull the circuit breaker to turn off the alarm. The radio contact ended as the aircraft climbed through 28 900 ft. The circuit breaker was located in a cabinet behind the captain. The captain got up from his seat to look for the circuit breaker. The crews were not wearing their oxygen masks as their mindset and actions were determined by the preconception that the problems were not related to the lack of cabin pressure.

As the airplane was still climbing the lack of oxygen seriously impaired the flight crew. The captain probably became unconscious when he was trying to find the circuit breaker. The first officer was still in his seat when he also became unconscious. Because the plane's autopilot was programmed for FL340 the Boeing continued to climb until leveling out at that altitude some 19 minutes after takeoff. At 09:37 the 737 entered the Athens FIR but no R/T contact was established with the flight. Over Rodos at about 09:52 the airplane entered the UL995 airway. At 10:21 the airplane passed the KEA VOR, which is located about 28 nm south of the Athens airport. The airplane then passed the Athens Airport and subsequently entered the KEA VOR holding pattern at 10:38. All efforts by Greek air traffic controllers to contact the pilots were futile. Around 11:00 two Greek F-16 fighter planes were scrambled from the Néa Anghialos air base. At 11:24, during the sixth holding pattern, the F-16's intercepted the airliner. The F-16 pilots reported that they were not able to observe the captain, while the first officer seemed to be unconscious and slumped over the controls.
At 11:49, the F-16's reported a person not wearing an oxygen mask entering the cockpit and occupying the captain's seat. The F-16 pilot tried to attract his attention without success. At 11:50, the left engine flamed out due to fuel depletion and the aircraft started descending. At 11:54, two Mayday messages were recorded on the CVR. At 12:00, the right engine also flamed out at an altitude of approximately 7100 feet. The aircraft continued descending rapidly and impacted hilly terrain.

The same Boeing 737 had, suffered a loss of cabin pressure on December 20, 2004 during a flight from Warsaw to Larnaca. Three passengers needed medical treatment after landing in Larnaca. This incident was caused by a leaking door seal of the right hand rear door.

DIRECT CAUSES:

1. Non-recognition that the cabin pressurization mode selector was in the MAN (manual) position during the performance of the:
a) Preflight procedure;
b) Before Start checklist; and
c) After Takeoff checklist.

2. Non-identification of the warnings and the reasons for the activation of the warnings (cabin altitude warning horn, passenger oxygen masks deployment indication, Master Caution), and continuation of the climb.

3. Incapacitation of the flight crew due to hypoxia, resulting in continuation of the flight via the flight management computer and the autopilot, depletion of the fuel and engine flameout, and impact of the aircraft with the ground.

LATENT CAUSES

1. The Operator’s deficiencies in organization, quality management and safety culture, documented diachronically as findings in numerous audits.

2. The Regulatory Authority’s diachronic inadequate execution of its oversight responsibilities to ensure the safety of operations of the airlines under its supervision and its inadequate responses to findings of deficiencies documented in numerous audits.

3. Inadequate application of Crew Resource Management (CRM) principles by the flight crew.

4. Ineffectiveness and inadequacy of measures taken by the manufacturer in response to previous pressurization incidents in the particular type of aircraft, both with regard to modifications to aircraft systems as well as to guidance to the crews.

CONTRIBUTING FACTORS TO THE ACCIDENT:

1. Omission of returning the pressurization mode selector to AUTO after un-scheduled maintenance on the aircraft.

2. Lack of specific procedures (on an international basis) for cabin crew procedures to address the situation of loss of pressurization, passenger oxygen masks deployment, and continuation of the aircraft ascent (climb).

3. Ineffectiveness of international aviation authorities to enforce implementation of corrective action plans after relevant audits.