Chapter 10. Emergencies

  • Views Views: 2,357
  • Last updated Last updated:

Navigation

   Appendices
         1−1−14. DISTRIBUTION
         1−1−2. AUDIENCE
         1−1−7. DELIVERY DATES
         1−2−1. WORD MEANINGS
         1−2−2. COURSE DEFINITIONS
         1−2−3. NOTES
         1−2−4. REFERENCES
         1−2−5. ANNOTATIONS
         1−2−6. ABBREVIATIONS
      Section 1. General
         10-1-2. OBTAINING INFORMATION
         10-1-3. PROVIDING ASSISTANCE
         10-1-4. RESPONSIBILITY
         10-1-5. COORDINATION
         10-2-11. AIRCRAFT BOMB THREATS
         10-2-13. MANPADS ALERT
         10-2-18. VOLCANIC ASH
         10-2-2. FREQUENCY CHANGES
         10-2-3. AIRCRAFT ORIENTATION
         10-2-5. EMERGENCY SITUATIONS
         10-2-6. HIJACKED AIRCRAFT
         10-3-4. ALNOT
         10-3-7. ALNOT CANCELLATION
         10-4-1. TRAFFIC RESTRICTIONS
         10-4-2. LIGHTING REQUIREMENTS
         10-4-3. TRAFFIC RESUMPTION
         10-4-4. COMMUNICATIONS FAILURE
         10-5-1. EXPLOSIVE CARGO
         10-6-1. APPLICATION
         10-6-2. PHASES OF EMERGENCY
         10-6-4. INFLIGHT CONTINGENCIES
         10-7-1. INFORMATION RELAY
         10-7-2. IFR AND SVFR MINIMA
         10-7-3. VFR MINIMA
         10-7-4. SMOKE COLUMN AVOIDANCE
         10-7-5. EXTENDED NOTIFICATION
      Section 1. General
         11-1-1. DUTY RESPONSIBILITY
         12-1-1. APPLICATION
         12-1-3. ONE THOUSAND-ON-TOP
         12-1-4. SEPARATION
         12-1-6. PARACHUTE JUMPING
         12-1-7. SPECIAL VFR (SVFR)
         13-1-1. DESCRIPTION
         13-1-11. DELAY REPORTING
         13-1-12. OVERDUE AIRCRAFT
         13-1-14. FORECAST WINDS
         13-1-3. TRIAL PLANNING
         13-1-7. HOLDING
         13-2-1. DESCRIPTION
         13-2-3. INFORMATION MANAGEMENT
         13-2-5. COORDINATION
      Section 1. General
         2-1-1. ATC SERVICE
         2-1-10. NAVAID MALFUNCTIONS
         2-1-11. USE OF MARSA
         2-1-12. MILITARY PROCEDURES
         2-1-13. FORMATION FLIGHTS
         2-1-15. CONTROL TRANSFER
         2-1-16. SURFACE AREAS
         2-1-17. RADIO COMMUNICATIONS
         2-1-18. OPERATIONAL REQUESTS
         2-1-19. WAKE TURBULENCE
         2-1-2. DUTY PRIORITY
         2-1-21. TRAFFIC ADVISORIES
         2-1-25. WHEELS DOWN CHECK
         2-1-29. RVSM OPERATIONS
         2-1-3. PROCEDURAL PREFERENCE
         2-1-4. OPERATIONAL PRIORITY
         2-1-5. EXPEDITIOUS COMPLIANCE
         2-1-6. SAFETY ALERT
         2-1-8. MINIMUM FUEL
         2-2-1. RECORDING INFORMATION
         2-2-2. FORWARDING INFORMATION
         2-2-3. FORWARDING VFR DATA
         2-2-8. ALTRV INFORMATION
         2-3-1. GENERAL
         2-3-10. CONTROL SYMBOLOGY
         2-3-2. EN ROUTE DATA ENTRIES
         2-3-3. OCEANIC DATA ENTRIES
         2-3-4. TERMINAL DATA ENTRIES
         2-3-5. AIRCRAFT IDENTITY
         2-3-6. AIRCRAFT TYPE
         2-3-9. CLEARANCE STATUS
         2-4-1. RADIO COMMUNICATIONS
         2-4-11. PRIORITY INTERRUPTION
         2-4-14. WORDS AND PHRASES
         2-4-15. EMPHASIS FOR CLARITY
         2-4-16. ICAO PHONETICS
         2-4-17. NUMBERS USAGE
         2-4-18. NUMBER CLARIFICATION
         2-4-2. MONITORING
         2-4-22. AIRSPACE CLASSES
         2-4-7. AUTHORIZED RELAYS
         2-4-8. RADIO MESSAGE FORMAT
         2-5-2. NAVAID TERMS
         2-5-3. NAVAID FIXES
         2-6-1. FAMILIARIZATION
         2-7-1. CURRENT SETTINGS
         2-8-1. FURNISH RVR VALUES
         2-8-3. TERMINOLOGY
         2-9-1. APPLICATION
         2-9-2. OPERATING PROCEDURES
         2-9-3. CONTENT
      Section 1. General
         3-1-1. PROVIDE SERVICE
         3-1-10. OBSERVED ABNORMALITIES
         3-1-2. PREVENTIVE CONTROL
         3-1-3. USE OF ACTIVE RUNWAYS
         3-1-6. TRAFFIC INFORMATION
         3-1-7. POSITION DETERMINATION
         3-10-1. LANDING INFORMATION
         3-10-11. CLOSED TRAFFIC
         3-10-12. OVERHEAD MANEUVER
         3-10-3. SAME RUNWAY SEPARATION
         3-10-5. LANDING CLEARANCE
         3-10-9. RUNWAY EXITING
         3-12-1. APPLICATION
         3-12-2. DEPARTURE SEPARATION
         3-12-3. ARRIVAL SEPARATION
         3-2-1. LIGHT SIGNALS
         3-2-2. WARNING SIGNAL
         3-3-1. LANDING AREA CONDITION
         3-3-3. TIMELY INFORMATION
         3-3-4. BRAKING ACTION
         3-4-1. EMERGENCY LIGHTING
         3-4-10. RUNWAY EDGE LIGHTS
         3-4-16. TAXIWAY LIGHTS
         3-4-17. OBSTRUCTION LIGHTS
         3-4-18. ROTATING BEACON
         3-4-5. APPROACH LIGHTS
         3-4-6. ALS INTENSITY SETTINGS
         3-4-8. MALSR/ODALS
         3-4-9. ALSF-2/SSALR
         3-5-1. SELECTION
         3-5-2. STOL RUNWAYS
         3-5-3. TAILWIND COMPONENTS
         3-6-1. EQUIPMENT USAGE
         3-6-2. IDENTIFICATION
         3-6-3. INFORMATION USAGE
         3-6-5. RADAR-ONLY MODE
         3-7-1. GROUND TRAFFIC MOVEMENT
         3-7-3. GROUND OPERATIONS
         3-7-4. RUNWAY PROXIMITY
         3-9-1. DEPARTURE INFORMATION
         3-9-10. TAKEOFF CLEARANCE
         3-9-4. LINE UP AND WAIT (LUAW)
         3-9-5. ANTICIPATING SEPARATION
         3-9-6. SAME RUNWAY SEPARATION
         4-1-2. EXCEPTIONS
         4-1-3. CROSSING ALTITUDE
         4-1-4. VFR-ON-TOP
         4-1-5. FIX USE
      Section 2. Clearances
         4-2-1. CLEARANCE ITEMS
         4-2-2. CLEARANCE PREFIX
         4-2-3. DELIVERY INSTRUCTIONS
         4-2-4. CLEARANCE RELAY
         4-2-6. THROUGH CLEARANCES
         4-2-7. ALTRV CLEARANCE
         4-2-9. CLEARANCE ITEMS
         4-3-1. DEPARTURE TERMINOLOGY
         4-3-2. DEPARTURE CLEARANCES
         4-3-5. GROUND STOP
         4-3-6. DELAY SEQUENCING
         4-4-1. ROUTE USE
         4-4-4. ALTERNATIVE ROUTES
         4-4-5. CLASS G AIRSPACE
         4-4-6. DIRECT CLEARANCES
         4-5-2. FLIGHT DIRECTION
         4-5-3. EXCEPTIONS
         4-5-7. ALTITUDE INFORMATION
         4-6-2. CLEARANCE BEYOND FIX
         4-6-3. DELAYS
         4-6-4. HOLDING INSTRUCTIONS
         4-6-5. VISUAL HOLDING POINTS
         4-6-7. UNMONITORED NAVAIDs
         4-7-1. CLEARANCE INFORMATION
         4-7-10. APPROACH INFORMATION
         4-7-12. AIRPORT CONDITIONS
         4-7-13. SWITCHING ILS RUNWAYS
         4-7-6. ARRIVAL INFORMATION
         4-7-7. WEATHER INFORMATION
         4-8-1. APPROACH CLEARANCE
         4-8-10. APPROACH INFORMATION
         4-8-11. PRACTICE APPROACHES
         4-8-2. CLEARANCE LIMIT
         4-8-5. SPECIFYING ALTITUDE
         4-8-6. CIRCLING APPROACH
         4-8-7. SIDE-STEP MANEUVER
         4-8-8. COMMUNICATIONS RELEASE
         4-8-9. MISSED APPROACH
      Section 1. General
         5-1-6. DEVIATION ADVISORIES
         5-1-7. MANUAL FIX POSTING
         5-1-8. POSITION REPORTING
         5-10-1. APPLICATION
         5-10-11. MISSED APPROACH
         5-10-13. TOWER CLEARANCE
         5-10-2. APPROACH INFORMATION
         5-10-3. NO-GYRO APPROACH
         5-10-4. LOST COMMUNICATIONS
         5-10-5. RADAR CONTACT LOST
         5-10-6. LANDING CHECK
         5-10-7. POSITION INFORMATION
         5-10-9. COMMUNICATIONS CHECK
         5-11-1. ALTITUDE INFORMATION
         5-11-3. DESCENT NOTIFICATION
         5-11-4. DESCENT INSTRUCTIONS
         5-12-10. ELEVATION FAILURE
         5-12-11. SURVEILLANCE UNUSABLE
         5-12-3. DESCENT INSTRUCTION
         5-12-6. DECISION HEIGHT
         5-12-7. POSITION ADVISORIES
         5-12-9. COMMUNICATION TRANSFER
         5-13-6. SECTOR ELIGIBILITY
         5-13-7. COAST TRACKS
         5-14-1. APPLICATION
         5-14-2. RESPONSIBILITY
         5-14-3. FUNCTIONAL USE
         5-14-4. SYSTEM REQUIREMENTS
         5-14-5. INFORMATION DISPLAYED
         5-14-6. CA/MCI
         5-14-8. TRACK SUSPEND FUNCTION
         5-2-1. ASSIGNMENT CRITERIA
         5-2-10. STANDBY OPERATION
         5-2-11. CODE MONITOR
         5-2-20. BEACON TERMINATION
         5-2-21. ALTITUDE FILTERS
         5-2-23. ADS-B ALERTS
         5-2-4. RADIO FAILURE
         5-2-7. VFR CODE ASSIGNMENTS
         5-3-1. APPLICATION
         5-3-6. POSITION INFORMATION
         5-3-7. IDENTIFICATION STATUS
         5-3-8. DATA BLOCKS
         5-3-9. DATA BLOCKS
         5-4-1. APPLICATION
         5-4-2. TERMS
         5-4-3. METHODS
         5-4-4. TRAFFIC
         5-4-7. POINT OUT
         5-5-1. APPLICATION
         5-5-10. ADJACENT AIRSPACE
         5-5-11. EDGE OF SCOPE
         5-5-2. TARGET SEPARATION
         5-5-3. TARGET RESOLUTION
         5-5-4. MINIMA
         5-5-5. VERTICAL APPLICATION
         5-5-6. EXCEPTIONS
         5-5-7. PASSING OR DIVERGING
      Section 6. Vectoring
         5-6-1. APPLICATION
         5-6-2. METHODS
         5-7-1. APPLICATION
         5-7-2. METHODS
         5-7-3. SPEED ASSIGNMENTS
         5-7-4. TERMINATION
         5-8-1. PROCEDURES
         5-8-2. INITIAL HEADING
         5-8-4. DEPARTURE AND ARRIVAL
         5-9-11. TRANSITIONAL PROCEDURE
         5-9-4. ARRIVAL INSTRUCTIONS
      Section 1. General
         6-1-1. DISTANCE
         6-1-5. ARRIVAL MINIMA
         6-2-2. MINIMA ON SAME COURSE
         6-3-1. SEPARATION MINIMA
         6-4-1. APPLICATION
         6-4-4. SEPARATION BY PILOTS
         6-5-1. SEPARATION METHODS
         6-5-1. SEPARATION METHODS
         6-5-3. DME ARC MINIMA
         6-6-1. APPLICATION
         6-6-2. EXCEPTIONS
         6-6-3. SEPARATION BY PILOTS
         6-7-1. APPLICATION
         6-7-2. APPROACH SEQUENCE
         6-7-3. SEQUENCE INTERRUPTION
         6-7-5. INTERVAL MINIMA
         6-7-6. TIME CHECK
         6-7-7. MISSED APPROACHES
      Section 1. General
         7-1-2. VFR CONDITIONS
         7-2-1. VISUAL SEPARATION
      Section 3. VFR-On-Top
         7-3-1. VFR-ON-TOP
      Section 4. Approaches
         7-4-1. VISUAL APPROACH
         7-4-7. CONTACT APPROACH
         7-5-1. AUTHORIZATION
         7-5-2. PRIORITY
         7-5-3. SEPARATION
         7-5-4. ALTITUDE ASSIGNMENT
         7-5-5. LOCAL OPERATIONS
         7-5-6. CLIMB TO VFR
         7-6-1. APPLICATION
         7-6-11. TERMINATION OF SERVICE
         7-6-2. SERVICE AVAILABILITY
         7-6-3. INITIAL CONTACT
         7-6-4. IDENTIFICATION
         7-6-5. HOLDING
         7-6-6. APPROACH SEQUENCE
         7-6-7. SEQUENCING
         7-6-8. CONTROL TRANSFER
         7-6-9. ABANDONED APPROACH
         7-7-1. APPLICATION
         7-7-2. ISSUANCE OF EFC
         7-7-3. SEPARATION
         7-7-4. HELICOPTER TRAFFIC
         7-7-5. ALTITUDE ASSIGNMENTS
         7-7-6. APPROACH INTERVAL
         7-8-1. APPLICATION
         7-8-2. CLASS C SERVICES
         7-8-3. SEPARATION
         7-8-5. ALTITUDE ASSIGNMENTS
         7-8-6. EXCEPTIONS
         7-8-8. TERMINATION OF SERVICE
         7-9-1. APPLICATION
         7-9-3. METHODS
         7-9-4. SEPARATION
         7-9-5. TRAFFIC ADVISORIES
         7-9-6. HELICOPTER TRAFFIC
         7-9-7. ALTITUDE ASSIGNMENTS
         7-9-8. APPROACH INTERVAL
      Section 1. General
         8-1-1. ATC SERVICE
         8-1-3. VFR FLIGHT PLANS
         8-1-4. TYPES OF SEPARATION
         8-1-5. ALTIMETER SETTING
         8-1-9. RVSM OPERATIONS
         8-10-1. APPLICATION
         8-10-2. VERTICAL SEPARATION
         8-10-4. LATERAL SEPARATION
         8-2-1. GENERAL
         8-3-1. APPLICATION
         8-3-2. SEPARATION METHODS
         8-3-3. MACH NUMBER TECHNIQUE
         8-4-1. APPLICATION
         8-4-2. SEPARATION METHODS
         8-4-4. TRACK SEPARATION
         8-5-2. COURSE DIVERGENCE
         8-5-3. OPPOSITE DIRECTION
         8-5-4. SAME DIRECTION
         8-7-1. APPLICATION
         8-7-2. VERTICAL SEPARATION
         8-7-3. LONGITUDINAL SEPARATION
         8-7-4. LATERAL SEPARATION
         8-8-1. APPLICATION
         8-8-2. VERTICAL SEPARATION
         8-8-3. LONGITUDINAL SEPARATION
         8-8-4. LATERAL SEPARATION
         8-8-5. VFR CLIMB AND DESCENT
         8-9-1. APPLICATION
         8-9-2. VERTICAL SEPARATION
         8-9-3. LONGITUDINAL SEPARATION
         8-9-4. LATERAL SEPARATION
      Section 1. General
         9-1-1. GENERAL
         9-1-2. SPECIAL HANDLING
         9-1-3. FLIGHT CHECK AIRCRAFT
         9-2-17. SAMP FLIGHTS
         9-2-5. FLYNET
         9-2-7. INTERCEPTOR OPERATIONS
         9-2-8. SPECIAL INTEREST SITES
         9-3-1. APPLICATION
         9-3-2. SEPARATION MINIMA
         9-3-3. VFR-ON-TOP
         9-4-2. ROUTING
         9-4-3. ALTITUDE ASSIGNMENT
         9-4-4. SEPARATION MINIMA
         9-6-1. APPLICATION
         9-6-2. DERELICT BALLOONS
         9-7-1. COORDINATION
         9-7-3. CLASS D AIRSPACE
         9-7-4. OTHER CONTROL AIRSPACE
         9-8-1. GENERAL
  • Chapter 10. Emergencies

    Section 1. General

    10-1-1. EMERGENCY DETERMINATIONS

    interpretation 10
    1. An emergency can be either a Distress or an Urgency condition as defined in the “Pilot/Controller Glossary.”
    2. A pilot who encounters a Distress condition should declare an emergency by beginning the initial communication with the word “Mayday,” preferably repeated three times. For an Urgency condition, the word “Pan-Pan” should be used in the same manner.
    3. If the words “Mayday” or “Pan-Pan” are not used but you believe an emergency or an urgent situation exists, handle it as though it were an emergency.
    4. Because of the infinite variety of possible emergency situations, specific procedures cannot be prescribed. However, when you believe an emergency exists or is imminent, select and pursue a course of action which appears to be most appropriate under the circumstances and which most nearly conforms to the instructions in this manual.

    10-1-2. OBTAINING INFORMATION

    1. Use the information provided or solicit more information as necessary to assist the distressed aircraft. Provide assistance that is consistent with the requests of the pilot. If you believe an alternative course of action may prove more beneficial, transmit your recommendation(s) to the pilot.
      • REFERENCE
      • 14 CFR § 91.3 Responsibilities and authority of pilot in command.
    2. If an emergency was declared by an Emergency Autoland system, the aircraft may transmit the following:
      1. Callsign.
      2. That Emergency Autoland has been activated.
      3. Position (mileage and direction) relative to a nearby airport.
      4. The intended emergency landing airport and the planned landing runway.
      5. An ETE to the emergency landing airport.
      • EXAMPLE
      • “Aircraft, N123B, pilot incapacitation, 12 miles southwest of KOJC, landing KIXD airport. Emergency Autoland in 13 minutes on runway 36.”
      • NOTE:
      • 1. System configurations may vary between manufactur-ers. All systems should be configured to transmit enough information for the controller to respond effectively to the emergency.
      • 2. In the event of frequency congestion, an Emergency Autoland system may transmit on 121.5 or CTAF instead of the last assigned ATC frequency.

    10-1-3. PROVIDING ASSISTANCE

    Provide maximum assistance to aircraft in distress. Enlist the services of available radar facilities operated by the FAA, the military services, and the Federal Communications Commission, as well as their emergency services and facilities, when the pilot requests or when you deem necessary.

    10-1-4. RESPONSIBILITY

    1. If you are in communication with an aircraft in distress, handle the emergency and coordinate and direct the activities of assisting facilities. Transfer this responsibility to another facility only when you feel better handling of the emergency will result.
    2. When you receive information about an aircraft in distress, forward detailed data to the center in whose area the emergency exists.
      • NOTE:
      • 1. Centers serve as the central points for collecting information, for coordinating with SAR, and for conducting a communications search by distributing any necessary ALNOTs concerning:
        1. Overdue or missing IFR aircraft.
        2. Aircraft in an emergency situation occurring in their respective area.
        3. Aircraft on a combination VFR/IFR or an air-filed IFR flight plan and 30 minutes have passed since the pilot requested IFR clearance and neither communication nor radar contact can be established with it. For SAR purposes, these aircraft are treated the same as IFR aircraft.
        4. Overdue or missing aircraft which have been authorized to operate in accordance with special VFR clearances.
      • 2. Notifying the center about a VFR aircraft emergency allows provision of IFR separation if considered necessary.
    3. If the aircraft involved is operated by a foreign air carrier, notify the center serving the departure or destination point, when either point is within the U.S., for relay to the operator of the aircraft.
    4. The ARTCC must be responsible for receiving and relaying all pertinent ELT signal information to the appropriate authorities.
    5. When consideration is given to the need to escort an aircraft in distress, evaluate the close formation required by both aircraft. Special consideration should be given if the maneuver takes the aircraft through the clouds.
    6. Before a determination is made to have an aircraft in distress be escorted by another aircraft, ask the pilots if they are familiar with and capable of formation flight.
      1. Do not allow aircraft to join up in formation during emergency conditions, unless:
        1. (a) The pilots involved are familiar with and capable of formation flight.
        2. (b) They can communicate with one another, and have visual contact with each other.
      2. If there is a need for aircraft that are not designated as search and rescue aircraft to get closer to one another than radar separation standards allow, the maneuver must be accomplished, visually, by the aircraft involved.

    10-1-5. COORDINATION

    Coordinate efforts to the extent possible to assist any aircraft believed overdue, lost, or in emergency status.

    10-1-6. AIRPORT GROUND EMERGENCY

    TERMINAL

    1. When an emergency occurs on the airport proper, control other air and ground traffic to avoid conflicts in the area where the emergency is being handled. This also applies when routes within the airport proper are required for movement of local emergency equipment going to or from an emergency which occurs outside the airport proper.

      NOTE: Aircraft operated in proximity to accident or other emergency or disaster locations may cause hindrances to airborne and surface rescue or relief operations. Congestion, distraction or other effects, such as wake turbulence from nearby airplanes and helicopters, could prevent or delay proper execution of these operations.

    2. Workload permitting, monitor the progress of emergency vehicles responding to a situation. If necessary, provide available information to assist responders in finding the accident/incident scene.

    10-1-7. INFLIGHT EMERGENCIES INVOLVING MILITARY FIGHTER-TYPE AIRCRAFT

    1. The design and complexity of military fighter-type aircraft places an extremely high workload on the pilot during an inflight emergency. The pilot's full attention is required to maintain control of the aircraft. Therefore, radio frequency and transponder code changes should be avoided and radio transmissions held to a minimum, especially when the aircraft experiencing the emergency is at low altitude.
    2. Pilots of military fighter-type aircraft, normally single engine, experiencing or anticipating loss of engine power or control may execute a flameout pattern in an emergency situation. Circumstances may dictate that the pilot, depending on the position and nature of the emergency, modify the pattern based on actual emergency recovery requirements.
    3. Military airfields with an assigned flying mission may conduct practice emergency approaches. Participating units maintain specific procedures for conducting these operations.

    Section 2. Emergency Assistance

    10-2-1. INFORMATION REQUIREMENTS

    1. Start assistance as soon as enough information has been obtained upon which to act. Information requirements will vary, depending on the existing situation. Minimum required information for inflight emergencies is:

      NOTE: In the event of an ELT signal see para 10-2-10, Emergency Locator Transmitter (ELT) Signals.

      1. Aircraft identification and type.
      2. Nature of the emergency.
      3. Pilot's desires.
    2. After initiating action, obtain the following items or any other pertinent information from the pilot or aircraft operator, as necessary:
      • NOTE:
      • 1. Emergency Autoland systems may not provide all of the required information for emergencies. Use the information provided to develop an appropriate course of action to assist the aircraft.
      • 2. If an emergency has been declared by an Emergency Autoland system, transmissions to the aircraft may go unanswered.
      • 3. Normally, do not request this information from military fighter-type aircraft that are at low altitudes (for example, on approach, immediately after departure, on a low level route). However, request the position of an aircraft that is not visually sighted or displayed on radar if the location is not given by the pilot.
      1. Aircraft altitude.
      2. Fuel remaining in time.
      3. Pilot reported weather.
      4. Pilot capability for IFR flight.
      5. Time and place of last known position.
      6. Heading since last known position.
      7. Airspeed.
      8. Navigation equipment capability.
      9. NAVAID signals received.
      10. Visible landmarks.
      11. Aircraft color.
      12. Number of people on board.
      13. Point of departure and destination.
      14. Emergency equipment on board.

    10-2-2. FREQUENCY CHANGES

    Although 121.5 MHz and 243.0 MHz are emergency frequencies, it might be best to keep the aircraft on the initial contact frequency. Change frequencies only when there is a valid reason.

    10-2-3. AIRCRAFT ORIENTATION

    Orientate an aircraft by the means most appropriate to the circumstances. Recognized methods include:

    1. Radar.
    2. NAVAIDs.
    3. Pilotage.
    4. Sighting by other aircraft.

    10-2-4. ALTITUDE CHANGE FOR IMPROVED RECEPTION

    When you consider it necessary and if weather and circumstances permit, recommend that the aircraft maintain or increase altitude to improve communications or radar.

    NOTE: Aircraft with high-bypass turbofan engines (such as B747) encountering volcanic ash clouds have experienced total loss of power to all engines. Damage to engines due to volcanic ash ingestion increases as engine power is increased, therefore, climb while in the ash cloud is to be avoided where terrain permits.

    10-2-5. EMERGENCY SITUATIONS

    Consider that an aircraft emergency exists and inform the RCC or ARTCC if:

    NOTE: USAF facilities are only required to notify the ARTCC.

    1. An emergency is declared by any on the following:
      1. The pilot.
      2. Facility personnel.
      3. Officials responsible for the operation of the aircraft.
      4. A system-generated transmission from an aircraft.
    2. There is unexpected loss of radar contact and radio communications with any IFR or VFR aircraft.
    3. Reports indicate it has made a forced landing, is about to do so, or its operating efficiency is so impaired that a forced landing will be necessary.
    4. Reports indicate the crew has abandoned the aircraft or is about to do so.
    5. An emergency transponder code is displayed or reported.

      NOTE: EN ROUTE. ERAM: Code 7700 causes an emergency indicator to blink in the data block.

    6. Intercept or escort aircraft services are required.
    7. The need for ground rescue appears likely.
    8. An Emergency Locator Transmitter (ELT) signal is heard or reported.

    10-2-6. HIJACKED AIRCRAFT

    Hijack attempts or actual events are a matter of national security and require special handling. FAA Order JO 7610.4, Special Operations, describes additional procedures and reporting requirements that must be followed.

    1. When a pilot notifies ATC verbally of a hijacking situation, assign code 7500 to the subject aircraft.
      • PHRASEOLOGY
      • (Identification) SQUAWK SEVEN FIVE ZERO ZERO.
      1. Should the pilot acknowledge assignment of code 7500 without further communication, or fail to acknowledge or communicate further, assume that the flight is being subject to hijack.
      2. No reference to the hijacking must be made in subsequent communications unless initiated by the pilot, or unless directed by the Domestic Events Network (DEN) Air Traffic Security Coordinator.
      3. Immediately inform the operations manager, supervisor or CIC.

      NOTE: When an aircraft squawks code 7500, ERAM will display “HIJK,” and STARS/MEARTS will display “HJ” in the data block.

    2. When a pilot notifies ATC of a hijacking situation by squawking code 7500, use the following phraseology to verify that the aircrew intentionally selected code 7500.
      • PHRASEOLOGY
      • (Identification)(name of facility) VERIFY SQUAWKING SEVEN FIVE ZERO ZERO.
      1. Should the pilot fail to acknowledge or communicate further, assume that the flight is being subject to hijack.
      2. No reference to the hijacking must be made in subsequent communications unless initiated by the pilot, or unless directed by the DEN Air Traffic Security Coordinator.
      3. Immediately inform the operations manager, supervisor or CIC.

    10-2-7. VFR AIRCRAFT IN WEATHER DIFFICULTY

    1. If VFR aircraft requests assistance when it encounters or is about to encounter IFR weather conditions, determine the facility best able to provide service. If a frequency change is necessary, advise the pilot of the reason for the change, and request the aircraft contact the appropriate control facility. Inform that facility of the situation. If the aircraft is unable to communicate with the control facility, relay information and clearances.
    2. The following must be accomplished on a Mode C equipped VFR aircraft which is in emergency but no longer requires the assignment of Code 7700:
      1. TERMINAL. Assign a beacon code that will permit terminal minimum safe altitude warning (MSAW) alarm processing.
      2. EN ROUTE. An appropriate keyboard entry must be made to ensure en route MSAW (EMSAW) alarm processing.

    10-2-8. RADAR ASSISTANCE TO VFR AIRCRAFT IN WEATHER DIFFICULTY

    1. If a VFR aircraft requests radar assistance when it encounters or is about to encounter IFR weather conditions, ask the pilot if he/she is qualified for and capable of conducting IFR flight.
    2. If the pilot states he/she is qualified for and capable of IFR flight, request him/her to file an IFR flight plan and then issue clearance to destination airport, as appropriate.
    3. If the pilot states he/she is not qualified for or not capable of conducting IFR flight, or if he/she refuses to file an IFR flight plan, take whichever of the following actions is appropriate:
      1. Inform the pilot of airports where VFR conditions are reported, provide other available pertinent weather information, and ask if he/she will elect to conduct VFR flight to such an airport.
      2. If the action in subparagraph 1 above is not feasible or the pilot declines to conduct VFR flight to another airport, provide radar assistance if the pilot:
        1. (a) Declares an emergency.
        2. (b) Refuses to declare an emergency and you have determined the exact nature of the radar services the pilot desires.
      3. If the aircraft has already encountered IFR conditions, inform the pilot of the appropriate terrain/obstacle clearance minimum altitude. If the aircraft is below appropriate terrain/obstacle clearance minimum altitude and sufficiently accurate position information has been received or radar identification is established, furnish a heading or radial on which to climb to reach appropriate terrain/obstacle clearance minimum altitude.
    4. The following must be accomplished on a Mode C equipped VFR aircraft which is in emergency but no longer requires the assignment of Code 7700:
      1. TERMINAL. Assign a beacon code that will permit terminal minimum safe altitude warning (MSAW) alarm processing.
      2. EN ROUTE. An appropriate keyboard entry must be made to ensure en route MSAW (EMSAW) alarm processing.

    10-2-9. RADAR ASSISTANCE TECHNIQUES

    Use the following techniques to the extent possible when you provide radar assistance to a pilot not qualified to operate in IFR conditions:

    1. Avoid radio frequency changes except when necessary to provide a clear communications channel.
    2. Make turns while the aircraft is in VFR conditions so it will be in a position to fly a straight course while in IFR conditions.
    3. Have pilot lower gear and slow aircraft to approach speed while in VFR conditions.
    4. Avoid requiring a climb or descent while in a turn if in IFR conditions.
    5. Avoid abrupt maneuvers.
    6. Vector aircraft to VFR conditions.
    7. The following must be accomplished on a Mode C equipped VFR aircraft which is in emergency but no longer requires the assignment of Code 7700:
      1. TERMINAL. Assign a beacon code that will permit terminal minimum safe altitude warning (MSAW) alarm processing.
      2. EN ROUTE. An appropriate keyboard entry must be made to ensure en route MSAW (EMSAW) alarm processing.

    10-2-10. EMERGENCY LOCATOR TRANSMITTER (ELT) SIGNALS

    When an ELT signal is heard or reported:

    1. EN ROUTE. Notify the Rescue Coordination Center (RCC).

      NOTE: FAA Form 7210-8, ELT INCIDENT, contains standardized format for coordination with the RCC.

      • REFERENCE
      • FAA Order JO 7210.3, Para 9-3-1, FAA Form 7210-8, ELT Incident.
    2. TERMINAL. Notify the ARTCC which will coordinate with the RCC.
      • NOTE:
      • 1. Operational ground testing of emergency locator transmitters (ELTs) has been authorized during the first 5 minutes of each hour. To avoid confusing the tests with an actual alarm, the testing is restricted to no more than three audio sweeps.
      • 2. Controllers can expect pilots to report aircraft position and time the signal was first heard, aircraft position and time the signal was last heard, aircraft position at maximum signal strength, flight altitude, and frequency of the emergency signal (121.5/243.0). (See AIM, Para 6-2-4, Emergency Locator Transmitter (ELT).)
    3. TERMINAL. Attempt to obtain fixes or bearings on the signal.
    4. Solicit the assistance of other aircraft known to be operating in the signal area.
    5. TERMINAL. Forward fixes or bearings and any other pertinent information to the ARTCC.

      NOTE: Fix information in relation to a VOR or VORTAC (radial-distance) facilitates accurate ELT plotting by RCC and should be provided when possible.

    6. EN ROUTE. When the ELT signal strength indicates the signal may be emanating from somewhere on an airport or vicinity thereof, notify the on-site technical operations personnel and the Regional Operations Center (ROC) for their actions. This action is in addition to the above.
    7. TERMINAL. When the ELT signal strength indicates the signal may be emanating from somewhere on the airport or vicinity thereof, notify the on-site technical operations personnel and the ARTCC for their action. This action is in addition to the above.
    8. Air traffic personnel must not leave their required duty stations to locate an ELT signal source.

      NOTE: Portable hand-carried receivers assigned to air traffic facilities (where no technical operations personnel are available) may be loaned to responsible airport personnel or local authorities to assist in locating the ELT signal source.

    9. EN ROUTE. Notify the RCC and the ROC if signal source is located/terminated.
    10. TERMINAL. Notify the ARTCC if signal source is located/terminated.

    10-2-11. AIRCRAFT BOMB THREATS

    1. When information is received from any source that a bomb has been placed on, in, or near an aircraft for the purpose of damaging or destroying such aircraft, notify your supervisor or the facility air traffic manager. If the threat is general in nature, handle it as a “Suspicious Activity.” When the threat is targeted against a specific aircraft and you are in contact with the suspect aircraft, take the following actions as appropriate:
      • REFERENCE
      • FAA Order JO 7610.4, Chapter 7, Procedures for Handling Suspicious Flight Situations and Hijacked Aircraft.
      1. Advise the pilot of the threat.
      2. Inform the pilot that technical assistance can be obtained from an FAA aviation explosives expert.

        NOTE: An FAA aviation explosive expert is on call at all times and may be contacted by calling the FAA Operations Center, Washington, DC, Area Code 202-267-3333, ETN 521-0111, or DSN 851-3750. Technical advice can be relayed to assist civil or military air crews in their search for a bomb and in determining what precautionary action to take if one is found.

      3. Ask the pilot if he/she desires to climb or descend to an altitude that would equalize or reduce the outside air pressure/existing cabin air pressure differential. Issue or relay an appropriate clearance considering MEA, MOCA, MRA, and weather.

        NOTE: Equalizing existing cabin air pressure with outside air pressure is a key step which the pilot may wish to take to minimize the damage potential of a bomb.

      4. Handle the aircraft as an emergency and/or provide the most expeditious handling possible with respect to the safety of other aircraft, ground facilities, and personnel.

        NOTE: Emergency handling is discretionary and should be based on the situation. With certain types of threats, plans may call for a low-key action or response.

      5. Issue or relay clearances to a new destination if requested.
      6. When a pilot requests technical assistance or if it is apparent that a pilot may need such assistance, do NOT suggest what actions the pilot should take concerning a bomb, but obtain the following information and notify your supervisor who will contact the FAA aviation explosives expert:

        NOTE: This information is needed by the FAA aviation explosives expert so that he/she can assess the situation and make immediate recommendations to the pilot. The aviation explosives expert may not be familiar with all military aircraft configurations but he/she can offer technical assistance which would be beneficial to the pilot.

        1. (a) Type, series, and model of the aircraft.
        2. (b) Precise location/description of the bomb device if known.
        3. (c) Other details which may be pertinent.

        NOTE: The following details may be of significance if known, but it is not intended that the pilot should disturb a suspected bomb/bomb container to ascertain the information: The altitude or time set for the bomb to explode, type of detonating action (barometric, time, anti-handling, remote radio transmitter), power source (battery, electrical, mechanical), type of initiator (blasting cap, flash bulb, chemical), and the type of explosive/incendiary charge (dynamite, black powder, chemical).

    2. When a bomb threat involves an aircraft on the ground and you are in contact with the suspect aircraft, take the following actions in addition to those discussed in the preceding paragraphs which may be appropriate:
      1. If the aircraft is at an airport where tower control or FSS advisory service is not available, or if the pilot ignores the threat at any airport, recommend that takeoff be delayed until the pilot or aircraft operator establishes that a bomb is not aboard in accordance with 14 CFR Part 121. If the pilot insists on taking off and in your opinion the operation will not adversely affect other traffic, issue or relay an ATC clearance.
      2. Advise the aircraft to remain as far away from other aircraft and facilities as possible, to clear the runway, if appropriate, and to taxi to an isolated or designated search area. When it is impractical or if the pilot takes an alternative action; e.g., parking and off-loading immediately, advise other aircraft to remain clear of the suspect aircraft by at least 100 yards if able.

        NOTE: Passenger deplaning may be of paramount importance and must be considered before the aircraft is parked or moved away from service areas. The decision to use ramp facilities rests with the pilot, aircraft operator/airport manager.

    3. If you are unable to inform the suspect aircraft of a bomb threat or if you lose contact with the aircraft, advise your supervisor and relay pertinent details to other sectors or facilities as deemed necessary.
    4. When a pilot reports the discovery of a bomb or suspected bomb on an aircraft which is airborne or on the ground, determine the pilot's intentions and comply with his/her requests in so far as possible. Take all of the actions discussed in the preceding paragraphs which may be appropriate under the existing circumstances.
    5. The handling of aircraft when a hijacker has or is suspected of having a bomb requires special considerations. Be responsive to the pilot's requests and notify supervisory personnel. Apply hijacking procedures and offer assistance to the pilot according to the preceding paragraphs, if needed.

    10-2-12. EXPLOSIVE DETECTION K-9 TEAMS

    Take the following actions should you receive an aircraft request for the location of the nearest explosive detection K-9 team.

    • REFERENCE
    • FAA Order JO 7210.3, Para 2-1-12, Explosives Detection K-9 Teams.
    1. Obtain the aircraft identification and position and advise your supervisor of the pilot request.
    2. When you receive the nearest location of the explosive detection K-9 team, relay the information to the pilot.
    3. If the aircraft wishes to divert to the airport location provided, obtain an estimated arrival time from the pilot and advise your supervisor.

    10-2-13. MANPADS ALERT

    When a threat or attack from Man-Portable Air Defense Systems (MANPADS) is determined to be real, notify and advise aircraft as follows:

    1. Do not withhold landing clearance. To the extent possible, issue information on MANPADS threats, confirmed attacks, or post-event activities in time for it to be useful to the pilot. The pilot or parent company will determine the pilot's actions.
    2. MANPADS information will be disseminated via the ATIS and/or controller-to-pilot transmissions.
    3. Disseminate via controller-to-pilot transmission until the appropriate MANPADS information is broadcast via the ATIS and pilots indicate they have received the appropriate ATIS code. MANPADS information will include nature and location of threat or incident, whether reported or observed and by whom, time (if known), and when transmitting to an individual aircraft, a request for pilot's intentions.
      • PHRASEOLOGY
      • ATTENTION (aircraft identification), MANPADS ALERT. EXERCISE EXTREME CAUTION. MANPADS THREAT/ ATTACK/POST-EVENT ACTIVITY OBSERVED/ REPORTED BY (reporting agency) (location) AT (time, if known). (When transmitting to an individual aircraft) SAY INTENTIONS.
      • EXAMPLE
      • “Attention Eastern Four Seventeen, MANPADS alert. Exercise extreme caution. MANPADS threat reported by TSA, La Guardia vicinity. Say intentions.”
      • “Attention all aircraft, MANPADS alert. Exercise extreme caution. MANPADS post-event activity observed by tower south of airport at two-one-zero-zero Zulu.”
    4. Report MANPADS threat/attack/post-event activity via the ATIS and/or controller-to-pilot transmissions until notified otherwise by the Domestic Events Network (DEN) Air Traffic Security Coordinator (ATSC).

    10-2-14. UNAUTHORIZED LASER ILLUMINATION OF AIRCRAFT

    1. When a laser event is reported to an air traffic facility, broadcast on all appropriate frequencies a general caution warning every five minutes for 20 minutes following the last report.
      • PHRASEOLOGY
      • UNAUTHORIZED LASER ILLUMINATION EVENT, (location), (altitude).
    2. Terminal facilities must include reported unauthorized laser illumination events on the ATIS broadcast for one hour following the last report. Include the time, location, altitude, color, and direction of the laser as reported by the pilot.

    NOTE: All personnel can expect aircrews to regard lasers as an inflight emergency and may take evasive action to avoid laser illumination. Additionally, other aircraft may request clearance to avoid the area.

    10-2-15. EMERGENCY AIRPORT RECOMMENDATION

    1. Consider the following factors when recommending an emergency airport:
      1. Remaining fuel in relation to airport distances.
      2. Weather conditions.

        NOTE: Depending on the nature of the emergency, certain weather phenomena may deserve weighted consideration when recommending an airport; e.g., a pilot may elect to fly farther to land at an airport with VFR instead of IFR conditions.

      3. Airport conditions.
      4. NAVAID status.
      5. Aircraft type.
      6. Pilot's qualifications.
      7. Vectoring or homing capability to the emergency airport.

      NOTE: In the event of an Emergency Autoland system activation, the system will select a suitable airport and advise ATC. The Emergency Autoland system does not consider closed runways, equipment on the runway, construction, or other possible airport hazards when selecting a suitable airport.

    2. Consideration to the provisions of subparagraph a and paragraph 10-2-16, Guidance to Emergency Airport, must be used in conjunction with the information derived from any automated emergency airport information source.

    10-2-16. GUIDANCE TO EMERGENCY AIRPORT

    1. When necessary, use any of the following for guidance to the airport:
      1. Radar.
      2. Following another aircraft.
      3. NAVAIDs.
      4. Pilotage by landmarks.
      5. Compass headings.
    2. Consideration to the provisions of paragraph 10-2-15, Emergency Airport Recommendation, must be used in conjunction with the information derived from any automated emergency airport information source.

    10-2-17. EMERGENCY OBSTRUCTION VIDEO MAP (EOVM)

    1. The EOVM is intended to facilitate advisory service to an aircraft in an emergency situation wherein an appropriate terrain/obstacle clearance minimum altitude cannot be maintained. It must only be used and the service provided under the following conditions:
      1. The pilot has declared an emergency, or
      2. The controller has determined that an emergency condition exists or is imminent because of the pilot's inability to maintain an appropriate terrain/obstacle clearance minimum altitude.

        NOTE: Appropriate terrain/obstacle clearance minimum altitudes may be defined as Minimum IFR Altitude (MIA), Minimum En Route Altitude (MEA), Minimum Obstruction Clearance Altitude (MOCA), or Minimum Vectoring Altitude (MVA).

    2. When providing emergency vectoring service, the controller must advise the pilot that any headings issued are emergency advisories intended only to direct the aircraft toward and over an area of lower terrain/obstacle elevation.

      NOTE: Altitudes and obstructions depicted on the EOVM are the actual altitudes and locations of the obstacle/terrain and contain no lateral or vertical buffers for obstruction clearance.

    • REFERENCE
    • FAA Order JO 7210.3, Para 3-8-4, Emergency Obstruction Video Map (EOVM).

    10-2-18. VOLCANIC ASH

    1. If a volcanic ash cloud is known or forecast to be present:
      1. Relay all information available to pilots to ensure that they are aware of the ash cloud's position and altitude(s).
      2. Suggest appropriate reroutes to avoid the area of known or forecast ash clouds.

      NOTE: Volcanic ash clouds are not normally detected by airborne or air traffic radar systems.

    2. If advised by an aircraft that it has entered a volcanic ash cloud and indicates that a distress situation exists:
      1. Consider the aircraft to be in an emergency situation.
      2. Do not initiate any climb clearances to turbine-powered aircraft until the aircraft has exited the ash cloud.
      3. Do not attempt to provide escape vectors without pilot concurrence.
      • NOTE:
      • 1. The recommended escape maneuver is to reverse course and begin a descent (if terrain permits). However, it is the pilot's responsibility to determine the safest escape route from the ash cloud.
      • 2. Controllers should be aware of the possibility of complete loss of power to any turbine-powered aircraft that encounters an ash cloud.

    10-2-19. REPORTING DEATH, ILLNESS, OR OTHER PUBLIC HEALTH RISK ON BOARD AIRCRAFT

    1. If an air traffic controller receives are port of the death of person, an illness, and/or other public health risk obtain the following information and notify the operations manager in charge (OMIC)/operations supervisor (OS)/controller-in-charge (CIC) as soon as possible.
      1. Call sign.
      2. Number of suspected cases of illness on board.
      3. Nature of the illnesses or other public health risk, if known.
      4. Number of persons on board.
      5. Number of deaths, if applicable.
      6. Pilot's intent (for example, continue to destination or divert).
      7. Any request for assistance (for example, needing emergency medical services to meet the aircraft at arrival).
    2. The OMIC/OS/CIC must relay the information to the DEN as soon as possible.
      • NOTE:
      • 1. If the ATC facility is not actively monitoring the DEN or does not have a dedicated line to the DEN, they must call into the DEN directly via 844-432-2962 (toll free).
      • 2. Except in extraordinary circumstances, such as a situation requiring ATC intervention, follow-on coordination regarding the incident will not involve ATC frequencies.
      • 3. The initial report to a U.S. ATC facility may be passed from a prior ATC facility along the route of flight.
    • REFERENCE
    • FAA Order JO 7210.3, Para 2-1-33, Reporting Death, Illness, or Other Public Health Risk On Board Aircraft.

    Section 3. Overdue Aircraft

    10-3-1. OVERDUE AIRCRAFT/OTHER SITUATIONS

    1. Consider an aircraft to be overdue and initiate the procedures stated in this section to issue an ALNOT when neither communications nor radar contact can be established and 30 minutes have passed since:

      NOTE: The procedures in this section also apply to an aircraft referred to as “missing” or “unreported.”

      1. Its ETA over a specified or compulsory reporting point or at a clearance limit in your area.
      2. Its clearance void time.
      3. A VFR or IFR aircraft arriving at an airport not served by an air traffic control tower or flight service station fails to cancel a flight plan after receiving instructions on how to cancel.

        NOTE: If you have reason to believe that an aircraft is overdue prior to 30 minutes, take the appropriate action immediately.

    2. Consider an aircraft to be in an emergency status and initiate ALNOT procedures in this section immediately when there is an abnormal simultaneous loss of radar and communications with an IFR aircraft or VFR/SVFR aircraft receiving flight following services. This situation may be applicable to an aircraft operating in a non-radar environment and an unexpected/abnormal loss of communications occurs.
    3. The ARTCC in whose area the aircraft is reported as overdue, missing or lost will make these determinations and takes any subsequent action required.
    4. If you have reason to believe that an aircraft is overdue prior to 30 minutes, take the appropriate action immediately.
    5. The center in whose area the aircraft is first unreported or overdue will make these determinations and takes any subsequent action required.

    10-3-2. INFORMATION TO BE FORWARDED TO ARTCC

    TERMINAL

    When an aircraft is considered to be in emergency status that may require SAR procedures, or an IFR aircraft is overdue, the terminal facility must alert the appropriate ARTCC and forward the following information, as available:

    1. Flight plan, including color of aircraft, if known.
    2. Time of last transmission received, by whom, and frequency used.
    3. Last position report and how determined.
    4. Aircraft beacon code.
    5. Number of persons on board.
    6. Fuel status.
    7. Facility working aircraft and frequency.
    8. Last known position, how determined, time, estimated present position, and maximum range of flight of the aircraft based on remaining fuel and airspeed.
    9. Position of other aircraft near aircraft's route of flight, when requested.
    10. Whether or not an ELT signal has been heard or reported in the vicinity of the last known position.
    11. Other pertinent information.

    NOTE: FSSs serve as the central points for collecting and disseminating information on an overdue or missing aircraft which is not on an IFR flight plan. Non-FSS ATC facilities that receive telephone calls or other inquiries regarding these flights must refer these calls and inquiries to the appropriate FSS.

    10-3-3. INFORMATION TO BE FORWARDED TO RCC

    EN ROUTE

    When an aircraft is considered to be in emergency status or an IFR aircraft is overdue, the ARTCC must alert the RCC and forward the following information, as available:

    1. Facility and person calling.
    2. Flight plan, including color of aircraft, if known.
    3. Time of last transmission received, by whom, and frequency used.
    4. Last position report and how determined.
    5. Aircraft beacon code.
    6. Action taken by reporting facility and proposed action.
    7. Number of persons on board.
    8. Fuel status.
    9. Facility working aircraft and frequency.
    10. Last known position, how determined, time, estimated present position, and maximum range of flight of the aircraft based on remaining fuel and airspeed.
    11. Position of other aircraft near aircraft's route of flight, when requested.
    12. Whether or not an ELT signal has been heard or reported in the vicinity of the last known position.
    13. Other pertinent information.

    NOTE: FSSs serve as the central points for collecting and disseminating information on an overdue or missing aircraft which is not on an IFR flight plan. Non-FSS ATC facilities that receive telephone calls or other inquiries regarding these flights must refer these calls and inquiries to the appropriate FSS.

    10-3-4. ALNOT

    EN ROUTE

    1. In addition to routing to the regional office operations center for the area in which the facility is located, issue an ALNOT to all centers and Area B circuits, generally 50 miles on either side of the route of flight from the last reported position to destination. Include the original or amended flight plan, as appropriate, and the last known position of the aircraft. At the recommendation of the RCC or at your discretion, the ALNOT may be issued to cover the maximum range of the aircraft.
      • NOTE:
      • 1. An ALNOT must be issued before the RCC can begin search and rescue procedures.
      • 2. Flight plan information on military aircraft is available at the FSS serving as a tie-in station for the departure or destination airport. FAA tie-in stations for airports in the continental U.S. are listed in FAA Order JO 7350.8, Location Identifiers. In the West Flight Services Area Office, tie-in stations are listed in service area publications entitled, “Flight Plan Routing and Airport Search Directory.” For flights with overseas departure points, the information is available through the destination FSS or the appropriate IFSS.
    2. Upon receipt of an INREQ or ALNOT, check the position records to determine whether the aircraft has contacted your facility. Notify the originator of the results or status of this check within one hour of the time the alert was received. Retain the alert in an active status, and immediately notify the originator of subsequent contact, until cancellation is received.
    3. Include pertinent information in the ALNOT that will aid the RCC and SAR Teams in conducting the SAR mission. When known, include:
      1. Last known position.
      2. Time.
      3. Aircraft beacon code.
    4. When information is obtained not previously contained in the ALNOT, issue an amended ALNOT to update information that will assist the SAR providers.

    10-3-5. RESPONSIBILITY TRANSFER TO RCC

    EN ROUTE

    Transfer responsibility for further search to the RCC when one of the following occurs:

    1. Thirty minutes have elapsed after the estimated aircraft fuel exhaustion time.
    2. The aircraft has not been located within one hour after ALNOT issuance.
    3. The ALNOT search has been completed with negative results.

    10-3-6. LAST KNOWN POSITION DETERMINATION

    1. To assist the RCC and SAR Teams in the conduct of the SAR mission, provide the most accurate latitude and longitude available to the FAA using en route and terminal radar sensor data near the aircraft's last known position.
    2. If necessary to prevent an undue delay, utilize any available method to determine the initial latitude and longitude. Follow-up as soon as possible with a formal latitude and longitude using the appropriate terminal or en route facility data extraction tools.
    3. If available, solicit the assistance of other aircraft known to be operating near the aircraft in distress.
    4. Forward this information to the RCC or the ARTCC as appropriate.

    10-3-7. ALNOT CANCELLATION

    EN ROUTE

    1. When directed by the RCC, cancel the ALNOT when the aircraft is located or the search is abandoned.
    2. Include pertinent information in the cancellation that will aid the RCC, SAR Teams, and FAA SAR management to include the location where the aircraft or wreckage was found.

    Section 4. Control Actions

    10-4-1. TRAFFIC RESTRICTIONS

    IFR traffic which could be affected by an overdue or unreported aircraft must be restricted or suspended unless radar separation is used. The facility responsible must restrict or suspend IFR traffic for a period of 30 minutes following the applicable time listed in subparagraphs a thru e:

    1. The time at which approach clearance was delivered to the pilot.
    2. The EFC time delivered to the pilot.
    3. The arrival time over the NAVAID serving the destination airport.
    4. The current estimate, either the control facility's or the pilot's, whichever is later, at:
      1. The appropriate en route NAVAID or fix, and
      2. The NAVAID serving the destination airport.
    5. The release time and, if issued, the clearance void time.

    10-4-2. LIGHTING REQUIREMENTS

    1. EN ROUTE. At nontower or non-FSS locations, request the airport management to light all runway lights, approach lights, and all other required airport lighting systems for at least 30 minutes before the ETA of the unreported aircraft until the aircraft has been located or for 30 minutes after its fuel supply is estimated to be exhausted.
    2. TERMINAL. Operate runway lights, approach lights, and all other required airport lighting systems for at least 30 minutes before the ETA of the unreported aircraft until the aircraft has been located or for 30 minutes after its fuel supply is estimated to be exhausted.

    10-4-3. TRAFFIC RESUMPTION

    After the 30-minute traffic suspension period has expired, resume normal air traffic control if the operators or pilots of other aircraft concur. This concurrence must be maintained for a period of 30 minutes after the suspension period has expired.

    10-4-4. COMMUNICATIONS FAILURE

    Take the following actions, as appropriate, if two-way radio communications are lost with an aircraft:

    • NOTE:
    • 1. When an IFR aircraft experiences two-way radio communications failure, air traffic control is based on anticipated pilot actions. Pilot procedures and recommended practices are set forth in the AIM, CFRs, and pertinent military regulations.
    • 2. Should the pilot of an aircraft equipped with a coded radar beacon transponder experience a loss of two-way radio capability, the pilot can be expected to adjust the transponder to reply on Mode 3/A Code 7600.
    1. In the event of lost communications with an aircraft under your control jurisdiction use all appropriate means available to reestablish communications with the aircraft. These may include, but are not limited to, emergency frequencies, NAVAIDs that are equipped with voice capability, FSS, New York Radio, San Francisco Radio, etc.
      • NOTE:
      • 1. New York Radio and San Francisco Radio are operated by Collins Aerospace (formerly ARINC, Incorporated) under contract with the FAA for communications services. These Radio facilities have the capability of relaying information to/from ATC facilities throughout the country.
      • 2. Aircraft communications addressing and reporting system (ACARS) or selective calling (SELCAL) may be utilized to reestablish radio communications with suitably equipped aircraft. ACARS can be utilized by contacting San Francisco Radio at (800)−621−0140 or New York Radio at (800) 645−1095. Provide the aircraft call sign, approximate location, and contact instructions. In order to utilize the SELCAL system, the SELCAL code for the subject aircraft must be known. If the SELCAL code is not contained in the remarks section of the flight plan, contact the pertinent air carrier dispatch office to determine the code. Then contact San Francisco Radio (for aircraft over the Pacific, U.S. or Mexico) or New York Radio (for aircraft over the Atlantic, Gulf of Mexico, or Caribbean) and provide the aircraft call sign, SELCAL code, approximate location, and contact instructions.
    2. Broadcast clearances through any available means of communications including the voice feature of NAVAIDs.
      • NOTE:
      • 1. Some UHF equipped aircraft have VHF navigation equipment and can receive 121.5 MHz.
      • 2. “Any available means” includes the use of FSS and New York Radio or San Francisco Radio.
    3. Attempt to re-establish communication by having the aircraft use its transponder or make turns to acknowledge clearances and answer questions. Request any of the following in using the transponder:
      1. Request the aircraft to reply Mode 3/A “IDENT.”
      2. Request the aircraft to reply on Code 7600 or if already on Code 7600, the appropriate stratum code.
      3. Request the aircraft to change to “stand-by” for sufficient time for you to be sure that the lack of a target is the result of the requested action.
      • PHRASEOLOGY
      • REPLY NOT RECEIVED, (appropriate instructions). (Action) OBSERVED, (additional instructions/information if necessary).
    4. Broadcast a clearance for the aircraft to proceed to its filed alternate airport at the MEA if the aircraft operator concurs.
    5. If radio communications have not been (re) established with the aircraft after 5 minutes, consider the aircraft's or pilot's activity to be suspicious and report it to the OS/CIC per FAA Order JO 7610.4, Chapter 7, Procedures for Handling Suspicious Flight Situations and Hijacked Aircraft, and paragraph 2-1-26f, Supervisory Notification, of this order.

    Section 5. Miscellaneous Operations

    10-5-1. EXPLOSIVE CARGO

    TERMINAL

    When you receive information that an emergency landing will be made with explosive cargo aboard, inform the pilot of the safest or least congested airport areas. Relay the explosive cargo information to:

    1. The emergency equipment crew.
    2. The airport management.
    3. The appropriate military agencies, when requested by the pilot.

    Section 6. Oceanic Emergency Procedures

    10-6-1. APPLICATION

    The procedures in this section are to be used solely in oceanic airspace.

    10-6-2. PHASES OF EMERGENCY

    Emergency phases are described as follows:

    1. Uncertainty phase (INCERFA). When there is concern about the safety of an aircraft or its occupants, an INCERFA exists:
      1. When communication from an aircraft has not been received within 30 minutes after the time a communication should have been received or after the time an unsuccessful attempt to establish communication with such aircraft was first made, whichever is earlier; or
      2. When an aircraft fails to arrive within 30 minutes after the time of arrival last estimated by the pilot or by the ATC units, whichever is later.
    2. Alert phase (ALERFA). When there is apprehension about the safety of an aircraft and its occupants, an ALERFA exists:
      1. Following the uncertainty phase when subsequent attempts to establish communications with the aircraft, or inquiries to other relevant sources have failed to reveal any information about the aircraft; or
      2. When information has been received which indicates that the operating efficiency of the aircraft has been impaired but not to the extent that a forced landing is likely; or
      3. When communication from an aircraft has not been received within 60 minutes after the time a communication should have been received or after the time an unsuccessful attempt to establish communication with such aircraft was first made, whichever is earlier.
    3. Distress phase (DETRESFA). When there is reasonable certainty that the aircraft and its occupants are threatened by grave and imminent danger, a DETRESFA exists:
      1. Following the alert phase when further attempts to establish communications with the aircraft and more widespread inquiries are unsuccessful; or
      2. When the fuel on board is considered to be exhausted or to be insufficient for the aircraft to reach safety; or
      3. When information is received which indicates that the operating efficiency of the aircraft has been impaired to the extent that a forced landing is likely; or
      4. When information is received or it is reasonably certain that the aircraft is about to make or has made a forced landing.

    10-6-3. ALERTING SERVICE AND SPECIAL ASSISTANCE

    1. Provide alerting service to:
      1. All aircraft receiving ATC service;
      2. All other aircraft which have filed a flight plan or which are otherwise known to the ATC unit; and
      3. Any aircraft known or believed to be the subject of unlawful interference.
    2. When alerting service is required, the responsibility for coordinating such service must, unless otherwise established by letter of agreement, rest with the facility serving the FIR or CTA:
      1. Within which the aircraft was flying at the time of last air-ground radio contact; or
      2. Which the aircraft was about to enter if the last air-ground contact was established at or close to the boundary; or
      3. Within which the point of destination is located if the aircraft:
        1. (a) Was not equipped with suitable two-way radio communications equipment; or
        2. (b) Was not under obligation to transmit position reports.
    3. The responsible Area Control Center (ACC) must serve as the control point for:
      1. Collecting all information relevant to a state of emergency of an aircraft;
      2. Forwarding that information to the appropriate RCC; and
      3. Coordinating with other facilities concerned.
    4. The responsibility of the ACC to provide alerting service for military aircraft may be waived upon a written or recorded request from a military agency. In this case, the military request must state that the military agency assumes full responsibility for their aircraft while the aircraft are operating in the oceanic airspace.
    5. Responsibility to provide alerting service for flight operations conducted under the “due regard” or “operational” prerogative of military aircraft is assumed by the military. When “due regard” operations are scheduled to end with aircraft filed under ICAO procedures, the ACC may, if specified in a letter of agreement, assume responsibility for alerting service at proposed time filed.
    6. In the event of INCERFA, ALERFA, or DETRESFA, notify the following:
      1. When practicable, the aircraft operator.
      2. The appropriate RCC.
      3. Aeronautical stations having en route communications guard responsibilities at the point of departure, along or adjacent to the route of flight, and at the destination.
      4. ACCs having jurisdiction over the proposed route of flight from the last reported position to the destination airport.
    7. INCERFA, ALERFA, and DETRESFA mes- sages must include the following information, if available, in the order listed:
      1. INCERFA, ALERFA, or DETRESFA according to the phase of the emergency.
      2. Agency and person originating the message.
      3. Nature of the emergency.
      4. Significant flight plan information.
      5. The air traffic unit which made the last radio contact, the time, and the frequency used.
      6. The aircraft's last position report, how it was received, and what facility received it.
      7. Color and distinctive marks of aircraft.
      8. Any action taken by reporting office.
      9. Other pertinent remarks.
    8. An INCERFA phase ends with the receipt of any information or position report on the aircraft. Cancel the INCERFA by a message addressed to the same stations as the INCERFA message.
      1. An ALERFA ends when:
        1. (a) Evidence exists that would ease apprehension about the safety of the aircraft and its occupants; or
        2. (b) The concerned aircraft lands. Cancel the ALERFA message by a message addressed to the same stations as the ALERFA message.
      2. A DETRESFA ends when the:
        1. (a) Aircraft successfully lands; or
        2. (b) RCC advises of a successful rescue; or
        3. (c) RCC advises of termination of SAR activities. Cancel the DETRESFA by a message addressed to the same stations as the DETRESFA message.
    9. A separate chronological record should be kept on each ALERFA and DETRESFA together with a chart which displays the projected route of the aircraft, position reports received, route of interceptor aircraft, and other pertinent information.

    10-6-4. INFLIGHT CONTINGENCIES

    1. If an aircraft over water requests weather, sea conditions, ditching information, and/or assistance from surface vessels, or if the controller feels that this information may be necessary for aircraft safety, it should be requested from the RCC. Also, an appropriate AMVER SURPIC should be asked for if requested by the aircraft or deemed beneficial by control personnel.

      NOTE: The AMVER Center can deliver, in a matter of minutes, a SURPIC of vessels in the area of a SAR incident, including their predicted positions and their characteristics.

    2. In all cases of aircraft ditching, the airspace required for SAR operations must be determined by the RCC. The ACC must block that airspace until the RCC advises the airspace is no longer required. An International Notice to Air Missions (NOTAM) must be issued describing the airspace affected.
    3. The following actions will be taken in the event an aircraft must make an emergency descent:
      1. In the event an aircraft requests an emergency descent:
        1. (a) Issue a clearance to the requested altitude if approved separation can be provided.
        2. (b) Advise the aircraft of the traffic, and request its intentions if traffic prevents an unrestricted descent.
        • PHRASEOLOGY
        • ATC ADVISES (aircraft identification) UNABLE TO APPROVE UNRESTRICTED DESCENT.
        • TRAFFIC (traffic information).
        • REQUEST INTENTIONS.
      2. In the event an aircraft is making or will make an emergency descent without a clearance:
        1. (a) Advise other aircraft of the emergency descent.
          • PHRASEOLOGY
          • ATC ADVISES (aircraft identification/all aircraft) BE ALERT FOR EMERGENCY DESCENT IN THE VICINITY OF (latitude/longitude) FROM (altitude/FL) TO (altitude/FL).
        2. (b) Advise other aircraft when the emergency descent is complete.
          • PHRASEOLOGY
          • (Aircraft identification/all aircraft) EMERGENCY DESCENT AT (location) COMPLETED.
      3. Upon notification that an aircraft is making an emergency descent through other traffic, take action immediately to safeguard all aircraft concerned.
      4. When appropriate, broadcast by ATC communications, by radio navigation aids, and/or through aeronautical communication stations/services an emergency message to all aircraft in the vicinity of the descending aircraft.

        Include the following information:

        1. (a) Location of emergency descent.
        2. (b) Direction of flight.
        3. (c) Type aircraft.
        4. (d) Route if appropriate.
        5. (e) Altitude vacated.
        6. (f) Other information.
        • EXAMPLE
        • “Attention all aircraft in the vicinity of Trout, a northbound D-C Ten on A-T-S Route Alfa Seven Hundred is making an emergency descent from flight level three three zero.” (Repeat as you deem appropriate.)
      5. If traffic conditions permit, provide traffic information to the affected aircraft.
      6. Immediately after an emergency broadcast or traffic information has been made, issue appropriate clearances or instructions, as necessary, to all aircraft involved.

    10-6-5. SERVICES TO RESCUE AIRCRAFT

    1. Provide IFR separation between the SAR and the aircraft in distress, except when visual or radar contact has been established by the search and rescue aircraft and the pilots of both aircraft concur, IFR separation may be discontinued.
    2. Clear the SAR aircraft to a fixed clearance limit rather than to the aircraft in distress, which is a moving fix. Issue route clearances that are consistent with that of the distressed aircraft.
    3. Advise the rescue aircraft, as soon as practicable, of any factors that could adversely affect its mission; e.g., unfavorable weather conditions, anticipated problems, the possibility of not being able to approve an IFR descent through en route traffic, etc.
    4. Advise the appropriate rescue agency of all pertinent information as it develops.
    5. Forward immediately any information about the action being taken by the RCC, other organizations, or aircraft to the aircraft concerned.
    6. Advise the aircraft operator of the current status of the SAR operation as soon as practicable.
    7. Since prompt, correct, and complete information is the key to successful rescue operations, ensure that this information is swiftly and smoothly supplied to those organizations actively engaged in rescue operations.

    Section 7. Ground Missile Emergencies

    10-7-1. INFORMATION RELAY

    When you receive information concerning a ground missile emergency, notify other concerned facilities and take action to have alerting advisories issued by:

    1. EN ROUTE. Air carrier company radio stations for each VFR company aircraft which is or will be operating in the vicinity of the emergency.
    2. EN ROUTE. FSSs adjacent to the emergency location.
    3. TERMINAL. Relay all information concerning a ground missile emergency to the ARTCC within whose area the emergency exists and disseminate as a NOTAM.

    10-7-2. IFR AND SVFR MINIMA

    Reroute IFR and SVFR aircraft as necessary to avoid the emergency location by one of the following minima, or by greater minima when suggested by the notifying official:

    1. Lateral separation- 1 mile between the emergency location and either of the following:
      1. An aircraft under radar control and the emergency location which can be accurately determined by reference to the radar scope.
      2. The airspace to be protected for the route being flown.
    2. Vertical separation- 6,000 feet above the surface over the emergency location.

    10-7-3. VFR MINIMA

    Advise all known VFR aircraft which are, or will be, operating in the vicinity of a ground missile emergency, to avoid the emergency location by 1 mile laterally or 6,000 feet vertically, or by a greater distance or altitude, when suggested by the notifying official.

    10-7-4. SMOKE COLUMN AVOIDANCE

    Advise all aircraft to avoid any observed smoke columns in the vicinity of a ground missile emergency.

    10-7-5. EXTENDED NOTIFICATION

    EN ROUTE

    When reports indicate that an emergency will exist for an extended period of time, a Notice to Air Missions may be issued.

Back
Top Bottom