| ||||||||||||||
Chapter 2. General ControlSection 1. General 2-1-1. ATC SERVICE The primary purpose of the ATC system is to prevent a collision between aircraft operating in the system and to organize and expedite the flow of traffic, and to provide support for National Security and Homeland Defense. In addition to its primary function, the ATC system has the capability to provide (with certain limitations) additional services. The ability to provide additional services is limited by many factors, such as the volume of traffic, frequency congestion, quality of radar, controller workload, higher priority duties, and the pure physical inability to scan and detect those situations that fall in this category. It is recognized that these services cannot be provided in cases in which the provision of services is precluded by the above factors. Consistent with the aforementioned conditions, controllers must provide additional service procedures to the extent permitted by higher priority duties and other circumstances. The provision of additional services is not optional on the part of the controller, but rather is required when the work situation permits. Provide air traffic control service in accordance with the procedures and minima in this order except when: a. A deviation is necessary to conform with ICAO Documents, National Rules of the Air, or special agreements where the U.S. provides air traffic control service in airspace outside the U.S. and its possessions or: NOTE- b. Other procedures/minima are prescribed in a letter of agreement, FAA directive, or a military document, or: NOTE- REFERENCE- c. A deviation is necessary to assist an aircraft when an emergency has been declared. REFERENCE- 2-1-2. DUTY PRIORITY a. Give first priority to separating aircraft and issuing safety alerts as required in this order. Good judgment must be used in prioritizing all other provisions of this order based on the requirements of the situation at hand. REFERENCE- NOTE- b. Provide support to national security and homeland defense activities to include, but not be limited to, reporting of suspicious and/or unusual aircraft/pilot activities. REFERENCE- c. Provide additional services to the extent possible, contingent only upon higher priority duties and other factors including limitations of radar, volume of traffic, frequency congestion, and workload. 2-1-3. PROCEDURAL PREFERENCE a. Use automation procedures in preference to nonautomation procedures when workload, communications, and equipment capabilities permit. b. Use radar separation in preference to nonradar separation when it will be to an operational advantage and workload, communications, and equipment permit. c. Use nonradar separation in preference to radar separation when the situation dictates that an operational advantage will be gained. NOTE- 2-1-4. OPERATIONAL PRIORITY Provide air traffic control service to aircraft on a “first come, first served” basis as circumstances permit, except the following: NOTE- a. An aircraft in distress has the right of way over all other air traffic. REFERENCE- b. Provide priority to civilian air ambulance flights “LIFEGUARD.” Air carrier/taxi usage of the “LIFEGUARD” call sign, indicates that operational priority is requested. When verbally requested, provide priority to military air evacuation flights (AIR EVAC, MED EVAC) and scheduled air carrier/air taxi flights. Assist the pilots of air ambulance/evacuation aircraft to avoid areas of significant weather and turbulent conditions. When requested by a pilot, provide notifications to expedite ground handling of patients, vital organs, or urgently needed medical materials. NOTE- c. Provide maximum assistance to SAR aircraft performing a SAR mission. REFERENCE- d. Expedite the movement of presidential aircraft and entourage and any rescue support aircraft as well as related control messages when traffic conditions and communications facilities permit. NOTE- REFERENCE- e. Provide special handling, as required to expedite Flight Check aircraft. NOTE- REFERENCE- f. Expedite movement of NIGHT WATCH aircraft when NAOC (pronounced NA-YOCK) is indicated in the remarks section of the flight plan or in air/ground communications. NOTE- REFERENCE- g. Provide expeditious handling for any civil or military aircraft using the code name “FLYNET." REFERENCE- h. Provide expeditious handling of aircraft using the code name “Garden Plot” only when CARF notifies you that such priority is authorized. Refer any questions regarding flight procedures to CARF for resolution. NOTE- i. Provide special handling for USAF aircraft engaged in aerial sampling missions using the code name “SAMP.” REFERENCE- j. Provide maximum assistance to expedite the movement of interceptor aircraft on active air defense missions until the unknown aircraft is identified. k. Expedite movement of Special Air Mission aircraft when SCOOT is indicated in the remarks section of the flight plan or in air/ground communications. NOTE- REFERENCE- l. When requested, provide priority handling to TEAL and NOAA mission aircraft. NOTE- REFERENCE- m. IFR aircraft must have priority over SVFR aircraft. REFERENCE- n. Providing priority and special handling to expedite the movement of OPEN SKIES observation and demonstration flights. NOTE- REFERENCE- o. Aircraft operating under the North American Route Program (NRP) and in airspace identified in the High Altitude Redesign (HAR) program, are not subject to route limiting restrictions (e.g., published preferred IFR routes, letter of agreement requirements, standard operating procedures). REFERENCE- p. If able, provide priority handling to diverted flights. Priority handling may be requested via use of “DVRSN" in the remarks section of the flight plan or by the flight being placed on the Diversion Recovery Tool (DRT). REFERENCE- 2-1-5. EXPEDITIOUS COMPLIANCE a. Use the word “immediately” only when expeditious compliance is required to avoid an imminent situation. b. Use the word “expedite” only when prompt compliance is required to avoid the development of an imminent situation. If an “expedite" climb or descent clearance is issued by ATC, and subsequently the altitude to maintain is changed or restated without an expedite instruction, the expedite instruction is canceled. c. In either case, if time permits, include the reason for this action. 2-1-6. SAFETY ALERT Issue a safety alert to an aircraft if you are aware the aircraft is in a position/altitude that, in your judgment, places it in unsafe proximity to terrain, obstructions, or other aircraft. Once the pilot informs you action is being taken to resolve the situation, you may discontinue the issuance of further alerts. Do not assume that because someone else has responsibility for the aircraft that the unsafe situation has been observed and the safety alert issued; inform the appropriate controller. NOTE- 2. Recognition of situations of unsafe proximity may result from MSAW/E-MSAW/LAAS, automatic altitude readouts, Conflict/Mode C Intruder Alert, observations on a PAR scope, or pilot reports. 3. Once the alert is issued, it is solely the pilot's prerogative to determine what course of action, if any, will be taken. a. Terrain/Obstruction Alert. Immediately issue/initiate an alert to an aircraft if you are aware the aircraft is at an altitude that, in your judgment, places it in unsafe proximity to terrain and/or obstructions. Issue the alert as follows: PHRASEOLOGY- REFERENCE- b. Aircraft Conflict/Mode C Intruder Alert. Immediately issue/initiate an alert to an aircraft if you are aware of another aircraft at an altitude that you believe places them in unsafe proximity. If feasible, offer the pilot an alternate course of action. When an alternate course of action is given, end the transmission with the word “immediately.” PHRASEOLOGY- EXAMPLE- REFERENCE- 2-1-7. INFLIGHT EQUIPMENT MALFUNCTIONS a. When a pilot reports an inflight equipment malfunction, determine the nature and extent of any special handling desired. NOTE- b. Provide the maximum assistance possible consistent with equipment, workload, and any special handling requested. c. Relay to other controllers or facilities who will subsequently handle the aircraft, all pertinent details concerning the aircraft and any special handling required or being provided. 2-1-8. MINIMUM FUEL If an aircraft declares a state of “minimum fuel,” inform any facility to whom control jurisdiction is transferred of the minimum fuel problem and be alert for any occurrence which might delay the aircraft en route. NOTE- 2-1-9. REPORTING ESSENTIAL FLIGHT INFORMATION Report as soon as possible to the appropriate FSS, airport manager's office, ARTCC, approach control facility, operations office, or military operations office any information concerning components of the NAS or any flight conditions which may have an adverse effect on air safety. NOTE- REFERENCE- 2-1-10. NAVAID MALFUNCTIONS a. When an aircraft reports a ground-based NAVAID malfunction, take the following actions: 1. Request a report from a second aircraft. 2. If the second aircraft reports normal operations, continue use and inform the first aircraft. Record the incident on FAA Form 7230-4 or appropriate military form. 3. If the second aircraft confirms the malfunction or in the absence of a second aircraft report, activate the standby equipment or request the monitor facility to activate. 4. If normal operation is reported after the standby equipment is activated, continue use, record the incident on FAA Form 7230-4 or appropriate military form, and notify technical operations personnel (the Systems Engineer of the ARTCC when an en route aid is involved). 5. If continued malfunction is reported after the standby equipment is activated or the standby equipment cannot be activated, inform technical operations personnel and request advice on whether or not the aid should be shut down. In the absence of a second aircraft report, advise the technical operations personnel of the time of the initial aircraft report and the estimated time a second aircraft report could be obtained. b. When an aircraft reports a GPS anomaly, request the following information and/or take the following actions: 1. Record the following minimum information: (a) Aircraft call sign and type. (b) Location. (c) Altitude. (d) Date/time of occurrence. 2. Record the incident on FAA Form 7230-4 or appropriate military form. 3. Broadcast the anomaly report to other aircraft as necessary. PHRASEOLOGY- EXAMPLE- c. When an aircraft reports a Wide Area Augmentation System (WAAS) anomaly, request the following information and/or take the following actions: 1. Determine if the pilot has lost all WAAS service. PHRASEOLOGY- 2. If the pilot reports receipt of any WAAS service, acknowledge the report and continue normal operations. 3. If the pilot reports loss of all WAAS service, report as a GPS anomaly using procedures in subpara 2-1-10b. 2-1-11. USE OF MARSA a. MARSA may only be applied to military operations specified in a letter of agreement or other appropriate FAA or military document. NOTE- b. ATC facilities do not invoke or deny MARSA. Their sole responsibility concerning the use of MARSA is to provide separation between military aircraft engaged in MARSA operations and other nonparticipating IFR aircraft. c. DOD must ensure that military pilots requesting special-use airspace/ATCAAs have coordinated with the scheduling agency, have obtained approval for entry, and are familiar with the appropriate MARSA procedures. ATC is not responsible for determining which military aircraft are authorized to enter special-use airspace/ATCAAs.
REFERENCE- 2-1-12. MILITARY PROCEDURES Military procedures in the form of additions, modifications, and exceptions to the basic FAA procedure are prescribed herein when a common procedure has not been attained or to fulfill a specific requirement. They must be applied by: a. ATC facilities operated by that military service. EXAMPLE- 2. A Navy facility providing service for a Naval Air Station would apply USN procedures to all traffic regardless of class. b. ATC facilities, regardless of their parent organization (FAA, USAF, USN, USA), supporting a designated military airport exclusively. This designation determines which military procedures are to be applied. EXAMPLE- 2. An FAA facility provides approach control service for a Naval Air Station as well as supporting a civil airport; basic FAA procedures are applied at both locations by the FAA facility. 3. A USAF facility supports a USAF base and provides approach control service to a satellite civilian airport; USAF procedures are applied at both locations by the USAF facility. REFERENCE- c. Other ATC facilities when specified in a letter of agreement. EXAMPLE- 2-1-13. FORMATION FLIGHTS a. Control formation flights as a single aircraft. When individual control is requested, issue advisory information which will assist the pilots in attaining separation. When pilot reports indicate separation has been established, issue control instructions as required. NOTE- 2. Formation join-up and breakaway will be conducted in VFR weather conditions unless prior authorization has been obtained from ATC or individual control has been approved. REFERENCE- b. Military and civil formation flights in RVSM airspace. 1. Utilize RVSM separation standards for a formation flight, which consists of all RVSM approved aircraft. 2. Utilize non-RVSM separation standards for a formation flight above FL 290, which does not consist of all RVSM approved aircraft. 3. If aircraft are requesting to form a formation flight to FL 290 or above, the controller who issues the clearance creating the formation flight is responsible for ensuring that the proper equipment suffix is entered for the lead aircraft. 4. If the flight departs as a formation, and is requesting FL 290 or above, the first center sector must ensure that the proper equipment suffix is entered. 5. If the formation flight is below FL 290 and later requests FL 290 or above, the controller receiving the RVSM altitude request must ensure the proper equipment suffix is entered. 6. Upon break-up of the formation flight, the controller initiating the break-up must ensure that all aircraft or flights are assigned their proper equipment suffix. 2-1-14. COORDINATE USE OF AIRSPACE a. Ensure that the necessary coordination has been accomplished before you allow an aircraft under your control to enter another controller's area of jurisdiction. b. Before you issue control instructions directly or relay through another source to an aircraft which is within another controller's area of jurisdiction that will change that aircraft's heading, route, speed, or altitude, ensure that coordination has been accomplished with each of the controllers listed below whose area of jurisdiction is affected by those instructions unless otherwise specified by a letter of agreement or a facility directive: 1. The controller within whose area of jurisdiction the control instructions will be issued. 2. The controller receiving the transfer of control. 3. Any intervening controller(s) through whose area of jurisdiction the aircraft will pass. c. If you issue control instructions to an aircraft through a source other than another controller (e.g., ARINC, FSS, another pilot) ensure that the necessary coordination has been accomplished with any controllers listed in subparas b1, 2, and 3, whose area of jurisdiction is affected by those instructions unless otherwise specified by a letter of agreement or a facility directive. REFERENCE- 2-1-15. CONTROL TRANSFER a. Transfer control of an aircraft in accordance with the following conditions: 1. At a prescribed or coordinated location, time, fix, or altitude; or, 2. At the time a radar handoff and frequency change to the receiving controller have been completed and when authorized by a facility directive or letter of agreement which specifies the type and extent of control that is transferred. REFERENCE- b. Transfer control of an aircraft only after eliminating any potential conflict with other aircraft for which you have separation responsibility. c. Assume control of an aircraft only after it is in your area of jurisdiction unless specifically coordinated or as specified by letter of agreement or a facility directive. 2-1-16. SURFACE AREAS a. Coordinate with the appropriate nonapproach control tower on an individual aircraft basis before issuing a clearance which would require flight within a surface area for which the tower has responsibility unless otherwise specified in a letter of agreement. REFERENCE- b. Coordinate with the appropriate control tower for transit authorization when you are providing radar traffic advisory service to an aircraft that will enter another facility's airspace. NOTE- c. Transfer communications to the appropriate facility, if required, prior to operation within a surface area for which the tower has responsibility. REFERENCE- 2-1-17. RADIO COMMUNICATIONS a. Transfer radio communications before an aircraft enters the receiving controller's area of jurisdiction unless otherwise coordinated or specified by a letter of agreement or a facility directive. b. Transfer radio communications by specifying the following: NOTE- 1. The facility name or location name and terminal function to be contacted. TERMINAL: Omit the location name when transferring communications to another controller within your facility; except when instructing the aircraft to change frequency for final approach guidance include the name of the facility. 2. Frequency to use except the following may be omitted: (a) FSS frequency. (b) Departure frequency if previously given or published on a SID chart for the procedure issued. (c) TERMINAL: (1) Ground or local control frequency if in your opinion the pilot knows which frequency is in use. (2) The numbers preceding the decimal point if the ground control frequency is in the 121 MHz bandwidth. EXAMPLE- 3. Time, fix, altitude, or specifically when to contact a facility. You may omit this when compliance is expected upon receipt. NOTE- PHRASEOLOGY- c. Controllers must, within a reasonable amount of time, take appropriate action to establish/restore communications with all aircraft for which a communications transfer or initial contact to his/her sector is expected/required. NOTE- d. In situations where an operational advantage will be gained, and following coordination with the receiving controller, you may instruct aircraft on the ground to monitor the receiving controller's frequency. EXAMPLE- e. In situations where a sector has multiple frequencies or when sectors are combined using multiple frequencies and the aircraft will remain under your jurisdiction, transfer radio communication by specifying the following: PHRASEOLOGY- EXAMPLE- REFERENCE- f. Avoid issuing a frequency change to helicopters known to be single-piloted during air-taxiing, hovering, or low-level flight. Whenever possible, relay necessary control instructions until the pilot is able to change frequency. NOTE- REFERENCE- g. In situations where the controller does not want the pilot to change frequency but the pilot is expecting or may want a frequency change, use the following phraseology. PHRASEOLOGY- REFERENCE- 2-1-18. OPERATIONAL REQUESTS Respond to a request from another controller, a pilot or vehicle operator by one of the following verbal means: a. Restate the request in complete or abbreviated terms followed by the word “APPROVED.” The phraseology “APPROVED AS REQUESTED” may be substituted in lieu of a lengthy readback. PHRASEOLOGY- b. State restrictions followed by the word “APPROVED.” PHRASEOLOGY- c. State the word “UNABLE” and, time permitting, a reason. PHRASEOLOGY- d. State the words “STAND BY.” NOTE- REFERENCE- 2-1-19. WAKE TURBULENCE a. Apply wake turbulence procedures to aircraft operating behind heavy jets/B757s and, where indicated, to small aircraft behind large aircraft. NOTE- b. The separation minima must continue to touchdown for all IFR aircraft not making a visual approach or maintaining visual separation. REFERENCE- 2-1-20. WAKE TURBULENCE CAUTIONARY ADVISORIES a. Issue wake turbulence cautionary advisories and the position, altitude if known, and direction of flight of the heavy jet or B757 to: REFERENCE- 1. TERMINAL. VFR aircraft not being radar vectored but are behind heavy jets or B757s. 2. IFR aircraft that accept a visual approach or visual separation. REFERENCE- 3. TERMINAL. VFR arriving aircraft that have previously been radar vectored and the vectoring has been discontinued. b. Issue cautionary information to any aircraft if in your opinion, wake turbulence may have an adverse effect on it. When traffic is known to be a heavy aircraft, include the word heavy in the description. NOTE- REFERENCE- PHRASEOLOGY- REFERENCE- 2-1-21. TRAFFIC ADVISORIES Unless an aircraft is operating within Class A airspace or omission is requested by the pilot, issue traffic advisories to all aircraft (IFR or VFR) on your frequency when, in your judgment, their proximity may diminish to less than the applicable separation minima. Where no separation minima applies, such as for VFR aircraft outside of Class B/Class C airspace, or a TRSA, issue traffic advisories to those aircraft on your frequency when in your judgment their proximity warrants it. Provide this service as follows: a. To radar identified aircraft: 1. Azimuth from aircraft in terms of the 12-hour clock, or 2. When rapidly maneuvering aircraft prevent accurate issuance of traffic as in 1 above, specify the direction from an aircraft's position in terms of the eight cardinal compass points (N, NE, E, SE, S, SW, W, and NW). This method must be terminated at the pilot's request. 3. Distance from aircraft in miles. 4. Direction in which traffic is proceeding and/or relative movement of traffic. NOTE- 5. If known, type of aircraft and altitude. REFERENCE- PHRASEOLOGY- EXAMPLE- 6. When requested by the pilot, issue radar vectors to assist in avoiding the traffic, provided the aircraft to be vectored is within your area of jurisdiction or coordination has been effected with the sector/facility in whose area the aircraft is operating. 7. If unable to provide vector service, inform the pilot. REFERENCE- 8. Inform the pilot of the following when traffic you have issued is not reported in sight: (a) The traffic is no factor. (b) The traffic is no longer depicted on radar. PHRASEOLOGY- b. To aircraft that are not radar identified: 1. Distance and direction from fix. 2. Direction in which traffic is proceeding. 3. If known, type of aircraft and altitude. 4. ETA over the fix the aircraft is approaching, if appropriate. PHRASEOLOGY- EXAMPLE- c. For aircraft displaying Mode C, not radar identified, issue indicated altitude. EXAMPLE- REFERENCE- 2-1-22. BIRD ACTIVITY INFORMATION a. Issue advisory information on pilot-reported, tower-observed, or radar-observed and pilot-verified bird activity. Include position, species or size of birds, if known, course of flight, and altitude. Do this for at least 15 minutes after receipt of such information from pilots or from adjacent facilities unless visual observation or subsequent reports reveal the activity is no longer a factor. EXAMPLE- b. Relay bird activity information to adjacent facilities and to AFSSs/FSSs whenever it appears it will become a factor in their areas. 2-1-23. TRANSFER OF POSITION RESPONSIBILITY The transfer of position responsibility must be accomplished in accordance with the “Standard Operating Practice (SOP) for the Transfer of Position Responsibility,” and appropriate facility directives each time operational responsibility for a position is transferred from one specialist to another. 2-1-24. WHEELS DOWN CHECK USA/USAF/USN Remind aircraft to check wheels down on each approach unless the pilot has previously reported wheels down for that approach. NOTE- a. Tower must issue the wheels down check at an appropriate place in the pattern. PHRASEOLOGY- b. Approach/arrival control, GCA must issue the wheels down check as follows: 1. To aircraft conducting ASR, PAR, or radar monitored approaches, before the aircraft starts descent on final approach. 2. To aircraft conducting instrument approaches and remaining on the radar facility's frequency, before the aircraft passes the outer marker/final approach fix. PHRASEOLOGY- 2-1-25. SUPERVISORY NOTIFICATION Ensure supervisor/controller-in-charge (CIC) is aware of conditions which impact sector/position operations including, but not limited to, the following: a. Weather. b. Equipment status. c. Potential sector overload. d. Emergency situations. e. Special flights/operations. f. Possible suspicious aircraft/pilot activity as prescribed in FAA Order JO 7610.4, paragraph 7-3-1. 2-1-26. PILOT DEVIATION NOTIFICATION When it appears that the actions of a pilot constitute a pilot deviation, notify the pilot, workload permitting. PHRASEOLOGY- REFERENCE- 2-1-27. TCAS RESOLUTION ADVISORIES a. When an aircraft under your control jurisdiction informs you that it is responding to a TCAS Resolution Advisory (RA), do not issue control instructions that are contrary to the RA procedure that a crew member has advised you that they are executing. Provide safety alerts regarding terrain or obstructions and traffic advisories for the aircraft responding to the RA and all other aircraft under your control jurisdiction, as appropriate. b. Unless advised by other aircraft that they are also responding to a TCAS RA, do not assume that other aircraft in the proximity of the responding aircraft are involved in the RA maneuver or are aware of the responding aircraft's intended maneuvers. Continue to provide control instructions, safety alerts, and traffic advisories as appropriate to such aircraft. c. Once the responding aircraft has begun a maneuver in response to an RA, the controller is not responsible for providing standard separation between the aircraft that is responding to an RA and any other aircraft, airspace, terrain or obstructions. Responsibility for standard separation resumes when one of the following conditions are met: 1. The responding aircraft has returned to its assigned altitude, or 2. A crew member informs you that the TCAS maneuver is completed and you observe that standard separation has been reestablished, or 3. The responding aircraft has executed an alternate clearance and you observe that standard separation has been reestablished. NOTE- EXAMPLE- NOTE- EXAMPLE- 2-1-28. RVSM OPERATIONS Controller responsibilities must include but not be limited to the following: a. Non-RVSM aircraft operating in RVSM airspace. 1. Ensure non-RVSM aircraft are not permitted in RVSM airspace unless they meet the criteria of excepted aircraft and are previously approved by the operations supervisor/CIC. The following aircraft are excepted: DOD, DOD certified aircraft operated by NASA (T38, F15, F18, WB57, S3, and U2 aircraft only), Lifeguard, manufacturer aircraft being flown for development/certification, and Foreign State aircraft. These exceptions are accommodated on a workload or traffic-permitting basis. NOTE- 2. Ensure sector-to-sector coordination for all non-RVSM aircraft operations within RVSM airspace. 3. Inform the operational supervisor/CIC when a non-RVSM exception flight is denied clearance into RVSM airspace or is removed from RVSM airspace. b. Non-RVSM aircraft transitioning RVSM airspace. Ensure that operations supervisors/CICs are made aware when non-RVSM aircraft are transitioning through RVSM airspace. c. Apply appropriate separation standards and remove any aircraft from RVSM airspace that advises it is unable RVSM due to equipment while en route. d. Use “negative RVSM" in all verbal ground-to-ground communications involving non-RVSM aircraft while cleared to operate within RVSM airspace. EXAMPLE- e. For the following situations, use the associated phraseology: 1. To deny clearance into RVSM airspace. PHRASEOLOGY- 2. To request a pilot to report when able to resume RVSM. PHRASEOLOGY- f. In the event of a change to an aircraft's navigational capability amend the equipment suffix in order to properly identify non-RVSM aircraft on the controller display. 2-1-29. TERRAIN AWARENESS WARNING SYSTEM (TAWS) ALERTS a. When an aircraft under your control jurisdiction informs you that it is responding to a TAWS (or other on-board low altitude) alert, do not issue control instructions that are contrary to the TAWS procedure that a crew member has advised you that they are executing. Provide safety alerts regarding terrain or obstructions and traffic advisories for the aircraft responding to the TAWS alert and all other aircraft under your control jurisdiction, as appropriate. b. Once the responding aircraft has begun a maneuver in response to TAWS alert, the controller is not responsible for providing standard separation between the aircraft that is responding to a TAWS alert and any other aircraft, airspace, terrain or obstructions. Responsibility for standard separation resumes when one of the following conditions are met: 1. The responding aircraft has returned to its assigned altitude, or 2. A crew member informs you that the TAWS maneuver is completed and you observe that standard separation has been reestablished, or 3. The responding aircraft has executed an alternate clearance and you observe that standard separation has been reestablished. 2-1-30. "BLUE LIGHTNING" EVENTS Ensure that the supervisor/controller-in-charge (CIC) is notified of reports of possible human trafficking. These may be referred to as "Blue Lightning" events. . |
|
|
