Radar Vectors
FAA Order Cancelled Issued Feb 1, 2013 AJV-2 57 pages Copy saved Nov 18, 2026

Order 7900.2B Reporting of Navigational Aids, Communication Facilities, and Aviation Weather Systems Data to the NFDC

This document is cancelled. Cancelled by JO 7900.2C. Check the official source before relying on it.

Official source ↗ Open PDF

FAA Logo

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

Air Traffic Organization Policy

ORDER JO 7900.2B

Effective Date:

01/31/2013

SUBJ: Reporting of Navigational Aids, Communication Facilities, and Aviation Weather Systems Data to the National Flight Data Center

ORDER JO 7900.2B

1. Purpose of This Order. This order defines requirements and responsibilities for reporting Navigational Aids (NAVAIDs), Communication Facilities (e.g., Air Route Traffic Control Centers (ARTCC), Terminal Radar Approach Control (TRACON) facilities, Airport Traffic Control Towers (ATCT), DoD Approach Control Facilities, and Flight Service Stations (FSS)), and Aviation Weather Systems (e.g., AWOS, ASOS) data to the National Flight Data Center (NFDC).

2. Audience. This order applies to the following organizations within the Federal Aviation Administration (FAA) Air Traffic Organization (ATO), who have the responsibility for submitting data to the NFDC: the System Operations Flight Services Program Operations Office; the En Route and Oceanic Services Service Areas (ARTCC and CERAP facilities); the Terminal Services Service Areas (ATCT and TRACON facilities); the Technical Operations Service Areas (NAVAID Engineering Group), Program Operations Services directorate (Spectrum Engineering Services Group), and Flight Inspection Services directorate; and the Mission Support Services Service Centers (Non-Fed Program Coordination Offices and Planning and Requirements Group). This order also applies to organizations within the Department of Defense for the submission of military data to the NFDC.

3. Where Can I Find This Order? This order is available on the MyFAA employee website at https://employees.faa.gov/tools_resources/orders_notices/ and on the FAA’s public website at http://www.faa.gov/regulations_policies/orders_notices/.

4. Cancellation. Order 7900.2A, Reporting of Electronic Navigation Aids and Communication Facilities Data to the National Flight Data Center, dated June 12, 1978, is cancelled.

5. Explanation of Policy Changes. These changes are being implemented to provide new and updated guidance and policy for reporting aeronautical data to the National Flight Data Center. Specific changes include:

a. General. This order standardizes data reporting requirements, defines authorized sources, provides data submission forms, and expands the data domains to include aviation weather systems.

Distribution: Electronic Initiated By: AJV-212

01/31/2013 7900.2B

b. Format. Formatting is revised to meet current FAA standards. Paragraphs are realigned for better editorial flow. Office identifications and routing codes are updated to reflect the current FAA organizational structure.

c. NAVAID Data. The NAVAID form and Instrument Landing System (ILS) form will replace Form 8240-22 (Facility Data Sheet), previously provided in Order 8240.52, for the submission of these data to the NFDC.

6. Requirements for Reporting Aeronautical Data to the National Flight Data Center (NFDC).

a. General. When a National Airspace System (NAS) service, facility or system is commissioned, decommissioned or modified, the data must be reported to the NFDC. Each organization with the authority to submit NAS data changes must submit the changes on the appropriate data forms which are available on the NFDC website (https://nfdc.faa.gov), and are included in the Appendices of this Order for reference. Prior to submission of the form, the responsible organization must ensure authorization and certification for the changes through coordination with the appropriate stakeholder organizations, as mandated by applicable FAA directives.

b. Forms. Forms have been created to replace the legacy memorandum-based method of submitting NAS data changes to the NFDC. The forms presented in this Order are intended to capture data describing the following facilities and systems:

(1) Instrument Landing Systems. This form is used to submit Instrument Landing System (ILS), Simplified Directional Facility (SDF), Microwave Landing System (MLS), Interim Standard Microwave Landing System (ISMLS), and Localizer-type Directional Aid (LDA) data to the NFDC.

(2) Navigational Aids. This form is used to submit navigational aid (NAVAID) data to the NFDC. NAVAIDs include distance measuring equipment (DME), non-directional beacons (NDB), tactical air navigation (TACAN) systems, very high frequency (VHF) omni-directional range (VOR) systems, VOR test facilities (VOT), and certain combinations of these systems.

(3) Air Route Traffic Control Centers. This form is used to submit Air Route Traffic Control Center (ARTCC), Center Radar Approach Control (CERAP), and the en route portion of the combined control facility (CCF), including Remote Center Air/Ground (RCAG) communications facilities, data to the NFDC.

Note: This form is NOT used to submit data describing ARTCC boundaries. For instructions detailing how to submit ARTCC boundary data to the NFDC, reference FAA Order 7900.1, Changes to Domestic/Oceanic Air Route Traffic Control Center (ARTCC) and ICAO Flight Information Region (FIR) Boundaries.

2

01/31/2013 7900.2B

(4) Terminal Air Traffic Control Facilities. This form is used to submit data describing terminal air traffic control facilities, including airport traffic control towers (ATCT), Remote Transmitter/Receiver (RTR), terminal radar approach control (TRACON) facilities (including both on airport and consolidated TRACON facilities), the terminal portion of the combined control facility (CCF), DoD Approach Control Facilities, and military ground controlled approach (GCA) facilities to the NFDC.

(5) Weather Systems. This form is used to submit weather (WX) system (e.g., Automated Surface Observing System (ASOS) and Automated Weather Observing System (AWOS)) data to the NFDC.

(6) Flight Service Stations. This form is used to submit data describing Flight Service Stations (FSS), Radio Communication Outlets (RCO), and Self Sustained Outlets (SSO) to the NFDC.

c. Geodetic Datum. Each of the forms includes a field to identify the datums used to measure the reported geodetic data. Any civilian domestic geodetic data reported to the NFDC on the forms in this Order must use the North American Datum of 1983 (NAD83) as the horizontal reference system and the North American Vertical Datum of 1988 (NAVD88) as the vertical reference system. Military geodetic data may use WGS84 as the horizontal reference system and EGM96 as the vertical reference system to comply with international standards.

d. Submission. Instructions for how to submit NAS data changes (via the forms) to the NFDC are available on the NFDC website (https://nfdc.faa.gov). In the event that the NFDC website is unavailable, the forms provided in the Appendices of this Order may be completed and then faxed or mailed to the NFDC via the following:

FAA, Aeronautical Information Management NFDC Group, AJV-21 800 Independence Ave., SW Washington, DC 20591 FAX: 202-267-5322

The submitting organization must provide NAS data changes to the NFDC as soon as possible but not later than the “cut-off” dates listed on the NFDC website (https://nfdc.faa.gov) and in the Airport Facility Directory (A/FD). Adherence to established data submission cut-off dates is required to ensure changes to the NAS are disseminated in compliance with Aeronautical Information Regulation and Control (AIRAC) effective dates.

7. Distribution. This order is distributed in Washington headquarters to the branch level of the Office of Airports, the Air Traffic Organization (including En Route and Oceanic Services, Terminal Services, Technical Operations Services, System Operations Services, and Mission Support Services), and the Office of Aviation Safety (including Flight Standards Service); to the

3

01/31/2013 7900.2B

William J. Hughes Technical Center; to the Mike Monroney Aeronautical Center; to all Regional Offices; and to all associated field offices and facilities. This order is also distributed to the following external organizations: the National Geospatial-Intelligence Agency, the Department of Defense, and the Department of Homeland Security.

8. Background. The NFDC, within the Aeronautical Information Management (AIM) directorate of Mission Support Services, is the central authority and official repository within the FAA responsible for the collection, validation and quality control of aeronautical information disseminated to support NAS operations detailing the physical description, geographical position, and operational characteristics and status of all components of the NAS.

The NFDC is responsible for providing aeronautical information for operational use by ATCTs, TRACONs, ARTCCs, Air Traffic Control System Command Center, Flight Service Stations, DoD, DHS, private chart producers, airports, pilots, Flight Management Systems, Global Positioning Systems, onboard cockpit displays, moving maps, and data link systems. NFDC aeronautical information is used to develop and update Instrument Approach Procedures, digital products, aeronautical charts and related publications. The NFDC disseminates aeronautical information in accordance with standards established by the International Civil Aviation Organization (ICAO) and in accordance with the AIRAC cycle.

Signed by Elizabeth L. Ray on January 30, 2013 Air Traffic Organization

4

01/31/2013 7900.2B Appendix A

Appendix A: Instrument Landing System Data Form Instructions

Appendix A: Instrument Landing System Data Form Instructions

1. General. This form is used to submit Instrument Landing System (ILS), Simplified Directional Facility (SDF), Microwave Landing System (MLS), Interim Standard Microwave Landing System (ISMLS), and Localizer-type Directional Aid (LDA) data to the NFDC.

This form should only be used to submit instrument landing system (ILS) data to the NFDC. There is a separate data form that should be used to submit data describing other navigational aids, such as non-directional beacons (NDB), tactical air navigation (TACAN) systems, and very high frequency (VHF) omni-directional range (VOR) systems.

Submitters should carefully read all of the following instructions to ensure the preparation of complete and accurate submissions that can be processed in a timely manner.

2. Authorized Submitters. For federally owned systems, this form should be submitted to the NFDC by personnel within the NAVAID Engineering group within FAA ATO Technical Operations.

For non-federally owned systems, this form should be submitted to the NFDC by personnel within the non-federal program implementation management group within the appropriate Regional Service Center under FAA ATO Mission Support Services.

For military owned systems, this form should be submitted to the NFDC by authorized personnel within the appropriate service under the DoD.

3. Form Sections.

I. Submission. This section provides information related to submission of the data to the NFDC, including the contact information of the submitter, the name of the official who authorizes the changes to made, the purpose of the submission, and the estimated date that the changes will be effective.

(1) Name. Enter the name of the submitter.

(2) Organization. Enter the name of the submitter’s employer (organization and routing code).

(3) Date. Enter the month, day, and year the form was prepared.

(4) Email. Enter the email address of the submitter.

(5) Phone. Enter the phone number (with area code) of the submitter.

(6) Authorizing Official. Enter the name of the official authorizing the changes to be made (i.e. facility manager, program director, lead engineer, etc.).

01/31/2013 7900.2B Appendix A

(7) Purpose of Submission. Select one of the following options to indicate the purpose for submitting the form:

 Changes to Existing System. Select this box if this form is being submitted to report changes to an existing ILS, e.g., addition of a DME

 New System. Select this box if this form is being submitted to report a new ILS that has been or will be newly commissioned

 Decommission System. Select this box if this form is being submitted to report decommissioning of an existing ILS

(8) Are any changes being made to the runway associated with this ILS (e.g., new RWY threshold, displaced threshold, RWY length, RWY width)? Indicate whether any changes are being made to the runway as a result of the new/changing/relocating ILS. If yes, reference the source of the RWY data changes (e.g., survey, airport district office (ADO), Aeronautical Information Publication (AIP)) in the REMARKS section of the form.

Note: The source is only requested to provide the source of the RWY data, not the data itself.

(9) Proposed Effective Date. Enter the date that the reported changes will take effect. This date may be the same as the form preparation date; however, if this form is being used to provide advance notice of changes to the NFDC, the submitter should enter the date that those changes will take effect.

II. General. This section provides general information that describes the ILS for which data is being reported.

(10) Facility ID. Enter the identifier of the facility per FAA Order 7350.8.

(11) Facility Type. Indicate the type of facility being reported as:

 ILS – Instrument Landing System  ILS/DME – ILS with Distance Measuring Equipment (DME)  ISMLS – Interim Standard Microwave Landing System  LDA – Localizer-type Directional Aid  LDA/DME – LDA with DME  LOC - Localizer  LOC/DME – LOC with DME  MLS – Microwave Landing System  PAR – Precision Approach Radar  SDF – Simplified Directional Facility  SDF/DME – SDF with DME

01/31/2013 7900.2B Appendix A

(12) Owner Type. Choose the type of funding used for the facility as:

 Federal  Non-Federal  Military

(13) ILS Classification. Enter the classification of the ILS (per FAA Order 6750.24) used to describe the system’s performance.

a. Facility Performance Category (CAT). Indicate the facility performance category as defined in FAA Order 6750.24:

 I – ILS equipment meeting performance standards and monitors adjusted to support Category I approach operations

 II – ILS equipment meeting performance standards and monitors adjusted to support Category II approach operations

 III – ILS equipment meeting performance standards and monitors adjusted to support Category III approach operations

b. Course Structure Tolerance (TOL). Indicate the ILS point (defined in FAA Order 6750.24) to which the localizer conforms to the CAT III course structure tolerances using a physical location on the approach or runway:

 A – 4 nautical miles (NM) before the threshold  B – 3,500 feet before the threshold  C – Glide path altitude of 100 feet height above touchdown (HAT) (CAT II

decision point)  T – Threshold  D – 3,000 feet beyond the threshold (CAT III requirement only)  E – 2,000 feet before the runway end (CAT III requirement only) c. Integrity/Continuity (I/C). Indicate the minimum level of integrity and Continuity of Service (CoS) of the ILS as (for the specific requirements regarding the levels of integrity and continuity, reference FAA Order 6750.24):

 Level 1  Level 2  Level 3  Level 4

(14) Magnetic (Mag) Variation. Enter the magnetic variation of record for the ILS and the epoch year. If unknown, contact the Product Support Group within the Aeronautical Products directorate of FAA ATO Mission Support Services or appropriate DoD agency.

(15) Owner. Enter the name of the organization or authority that owns the facility (e.g., FAA, U.S. Air Force, county, state).

(16) Airport Name. Enter the airport name or name of the military airfield per FAA Order 7350.8.

01/31/2013 7900.2B Appendix A

(17) Airport Location (Loc) Identifier (ID). Enter the three character FAA location identifier or the four letter International Civil Aviation Organization (ICAO) location identifier of the associated airport per FAA Order 7350.8.

(18) Location. Enter the city and state (for US) or city and country (for international) where the facility is located per FAA Order 7350.8.

(19) Operator. Enter the name of the organization or authority that operates the facility (e.g., FAA, U.S. Air Force, county, state).

(20) Approach Runway End Number. Identify the number of the approach runway end served by the ILS.

(21) Approach (Apch) Bearing. Enter the approach bearing of the ILS in degrees to the nearest hundredth.

(22) Geodetic Datum. Choose the applicable horizontal and vertical reference systems used for any geodetic data reported.

 Horizontal: NAD83 or WGS84  Vertical: NAVD88 or EGM96

(23) Transmitter. Choose whether the ILS utilizes a single or dual transmitter.

(24) Dual Frequency. Choose whether or not the ILS uses a dual frequency.

(25) Remotely Monitored. Choose whether or not the ILS is remotely monitored; if so; enter the name of the monitoring facility (e.g., ATCT).

III. Localizer or MLS Azimuth. This section provides information that describes the localizer component of the ILS (or azimuth for MLS) for which data is being reported.

(26) Coordinates. Enter the latitude and longitude of the localizer in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude and an E or W after the longitude.

(27) Elevation (MSL). Enter the ground elevation of the localizer in feet to the nearest tenth of a foot, mean sea level (MSL). If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

(28) Equipment Type. Enter information describing the equipment type of the localizer (e.g., manufacturer, model number, etc.).

(29) Antenna Type. Indicate the antenna type of the localizer as:

 4D – 4-DIPOLE  6D – 6-DIPOLE  SL – 8-LOOP

 4D – 4-DIPOLE  6D – 6-DIPOLE  SL – 8-LOOP

01/31/2013 7900.2B Appendix A

 CE – CAP-EFF  LD - LDA  LP – LOG-PER  TW – TRAV-WAVE  V4 – VRING-14  V5 – VRING-15  V8 – VRING-8  WG – WAV-GUIDE  YG – YAGI  Other – Specify in Remarks section

(30) Frequency (Freq). Enter the frequency of the Localizer in MHz to the nearest thousandth.

(31) Voice. Indicate the type of service provided by remote voice capability as:

 Automated Terminal Information Services (ATIS)  Approach Control (APCH CTL)  None

(32) Distance (Dist) to Approach End of Runway (AER). Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the leading edge of the localizer or azimuth antenna to the landing threshold at the approach end of the runway (accounting for any displacements).

(33) Distance (Dist) to Departure End of Runway (DER). Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the leading edge of the localizer or azimuth antenna to the stop/departure end of the runway. An offset antenna inside the stop/departure end, toward the threshold, will require the use of a minus sign preceding the distance value (e.g., offset stop/departure end, -76 feet).

(34) Standby Power. Choose the form of standby power as:

 Commercial  Engine  Battery  None

(35) Course Width (CW). Enter (to the nearest hundredth) the localizer monitor limits.

Note: Ideal widths for ILS are between 3.00 and 6.00 degrees, and ideal widths for SDF are between 6.00 and 12.00 degrees.

(36) Tailored Course Width. Indicate whether or not the localizer course width is tailored; if so; enter the sector course width at the threshold in feet to the nearest foot. Note that a tailored localizer course must have a width of 700 feet + 5 feet at the threshold.

01/31/2013 7900.2B Appendix A

(37) Back Course Status. Choose whether the back course of the localizer is usable or unusable.

(38) Dist (Dist) and Direction (Dir) Offset from Runway (RWY) Centerline (C/L). If the localizer/ azimuth antenna is offset from the runway center, enter the distance it is offset (to the nearest foot). The direction (right or left) is determined by facing the runway at the approach end. If the localizer/azimuth is within + 10 feet from runway center, enter C/L.

IV. Glide Path or MLS Elevation Station. This section provides information that describes the glide path data of the system for which data is being reported. This section can be used to provide data for the glide slope component of an ILS, the elevation station of an MLS, or a precision approach radar.

(39) Coordinates. Enter the latitude and longitude of the glide slope antenna in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after to the latitude and an E or W after to the longitude.

(40) Elevation (MSL). Enter the ground elevation of the glide slope in feet to the nearest tenth of a foot, mean sea level (MSL). If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

(41) Antenna Height (AGL). Enter the height of the glide slope antenna (i.e., the highest point of the glide slope antenna structure) in feet to the nearest tenth of a foot, above ground level (AGL).

(42) Equipment Type. Enter information describing the equipment type of the glide slope (e.g., manufacturer, model number, etc.).

(43) Freq. Enter the frequency of the glide slope in MHz to the nearest thousandth.

(44) Glide Angle. Enter the angle of the glide path to the nearest hundredth of a degree.

(45) Antenna Type. Indicate the antenna type of the glide slope as:

 CE – CAP-EFF  EF – END-FIRE (Must include the Phase Center Line Elevation and Runway Point of Intercept with this antenna type in the remarks section)

 EU – END-UPSLOPE  NR – NULL-REF  SR – SIDE-REF  Other – Specify in Remarks section

(46) Aiming Point Coordinates. Enter the latitude and longitude of the Aiming Point of the GS in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after to the latitude and an E or W after to the longitude.

01/31/2013 7900.2B Appendix A

(47) RWY Elevation (Elev) Adjacent to Glide Slope (GS). Enter the elevation (to the nearest tenth of a foot, if available) of the runway C/L abeam the ILS glide slope or MLS elevation antenna.

(48) Dist to AER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the glide slope to the landing threshold at the approach end of the runway (accounting for any displacements).

(49) Dist / Dir From Antenna to RWY C/L. Enter if the ILS glide slope is left or right of runway centerline and enter the precise perpendicular distance to runway centerline (to the nearest foot).

(50) Standby Power. Choose the form of standby power as:

 Commercial  Engine  Battery  None

V. Distance Measuring Equipment (DME). This section provides information that describes the DME component of the ILS for which data is being reported.

(51) Coordinates. Enter the latitude and longitude of the DME in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after to the latitude and an E or W after to the longitude.

(52) Elevation. Enter the ground elevation of the DME Antenna in feet, MSL, to the nearest tenth of a foot. If elevation is below sea level, precede the value by a minus sign (e.g., - 15 feet). (53) Dist to AER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the DME to the approach end of the runway (accounting for any displacements).

(54) Dist to DER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the DME to the stop/departure end of the runway.

(55) Standby Power. Choose the form of standby power as:

 Commercial  Engine  Battery  None

(56) Channel. Enter the DME channel number used for operation of the DME.

(57) Dist / Dir Offset from RWY C/L. Enter if the DME is left or right of runway centerline and enter the precise perpendicular distance to runway centerline (to the nearest foot).

01/31/2013 7900.2B Appendix A

VI. Inner Marker (IM). This section provides information that describes the inner marker component of the ILS for which data is being reported.

(58) Coordinates. Enter the latitude and longitude of the IM in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after to the latitude and an E or W after to the longitude.

(59) Elevation. Enter the ground elevation of the IM in feet, MSL, to the nearest tenth of a foot. If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

(60) Dist to AER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the IM to the approach end of the runway (accounting for any displacements).

(61) Dist to DER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the IM to the stop/departure end of the runway.

(62) Dist / Dir Offset from RWY C/L. Enter if the IM is left or right of runway centerline and enter the precise perpendicular distance to runway centerline (to the nearest foot).

VII. Middle Marker (MM). This section provides information that describes the middle marker component of the ILS for which data is being reported.

(63) Coordinates. Enter the latitude and longitude of the MM in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after to the latitude and an E or W after to the longitude.

(64) Elevation. Enter the ground elevation of the MM in feet to the nearest tenth of a foot, MSL. If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

(65) Dist to AER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the MM to the landing threshold at the approach end of the runway (accounting for any displacements).

(66) Dist to DER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the MM to the stop/departure end of the runway.

(67) Dist / Dir Offset from RWY C/L. Enter if the MM is left or right of runway centerline and enter the precise perpendicular distance to runway centerline (to the nearest foot).

(68) Name. Enter the name of the middle marker, or the collocated compass locator or NDB.

(69) Facility Type. Indicate the facility type of the MM as:

 Marker Only  LMM (Marker/NDB)

01/31/2013 7900.2B Appendix A

(70) Class. Indicate the class of the collocated compass locator or NDB as:

 LMM. Compass Locator station when installed at middle marker site (15 NM at all altitudes)

 MH. Non-directional radio beacon (homing) power less than 50 watts (25 NM at all altitudes)

 H. Non-directional radio beacon (homing) power 50 watts to less than 2000 watts (50 NM at all altitudes)

 HH. Non-directional radio beacon (homing) power greater than 2000 watts (75 NM at all altitudes)

(71) Frequency. Enter the frequency of the collocated NDB in MHz to the nearest thousandth.

VIII. Outer Marker (OM). This section provides information that describes the outer marker component of the ILS for which data is being reported.

(72) Coordinates. Enter the latitude and longitude of the OM in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after to the latitude and an E or W after to the longitude.

(73) Elevation. Enter the ground elevation of the OM in feet to the nearest tenth of a foot, MSL. If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

(74) Dist to AER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the OM to the approach end of the runway (accounting for any displacements).

(75) Dist to DER. Enter the distance (to the nearest foot) measured along the runway centerline from a point abeam the OM to the stop/departure end of the runway.

(76) Dist / Dir Offset from RWY C/L. Enter if the OM is left or right of runway centerline and enter the precise perpendicular distance to runway centerline (to the nearest foot).

(77) Name. Enter the name of the outer marker, or the collocated compass locator or NDB.

(78) Facility Type. Indicate the facility type of the OM as:

 Marker Only  LOM (Marker/NDB)

(79) Class. Indicate the class of the collocated compass locator or NDB as:

 LOM - Compass Locator station when installed at outer marker site (can be used for navigation at distances of approximately 15 NM at all altitudes)

 MH - Non-directional radio beacon (homing) power less than 50 watts (can be used for navigation at distances of approximately 25 NM at all altitudes)

01/31/2013 7900.2B Appendix A

 H - Non-directional radio beacon (homing) power 50 watts to less than 2000 watts (can be used for navigation at distances of approximately 50 NM at all altitudes)

 HH - Non-directional radio beacon (homing) power greater than 2000 watts (can be used for navigation at distances of approximately 75 NM at all altitudes)

(80) Freq. Enter the frequency of the collocated NDB in MHz to the nearest thousandth.

IX. Remarks. If there is insufficient space in any block, complete the entry in this block and reference the block number. If more space is required for remarks, attach additional pages and use only the Remarks section. Label the pages as Page 1 of 2, Page 2 of 2, etc. This space will also be used to enter any other pertinent data for which no space has been provided.

01/31/2013 7900.2B Appendix A

FAA Form 7900-6 Instrument Landing System (ILS) Form FAA Form 7900-6 ILS Form Information for Publica RespondentA-11

01/31/2013 7900.2B Appendix A

FAA Form 7900-6 Instrument Landing System (ILS) Form FAA Form 7900-6 ILS Form Page 1

01/31/2013 7900.2B Appendix A

FAA Form 7900-6 Instrument Landing System (ILS) Form FAA Form 7900-6 ILS Form Page 2

01/31/2013 7900.2B Appendix B

Appendix B: Navigational Aid Data Form Instructions

Appendix B: Navigational Aid Data Form Instructions

A. General. This form is used to submit navigational aid (NAVAID) data to the NFDC. NAVAIDs include distance measuring equipment (DME), non-directional beacons (NDB), tactical air navigation (TACAN) systems, very high frequency (VHF) omni-directional range (VOR) systems, VOR test facilities (VOT), and certain combinations of these systems.

This form should NOT be used to submit instrument landing system (ILS) data to the NFDC. There is a separate ILS data form that should be used to handle these submissions.

Submitters should carefully read all of the following instructions to ensure the preparation of complete and accurate submissions that can be processed in a timely manner.

B. Submission. For federally owned NAVAIDs, this form should be submitted to the NFDC by personnel within the NAVAID Engineering group within FAA ATO Technical Operations.

For non-federally owned NAVAIDs, this form should be submitted to the NFDC by personnel within the non-federal program implementation management group within the appropriate Regional Service Center under FAA ATO Mission Support Services.

For military owned NAVAIDs, this form should be submitted to the NFDC by authorized personnel within the appropriate service under the DoD.

C. Form Sections.

I. Submission. This section provides information related to submission of the data to the NFDC, including the contact information of the submitter, the name of the official who authorizes the changes to made, the purpose of the submission, and the estimated date that the changes will be effective.

(1) Name. Enter the name of the submitter.

(2) Organization. Enter the name of the submitter’s employer (organization and routing code, if applicable).

(3) Date. Enter the month, day, and year the form was prepared.

(4) Email. Enter the email address of the submitter.

(5) Phone. Enter the phone number (with area code) of the submitter.

(6) Authorizing Official. Enter the name of the official authorizing the changes to be made (i.e., facility manager, program director, lead engineer, etc.).

(7) Purpose of Submission. Select one of the following options to indicate the purpose for submitting the form:

 Changes to Existing System. Select this box if this form is being submitted to report changes to an existing NAVAID, e.g., addition of a DME.

01/31/2013 7900.2B Appendix B

 New System. Select this box if this form is being submitted to report a new NAVAID that has not been commissioned

 Decommission System. Select this box if this form is being submitted to report decommissioning of an existing NAVAID

(8) Proposed Effective Date. Enter the date that the reported changes will take effect. This date may be the same as the form preparation date; however, if this form is being used to provide advance notice of changes to the NFDC, the submitter should enter the date that those changes will take effect.

II. NAVAID. This section provides information that describes the NAVAID for which data is being reported.

(9) NAVAID ID. Enter the identifier of the NAVAID per FAA Order 7350.8.

(10) Type. Indicate the type of facility(ies) being reported as:

 DME - Distance Measuring Equipment  Doppler VOR - Doppler-based VOR  NDB - Non-Directional Beacon  NDB/DME - A co-located NDB and DME  TACAN - Tactical Air Navigation System  UHF/NDB - A co-located UHF Transmitter and NDB  VOR - VHF Omnidirectional Range  VOR/DME - A co-located VOR and DME  VORTAC - A co-located VOR and TACAN  VOT - VOR Test Facility

(11) Frequency (Freq). Enter the frequency of the NAVAID in MHz to at least the nearest tenth.

(12) Frequency License Number. Enter the license number that has been assigned to the frequency to authorize its use and publication. For FAA-owned systems, this number will be the Facility Transmitting Authorization (FTA) number assigned by FAA Spectrum Engineering. For non-federally-owned systems, this number will be the Federal Communications Commission (FCC) license number or “call sign” assigned by the FCC. For military-owned systems, this number will be the National Telecommunications and Information Administration (NTIA) serial number assigned by the FTIA.

(13) Channel. Enter the channel the NAVAID uses for transmission. This box should be completed for VORTAC, TACAN, and DME.

Note: See channel/VHF frequency pairings in FAA Order 6050.5.

(14) Owner Type. Choose the type of funding used for the facility as:

 Federal  Non-Federal  Military

01/31/2013 7900.2B Appendix B

(15) Owner. Enter the name of the organization or authority that owns the facility (e.g., FAA, U.S. Air Force, County Authority, State Authority).

(16) Operator. Enter the name of the organization or authority that operates the facility (e.g., FAA, U.S. Air Force, County Authority, State Authority).

(17) Operating Hours. Enter the hours of operation for the NAVAID.

(18) Voice Call. Enter the radio voice call that is used when using the voice capability of the NAVAID. If there is no voice capability, enter none.

(19) Located on/off airport. Indicate whether or not the NAVAID is located on an airport. If off airport, provide the distance in nautical miles (NM) from the nearest public use airport.

(20) Airport/Facility Name. Enter the airport name or name of the military airfield associated with the NAVAID per FAA Order 7350.8. If the NAVAID is not located on an airport, enter the name of the nearest public use airport.

(21) Airport Location (Loc) Identifier (ID). Enter the three character FAA location identifier or the four letter International Civil Aviation Organization (ICAO) location identifier of the associated airport per FAA Order 7350.8. If the NAVAID is not located on an airport, enter the identifier of the nearest public use airport.

(22) Location. Enter the city and state (for US) or city and country (for international) where the facility is located per FAA Order 7350.8.

(23) Standard Service Volume Class. Indicate the standard service volume of the NAVAID as (all altitudes are with respect to the site elevation of the NAVAID):

 T - Terminal – Altitude: 1000’ to 12,000’; Distance: 25 NM  L - Low – Altitude: 1000’ to 18,000’; Distance: 40 NM  H - High – Altitude: 1000’ to 14,500’; Distance: 40 NM

Altitude: 14,500’ to 18,000’; Distance: 100 NM Altitude: 18,000’ to 45,000’; Distance: 130 NM Altitude: 45,000’ to 60,000’; Distance: 100 NM

(24) Radio Class Codes. Indicate the radio class code of the NAVAID as:

 AB – Automatic Weather Broadcast  S – Simultaneous range homing signal and/or voice  W – Without voice on radio frequency

01/31/2013 7900.2B Appendix B

(25) Transmitter Indicator. Indicate the transmitter indicator as:

 Single  Dual  None

(26) Type of Standby Power. Indicate the type of standby power available to the NAVAID as:

 Battery  Commercial  Generator  None

(27) FSS Radio Call. Enter the Flight Service Station (FSS) radio call (i.e., associated/Local FSS name) associated with the NAVAID.

Note: Even though FSSs have been consolidated in the continental US, there is still a requirement to use the legacy radio calls associated with the NAVAID, e.g., Los Angeles (LAX) VORTAC (Hawthorne Radio), Montour (MMJ) VORTAC (Altoona Radio). For Alaska, this field will still reference the appropriate in-service FSS, e.g., King Salmon (AKN) VORTAC (Kenai FSS), Shemya (SYA) VORTAC (Cold Bay FSS).

(28) Geodetic Datum. Choose the applicable horizontal and vertical reference systems used for any geodetic data reported.

 Horizontal: NAD83 or WGS84  Vertical: NAVD88 or EGM96

(29) Coordinates. Enter the latitude and longitude of the NAVAID in degrees, minutes, and seconds to the nearest ten thousandth of a second, if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude, and an E or W after the longitude.

(30) Magnetic (Mag) Variation. Enter the magnetic variation of record for the NAVAID and the epoch year. If unknown, contact the National Flight Procedures Group.

(31) Elevation (MSL). Enter the ground elevation of the NAVAID in feet to the nearest tenth of a foot, mean sea level (MSL). If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

(32) Monitor Category Code. Indicate the monitoring category of the NAVAID as:

 1 – Internal monitoring plus a status monitor installed at control point.  2 – Internal monitoring with status indicator at control point inoperative but pilot reports indicated facility is operating normally.

 3 – Internal monitoring only. Status indicator not installed at control point.  4 – Internal monitor not installed. Remote status indicator provided at control point. (only applicable to NDB)

01/31/2013 7900.2B Appendix B

(33) TWEB Hours. Enter the hours of operation of the Transcribed Weather Broadcast (TWEB).

(34) TWEB Phone. Enter the phone number used to access the TWEB.

(35) NAS Use. Choose whether or not the NAVAID has been certified for NAS use.

(36) Simultaneous Voice Avail. Choose whether or not the NAVAID has simultaneous voice capability, i.e., Can voice be transmitted without interrupting the directional guidance?

(37) Automatic Voice ID Avail. Choose whether or not the NAVAID has an automatic voice identification capability.

(38) Hazardous Inflight Weather Advisory Service (HIWAS) Avail. Choose whether or not the NAVAID broadcasts hazardous weather information.

(39) Approved ESVs on File. Choose whether or not the NAVAID has any approved extended service volume(s) (ESV) on file.

(40) Is Low Alt NAVAID on High Alt Chart. Indicate whether or not the low altitude NAVAID meets the requirements for publication on the high altitude en-route chart, i.e., the NAVAID has ESV.

III. Remarks. Use the Remarks section if there is insufficient space in any data field and reference the data field number. If more space is required for remarks, attach additional pages and use only the Remarks section. Label the pages as Page 1 of 2, Page 2 of 2, etc. This space can also be used to enter any other pertinent data for which no space has been provided.

01/31/2013 7900.2B Appendix B

FAA Form 7900-2 NAVAID Data Form Page 1

01/31/2013 7900.2B Appendix C

Appendix C: Air Route Traffic Control Center (ATRCC) Data Form Instructions

Appendix C: Air Route Traffic Control Center (ATRCC) Data Form Instructions

A. General. This form is used to submit Air Route Traffic Control Center (ARTCC) and Center Radar Approach Control (CERAP), including Remote Center Air/Ground (RCAG) communication facilities, data to the NFDC.

Submitters should carefully read all of the following instructions to ensure the preparation of complete and accurate submissions that can be processed in a timely manner.

B. Authorized Submitters. This form should be submitted to the NFDC by personnel at the affected ARTCC facility.

C. Form Sections.

I. Submission. This section provides information related to submission of the data to the NFDC, including the contact information of the submitter, the name of the official who authorizes the changes to made, the purpose of the submission, and the estimated date that the changes will be effective.

(1) Name. Enter the name of the submitter.

(2) Organization. Enter the name of the submitter’s employer (organization and routing code, if applicable).

(3) Date. Enter the month, day, and year the form was prepared.

(4) Email. Enter the email address of the submitter.

(5) Phone. Enter the phone number (with area code) of the submitter.

(6) Authorizing Official. Enter the name of the official authorizing the changes to be made (i.e., facility manager, program director, safety and operations manager, etc.).

(7) Purpose of Submission. Select one of the following options to indicate the purpose for submitting the form:

 Changes to Existing ARTCC Facility. Select this box if this form is being submitted to report changes to an existing ARTCC or CERAP. The submitter will indicate the type(s) of change(s) being submitted in Item 20 under Section III

 New ARTCC Facility. Select this box if this form is being submitted to report a new ARTCC or CERAP that has not been commissioned

Note: When reporting a new ARTCC or CERAP facility, the submitter must first request an ARTCC/CERAP ID from the NFDC. Please refer to the NFDC website (http://nfdc.faa.gov) for details on how to contact the NFDC.

 Close/Decommission ARTCC Facility. Select this box if this form is being submitted to report decommissioning of an existing ARTCC or CERAP. For facility closure and decommissioning, the submitter is only required to complete section II of the form

01/31/2013 7900.2B Appendix C

Note: If reporting the closure or decommissioning of a Remote Center Air/Ground (RCAG) site, the submitter should not choose this box, but should choose Changes to Existing ARTCC Facility and then choose Del RCAG Site in item 20

(8) Proposed Effective Date. Enter the date that the reported changes will take effect. This date may be the same as the form preparation date; however, if this form is being used to provide advance notice of changes to the NFDC, the submitter should enter the date that those changes will take effect.

II. ARTCC Facility. This section provides basic information that describes the ARTCC facility for which data is being reported.

(9) Name. Enter the name of the ARTCC.

(10) Loc ID. Enter the FAA assigned 3-letter identifier of the ARTCC, e.g. ZOA, ZKC, ZDC, per FAA Order 7350.8.

(11) Computer ID. Enter the ARTCC assigned 3-letter computer identifier of the ARTCC, e.g., ZCO, ZCK, ZCW.

(12) ARTCC Reference Point. Enter the latitude and longitude of the ARTCC reference point in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude and an E or W after the longitude.

(13) Type. Select the type of facility being reported as:

 ARTCC  Center Radar Approach Control (CERAP)  Combined Control Facility (CCF)

(14) Apch/Dep Call. Enter the Approach/Departure Call for the ARTCC.

(15) Location (City, State, Country). Enter the city, state, and country where the facility is located per FAA Order 7350.8.

(16) Geodetic Datum. Choose the applicable horizontal and vertical reference systems used for any geodetic data reported.

 Horizontal: NAD83 or WGS84  Vertical: NAVD88 or EGM96

(17) Frequencies at ARTCC Facility. This form can be used to submit routine changes to the frequencies used by the ARTCC. For more extensive frequency changes than the form will accommodate (e.g., airspace and frequency re-sectorization), refer to the NFDC website (http://nfdc.faa.gov) to obtain the ARTCC facility/frequency record to include as an attachment to this form.

a. Action. Choose whether the frequency will be added (Add Freq), deleted (Del Freq), or if the altitude of the frequency is being changed (Change Altitude).

01/31/2013 7900.2B Appendix C

b. Frequency. Enter the frequency in MHz to the nearest hundredth. c. Altitude. Indicate the altitude of the frequency being reported as:

 Low (LO) – For use up to but not including 18,000' MSL  Low/High (L/H) – For use below and above 18,000’ MSL  High (HI) – For use at and above 18,000’ MSL  Ultra – High (UH) – For use from 18,000’ MSL to Flight Level (600) and

above

(18) Revision Type. Indicate the type(s) of changes being reported on the form.

 Add RCAG Site. Select this box to add a new RCAG site to an existing ARTCC facility, and complete Section III of the form

 Add Freq to RCAG. Select this box to add a new frequency to an existing RCAG site at an existing ARTCC facility, and complete Section III of the form

 Add Sat Airport to RCAG. Select this box to add a new satellite airport to a frequency at a RCAG site at an existing ARTCC facility, and complete Section IV of the form

 Add Radar Site. Select this box to add a new radar site to an existing ARTCC facility, and complete Section V of the form

 Change Existing Freq Altitude. Select this box to change the altitude of a frequency at a RCAG site at an existing ARTCC facility, and complete Section III of the form

 Change Existing Freq Usage. Select this box to change the usage of a frequency at a RCAG site at an existing ARTCC facility, and complete Section III of the form

 Del RCAG Site. Select this box to delete an existing RCAG site from an existing ARTCC facility, and complete Section III of the form

 Del Freq from RCAG. Select this box to delete an existing frequency from an existing RCAG site at an existing ARTCC facility, and complete Section III of the form

 Del Sat Airport from RCAG. Select this box to remove a satellite airport from a RCAG site at an existing ARTCC facility, and complete Section IV of the form

 Del Radar Site. Select this box to remove an existing radar site from an existing ARTCC facility, and complete Section V of the form

 Transfer Sat Airports Between Facilities. Select this box to transfer satellite airports between facilities (e.g., from an ARTCC to a TRACON), and complete Section IV of the form

 Other. Select this box if the changes being submitted to not fall under any of the previous categories, and explain the change in the Remarks section (Section VI)

01/31/2013 7900.2B Appendix C

III. RCAG Sites. This section provides information that describes the RCAG sites associated with the ARTCC facility. This form can be used to submit routine changes to the RCAG site and its associated frequencies, and multiple pages may be used as necessary. For more extensive frequency changes than the form will accommodate (e.g., airspace and frequency re-sectorization), refer to the NFDC website (http://nfdc.faa.gov) to obtain the ARTCC facility/frequency record to include as an attachment to this form.

(19) RCAG Sites.

a. Action. Indicate if the RCAG site is to be Added or Deleted by selecting the appropriate box.

b. Name. Enter the name of the RCAG site. c. ID. Enter the identifier of the RCAG site. d. State. Enter the two-letter abbreviation of the state where the RCAG site resides. e. Coordinates. Enter the latitude and longitude of the RCAG site in degrees, minutes, and seconds to the nearest ten thousandth of a second, if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude, and an E or W after the longitude.

f. Elevation (MSL). Enter the ground elevation of the RCAG site in feet to the nearest tenth of a foot, mean sea level (MSL). If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

g. Height (AGL). Enter the height of the RCAG antenna (i.e., the highest point of the RCAG antenna structure) in feet to the nearest tenth of a foot, above ground level (AGL).

(20) RCAG Frequencies.

a. Action. Choose whether the frequency will be added (Add Freq), deleted (Del Freq), if the altitude of the frequency is being changed (Change Altitude), or if the usage of the frequency is being changed (Change Usage).

b. Frequency. Enter the frequency in MHz to the nearest hundredth. Note: Only one (1) VHF / UHF frequency pair will be charted for each RCAG site on the En-Route Low or En-Route High chart.

c. RCAG Name. Enter the name of the RCAG Site that operates the frequency. d. Altitude. Indicate the altitude of the frequency being reported as:

 Low (LO) – For use up to but not including 18,000' MSL  Low/High (L/H) – For use below and above 18,000’ MSL  High (HI) – For use at and above 18,000’ MSL  Ultra – High (UH) – For use from 18,000’ MSL to Flight Level (600) and above e. Usage. Indicate the usage of the frequency as:

 For Charting (C)  Not for Charting (N)  Oceanic (O)

01/31/2013 7900.2B Appendix C

IV. Satellite Airports. This section provides information that describes the satellite airports that are served by the ARTCC facility.

(21) Add Satellite Airports to RCAG Frequency.

a. ARTCC Name. Enter the name of the ARTCC that controls the RCAG site that will now service the reported airports.

b. RCAG Name. Enter the name of the RCAG site that controls the frequency to which the satellite airports will be added.

c. RCAG ID. Enter the identifier of the RCAG site. d. Frequency. Enter the frequency in MHz to the nearest hundredth to which the satellite airports will be added.

e. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of all airports that will be serviced by the frequency, e.g., BVI, LBE, etc.

(22) Delete Satellite Airports from RCAG Frequency.

a. ARTCC Name. Enter the name of the ARTCC that controls the RCAG site that will no longer service the reported airports.

b. RCAG Name. Enter the name of the RCAG site that controls the frequency from which satellite airports will be removed.

c. RCAG ID. Enter the identifier of the RCAG site. d. RCAG Frequency. Enter the frequency in MHz to the nearest hundredth from which satellite airports will be removed.

e. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of all airports that will no longer be serviced by the frequency, e.g., BVI, LBE, etc.

(23) Transfer Satellite Airports Between ARTCC and TRACON Frequencies or Between RCAG Frequencies.

a. Action

 From. Indicate whether the satellite airports are being transferred from a frequency at a TRACON or ARTCC (RCAG)

 To. Indicate whether the satellite airports are being transferred to a frequency at a TRACON or ARTCC (RCAG)

b. TRACON/ARTCC Name. Enter the name of the TRACON or ARTCC that controls the frequency.

c. RCAG Name. If the frequency is controlled by an ARTCC, enter the name of the associated RCAG site that controls the frequency

d. RCAG ID. Enter the identifier of the RCAG site e. Frequency. Enter the frequency in MHz to the nearest hundredth that is involved in the transfer.

f. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of the airports that will be transferred between the ARTCC and TRACON or between the RCAG sites.

01/31/2013 7900.2B Appendix C

V. Radar Sites. This section provides information that describes the radar sites associated with the ARTCC facility.

(24) Radar Sites.

a. Action. Indicate if the Radar site is to be Added or Deleted by selecting the appropriate box.

b. Name. Enter the name of the radar site. c. ID. Enter the identifier of the radar site. d. Type. Indicate the type of radar at the site as:

 Automatic Dependent Surveillance – Broadcast (ADS-B)  Air Route Surveillance Radar (ARSR) Note: Selection of ARSR assumes that a secondary radar is present.

 Secondary Radar (SECRA) Note: Selection of SECRA implies that no ARSR is present (i.e., SECRA only).

e. State. Enter the two-letter abbreviation of the state where the radar site resides. f. Coordinates. Enter the latitude and longitude of the radar site in degrees, minutes, and seconds to the nearest ten thousandth of a second, if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude, and an E or W after the longitude.

g. Elevation (MSL). Enter the ground elevation of the radar site in feet to the nearest tenth of a foot, mean sea level (MSL). If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

h. Height (AGL). Enter the height of the radar antenna (i.e., the highest point of the radar antenna structure) in feet to the nearest tenth of a foot, above ground level (AGL).

VI. Remarks. Use the Remarks section if there is insufficient space in any data field and reference the data field number. If more space is required for remarks, attach additional pages and use only the Remarks section. Label the pages as Page 1 of 2, Page 2 of 2, etc. This space can also be used to enter any other pertinent data for which no space has been provided.

01/31/2013 7900.2B Appendix C

FAA Form 7900.1 Air Route Traffic Control Center (ARTCC) Data Form FAA Form 7900-1 ARTCC Data Form Page 1

01/31/2013 7900.2B Appendix C

FAA Form 7900-1 ARTCC Data Form Page 2

01/31/2013 7900.2B Appendix C

FAA Form 7900-1 ARTCC Data Form Page 3

01/31/2013 7900.2B Appendix C

FAA Form 7900-1 ARTCC Data Form Page 4

01/31/2013 7900.2B Appendix D

Appendix D: Terminal Air Traffic Control Facilities Data Sheet Instructions

A. General. This form is used to submit data describing terminal air traffic control facilities, include airport traffic control towers (ATCT), terminal radar approach control (TRACON) facilities (including both on airport and consolidated TRACON facilities), Remote Transmitter/Receivers (RTR), DoD Approach Control Facilities, and military ground controlled approach (GCA) facilities to the NFDC.

Appendix D: Terminal Air Traffic Control Facilities Data Sheet Instructions

Submitters should carefully read all of the following instructions to ensure the preparation of complete and accurate submissions that can be processed in a timely manner.

B. Authorized Submitters. For civil facilities, this form should be submitted to the NFDC by personnel at the affected control facility (i.e., ATCT or TRACON).

For military facilities, this form should be submitted to the NFDC by authorized personnel within the appropriate service under the DoD.

C. Form Sections.

I. Submission. This section provides information related to submission of the data to the NFDC, including the contact information of the submitter, the name of the official who authorizes the changes to made, the purpose of the submission, and the estimated date that the changes will be effective.

(1) Name. Enter the name of the submitter.

(2) Organization. Enter the name of the submitter’s employer (organization and routing code if applicable).

(3) Date. Enter the month, day, and year the form was prepared.

(4) Email. Enter the email address of the submitter.

(5) Phone. Enter the phone number (with area code) of the submitter.

(6) Authorizing Official. Enter the name of the official authorizing the changes to be made (i.e., facility manager, program director, etc.).

(7) Purpose of Submission. Select one of the following options to indicate the purpose for submitting the form:

a. Changes to Existing Control Facility – Select this box if this form is being

submitted to report changes to an existing facility. b. New Control Facility – Select this box if this form is being submitted to report a

facility that has been or will be newly commissioned. c. Close/Decommission Control Facility – Select this box if this form is being

submitted to report a facility that has been or will be decommissioned.

01/31/2013 7900.2B Appendix D

(8) Proposed Effective Date. Enter the date that the reported changes will take effect. This date may be the same as the form preparation date; however, if this form is being used to provide advance notice of changes to the NFDC, the submitter should enter the date that those changes will take effect.

II. Control Facility. This section provides basic information that describes the control facility for which data is being reported.

(9) Name. Enter the name of the control facility.

(10) Facility ID. Enter the FAA identifier of the control facility per FAA Order 7350.8. For ATCT, enter the FAA airport identifier of the airport where the facility is located.

(11) Facility Type. Indicate the type of control facility being reported as:

a. ATCT – Airport Traffic Control Tower, but does not provide approach control b. ATCT-A/C – Airport Traffic Control Tower plus non-radar approach control c. ATCT-ARAC – Airport Traffic Control Tower plus Army Approach Control (Army) d. ATCT-GCA – Airport Traffic Control Tower plus Ground Control Approach e. ATCT-RAPCON – Airport Traffic Control Tower plus Radar Approach Control (Air Force) f. ATCT-RATCF – Airport Traffic Control Tower plus Radar Approach Control (Navy) g. ATCT-TRACON – Airport Traffic Control Tower plus Terminal Radar Approach Control h. CCF – Combined Control Facility i. Csldtd TRACON – Consolidated TRACON (i.e., stand-alone TRACON, such as PCT, Potomac TRACON)

(12) Location (City, State, Country). Enter the city, state, and country where the control facility is located.

(13) Apch/Dep Call. Enter the primary approach/departure call for the control facility.

(14) Operator. Indicate the primary operator of the control facility as:

a. Federal Aviation Administration b. FAA Contract Tower c. Federal Government – Not USA d. Non-Fed Controlled Tower e. City f. County g. Canadian Ministry of Transport h. Other (If other, indicate the name of the operator)

(15) Apch/Dep Hours. Enter the hours (and days, if applicable) when the control facility provides approach/departure control services. If the facility provides apch/dep control services for 24 hours, enter 24 in this field. All other hours should be entered as is, in local time, using

01/31/2013 7900.2B Appendix D

the 24 hour clock. For example, if apch/dep control services are provided from 7:00 AM to 9:00 PM, enter 0700 – 2100 in this field.

(16) Secondary Apch/Dep Facility ID. If the facility does not provide 24-hour control services, enter the identifier of the control facility that provides the control services after hours.

(17) Tower Hours. Enter the hours (and days, if applicable) when the tower is open. If the tower is open for 24 hours, enter 24 in this field. All other hours should be entered as is, in local time, using the 24 hour clock. For example, if the tower is open from 7:00 AM to 9:00 PM, enter 0700 – 2100 in this field.

Note: Leave this field blank when reporting a consolidated TRACON.

(18) ATIS. Choose whether or not an Automatic Terminal Information System (ATIS) is located at the tower. If yes, provide the following data:

a. Digital – Choose whether or not the ATIS is available in digital format. b. ATIS Hours – Enter the hours of operation of the ATIS. c. ATIS Phone Number – Enter the phone number used to access the ATIS.

(19) Geodetic Datum. Choose the applicable horizontal and vertical reference systems used for any geodetic data reported.

 Horizontal: NAD83 or WGS84  Vertical: NAVD88 or EGM96

(20) Revision Type. Indicate the type(s) of changes being reported on the form.

 Add Freq. Select this box to add a new frequency to a control facility, and complete Section III of the form  Add Satellite Airport. Select this box to add a new satellite airport to a Frequency at a control facility, and complete Section V of the form  Add Control Operations. Select this box to add a new control service to a control facility, and complete Section IV of the form  Add Radar Site. Select this box to add a new radar site to a control facility, and complete Section VI of the form  Del Freq. Select this box to delete a frequency from a control facility, and complete Section III of the form  Del Satellite Airport. Select this box to delete a satellite airport from a Frequency at a control facility, and complete Section V of the form  Del Control Operations. Select this box to delete a control service from a control facility, and complete Section IV of the form  Del Radar Site. Select this box to remove an existing radar site from a control facility, and complete Section V of the form  Change Existing Freq Use. Select this box to change the use of a frequency at a control facility, and complete Section III of the form

01/31/2013 7900.2B Appendix D

 Change Existing Freq Sector. Select this box to change the sectorization of a frequency at a control facility, and complete Section III of the form

 Transfer Satellite Airport between Facilities. Select this box to transfer satellite airports between control facilities (i.e., tower, TRACON, ARTCC), and complete Section V of the form

 Other. Select this box if the changes being submitted to not fall under any of the previous categories, and explain the change in the Remarks section (Section VII)

III. Tower/Tracon Frequencies. This section provides information that describes the frequencies associated with the air traffic control (ATC) facility (i.e., tower or TRACON). This form can be used to submit routine changes to the frequencies used by the ATC facility. For more extensive frequency changes than the form will accommodate (e.g., airspace and frequency re-sectorization), refer to the NFDC website (http://nfdc.faa.gov) to obtain the tower or TRACON facility/frequency record to include as an attachment to this form.

(21) Frequencies.

a. Action. Choose whether the frequency will be added (Add Freq), deleted (Del Freq), if the use of the frequency is being changed (Change Use), or if the sectorization of the frequency is being changed (Change Sector).

b. Frequency Pair. Enter each frequency in MHz to the nearest thousandth. c. Use. Indicate the air traffic control use of the frequency:

 APCH – Approach Control  AS ASGN – As Assigned  ATIS – Automatic Terminal Information System  CD – Clearance Delivery  Class B – Class B Advisory (VFR Landing, Transitions, etc.)  Class C – Class C Advisory (VFR Landing, Transitions, etc.)  D-ATIS – Digital ATIS  DEP – Departure Control  EMERG – Emergency  GND – Ground Control  LCL – Local  PRM – Precision Runway Monitor  RDR – Radar  Other – Specify in the Remarks section d. Role. Indicate the role of the frequency as:

 Primary  Secondary e. IC. Indicate whether or not the frequency is used for initial contact.

01/31/2013 7900.2B Appendix D

f. Sectorization. Enter the airspace sector in which the frequency is used. Sectorization can be denoted based on a range of NAVAID radials (normally from the primary NAVAID at the airport), a control tower physical location (when more than one tower on the airport, e.g., O’Hare Tower North), directionality, or runway number denoting arrival and departure flows. This field should not be used to define vertical limits within approach control.

Refer to the following table as guidance when providing the sectorization for a frequency:

If the use of the frequency is: Then the sectorization should be:

APCH, DEP, APCH/DEP Range of NAVAID Radials (e.g., 111 – 270, 271 – 110)

ATIS, D-ATIS Arrival (ARR), Departure (DEP), or Both (ARR/DEP) GND, Class B Directionality (e.g., N, W, NW) LCL, PRM Runway(s) Served (e.g., Ry 18L, Ry 11/29) AS ASGN, CD, EMERG N/A

IV. Satellite Airports. This section provides information that describes the satellite airports that are served by the ATC facility.

(22) Add Satellite Airports to Control Facility.

a. Frequency. Enter the frequency in MHz to the nearest thousandth to which the satellite airports will be added.

b. Use. Indicate the air traffic control use of the frequency (see Item (21)c for a list of options).

c. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of all airports that will be serviced by the frequency, e.g., BVI, LBE, etc.

(23) Delete Satellite Airports from Control Facility.

a. Frequency. Enter the frequency in MHz to the nearest hundredth from which satellite airports will be removed.

b. Use. Indicate the air traffic control use of the frequency (see Item (21)c for a list of options)

c. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of all airports that will no longer be serviced by the frequency, e.g., BVI, LBE, etc.

(24) Transfer Satellite Airports Between Control Facilities

a. Action.

 From. Indicate the control facility from which the satellite airports are being transferred

 To. Indicate the control facility to which the satellite airports are being transferred

b. Facility ID. Enter the FAA identifier of the control facility per FAA Order 7350.8. For ATCT, enter the FAA airport identifier of the airport where the facility is located.

01/31/2013 7900.2B Appendix D

c. Frequency. Enter the frequency in MHz to the nearest thousandth that is involved in the transfer.

d. Use. Indicate the air traffic control use of the frequency (see Item (21)c for a list of options).

e. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of the airports that will be transferred between the control facilities.

V. CONTROL OPERATIONS. This section provides information that describes the control operations that are provided by the ATC facility.

(25) ADD Air Traffic Control Systems/Services Available from Facility. Choose what system(s) and/or service(s) will be added to the tower or TRACON (including consolidated TRACONs):

 ARTS-IIE – Automated Radar Terminal System, Version 2E  ARTS-IIIE – Automated Radar Terminal System, Version 3E  ASDE-X – Airport Surface Detection Equipment, Version X  Basic Radar Svc – Basic Radar Services  BRITE – Bright Radar Indicator Tower Equipment  Class B – Class B Traffic and Advisory Services  Class C – Class C Traffic and Advisory Services  CA – Conflict Alert  ITWS – Integrated Terminal Weather System  LAWRS – Limited Aviation Weather Reporting Station  LLWAS – Low Level Wind Shear Alert System  MSAW – Minimum Safe Altitude Warning  Radar Vectoring  SAWS – Stand Alone Weather System  SAWRS – Supplementary Aviation Weather Reporting Station  STARS – Standard Terminal Automation Replacement System  TDWR – Terminal Doppler Weather Radar  TRSA – Terminal Radar Service Area  VFR Advisory – Visual Flight Rules Advisory  WEF – Wind Equipment F-420 type  WHDE – Wind Hazard Detection Equipment  WMS – Wind Measuring Equipment  WSP – Weather Systems Processor  Other – Specify in the Remarks section

(26) DEL Air Traffic Control Systems/Services Available from Facility. Choose what system(s) and/or service(s) will be removed from the tower or TRACON (including consolidated TRACONs). The list of available options is the same as provided for Item 24 (see above).

(27) Controlled Airspace. Choose the class(es) of airspace in the terminal area that are controlled by the control tower facility, and the effective hours of the airspace control.

01/31/2013 7900.2B Appendix D

a. Class. Choose the airspace class that is present in the terminal area. General definitions of each airspace class from the FAA Aeronautical Information Manual are included below for reference (for more comprehensive definitions and operating requirements, consult the FAA Aeronautical Information Manual):

 Class B – Controlled airspace from the surface to 10,000 feet mean sea level (MSL) surrounding the nation’s busiest airports in terms of IFR operations or passenger enplanements

 Class C – Controlled airspace from the surface to 4,000 feet (MSL) above the airport elevation surrounding those airports that have an operational control tower, are serviced by radar approach control, and that have a certain number of IFR operations or passenger enplanements

 Class D – Controlled airspace from the surface to 2,500 feet (MSL) above the airport elevation surrounding those airports that have an operational control tower

 Class E – Controlled airspace that is not designated as Class B, Class C, or Class D

 Class G – Uncontrolled airspace that is not designated as Class B, Class C, Class D, or Class E

b. Effective Hours. Enter the hours (and days, if applicable) during which the airspace control is effective. If the airspace is effective for 24 hours, enter 24 in this field. All other hours should be entered as is, in local time, using the 24 hour clock.

VI. RADAR. This section provides information that describes the radar sites that are associated with the ATC facility.

(28) Radar Sites.

a. Action. Choose whether the radar site will be added (Add) or deleted (Del). b. Type. Indicate the type(s) of radar at the site as:

 ASR - Airport Surveillance Radar (include version)  BCN – Beacon Radar (includes Air Traffic Control Beacon Interrogator (ATCBI) and Air Traffic Control Radar Beacon (ATCRB))

 PAR – Precision Approach Radar c. Hours. Enter the hours of operation for the radar. If the radar operates for 24 hours, enter 24 in this field. All other hours should be entered as is, in local time, using the 24 hour clock. For example, if the radar operates from 7:00 AM to 9:00 PM, enter 0700 – 2100 in this field

d. Latitude. Enter the latitude of the radar site in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude.

e. Elevation (MSL). Enter the ground elevation of the radar site in feet to the nearest tenth of a foot, mean sea level (MSL). If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

f. Height (AGL). Enter the height of the radar antenna (i.e., the highest point of the radar antenna structure) in feet to the nearest tenth of a foot, above ground level (AGL).

VII. Remarks. Use the Remarks section if there is insufficient space in any data field and reference the data field number. If more space is required for remarks, attach additional pages and

01/31/2013 7900.2B Appendix D

use only the Remarks section. Label the pages as Page 1 of 2, Page 2 of 2, etc. This space can also be used to enter any other pertinent data for which no space has been provided.

01/31/2013 7900.2B Appendix D

FAA Form 7900.4 Terminal Air Traffic Control Facilities Data Form FAA Form 7900-4 Terminal ATC Facilities Data Form Page 1

01/31/2013 7900.2B Appendix D

FAA Form 7900.4 Terminal Air Traffic Control Facilities Data Form FAA Form 7900-4 Terminal ATC Facilities Data Form Page 2

01/31/2013 7900.2B Appendix D

FAA Form 7900.4 Terminal Air Traffic Control Facilities Data Form FAA Form 7900-4 Terminal ATC Facilities Data Form Page 3

01/31/2013 7900.2B Appendix E

Appendix E: Weather (WX) System Data Sheet Instructions

Appendix E: Weather (WX) System Data Sheet Instructions

A. General. This form is used to submit weather (WX) system (e.g., Automated Surface Observing System (ASOS) and Automated Weather Observing System (AWOS)) data to the NFDC.

Submitters should carefully read all of the following instructions to ensure the preparation of complete and accurate submissions that can be processed in a timely manner.

B. Authorized Submitters. For federally owned weather systems, this form should be submitted to the NFDC by personnel within the safety and operations support group within FAA ATO Technical Operations.

For non-federally owned weather systems, this form should be submitted to the NFDC by personnel within the non-federal program implementation management group within the appropriate Regional Service Center under FAA ATO Mission Support Services.

For military owned weather systems, this form should be submitted to the NFDC by authorized personnel within the appropriate service under the DoD.

C. Form Sections.

I. Submission. This section provides information related to submission of the data to the NFDC, including the contact information of the submitter, the name of the official who authorizes the changes to made, the purpose of the submission, and the estimated date that the changes will be effective.

(1) Name. Enter the name of the submitter.

(2) Organization. Enter the name of the submitter’s employer (organization and routing code, if applicable).

(3) Date. Enter the month, day, and year the form was prepared.

(4) Email. Enter the email address of the submitter.

(5) Phone. Enter the phone number (with area code) of the submitter.

(6) Authorizing Official. Enter the name of the official authorizing the changes to be made (i.e., facility manager, program director, lead engineer, etc.).

(7) Purpose of Submission. Select one of the following options to indicate the purpose for submitting the form:

 Changes to Existing System. Select this box if this form is being submitted to report changes to an existing weather system

 New System. Select this box if this form is being submitted to report a weather system that has been or will be newly commissioned

01/31/2013 7900.2B Appendix E

 Decommission System .Select this box if this form is being submitted to report decommissioning of an existing weather system

(8) Proposed Effective Date. Enter the date that the reported changes will take effect. This date may be the same as the form preparation date; however, if this form is being used to provide advance notice of changes to the NFDC, the submitter should enter the date that those changes will take effect.

II. Weather (WX) System. This section provides information that describes the WX Station for which data is being reported.

(9) WX System ID. Enter the identifier of the weather system.

Note: A weather system ID should only be entered for existing weather systems. This field should be left blank for new weather systems. NFDC will assign a location identifier to all new weather systems in accordance with FAA Order 7350.8.

(10) WX System Type. Indicate the type of weather system as:

 ASOS. An Automated Surface Observing System (ASOS) that measures and reports all parameters of the AWOS-3P/T/Z (see below)

 AWOS-A . An AWOS that measures and reports altimeter only  AWOS-AV. An AWOS that measures and reports altimeter and visibility  AWOS-1. An AWOS that measures and reports wind data, e.g., speed, direction, and gusts; temperature; dew point; altimeter; and density altitude

 AWOS-2. An AWOS that measures and reports all parameters of the AWOS­ 1 plus visibility  AWOS-3. An AWOS that measures and reports all parameters of the AWOS­ 2 plus precipitation accumulation (rain gauge) and cloud height  AWOS-4. An AWOS that measures and reports all parameters of the AWOS­ 3P/T plus freezing rain and/or runway surface condition Note: When choosing AWOS-4, the submitter must select either freezing rain (Z) or runway surface condition (R) in Item (11).

 AWSS. An Automated Weather Sensor System (AWSS) has the same capabilities as an ASOS

 Other. Specify in the Remarks section

(11) Additional Certified WX Sensor(s). Indicate any certified weather sensors (in accordance with FAA Order 7900.5 and/or Advisory Circular 150-5220-16) that are included as part of the weather system configuration:

 P – Present Weather Sensor (e.g., precipitation type and intensity)  T – Thunderstorm/Lightning Sensor  Z – Freezing Rain Sensor  R – Runway Surface Condition Sensor  Other – Specify in the Remarks section

01/31/2013 7900.2B Appendix E

(12) Owner Type. Choose the type of funding used for the facility as:

 Federal  Non-Federal  Military

(13) Owner. Enter the name of the organization or authority that owns the weather system (e.g., FAA, National Weather Service (NWS), US Air Force, State Authority).

(14) Frequency. Enter the frequency (in MHz to the nearest thousandth) used by the system to broadcast weather information.

(15) Frequency License Number. Enter the license number that has been assigned to the frequency to authorize its use and publication. For FAA-owned systems, this number will be the Facility Transmitting Authorization (FTA) number assigned by FAA Spectrum Engineering. For non-federally-owned systems, this number will be the Federal Communications Commission (FCC) license number or “call sign” assigned by the FCC. For military-owned systems, this number will be the National Telecommunications and Information Administration (NTIA) serial number assigned by the FTIA.

(16) WX System Phone No. Enter the phone number used to obtain data from the weather system.

(17) Geodetic Datum. Choose the applicable horizontal and vertical reference systems used for any geodetic data reported.

 Horizontal: NAD83 or WGS84  Vertical: NAVD88 or EGM96

(18) Sensor Site Elevation (MSL). Enter the ground elevation of the weather system sensor site in feet, to the nearest foot, mean sea level (MSL). If elevation is below sea level, precede the value by a minus sign (e.g., -15 feet).

(19) Sensor Height (AGL). Enter the height of the weather sensor antenna (i.e., the highest point of the weather sensor structure) in feet to the nearest tenth of a foot, above ground level (AGL).

(20) Location. Enter the city, state, and country where the weather system is located.

(21) WX System Sensor Site Coordinates. Enter the latitude and longitude of the weather system sensor site in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude, and an E or W after the longitude.

01/31/2013 7900.2B Appendix E

(22) WX System Site Association. Indicate the nearest facility to the weather system sensor site based on the options provided.

 Stand Alone. System is not associated with an airport and not associated with a NAVAID

 On Airport. System is located on an airport. Provide the identifier of the airport

(23) WX System Co-located with NAVAID. Indicate whether or not the weather sensor site is co-located with a NAVAID. If yes, provide the identifier of the NAVAID.

(24) WX System Transmits over NADIN/WMSCR Service A. Indicate whether or not the weather system transmits weather reports over the National Airspace Data Interchange Network (NADIN).

(25) WX Reporting Services. Indicate the type of weather reporting services provided by the weather system to support NADIN/WMSCR as:

 METAR – Aviation Routine Weather Report (ICAO)  NOTAM – Notices to Airmen  SD – RADAR Weather Report  SPECI – Special Report (METAR)  TAF – Terminal Forecast  UA – Aircraft Report (PIREP)  WST – Convective SIGMET  Other – Specify in the Remarks section

III. Remarks. Use the Remarks section if there is insufficient space in any data field and reference the data field number. If more space is required for remarks, attach additional pages and use only the Remarks section. Label the pages as Page 1 of 2, Page 2 of 2, etc. This space can also be used to enter any other pertinent data for which no space has been provided.

01/31/2013 7900.2B Appendix E

FAA Form 7900.5 Weather (WX) System Data Form FAA Form 7900-5 Weather System Data Form Information for Public Respondent

01/31/2013 7900.2B Appendix E

FAA Form 7900.5 Weather (WX) System Data Form FAA Form 7900-5 Weather System Data Form Page 1

01/31/2013 7900.2B Appendix F

Appendix F: Flight Service Stations Data Sheet Instructions

Appendix F: Flight Service Stations Data Sheet Instructions

A. General. This form is used to submit data describing Flight Service Stations (FSS) and Radio Communication Outlets (RCO) to the NFDC.

Submitters should carefully read all of the following instructions to ensure the preparation of complete and accurate submissions that can be processed in a timely manner.

B. Authorized Submitters. This form should be submitted to the NFDC by personnel within the Flight Services Program Operations Office within the FAA ATO System Operations. For FSS located in Alaska, this form should be submitted to the NFDC by personnel within the Alaska FAA Flight Services Information Area Group (AFSIAG) within the FAA ATO System Operations.

C. Form Sections.

I. Submission. This section provides information related to submission of the data to the NFDC, including the contact information of the submitter, the name of the official who authorizes the changes to made, the purpose of the submission, and the estimated date that the changes will be effective.

(1) Name. Enter the name of the submitter.

(2) Organization. Enter the name of the submitter’s employer (organization and routing code, if applicable).

(3) Date. Enter the month, day, and year the form was prepared.

(4) Email. Enter the email address of the submitter.

(5) Phone. Enter the phone number (with area code) of the submitter.

(6) Authorizing Official. Enter the name of the official authorizing the changes to be made (i.e., facility manager, program director, safety and operations manager, etc.).

(7) Purpose of Submission. Select one of the following options to indicate the purpose for submitting the form:

 Changes to Existing FSS. Select this box if this form is being submitted to

report changes to an existing FSS, e.g., reporting new frequencies  New FSS. Select this box if this form is being submitted to report an FSS that

will be newly commissioned  Close/Decommission FSS. Select this box if this form is being submitted to

report decommissioning of an existing FSS Note: If reporting the closure or decommissioning of a RCO site, the submitter should not choose this box, but should choose Changes to Existing Facility and then choose Del RCO Site in item 21.

01/31/2013 7900.2B Appendix F

(8) Proposed Effective Date. Enter the date that the reported changes will take effect. This date may be the same as the form preparation date; however, if this form is being used to provide advance notice of changes to the NFDC, the submitter should enter the date that those changes will take effect.

II. Facility. This section provides information that describes the Flight Service Station for which data is being reported.

(9) Name. Enter the name of the facility.

(10) ID. Enter the identifier of the facility.

(11) Type. Indicate the type of facility being reported as:

 FSS. Flight Service Station  HUB. Flight Service Station Hub  BASEOPS. Military Base Operations

(12) Local Phone Number. Enter the local phone number used for administrative purposes.

(13) Toll Free Phone Number(s). Enter the toll free phone number(s) dedicated to briefings and other services provided by the FSS.

(14) Coordinates. Enter the latitude and longitude of the FSS in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude, and an E or W after the longitude.

(15) Located on airport. Indicate whether or not the FSS is located on the airport. If yes, enter the identifier of the airport in the space provided.

(16) Location. Enter the city, state, and country where the facility is located.

(17) Owner. Enter the name of the organization or authority that owns the facility (e.g., FAA, FAA Contractor, U.S. Air Force, County Authority, State Authority).

(18) Operator. Enter the name of the organization or authority that operates the facility (e.g., FAA, FAA Contractor, U.S. Air Force, County Authority, State Authority).

(19) Operating Hours. Enter the operating hours of the facility. If the facility provides services for 24 hours, enter 24 in this field. All other hours should be entered as is, in local time, using the 24 hour clock. For example, if control services are provided from 7:00 AM to 9:00 PM, enter 0700 – 2100 in this field.

(20) Secondary FSS Name. If the facility does not provide 24-hour flight services, enter the name of the facility that provides the flight services after hours.

01/31/2013 7900.2B Appendix F

(21) Secondary FSS ID. If the facility does not provide 24-hour flight services, enter the identifier of the facility that provides the flight services after hours.

(22) Geodetic Datum. Choose the applicable horizontal and vertical reference systems used for any geodetic data reported.

 Horizontal: NAD83 or WGS84  Vertical: NAVD88 or EGM96

(23) AFIS. Choose whether or not an Automatic Flight Information System (AFIS) is available from the FSS. If yes, provide the following data:

a. Digital. Choose whether or not the AFIS is available in digital format. b. AFIS Hours. Enter the hours of operation of the AFIS. c. AFIS Phone Number. Enter the phone number used to access the AFIS.

(24) FSS Frequencies. List the frequencies available at the FSS:

a. Action. Choose whether the frequency will be added (Add) or deleted (Del). b. Frequency. Enter each frequency in MHz to the nearest hundredth. c. Type. Indicate the type of frequency being reported as:

 Advisory. The frequency is used to provide airport advisory service.  Primary (Discrete). The primary frequency used by the FSS to provide flight services

 Secondary. A secondary frequency used by the FSS to provide flight services  Other. The frequency does not fit one of the three options above. Specify the type of frequency in the remarks section

III. Remote Communication Outlets (RCO). This section is used to provide data describing the RCOs that are associated with an FSS. This section also applies to Self Sustained Outlets (SSO), and for the purpose of reporting data to the NFDC, SSOs will be referred to as RCOs. When adding an RCO, the submitter will provide the location of the RCO in Item 21 and then list the applicable frequency(ies) in Item 22. When deleting an existing RCO site, the submitter can provide the idata using only Item 21. When adding, deleting, or changing (i.e., delete old plus add new) frequencies from an existing RCO, the submitter can provide the data using only Item 22.

(25) RCO Sites.

a. Action. Choose whether the RCO site will be added (Add) or deleted (Del). b. Comm ID. Enter the three character communication identifier of the RCO. c. Name. Enter the name of the RCO. d. Latitude. Enter the latitude of the RCO in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an N or S after the latitude.

e. Longitude. Enter the longitude of the RCO in degrees, minutes, and seconds to the nearest ten thousandth of a second if available (coordinates must be provided to the nearest hundredth of a second at a minimum). Enter an E or W after the longitude.

01/31/2013 7900.2B Appendix F

(26) RCO Frequencies.

a. Action. Choose whether the frequency will be added (Add) or deleted (Del). b. Frequency. Enter each frequency in MHz to the nearest thousandth. c. Comm ID. Enter the three character communication identifier of the RCO that transmits over the frequency.

IV. Satellite Airports. This section provides information that describes the satellite airports that are served by the RCOs.

(27) Add Satellite Airports to RCO Frequency.

a. FSS Name. Enter the name of the FSS that controls the RCO site that will now service the reported airports.

b. RCO Name. Enter the name of the RCO site that controls the frequency to which the satellite airports will be added.

c. RCO ID. Enter the identifier of the RCO site. d. Frequency. Enter the frequency in MHz to the nearest hundredth to which the satellite airports will be added.

e. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of all airports that will be serviced by the frequency, e.g., BVI, LBE, etc.

(28) Delete Satellite Airports from RCO Frequency.

a. FSS Name. Enter the name of the FSS that controls the RCO site that will no longer service the reported airports.

b. RCO Name. Enter the name of the RCO site that controls the frequency from which satellite airports will be removed.

c. RCO ID. Enter the identifier of the RCO site. d. Frequency. Enter the frequency in MHz to the nearest hundredth from which satellite airports will be removed.

e. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of all airports that will no longer be serviced by the frequency, e.g., BVI, LBE, etc.

(29) Transfer Satellite Airports Between RCO Frequencies.

a. Action.

 From. Enter the information (items b-f) for the RCO site from which the satellite airports are being transferred

 To. Enter the information (items b-f) for the RCO site to which the satellite airports are being transferred

b. FSS Name. Enter the name of the FSS that controls the frequency. c. RCO Name. Enter the name of the associated RCO site that controls the frequency.

d. RCO ID. Enter the identifier of the RCO site. e. Frequency. Enter the frequency in MHz to the nearest hundredth that is involved in the transfer.

f. Serviced Airport IDs. Enter the FAA three-character airport identifier(s) of the airports that will be transferred between the RCO sites

01/31/2013 7900.2B Appendix F

V. Remarks. Use the Remarks section if there is insufficient space in any data field and reference the data field number. If more space is required for remarks, attach additional pages and use only the Remarks section. Label the pages as Page 1 of 2, Page 2 of 2, etc. This space can also be used to enter any other pertinent data for which no space has been provided.

01/31/2013 7900.2B Appendix F

FAA Form 7900.3 Flight Service Station Data Form FAA Form 7900-3 Flight Service Station Data Form Page 1

01/31/2013 7900.2B Appendix F

FAA Form 7900-3 Flight Service Station Data Form Page 2