Certificate of waiver or authorization COA WSA 41

0281-EX-CN-2016 Pre Coordination Document

Battelle Memorial Institute

2016-12-07ELS_185280

FAA FORM 7711-1 UAS COA Attachment Page 1 of 26 2015-WSA-41-COA-TS DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION CERTIFICATE OF WAIVER OR AUTHORIZATION ISSUED TO Test Site – University of Alaska - Fairbanks 3330 Industrial Way Fairbanks, AK 99701 This certificate is issued for the operations specifically described hereinafter. No person shall conduct any operation pursuant to the authority of this certificate except in accordance with the standard and special provisions contained in this certificate, and such other requirements of the Federal Aviation Regulations not specifically waived by this certificate. OPERATIONS AUTHORIZED Operation of the Arcturus T-20, Unmanned Aircraft System (UAS) in Class D, E, and G airspace at or below 9,999 feet above Mean Sea Level (MSL) over Northern Oregon, under the jurisdiction of Seattle Air Route Traffic Control Center (ARTCC), Salt Lake ARTCC, Chinook Terminal Radar Approach Control (TRACON), and Pendleton Federal Contract Tower (FCT). See Attachment 1 for Operations Area. LIST OF WAIVED REGULATIONS BY SECTION AND TITLE N/A STANDARD PROVISIONS 1. A copy of the application made for this certificate shall be attached and become a part hereof. 2. This certificate shall be presented for inspection upon the request of any authorized representative of the Federal Aviation Administration, or of any State or municipal official charged with the duty of enforcing local laws or regulations. 3. The holder of this certificate shall be responsible for the strict observance of the terms and provisions contained herein. 4. This certificate is nontransferable. Note-This certificate constitutes a waiver of those Federal rules or regulations specifically referred to above. It does not constitute a waiver of any State law or local ordinance. SPECIAL PROVISIONS Special Provisions are set forth and attached. This certificate, 2015-WSA-41-TS, is effective from July 13, 2016, through July 12, 2018, and is subject to cancellation at any time upon notice by the Administrator or his/her authorized representative. BY DIRECTION OF THE ADMINISTRATOR FAA Headquarters, AJV-115 Scott J. Gardner (Region) (Signature) July 12, 2016 Acting Manager, UAS Tactical Operations Section (Date) (Title) FAA Form 7711-1 (7-74) Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 2 of 26 2015-WSA-41-COA-TS COA Number: 2015-WSA-41 Issued To: Test Site – University of Alaska - Fairbanks referred herein as the “proponent” Address: 3330 Industrial Way Fairbanks, AK 99701 Activity: Operation of the Arcturus T-20, Unmanned Aircraft System (UAS) in Class D, E, and G airspace at or below 9,999 feet above Mean Sea Level (MSL) over Northern Oregon, under the jurisdiction of Seattle Air Route Traffic Control Center (ARTCC), Salt Lake ARTCC, Chinook Terminal Radar Approach Control (TRACON), and Pendleton Federal Contract Tower (FCT). See Attachment 1 for Operations Area. Purpose: To prescribe UAS operating requirements in the National Airspace System (NAS) for the purpose of aeronautical research. Dates of Use: This COA is valid from July 13, 2016 through July 12, 2018. Should a renewal become necessary, the proponent shall advise the Federal Aviation Administration (FAA), in writing, no later than 45 business days prior to the requested effective date. Public Aircraft 1. A public aircraft operation is determined by statute, 49 USC §40102(a)(41) and §40125. 2. All public aircraft flights conducted under a COA must comply with the terms of the statute. 3. All flights must be conducted per the declarations submitted on COA on-line. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 3 of 26 2015-WSA-41-COA-TS STANDARD PROVISIONS A. General. The review of this activity is based upon current understanding of UAS operations and their impact in the NAS. This COA will not be considered a precedent for future operations. (As changes in or understanding of the UAS industry occur, limitations and conditions for operations will be adjusted.) All personnel connected with the UAS operation must read and comply with the contents of this authorization and its provisions. A copy of the COA including the special limitations must be immediately available to all operational personnel at each operating location whenever UAS operations are being conducted. This authorization may be canceled at any time by the Administrator, the person authorized to grant the authorization, or the representative designated to monitor a specific operation. As a general rule, this authorization may be canceled when it is no longer required, there is an abuse of its provisions, or when unforeseen safety factors develop. Failure to comply with the authorization is cause for cancellation. The proponent will receive written notice of cancellation. During the time this COA is approved and active, a site safety evaluation/visit may be accomplished to ensure COA compliance, assess any adverse impact on ATC or airspace, and ensure this COA is not burdensome or ineffective. Deviations, accidents/incidents/mishaps, complaints, etc will prompt a COA review or site visit to address the issue. Refusal to allow a site safety evaluation/visit may result in cancellation of the COA. Note: This section does not pertain to agencies that have other existing agreements in place with the FAA. B. Airworthiness Certification. The unmanned aircraft must be shown to be airworthy to conduct flight operations in the NAS. Test Site – University of Alaska - Fairbanks has made its own determination that the Arcturus T- 20 unmanned aircraft is airworthy. The Arcturus T-20 must be operated in strict compliance with all provisions and conditions contained in the Airworthiness Safety Release, including all documents and provisions referenced in the COA application. 1. A configuration control program must be in place for hardware and/or software changes made to the UAS to ensure continued airworthiness. If a new or revised Airworthiness Release is generated as a result of changes in the hardware or software affecting the operating characteristics of the UAS, notify the UAS Integration Office of the changes as soon as practical. a. Software and hardware changes should be documented as part of the normal maintenance procedures. Software changes to the aircraft and control station as well as hardware system changes are classified as major changes unless the agency has a formal process, accepted by the FAA. These changes should be provided to the UAS Integration office in summary form at the time of incorporation. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 4 of 26 2015-WSA-41-COA-TS b. Major modifications or changes, performed under the COA, or other authorizations that could potentially affect the safe operation of the system must be documented and provided to the FAA in the form of a new AWR, unless the agency has a formal process, accepted by the FAA. c. All previously flight proven systems to include payloads, may be installed or removed as required, and that activity recorded in the unmanned aircraft and ground control stations logbooks by persons authorized to conduct UAS maintenance Describe any payload equipment configurations in the UAS logbook that will result in a weight and balance change, electrical loads, and or flight dynamics, unless the agency has a formal process, accepted by the FAA. d. For unmanned aircraft system discrepancies, a record entry should be made by an appropriately rated person to document the finding in the logbook. No flights may be conducted following major changes, modifications or new installations unless the party responsible for certifying airworthiness has determined the system is safe to operate in the NAS and a new AWR is generated, unless the agency has a formal process, accepted by the FAA. The successful completion of these tests must be recorded in the appropriate logbook, unless the agency has a formal process, accepted by the FAA. 2. The Arcturus T-20 must be operated in strict compliance with all provisions and conditions contained within the spectrum analysis assigned and authorized for use within the defined operations area. 3. All items contained in the application for equipment frequency allocation must be adhered to, including the assigned frequencies and antenna equipment characteristics. A ground operational check to verify the control station can communicate with the aircraft (frequency integration check) must be conducted prior to the launch of the unmanned aircraft to ensure any electromagnetic interference does not adversely affect control of the aircraft. 4. The use of a Traffic Collision Avoidance System (TCAS) in any mode while operating an unmanned aircraft is prohibited. C. Operations. 1. Unless otherwise authorized as a special provision, a maximum of one unmanned aircraft will be controlled: a. In any defined operating area, b. From a single control station, and c. By one pilot at a time. 2. A Pilot-in-Command (PIC) is the person who has final authority and responsibility for the operation and safety of flight, has been designated as PIC before or during the flight, and holds the appropriate category, class, and type rating, if appropriate, for the conduct of the flight. The responsibility and authority of the PIC as described by 14 CFR 91.3, Responsibility and Authority of the Pilot-in-Command, apply to the unmanned aircraft PIC. The PIC position may rotate duties as necessary with equally qualified pilots. The individual Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 5 of 26 2015-WSA-41-COA-TS designated as PIC may change during flight. Note: The PIC can only be the PIC for one aircraft at a time. For Optionally Piloted Aircraft (OPA), PIC must meet UAS guidance requirements for training, pilot licensing, and medical requirements when operating OPA as a UAS. 3. The PIC must conduct a pre-takeoff briefing as applicable prior to each launch. The briefing should include but is not limited to the: a. Contents of the COA, b. Altitudes to be flown, c. Mission overview including handoff procedures, d. Frequencies to be used, e. Flight time, including reserve fuel requirements, f. Contingency procedures to include lost link, divert, and flight termination, and g. Hazards unique to the flight being flown. Note: Flight Crew Member (UAS). In addition to the flight crew members identified in 14 CFR Part 1, Definitions and Abbreviations, an Unmanned Aircraft System flight crew members include pilots, sensor/payload operators, and visual observers and may include other persons as appropriate or required to ensure safe operation of the aircraft. 4. All operations will be conducted in compliance with Title 14 CFR Part 91. Special attention should be given to: a. § 91.3 Responsibility and authority of the pilot in command b. § 91.13 Careless or reckless operation c. § 91.17 Alcohol or drugs d. § 91.103 Preflight Actions e. § 91.111 Operating near other aircraft. f. § 91.113 Right-of-way rules: Except water operations g. § 91.115 Right-of-way rules: Water operations h. § 91.119 Minimum safe altitudes: General i. § 91.123 Compliance with ATC clearances and instructions. j. § 91.133 Restricted and prohibited areas k. § 91.137 Temporary flight restrictions in the vicinity of disaster/hazard areas l. § 91.145 Management of aircraft operations in the vicinity of aerial demonstrations and major sporting events m. § 91.151 Fuel requirements for flight in VFR conditions n. § 91.155 Basic VFR weather minimums o. § 91.159 VFR cruising altitude or flight level Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 6 of 26 2015-WSA-41-COA-TS p. § 91.209 Aircraft Lights q. § 91.213 Inoperative instruments and equipment r. § 91.215 ATC transponder and altitude reporting equipment and use s. Appendix D to Part 91—Airports/Locations: Special Operating Restrictions 5. Unless otherwise authorized as a special provision, all operations must be conducted in visual meteorological conditions (VMC) during daylight hours in compliance with Title 14 of the Code of Federal Regulations (CFR) Part 91 §91.155 and the following: 6. Special Visual Flight Rules (VFR) operations are not authorized. a. VFR cloud clearances specified in 14 CFR Part 91 §91.155, must be maintained, except in Class G airspace where Class E airspace visibility requirements must be applied, but not less than 3 statute miles (SM) flight visibility and 1000’ ceiling. b. Flights conducted under Instrument Flight Rules (IFR) in Class A airspace shall remain clear of clouds. NOTE: Deviations from IFR clearance necessary to comply with this provision must have prior ATC approval. c. Chase aircraft must maintain 5 NM flight visibility. 7. Night operations are prohibited unless otherwise authorized as a special provision. 8. Operations (including lost link procedures) must not be conducted over populated areas, heavily trafficked roads, or an open-air assembly of people. D. Air Traffic Control (ATC) Communications. 1. The pilot and/or PIC will maintain direct, two-way communication with ATC and have the ability to maneuver the unmanned aircraft in response to ATC instructions, unless addressed in the Special Provision Section. a. When required, ATC will assign a radio frequency for air traffic control during flight. The use of land-line and/or cellular telephones is prohibited as the primary means for in-flight communication with ATC. 2. The PIC must not accept an ATC clearance requiring the use of visual separation, sequencing, or visual approach. 3. When necessary, transit of airways and routes must be conducted as expeditiously as possible. The unmanned aircraft must not loiter on Victor airways, jet routes, Q and T routes, IR routes, or VR routes. 4. For flights operating on an IFR clearance at or above 18,000 feet mean sea level (MSL), the PIC must ensure positional information in reference to established National Airspace System Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 7 of 26 2015-WSA-41-COA-TS (NAS) fixes, NAVAIDs, and/or waypoints is provided to ATC. The use of latitude/longitude positions is not authorized, except oceanic flight operations. 5. If equipped, the unmanned aircraft must operate with: a. An operational mode 3/A transponder with altitude encoding, or mode S transponder (preferred) set to an ATC assigned squawk. b. Position/navigation and anti-collision lights on at all times during flight unless stipulated in the special provisions or the proponent has a specific exemption from 14 CFR Part 91.209. 6. Operations that use a Global Positioning System (GPS) for navigation must check Receiver Autonomous Integrity Monitoring (RAIM) notices prior to flight operations. Flight into a GPS test area or degraded RAIM is prohibited for those aircraft that use GPS as their sole means for navigation. E. Safety of Flight. 1. The proponent or delegated representative is responsible for halting or canceling activity in the COA area if, at any time, the safety of persons or property on the ground or in the air is in jeopardy, or if there is a failure to comply with the terms or conditions of this authorization. 2. ATC must be immediately notified in the event of any emergency, loss and subsequent restoration of command link, loss of PIC or observer visual contact, or any other malfunction or occurrence that would impact safety or operations. 3. Sterile Cockpit Procedures: a. Critical phases of flight include all ground operations involving: (1) Taxi (movement of an aircraft under its own power on the surface of an airport). (2) Take-off and landing (launch or recovery). (3) All other flight operations in which safety or mission accomplishment might be compromised by distractions. b. No crewmember may perform any duties during a critical phase of flight not required for the safe operation of the aircraft. c. No crewmember may engage in, nor may any PIC permit, any activity during a critical phase of flight which could: (1) Distract any crewmember from the performance of his/her duties, or (2) Interfere in any way with the proper conduct of those duties. d. The pilot and/or the PIC must not engage in any activity not directly related to the operation of the aircraft. Activities include, but are not limited to, operating UAS sensors or other payload systems. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 8 of 26 2015-WSA-41-COA-TS e. The use of cell phones or other electronic devices is restricted to communications pertinent to the operational control of the unmanned aircraft and any required communications with Air Traffic Control. 4. See-and-Avoid. Unmanned aircraft have no on-board pilot to perform see-and-avoid responsibilities; therefore, when operating outside of active restricted and warning areas approved for aviation activities, provisions must be made to ensure an equivalent level of safety exists for unmanned operations. Adherence to 14 CFR Part 91 §91.111, §91.113 and §91.115, is required. a. The proponent and/or delegated representatives are responsible at all times for collision avoidance with all aviation activities and the safety of persons or property on the surface with respect to the UAS. b. UAS pilots will ensure there is a safe operating distance between aviation activities and unmanned aircraft at all times. c. Any crew member responsible for performing see-and-avoid requirements for the UA must have and maintain instantaneous communication with the PIC. d. UA operations will only be conducted within Reduced Vertical Separation Minimum (RVSM) altitudes, when appropriately equipped or having received a clearance under an FAA deviation. NOTE: UA operations should not plan on an en-route clearance in RVSM altitudes, without being RVSM equipped. e. Visual observers must be used at all times except in Class A, airspace, active Restricted Areas, and Warning areas designated for aviation activities. (1) Observers may either be ground-based or in a chase plane. (2) If the chase aircraft is operating more than 100 feet above/below and/or more than ½ NM laterally of the unmanned aircraft, the chase aircraft PIC will advise the controlling ATC facility. f. The PIC is responsible to ensure visual observers are: (1) Able to see the aircraft and the surrounding airspace throughout the entire flight, and (2) Able to provide the PIC with the UA’s flight path, and proximity to all aviation activities and other hazards (e.g., terrain, weather, structures) sufficiently to exercise effective control of the UA to: (a) Comply with CFR Parts 91.111, 91.113 and 91.115, and (b) Prevent the UA from creating a collision hazard. 5. Observers must be able to communicate clearly to the pilot any instructions required to remain clear of conflicting traffic, using standard phraseology as listed in the Aeronautical Information Manual when practical. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 9 of 26 2015-WSA-41-COA-TS 6. A PIC may rotate duties as necessary to fulfill operational requirements; a PIC must be designated at all times. 7. Pilots flying chase aircraft must not concurrently perform observer or UA pilot duties. 8. Pilot and observers must not assume concurrent duties as both pilot and observer. 9. The required number of ground observers will be in place during flight operations. 10. The use of multiple successive observers (daisy chaining) is prohibited unless otherwise authorized as a special provision. 11. The dropping or spraying of aircraft stores, or carrying of hazardous materials (including ordnance) outside of active Restricted, Prohibited, or Warning Areas approved for aviation activities is prohibited unless specifically authorized as a special provision. F. Crewmember Requirements. 1. All crewmembers associated with the operation of the unmanned aircraft, including chase operations, must be qualified or must be receiving formal training under the direct supervision of a qualified instructor, who has at all times, responsibility for the operation of the unmanned aircraft. 2. Pilots and observers must have an understanding of, and comply with, Title 14 Code of Federal Regulations, and/or agency directives and regulations, applicable to the airspace where the unmanned aircraft will operate. 3. Pilots, supplemental pilots, and observers must maintain a current second class (or higher) airman medical certificate that has been issued under 14 CFR Part 67, or an FAA accepted agency equivalent based on the application. 4. At a minimum, the use of alcohol and/or drugs in violation of 14 CFR Part 91 §91.17 applies to UA pilots and observers. 5. At a minimum, observers must receive training on rules and responsibilities described in 14 CFR Part 91 §91.111. §91.113 and §91.115, regarding cloud clearance, flight visibility, and the pilot controller glossary, including standard ATC phraseology and communication. 6. Recent Pilot Experience (Currency). The proponent must provide documentation, upon request, showing the pilot/supplemental pilot/PIC maintains an appropriate level of recent pilot experience in either the UAS being operated or in a certified simulator. At a minimum, he/she must conduct three takeoffs (launch) and three landings (recovery) in the specific UAS within the previous 90 days (excluding pilots who do not conduct launch/recovery during normal/emergency operations). If a supplemental pilot assumes the role of PIC, he/she must comply with PIC rating requirements. 7. A PIC and/or supplemental pilot have the ability to assume the duties of an internal or an external UAS pilot at any point during the flight. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 10 of 26 2015-WSA-41-COA-TS 8. A PIC may be augmented by supplemental pilots. 9. PIC Ratings. Rating requirements for the UAS PIC depend on the type of operation conducted. The requirement for the PIC to hold, at a minimum, a current FAA private pilot certificate or the FAA accepted agency equivalent, based on the application of 14 CFR Part 61, is predicated on various factors including the location of the planned operations, mission profile, size of the unmanned aircraft, and whether or not the operation is conducted within or beyond visual line-of-sight. a. The PIC must hold, at a minimum, a current FAA private pilot certificate or the FAA accepted agency equivalent, based on the application or 14 CFR Part 61.under all operations: (1) Approved for flight in Class A, B, C, D, E, and G (more than 400 feet above ground level (AGL)) airspace. (2) Conducted under IFR (FAA instrument rating required, or the FAA accepted agency equivalent, based on the application or 14 CFR Part 61. (3) Approved for night operations. (4) Conducted at or within 5 NM of a joint use or public airfields. (5) Requiring a chase aircraft. (6) At any time the FAA has determined the need based on the UAS characteristics, mission profile, or other operational parameters. b. Operations without a pilot certificate may be allowed when all of the following conditions are met: (1) The PIC has successfully completed, at a minimum, FAA private pilot ground instruction and passed the written examination, or the FAA accepted agency equivalent, based on the application. Airman Test reports are valid for the 24-calendar month period preceding the month the exam was completed, at which time the instruction and written examination must be repeated. (2) Operations are during daylight hours. (3) The operation is conducted in a sparsely populated location. (4) The operation is conducted from a privately owned airfield, military installation, or off-airport location. (5) Operations are approved and conducted solely within visual line-of-sight in Class G airspace. (6) Visual line-of-sight operations are conducted at an altitude of no more than 400 feet Above Ground Level (AGL) in class G airspace at all times. c. The FAA may require specific aircraft category and class ratings in manned aircraft depending on the UAS seeking approval and the characteristics of its flight controls interface. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 11 of 26 2015-WSA-41-COA-TS 10. PIC Recent Flight Experience (Currency). a. For those operations that require a certificated pilot or FAA accepted agency equivalent, based on the application, the PIC must have flight reviews 14 CFR Part 61.56, and if the pilot conducts takeoff, launch, landing or recovery the PIC must maintain recent pilot experience in manned aircraft per 14 CFR Part 61.57,; Recent Flight Experience: Pilot in Command. b. For operations approved for night or IFR through special provisions, the PIC must maintain minimum recent pilot experience per 14 CFR Part 61.57, Recent Flight Experience: Pilot in Command, as applicable. 11. Supplemental pilots must have, at a minimum, successfully completed private pilot ground school and passed the written test or the FAA accepted agency equivalent, based on the application. The ground school written test results are valid for two years from the date of completion, at which time the instruction and written examination must be repeated. If a supplemental pilot assumes the role of PIC, he/she must comply with PIC rating, currency, medical, and training requirements listed in this document. 12. Ancillary personnel such as systems operators or mission specialists must be thoroughly familiar with and possess operational experience of the equipment being used. If the systems being used are for observation and detection of other aircraft for collision avoidance purposes, personnel must be thoroughly trained on collision avoidance procedures and techniques and have direct communication with the UAS pilot, observer, and other crewmembers. 13. The Agency will ensure that Crew Resource Management (CRM) training is current for all crew members before flying operational or training missions. The CRM program must consist of initial training, as well as CRM recurrent training during every recurrent training cycle, not to exceed a 12 month interval between initial training and recurrent training or between subsequent recurrent training sessions. G. Notice to Airmen (NOTAM). 1. A distant (D) NOTAM must be issued when unmanned aircraft operations are being conducted. This requirement may be accomplished: a. Through the proponent’s local base operations or NOTAM issuing authority, or b. By contacting the NOTAM Flight Service Station at 1-877-4-US-NTMS (1-877-487- 6867) not more than 72 hours in advance, but not less than 48 hours prior to the operation, unless otherwise authorized as a special provision. The issuing agency will require the: (1) Name and address of the pilot filing the NOTAM request (2) Location, altitude, or operating area (3) Time and nature of the activity. 2. For proponents filing their NOTAM with the Department of Defense: The requirement to file with an Automated Flight Service Station (AFSS) is in addition to any local procedures/requirements for filing through the Defense Internet NOTAM Service (DINS). Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 12 of 26 2015-WSA-41-COA-TS H. Data Reporting. 1. Documentation of all operations associated with UAS activities is required regardless of the airspace in which the UAS operates. This requirement includes COA operations within Special Use airspace. NOTE: Negative (zero flights) reports are required. 2. The proponent must submit the following information through UAS COA On-Line on a monthly basis: a. The number of flights conducted under this COA. (A flight during which any portion is conducted in the NAS must be counted only once, regardless of how many times it may enter and leave Special Use airspace between takeoff and landing) b. Aircraft operational hours per flight c. Ground control station operational hours in support of each flight, to include Launch and Recovery Element (LRE) operations d. Pilot duty time per flight e. Equipment malfunctions (hardware/software) affecting either the aircraft or ground control station f. Deviations from ATC instructions and/or Letters of Agreement/Procedures g. Operational/coordination issues h. The number and duration of lost link events (control, vehicle performance and health monitoring, or communications) per aircraft per flight. I. Incident/Accident/Mishap Reporting. Immediately after an incident or accident, and before additional flight under this COA, the proponent must provide initial notification of the following to the FAA via the UAS COA On-Line forms (Incident/Accident). 1. All accidents/mishaps involving UAS operations where any of the following occurs: a. Fatal injury, where the operation of a UAS results in a death occurring within 30 days of the accident/mishap b. Serious injury, where the operation of a UAS results in a hospitalization of more than 48 hours, the fracture of any bone (except for simple fractures of fingers, toes, or nose), severe hemorrhage or tissue damage, internal injuries, or second or third-degree burns c. Total unmanned aircraft loss d. Substantial damage to the unmanned aircraft system where there is damage to the airframe, power plant, or onboard systems that must be repaired prior to further flight e. Damage to property, other than the unmanned aircraft. 2. Any incident/mishap that results in an unsafe/abnormal operation including but not limited to: Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 13 of 26 2015-WSA-41-COA-TS a. A malfunction or failure of the unmanned aircraft’s on-board flight control system (including navigation) b. A malfunction or failure of ground control station flight control hardware or software (other than loss of control link) c. A power plant failure or malfunction d. An in-flight fire e. An aircraft collision f. Any in-flight failure of the unmanned aircraft’s electrical system requiring use of alternate or emergency power to complete the flight g. A deviation from any provision contained in the COA h. A deviation from an ATC clearance and/or Letter(s) of Agreement/Procedures i. A lost control link event resulting in (1) Fly-away, or (2) Execution of a pre-planned/unplanned lost link procedure. 3. Initial reports must contain the information identified in the COA On-Line Accident/Incident Report. 4. Follow-on reports describing the accident/incident/mishap(s) must be submitted by providing copies of proponent aviation accident/incident reports upon completion of safety investigations. Such reports must be limited to factual information only where privileged safety or law enforcement information is included in the final report. 5. Public-use agencies other than those which are part of the Department of Defense are advised that the above procedures are not a substitute for separate accident/incident reporting required by the National Transportation Safety Board under 49 CFR Part 830 §830.5. 6. This COA is issued with the provision that the FAA be permitted involvement in the proponent’s incident/accident/mishap investigation as prescribed by FAA Order 8020.11, Aircraft Accident and Incident Notification, Investigation, and Reporting. FLIGHT STANDARDS SPECIAL PROVISIONS A. Contingency Planning 1. Point Identification. The proponent must submit contingency plans that address emergency recovery or flight termination of the unmanned aircraft (UA) in the event of unrecoverable system failure. These procedures will normally include Lost Link Points (LLP), Divert/Contingency Points (DCP) and Flight Termination Points (FTP) for each operation. LLPs and DCPs must be submitted in latitude/longitude (Lat/Long) format along with a graphic representation plotted on an aviation sectional chart (or similar format). FTPs or other accepted contingency planning measures must also be submitted in latitude/longitude (Lat/Long) format along with a graphic representation plotted on an aviation sectional chart, Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 14 of 26 2015-WSA-41-COA-TS or other graphic representation acceptable to the FAA. The FAA accepts the LLPs, DCPs, FTPs, and other contingency planning measures, submitted by the proponent but does not approve them. When conditions preclude the use of FTPs, the proponent must submit other contingency planning options for consideration and approval. At least one LLP, DCP, and FTP (or an acceptable alternative contingency planning measure) is required for each operation. The proponent must furnish this data with the initial COA application. Any subsequent changes or modifications to this data must be provided to AJV-13 for review and consideration no later than 30 days prior to proposed flight operations. 2. Risk Mitigation Plans. For all operations, the proponent must develop detailed plans to mitigate the risk of collision with other aircraft and the risk posed to persons and property on the ground in the event the UAS encounters a lost link, needs to divert, or the flight needs to be terminated. The proponent must take into consideration all airspace constructs and minimize risk to other aircraft by avoiding published airways, military training routes, NAVAIDs, and congested areas. In the event of a contingency divert or flight termination, the use of a chase aircraft is preferred when the UAS is operated outside of Restricted or Warning Areas. If time permits, the proponent should make every attempt to utilize a chase aircraft to monitor the aircraft to a DCP or to the FTP. In the event of a contingency divert or flight termination, the proponent will operate in Class A airspace and Special Use airspace to the maximum extent possible to reduce the risk of collision with non-participating air traffic. a. LLP Procedures. (1) LLPs are defined as a point, or sequence of points where the aircraft will proceed and hold at a specified altitude, for a specified period of time, in the event the command and control link to the aircraft is lost. The aircraft will autonomously hold, or loiter, at the LLP until the communication link with the aircraft is restored or the specified time elapses. If the time period elapses, the aircraft may autoland, proceed to another LLP in an attempt to regain the communication link, or proceed to an FTP for flight termination. LLPs may be used as FTPs. In this case, the aircraft may loiter at the LLP/FTP until link is re-established or fuel exhaustion occurs. (2) For areas where multiple or concurrent UAS operations are authorized in the same operational area, a segregation plan must be in place in the event of a simultaneous lost link scenario. The segregation plan may include altitude offsets and horizontal separation by using independent LLPs whenever possible. b. DCP Procedures. (1) A DCP is defined as an alternate landing/recovery site to be used in the event of an abnormal condition that requires a precautionary landing. Each DCP must incorporate the means of communication with ATC throughout the descent and landing (unless otherwise specified in the Special Provisions) as well as a plan for ground operations and securing/parking the aircraft on the ground. This includes the availability of ground control stations capable of launch/recovery, communication equipment, and an adequate power source to operate all required equipment. (2) For local operations, the DCP specified will normally be the airport/facility used for launch and recovery; however, the proponent may specify additional DCPs as alternates. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 15 of 26 2015-WSA-41-COA-TS (3) For transit and/or mission operations that are being conducted in Class A airspace or Class E airspace above flight level (FL)-600, DCPs will be identified during the flight to be no further than one hour of flight time at any given time, taking into consideration altitude, winds, fuel consumption, and other factors. If it is not possible to define DCPs along the entire flight plan route, the proponent must identify qualified FTPs along the entire route and be prepared to execute flight termination at one of the specified FTPs if a return to base (RTB) is not possible. (4) It is preferred that specified DCPs are non-joint use military airfields, other government-owned airfields, or private-use airfields. However, the proponent may designate any suitable airfield for review and consideration. c. Flight Termination Procedures. (1) Flight termination is the intentional and deliberate process of performing controlled flight into terrain (CFIT). Flight termination must be executed in the event that all contingencies have been exhausted and further flight of the aircraft cannot be safely achieved or other potential hazards exist that require immediate discontinuation of flight. FTPs or alternative contingency planning measures must be located within power off glide distance of the aircraft during all phases of flight and must be submitted for review and acceptance. The proponent must ensure sufficient FTPs or other contingency plan measures are defined to accommodate flight termination at any given point along the route of flight. The location of these points is based on the assumption of an unrecoverable system failure and must take into consideration altitude, winds, and other factors. (2) Unless otherwise authorized, FTPs must be located in sparsely populated areas. Except for on- or near-airport operations, FTPs will be located no closer than five nautical miles from any airport, heliport, airfield, NAVAID, airway, populated area, major roadway, oil rig, power plant, or any other infrastructure. For offshore locations, the proponent must refer to appropriate United States Coast Guard (USCG) charts and other publications to avoid maritime obstructions, shipping lanes, and other hazards. Populated areas are defined as those areas depicted in yellow on a VFR sectional chart or as determined from other sources. (a) It is preferred that flight termination occurs in Restricted or Warning Areas, government-owned land, or offshore locations that are restricted from routine civil use. However, the proponent may designate any suitable location for review and consideration. (b) The proponent is required to survey all designated areas prior to their use as an FTP. All FTPs will be reviewed for suitability on a routine and periodic basis, not to exceed six months. The proponent assumes full risk and all liability associated with the selection and use of any designated FTP. (c) It is desirable that the proponent receive prior permission from the land owner or using agency prior to the use of this area as an FTP. The proponent should clearly communicate the purpose and intent of the FTP. (d) For each FTP, plans must incorporate the means of communication with ATC throughout the descent as well as a plan for retrieval/recovery of the aircraft. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 16 of 26 2015-WSA-41-COA-TS (e) Contingency planning must take into consideration all airspace constructs and minimize risk to other aircraft by avoiding published airways, military training routes, NAVAIDs, and congested areas to the maximum extent possible. (f) In the event of a contingency divert or flight termination, if time permits, the use of a chase aircraft is preferred when the UA is operated outside of Restricted or Warning Areas. (g) In the event of a contingency divert or flight termination or other approved contingency measures, the proponent will operate in Class A airspace and Special Use airspace to the maximum extent possible to reduce the risk of collision with non-participating air traffic. B. Night Operation Limitations. The following measures are considered adequate to ensure an acceptable level of safety for UAS night operations. UAS night operations are those operations that occur between the end of evening civil twilight and the beginning of morning civil twilight, as published in the American Air Almanac, converted to local time. (Note: this is equal to approximately 30 minutes after sunset until 30 minutes before sunrise). 1. For Class D - UAS launch and recovery operations will take place wholly within Class D airspace while the ATC tower is open and the Class D active. 2. For Class D - The mixing of civil manned and unmanned traffic within Class D airspace during launch and recovery operations is prohibited. 3. All classes of airspace - External pilots and UAS ground observer(s) must be in place 30 minutes prior to night operations to ensure dark adaptation. 4. All classes of airspace - Ground observers will undergo additional training on the lighting configuration of the UAS to ensure proper recognition during flight at night. 5. For Class D - In addition to the ground observers, ATCT will monitor the Tower Display Monitor (TDM) display, if available, as a supplement to ensure no traffic is approaching the controlled airspace without making the required radio contact. Additionally, information from the Tower Display Monitor will be used to help reduce possible night time optical illusions. If the TDM is not operational, night operations will not be authorized. C. 14 CFR Part 91.209. The proponent 's airworthiness criteria must include a performance analysis of the light emitting diode (LED) position lights installed to comply with Title 14 of the Code of Federal Regulations ( 1 4 CFR) Section 91.209. This performance analysis must ensure the position lights are of sufficient intensity, placement, and coverage to allow pilot(s) of other aircraft to determine the orientation and direction of flight of the proponent's aircraft. If the proponent has not established a criterion to evaluate aircraft position lights they must reference the applicable sections of 14 CFR parts 23, 25, 27, or 29, relating to minimum performance standard s for aircraft position lights. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 17 of 26 2015-WSA-41-COA-TS AIR TRAFFIC CONTROL SPECIAL PROVISIONS A. Coordination Requirements. 1. Proponent must coordinate operational details, including NOTAM information, and a cell/land line to be used in the event of an emergency, with Seattle ARTCC at (253) 351- 3520, Chinook Approach at (509) 542-4209, and Eastern Oregon Regional (PDT) ATCT at (541) 278-1993 (as appropriate) one hour prior to the start of UAS operations. The NOTAM filed in accordance with standard provision G.1. will serve the coordination requirement for Salt Lake ARTCC. 2. The area identified in the NOTAM and during the coordination phone calls must be restricted to the airspace to be flown that day, and not for the entire approved operating area in attachment 1. 3. Proponent must notify Seattle ARTCC, Pendleton Airport Tower, or Chinook Approach (as appropriate) within 15 minutes after completion of UAS operations. 4. Due to Military Training Route (MTR) Operations 100 feet AGL and above near the UAS Operations Area, Contact the MTR scheduling agency at least 24 hours prior to flight operations to de-conflict the airspace, noting UAS operations in Northern Oregon with the specific location within the UAS Operations Area to be flown that day, at or below 9,999 feet MSL, and advise of NOTAM number. If unable to deconflict with the appropriate MTR scheduling agency, keep well clear of the MTR. Scheduling Agency contact information is as follows: MTR Number Scheduling Agency Phone Number Segments MTR Width VR-1301 124 OSS, Boise, ID 208-422-6127 A-C 5nm VR-1351 NAS Whidbey Island Range Schedules 360-257-2877 I-K 4nm VR-1352 NAS Whidbey Island Range Schedules 360-257-2877 A-B 4nm VR-1353 NAS Whidbey Island Range Schedules 360-257-2877 D-E 4nm VR-1354 NAS Whidbey Island Range Schedules 360-257-2877 B-D 4nm IR-304 366 OSS, Mountain Home AFB, ID 208-828-2172/4607 A-D On Centerline IR-329 62 Oss, McChord Field, WA 253-982-9925 C-E 5nm IR-341 NAS Whidbey Island Range Schedules 360-257-2877 B-C 4nm IR-342 NAS Whidbey Island Range Schedules 360-257-2877 A-B; I-J 4nm IR-343 NAS Whidbey Island Range Schedules 360-257-2877 B-H 4nm *MTR widths are either side of centerline *For simplification of working hours amongst all facilities, call between 0800-1600 local time for the applicable facility. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 18 of 26 2015-WSA-41-COA-TS B. Communication Requirements. 1. Chase aircraft must maintain direct, two-way communication with UAS PIC and ATC. ATC contact information is as follows: Location (Airport ATC Facility ID) Frequency (MHz) Phone Number Seattle ARTCC Lexington (9S9) 132.6 253-351-3520 Seattle ARTCC La Grande (LGD) 132.6 253-351-3520 Seattle ARTCC Monument (12S) 128.15 253-351-3520 Seattle ARTCC Enterprise (8S4) 123.95 253-351-3520 Seattle ARTCC Joseph State (JSY) 123.95 253-351-3520 Salt Lake 128.05 ARTCC Baker (BKE) 801-320-2564 Chinook Appr. Pendleton (PDT) 133.15 509-542-4209 Pendleton Twr. Pendleton (PDT) 119.7 541-278-1993 2. Chase aircraft/UAS PIC must monitor the appropriate CTAF when operating within 4 nm of an airport. 3. Chase aircraft / UAS PIC must continuously monitor Eastern Oregon Regional ATCT on 119.7 MHz during operations in Pendleton Airport Class D airspace. 4. For operations without a chase aircraft, Special Provisions A and D will be used in lieu of maintaining direct two-way communications with ATC. 5. For operations without a Chase Aircraft, the UAS PIC must monitor and make periodic position reports including UA position and altitude, on the Common Traffic Advisory Frequency (CTAF) when within 4nm of an airport. C. Procedural Requirements. 1. Operations are not authorized within Baker City Class E surface airspace. 2. For Non-Chase aircraft operations, UAS operations must remain within the proponent defined visual surveillance/detection capability limits of 4,000 feet vertically and 1.5 nautical miles horizontally. 3. Launching, landing, or operating an unmanned aircraft from or on lands and waters administered by McKay Creek National Wildlife Refuge, Cold Spring National Wildlife Refuge, North Fork Umatilla Wilderness Area, Eagle Cap Wilderness Area, John Day Fossil Beds National Monument, Wenaha Tucannon Wilderness Area, or North Fork John Day Wilderness Area is prohibited without the authorization of the respective agency land manager. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 19 of 26 2015-WSA-41-COA-TS D. Operations in Pendleton Class D Airspace 1. Inside PDT Class D Airspace: a) UAS operations must be conducted per the Letter of Agreement between East Oregon Regional Airport ATCT, Pasco TRACON, and the Oregon National Guard dated February 23, 2015 (as amended/ superseded). Where different, the procedures in this COA have priority. b) Maintain altitude: at or below 4,000 ft MSL (as assigned by PDT ATCT) c) UAS operations allowed only with clearance from PDT ATCT. d) NW, NE and SW Holding Points (as depicted in Attachment 1 “Operations in PDT Class D Airspace”) will be used as directed by PDT ATCT. Holding altitude: 3,500 MSL or as assigned. e) Use of non-TSO certified transponder is prohibited as per 14 CFR 91.215(a). E. Emergency/Contingency Procedures. 1. Lost Link Procedures: In the event of a lost link, the UAS pilot will immediately notify the applicable Air Traffic Control facility using the contact information below, state pilot intentions, and comply with the following provisions: Location (Airport ATC Facility ID) Frequency (MHz) Phone Number Seattle ARTCC Lexington (9S9) 132.6 253-351-3520 Seattle ARTCC La Grande (LGD) 132.6 253-351-3520 Seattle ARTCC Monument (12S) 128.15 253-351-3520 Seattle ARTCC Enterprise (8S4) 123.95 253-351-3520 Seattle ARTCC Joseph State (JSY) 123.95 253-351-3520 Salt Lake 128.05 ARTCC Baker (BKE) 801-320-2564 Chinook Appr. Pendleton (PDT) 133.15 509-542-4209 Pendleton Twr. Pendleton (PDT) 119.7 541-278-1993 a. Comply with those procedures outlined in Attachment 2. b. If lost link occurs within a restricted or warning area, or the lost link procedure above takes the UA into the restricted or warning area – the aircraft will not exit the restricted or warning areas until the link is re-established. c. The unmanned aircraft lost link mission will not transit or orbit over populated areas. d. Lost link programmed procedures will avoid unexpected turn-around and/or altitude changes and will provide sufficient time to communicate and coordinate with ATC e. Lost link orbit points shall not coincide with the centerline of Victor airways. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 20 of 26 2015-WSA-41-COA-TS 2. Lost Communications: Comply with those procedures outlined in Attachment 3. 3. Loss of Visual Contact between Chase Aircraft and UAS: If a ground observer or chase aircraft loses sight of the Unmanned Aircraft (UA), the UAS PIC will be notified immediately. If the UA is visually reacquired promptly, the mission may continue, if not, the UAS PIC must immediately terminate the flight. The Chase Aircraft is outfitted with a secondary UAS Ground Control Station (GCS), which includes a terrain map displaying the UAS. The observer can view the UAS’s current position using this GCS. If visual line of sight is lost the observer can determine the UAS position by referencing geographic / electronic navigation points, referencing the GCS display, and reacquire the UAS visually. D. Operations Area See Attachment 1. AUTHORIZATION This Certificate of Waiver or Authorization does not, in itself, waive any Title 14 Code of Federal Regulations, nor any state law or local ordinance. Should the proposed operation conflict with any state law or local ordinance, or require permission of local authorities or property owners, it is the responsibility of Test Site – University of Alaska - Fairbanks to resolve the matter. This COA does not authorize flight within Special Use Airspace (SUA) without notification and de-confliction with the using agency. Test Site – University of Alaska - Fairbanks is hereby authorized to operate the Arcturus T-20 Unmanned Aircraft System in the operations area depicted in the Activity section of this attachment. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 21 of 26 2015-WSA-41-COA-TS Attachment 1 2015-WSA-41 Operations Area Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 22 of 26 2015-WSA-41-COA-TS Pt Latitude Longitude 1 46⁰ 00' 00.00"N 119⁰ 00' 00.00"W 2 46⁰ 00' 00.00"N 116⁰ 55' 00.00"W 3 44⁰ 30' 00.00"N 117⁰ 12' 00.00"W 4 44⁰ 30' 00.00"N 120⁰ 00' 00.00"W 5 45⁰ 35' 00.00"N 120⁰ 00' 00.00"W 6 45⁰ 35' 00.00"N 119⁰ 30' 00.00"W To the point of Beginning Altitude: At or below 9,999 feet above Mean Sea Level (MSL) Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 23 of 26 2015-WSA-41-COA-TS Operations in PDT Class D Airspace: Lost Link Coordinate Table: Lost Link Orbit: N 45º46’46.00” W 118º48’11.00” Lost Link holding altitude: 3,500 ft MSL NW Holding: N 45º43’32.00” W 118º51’33.00” NE Holding: N 45º43’30.00” W 118º47’49.00” SW Holding: N 45º39’05.00” W 118º51’33.00” Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 24 of 26 2015-WSA-41-COA-TS Attachment 2 LOST LINK PROCEDURE(S) In the event of a lost link, the UAS pilot will immediately notify the appropriate ATC facility using the contact information below (for PDT Class D operations, see specific procedures below), state pilot intentions, and comply with the following provisions: ATC Facility Location (Airport ID) Frequency (MHz) Phone Number Seattle ARTCC Lexington (9S9) 132.6 253‐351‐3520 Seattle ARTCC La Grande (LGD) 132.6 253‐351‐3520 Seattle ARTCC Monument (12S) 128.15 253‐351‐3520 Seattle ARTCC Enterprise (8S4) 123.95 253‐351‐3520 Seattle ARTCC Joseph State (JSY) 123.95 253‐351‐3520 Salt Lake ARTCC Baker (BKE) 128.05 801‐320‐2564 Chinook Appr. Pendleton (PDT) 133.15 509‐542‐4209 Pendleton ATCT Pendleton (PDT) 119.7 541‐278‐1993 1. A lost link flight plan will be verified and input into the control software prior to launch. This flight plan can be adjusted while in flight. 2. Within PDT Class D Airspace: a. The UAS pilot will immediately notify Eastern Oregon Regional ATCT on 119.7 MHz or (541) 278-1993 and Pasco/Tri Cities TRACON ( Chinook Approach) on assigned frequency or (509) 542-4209 (backup) state pilot intentions, and comply with the following provision specific procedures: b. Proceed to the Lost Link holding point (depicted in attachment 1) at an altitude of 3,500 ft MSL. The UA will orbit at this location until link is re-established. If link has not been re-established after 15 minutes, then UAS will return to PDT and execute an auto landing. 3. In the remainder of the PUR Test Range, the UAS will proceed to the designated LLP and orbit at established altitude until link is re-established. 4. Primary selection for LLP will be the Return Home point, unless conditions require another point. 5. If link is not re-established within 15 minutes of reaching the LLP, the aircraft will proceed to the Return Home Point if not collocated, whence the autopilot will initiate an autonomous landing sequence. 6. If LLP is collocated with Return Home point, after 15 minutes of reaching the LLP the autonomous landing sequence will commence. 7. If the UAS is established at an altitude above 1,000’ AGL, it will spiral down to 1,000’ AGL prior to initiation of the landing sequence. 8. Should the pilot be able to regain control manually, the landing sequence may be conducted in manual mode. 9. The UA lost link mission will not transit or orbit, over populated areas. 10. Lost link orbit points do not coincide with the centerline of Victor airways. 11. Lost link programmed procedures will avoid unexpected turn-around and/or altitude changes and will provide sufficient time to communicate and coordinate with ATC. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 25 of 26 2015-WSA-41-COA-TS Attachment 3 LOST COMMUNICATIONS PROCEDURE(S) 1. Lost Communication between UAS PIC and Visual Observer (VO) a. In the event voice communication between UAS PIC and VO are lost, the appropriate ATC facility will be notified immediately using the contact information below. The UAS can continue to operate as originally cleared, as long as an acceptable alternate direct two-way communications are maintained between the UAS PIC and the Visual Observer. ATC or the UAS PIC may terminate operations if the alternate communication method detracts from safety. ATC Facility Location (Airport ID) Frequency (MHz) Phone Number Seattle ARTCC Lexington (9S9) 132.6 253‐351‐3520 Seattle ARTCC La Grande (LGD) 132.6 253‐351‐3520 Seattle ARTCC Monument (12S) 128.15 253‐351‐3520 Seattle ARTCC Enterprise (8S4) 123.95 253‐351‐3520 Seattle ARTCC Joseph State (JSY) 123.95 253‐351‐3520 Salt Lake ARTCC Baker (BKE) 128.05 801‐320‐2564 Chinook Appr. Pendleton (PDT) 133.15 509‐542‐4209 Pendleton ATCT Pendleton (PDT) 119.7 541‐278‐1993 b. PIC must immediately land the UAS if communication with the visual observer is lost. c. The UAS PIC will maintain two-way communication with ground-based Visual Observers via Land Mobile Radio (LMR). These radios will be fully charged and tested prior to all flights. d. The UAS PIC will maintain two-way communication with airborne VOs via chase plane secondary VHF radio. These radios will be tested prior to UAS launch. e. An observer may be located within 25 ft of the UAS PIC during flights, making radio communications unnecessary. f. Should circumstances arise whereupon a ground-based VO is required to be located more than 25 ft, or separated by a structure, from the UAS PIC, the radio will be utilized. g. Cell phones will provide redundant communications. Phone numbers will be pre- coordinated between PIC and VO(s). h. Should an airborne VO be in use, the second radio, onboard the chase aircraft or with the UAS PIC, may be used for internal communications with ATC concurrence. The PIC with two operational radios will be responsible for any required ATC communications for the formation. Version 2.1: June 2012

FAA FORM 7711-1 UAS COA Attachment Page 26 of 26 2015-WSA-41-COA-TS 2. Lost Communications between UAS PIC and ATC for chase aircraft operations: a. In the event that radio communications between UAS PIC and ATC are lost, ATC must be notified immediately by telephone using the contact information below: ATC Facility Location (Airport ID) Frequency (MHz) Phone Number Seattle ARTCC Lexington (9S9) 132.6 253‐351‐3520 Seattle ARTCC La Grande (LGD) 132.6 253‐351‐3520 Seattle ARTCC Monument (12S) 128.15 253‐351‐3520 Seattle ARTCC Enterprise (8S4) 123.95 253‐351‐3520 Seattle ARTCC Joseph State (JSY) 123.95 253‐351‐3520 Salt Lake ARTCC Baker (BKE) 128.05 801‐320‐2564 Chinook Appr. Pendleton (PDT) 133.15 509‐542‐4209 Pendleton ATCT Pendleton (PDT) 119.7 541‐278‐1993 The UAS can continue to operate as originally cleared, as long as an acceptable alternate direct two-way communications are maintained between ATC and the UAS PIC. ATC or the UAS PIC may terminate operations if the alternate communication method detracts from safety. b. The means of communications available to the UAS PIC for the purpose of communicating with ATC: i. VHF radio which will be tested prior to each activity. ii. Cell phone, by which the PIC will be able to reach ATC personnel via recorded telephone line. The phone number will have been pre-coordinated with the ATC supervisor. iii. If a chase aircraft is being used, the chase aircraft PIC can communicate with ATC for the formation. c . Should these means of communications fail to provide the necessary levels of safety, all flight activity will cease, and the UAS PIC will land the UAS. Version 2.1: June 2012


Document Created: 2016-07-12 20:20:12
Document Modified: 2016-07-12 20:20:12
© 2025 FCC.report
This site is not affiliated with or endorsed by the FCC