Skip to Main Content
FlightPushFLIGHTPUSH
Chapter 12

Learn

Dashboard My Courses Mastery Map Practice Flight Bag

Resources

CFR & AIM FAA Orders Handbooks & Guides Certification Standards Pilot/Controller Glossary Advisory Circulars Legal Interpretations
Safety Center
Articles Trust Center
Help Center FAQ Status
  1. Reference Library
  2. FAA Orders
  3. JO 7210.3
  4. Chapter 12
  5. Section 7
Loading
flightpush.co home
JO 7210.3 Facility Operation and Administration
  1. Chapter 1. General

    Section 1. Introduction
  2. Section 2. Order Use
  3. Chapter 2. Administration of Facilities

    Section 1. General
  4. Section 2. Responsibilities
  5. Section 3. Air Traffic Familiarization/Currency Requirements for En Route/Terminal/System Operations Facilities
  6. Section 4. Hours of Duty
  7. Section 5. Watch Coverage-Flight Service Stations
  8. Section 6. Watch Supervision-Terminal/En Route
  9. Section 7. Appearance and Security
  10. Section 8. Medical
  11. Section 9. Weather/Visibility
  12. Section 10. Wind/Altimeter Information
  13. Chapter 3. Facility Equipment

    Section 1. General
  14. Section 2. Use of Communications
  15. Section 3. Communications Procedures
  16. Section 4. Recorders
  17. Section 5. Navigational Aids
  18. Section 6. Surveillance Source Use
  19. Section 7. Video Maps
  20. Section 8. Other Displays
  21. Section 9. Color Displays-Terminal
  22. Chapter 4. Correspondence, Conferences, Records, and Reports

    Section 1. General
  23. Section 2. User Coordination/Conferences/Publicity
  24. Section 3. Letters of Agreement (LOA)
  25. Section 4. Application
  26. Section 5. Other Correspondence
  27. Section 6. Records
  28. Section 7. Reports
  29. Section 8. Freedom of Information Act (FOIA)
  30. Chapter 5. Special Flight Handling

    Section 1. Presidential Aircraft
  31. Section 2. FAA Aircraft
  32. Section 3. DOE and Other Aircraft
  33. Section 4. Other Flight Requests
  34. Section 5. 14 CFR Part 91, UAS Operations
  35. Chapter 6. En Route Operations and Services

    Section 1. General
  36. Section 2. Sector Information Binders
  37. Section 3. Operations
  38. Section 4. Services
  39. Section 5. Air Carrier Computer Interface Program
  40. Section 6. En Route Decision Support Tool (EDST)
  41. Section 7. Advanced Technologies and Oceanic Procedures (ATOP)
  42. Section 8. Reduced Vertical Separation Minimum (RVSM)
  43. Section 9. En Route Information Display System (ERIDS)
  44. Section 10. En Route Data Communications
  45. Chapter 7. En Route Data

    Section 1. Performance Checks
  46. Section 2. Deficiencies
  47. Chapter 8. NAS En Route Automation

    Section 1. General
  48. Section 2. Procedures
  49. Section 3. Displays
  50. Chapter 9. Facility Statistical Data, Reports, and Forms

    Section 1. Operational Count Data
  51. Section 2. Instrument Approach Data
  52. Section 3. Other Reports and Forms
  53. Chapter 10. Terminal Operations, Services, and Equipment

    Section 1. General
  54. Section 2. Position Binders
  55. Section 3. Operations
  56. Section 4. Services
  57. Section 5. Terminal Radar
  58. Section 6. Airport Lighting
  59. Section 7. Airport Arrival Rate (AAR)
  60. Chapter 11. FAA Contract Tower Operation and Administration

    Section 1. Organizational Responsibilities
  61. Section 2. Operations and Staffing
  62. Section 3. Training
  63. Section 4. Documents, Forms, and Charts
  64. Section 5. Operational Documents, Directives, and Regulations
  65. Chapter 12. National Programs

    Section 1. Terminal VFR Radar Services
  66. Section 2. Data Recording and Retention
  67. Section 3. VFR Flyway Planning Chart Program
  68. Section 4. Helicopter Route Chart Program
  69. Section 5. VFR Transition Route Program
  70. Section 6. Standard Terminal Automation Replacement System (STARS)
  71. Section 7. Safety Logic Systems Operations Supervisor/CIC Procedures
    1. 12-7-1 ASDE SYSTEM OPERATION
    2. 12-7-2 ENSURE STATUS
    3. 12-7-3 MONITOR ALERTS AND ENSURE CORRECTIVE ACTION
    4. 12-7-4 RAIN CONFIGURATION
    5. 12-7-5 LIMITED CONFIGURATION
    6. 12-7-6 WATCH CHECKLIST
  72. Section 8. VFR Waypoint Chart Program
  73. Section 9. Low Altitude Authorization Notification Capability
  74. Section 10. UAS Facility Maps (UASFM)
  75. Section 11. UAS Operations at Towered Airports
  76. Chapter 13. Facility Statistical Data, Reports, and Forms

    Section 1. General Information
  77. Section 2. Itinerant Operations
  78. Section 3. Local Operations
  79. Section 4. Overflight Operations
  80. Section 5. Amending and Reviewing Data
  81. Chapter 14. Flight Service Operations and Services

    Section 1. General
  82. Section 2. Position/Service Information Binders
  83. Section 3. Operations
  84. Section 4. Services
  85. Chapter 15. Aviation Meteorological Services and Equipment

    Section 1. General
  86. Section 2. Pilot Weather Briefing
  87. Section 3. Broadcasts
  88. Chapter 16. Equipment

    Section 1. General
  89. Section 2. Frequencies
  90. Chapter 17. Facility Statistical Data, Reports, and Forms (Alaska Only)

    Section 1. General Information
  91. Section 2. Aircraft Contacted
  92. Section 3. Flight Plan Count
  93. Section 4. Pilot Briefing Count
  94. Section 5. Other Reports and Information
  95. Section 6. FSS Lists, Logs, and Tallies (OASIS)
  96. Chapter 18. Traffic Management National, Center, and Terminal

    Section 1. Organizational Missions
  97. Section 2. Organizational Responsibilities
  98. Section 3. Line of Authority
  99. Section 4. Supplemental Duties
  100. Section 5. Coordination
  101. Section 6. Trajectory‐Based Operations (TBO)
  102. Section 7. Traffic Management Initiatives
  103. Section 8. Flow Evaluation Area (FEA), Flow Constrained Area (FCA), and Integrated Collaborative Rerouting (ICR)
  104. Section 9. Monitor Alert Parameter
  105. Section 10. Ground Delay Programs
  106. Section 11. Airspace Flow Programs (AFP)
  107. Section 12. Collaborative Trajectory Options Program (CTOP)
  108. Section 13. Ground Stop(s)
  109. Section 14. Special Traffic Management Programs
  110. Section 15. Severe Weather Management
  111. Section 16. Severe Weather Avoidance Plan (SWAP)
  112. Section 17. Preferred IFR Routes Program
  113. Section 18. North American Route Program
  114. Section 19. Coded Departure Routes
  115. Section 20. Route Advisories
  116. Section 21. Operations Plan
  117. Section 22. National Playbook
  118. Section 23. Traffic Management (TM) Support of Non‐Reduced Vertical Separation Minima (RVSM) Aircraft
  119. Section 24. Route Test
  120. Section 25. Time‐Based Flow Management (TBFM)
  121. Section 26. Weather Management
  122. Chapter 19. Waivers, Authorizations, and Exemptions

    Section 1. Regulatory Waivers and Authorizations
  123. Section 2. Elimination of Fixed‐Wing Special Visual Flight Rules Operations
  124. Section 3. Current Authorizations and Exemptions from Title 14, Code of Federal Regulations
  125. Section 4. Parachute Jump Operations
  126. Section 5. Moored Balloons, Kites, Parasail, Unmanned Rockets, and Unmanned Free Balloons/Objects
  127. Section 6. 14 CFR Part 107, sUAS Operations
  128. Section 7. Procedural Waivers
  129. Chapter 20. Temporary Flight Restrictions (TFRs)

    Section 1. General Information
  130. Section 2. Temporary Flight Restrictions for Unmanned Aircraft (49 U.S.C. Section 44812)
  131. Section 3. Temporary Flight Restrictions in the Vicinity of Disaster/Hazard Areas (14 CFR Section 91.137)
  132. Section 4. Temporary Flight Restrictions in National Disaster Areas in the State of Hawaii (Section 91.138)
  133. Section 5. Emergency Air Traffic Rules (14 CFR Section 91.139)
  134. Section 6. Flight Restrictions in the Proximity of the Presidential and Other Parties (14 CFR Section 91.141)
  135. Section 7. Flight Limitation in the Proximity of Space Flight Operations (14 CFR Section 91.143)
  136. Section 8. Management of Aircraft Operations in the Vicinity of Aerial Demonstrations and Major Sporting Events (14 CFR Section 91.145)
  137. Chapter 21. Operations Security: Tactical, Special, and Strategic

    Section 1. Organizational Missions
  138. Section 2. Responsibilities
  139. Section 3. Operational Line of Authority
  140. Section 4. Supplemental Duties
  141. Section 5. Coordination
  142. Section 6. Special Security Instruction (SSI) (14 CFR Section 99.7)
  143. Section 7. Security Notice (SECNOT)
  144. Appendices

    Appendix 1. [RESERVED]
  145. Appendix 2. [RESERVED]
  146. Appendix 3. Air Carrier Aircraft for Air Traffic Activity Operations Count
  147. Appendix 4. Glideslope Outage Authorization Request
  148. Appendix 5. Checklist for Reported Headset Tone Incidents
  149. Appendix 6. Space LOA Sample Templates

JO 7210.3 Facility Operation and Administration|JO 7210.3EE · Change 3 · Effective 7/9/2026

Chapter 12 · Section 7

Safety Logic Systems Operations Supervisor/CIC Procedures

6 Paragraphs|12-7-1–12-7-6

Read Citation (on FlightPush)

12-7-1 ASDE SYSTEM OPERATION

a.

Safety logic systems are software enhancements to the ASDE systems (ASDE-3, ASDE-X and ASSC) that predict the path of aircraft landing and/or departing, and/or vehicular movements on runways. Visual and aural alerts are activated when the safety logic projects a potential collision.

b.

The safety logic system must be operated in a full core alert runway configuration. (In ASDE-X/ASSC, when rain configuration is selected, it includes full core alerting capabilities.)

c.

In the event of a simultaneous loss of Multilateration (MLAT) and ADS-B data, or an ADS-B data loss when MLAT is not present, ASDE-X/ASSC will remain operational. In this case, ASDE-X/ASSC will operate in radar‐only mode. The system automatically transitions to radar‐only mode when it senses a simultaneous MLAT and ADS-B data loss, or an ADS-B data loss when MLAT is not present.

d.

When ASDE-3 and/or AMASS is in maintenance mode, AMASS data must be considered invalid and the system must be taken offline. The OS/CIC must validate, upon resuming normal AMASS operations, that runway configurations and other user settings are adequate for operational use.

NOTE

Action to change AMASS online/offline status is a technical operations function. ASDE-X/ASSC safety logic will automatically be disabled when the system is in maintenance mode.

e.

When a runway becomes unavailable for aircraft operations for an extended period of time, the runway should be entered as “closed” in the safety logic system. Facility procedures should be developed to address using the safety logic system in this capacity.

f.

Construction projects in the vicinity of runways may cause nuisance or false alerts. It is the responsibility of air traffic facility management to mitigate alerts.

1.

Air traffic facilities must use the ASDE-X/ASSC “Inhibit Area” map feature to manage construction related alerts when possible.

2.

National Airway Systems Engineering (NAS Engineering) is able to assist facilities that do not have access to the ASDE-X/ASSC “Inhibit Area” map feature to manage construction related alerts. Facilities must contact NAS Engineering for assistance 30 to 45 days before construction via email at 9-AMC-ATOW-ASDES@faa.gov.

g.

Changes to the airport movement areas which require updated ASDE-X/ASSC Maps can be provided by NAS Engineering. Facilities must contact NAS Engineering for assistance 30 to 45 days before construction via email at 9-AMC-ATOW-ASDES@faa.gov.

h.

ASDE-X/ASSC false targets may be temporarily track dropped after positive verification has been done by pilot/vehicle operator position report or controller visual observation. When a false target is temporarily dropped, it must be noted on FAA Form 7230-4, Daily Record of Facility Operation.

REFERENCE

FAA Order JO 7110.65, Para 3-6-2, Identification.

i.

The air traffic manager may authorize a real target to be inhibited from safety logic processing when the target will likely generate a nuisance alert.

12-7-2 ENSURE STATUS

a.

The OS/CIC is responsible for ensuring that the Safety Logic System is set for the correct runway configuration.

b.

The OS/CIC must ensure that the operational status of the Safety Logic System is known to all operational personnel.

c.

When a status change is made to the Safety Logic System all personnel assigned an operational position must be notified verbally.

d.

When any status change is made to the Safety Logic System it must be noted on FAA Form 7230-4, Daily Record of Facility Operation. Such status must be shown in the facility Status Information Area (SIA). The OS/CIC must ensure that all outages are carried over on applicable logs.

12-7-3 MONITOR ALERTS AND ENSURE CORRECTIVE ACTION

a.

The OS/CIC must ensure that the Safety Logic System is monitored and all alerts are complied with.

b.

All Safety Logic System Alerts generated must be documented on FAA Form 7230-4. If unable to determine the origin of an alert, treat the alert as false and notify Technical Operations so that corrective action can be taken.

REFERENCE

Pilot/Controller Glossary Term- Safety Logic System Alerts. FAA Order JO 7210.632, Chapter 2, Reporting Requirements. FAA Order JO 7210.632, Appendix A, Mandatory Occurrence Report Criteria.

12-7-4 RAIN CONFIGURATION

a.

Due to the required sensitivity of surface movement radars, numerous false targets may be generated by moderate to extreme precipitation. During these periods the ASDE Safety Logic Systems should be operated in rain configuration. Should precipitation of this magnitude occur or be imminent, rain configuration may be applied to avoid the likelihood of false alerts.

b.

When the event that led to placing the system into rain configuration is no longer a factor, the Safety Logic System must be reset to a normal configuration.

NOTE

When AMASS is in rain configuration all safety logic alerts with the exception of arrivals to a closed runway are inhibited and AMASS is not in full core alert status.

12-7-5 LIMITED CONFIGURATION

a.

Under certain circumstances, there may be a need to operate the Safety Logic System in limited configuration. The limited configuration must only be used to temporarily inhibit persistent false alerts. The term “persistent false alert” refers to frequent false alerts caused by continuous or repetitive circumstances. False alerts caused by random events or circumstances of short duration are not considered “persistent false alerts.” The determination of “persistent false alerts” is at the discretion of each OS/CIC.

b.

Due to the required sensitivity of surface movement radars, numerous false targets may be caused by precipitation of moderate or greater intensity. Should precipitation of this magnitude occur or be imminent at locations where ASDE does not have rain configuration availability, limited configuration may be applied to avoid the likelihood of false alerts.

c.

When it is necessary to operate the ASDE-X/ASSC Safety Logic System in limited configuration due to “persistent false alerts,” notify Technical Operations so that corrective action can be taken.

d.

When an AMASS false alert is received, limited configuration must only be used until Technical Operations verifies that the system is functioning properly and that the data necessary to analyze the alert has been obtained. Analysis and resolution of the circumstances surrounding the false alert will be determined by Technical Operations at a later date.

e.

When limited configuration is applied, it must be noted on FAA Form 7230-4, Daily Record of Facility Operation, including the reason for the configuration change. Ensure that all limited configurations are carried over on applicable logs.

NOTE

1. For AMASS, the limited configuration disables all alerts except arrivals to a closed runway and is not considered full‐core alert status. 2. For ASDE-X/ASSC the limited configuration disables all alerts except arrivals to and departures on a closed runway and is not considered full‐core alert status.

12-7-6 WATCH CHECKLIST

The Safety Logic System status must be included in the facility watch checklist. At a minimum, the following items must be reviewed:

a.

Operational status.

b.

Runway configuration.

c.

Presentation of the Safety Logic System data on all ASDE system displays.

d.

When test button is activated, the aural alert is heard, and the speaker volume is adequate.

Referenced in This Section

JO 7110.65 3-6-2
Previous Section12-6 Standard Terminal Automation Replacement System (STARS)Next Section 12-8 VFR Waypoint Chart Program

You Are Reading

12-7-1 ASDE SYSTEM OPERATION

Read Citation (on FlightPush)