Radar Vectors
FAA Order Current Issued Sep 14, 2023 AJW-121 80 pages Copy saved Nov 18, 2026

Order FAA 6700.20C Approval, Operation, and Oversight of Non-federal Systems

Official source ↗ Open PDF

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

ORDER 6700.20C

National Policy Effective date:

09/14/2023

SUBJ: Approval, Operation, and Oversight of Non-federal Systems

Federal Aviation Administration (FAA) Order 6700.20, Approval, Operation, and Oversight of Non-federal Systems, establishes policy for the FAA’s Advanced Systems Design Service Team (ASDS). ASDS is responsible for implementing and managing the FAA’s Non-federal Program under the direction of the Air Traffic Organization. Title 49 of the United States Code, Sub-Title VII, Aviation Programs, authorizes the FAA to regulate non-federal systems. ASDS performs that regulatory function. ASDS manages the approval of non-federal systems designed for use in the National Airspace System (NAS). The team also regulates non-federal systems’ lifecycles, i.e., ownership, installation, commissioning, operation, maintenance, and decommissioning. Lastly, ASDS is responsible for the assumption of ownership of non-federal systems.

The guidance in this order is applicable throughout the NAS. The order outlines policy for nonfederal system lifecycles. It identifies the qualifications for federal and non-federal personnel associated with the maintenance and inspection of non-federal systems.

The appendices to this order include supporting documents for the Non-federal Program. ASDS has the discretion to amend these appendices to reflect changes in processes, as needed.

Polly Trottenberg Acting Administrator

Distribution: Electronic Initiated By: AJW-121

Table of Contents

Paragraph Page

i

Chapter 1. General Information … 1

1. Purpose of This Order … 1 2. Audience … 1 3. Where Can I Find This Order … 1 4. What This Order Cancels … 1 5. Explanation of Policy Changes … 1 6. Internet Links … 2 7. Geographical Scope … 2 8. Interpretations … 2 9. Common Terms Used in This Order … 3 10. Navigating This Order … 3

Chapter 2. Roles and Responsibilities … 5

1. Division of Duties … 5 2. Technical Operations (AJO/AJW) … 5 3. Director of Operations Support (AJO/AJW-1) … 5 4. NAS Modernization Group Manager (AJO/AJW-12) … 6 5. Advanced Systems Design Service (ASDS) Team Manager (AJO/AJW-121) … 6 6. Other Operations Support Directorate Staff (AJO/AJW-1) … 7 7. Service Area Technical Operations (AJO/AJW-W/C/E) … 8 8. Facilities & Engineering Services (AJO/AJW-2) … 9 9. NAS Security & Enterprise Operations (AJO/AJW-B) … 9 10. Logistics Center (AJO/AJW-L) … 10 11. Air Traffic Services (AJO/AJT) … 10 12. Flight Program Operations (AJO/AJF) … 10 13. Mission Support Services (AJO/AJV) … 10 14. Program Management Organization (AJO/AJM) … 12 15. Safety & Technical Training (AJO/AJI) … 13 16. System Operations Services (AJO/AJR) … 13 17. Airports (ARP) … 13 18. Security & Hazardous Materials Safety (ASH) … 13 19. Aviation Safety (AVS) … 13 20. Office of NextGen (ANG) … 14 21. Finance and Management (AFN) … 14

Chapter 3. Non-federal Systems Design Approval … 15

1. Design Approval … 15 2. Process Phases … 15 3. Intake … 15 4. First Decision Point … 16 5. Transition … 17 6. Assessment … 17 7. Second Decision Point … 18 8. Decision Notification … 18 9. Commission … 18

Table of Contents (continued)

Paragraph Page

ii

10. Configuration Management (CM) … 18 11. System Modification Requests … 19 12. Change in Ownership … 19 13. Advancements Requiring Improvements … 20

Chapter 4. Operating Life Cycle … 21

1. Decision to Install a Non-federal System … 21 2. Systems Identified in Part 171 … 21 3. Systems Not Identified in Part 171 … 21 4. Backup Weather Equipment … 22 5. Program Coordination … 22 6. Guidelines for Installation … 22 7. Guidelines for Commissioning … 24 8. Reimbursable Maintenance Agreements … 24 9. Decommissioning … 25

Chapter 5. Assumption of Ownership … 27

1. General … 27 2. AC 170-9, Criteria for Assumption of Ownership of Non-Federal Systems … 27 3. SOP 6700-5, Assumption of Ownership Process Flowchart … 27 4. System Eligibility … 27 5. Automatic Disapprovals … 27 6. Joint Investment Effort … 27 7. Prohibited Ownership … 28 8. Operation and Maintenance Philosophy … 28 9. Disposing of Systems … 28

Chapter 6. Technical Standards and Verification … 29

1. Standards and Tolerances … 29 2. Preservation of Standards and Tolerances … 29 3. Compliance with FAA Mandated Modifications … 30 4. Modification Documents … 30 5. System Replacement, Upgrade, Relocation and Reinstallation … 30 6. Federal Systems Transferred to Sponsors … 30 7. Waivers and Deviations … 31 8. Test Equipment … 31 9. Monitoring … 31 10. Cybersecurity … 32 11. Sponsors and Security … 32 12. Aircraft Accidents/Incidents … 33 13. Facility Reference Data … 33 14. Submitting FRD … 34 15. Periodic Ground Inspection … 35 16. Virtual Inspection … 36 17. Verification … 37 18. Outages … 37

Table of Contents (continued)

Paragraph Page

iii

19. Return to Service … 39 20. Non-compliance … 39

Chapter 7. Non-federally Employed Maintenance Technicians … 42

1. Verification Authority for Non-federally Employed Maintenance Technicians … 42 2. Non-federally Employed Maintenance Technicians’ Relationship to the FAA … 42 3. Recommending Maintenance Services … 42 4. Verification vs. Certification … 42 5. FCC License Requirement … 43 6. Validation of Non-federally Employed Maintenance Technicians … 43 7. Training and Examination Requirements … 43 8. Bypass Exams … 45 9. Grading Exams … 45 10. Failed FAA Performance Exam … 45 11. Issuing Verification Authority Letters … 46 12. Verification Authority Reciprocity … 46 13. Suspension & Revocation … 47 14. Moonlighting as a Non-federally Employed Maintenance Technician … 48

Chapter 8. FAA Personnel - Non-federal Training … 50

1. General … 50 2. Non-federal Program Training … 50 3. Examiner Qualifications … 50 4. System Training … 50 5. Certification … 51 6. FAA Performance Exams … 51 7. GROL … 51

Chapter 9. Automation Support: Non-federal Tool & Other Applications … 52

1. Facility, Service, and Equipment Profile (FSEP) … 52 2. Remote Monitoring and Logging System (RMLS) … 52 3. Non-federal Tool … 52 4. Online Resources and Applications … 53

Appendix A. Administrative Information … A-1

1. Distribution … A-1 2. Background … A-1 3. Authority to Change This Order … A-1 4. Program Management … A-1 5. Suggestions for Improvements … A-2 6. Records Management … A-2

Appendix B. Acronyms … B-1

Appendix C. Definitions … C-1

Appendix D. Related Laws, Regulations, Orders, and ACs … D-1

Appendix E. List of Ground Inspection Forms … E-1

Table of Contents (continued)

Paragraph Page

iv

Appendix F. List of Related Forms … F-1

Appendix G. ASDS Project Intake Form … G-1

Appendix H. FAA Approved Systems for Non-federal Use … H-1

Appendix I. Establishing a Non-federal System … I-1

Appendix J. Non-federal Systems Requiring Ground Inspection … J-1

Appendix K. Standard Operating Procedures … K-1

Appendix L. Record Retention … L-1

Appendix M. Approved Non-federal Training Courses … M-1

Appendix N. Quality Control Management … N-1

Appendix O. Virtual Inspection Requirements … O-1

Appendix P. Controlled Unclassified Information … P-1

Appendix Q. Directive Feedback Information … Q-1

List of Tables

Table 1-1. Internet Links … 2

Table 3-1. R.A.S.C.I. Matrix Defined … 17

Table 6-1. Notice of Non-compliance … 40

Table 7-1. FAA Performance Exams - Retesting … 46

Table 7-2. Suspension/Revocation Summary … 48

List of Figures

Figure 1-1. Navigating This Order … 4

Figure 2-1. Organizational Outline … 5

Figure 6-1. Annual Inspection Timeline … 35

Chapter 1. General Information › 5. Explanation of Policy Changes.

Chapter 1. General Information

1. Purpose of This Order. This order establishes policy applicable throughout the National Airspace System (NAS) for the governance of system approval, ownership, installation, commissioning, operation, maintenance, decommissioning, and assumption of ownership of nonfederal systems. This includes systems owned and operated for public and private benefit. It ensures safe air navigation by regulating specific non-federal systems. This order establishes criteria for the verification of non-federally employed maintenance technicians. It also provides guidance for Federal Aviation Administration (FAA) Service Area Non-federal Inspectors and Service Center Non-federal Program Implementation Managers (PIMs). This order does not pertain to stand-alone lighting systems covered by the most recent version of Advisory Circular (AC) 150/5345-53, Airport Lighting Equipment Certification Program. The guidance in this order does not apply to systems used specifically for Uncrewed Aircraft System Traffic Management (UTM), Urban Air Mobility (UAM), or Advanced Air Mobility Traffic Management (AAM), at this time. In addition, this order does not pertain to non-federal airport traffic control towers, or control towers in the FAA Contract Tower (FCT) Program, although certain systems within these towers may be subject to oversight.

2. Audience. This order applies to all FAA personnel and anyone external to the FAA involved with non-federal systems.

3. Where Can I Find This Order. You can find an electronic copy of this order on the Directives Management System (DMS) website: https://employees.faa.gov/tools_resources/orders_notices/. Or go to the MyFAA Employee website, select ‘Tools and Resources,’ then select “Orders and Notices.” It is also available on the public FAA website at Orders & Notices (faa.gov).

4. What This Order Cancels. This order cancels Order 6700.20B, Non-Federal Navigational Aids, Air Traffic Control Facilities, and Automated Weather Systems (11/25/2015).

5. Explanation of Policy Changes. This version of the order represents a significant re-write of its predecessor. Major changes include, but are not limited to, the order’s title, training requirements for FAA Non-federal Inspectors, assumption of ownership policy, use of reimbursable agreements, consolidation of the Memorandum of Agreement and Operations and Maintenance Manual (OMM), and OMM updates and periodic renewals. This version of the order revises roles and responsibilities to identify the FAA organizations responsible for specific tasks associated with the Non-federal Program at a high level, leaving the assignment of duties to the appropriate Directorate or designee to decide. The order makes use of the Non-federal Tool mandatory. It reflects statutory changes implemented since the last version. It revises guidance for issuance of verification authority. This revision adds the option for virtual periodic inspections. It documents the new process for receipt, assessment, and approval of new system designs and the modification of systems already

Chapter 1. General Information › 8. Interpretations.

approved. The order documents new policy for cybersecurity and system configuration management (CM).

6. Internet Links. See Table 1-1. Internet Links.

a. To access certain links in Table 1-1, you must have a connection to the FAA network. The network is only accessible to FAA personnel. If you are unable to access a link, please contact the Advanced Systems Design Service (ASDS) Team at the following email address: [email protected].

b. The system performance and maintenance forms listed below are available via the FAA’s public webpage.

(1) 6000-8, Technical Performance Record (TPR)

(2) 6000-10, Technical Reference Data Record (TRDR)

(3) 6030-1, Facility Maintenance Log (FML)

c. To obtain additional information and resources, visit ASDS’s public webpage for the Non-federal Program at www.FAA.gov/Go/NonFed.

d. Standard Operating Procedures (SOP) and other supplemental documents are accessible to FAA personnel via the ASDS internal website.

e. Non-federal system ground inspection forms are accessible via the Non-federal Tool.

Table 1-1. Internet Links

Public FAA website Internal ASDS webpage Public FAA Orders search page Internal search page for FAA Orders Public FAA Advisory Circulars search page Non-federal Tool: MyAccess Sign In Public ASDS Non-federal Program website Aeronautical Information Portal Public FAA Forms search page National Test Equipment Website Code of Federal Regulations, Part 171 iOE/AAA System United States Code Title 49, Subtitle 7 Frequency Coordination Request (WebFCR) FSEP Search TAP Login RMLS Log Index Instrument Flight Procedures Information Gateway

7. Geographical Scope. ASDS has regulatory authority over all 50 states, the District of Columbia, all United States (U.S.) territories, and U.S. possessions.

8. Interpretations. Forward all requests for interpretations of this order to the ASDS email address: [email protected].

Chapter 1. General Information › 10. Navigating This Order.

9. Common Terms Used in This Order. This order will use the following terms throughout the document. Below is a simplistic description of the terms and to whom/what they refer. This list should simplify the reading of this order. All definitions are in Appendix C, Definitions.

a. Inspectors – FAA Non-federal Program Inspectors are federal personnel with responsibilities for inspecting non-federally owned systems on behalf of the FAA’s Non-federal Program.

b. Program Implementation Managers (PIM) – FAA Non-federal Program PIMs are federal personnel who coordinate with sponsors and other federal personnel with respect to assisting sponsors with managing their non-federal systems.

c. Training Specialists – Training Specialists are federal personnel in the Operations Support Staff offices in the Districts and/or Technical Services who coordinate the issuance of verification authority to non-federally employed maintenance technicians hired by sponsors.

d. Sponsors – Sponsors are the non-federal entities who own and operate a non-federal system in the NAS.

e. Technicians – Technicians are non-federally employed maintenance technicians with FAA-issued verification authority who sponsors hire to maintain their non-federal systems.

10. Navigating This Order. See Figure 1-1. Navigating This Order for a snapshot of how the chapters relate to one another.

Figure 1-1. Navigating This Order

Chapter 2. Roles and Responsibilities › 3. Director of Operations Support (AJO/AJW-1).

Chapter 2. Roles and Responsibilities

1. Division of Duties. The Non-federal Program is a NAS-wide regulatory program under the authority of the FAA Administrator. The Administrator delegated managerial oversight and authority for the program to the Air Traffic Organization (AJO) Line of Business, under the Technical Operations (AJW) Vice President and the Operations Support Directorate (AJW-1). Starting with the Vice President of Technical Operations, this chapter specifically identifies the roles and responsibilities of the direct line of management for the program. The chapter will pinpoint responsibilities attributed to other AJW organizations at the Directorate level, AJO organizations at the Vice President level, and those outside of AJO at the Line of Business or Staff Office level. See Figure 2-1. Organizational Outline.

Figure 2-1. Organizational Outline

2. Technical Operations (AJO/AJW). AJW is the FAA organization that has direct managerial oversight for the Non-federal Program.

3. Director of Operations Support (AJO/AJW-1). The Director of Operations Support has managerial and decision-making authority for policies, processes, and approvals originating with

ASDS. Responsibilities include coordinating with other FAA Directorates, other government agencies, and airport representatives to ensure safe system oversight and maintenance.

5. Advanced Systems Design Service (ASDS) Team Manager (AJO/AJW-121). › l. Managing ASDS personnel, including, but not limited to, the…

4. NAS Modernization Group Manager (AJO/AJW-12). The NAS Modernization Group Manager oversees the ASDS Team. Responsibilities include issuing assignments, approving final work products, providing direction and guidance, assessing changes to policy and procedures, as well as ensuring consistent development of standards and application NAS-wide.

5. Advanced Systems Design Service (ASDS) Team Manager (AJO/AJW-121). The ASDS Team Manager is responsible for the Non-federal Program, including:

a. Serving as the FAA’s primary point of contact for ASDS policy and actions. This includes processes as well as interpretations of Federal legislation and regulations pertaining to the Non-federal Program;

b. Establishing the criteria used to ensure the accuracy and reliability of non-federal systems, e.g., compliance with performance standards, oversight policy, and system verification;

c. Managing the system design approval process for new manufacturers/vendors interested in making their systems available for non-federal use in the NAS;

d. Receiving applications requesting approval of modifications to FAA-approved nonfederal systems;

e. Managing the approval process for modifications to FAA-approved non-federal systems;

f. Coordinating review and determination of the level of oversight needed for non-federally owned systems, when applicable, e.g., when the use case changes;

g. Providing status reports and recommendations as they relate to the approval, ownership, operation, and maintenance of non-federal systems in the NAS;

h. Coordinating training needs and facilitating appropriate training for Inspectors with their appropriate level of management. The ASDS Team does not manage training for Inspectors;

i. Maintaining the official repositories for ASDS documentation, including, but not limited to, applications, manufacturer/vendor documentation and specifications, correspondence, and final decisions. This includes the Non-federal Tool;

Note: The FAA CM process will manage official FAA-owned documents, such as minimum requirements.

j. Addressing Congressional inquiries, as required;

k. Coordinating with the Office of Chief Counsel and the FAA Office of Government and Industry Affairs;

l. Managing ASDS personnel, including, but not limited to, the Non-federal Program’s National Lead;

m. Providing guidance on the Non-federal Program to FAA personnel and external stakeholders;

6. Other Operations Support Directorate Staff (AJO/AJW-1). › f. Engineering frequency assignments for non-federal systems with radio…

n. Managing the administrative function of the Non-federal Tool;

o. Collecting and tracking Controlled Unclassified Information (CUI) agreements;

p. Monitoring the content and accuracy of this order;

q. Updating directives related to the Non-federal Program;

r. Coordinating with other lines of business to solve problems and/or coordinate efforts on various topics, such as requests for assumption of ownership, non-standard system installations, and requests for waivers;

s. Hosting national program teleconferences, etc., and distributing information related to ASDS tasks, as necessary;

t. Developing and updating training specific to the Non-federal Program’s policies, processes, and procedures for the PIMs and the Inspectors; and

u. Collecting, consolidating, and analyzing metrics pertaining to program tasks.

6. Other Operations Support Directorate Staff (AJO/AJW-1). This list of responsibilities falls within the AJW-1 Directorate, but outside of the ASDS Team. They include the following:

a. Supporting the ASDS Team in the assessment of requests for system modifications, system approvals, non-standard installations, and waivers for non-federal systems. This task includes making timely recommendations to allow for a prompt response to the requestors;

b. Preparing and managing changes and updates to FAA directives for which they are the organization of responsibility;

c. Coordinating with the FAA’s Logistics Center to ensure appropriate funding of supply support for non-federal systems approved for assumption of ownership;

d. Supporting Service Area points of contact responsible for responding to aircraft accidents and incidents involving non-federal systems;

e. Inspecting non-federally owned systems maintained by the FAA under a Reimbursable Maintenance Agreement; and

f. Engineering frequency assignments for non-federal systems with radio transmitters. This task includes coordinating frequency assignments with the Federal Communications Commission (FCC) and providing sponsors with coordination information to help in obtaining their FCC licenses. The FCC will only issue licenses after proper coordination with the appropriate FAA office.

d. Maintaining positions for Inspectors who have the following… › (8) Validating that non-federally employed maintenance technicians…

7. Service Area Technical Operations (AJO/AJW-W/C/E). AJW-W/C/E has the following responsibilities:

a. Overseeing the Service Areas’ systems regulated by ASDS;

b. Planning/budgeting funds and resources needed to perform non-federal duties;

c. Maintaining positions for FAA personnel who will administer the FAA’s performance exams to technicians;

d. Maintaining positions for Inspectors who have the following responsibilities:

(1) Ensuring non-federal systems, sponsors, and technicians comply with FAA policies and procedures;

(2) Creating, updating, and executing an OMM, via the Non-federal Tool, for each system/site in accordance with the appropriate directives listed in Appendix D, Related Laws, Regulations, Orders, and ACs. Preparers must only add to and not modify the language in the OMM. The Non-federal Tool has the functionality to create the document with site-specific input by the preparer. Preparers must issue a new OMM every three years;

(3) Providing Training Specialists with sponsor requests for verification authority and the candidate’s qualifying documentation;

(4) Maintaining system records located in FAA databases, including, but not limited to, updating the Remote Monitoring and Logging System (RMLS), the Non-federal Tool, and providing the proper information to the appropriate points of contact for updates to the Facility, Service, and Equipment Profile (FSEP) database;

(5) Updating the appropriate Control Center with the latest points of contact for each non-federal system;

(6) Conducting both commissioning and periodic inspections in a timely manner. This task includes completing the appropriate pre- and post- inspection tasks, as well as activities performed during an inspection. Inspectors must prepare, update, execute, and disseminate FAA site-specific documentation. This documentation includes ground inspection forms, periodic inspection reports, and cover letters. Management has the option to allow a virtual inspection in lieu of an in-person periodic inspection to allow for flexibility in managing workload, as needed. Commissioning inspections cannot be virtual;

(7) Providing the PIM with system deficiencies and/or compliance issues with technicians to help them draft a Notice of Non-compliance;

(8) Validating that non-federally employed maintenance technicians signed the agreements required to receive copies of system-related FAA documentation that contains CUI; and

Chapter 2. Roles and Responsibilities › 9. NAS Security & Enterprise Operations (AJO/AJW-B).

(9) Ensuring non-federally employed maintenance technicians have copies of the appropriate FAA documents needed to maintain non-federal systems.

e. Maintaining positions for Training Specialists who have the following responsibilities, which require the use of the Non-federal Tool:

(1) Validating that technicians meet the specified requirements in this order to maintain non-federal systems;

(2) Receiving requests for verification authority from sponsors via Inspectors;

(3) Issuing verification authority and distributing the verification authority letters;

(4) Updating technician files in the Non-federal Tool; and

(5) Preparing and distributing letters suspending or revoking verification authority.

f. Maintaining positions in each Service Area for personnel who have the following responsibilities:

(1) Ensuring non-federal projects for the installation of non-federal systems meet appropriate siting criteria and do not jeopardize or interfere with the operation and reliability of other NAS systems. The ASDS Team must provide proper siting guidance and/or coordinate, as appropriate, with the FAA office(s) having expertise for any non-federal system based on new technology and/or systems not in FAA inventory (e.g., Ground Based Augmentation System - GBAS) to allow for proper evaluation when conducting Non-Rule Making (NR) airspace studies in accordance with the most recent version of Order JO 7400.2, Procedures for Handling Airspace Matters; and

(2) Ensuring Inspectors have the appropriate level of system-specific training prior to carrying out their assignments. Take note that it is possible that this training is only available via the manufacturer/vendor.

8. Facilities & Engineering Services (AJO/AJW-2). AJW-2 has the following responsibilities:

a. Providing engineering, environmental, construction, and installation support for assumption of ownership projects if a reimbursable agreement covers these services. Tasks associated with this responsibility may include, but are not limited to, siting, reviewing project designs, and providing a resident engineer;

b. Supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed.

9. NAS Security & Enterprise Operations (AJO/AJW-B). AJW-B has the following responsibilities:

a. Maintaining positions for a PIM in each Service Center, who is… › (1) Coordinating with all internal stakeholders on sponsor-proposed…

a. Responding to aircraft accidents or incidents involving non-federal systems, coordinating decisions with the appropriate lines of business, and providing ASDS with operational status information for such systems until cleared for return to service;

b. Overseeing the process to evaluate potential cybersecurity risks posed by non-federal systems intending to use and/or connect to FAA NAS services. Issuing determinations based on the evaluation and obtaining an Air Traffic Organization Authorization to Operate, based on the decision;

c. Defining cybersecurity requirements and/or controls for systems that do not connect to FAA systems, networks, and/or infrastructure, if necessary; and

d. Supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed.

10. Logistics Center (AJO/AJW-L). Developing, establishing, and providing life-cycle supply chain support for non-federal systems approved for assumption of ownership.

11. Air Traffic Services (AJO/AJT). AJT has the following responsibilities:

a. Managing the FCT Program;

b. Coordinating non-standard equipment requests with ASDS, in accordance with the joint SOP. Systems that meet the criteria will follow Chapter 3 guidance; and

c. Supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed.

12. Flight Program Operations (AJO/AJF). AJF is responsible for the following:

a. Validating instrument flight procedures (IFP);

b. Conducting commissioning, periodic, and special (as required) flight inspections to determine compliance with established standards for signal-in-space performance;

c. Coordinating, scheduling, and conducting flight inspections of non-federal systems; and

d. Supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed.

13. Mission Support Services (AJO/AJV). AJV has the following responsibilities:

a. Maintaining positions for a PIM in each Service Center, who is responsible for the following:

(1) Coordinating with all internal stakeholders on sponsor-proposed projects to install a non-federal system, either for non-federal ownership or for FAA assumption of ownership. The PIM will be the sponsor’s liaison to all other FAA personnel. The PIM receives requests to

establish, relocate, replace, upgrade, and/or decommission non-federal systems, as well as requests for waivers or deviations;

b. Maintaining positions in each Service Center responsible for the… › (5) Processing decommissioning requests, including (if necessary)…

(2) Providing guidance and support to the sponsor throughout ASDS processes. These tasks include verifying that systems have FAA approval, coordinating NRs, issuing Project Approval Letters, obtaining system identifier codes (commonly known as “idents”), directing sponsors to request IFPs via the Instrument Flight Procedures Information Gateway, and directing sponsors to request FCC frequencies via the Web-based Frequency Coordination Request (WebFCR) portal;

(3) Distributing ASDS information internally as directed by ASDS or as deemed necessary;

(4) Submitting decommissioning requests to the Service Area Decommission Committee (SADC) point of contact for processing;

(5) Notifying the Inspector of the pending decommissioning of a system;

(6) Updating and tracking pre-commissioned and decommissioned systems in the Nonfederal Tool. Updates to the Non-federal Tool also include information pertaining to assumption of ownership requests and making changes to system identifiers;

(7) Taking actions to ensure sponsors and technicians comply with ASDS policies. This may require coordination with Inspectors, Training Specialists, and/or ASDS; and

(8) Drafting and issuing a Notice of Non-compliance to sponsors to enforce the requirement to correct system deficiencies reported by Inspectors.

b. Maintaining positions in each Service Center responsible for the following:

(1) Supporting the development of Reimbursable Agreements between the FAA and sponsors for non-federal airport projects, if applicable;

(2) Supporting airspace analysis and NR studies, as needed. This task may include airspace modeling and simulations;

(3) Issuing location specific system identifiers for use in flight procedures, aeronautical chart supplements, FCC licenses, and FAA databases;

(4) Developing and maintaining flight procedures. Determining the impact of proposed systems on existing or proposed instrument flight rule (IFR) and visual flight rule operations. Coordinating with the office that performs flight validation/inspections. This includes the publication of procedures and updates to aeronautical chart supplements that show non-federal systems installed on and off airport property; and

(5) Processing decommissioning requests, including (if necessary) tracking the decommissioning process, conducting NR studies, notifying impacted stakeholders, responding to external objections, issuing a decommissioning memo, filing the proper Form 7900, filing a

14. Program Management Organization (AJO/AJM). › e. Submitting budget updates for non-federal systems eligible for…

cancellation request for IFP, etc. The SADC will provide the PIM with a copy of the decommissioning memo and the confirmed chart date. See Appendix F, List of Related Forms.

c. Collaborating on the development of operational requirements for new technologies, if necessary;

d. Assessing the need for proposed Joint Investment Efforts, defined in Chapter 5. This includes coordinating final decisions with the appropriate sustainment organization and Service Area personnel in AJW; and

e. Supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed.

14. Program Management Organization (AJO/AJM). The Program Management Organization has the following responsibilities in support of the Advanced Systems Design Service Team:

a. Supporting the assessment of systems designed by the private sector for non-federal use in the NAS. This includes supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed;

b. Validating the need for systems installed by sponsors as a Joint Investment Effort, where the FAA will operate and maintain the system in its end-state. This includes coordinating with the appropriate Service Center personnel in AJV and Service Area personnel in AJW with respect to conducting a needs assessment and determining concurrence;

c. Notifying ASDS when manufacturers/vendors receive or end a contract with the FAA for the procurement and use of system types overseen by the Non-federal Program. This will allow ASDS to:

(1) Issue the manufacturer an approval letter to sell the system to sponsors;

(2) Notify manufacturers about the program’s policy concerning system modifications that they must follow once ending their contract with the FAA, if they choose to continue selling their system to sponsors; and

(3) See Appendix J, Non-federal Systems Requiring Ground Inspection.

d. Notifying ASDS when a manufacturer/vendor, under contract with the FAA, makes system configuration modifications or updates to system types overseen by the Non-federal Program. See Appendix J; and

e. Submitting budget updates for non-federal systems eligible for assumption of ownership, under Title 49 United States Code (USC), to ensure the inclusion of these systems in the proper sustainment programs.

15. Safety & Technical Training (AJO/AJI). AJI is responsible for the following in accordance with the most recent version of Order JO 3000.22, Air Traffic Organization Technical Training Management:

19. Aviation Safety (AVS). › a. Establishing criteria for flight inspection and procedure validation;

a. Reviewing, assessing, and approving training courses and hands-on FAA performance exams for non-federal systems;

b. Publishing, storing, and maintaining approved FAA courses and performance exams;

c. Supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed; and

d. Conduct periodic compliance audits of external training courses.

16. System Operations Services (AJO/AJR). AJR is responsible for managing the Non-federal Weather Observer Program. Requesting assessments via ASDS of backup weather equipment for use by applicants to the Non-federal Weather Observer Program.

17. Airports (ARP). ARP is responsible for the following:

a. Generating funding criteria for approval of grants to establish non-federal systems;

b. Evaluating proposals for new grant-eligible system requests with respect to existing airports and planned airport developments that are part of the National Plan of Integrated Airport Systems, as defined by Title 49 USC Chapter 471;

c. Advising grant recipients of their obligations with respect to the system life cycle for grant-funded non-federal systems;

d. Advising sponsors to contact their PIM prior to procuring and installing a non-federal system;

e. Ensuring prompt notification to the PIM when a sponsor indicates their intent to request that the FAA assume ownership of a non-federal system;

f. Overseeing lighting systems governed by the most recent version of AC 150/5345-53; and

g. Supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed.

18. Security & Hazardous Materials Safety (ASH). Providing security requirements for potential installations of non-federal systems ASDS is assessing under the system design approval process, if ASDS requests assistance.

19. Aviation Safety (AVS). AVS is responsible for the following:

a. Establishing criteria for flight inspection and procedure validation;

Chapter 2. Roles and Responsibilities › 21. Finance and Management (AFN).

b. Coordinating with ASDS prior to issuing waivers dependent on the operation of nonfederal systems; and

c. Participating in ASDS assessments of new technology, including providing subject matter experts and concurrence for non-federal system design approvals. This includes supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed.

20. Office of NextGen (ANG). Coordinating with ASDS on assessment and testing processes with respect to the development of new systems designed specifically for non-federal use. This includes supporting the ASDS process to assess requests for system modifications and system approvals described in Chapter 3, as needed. ANG must also ensure ASDS is aware of new technology research and development that has the potential to become non-federal systems.

21. Finance and Management (AFN). Managing the disposal of decommissioned FAA systems obtained via the assumption of ownership process. This includes offering to return the system to the original owner.

Chapter 3. Non-federal Systems Design Approval › 3. Intake.

Chapter 3. Non-federal Systems Design Approval

1. Design Approval. Design Approval is FAA approval of a manufacturer’s uniquely identified configuration of a system type designed for specific use cases, intended to sell to non-federal sponsors for use in the NAS.

a. ASDS (AJW-121) is responsible for screening and processing system design approval requests of new non-federal systems. This includes new and legacy technology. In addition, there may be a need for the pro-active development of requirements and specifications in support of viable non-federal systems for potential use by non-federal sponsors.

b. ASDS is responsible for processing requests to make modifications to non-federal systems that have FAA approval.

c. System manufacturers/vendors must submit requests to ASDS via the following email address: [email protected]. ASDS screens submissions, coordinates with applicable agency organizations, and provides final determinations.

d. ASDS will not accept or assess requests to modify systems that are under an FAA procurement contract if the proposed change will impact FAA-owned systems. These requests require submission to the FAA contract holder.

e. This process excludes the review of systems used specifically for UTM, UAM, and AAM, as well as lighting systems governed by the most recent version of AC 150/5345-53.

2. Process Phases. A “system approval” is a collaborative FAA effort that involves various FAA organizations. The process has four phases and two definitive decision points to ensure the Agency considers all aspects of the proposal, as well as its impact on FAA-wide goals.

a. The phases to reach an assessment decision are as follows:

(1) Intake

(2) Transition

(3) Assessment

(4) Commission

b. The decision points follow the Intake and Assessment Phases.

c. Refer to SOP 6700-3, Non-federal System Review & Approval Process Flowchart, identified in Appendix K, Standard Operating Procedures, for specific details related to each phase of the process.

3. Intake. The Intake Phase starts with ASDS receiving a manufacturer/vendor’s request to approve a new non-federal system or modification to an existing approved system (see Appendix H, FAA Approved Systems for Non-federal Use). Document submission may include any or all

the following, if applicable: Intake Form (see Appendix G, ASDS Project Intake Form), Concept of Operations, System Specifications, Change Impact Analysis (for modifications).

4. First Decision Point. › f. While passing the Intake Phase informs the applicant that the…

a. The ASDS Team Manager assigns a project lead (ASDS Lead) based on system type.

b. The ASDS Lead conducts a preliminary review of the submitted materials and prepares a System Assessment Portfolio to track the submission throughout the process. The Lead will store the portfolio in the ASDS Team’s official document repository. During this phase, the ASDS Lead may need to conduct research, including the review of International Civil Aviation Organization (ICAO) standards or other applicable public or FAA information.

c. ASDS determines if the portfolio is ready for coordination. If not, ASDS notifies the manufacturer/vendor and identifies the inadequacies requiring resolution if they wish to resubmit.

d. Assessments for approval of new systems may require manufacturers to have support from a sponsor willing to participate in the assessment process.

4. First Decision Point. The ASDS Lead will provide an overview of the request and the initial assessment to internal stakeholders. These internal stakeholders will be the Intake Team for the request, and the ASDS Lead will act as the Team Chair. Personnel from organizations identified in Chapter 2 with a responsibility to support ASDS in the assessment of system modifications and system approvals will make up the Intake Team. This effort may require multiple meetings before reaching a final decision on the viability of the request and a recommendation to assess or not assess the system.

a. These stakeholders must use this information to brief their individual organizations.

b. Final decisions on future actions come from the associated Directorate levels.

c. The FAA decision to assess a system for design approval considers many facets, including, but not limited to, investment costs, resources, cybersecurity, and safety. For legacy systems, discussions will include consideration of system obsolescence.

d. If the decision is to assess, the Intake Team meetings will continue. The purpose of the meetings will be to prepare a R.A.S.C.I. matrix (see Table 3-1) to identify the scope of work for each stakeholder organization and draft a response letter to the manufacturer/vendor informing them that their project passed the Intake Phase.

e. The letter to the manufacturer will include information on the FAA’s next steps prior to beginning an assessment, which may include the approval of funding to support the project.

f. While passing the Intake Phase informs the applicant that the project is viable, it does not guarantee the Agency will conduct an assessment. Systems that may require integration with FAA-owned infrastructure and/or development of standards, identified during Intake, may require approval and proper assignment by FAA Senior Management and/or the FAA’s Investment Needs Process. Depending on that decision, the assessment may not be able to proceed despite viability.

6. Assessment. › a. There are many categories of aviation systems and there may be new…

g. The draft response letter and R.A.S.C.I. matrix will require concurrence by the stakeholders’ Directors. The final approved R.A.S.C.I. matrix will establish which organizations need to participate as part of the Assessment Team.

h. If the decision is to not assess, ASDS will notify the manufacturer/vendor.

Table 3-1. R.A.S.C.I. Matrix Defined

A matrix used to identify the roles and responsibilites of each stakeholder working on a project.

Role Description

R: Responsible Executes the activities identified and is responsible for their completion.

A: Accountable Ultimately responsible for the absolute completion of an activity. Highest level of authority.

A/R: Accountable/ Responsible Responsible for the execution and the ultimate completion of an activity.

S: Supporting Provides resources to the execution of an activity.

C: Consulted Provides expertise or information necessary for the completion of an activity.

I: Informed Requires status about the progress of an activity; the outcome affects them.

5. Transition. The Transition Phase is the point in the process that moves the request from a high-level Intake review to the full Assessment Phase. The Assessment Team will meet to discuss and decide on prioritization, an appropriate schedule, resource needs, funding strategies, and developing an assessment plan. Following a firm commitment by each organization, the manufacturer/vendor will receive official notification that includes the FAA’s assessment plan and schedule. If the Agency is not able to secure the funding required to support an assessment, the letter will explain that while the project is conceptually viable, the FAA is unable to provide a schedule for an assessment at this time.

6. Assessment. This phase includes the bulk of the work necessary for approval. It may include some or all the following tasks: reviewing the manufacturer/vendor’s system development documentation (e.g., system safety, hardware and software assurance, instruction book), system requirements, design, and verification data; reviewing training materials; conducting on-site design assurance audits; and conducting FAA Safety Risk Management (SRM) panels, internal meetings, and meetings with the manufacturer/vendor and sponsor.

a. There are many categories of aviation systems and there may be new categories in the future. If this is the first assessment for this category of equipment and/or the type of system, the team will decide on the oversight plan. ASDS will include the final oversight guidance in Appendix J.

Chapter 3. Non-federal Systems Design Approval › 10. Configuration Management (CM).

b. Throughout the assessment, the Assessment Team will periodically review whether the effort remains viable.

c. Upon completion, the team will make a recommendation to approve or disapprove the system for use in the NAS. For legacy systems, previously established system specifications will be the basis for the assessment. For new technologies, the team may use other requirement sources if all stakeholder’s Directorates concur.

7. Second Decision Point. Final documents supporting the decision will include, at a minimum, a National Design SRM Document, Design Approval Data Sheets (if approved), and a draft Decision Letter. The Assessment Team will provide management with these documents, and ASDS will brief the recommendation to the Directors for concurrence.

8. Decision Notification. The ASDS Lead will ensure all documentation developed is included in the System Assessment Portfolio. The portfolio becomes a permanent part of the ASDS CM file regardless of the outcome. The ASDS Lead will issue the manufacturer/vendor an official FAA decision letter signed by AJW-1.

a. Approvals will trigger the addition of the system to the ASDS list of approved nonfederal systems. Approvals only apply to the configuration(s) assessed. The letter will specify the manufacturer, model – including part number(s), and applicable configuration(s) with approval.

b. Disapprovals at any point in the process will include the basis for the decision, as well as guidance the manufacturer/vendor may follow for resubmitting their request later.

(1) Regardless of when the FAA decides to disapprove the request, any resubmission will require starting with the Intake Phase. Previous viability does not guarantee viability for a resubmitted application.

(2) If the denial is policy-based, ASDS will document that decision in an official FAA memo to ensure the FAA responds to all comparable requests with the same determination.

9. Commission. The Commission Phase will determine final site-specific requirements pertaining to the system configuration and installation. It will provide time to allow the sponsor to complete tasks required to meet the final approved configuration.

a. ASDS will issue guidance to Inspectors and PIMs pertaining to approval, training, FAA performance exams, installation, operation, maintenance, and inspection, if required.

b. The FAA will commission the supporting sponsor’s system following the completion of all pre-commissioning tasks, e.g., ground inspection, flight inspection. This includes any installations used during the manufacturer/vendor’s system assessment that meet the final approved standards.

10. Configuration Management (CM). CM control begins with baselining the system and its technical documentation. It ends with the decommissioning of the system from the specific installation sites.

12. Change in Ownership. › a. This notification must unambiguously identify the approved system…

a. All non-federal system manufacturers must have a CM plan and provide it to the FAA for filing with the approved system’s technical documentation.

b. The manufacturer must identify each configuration item and assign a unique control “number” (alpha-numeric is acceptable). This policy pertains to the overall system, subsystems, components, software, firmware, and any related documentation, such as training courseware and manuals.

c. Each revision must include a revised control number.

d. ASDS stores all CM-related documents in an electronic file folder with restricted access. In accordance with the most recent version of Order 1800.66, Configuration Management Policy, the ASDS Team will provide copies of approval letters to the NAS Policy & Quality Control Group’s NAS Configuration Management Team (AJW-181) for filing in the FAA’s Master Configuration Index.

11. System Modification Requests. Manufacturers/vendors must submit all change requests to ASDS via the following email address: [email protected]. The FAA must approve the changes before a sponsor operates the modified system in the NAS.

a. The submission must include a description of the changes and the impact on the system.

b. ASDS recommends, but does not require, the use of the most recent version of the Department of Defense Engineering Change Proposal form, DD-Form-1692.

c. The ASDS Team will determine the scope of the assessment required and issue an appropriate response to the manufacturer/vendor. Once the scope is determined, the FAA will evaluate and adjudicate proposed changes and their impact on the NAS.

d. ASDS will document, verify, and track all changes to ensure incorporation into the system’s CM file.

e. All submissions must be in writing. There must be two copies of each document: a final “clean” version, and one “redlined” to show changes made to the previous version of the documents.

f. If a sponsor or technician wishes to propose a modification, they must contact the manufacturer/vendor.

12. Change in Ownership. If a manufacturer/vendor merges or acquires the design and/or production rights of an FAA-approved system from another manufacturer/vendor with the intent to produce, sell, and/or maintain the system(s), the new owner must notify the FAA of their intent.

a. This notification must unambiguously identify the approved system configuration (e.g., production-controlled part number) and include a list of the acquired design data (e.g., requirements, design assurance documents, safety assessments/analysis, verification data).

Chapter 3. Non-federal Systems Design Approval › 13. Advancements Requiring Improvements.

b. The notification must also identify the new manufacturer/vendor’s plan for ensuring continued conformance to the original system approval requirements/standards.

c. In addition, the notice should advise of any branding changes to the system and the system’s documentation.

d. The new manufacturer/vendor has 60 calendar days to submit a formal notice or risk the removal of the system from the FAA’s approved systems list.

e. ASDS will issue a new approval letter, if necessary. This step will document the transfer for historical records, CM, e.g., traceability to future potential modifications, and allow for updates to the list of FAA approved systems.

13. Advancements Requiring Improvements. The FAA may require the sponsor to incorporate improvements in systems, maintenance, or maintenance-personnel safety practices realized by advancements in technology and/or safety practices. In such cases, the appropriate FAA organization must issue specific written guidance for distribution to sponsors regarding mandatory changes, appropriate implementation timetables, and feedback options.

3. Systems Not Identified in Part 171. › c. In line with the requirement to meet standards in Annex 10,…

Chapter 4. Operating Life Cycle

1. Decision to Install a Non-federal System. The FAA recognizes the need for a non-federal sponsor to establish, relocate, and/or replace aeronautical systems at public and private use airports and other locations in the NAS.

a. The FAA’s ASDS Team oversees the project approval process, which begins with a sponsor request to the PIM.

b. Sponsors must not start a project until receiving approval via the PIM. This applies to not only new installations but also upgrades, replacements, and relocations.

c. When installing a non-federal system, the sponsor makes a commitment to operate and maintain the system for its useful life without reimbursement or financial aid from the FAA. If such systems require upgrades, replacement, or relocation, the sponsor takes full responsibility for accomplishing these tasks.

d. If at any time the sponsor decides they can no longer meet the obligations agreed to, the sponsor may petition the FAA to decommission the system.

2. Systems Identified in Part 171.

a. Title 14 of the Code of Federal Regulations (CFR) Part 171, Non-Federal Navigation Facilities, establishes minimum requirements for the operation of certain non-federal systems used under IFR or used for public and private IFPs.

b. Title 14 CFR specifically identifies that non-federal systems must perform in accordance with ICAO’s International Standards and Recommended Practices, Annex 10 – Aeronautical Telecommunications.

c. Systems established only for testing or training purposes do not appear on aeronautical charts and therefore do not require oversight by ASDS. These systems do not require an OMM or a ground inspection.

3. Systems Not Identified in Part 171.

a. Title 14 CFR Part 171 Section 171.75 states that it does not specifically identify all systems requiring oversight by ASDS.

b. Systems not listed in Part 171, but identified in Appendix J, must follow the technical requirements, operational standards, and tolerances accepted at the time of system approval and/or approved system modifications. These systems must follow the same ASDS policies as those systems identified in Part 171.

c. In line with the requirement to meet standards in Annex 10, non-federal weather systems must perform in accordance with ICAO’s International Standards and Recommended Practices, Annex 3 - Meteorological Service for International Air Navigation.

6. Guidelines for Installation. › c. Sponsors must use guidelines in the most recent version of AC…

d. ASDS does not regulate lighting systems unless specifically identified in Appendix J. These systems must also meet the stated condition(s) in the appendix, if any. Visual Aids not identified in the appendix must meet the requirements in the most recent version of AC 150/5340-26, Maintenance of Airport Visual Aid Facilities.

e. ASDS policy regarding periodic inspections only applies to systems in Appendix J. Inspection of any other system(s) must stop immediately. Inspectors must notify the PIM of these instances. The PIM will inform the sponsor, in writing, that the FAA is voiding the OMM and that the Agency will no longer inspect the system. The Inspector and PIM should perform their assigned tasks to request modification or removal of the system in FSEP and other databases.

4. Backup Weather Equipment.

a. The ASDS Team does not manage the Non-federal Weather Observer Program or approve/inspect backup weather equipment used by Non-federal Weather Observers. Sponsors should submit requests to participate in the Non-federal Weather Observer Program to 9-AJO- [email protected].

b. ASDS has the responsibility to ensure the appropriate personnel assess the acceptability of this equipment. The assessment request is internal, made by AJT to the Non-federal Program’s National Lead.

c. If a sponsor chooses to procure and install an Automated Weather Observing System (AWOS) for use as a backup weather tool, the sponsor must meet the same requirements as they would for a primary AWOS, including, but not limited to obtaining a system identifier, obtaining a frequency, commissioning, and signing an OMM.

5. Program Coordination. The PIM must be the sponsor’s first point of contact for guidance pertaining to the ownership of a non-federal system. Contact information is available on both the internal and external ASDS websites. The PIM will provide the sponsor with a copy of Appendix I, Establishing a Non-federal System; it provides detailed instructions to the sponsor on navigating the process.

6. Guidelines for Installation.

a. All non-federal systems must have FAA approval for use in the NAS. See Appendix H.

b. All transmitting non-federal systems require an FCC license that the sponsor must display in a visible location at the site or keep in a readily accessible location for systems without a shelter. The FCC will not issue a license without proof of coordination with the FAA. If the license expires, the FAA has the authority to remove the system from service.

c. Sponsors must use guidelines in the most recent version of AC 150/5300-13, Airport Design, to meet requirements in CFR Part 139, Certification of Airports, Subpart C, Airport Certification Manual, and Subpart D, Operations.

h. The sponsor and the FAA must sign an OMM. This assures a clear… › (4) ASDS is responsible for revising the OMM templates to reflect the…

d. Sponsors cannot begin a project prior to receiving a Project Approval Letter. The PIM will issue a Project Approval Letter to the sponsor upon completion of all required assessments. The District that will have inspection responsibility must receive a copy as well. Assessments include the following tasks.

(1) Completion of an NR Airspace Study via the Obstruction Evaluation/Airport Airspace Analysis (OE/AAA) process (see the most recent version of Order JO 7400.2). This study is necessary to ensure proper siting of the system in accordance with system-specific siting documents and will result in a Determination Letter. The purpose of this letter is to approve the siting of the system, not give permission to proceed with the project.

(2) The engineering of a system frequency (if applicable) developed by Spectrum Engineering via the WebFCR Tool.

(3) The approval of any requested IFP by the IFP Validation Team, if applicable.

e. The PIM must file the appropriate Form 7900 via the Aeronautical Information Portal to request a system location identifier, coordinate the addition of the system in FSEP, and create a record for the system in the Non-federal Tool.

f. Local FAA personnel, affiliated with operations at the airport, may require an SRM assessment. If this is the case, the SRM requires completion prior to signing any other documents. The SRM may require the development of a local Letter of Agreement (LOA). See the most recent version of FAA Order JO 7210.3, Facility Operation and Administration, Chapter 4, Section 3 Letters of Agreement, paragraph 4-3-1.

g. An LOA is an agreement between the sponsor and AJT that documents additional processes the sponsor must follow to coordinate with local AJT personnel. It does not supersede the OMM. Any conflicting information between the LOA and OMM requires resolution prior to commissioning the system.

h. The sponsor and the FAA must sign an OMM. This assures a clear understanding of the FAA and sponsor’s responsibilities with respect to the system. The OMM is the overarching governing document that contains operational requirements for the non-federal system.

(1) The OMM is one of several documents required in the Facility Reference Data (FRD).

(2) The OMM outlines the performance and maintenance requirements the system must meet and sustain to operate in the NAS.

(3) When the sponsor signs the OMM, the sponsor’s signature contractually obligates the sponsor to adhere to the policies presented in this order and any other directives referenced in the OMM.

(4) ASDS is responsible for revising the OMM templates to reflect the most current FAA policy information. The revised OMM templates will replace the previous versions in the Non-federal Tool upon completion, and the Non-federal Tool users will receive notification.

Chapter 4. Operating Life Cycle › 8. Reimbursable Maintenance Agreements.

(5) The Inspector must prepare and issue a new OMM at least every three years. This requires obtaining new signatures.

(6) The Inspector must issue a new OMM outside of the requirement in the above paragraph if the existing OMM does not reflect current policy.

(7) Changes to contact information, replacing a technician, and/or adding additional technician(s) do not require obtaining new signatures on the OMM. Inspectors may use the addendum to make these changes, update the contact information in the Non-federal Tool, and upload the addendum to the Non-federal Tool.

i. Sponsors must comply with written FAA policies and procedures, including all relevant directives. The OMM must reference this order and the appropriate public-accessible directives pertaining to the operation, maintenance, and siting requirements for the specific system type. See Appendix D.

7. Guidelines for Commissioning. The FAA must conduct a commissioning ground inspection before the system can operate in the NAS. Some systems also require a commissioning flight inspection.

a. Inspectors must not schedule a commissioning ground inspection if they have not received a copy of the Project Approval Letter.

b. The technician must be present for both the ground and flight inspections.

c. A technician must have system-specific verification authority prior to participating in the system commissioning. The FAA does not grant temporary or interim verification authority to a technician who completes the FAA’s performance exam close to the day of a scheduled commissioning. The technician must receive verification authority in advance and have their FAA authorization available on the day of commissioning.

d. The Inspector must conduct the commissioning ground inspection, prior to the sponsor operating the system in the NAS. The Inspector must confirm that the system complies with this order, the OMM, any applicable ACs, orders, regulations, operational requirements, siting, etc. Non-federal systems may not operate in a pre-commissioned status, except for validation of successful installation and during the commissioning ground and flight inspections.

e. If applicable, after a successful commissioning ground inspection, the FAA must conduct a commissioning flight inspection in accordance with the most current version of FAA Order 8200.1, United States Standard Flight Inspection Manual.

f. Sponsors and/or their technicians are responsible for scheduling flight inspections and making ground-based preparations.

8. Reimbursable Maintenance Agreements. Sponsors may request that the FAA maintain any non-federally owned system that has an identical counterpart in FAA inventory, i.e., the sponsor may hire the FAA to perform regular maintenance if the Agency agrees. This type of arrangement is optional for the FAA.

9. Decommissioning. › e. The PIM will update the Non-federal Tool after receiving…

a. ASDS does not provide any input on these requests. Approving such requests requires review and approval by the District Manager with concurrence by the Service Area’s Director of Technical Operations and, if necessary, the Vice President of Technical Operations. The proposal must be advantageous to the FAA, the sponsor, and the public.

b. This arrangement requires the sponsor to enter into a reimbursable agreement with the FAA to cover the Agency’s expenses, including labor, travel, spare parts, etc. These agreements must comply with policies and procedures for establishing and executing a reimbursable agreement, as outlined in the latest version of the FAA Financial Manual, Volume 6, Accounting, Chapter 6.16, Reimbursable Agreements.

c. When the FAA maintains non-federal systems under a reimbursable maintenance agreement, the Agency will hold the system to the same standards, including policies and procedures, as FAA-owned systems. The FAA must have sole responsibility for maintaining the system and therefore prohibits split maintenance, i.e., maintenance of separate components of the same system [Localizer and Glide Slope of an Instrument Landing System (ILS)].

d. These systems will not require an OMM. ASDS will not have oversight and therefore will not conduct periodic inspections. The FAA will perform oversight inspections in accordance with the most recent version of FAA Order JO 6040.6, National Airspace System Technical Evaluation Program (NASTEP).

e. The FAA must not provide any maintenance or support to a non-federally owned system without an appropriate and fully executed reimbursable agreement.

f. The parties must renew, modify, and/or terminate the agreement in accordance with the documented terms. Upon termination, the sponsor must immediately enter into an OMM for oversight by ASDS, unless they are decommissioning the system.

9. Decommissioning. Sponsors must submit a request to decommission a system to the PIM.

a. The PIM must submit the request to the SADC for processing.

b. Approval requires completion of an NR study, in accordance with the most recent version of Order JO 7400.2.

c. If applicable, the sponsor must submit a request to cancel their FCC license(s).

d. The SADC must complete the necessary decommissioning process, which includes issuing a decommissioning memo, filing the appropriate Form 7900 via the Aeronautical Information Portal, filing a cancelation request for any associated IFPs, and providing the PIM with a copy of the decommissioning memo and the confirmed chart date.

e. The PIM will update the Non-federal Tool after receiving documentation from the SADC.

9. Decommissioning. › h. The FAA reserves the right to initiate the decommissioning of a…

f. Sponsors who established systems with the use of federal grant dollars, e.g., Airport Improvement Program funds, must meet their obligations in accordance with the most recent version of FAA Order 5100.38, Airport Improvement Program Handbook.

g. The decommissioning of a non-federal system will void the OMM.

h. The FAA reserves the right to initiate the decommissioning of a non-federally owned system that the Non-federal Program considers non-compliant. See Chapter 6, paragraph 19, for details.

6. Joint Investment Effort. › a. A Joint Investment Effort is:

Chapter 5. Assumption of Ownership

1. General. The ASDS Team manages the assumption of ownership or “transfer” of nonfederally owned systems as mandated by Title 49 USC Section 44502(e) Transfers of Air Traffic Systems. Section 44502(e) allows sponsors to request that the FAA accept ownership of a specified list of Airport Improvement Program (AIP) funded non-federally procured systems. Not all systems are eligible for assumption of ownership. If ineligible, sponsors may be able to participate in a Joint Investment Effort with the FAA.

2. AC 170-9, Criteria for Assumption of Ownership of Non-Federal Systems. The most recent version of AC 170-9 provides detailed guidance for requesting, approving, and accepting these transfers. AC 170-9 is mandatory for sponsors wishing to exercise this option. FAA personnel must consider AC 170-9 as an extension of this order.

3. SOP 6700-5, Assumption of Ownership Process Flowchart. See SOP 6700-5 identified in Appendix K for process details.

4. System Eligibility. Section 44502(e) identifies the specific types of systems eligible for assumption of ownership. Systems not identified in the statute or the most recent version of AC 170-9 are ineligible for transfer.

a. Sponsors must procure these systems using funds from a federal airport aid or project grant program, e.g., AIP.

b. The systems must meet performance specifications developed by the FAA.

c. Systems require transfer “without consideration.” Without consideration, also defined in the most recent version of AC 170-9, means the sponsor is transferring the system to the FAA free of cost or condition. In addition, the FAA must not impose any costs or conditions on the sponsor with respect to operation and maintenance after the transfer is complete. However, the sponsor is responsible for all costs associated with the system prior to transfer, including, e.g., Joint Acceptance Inspection findings that require resolution and flight inspection costs.

5. Automatic Disapprovals. The FAA will disapprove all requests resulting in ownership of a system that:

a. Does not have approval for use in the NAS, or

b. Does not exist in the Agency’s current inventory.

Note: The PIM will route a Director of Operations Support pre-signed disapproval letter for concurrence before sending it to the sponsor.

6. Joint Investment Effort. ASDS does not manage requests involving systems that are ineligible for assumption of ownership under Title 49 USC Section 44502(e). These requests are Joint Investment Efforts, not assumption of ownership projects.

a. A Joint Investment Effort is:

Chapter 5. Assumption of Ownership › 9. Disposing of Systems.

(1) An airport project that includes a proposal by a sponsor to establish, upgrade, or replace a system intended for FAA ownership, but

(2) Ineligible for assumption of ownership under Section 44502(e).

b. The FAA must have an interest in owning the system.

c. Requests for Joint Investment Efforts require validation of a need by AJV and the appropriate organization responsible for sustainment (e.g., AJM is the sustainment organization for an ILS). The PIM does not assess or validate an airport’s requirement or need for a system.

d. AJV and the sustainment organization must coordinate concurrence and a final decision with the appropriate Technical Operations District, regardless of system type, prior to agreeing to such a project.

e. For any system that requires in-service management, Technical Operations District Managers must obtain approval from the Service Area’s Director of Technical Operations and, if necessary, the Vice President of Technical Operations prior to agreeing to the project.

f. If the FAA disapproves the Joint Investment Effort for any reason, the PIM needs to receive notification in case the sponsor requests any further guidance with respect to non-federal systems.

7. Prohibited Ownership. A sponsor must not – under any circumstances – own, operate, or maintain any system that directly connects to or interfaces with FAA systems or the FAA’s NAS Network where the safety and/or security of the NAS could be at risk. Examples include, but may not be limited to, Runway Status Lights and Standard Terminal Automation Replacement Systems. This may exclude systems approved only for non-federal use under ASDS’s oversight that have the capability for one-way system monitoring. Proposed installation of “prohibited” systems requires a Joint Investment Effort. If the appropriate FAA organizations do not concur with participating in a Joint Investment Effort, the Agency must disapprove the sponsor’s project.

8. Operation and Maintenance Philosophy. The method used to maintain, repair, replace, and sustain systems obtained by the FAA via assumption of ownership is a decision for the sustainment organization in cooperation with AJW-L.

9. Disposing of Systems. If the FAA determines that a system obtained via assumption of ownership meets the criteria for decommissioning, the FAA may dispose of that system. However, the sponsor has the “first right of refusal” prior to disposal. AFN handles the coordination of the disposal of systems that meet these conditions. If the sponsor declines, the appropriate AFN personnel will offer the system for reassignment within the FAA or make it available for public acquisition. The FAA will discard systems not accepted for reassignment or procured by the public.

Chapter 6. Technical Standards and Verification › 2. Preservation of Standards and Tolerances.

Chapter 6. Technical Standards and Verification

1. Standards and Tolerances. FAA orders, ACs, technical handbooks, and approved manufacturer instruction books describe technical standards and tolerances, maintenance schedules, and maintenance procedures for non-federal systems. The ICAO or another FAAauthorized technical advisory group may also establish operating standards and tolerances. The appropriate manufacturer’s documentation for each system model receives FAA approval during the process to approve the system for use.

a. Inspectors must ensure non-federally employed maintenance technicians have the FAA documentation needed to perform maintenance tasks to keep the systems operating in compliance with FAA policy.

b. FAA documentation includes FAA Orders, Technical Instruction Books, and Maintenance Handbooks, including theory of operation, specifications, and standards and tolerances, as well as system training materials.

c. The FAA documentation may contain NAS Sensitive Technical Information (STI). STI is equivalent to CUI, specifically identified as Sensitive Security Information (SSI) in Title 49 CFR, Transportation, Part 1520 Protection of SSI.

d. This CUI requires protection in accordance with the most current versions of the following directives:

(1) Executive Order 13556, Controlled Unclassified Information, dated November 4, 2010

(2) Title 32 CFR Part 2002, Controlled Unclassified Information

(3) Department of Transportation Order 1650.5, Controlled Unclassified Information Program

e. Before providing copies of FAA documentation that contain CUI, Inspectors must inform and validate that non-federally employed maintenance technicians sign the following agreements, in accordance with the assessment documented in the Memorandum for Record, see Appendix P, Controlled Unclassified Information:

(1) FAA CUI Non-Disclosure Agreement (NDA)

(2) Air Traffic Organization CUI Access and Acceptable Use Agreement (AAA)

f. If the FAA’s documentation for a specific system type does not contain CUI, the technician does not have to sign the NDA and AAA to receive copies.

2. Preservation of Standards and Tolerances. The FAA mandates that non-federal systems continue to meet the standards required at the time of their commissioning. These systems do not have to meet requirements developed or changed in subsequent years.

6. Federal Systems Transferred to Sponsors. › a. Systems listed in Appendix H require commissioning as a non-federal…

a. Systems may continue to operate if the sponsor can:

(1) Operate the system without using unapproved modifications;

(2) Maintain the system, in accordance with the OMM, by employing a technician with system-specific verification authority; and

(3) Operate the system safely.

b. If maintenance and/or operation becomes problematic (e.g., multiple outages, loss of technician), the sponsor must decommission or replace the system.

3. Compliance with FAA Mandated Modifications. The FAA may issue mandatory modifications for FAA-owned systems. ASDS strongly encourages sponsors to implement all FAA-issued modifications.

a. Sponsors owning identical systems do not have an obligation to comply with these modifications unless they affect safety of flight, as determined by the FAA.

b. The FAA may mandate modifications for non-federal systems that are not identical to an FAA system if the change will fix a potential or realized safety issue.

c. Systems established using AIP grants must meet the mandatory rules associated with accepting a grant; those rules may mandate that sponsors make the FAA-issued modifications.

d. The sponsor must pay for all modifications.

4. Modification Documents. Sponsors must file all modification records for their system, including upgrades and replacements, with the FRD. The record must show the title and date of installation for each change completed since the system’s original installation date.

5. System Replacement, Upgrade, Relocation and Reinstallation. Non-federal sponsors may find it necessary to replace, upgrade, or relocate and reinstall a non-federal system. Such proposed projects require coordination with the FAA via the PIM as discussed in Chapter 4. These types of projects require a ground inspection, flight inspection (if applicable), and commissioning. In these scenarios, a commissioning is a requirement even if the project does not relocate the system and/or the sponsor adds components that change its previous baseline.

6. Federal Systems Transferred to Sponsors. The Federal Government (FAA, Department of Defense, etc.) may transfer ownership of a system to a sponsor. These transfers are permissible if the sponsor prefers to take on ownership responsibilities, rather than see the system decommissioned.

a. Systems listed in Appendix H require commissioning as a non-federal system and the establishment of an OMM, as discussed in Chapter 4, regardless of their current operating state in the NAS.

9. Monitoring. › c. Non-federal systems must not connect directly to the FAA’s NAS…

b. The system must meet current FAA standards unless ASDS grants a waiver. Therefore, the system may require upgrades at the sponsor’s expense before commissioning.

c. The PIM must coordinate requests to transfer federal systems to non-federal sponsors.

7. Waivers and Deviations. A waiver eliminates or defers a requirement, while a deviation is an alternate method used to meet a requirement. They can be permanent or temporary. The sponsor must file FAA-approved waivers or deviations with the system’s FRD. Inspectors must upload these documents to the Non-federal Tool. See the link in Chapter 1.

a. Non-federal systems must meet all applicable FAA siting criteria and performance standards. However, ASDS, in consultation with the appropriate FAA organization(s), may approve a waiver or deviation.

b. Sponsors must submit such requests in writing to the PIM. They may not implement any changes before receiving written consent.

8. Test Equipment. The FAA does not allow the use of FAA-owned test equipment on nonfederal systems under any circumstances. The sponsor must ensure properly calibrated test equipment is available. If test equipment is not available, the Inspector should cancel the commissioning or inspection.

a. Test equipment must meet the calibration cycles published in the most recent version of FAA Order JO 6200.4, National Test Equipment Program (NTEP) Management. If Order JO 6200.4 does not reference the test equipment, the sponsor must refer to the manufacturer’s instruction book. Sponsors or their technicians should contact their PIM for a copy of the calibration requirements.

b. Calibration standards must comply with the manufacturer’s specifications and industry standards. Test equipment must have a visible calibration sticker and a certificate. The calibration of test equipment must be traceable to reference standards recognized by the National Institute of Standards and Technology.

9. Monitoring. In accordance with the most recent version of FAA Order 8260.19, Flight Procedures and Airspace, all electronic navigation systems used in an IFP must have a monitoring system. Monitoring systems confirm that the system is functioning as intended.

a. All navigational aids, except for Non-Directional Beacons, require an executive monitor. The executive monitor is an internal monitor that will shut down the system when its performance falls below established tolerances.

b. Systems that do not have an internal monitor must have a remote status indicator. Remote status indicators are external monitors that provide an alert for the individual responsible for monitoring the system.

c. Non-federal systems must not connect directly to the FAA’s NAS Network or to other FAA-owned systems without prior authorization by AJW-B. Authorization must follow the

11. Sponsors and Security. › b. Report cybersecurity incidents to the Federal Government, and

procedure outlined in the most recent version of Order 1800.66, Section 3.4.2.1, Originate Change.

d. Sponsors are responsible for monitoring non-federal systems and any cost associated with the installation, operation, and removal of the monitored system and the monitor(s).

e. Sponsors must have a locally prepared and signed LOA with AJT, if AJT has a local presence, that outlines each party’s responsibilities with respect to monitoring alerts and reporting issues.

f. If continuous monitoring is not available but mandated, the sponsor must follow the reporting requirements outlined in the LOA, as well as the OMM. The OMM provides guidance on issuing Notice to Airmen (NOTAM) and restoration.

g. Global Navigation Satellite Systems, such as some configurations of the GBAS, require monitoring in addition to that mentioned above. Specifically, they may require monitoring of satellite constellations and predictive availability. Sponsors must follow the requirements established by the manufacturer and approved by the FAA. One such FAA directive sponsors may reference is the most recent version of AC 20-138, Airworthiness Approval of Positioning and Navigation Systems. The OMM will document this requirement, if needed.

h. Remote Maintenance Monitors (RMM) do not require inspection. Currently, the FAA has only approved RMM for AWOS. See section 12.f. below.

10. Cybersecurity. In accordance with the most recent versions of the Federal Information Security Management Act; FAA Order 1370.121, FAA Information Security and Privacy Program & Policy; and other applicable government policies, all systems planning to utilize or connect to NAS services must contact AJW-B via ASDS before acquiring or using any system connections. This includes the intent to acquire or use the system in association with NAS Services for any aspect of operation, support, developmental efforts, monitoring, or testing.

a. AJW-B will evaluate each request and either:

(1) Issue a provisional approval and initiate the cybersecurity authorization process, or

(2) Reject the request and provide a reason.

b. Systems planning to connect require an Authorization to Operate from the proper Air Traffic Organization Authorizing Official prior to connecting.

11. Sponsors and Security. The sponsors of non-federal systems have a responsibility to meet certain physical and cybersecurity requirements, in accordance with Title 49 CFR Transportation, Part 1520, Protection of SSI and Part 1542, Airport Security. They include adopting and carrying out programs that:

a. Provide for the safety and security of persons and property,

b. Report cybersecurity incidents to the Federal Government, and

13. Facility Reference Data. › c. The TRDR, FAA Form 6000-10, provides a snapshot of the system’s…

c. Refer requests for SSI to the appropriate federal agency.

12. Aircraft Accidents/Incidents. The OMM provides a checklist and contact information for the sponsor to use in the event of an aircraft accident or incident involving their non-federal system. The checklist supports any subsequent FAA investigation.

a. The FAA will evaluate each system potentially involved, regardless of ownership, in accordance with the most current version of Order JO 8020.16, Air Traffic Organization Aircraft Accident and Aircraft Incident Notification, Investigation, and Reporting.

b. The system must remain as found immediately after the accident or incident, i.e., do not alter the system’s operational state following the event.

c. If necessary, the FAA will issue a NOTAM for the suspect system via the appropriate Control Center and notify the sponsor of the system’s status.

d. The technician may examine and repair the system after release, as documented in the most recent version of Order JO 8020.16, Chapter 13. The sponsor must have Control Center approval before returning the system to service and canceling the NOTAM.

13. Facility Reference Data. The FRD is a collection of technical documentation for a specific system at a specific location. The retention of this data is mandatory for all non-federal systems. Appendix L, Record Retention, provides references to specific documents and the appropriate time frames for preservation. The Non-federal Tool will automatically dispose of documents no longer needed as their expiration date arrives. The FRD includes the comprehensive, quantitative, and performance information for that system. In addition, it must contain directives used to operate, maintain, and repair the system. FRD documents include, among others, the OMM, FML, TRDR, TPR, and flight inspection reports. A printed or electronic version of the FRD must always remain on-site. It must be readily accessible to any FAA personnel.

a. The Inspector must upload/save copies of the FRD documents to the Non-federal Tool. The Inspector must collect copies of FRD documents from the site at the commissioning and during periodic inspections unless the Inspector and sponsor agree to another way to obtain submissions.

b. FAA personnel may not release copies of restricted orders without the approval of the Office of Primary Responsibility (OPR) via ASDS. Submit any request for access to ASDS via the Team’s email address, [email protected].

c. The TRDR, FAA Form 6000-10, provides a snapshot of the system’s parameters at the time of commissioning. It must include system adjustments and all meter readings. The technician must complete the TRDR at the time of commissioning. In most cases, the TRDR does not change; however, if there is a major repair, modernization, adjustment, or re-tuning that alters the system’s performance, the technician must create a new TRDR. Title 14 CFR Part 171 refers to this form by the obsolete form number and name - - FAA-198, Record of Meter Readings & Adjustments.

14. Submitting FRD. › a. If FRD is not available for submission at the periodic inspection,…

d. The TPR, FAA Form 6000-8, provides a historical record. It shows the system’s parameters as recorded by the technician at each scheduled and unscheduled maintenance visit. It allows the technician to monitor the “health” of the system. Title 14 CFR Part 171 refers to this form by the obsolete form number and name - - Form 418, Radio Equipment Operation Records.

e. The FML, FAA Form 6030-1, is the permanent record of all activities performed to maintain the system. Log entries must follow the guidelines provided in the most recent version of FAA Order 6000.15, General Maintenance Handbook for NAS Facilities, and the associated SOP, titled Paper Maintenance Logs.

(1) The technician must close out the log at the end of each month. If there is an open maintenance activity or active outage, the technician must not close the log until resolving the issue. Only authorized personnel may make entries in the log, i.e., a technician with FAA-issued system-specific verification authority and, in the case of an AWOS, personnel performing triannual maintenance. FAA personnel must not make entries in the FML.

(2) Log entries must include all periodic maintenance, malfunctions encountered while maintaining the system (including adjustments made, repairs made, parts replaced, component failures, causes, and corrective actions), and NOTAMs issued to remove the system from service.

f. Currently, RMM for non-federally owned systems is only permissible for an AWOS. All non-federal AWOS have FAA approval to use the FAA-approved and manufacturer-developed RMM device. The FAA has the authority to expand this functionality to other non-federally owned systems, if the Agency decides it is appropriate to do so.

(1) RMM Logs may use the structure of the FAA Form 6030-1 with the words “subsidiary log” written in plain sight. The RMM log must document all maintenance activities performed remotely. This log must remain at the remote maintenance site.

(2) If an RMM activity takes place within 30 days of a significant event, the technician must reference the RMM activity in the FML as soon as possible. The most current version of FAA Order 6000.15 defines a “significant event” as any event causing an impact on air traffic operations or that may cause a system/service interruption at airports, centers, and/or any other FAA facility. This is any unscheduled event requiring a NOTAM.

(3) Inspectors do not need to inspect or collect copies of RMM Logs. The sponsor or technician may discard RMM Logs 30 days after closing unless associated with a significant event. Retain RMM logs associated with a significant event for the same length of time as the FML.

14. Submitting FRD. Typically, Inspectors will receive copies of FRD during periodic inspections. Sponsors may elect to submit FRD more frequently and in the manner they choose, if the Inspector approves.

a. If FRD is not available for submission at the periodic inspection, the sponsor must ensure the Inspector receives the documents within 30 calendar days. FRD that is not readily accessible

b. ASDS requires a periodic ground inspection for all systems listed in… › (4) The inspection window does not shift based on the previous year’s…

is a deficiency that requires notation in the Inspection Report and the issuance of a Notice of Non-compliance.

b. Failure to submit FRD, in accordance with this order, may result in a NOTAM removing the system from service. The NOTAM will remain until such time that the FAA receives the documents.

15. Periodic Ground Inspection. ASDS will create, update, and maintain Non-federal Program ground inspection forms identified in Appendix E, List of Ground Inspection Forms. Inspectors must use these standardized forms, accessible via the Non-federal Tool, to complete inspections.

a. There is no requirement for the Inspector or the technician to sign the ground inspection forms. The Non-federal Tool automatically identifies the Inspector.

b. ASDS requires a periodic ground inspection for all systems listed in Appendix J using the appropriate ground inspection form, identified in Appendix E.

(1) Most systems require an annual inspection, defined as once every 12 months based on the scheduled date found in RMLS, in the Periodic Maintenance Log’s (LPM) Record Information section. The inspection window is +/- 60 days from the scheduled date.

(2) Category II and III ILS and their supporting systems, such as an Approach Lighting System with Sequenced Flashing Lights, require a semiannual inspection. Semiannual, defined as twice each year based on the RMLS LPM scheduled date. The inspection window is +/- 30 days from the scheduled date. The more frequent inspection schedule is a requirement in the most recent version of FAA Order JO 6750.57, Instrument Landing System Continuity of Service Requirements and Procedures.

(3) ASDS will determine the frequency of inspection intervals and the inspection parameters for new system types during the system design approval process.

(4) The inspection window does not shift based on the previous year’s actual inspection date, i.e., the window is the same fixed range every year. The scheduled date must not change unless there are extenuating circumstances, or the system requires a re-commissioning. See Figure 6-1. Annual Inspection Timeline.

Figure 6-1. Annual Inspection Timeline

Chapter 6. Technical Standards and Verification › 16. Virtual Inspection.

c. Inspectors must follow the steps listed in FAA Form 6700-13, Inspection Checklist. This form outlines the tasks the Inspector must complete before, during, and after the site visit. Inspectors must:

(1) Coordinate site visits and ensure their point of contact is aware of the requirement to coordinate facility outages;

(2) Determine if the FCC license is active via the FCC website;

(3) Validate that system information in the Non-federal Tool is up to date;

(4) Prepare a new OMM, if necessary, and obtain appropriate signatures;

(5) Prepare a Facility Contact Information addendum if the technician changed;

(6) Review the existing or revised OMM and inspection process with the sponsor;

(7) Confirm the technician’s identity, verify possession of a General Radiotelephone Operator License (GROL), and verify that the technician has a verification authority letter;

(8) Confirm outage status and that a NOTAM is in place;

(9) Review the FRD, ensuring the documents are readily accessible and the sponsor has an unexpired FCC license;

(10) Verify test equipment calibration is up to date;

(11) Observe the technician conducting maintenance activities; document any identified parameter issues and whether the technician follows appropriate procedures;

(12) Review inspection results with the technician and the sponsor (if the sponsor is on site);

(13) Collect copies of FRD and ensure the technician restores the system to service; and

(14) Update RMLS and the Non-federal Tool; confirm the accuracy of the Chart Supplement for the system inspected; review inspection results with your direct manager; generate an inspection report; notify the PIM of any discrepancies; and send the inspection report to the sponsor.

16. Virtual Inspection. The Inspector’s Manager will determine and give permission to conduct virtual inspections in lieu of an in-person periodic inspection. Management should use the following factors to determine if a virtual inspection is the appropriate option: location, priority, work life balance situation, site-specific issues, funding, travel requirement, and workload. See Appendix O, Virtual Inspection Requirements, for guidelines required to conduct a virtual inspection.

Chapter 6. Technical Standards and Verification › 18. Outages.

17. Verification. The OMM must reference the appropriate verification parameters.

a. These parameters must be in accordance with the standards of ICAO, the FAA, and the manufacturer’s operations manuals.

b. “Verification” is the technician’s documented assurance that the system is providing the expected or advertised service to the user.

c. The FML must include the required verification statement entered by the technician. The technician must use the format shown in the AWOS and Distance Measuring Equipment (DME) examples below, i.e., the system’s acronym followed by the word “verified.” For example, see the following:

(1) “AWOS verified”

(2) “DME verified”

(3) “[System acronym] verified”

d. Entering a verification statement in the FML is an event-based entry. The FAA requires a verification statement entry any time the technician returns the system to service. The most recent version of FAA Order 6000.15 provides additional details relevant to verification statements. Specific examples of instances requiring this entry are:

(1) Following a successful commissioning;

(2) Returning the system to service after an FAA inspection;

(3) Returning the system to service after routine or preventative maintenance;

(4) Returning the system to service after repairs;

(5) Returning the system to service after an FAA approved modification; or

(6) Returning the system to service after any other interruption of service.

e. Inspectors do not verify or certify non-federal systems and must not help with repairs or return a non-federal system to service. Inspectors may provide limited general advice if the technician requests it.

f. In extreme cases where a technician cannot identify a solution, even with the aid of the manufacturer, a technician may request help from the AJW-14 Surveillance & Weather Group and/or AJW-15 Navigation, Communications & Environmental Group, under a Reimbursable Agreement. Sponsors must request assistance through the PIM.

18. Outages. Sponsors must report outages or shutdowns to the appropriate Control Center. The OMM must provide the appropriate Control Center contact information.

18. Outages. › f. Non-federal systems are not reportable under the most recent version…

a. The sponsor must shutdown, i.e., remove the system from service, under the following circumstances:

(1) The sponsor must remove the system from service to complete routine maintenance, including inspections.

(2) The sponsor must remove the system from service if there is an out-of-tolerance condition.

(3) The sponsor must remove the system from service upon receipt of two reports concerning irregular operation or malfunctions of the system. The reports received can be from any two of the following sources, in any combination: Pilot Reports, Monitor station(s), and/or from other persons.

(4) The sponsor must remove the system from service in the case of an activity that could result in Hazardously Misleading Information or otherwise affect the accuracy or reliability of the radiating signal, if applicable.

b. The FAA requires the sponsor to coordinate the initiation/issuance of a NOTAM with the appropriate Control Center in the event of an outage.

c. For the purposes of routine maintenance, the sponsor must make notification at least 24 hours in advance. Advance notification must provide the specific time the interruption will occur, its planned duration, and the purpose. The Control Center will provide an initial approval. A follow-up to confirm permission to proceed must take place 30 minutes in advance of removal from service. The technician must not remove the system from service before obtaining confirmation. The FAA recommends scheduling routine maintenance during non-peak traffic periods.

d. In the event of an unexpected or unscheduled outage, the technician must follow the restoration guidelines in the OMM and the manufacturer’s handbook.

(1) Technicians must document all system interruptions in the FML, regardless of the length of the outage, upon discovery.

(2) Technicians must report unscheduled outages lasting one hour or longer to the appropriate Control Center, even if a NOTAM is not necessary.

(3) If the system is not restorable immediately, the technician must issue a NOTAM.

e. Category II and III landing systems are subject to following the continuity of service reporting requirements outlined in their agreement with the FAA. The technician must report all outages, lasting one minute or longer to the appropriate point of contact using the Service Interruption Account Form attached to the agreement.

f. Non-federal systems are not reportable under the most recent version of Order JO 6040.15, National Airspace Performance Reporting Service (NAPRS), and therefore do not follow or abide by the requirements outlined in the NAPRS desk guides. However, ASDS

c. Notification to the PIM by the Inspector that the sponsor remains… › (2) Informs the sponsor that the FAA has begun decommissioning of the…

requires that non-federal sponsors or technicians report all non-federal system outages to the appropriate Control Center identified in the OMM.

19. Return to Service. The sponsor must notify the appropriate Control Center when returning a system to service. In addition, the sponsor is responsible for removing any outstanding NOTAMs that are no longer valid.

20. Non-compliance. PIMs must prepare, for signature by the Service Area Director of Technical Operations, a Notice of Non-compliance that informs the sponsor of the consequences of not resolving the discrepancies identified in the inspection report.

a. Notification to the PIM by the Inspector of deficiencies found during the inspection triggers the First Notice of Non-compliance or warning letter. The PIM will prepare a letter that:

(1) Reiterates the deficiencies,

(2) References the inspection report, if applicable,

(3) Warns that the FAA will NOTAM the system out of service or “unserviceable” (U/S) if the sponsor does not work to resolve the issues, and

(4) Identifies a due date for resolution.

Note: For consistency, the PIM should use time periods referenced in the inspection report, if there is one.

b. Notification to the PIM by the Inspector that the sponsor did not resolve the issues by the given due date triggers the Second Notice of Non-compliance. The PIM will instruct the Inspector to issue a NOTAM for the system, removing it from service. The PIM will prepare a letter that:

(1) References the inspection report (if applicable) and the First Notice,

(2) Informs the sponsor that the FAA has NOTAMed the system U/S,

(3) Gives 60 calendar days for resolution, and

(4) Warns that the FAA will begin the decommissioning process if the sponsor does not comply.

c. Notification to the PIM by the Inspector that the sponsor remains non-compliant triggers the Third Notice of Non-compliance or final letter. The PIM will obtain concurrence from ASDS, instruct the Inspector to update the NOTAM, and begin the decommissioning process. The PIM will prepare a letter that:

(1) References all previous correspondence,

(2) Informs the sponsor that the FAA has begun decommissioning of the system, and

(3) Informs the sponsor that they are responsible for all associated costs to remove the system.

d. If the identified deficiency requires an immediate NOTAM removing the system from service, the PIM must adapt the Notice of Non-compliance.

f. The sponsor is non-compliant if their system misses a ground… › (2) The PIM must issue a Notice of Non-compliance, notifying the…

(1) Deficiencies requiring an immediate NOTAM do not face decommissioning if not resolved within 60 calendar days. The Inspector should provide a reasonable time frame to remedy the issue.

(2) If the sponsor does not remedy the issue in the time given, the PIM must give an extension of 60 calendar days prior to initiating the decommissioning process.

(3) Table 6-1. Notice of Non-compliance defines the actions and consequences for a typical scenario.

e. Inspection is not the only trigger for issuing a Notice of Non-compliance. The PIM may also issue a notice if informed of issues between inspections.

Table 6-1. Notice of Non-compliance

Notice Trigger Inspector Action PIM Action Consequence

First

Deficiencies identified during or between inspections

Send inspection report & Notify PIM Send First Notice None; Warns of NOTAM

Second Missed Due Date Notify PIM & Issue U/S NOTAM Send Second Notice NOTAM; Warns of Decommissioning

Third Sponsor Failure to Act Notify PIM

Obtain concurrence, Send Third Notice, begin decommissioning

Decommissioning

f. The sponsor is non-compliant if their system misses a ground inspection for any reason, including that the system is out of service. The consequence of missing two consecutive ground inspections is decommissioning. The Inspector should only consider the inspection missed after the inspection window closes.

(1) When the first inspection window closes, the Inspector must notify the PIM that the system missed its inspection and NOTAM the system out of service.

(2) The PIM must issue a Notice of Non-compliance, notifying the sponsor that the system missed its inspection window; the FAA has NOTAMed the system out of service; the system must remain off until the Inspector conducts an inspection; and the FAA will decommission the system if it misses the next inspection.

f. The sponsor is non-compliant if their system misses a ground… › (3) If the system misses a second inspection window, the Inspector must…

(3) If the system misses a second inspection window, the Inspector must notify the PIM. The PIM must begin the decommissioning process and notify the sponsor with a Final Notice of Non-compliance.

Chapter 7. Non-federally Employed Maintenance Technicians

1. Verification Authority for Non-federally Employed Maintenance Technicians. This chapter provides policy and guidance for issuing verification authority to potential technicians. Non-federal systems approved for use in the NAS require regular maintenance to ensure safe operation and to meet FAA policy that governs the use of those systems. Sponsors must hire a maintenance technician who can qualify for FAA-issued system-specific verification authority.

4. Verification vs. Certification. › a. The FAA issues certification authority to FAA-employed Airway…

a. Only sponsors may submit a request to obtain or confirm verification authority for a candidate they intend to hire.

b. Sponsors must submit the request to the Inspector. The Inspector will pass the request to the Training Specialist for processing.

c. The FAA issues system-specific verification authority to a candidate if they meet the FAA’s training requirements.

2. Non-federally Employed Maintenance Technicians’ Relationship to the FAA. A nonfederal sponsor may satisfy the requirement for a technician by employing candidate(s) in-house, hiring/contracting with a self-employed individual, or contracting with a company that provides maintenance services.

a. It is ultimately the sponsor’s responsibility to ensure that system maintenance and verification are in accordance with this order.

b. The FAA does not have an employer/employee relationship with the technician because the sponsor signs and agrees to the terms of operation and maintenance with the FAA and hires the technician. This means that the sponsor is responsible for the actions of those they employ and is liable for the technician(s)’ actions.

c. While there is no employer/employee relationship, the technician does have an obligation to meet the criteria the FAA used to base the issuance of verification authority. The FAA has the right to refuse, suspend, and/or revoke this authority in accordance with the requirements in this chapter or paragraph 13, respectively.

3. Recommending Maintenance Services. The FAA must not recommend a specific technician or a specific maintenance company under any circumstances. If approached for possible contacts, ASDS will provide a complete list of all technicians with current verification authority on the system type in question.

4. Verification vs. Certification. The two are not identical. There is only one path to obtaining verification authority. Nonetheless, technicians must follow the provided guidance for verifying a system like FAA personnel do when certifying a system.

a. The FAA issues certification authority to FAA-employed Airway Transportation Systems Specialists (ATSS) to perform maintenance and certify FAA-owned systems, in

a. Candidates must successfully complete an FAA-approved,… › (2) The candidate must be able to provide a copy of a certificate of…

accordance with the most recent version of Order JO 3000.57, Air Traffic Organization Technical Operations Training and Personnel Certification.

b. The Training Specialist issues verification authority to technicians to perform maintenance and verify non-federally owned systems, in accordance with the process in this order.

5. FCC License Requirement. Technicians that maintain any transmitter-equipped system must possess an FCC GROL, in accordance with Title 47 CFR Part 87 Aviation Services. The FAA does not allow split credentials, i.e., the technician with verification authority must also hold the GROL and vice versa. The FCC will revoke a technician’s GROL for working on an unlicensed system. The FAA requires the technician to carry a copy of their GROL when conducting maintenance.

6. Validation of Non-federally Employed Maintenance Technicians. Training Specialists must use the Non-federal Tool to create, verify, collect, log, store, and manage data files on each technician.

Continue reading ↓ 120 of 177 passages shown