Skip to content
TheChatArchiveThe Chat Archive
gpt-4o-mini-2024-07-18· OpenAIAi2 WildChat-4.8M (AI2)

Module 2: Emergency Procedures/Priority • Establishing Priorities in Emergencies: o…

  1. User

    Module 2: Emergency Procedures/Priority • Establishing Priorities in Emergencies: o Sequence of actions to manage emergencies. • Crew Coordination and Communication: o SOPs for emergency scenarios. • Case Studies: o Real-life incidents demonstrating effective emergency procedures. ChatGPT said: ChatGPT MODULE 2: EMERGENCY PROCEDURES/PRIORITY Module Overview: This module delves into the specific procedures and priorities necessary to manage emergencies effectively in aviation. It covers the sequence of actions to be taken during emergencies, the importance of crew coordination and communication, and provides case studies that illustrate successful application of emergency procedures.

    Learning Objectives: By the end of this module, participants should be able to:

    Establish and implement priorities during emergencies. Understand and apply Standard Operating Procedures (SOPs) for crew coordination and communication. Analyze real-life case studies to learn from successful emergency management. 2.1 Establishing Priorities in Emergencies Overview: In an aviation emergency, quick decision-making and clear prioritization are critical to ensuring the safety of passengers, crew, and the aircraft. Establishing the correct sequence of actions can mean the difference between a controlled situation and a disaster.

    Sequence of Actions to Manage Emergencies: Assess the Situation:

    Immediate Evaluation: The first priority is to quickly assess the nature and severity of the emergency. This includes identifying any immediate dangers and understanding the available options. Use Checklists: Refer to emergency checklists specific to the type of emergency (e.g., engine failure, fire, decompression) to ensure no critical step is overlooked. Declare an Emergency:

    Communicate with ATC: The flight crew should declare an emergency to Air Traffic Control (ATC) using the appropriate terminology (e.g., "Mayday" or "Pan-Pan"). Inform the Cabin Crew and Passengers: Cabin crew should be informed of the situation and instructed on necessary actions. Passengers should receive clear, calm instructions to prevent panic. Prioritize Actions Based on the Nature of the Emergency:

    Maintain Control of the Aircraft: The primary responsibility is to keep the aircraft under control. This includes ensuring stable flight, appropriate altitude, and speed adjustments. Address Immediate Threats: Any immediate threats, such as fire or loss of cabin pressure, should be managed first using emergency procedures. Navigate to a Safe Location:

    Determine the Nearest Suitable Airport: If an emergency landing is necessary, the crew should identify and proceed to the nearest suitable airport, considering factors like weather, runway length, and available emergency services. Prepare for Landing: Prepare the aircraft and passengers for an emergency landing if required. This may include dumping fuel, lowering landing gear, and briefing passengers on emergency procedures. Coordinate with Ground Services:

    Request Emergency Support: Coordinate with ground services, including fire and medical teams, to ensure they are prepared for an emergency landing or other necessary actions upon arrival. Review and Debrief Post-Emergency:

    Conduct a Post-Emergency Review: After the situation is resolved, the crew should review the incident, identify any lessons learned, and report to the relevant authorities for further analysis and safety improvements. 2.2 Crew Coordination and Communication Overview: Effective crew coordination and communication are fundamental to managing emergencies in aviation. Standard Operating Procedures (SOPs) outline the roles and responsibilities of each crew member and ensure that all actions are well-coordinated.

    SOPs for Emergency Scenarios: Clear Role Definitions:

    Captain: The captain is the ultimate decision-maker, responsible for evaluating the situation and directing the crew. First Officer: The first officer assists the captain by monitoring systems, handling communications, and following the captain's instructions. Cabin Crew: Responsible for passenger safety, managing the cabin environment, and assisting the flight crew as needed. Effective Communication:

    Closed-Loop Communication: Crew members should use closed-loop communication to ensure that instructions are understood and confirmed. This involves repeating orders and confirming actions taken. Use of Standard Phrases: Utilizing standard aviation phrases helps avoid misunderstandings, especially in high-stress situations. Cross-Check Procedures:

    Dual Verification: Critical actions, such as configuring the aircraft for emergency landing, should be verified by more than one crew member to avoid errors. Crew Resource Management (CRM): Emphasizes teamwork, situational awareness, and decision-making. CRM training helps crews work together efficiently and reduces the risk of errors. Regular Drills and Simulations:

    Emergency Simulations: Regular simulations of various emergency scenarios help crew members practice their roles and responses, ensuring preparedness. Debriefing After Drills: Post-simulation debriefings allow crews to discuss performance, identify areas for improvement, and reinforce best practices. 2.3 Case Studies Overview: Real-life case studies provide valuable insights into how emergencies are managed and the effectiveness of established procedures. Analyzing these cases helps reinforce the importance of proper training, coordination, and decision-making.

    Case Study 1: Miracle on the Hudson (2009) Incident: US Airways Flight 1549 struck a flock of geese shortly after takeoff, leading to a dual engine failure. Response: Captain Chesley "Sully" Sullenberger and First Officer Jeffrey Skiles successfully ditched the aircraft in the Hudson River. Key Lessons: Quick Decision-Making: The decision to land on the river was made within minutes, showcasing the importance of assessing the situation quickly. Crew Coordination: The crew maintained clear communication and executed their roles effectively under immense pressure. Preparation: Prior CRM training and adherence to SOPs contributed to the successful outcome. Case Study 2: British Airways Flight 38 (2008) Incident: The aircraft suffered a dual engine failure on final approach due to fuel starvation caused by ice crystals. Response: The crew managed to glide the aircraft onto the runway at Heathrow Airport, avoiding a catastrophic crash. Key Lessons: Handling the Unexpected: The crew's ability to maintain control and prioritize a safe landing despite unexpected circumstances was crucial. Post-Incident Analysis: The investigation led to changes in procedures for dealing with fuel-related issues in cold conditions. Case Study 3: Air Transat Flight 236 (2001) Incident: The aircraft experienced a complete fuel exhaustion over the Atlantic Ocean, requiring an emergency glide to the Azores. Response: The crew successfully glided the aircraft for 19 minutes and landed safely. Key Lessons: Emergency Preparedness: The crew's training in fuel management and emergency gliding techniques was instrumental in saving all onboard. Effective Communication: Coordination between the flight crew and ATC was essential in managing the situation and finding a safe landing spot. This module equips participants with the knowledge to prioritize actions during emergencies, understand the critical role of crew coordination, and learn from real-life examples. The goal is to enhance preparedness and ensure that every emergency situation is handled with the highest level of competence and safety.

  2. Assistant

    MODULE 2: EMERGENCY PROCEDURES/PRIORITY

    Module Overview:

    This module focuses on the essential procedures and priorities necessary for effective emergency management in aviation. It encompasses the sequence of actions required during emergencies, the significance of crew coordination and communication, and presents case studies that highlight the successful application of emergency protocols.

    Learning Objectives:

    By the end of this module, participants should be able to:

    • Establish and implement priorities during emergency scenarios.
    • Understand and apply Standard Operating Procedures (SOPs) for effective crew coordination and communication.
    • Analyze real-life case studies to extract lessons on successful emergency management.

    2.1 Establishing Priorities in Emergencies

    Overview:

    In aviation emergencies, rapid decision-making and clear prioritization are crucial in ensuring the safety of passengers, crew, and the aircraft. The correct sequence of actions can differentiate between a controlled situation and a potential disaster.

    Sequence of Actions to Manage Emergencies:

    1. Assess the Situation:

      • Immediate Evaluation: Quickly assess the nature and severity of the emergency, identifying immediate dangers and understanding available options.
      • Use Checklists: Refer to emergency checklists specific to the situation (e.g., engine failure, fire, cabin decompression) to ensure critical steps are not overlooked.
    2. Declare an Emergency:

      • Communicate with ATC: Declare an emergency to Air Traffic Control (ATC) using appropriate terminology (e.g., “Mayday” or “Pan-Pan”).
      • Inform the Cabin Crew and Passengers: Notify cabin crew about the situation and provide clear instructions, ensuring passengers receive calm guidance to prevent panic.
    3. Prioritize Actions Based on the Nature of the Emergency:

      • Maintain Control of the Aircraft: Keeping the aircraft under control is the top priority, focusing on stabilizing flight and adjusting altitude and speed.
      • Address Immediate Threats: Manage immediate threats (e.g., fire, cabin pressure loss) using established emergency procedures.
    4. Navigate to a Safe Location:

      • Determine the Nearest Suitable Airport: Identify and proceed to the nearest suitable airport for emergency landing, considering weather and runway conditions.
      • Prepare for Landing: If an emergency landing is necessary, prepare the aircraft and passengers, which may include dumping fuel, lowering landing gear, and briefing passengers.
    5. Coordinate with Ground Services:

      • Request Emergency Support: Collaborate with ground services such as fire and medical teams to ensure preparedness upon arrival.
    6. Review and Debrief Post-Emergency:

      • Conduct a Post-Emergency Review: After resolution, review the incident, identify lessons learned, and report findings to relevant authorities for analysis and safety improvements.

    2.2 Crew Coordination and Communication

    Overview:

    Effective crew coordination and communication are fundamental for managing aviation emergencies. Standard Operating Procedures (SOPs) ensure that each crew member's roles and responsibilities align, making actions well-coordinated and efficient.

    SOPs for Emergency Scenarios:

    1. Clear Role Definitions:

      • Captain: The decision-maker responsible for evaluating the situation and directing crew actions.
      • First Officer: Assists the captain by monitoring systems, handling communications, and executing captain’s instructions.
      • Cabin Crew: Manages passenger safety, assists in cabin environment control, and supports flight crew as needed.
    2. Effective Communication:

      • Closed-Loop Communication: Crew members should repeat and confirm instructions to ensure understanding and execution of actions.
      • Use of Standard Phrases: Utilize standard aviation phrases to avoid misunderstandings, especially in high-stress situations.
    3. Cross-Check Procedures:

      • Dual Verification: Ensure critical actions, like configuring for an emergency landing, are confirmed by more than one crew member.
      • Crew Resource Management (CRM): Emphasizes teamwork, situational awareness, and effective decision-making, reducing errors.
    4. Regular Drills and Simulations:

      • Emergency Simulations: Conduct regular simulations of various emergencies for practice and training.
      • Debriefing After Drills: Hold debriefings post-simulation to discuss performance, identify areas for improvement, and reinforce best practices.

    2.3 Case Studies

    Overview:

    Analyzing real-life case studies offers valuable insights into emergency management and the effectiveness of established procedures. These cases underline the importance of robust training, coordination, and decision-making.

    Case Study 1: Miracle on the Hudson (2009)

    • Incident: US Airways Flight 1549 encountered a flock of geese shortly after takeoff, leading to dual engine failure.
    • Response: Captain Chesley "Sully" Sullenberger and First Officer Jeffrey Skiles successfully ditched the aircraft in the Hudson River.
    • Key Lessons:
      • Quick Decision-Making: The timely decision to land on the river highlighted the importance of rapid situational assessment.
      • Crew Coordination: Effective communication and execution of roles were achieved under extreme pressure.
      • Preparation: Prior CRM training and strict adherence to SOPs were vital to the successful outcome.

    Case Study 2: British Airways Flight 38 (2008)

    • Incident: The aircraft experienced dual engine failure due to fuel starvation from ice crystals during final approach.
    • Response: The crew successfully glided the aircraft onto the runway at Heathrow Airport, averting disaster.
    • Key Lessons:
      • Handling the Unexpected: The crew’s ability to maintain control and prioritize a safe landing was crucial.
      • Post-Incident Analysis: Investigations prompted procedural changes to address fuel-related issues during cold conditions.

    Case Study 3: Air Transat Flight 236 (2001)

    • Incident: The aircraft faced complete fuel exhaustion over the Atlantic Ocean, necessitating an emergency glide to the Azores.
    • Response: The crew glided the aircraft for 19 minutes, landing safely.
    • Key Lessons:
      • Emergency Preparedness: The crew's training in fuel management and gliding techniques was critical for success.
      • Effective Communication: Coordination between flight crew and ATC was essential in managing the emergency and identifying a safe landing area.

    This module empowers participants to prioritize actions during emergencies, recognize the critical importance of crew coordination, and learn from real-world scenarios, enhancing preparedness for future incidents and ensuring the highest levels of safety.

  3. User

    reinforce this module with information from Doc 4444

    PROCEDURES RELATED TO EMERGENCIES, COMMUNICATION FAILURE AND CONTINGENCIES 15.1 EMERGENCY PROCEDURES 15.1.1 General 15.1.1.1 The various circumstances surrounding each emergency situation preclude the establishment of exact detailed procedures to be followed. The procedures outlined herein are intended as a general guide to air traffic services personnel. Air traffic control units shall maintain full and complete coordination, and personnel shall use their best judgement in handling emergency situations. Note 1.— Additional procedures to be applied in relation to emergencies and contingencies while using an ATS surveillance system are contained in Chapter 8, 8.8.1. Note 2.— If the pilot of an aircraft encountering a state of emergency has previously been directed by ATC to select a specific transponder code and/or a specific ADS-B emergency mode, that code and/or mode will normally be maintained unless, in special circumstances, the pilot has decided or has been advised otherwise. Where ATC has not requested a code or emergency mode to be set, the pilot will set the transponder to Mode A Code 7700 and/or the appropriate ADS-B emergency mode. Note 3.— Some aircraft equipped with first generation ADS-B avionics have the capability to transmit a general emergency alert only, regardless of the code selected by the pilot. Note 4.— Some aircraft equipped with first generation ADS-B avionics do not have the capability of squawking IDENT while the emergency and/or urgency mode is selected. 15.1.1.2 When an emergency is declared by an aircraft, the ATS unit should take appropriate and relevant action as follows: a) unless clearly stated by the flight crew or otherwise known, take all necessary steps to ascertain aircraft identification and type, the type of emergency, the intentions of the flight crew as well as the position and level of the aircraft; b) decide upon the most appropriate type of assistance which can be rendered; c) enlist the aid of any other ATS unit or other services which may be able to provide assistance to the aircraft; d) provide the flight crew with any information requested as well as any additional relevant information, such as details on suitable aerodromes, minimum safe altitudes, weather information; e) obtain from the operator or the flight crew such of the following information as may be relevant: number of persons on board, amount of fuel remaining, possible presence of hazardous materials and the nature thereof; and f) notify the appropriate ATS units and authorities as specified in local instructions. 15-2 Air Traffic Management (PANS-ATM) 10/11/16 15.1.1.3 Changes of radio frequency and SSR code should be avoided if possible and should normally be made only when or if an improved service can be provided to the aircraft concerned. Manoeuvring instructions to an aircraft experiencing engine failure should be limited to a minimum. When appropriate, other aircraft operating in the vicinity of the aircraft in emergency should be advised of the circumstances. Note.— Requests to the flight crew for the information contained in 15.1.1.2 e) will be made only if the information is not available from the operator or from other sources and will be limited to essential information. 15.1.2 Priority An aircraft known or believed to be in a state of emergency, including being subjected to unlawful interference, shall be given priority over other aircraft. 15.1.3 Unlawful interference and aircraft bomb threat 15.1.3.1 Air traffic services personnel shall be prepared to recognize any indication of the occurrence of unlawful interference with an aircraft. 15.1.3.2 Whenever unlawful interference with an aircraft is suspected, and where automatic distinct display of SSR Mode A Code 7500 and Code 7700 is not provided, the controller shall attempt to verify any suspicion by setting the SSR decoder to Mode A Code 7500 and thereafter to Code 7700. Note.— An aircraft equipped with an SSR transponder is expected to operate the transponder on Mode A Code 7500 to indicate specifically that it is the subject of unlawful interference. The aircraft may operate the transponder on Mode A Code 7700, to indicate that it is threatened by grave and imminent danger and requires immediate assistance. An aircraft equipped with other surveillance system transmitters, including ADS-B and ADS-C, might send the emergency and/or urgency signal by all of the available means. 15.1.3.3 Whenever unlawful interference with an aircraft is known or suspected or a bomb threat warning has been received, ATS units shall promptly attend to requests by, or to anticipated needs of, the aircraft, including requests for relevant information relating to air navigation facilities, procedures and services along the route of flight and at any aerodrome of intended landing, and shall take such action as is necessary to expedite the conduct of all phases of the flight. 15.1.3.3.1 ATS units shall also: a) transmit, and continue to transmit, information pertinent to the safe conduct of the flight, without expecting a reply from the aircraft; b) monitor and plot the progress of the flight with the means available, and coordinate transfer of control with adjacent ATS units without requiring transmissions or other responses from the aircraft, unless communication with the aircraft remains normal; c) inform, and continue to keep informed, appropriate ATS units, including those in adjacent FIRs, which may be concerned with the progress of the flight; Note.— In applying this provision, account must be taken of all the factors which may affect the progress of the flight, including fuel endurance and the possibility of sudden changes in route and destination. The objective is to provide, as far in advance as is practicable in the circumstances, each ATS unit with appropriate information as to the expected or possible penetration of the aircraft into its area of responsibility. d) notify: Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-3 10/11/16

    1. the operator or its designated representative;
    2. the appropriate rescue coordination centre in accordance with appropriate alerting procedures;
    3. the appropriate authority designated by the State; Note.— It is assumed that the designated security authority and/or the operator will in turn notify other parties concerned in accordance with pre-established procedures. e) relay appropriate messages, relating to the circumstances associated with the unlawful interference, between the aircraft and designated authorities. Note.— These messages include, but are not limited to: initial messages declaring an incident; update messages on an existing incident; messages containing decisions made by appropriate decision makers; messages on transfer of responsibility; messages on acceptance of responsibility; messages indicating that an entity is no longer involved in an incident; and messages closing an incident. 15.1.3.4 The following additional procedures shall apply if a threat is received indicating that a bomb or other explosive device has been placed on board a known aircraft. The ATS unit receiving the threat information shall: a) if in direct communication with the aircraft, advise the flight crew without delay of the threat and the circumstances surrounding the threat; or b) if not in direct communication with the aircraft, advise the flight crew by the most expeditious means through other ATS units or other channels. 15.1.3.5 The ATS unit in communication with the aircraft shall ascertain the intentions of the flight crew and report those intentions to other ATS units which may be concerned with the flight. 15.1.3.6 The aircraft shall be handled in the most expeditious manner while ensuring, to the extent possible, the safety of other aircraft and that personnel and ground installations are not put at risk. 15.1.3.7 Aircraft in flight shall be given re-clearance to a requested new destination without delay. Any request by the flight crew to climb or descend for the purpose of equalizing or reducing the differential between the outside air pressure and the cabin air pressure shall be approved as soon as possible. 15.1.3.8 An aircraft on the ground should be advised to remain as far away from other aircraft and installations as possible and, if appropriate, to vacate the runway. The aircraft should be instructed to taxi to a designated or isolated parking area in accordance with local instructions. Should the flight crew disembark passengers and crew immediately, other aircraft, vehicles and personnel should be kept at a safe distance from the threatened aircraft. 15.1.3.9 ATS units shall not provide any advice or suggestions concerning action to be taken by the flight crew in relation to an explosive device. 15.1.3.10 An aircraft known or believed to be the subject of unlawful interference or which for other reasons needs isolation from normal aerodrome activities shall be cleared to the designated isolated parking position. Where such an isolated parking position has not been designated, or if the designated position is not available, the aircraft shall be cleared to a position within the area or areas selected by prior agreement with the aerodrome authority. The taxi clearance shall specify the taxi route to be followed to the parking position. This route shall be selected with a view to minimizing any security risks to the public, other aircraft and installations at the aerodrome. Note.— See Annex 14, Volume I, Chapter 3. 15-4 Air Traffic Management (PANS-ATM) 10/11/16 15.1.4 Emergency descent 15.1.4.1 ACTION BY THE ATS UNIT Upon recognition that an aircraft is making an emergency descent, all appropriate action shall be taken immediately to safeguard all aircraft concerned. Appropriate actions may include the following, in the order appropriate for the circumstance: a) broadcasting an emergency message;

    b) issuing traffic information and/or instructions to aircraft affected by the descent;

    c) advising the minimum flight altitude and altimeter setting for the area of operation; and d) informing any other ATS units which may be affected by the emergency descent. 15.1.4.2 ACTION BY THE PILOT OF THE AIRCRAFT IN AN EMERGENCY DESCENT The pilot shall take the following steps as soon as practicable in the order appropriate for the circumstance: a) navigate as deemed appropriate by the pilot; b) advise the appropriate ATS unit of the emergency descent and, if able, intentions; c) set transponder to Code 7700 and, if applicable, select the appropriate emergency mode on ADS-B and/or ADS-C; d) turn on aircraft exterior lights (commensurate with appropriate operating limitations); e) watch for conflicting traffic both visually and by reference to ACAS (if equipped); and f) when emergency descent is complete, coordinate further intentions with the appropriate ATS unit. Note.— Procedures for the use of ACAS are contained in PANS-OPS, Volume I, Part III, Section 3, Chapter 3. 15.1.4.3 ACTION BY THE PILOT OF THE AIRCRAFT RECEIVING EMERGENCY DESCENT BROADCAST Unless specifically instructed by the ATS unit to clear the area or threatened by immediate danger, the pilot shall take the following actions: a) continue according to current clearance and maintain listening watch on the frequency in use for any further instructions from the ATS unit; and b) watch for conflicting traffic both visually and by reference to ACAS (if equipped). Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-5 10/11/16 15.2 SPECIAL PROCEDURES FOR IN-FLIGHT CONTINGENCIES IN OCEANIC AIRSPACE 15.2.1 Introduction 15.2.1.1 Although all possible contingencies cannot be covered, the procedures in 15.2.2, 15.2.3 and 15.2.4 provide for the more frequent cases such as: a) the inability to comply with assigned clearance due to meteorological conditions (15.2.4 refers); b) en-route diversion across the prevailing traffic flow (for example, due to medical emergencies (15.2.2 and 15.2.3 refer)); and c) the loss of, or significant reduction in, the required navigation capability when operating in an airspace where the navigation performance accuracy is a prerequisite to the safe conduct of flight operations, or pressurization failure (15.2.2 and 15.2.3 refer). Note.— Chapter 5, Section 5.2.2 contains procedures for degraded navigation capabilities. 15.2.1.2 The pilot shall take action as necessary to ensure the safety of the aircraft, and the pilot’s judgement shall determine the sequence of actions to be taken, having regard to the prevailing circumstances. Air traffic control shall render all possible assistance. 15.2.2 General procedures Note.— Figure 15-1 provides an aid for understanding and applying the contingency procedures contained in Sections 15.2.2 and 15.2.3. 15.2.2.1 If an aircraft is unable to continue the flight in accordance with its ATC clearance, a revised clearance shall be obtained, whenever possible, prior to initiating any action. 15.2.2.2 If prior clearance cannot be obtained, the following contingency procedures should be employed until a revised clearance is received. In general terms, the aircraft should be flown at an offset level and on an offset track where other aircraft are less likely to be encountered. Specifically, the pilot shall: a) leave the cleared track or ATS route by initially turning at least 30 degrees to the right or to the left, in order to establish and maintain a parallel, same direction track or ATS route offset 5.0 NM (9.3 km). The direction of the turn should be based on one or more of the following factors:

    1. aircraft position relative to any organized track or ATS route system;
    2. the direction of flights and flight levels allocated on adjacent tracks;
    3. the direction to an alternate airport;
    4. any strategic lateral offset being flown; and
    5. terrain clearance;

    5/11/20 No. 9 15-6 Air Traffic Management (PANS-ATM) 10/11/16 b) maintain a watch for conflicting traffic both visually and by reference to ACAS (if equipped) ), leaving ACAS in RA mode at all times, unless aircraft operating limitations dictate otherwise; c) turn on all aircraft exterior lights (commensurate with appropriate operating limitations); d) keep the SSR transponder on at all timesand, when able, squawk 7700, as appropriate and, if equipped with ADS-B or ADS-C, select the appropriate emergency functionality; e) as soon as practicable, advise air traffic control of any deviation from their assigned clearance; f) use means as appropriate (i.e. voice and/or CPDLC) to communicate during a contingency or emergency; g) if voice communications are used, the radiotelephony distress signal (MAYDAY) or urgency signal (PAN PAN) preferably spoken three times, shall be used, as appropriate; h) when emergency situations are communicated via CPDLC, the controller may respond via CPDLC. However, the controller may also attempt to make voice contact with the aircraft; Note.— Guidance on emergency procedures for controllers, radio operators, and flight crew in data link operations can be found in the Global Operational Data Link (GOLD) Manual (Doc 10037). i) establish communications with and alert nearby aircraft by broadcasting on the frequencies in use and at suitable intervals on 121.5 MHz (or, as a backup, on the inter-pilot air-to-air frequency 123.45 MHz): aircraft identification, the nature of the distress condition, intention of the pilot, position (including the ATS route designator or the track code, as appropriate) and flight level; and j) the controller should attempt to determine the nature of the emergency and ascertain any assistance that may be required. Subsequent ATC action with respect to that aircraft shall be based on the intentions of the pilot and overall traffic situation. 15.2.3 Actions to be taken once offset from track Note.— The pilot’s judgement of the situation and the need to ensure the safety of the aircraft will determine the actions outlined to be taken. Factors for the pilot to consider when deviating from the cleared track or ATS route or level without an ATC clearance include, but are not limited to: a) operation within a parallel track system; b) the potential for user preferred routes (UPRs) parallel to the aircraft’s track or ATS route; c) the nature of the contingency (e.g. aircraft system malfunction); and d) weather factors (e.g. convective weather at lower flight levels). 15.2.3.1 If possible, maintain the assigned flight level until established on the 9.3 km (5.0 NM) parallel, same direction track or ATS route offset. If unable, initially minimize the rate of descent to the extent that is operationally feasible. 15.2.3.2 Once established on a parallel, same direction track or ATS route offset by 9.3 km (5.0 NM), either:

    5/11/20 No. 9 Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-7 10/11/16 a) descend below FL 290, and establish a 150 m (500 ft) vertical offset from those flight levels normally used, and proceed as required by the operational situation or if an ATC clearance has been obtained, in accordance with the clearance; or Note 1.— Flight levels normally used are those contained in Annex 2 — Rules of the Air, Appendix 3. Note 2.— Descent below FL 290 is considered particularly applicable to operations where there is a predominant traffic flow (e.g. east-west) or parallel track system where the aircraft’s diversion path will likely cross adjacent tracks or ATS routes. A descent below FL 290 can decrease the likelihood of conflict with other aircraft, ACAS RA events and delays in obtaining a revised ATC clearance. b) establish a 150 m (500 ft) vertical offset (or 300 m (1000 ft) vertical offset if above FL 410) from those flight levels normally used, and proceed as required by the operational situation, or if an ATC clearance has been obtained, in accordance with the clearance. Note.— Altimetry system errors (ASE) may result in less than 150 m (500 ft) vertical spacing (less than 300 m (1000 ft) above FL 410) when the above contingency procedure is applied.

    5/11/20 No. 9 15-8 Air Traffic Management (PANS-ATM) 10/11/16 Figure 15-1. Visual aid for contingency procedures guidance

    5/11/20 No. 9  Attempt ATC clearance  Maintain FL if able or minimise climb/descent rate  Maintain visual and ACAS watch  ACAS in RA mode unless aircraft operating limitations dictate otherwise  Turn on exterior lights  When able, alert other aircraft on frequencies in use, 121.5 or 123.45 Pilot elects to descend below FL 290 Special procedures for in-flight contingencies in oceanic airspace (non-weather) When below FL 290, establish and maintain 150 m (500 ft) vertical offset when able and proceed as required until ATC clearance received.  Parallel offset same direction  Descend below FL 290 5 NM Cleared Slop No [15.2.3.2 a) refers] Cleared route [15.2.3.2 b) refers] Establish and maintain 150 m (500 ft) vertical offset when able and proceed as required until ATC clearance received. [or 300 m (1000 ft) vertical offset if above FL 410] Legend: Decision point ATC clearance No ATC clearance At least 30° Cleared level Offset route (FMS) (left or right of cleared route) Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-8A 10/11/16 15.2.4 Weather deviation procedures 15.2.4.1 GENERAL Note.— The following procedures are intended for deviations around adverse meteorological conditions. 15.2.4.1.1 When weather deviation is required, the pilot should initiate communications with ATC via voice or CPDLC. A rapid response may be obtained by either: a) stating “WEATHER DEVIATION REQUIRED” to indicate that priority is desired on the frequency and for ATC response; or b) requesting a weather deviation using a CPDLC lateral downlink message. 15.2.4.1.2 When necessary, the pilot should initiate the communications using the urgency call “PAN PAN” (preferably spoken three times) or by using a CPDCL urgency downlink message. 15.2.4.1.3 The pilot shall inform ATC when weather deviation is no longer required, or when a weather deviation has been completed and the aircraft has returned to its cleared route. 15.2.4.2 ACTIONS TO BE TAKEN WHEN CONTROLLER-PILOT 15.2.3.2COMMUNICATIONS ARE ESTABLISHED 15.2.4.2.1 The pilot should notify ATC and request clearance to deviate from track or ATS route, advising, when possible, the extent of the deviation requested. The flight crew will use whatever means are appropriate (i.e. voice and/or CPDLC) to communicate during a weather deviation. Note.— Pilots are advised to contact ATC as soon as possible with requests for clearance in order to provide adequate time for the request to be assessed and acted upon. 15.2.4.2.2 ATC should take one of the following actions: a) when appropriate separation can be applied, issue clearance to deviate from track; or b) if there is conflicting traffic and ATC is unable to establish appropriate separation, ATC shall:

    1. advise the pilot of inability to issue clearance for the requested deviation;
    2. advise the pilot of conflicting traffic; and
    3. request the pilot’s intentions. 15.2.4.2.3 The pilot should take the following actions: a) comply with the ATC clearance issued; or b) advise ATC of intentions and execute the procedures detailed in 15.2.4.3.

    5/11/20 No. 9 15-8B Air Traffic Management (PANS-ATM) 10/11/16 15.2.4.3 ACTIONS TO BE TAKEN IF A REVISED ATC CLEARANCE CANNOT BE OBTAINED Note.— The provisions of this section apply to situations where a pilot needs to exercise the authority of a pilot-in-command under the provisions of Annex 2, 2.3.1. 15.2.4.3.1 If the aircraft is required to deviate from track or ATS route to avoid adverse meteorological conditions and prior clearance cannot be obtained, an ATC clearance shall be obtained at the earliest possible time. Until an ATC clearance is received, the pilot shall take the following actions: a) if possible, deviate away from an organized track or ATS route system; b) establish communications with and alert nearby aircraft by broadcasting, at suitable intervals: aircraft identification, flight level, position (including ATS route designator or the track code) and intentions, on the frequency in use and on 121.5 MHz (or, as a backup, on the inter-pilot air-to-air frequency 123.45 MHz); c) watch for conflicting traffic both visually and by reference to ACAS (if equipped); d) turn on all aircraft exterior lights (commensurate with appropriate operating limitations); e) for deviations of less than 9.3 km (5.0 NM) from the originally cleared track or ATS route, remain at a level assigned by ATC; f) for deviations greater than, or equal to 9.3 km (5.0 NM) from the originally cleared track or ATS route, when the aircraft is approximately 9.3 km (5.0 NM) from track, initiate a level change in accordance with Table 15-1; g) if the pilot receives clearance to deviate from cleared track or ATS route for a specified distance and, subsequently, requests, but cannot obtain a clearance to deviate beyond that distance, the pilot should apply an altitude offset in accordance with Table 15-1 before deviating beyond the cleared distance; h) when returning to track or ATS route, be at its assigned flight level when the aircraft is within approximately 9.3 km (5.0 NM) of the centre line; and i) if contact was not established prior to deviating, continue to attempt to contact ATC to obtain a clearance. If contact was established, continue to keep ATC advised of intentions and obtain essential traffic information. Note.— If, as a result of actions taken under the provisions of 15.2.4.3.1, the pilot determines that there is another aircraft at or near the same flight level with which a conflict may occur, then the pilot is expected to adjust the path of the aircraft, as necessary, to avoid conflict. Table 15-1 Originally cleared track or ATS route centre line Deviations ≥ 9.3 km (5.0 NM) Level change EAST (000° – 179° magnetic) LEFT RIGHT DESCEND 90 m (300 ft) CLIMB 90 m (300 ft) WEST (180° – 359° magnetic) LEFT RIGHT CLIMB 90 m (300 ft) DESCEND 90 m (300 ft) 5/11/20 No. 9 Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-8C 10/11/16 15.3 AIR-GROUND COMMUNICATIONS FAILURE Note 1.— Procedures to be applied in relation to an aircraft experiencing air-ground communication failure when providing ATS surveillance services are contained in Chapter 8, Section 8.8.3. Note 2.— An aircraft equipped with an SSR transponder is expected to operate the transponder on Mode A Code 7600 to indicate that it has experienced air-ground communication failure. An aircraft equipped with other surveillance system transmitters, including ADS-B and ADS-C, might indicate the loss of air-ground communication by all of the available means. Note 3.— Some aircraft equipped with first generation ADS-B avionics have the capability to transmit a general emergency alert only, regardless of the code selected by the pilot. Note 4.— See also Chapter 6, 6.3.2.5, concerning departure clearances containing no geographical or time limit for a cleared level below the flight planned level and procedures to be applied in relation to an aircraft experiencing air-ground communication failure under such circumstances.

    5/11/20 No. 9 15-8D Air Traffic Management (PANS-ATM) 10/11/16 (This page is intentionally left blank)

    5/11/20 No. 9 Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-9 10/11/16 Note 5. — See also Chapter 5, 5.4.2.6.3.2, for additional requirements applying to communication failure during the application of the 50 NM longitudinal RNAV/RNP 10 separation minimum. 15.3.1 Action by air traffic control units when unable to maintain two-way communication with an aircraft operating in a control area or control zone shall be as outlined in the paragraphs which follow. 15.3.2 As soon as it is known that two-way communication has failed, action shall be taken to ascertain whether the aircraft is able to receive transmissions from the air traffic control unit by requesting it to execute a specified manoeuvre which can be observed by an ATS surveillance system or to transmit, if possible, a specified signal in order to indicate acknowledgement. Note.— Some aircraft equipped with first generation ADS-B avionics do not have the capability of squawking IDENT while the emergency and/or urgency mode is selected. 15.3.3 If the aircraft fails to indicate that it is able to receive and acknowledge transmissions, separation shall be maintained between the aircraft having the communication failure and other aircraft, based on the assumption that the aircraft will: a) if in visual meteorological conditions:

    1. continue to fly in visual meteorological conditions;
    2. land at the nearest suitable aerodrome; and
    3. report its arrival by the most expeditious means to the appropriate air traffic control unit; or b) if in instrument meteorological conditions or when conditions are such that it does not appear likely that the pilot will complete the flight in accordance with a):
    4. unless otherwise prescribed on the basis of a regional air navigation agreement, in airspace where procedural separation is being applied, maintain the last assigned speed and level, or minimum flight altitude if higher, for a period of 20 minutes following the aircraft’s failure to report its position over a compulsory reporting point and thereafter adjust level and speed in accordance with the filed flight plan; or
    5. in airspace where an ATS surveillance system is used in the provision of air traffic control, maintain the last assigned speed and level, or minimum flight altitude if higher, for a period of 7 minutes following: i) the time the last assigned level or minimum flight altitude is reached; or ii) the time the transponder is set to Code 7600 or the ADS-B transmitter is set to indicate the loss of air-ground communications; or iii) the aircraft’s failure to report its position over a compulsory reporting point; whichever is later and thereafter adjust level and speed in accordance with the filed flight plan;
    6. when being vectored or having been directed by ATC to proceed offset using RNAV without a specified limit, proceed in the most direct manner possible to rejoin the current flight plan route no later than the next significant point, taking into consideration the applicable minimum flight altitude;
    7. proceed according to the current flight plan route to the appropriate designated navigation aid or fix serving the destination aerodrome and, when required to ensure compliance with 5), hold over this aid or fix until commencement of descent;

    15-10 Air Traffic Management (PANS-ATM) 10/11/16 5) commence descent from the navigation aid or fix specified in 4) at, or as close as possible to, the expected approach time last received and acknowledged; or, if no expected approach time has been received and acknowledged, at, or as close as possible to, the estimated time of arrival resulting from the current flight plan; 6) complete a normal instrument approach procedure as specified for the designated navigation aid or fix; and 7) land, if possible, within 30 minutes after the estimated time of arrival specified in 5) or the last acknowledged expected approach time, whichever is later. Note 1.— Provisions related to minimum levels are contained in Annex 2, 5.1.2. Note 2.— As evidenced by the meteorological conditions prescribed therein, 15.3.3 a) relates to all controlled flights, whereas 15.3.3 b) relates only to IFR flights. Note 3.— See also 8.6.5.1 b) concerning the requirement for the flight crew to be informed of what a vector is to accomplish and the limit of the vector. 15.3.4 Action taken to ensure suitable separation shall cease to be based on the assumption stated in 15.3.3 when: a) it is determined that the aircraft is following a procedure differing from that in 15.3.3; or b) through the use of electronic or other aids, air traffic control units determine that action differing from that required by 15.3.3 may be taken without impairing safety; or c) positive information is received that the aircraft has landed. 15.3.5 As soon as it is known that two-way communication has failed, appropriate information describing the action taken by the air traffic control unit, or instructions justified by any emergency situation, shall be transmitted blind for the attention of the aircraft concerned, on the frequencies available on which the aircraft is believed to be listening, including the voice frequencies of available radio navigation or approach aids. Information shall also be given concerning: a) meteorological conditions favourable to a cloud-breaking procedure in areas where congested traffic may be avoided; and b) meteorological conditions at suitable aerodromes. 15.3.6 Pertinent information shall be given to other aircraft in the vicinity of the presumed position of the aircraft experiencing the failure. 15.3.7 As soon as it is known that an aircraft which is operating in its area of responsibility is experiencing an apparent radiocommunication failure, an air traffic services unit shall forward information concerning the radiocommunication failure to all air traffic services units concerned along the route of flight. The ACC in whose area the destination aerodrome is located shall take steps to obtain information on the alternate aerodrome(s) and other relevant information specified in the filed flight plan, if such information is not available. 15.3.8 If circumstances indicate that a controlled flight experiencing a communication failure might proceed to (one of) the alternate aerodrome(s) specified in the filed flight plan, the air traffic control unit(s) serving the alternate aerodrome(s) and any other air traffic control units that might be affected by a possible diversion shall be informed of the circumstances of the failure and requested to attempt to establish communication with the aircraft at a time when the aircraft could possibly be within communication range. This shall apply particularly when, by agreement with the operator or a designated representative, a clearance has been transmitted blind to the aircraft concerned to proceed to an alternate aerodrome, or when meteorological conditions at the aerodrome of intended landing are such that a diversion to an alternate is considered likely.

    Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-11 10/11/16 15.3.9 When an air traffic control unit receives information that an aircraft, after experiencing a communication failure has re-established communication or has landed, that unit shall inform the air traffic services unit in whose area the aircraft was operating at the time the failure occurred, and other air traffic services units concerned along the route of flight, giving necessary information for the continuation of control if the aircraft is continuing in flight. 15.3.10 If the aircraft has not reported within thirty minutes after: a) the estimated time of arrival furnished by the pilot; b) the estimated time of arrival calculated by the ACC; or c) the last acknowledged expected approach time, whichever is latest, pertinent information concerning the aircraft shall be forwarded to aircraft operators, or their designated representatives, and pilots-in-command of any aircraft concerned and normal control resumed if they so desire. It is the responsibility of the aircraft operators, or their designated representatives, and pilots-in-command of aircraft to determine whether they will resume normal operations or take other action. 15.4 ASSISTANCE TO VFR FLIGHTS 15.4.1 Strayed VFR flights and VFR flights encountering adverse meteorological conditions Note.— A strayed aircraft is an aircraft which has deviated significantly from its intended track or which reports that it is lost. 15.4.1.1 A VFR flight reporting that it is uncertain of its position or lost, or encountering adverse meteorological conditions, should be considered to be in a state of emergency and handled as such. The controller shall, under such circumstances, communicate in a clear, concise and calm manner and care shall be taken, at this stage, not to question any fault or negligence that the pilot may have committed in the preparation or conduct of the flight. Depending on the circumstances, the pilot should be requested to provide any of the following information considered pertinent so as to better provide assistance: a) aircraft flight conditions; b) position (if known) and level; c) airspeed and heading since last known position, if pertinent; d) pilot experience; e) navigation equipment carried and if any navigation aid signals are being received; f) SSR mode and code selected if relevant; g) ADS-B capability; h) departure and destination aerodromes; i) number of persons on board; j) endurance. 15-12 Air Traffic Management (PANS-ATM) 10/11/16 15.4.1.2 If communications with the aircraft are weak or distorted, it should be suggested that the aircraft climb to a higher level, provided meteorological conditions and other circumstances permit. 15.4.1.3 Navigation assistance to help the pilot determine the aircraft position may be provided by use of an ATS surveillance system, direction-finder, navigation aids or sighting by another aircraft. Care must be taken when providing navigation assistance to ensure that the aircraft does not enter cloud. Note.— The possibility of a VFR flight becoming strayed as a result of encountering adverse meteorological conditions must be recognized. 15.4.1.4 The pilot should be provided with reports and information on suitable aerodromes in the vicinity where visual meteorological conditions exist. 15.4.1.5 If reporting difficulty in maintaining or unable to maintain VMC, the pilot should be informed of the minimum flight altitude of the area where the aircraft is, or is believed to be. If the aircraft is below that level, and the position of the aircraft has been established with a sufficient degree of probability, a track or heading, or a climb, may be suggested to bring the aircraft to a safe level. 15.4.1.6 Assistance to a VFR flight should only be provided using an ATS surveillance system upon the request or concurrence of the pilot. The type of service to be provided should be agreed with the pilot. 15.4.1.7 When providing such assistance in adverse meteorological conditions, the primary objective should be to bring the aircraft into VMC as soon as possible. Caution must be exercised to prevent the aircraft from entering cloud. 15.4.1.8 Should circumstances be such that IMC cannot be avoided by the pilot, the following guidelines may be followed: a) other traffic on the ATC frequency not able to provide any assistance may be instructed to change to another frequency to ensure uninterrupted communications with the aircraft; alternatively the aircraft being assisted may be instructed to change to another frequency; b) ensure, if possible, that any turns by the aircraft are carried out clear of cloud; c) instructions involving abrupt manoeuvres should be avoided; and d) instructions or suggestions to reduce speed of the aircraft or to lower the landing gear, should, if possible, be carried out clear of cloud. 15.5 OTHER IN-FLIGHT CONTINGENCIES Note.— The texts of 15.5.1 and 15.5.2 are reproduced from Annex 11, Chapter 2, and have the status of Standards. 15.5.1 Strayed or unidentified aircraft Note 1.— The terms “strayed aircraft” and “unidentified aircraft” in this paragraph have the following meanings: Strayed aircraft. An aircraft which has deviated significantly from its intended track or which reports that it is lost. Unidentified aircraft. An aircraft which has been observed or reported to be operating in a given area but whose identity has not been established. Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-13 10/11/16 Note 2.— An aircraft may be considered, at the same time, as a “strayed aircraft” by one unit and as an “unidentified aircraft” by another unit. Note 3.— A strayed or unidentified aircraft may be suspected as being the subject of unlawful interference. See Annex 11, 2.25.1. 15.5.1.1 As soon as an air traffic services unit becomes aware of a strayed aircraft, it shall take all necessary steps as outlined in 15.5.1.1.1 and 15.5.1.1.2 to assist the aircraft and to safeguard its flight. Note.— Navigational assistance by an air traffic services unit is particularly important if the unit becomes aware of an aircraft straying, or about to stray, into an area where there is a risk of interception or other hazard to its safety. 15.5.1.1.1 If the aircraft’s position is not known, the air traffic services unit shall: a) attempt to establish two-way communication with the aircraft, unless such communication already exists; b) use all available means to determine its position; c) inform other ATS units into whose area the aircraft may have strayed or may stray, taking into account all the factors which may have affected the navigation of the aircraft in the circumstances; d) inform, in accordance with locally agreed procedures, appropriate military units and provide them with pertinent flight plan and other data concerning the strayed aircraft; e) request from the units referred to in c) and d) and from other aircraft in flight every assistance in establishing communication with the aircraft and determining its position. Note.— The requirements in d) and e) apply also to ATS units informed in accordance with c). 15.5.1.1.2 When the aircraft’s position is established, the air traffic services unit shall: a) advise the aircraft of its position and corrective action to be taken; and b) provide, as necessary, other ATS units and appropriate military units with relevant information concerning the strayed aircraft and any advice given to that aircraft. 15.5.1.2 As soon as an air traffic services unit becomes aware of an unidentified aircraft in its area, it shall endeavour to establish the identity of the aircraft whenever this is necessary for the provision of air traffic services or required by the appropriate military authorities in accordance with locally agreed procedures. To this end, the air traffic services unit shall take such of the following steps as are appropriate in the circumstances: a) attempt to establish two-way communication with the aircraft; b) inquire of other air traffic services units within the FIR about the flight and request their assistance in establishing two-way communication with the aircraft; c) inquire of air traffic services units serving the adjacent FIRs about the flight and request their assistance in establishing two-way communication with the aircraft; d) attempt to obtain information from other aircraft in the area.

    15-14 Air Traffic Management (PANS-ATM) 10/11/16 15.5.1.2.1 The air traffic services unit shall, as necessary, inform the appropriate military unit as soon as the identity of the aircraft has been established. Note.— Requirements for coordination between military authorities and air traffic services are specified in Annex 11, 2.18. 15.5.1.3 Should the ATS unit consider that a strayed or unidentified aircraft may be the subject of unlawful interference, the appropriate authority designated by the State shall immediately be informed, in accordance with locally agreed procedures. 15.5.2 Interception of civil aircraft 15.5.2.1 As soon as an air traffic services unit learns that an aircraft is being intercepted in its area of responsibility, it shall take such of the following steps as are appropriate in the circumstances: a) attempt to establish two-way communication with the intercepted aircraft via any means available, including the emergency frequency 121.5 MHz, unless such communication already exists; b) inform the pilot of the intercepted aircraft of the interception; c) establish contact with the intercept control unit maintaining two-way communication with the intercepting aircraft and provide it with available information concerning the aircraft; d) relay messages between the intercepting aircraft or the intercept control unit and the intercepted aircraft, as necessary; e) in close coordination with the intercept control unit take all necessary steps to ensure the safety of the intercepted aircraft; and f) inform ATS units serving adjacent FIRs if it appears that the aircraft has strayed from such adjacent FIRs. 15.5.2.2 As soon as an air traffic services unit learns that an aircraft is being intercepted outside its area of responsibility, it shall take such of the following steps as are appropriate in the circumstances: a) inform the ATS unit serving the airspace in which the interception is taking place, providing this unit with available information that will assist in identifying the aircraft and requesting it to take action in accordance with 15.5.2.1; b) relay messages between the intercepted aircraft and the appropriate ATS unit, the intercept control unit or the intercepting aircraft. 15.5.3 Fuel dumping 15.5.3.1 GENERAL 15.5.3.1.1 An aircraft in an emergency or other urgent situations may need to dump fuel so as to reduce to maximum landing mass in order to effect a safe landing. 15.5.3.1.2 When an aircraft operating within controlled airspace needs to dump fuel, the flight crew shall advise ATC. The ATC unit should then coordinate with the flight crew the following: Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-15 10/11/16 a) the route to be flown, which, if possible, should be clear of cities and towns, preferably over water and away from areas where thunderstorms have been reported or are expected; b) the level to be used, which should be not less than 1 800 m (6 000 ft); and c) the duration of the fuel dumping. 15.5.3.2 SEPARATION Other known traffic should be separated from the aircraft dumping fuel by: a) at least 19 km (10 NM) horizontally, but not behind the aircraft dumping fuel; b) vertical separation if behind the aircraft dumping fuel within 15 minutes flying time or a distance of 93 km (50 NM) by:

    1. at least 300 m (1 000 ft) if above the aircraft dumping fuel; and
    2. at least 900 m (3 000 ft) if below the aircraft dumping fuel. Note.— The horizontal boundaries of the area within which other traffic requires appropriate vertical separation extend for 19 km (10 NM) either side of the track flown by the aircraft which is dumping fuel, from 19 km (10 NM) ahead, to 93 km (50 NM) or 15 minutes along track behind it (including turns). 15.5.3.3 COMMUNICATIONS If the aircraft will maintain radio silence during the fuel dumping operation, the frequency to be monitored by the flight crew and the time when radio silence will terminate should be agreed. 15.5.3.4 INFORMATION TO OTHER ATS UNITS AND NON-CONTROLLED TRAFFIC 15.5.3.4.1 A warning message shall be broadcast on appropriate frequencies for non-controlled traffic to remain clear of the area concerned. Adjacent ATC units and control sectors should be informed of the fuel dumping taking place and requested to broadcast on applicable frequencies an appropriate warning message for other traffic to remain clear of the area concerned. 15.5.3.4.2 Upon completion of the fuel dumping, adjacent ATC units and control sectors should be advised that normal operations can be resumed. 15.5.4 Fuel emergency and minimum fuel Note 1.— General procedures to be applied when a pilot reports an emergency situation are contained in 15.1.1 and 15.1.2. Note 2.— Coordination procedures to be applied between transferring and accepting ATS units for flights in fuel emergency or minimum fuel situations are contained in Chapter 10, 10.2.5.

    15-16 Air Traffic Management (PANS-ATM) 10/11/16 Note 3.— The words MAYDAY FUEL describe the nature of the distress condition as required in Annex 10, Volume II, 5.3.2.1.1 b) 3. 15.5.4.1 When a pilot reports a state of minimum fuel, the controller shall inform the pilot as soon as practicable of any anticipated delays or that no delays are expected. Note.— The declaration of MINIMUM FUEL informs ATC that all planned aerodrome options have been reduced to a specific aerodrome of intended landing, and any change to the existing clearance may result in landing with less than planned final reserve fuel. This is not an emergency situation but an indication that an emergency situation is possible should any additional delay occur. 15.5.5 Descents by aircraft due to solar radiation from space weather events Air traffic control units should be prepared for the possibility that aircraft may, on rare occasions, experience a rise in solar radiation which requires them to descend to lower levels. When such a situation is known or suspected, air traffic control units should take all possible action to safeguard all aircraft concerned, including any aircraft affected by the descent. Note.— All aircraft in a particular portion of airspace and above a certain altitude may be affected at the same time, and the event may be accompanied by a deterioration or loss of air ground communications. It is expected that the aircraft will alert air traffic control units before the radiation reaches a critical level and will request a descent clearance when the critical level is reached. However, situations may occur in which the aircraft will need to descend without waiting for a clearance. In such cases, the aircraft are expected to advise air traffic control units, as soon as possible, of the emergency action taken. 15.6 ATC CONTINGENCIES The various circumstances surrounding each contingency situation preclude the establishment of exact detailed procedures to be followed. The procedures outlined below are intended as a general guide to air traffic services personnel. 15.6.1 Radiocommunications contingencies 15.6.1.1 GENERAL ATC contingencies related to communications, i.e. circumstances preventing a controller from communicating with aircraft under control, may be caused by either a failure of ground radio equipment, a failure of airborne equipment, or by the control frequency being inadvertently blocked by an aircraft transmitter. The duration of such events may be for prolonged periods and appropriate action to ensure that the safety of aircraft is not affected should therefore be taken immediately.

    8/11/18 No. 8 Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-17 10/11/16 15.6.1.2 GROUND RADIO FAILURE 15.6.1.2.1 In the event of complete failure of the ground radio equipment used for ATC, the controller shall: a) where aircraft are required to keep a listening watch on the emergency frequency 121.5 MHz, attempt to establish radiocommunications on that frequency; b) without delay inform all adjacent control positions or ATC units, as applicable, of the failure; c) appraise such positions or units of the current traffic situation; d) if practicable, request their assistance, in respect of aircraft which may establish communications with those positions or units, in establishing separation between and maintaining control of such aircraft; and e) instruct adjacent control positions or ATC units to hold or re-route all controlled flights outside the area of responsibility of the position or ATC unit that has experienced the failure until such time that the provision of normal services can be resumed. 15.6.1.2.2 In order to reduce the impact of complete ground radio equipment failure on the safety of air traffic, the appropriate ATS authority should establish contingency procedures to be followed by control positions and ATC units in the event of such failures. Where feasible and practicable, such contingency procedures should provide for the delegation of control to an adjacent control position or ATC unit in order to permit a minimum level of services to be provided as soon as possible, following the ground radio failure and until normal operations can be resumed. 15.6.1.3 BLOCKED FREQUENCY In the event that the control frequency is inadvertently blocked by an aircraft transmitter, the following additional steps should be taken: a) attempt to identify the aircraft concerned; b) if the aircraft blocking the frequency is identified, attempts should be made to establish communication with that aircraft, e.g. on the emergency frequency 121.5 MHz, by SELCAL, through the aircraft operator’s company frequency if applicable, on any VHF frequency designated for air-to-air use by flight crews or any other communication means or, if the aircraft is on the ground, by direct contact; c) if communication is established with the aircraft concerned, the flight crew shall be instructed to take immediate action to stop inadvertent transmissions on the affected control frequency. 15.6.1.4 UNAUTHORIZED USE OF ATC FREQUENCY 15.6.1.4.1 Instances of false and deceptive transmissions on ATC frequencies which may impair the safety of aircraft can occasionally occur. In the event of such occurrences, the ATC unit concerned should: a) correct any false or deceptive instructions or clearances which have been transmitted; b) advise all aircraft on the affected frequency(ies) that false and deceptive instructions or clearances are being transmitted; c) instruct all aircraft on the affected frequency(ies) to verify instructions and clearances before taking action to comply; 15-18 Air Traffic Management (PANS-ATM) 10/11/16 d) if practical, instruct aircraft to change to another frequency; and e) if possible, advise all aircraft affected when the false and deceptive instructions or clearances are no longer being transmitted. 15.6.1.4.2 Flight crews shall challenge or verify with the ATC unit concerned any instruction or clearance issued to them which they suspect may be false or deceptive. 15.6.1.4.3 When the transmission of false or deceptive instructions and clearances is detected, the appropriate authority shall take all necessary action to have the transmitter located and the transmission terminated. 15.7 OTHER ATC CONTINGENCY PROCEDURES 15.7.1 Emergency separation 15.7.1.1 If, during an emergency situation, it is not possible to ensure that the applicable horizontal separation can be maintained, emergency separation of half the applicable vertical separation minimum may be used, i.e. 150 m (500 ft) between aircraft in airspace where a vertical separation minimum of 300 m (1 000 ft) is applied, and 300 m (1 000 ft) between aircraft in airspace where a 600 m (2 000 ft) vertical separation minimum is applied. 15.7.1.2 When emergency separation is applied the flight crews concerned shall be advised that emergency separation is being applied and informed of the actual minimum used. Additionally, all flight crews concerned shall be provided with essential traffic information. 15.7.2 Short-term conflict alert (STCA) procedures Note 1.— The generation of short-term conflict alerts is a function based on surveillance data, integrated into an ATC system. The objective of the STCA function is to assist the controller in preventing collision between aircraft by generating, in a timely manner, an alert of a potential or actual infringement of separation minima. Note 2. — In the STCA function the current and predicted three-dimensional positions of aircraft with pressure-altitude reporting capability are monitored for proximity. If the distance between the three-dimensional positions of two aircraft is predicted to be reduced to less than the defined applicable separation minima within a specified time period, an acoustic and/or visual alert will be generated to the controller within whose jurisdiction area the aircraft is operating. 15.7.2.1 Local instructions concerning use of the STCA function shall specify, inter alia: a) the types of flight which are eligible for generation of alerts; b) the sectors or areas of airspace within which the STCA function is implemented; c) the method of displaying the STCA to the controller; d) in general terms, the parameters for generation of alerts as well as alert warning time; e) the volumes of airspace within which STCA can be selectively inhibited and the conditions under which this will be permitted; f) conditions under which specific alerts may be inhibited for individual flights; and Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-19 10/11/16 g) procedures applicable in respect of volume of airspace or flights for which STCA or specific alerts have been inhibited. 15.7.2.2 In the event an STCA is generated in respect of controlled flights, the controller shall without delay assess the situation and, if necessary, take action to ensure that the applicable separation minimum will not be infringed or will be restored. 15.7.2.3 Following the generation of an STCA, controllers should be required to complete an air traffic incident report only in the event that a separation minimum was infringed. 15.7.2.4 The appropriate ATS authority should retain electronic records of all alerts generated. The data and circumstances pertaining to each alert should be analysed to determine whether an alert was justified or not. Non-justified alerts, e.g. when visual separation was applied, should be ignored. A statistical analysis should be made of justified alerts in order to identify possible shortcomings in airspace design and ATC procedures as well as to monitor overall safety levels. 15.7.3 Procedures in regard to aircraft equipped with airborne collision avoidance systems (ACAS) 15.7.3.1 The procedures to be applied for the provision of air traffic services to aircraft equipped with ACAS shall be identical to those applicable to non-ACAS equipped aircraft. In particular, the prevention of collisions, the establishment of appropriate separation and the information which might be provided in relation to conflicting traffic and to possible avoiding action shall conform with the normal ATS procedures and shall exclude consideration of aircraft capabilities dependent on ACAS equipment. 15.7.3.2 When a pilot reports an ACAS resolution advisory (RA), the controller shall not attempt to modify the aircraft flight path until the pilot reports “Clear of Conflict”. 15.7.3.3 Once an aircraft departs from its ATC clearance or instruction in compliance with an RA, or a pilot reports an RA, the controller ceases to be responsible for providing separation between that aircraft and any other aircraft affected as a direct consequence of the manoeuvre induced by the RA. The controller shall resume responsibility for providing separation for all the affected aircraft when: a) the controller acknowledges a report from the flight crew that the aircraft has resumed the current clearance; or b) the controller acknowledges a report from the flight crew that the aircraft is resuming the current clearance and issues an alternative clearance which is acknowledged by the flight crew. Note.— Pilots are required to report RAs which require a deviation from the current ATC clearance or instruction (see PANS-OPS (Doc 8168), Volume I, Part III, Section 3, Chapter 3, 3.2 c) 4)). This report informs the controller that a deviation from clearance or instruction is taking place in response to an ACAS RA. 15.7.3.4 Guidance on training of air traffic controllers in the application of ACAS events is contained in the Airborne Collision Avoidance System (ACAS) Manual (Doc 9863). 15.7.3.5 ACAS can have a significant effect on ATC. Therefore, the performance of ACAS in the ATC environment should be monitored. 15.7.3.6 Following a significant ACAS event, pilots and controllers should complete an air traffic incident report. Note 1.— The ACAS capability of an aircraft may not be known to air traffic controllers. 15-20 Air Traffic Management (PANS-ATM) 10/11/16 Note 2.— Operating procedures for use of ACAS are contained in PANS-OPS (Doc 8168), Volume I, Part III, Section 3, Chapter 3. Note 3.— The phraseology to be used by controllers and pilots is contained in Chapter 12, 12.3.1.2. 15.7.4 Minimum safe altitude warning (MSAW) procedures Note 1.— The generation of minimum safe altitude warnings is a function of an ATC radar data-processing system. The objective of the MSAW function is to assist in the prevention of controlled flight into terrain accidents by generating, in a timely manner, a warning of the possible infringement of a minimum safe altitude. Note 2.— In the MSAW function, the reported levels from aircraft with pressure-altitude reporting capability are monitored against defined minimum safe altitudes. When the level of an aircraft is detected or predicted to be less than the applicable minimum safe altitude, an acoustic and visual warning will be generated to the controller within whose jurisdiction area the aircraft is operating. 15.7.4.1 Local instructions concerning use of the MSAW function shall specify, inter alia: a) the types of flight which are eligible for generation of MSAW; b) the sectors or areas of airspace for which MSAW minimum safe altitudes have been defined and within which the MSAW function is implemented; c) the values of the defined MSAW minimum safe altitudes; d) the method of displaying the MSAW to the controller; e) the parameters for generation of MSAW as well as warning time; and f) conditions under which the MSAW function may be inhibited for individual aircraft tracks as well as procedures applicable in respect of flights for which MSAW has been inhibited. 15.7.4.2 In the event an MSAW is generated in respect of a controlled flight, the following action shall be taken without delay: a) if the aircraft is being vectored, the aircraft shall be instructed to climb immediately to the applicable safe level and, if necessary to avoid terrain, be assigned a new heading; b) in other cases, the flight crew shall immediately be advised that a minimum safe altitude warning has been generated and be instructed to check the level of the aircraft. 15.7.4.3 Following an MSAW event, controllers should complete an air traffic incident report only in the event that a minimum safe altitude was unintentionally infringed with a potential for controlled flight into terrain by the aircraft concerned. 15.7.5 Autonomous runway incursion warning system (ARIWS) Note 1.— The generation of ARIWS warnings is a function based on surveillance data. The objective of the ARIWS function is to assist flight crews and vehicle drivers in the prevention of runway incursions by generating, in a timely manner, a direct warning of a possible runway hazard making it unsafe to enter, to cross a runway or to take-off Chapter 15. Procedures Related to Emergencies, Communication Failure and Contingencies 15-21 10/11/16 Note 2.— The function of ARIWS is to operate independently from ATC, and the warnings are generated for pilots and vehicle drivers. Note 3.— Annex 14, Volume I, Attachment A, Section 21, provides a description of an autonomous runway incursion warning system (ARIWS) and information on its use. 15.7.5.1 In the event an ARIWS warning is generated that conflicts with the ATC clearance, the following action shall be taken by flight crew and vehicle drivers: a) the flight crew or vehicle driver shall give priority to the ARIWS warning over the ATC clearance. They shall not proceed onto the runway or commence the take-off roll. The flight crew or vehicle driver shall inform the controller of the ARIWS warning and await further clearance; and b) in the event the aircraft or vehicle has initiated actions to comply with a clearance that conflicts with the warning, the flight crew or the vehicle driver shall use the warning to exercise their best judgement and full authority in the choice of the best course of action to resolve any potential conflict. The controller should be informed, when practicable, of the ARIWS warning. 15.7.5.2 ATS units shall have procedures in place for situations when controllers are informed of ARIWS warnings, including how to disable the ARIWS in case of malfunctions. 15.7.6 Change of radiotelephony call sign for aircraft 15.7.6.1 An ATC unit may instruct an aircraft to change its type of RTF call sign, in the interests of safety, when similarity between two or more aircraft RTF call signs are such that confusion is likely to occur. 15.7.6.1.1 Any such change to the type of call sign shall be temporary and shall be applicable only within the airspace(s) where the confusion is likely to occur. 15.7.6.2 To avoid confusion, the ATC unit should, if appropriate, identify the aircraft which will be instructed to change its call sign by referring to its position and/or level. 15.7.6.3 When an ATC unit changes the type of call sign of an aircraft, that unit shall ensure that the aircraft reverts to the call sign indicated by the flight plan when the aircraft is transferred to another ATC unit, except when the call sign change has been coordinated between the two ATC units concerned. 15.7.6.4 The appropriate ATC unit shall advise the aircraft concerned when it is to revert to the call sign indicated by the flight plan. 15.8 PROCEDURES FOR ATS UNITS WHEN A VOLCANIC ASH CLOUD IS REPORTED OR FORECAST 15.8.1 If a volcanic ash cloud is reported or forecast in the airspace for which the ATS unit is responsible, the following actions should be taken: a) relay pertinent information immediately to flight crews whose aircraft could be affected to ensure that they are aware of the ash cloud’s current and forecast position and the flight levels affected; b) accommodate requests for re-routing or level changes to the extent practicable; 15-22 Air Traffic Management (PANS-ATM) 10/11/16 c) suggest re-routing to avoid or exit areas of reported or forecast ash clouds when requested by the pilot or deemed necessary by the controller; and d) when practicable, request a special air-report when the route of flight takes the aircraft into or near the forecast ash cloud and provide such special air-reports to the appropriate agencies. Note 1.— Experience has shown that the recommended escape manoeuvre for an aircraft which has encountered an ash cloud is to reverse its course and begin a descent if terrain permits. The final responsibility for this decision, however, rests with the pilot-in-command as specified in the Manual on Volcanic Ash, Radioactive Material and Toxic Chemical Clouds (Doc 9691), 5.2.4.1. Note 2.— The final authority as to the disposition of the aircraft, whether to avoid or proceed through a reported or forecast ash cloud, rests with the pilot-in-command, as prescribed in Annex 2, 2.4. 15.8.2 When the flight crew advises the ATS unit that the aircraft has inadvertently entered a volcanic ash cloud, the ATS unit should: a) take such action applicable to an aircraft in an emergency situation; and b) initiate modifications of route or level assigned only when requested by the pilot or necessitated by airspace requirements or traffic conditions. Note 1.— General procedures to be applied when a pilot reports an emergency situation are contained in Chapter 15, 15.1.1 and 15.1.2. Note 2.— Guidance material concerning the effect of volcanic ash and the impact of volcanic ash on aviation operational and support services is provided in Chapters 4 and 5 of Doc 9691.

  4. Assistant

    To enhance Module 2: Emergency Procedures/Priority, the following information from Doc 4444 (PANS-ATM) offers valuable procedures related to emergencies, communication failure, and contingencies. This integration underscores the importance of a coordinated approach between the flight crew and Air Traffic Services (ATS) personnel during emergencies.

    2.1 Establishing Priorities in Emergencies (Reinforced with Doc 4444)

    Overview:

    The protocols established in Doc 4444 highlight that emergencies cannot be handled with one-size-fits-all procedures due to their variable nature. Instead, the guidelines serve as a general framework for ATS personnel.

    Emergency Declaration:

    • Emergency Procedures (Doc 4444, 15.1.1.2):
      • Upon declaration of an emergency, ATS must quickly ascertain the aircraft's identification, type, nature of the emergency, intentions of the flight crew, and current position and altitude.
      • Assist the flight crew by providing necessary information such as weather conditions, nearest aerodromes, and safe altitudes.

    Priority Handling:

    • Priority (Doc 4444, 15.1.2):
      • An aircraft believed to be in a state of emergency must take precedence over all other air traffic. This ensures that emergency situations are addressed promptly and with necessary resources.

    2.2 Crew Coordination and Communication (Reinforced with Doc 4444)

    Overview:

    Effective communication between the cockpit and ATS is essential, especially during an emergency. Doc 4444 provides detailed procedures on how ATS should engage with aircraft in distress.

    Communication Protocols:

    • Two-Way Communication (Doc 4444, 15.3.1):

      • ATS should verify if a lost communication situation has occurred by requesting the aircraft to perform specific maneuvers or to acknowledge signals. If communication is not established, assume the aircraft is operational and maintain separation with other air traffic based on predefined procedures.
    • Emergency Communication (Doc 4444, 15.4.1):

      • Controllers must handle VFR flights as emergencies if they report being lost or uncertain of their position, ensuring clear and calm instructions without placing blame on the flight crew.

    2.3 Case Studies (Reinforced with Doc 4444)

    Overview:

    Real-life case studies provide a unique opportunity to explore the effectiveness of emergency procedures while learning from actual events. Insights from Doc 4444 strengthen our understanding of coordinated responses during emergencies.

    Real-Life Application:

    • Unlawful Interference (Doc 4444, 15.1.3):

      • Recognize indications of unlawful interference and prepare ATS personnel to provide critical information and initiate necessary safety procedures, including updating all relevant authorities.
    • Emergency Response to Aircraft Emergencies (Doc 4444, 15.5):

      • Elaborates on emergency responses to strayed or unidentified aircraft, emphasizing the need for coordinated action between different ATS units and military authorities when necessary.

    Conclusion:

    Integrating the guidance from Doc 4444 into Module 2 reinforces the necessity for a structured yet flexible approach to emergency procedures and priorities in aviation. This module aims to enhance the collaboration between flight crews and Air Traffic Services to ensure the safety and efficiency of emergency responses, minimizing risks to passengers and crew during critical situations. This comprehensive understanding of both procedural frameworks and real-life case studies prepares participants for effective decision-making and communication in emergencies.

  5. User

    list all emergencies from document 4444

  6. Assistant

    The emergencies outlined in Doc 4444 (PANS-ATM) include various scenarios that pilots and Air Traffic Services (ATS) personnel must be prepared to handle. Here is a detailed list of emergencies referenced in the document:

    1. General Emergency Situations:

      • Any situation that threatens the safety of the aircraft, passengers, or crew.
    2. Loss of Communication:

      • Situations where the aircraft is unable to maintain two-way communication with ATS.
    3. Unlawful Interference:

      • Instances where an aircraft is subject to unlawful interference (e.g., hijacking or threats on board).
    4. Bomb Threat:

      • Situations involving credible threats of an explosive device on board the aircraft.
    5. Emergency Descent:

      • Events necessitating an emergency descent due to rapid decompression, fire, or other immediate threats.
    6. Fuel Emergency:

      • Scenarios where the aircraft is approaching critical fuel levels or needs to dump fuel for safe landing.
    7. Strayed Aircraft:

      • An aircraft deviating significantly from its intended route or reporting it is lost.
    8. VFR Flights Encountering Adverse Weather:

      • Visual Flight Rules (VFR) flights facing difficulties due to poor weather conditions.
    9. Navigation Failure:

      • Loss of navigation capabilities essential for safe operations.
    10. Inability to Comply with ATC Clearance:

      • Aircraft unable to follow assigned clearances due to operational issues, such as bad weather.
    11. Emergency Landing or Diversion:

      • Situations where an aircraft must divert or make an emergency landing.
    12. Fuel Dumping Operations:

      • Procedures relating to fuel dumping to reduce landing weight.
    13. Emergency Separation:

      • Applying reduced separation minima between aircraft during emergencies.
    14. In-flight Medical Emergencies:

      • Situations requiring immediate medical assistance for onboard personnel or passengers.
    15. Emergency Equipment Malfunction:

      • Failures of essential aircraft systems that necessitate immediate attention.

    This list highlights the diverse range of emergencies that aviation personnel may encounter, and underscores the need for comprehensive training and preparedness to respond effectively to all types of emergencies as detailed in Doc 4444.

  7. User

    2.4 Case Studies Overview: Real-life case studies provide valuable insights into how emergencies are managed and the effectiveness of established procedures. Analyzing these cases helps reinforce the importance of proper training, coordination, and decision-making. Case Study 1: Miracle on the Hudson (2009) Incident: US Airways Flight 1549 struck a flock of geese shortly after takeoff, leading to a dual engine failure. Response: Captain Chesley "Sully" Sullenberger and First Officer Jeffrey Skiles successfully ditched the aircraft in the Hudson River. Key Lessons: Quick Decision-Making: The decision to land on the river was made within minutes, showcasing the importance of assessing the situation quickly. Crew Coordination: The crew maintained clear communication and executed their roles effectively under immense pressure. Preparation: Prior CRM training and adherence to SOPs contributed to the successful outcome. Case Study 2: British Airways Flight 38 (2008) Incident: The aircraft suffered a dual engine failure on final approach due to fuel starvation caused by ice crystals. Response: The crew managed to glide the aircraft onto the runway at Heathrow Airport, avoiding a catastrophic crash. Key Lessons: Handling the Unexpected: The crew's ability to maintain control and prioritize a safe landing despite unexpected circumstances was crucial. Post-Incident Analysis: The investigation led to changes in procedures for dealing with fuel-related issues in cold conditions. Case Study 3: Air Transat Flight 236 (2001) Incident: The aircraft experienced a complete fuel exhaustion over the Atlantic Ocean, requiring an emergency glide to the Azores. Response: The crew successfully glided the aircraft for 19 minutes and landed safely. Key Lessons: Emergency Preparedness: The crew's training in fuel management and emergency gliding techniques was instrumental in saving all onboard. Effective Communication: Coordination between the flight crew and ATC was essential in managing the situation and finding a safe landing spot.

    reinfore with information from 444

  8. Assistant

    To reinforce the case studies with relevant information from Doc 4444 (PANS-ATM), which outlines recommended procedures and best practices for managing aviation emergencies, the following details can be integrated into each case analysis.

    2.4 Case Studies

    Overview:

    Real-life case studies provide valuable insights into how emergencies are managed and highlight the effectiveness of established procedures. Analyzing these cases helps reinforce the importance of proper training, coordination, and decision-making, as supported by the guidelines in Doc 4444.


    Case Study 1: Miracle on the Hudson (2009)

    • Incident: US Airways Flight 1549 struck a flock of geese shortly after takeoff, leading to dual engine failure.
    • Response: Captain Chesley "Sully" Sullenberger and First Officer Jeffrey Skiles successfully ditched the aircraft in the Hudson River.

    Key Lessons:

    • Quick Decision-Making: The decision to land on the river was made within minutes, emphasizing the need for rapid assessment of emergency situations as outlined in Doc 4444, 15.1.1.2, which stresses the importance of quick identification of the emergency type and intentions of the flight crew.
    • Crew Coordination: The crew’s effective communication under pressure aligns with Doc 4444's emphasis on closed-loop communication, ensuring all instructions and acknowledgments are confirmed to facilitate a cohesive response during emergencies.
    • Preparation: Prior CRM training and adherence to SOPs greatly contributed to the successful outcome. Doc 4444 underscores the relevance of CRM, highlighting its role in fostering teamwork and situational awareness in emergency management.

    Case Study 2: British Airways Flight 38 (2008)

    • Incident: The aircraft suffered a dual engine failure on final approach due to fuel starvation caused by ice crystals.
    • Response: The crew managed to glide the aircraft onto the runway at Heathrow Airport, avoiding a catastrophic crash.

    Key Lessons:

    • Handling the Unexpected: The crew’s ability to maintain control and prioritize a safe landing resonates with Doc 4444, 15.1.1.2(b), which suggests that recognizing the type of emergency and determining the most appropriate assistance is crucial for successful resolution.
    • Post-Incident Analysis: The investigation led to procedural changes regarding fuel-related issues in cold conditions. This aligns with the lessons learned aspect of Doc 4444, 15.1.1.1, which advocates for continuous improvement based on past incident analyses to enhance procedures and training.

    Case Study 3: Air Transat Flight 236 (2001)

    • Incident: The aircraft experienced complete fuel exhaustion over the Atlantic Ocean, requiring an emergency glide to the Azores.
    • Response: The crew successfully glided the aircraft for 19 minutes and landed safely.

    Key Lessons:

    • Emergency Preparedness: The crew's training in fuel management and emergency gliding techniques was instrumental in saving all onboard. This reflects Doc 4444's mandate on preparedness, stating that ATS must assist crews in emergencies, ensuring they have information regarding aerodromes and weather conditions (Doc 4444, 15.1.1.2(d)).
    • Effective Communication: Coordination between the flight crew and ATS was essential in managing the situation and identifying a safe landing spot. This is supported by Doc 4444, 15.1.3.3, which requires ATS to provide continual and relevant information to the flight crew during emergencies.

    These enhancements to the case studies using Doc 4444 not only substantiate the lessons learned but also underscore the importance of established procedures and effective communication in navigating aviation emergencies successfully. This integration encourages a comprehensive understanding of how both real-life incidents and regulatory guidelines can work together to improve safety outcomes in the aviation sector.