2009-WSA-92 1 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. DEPARTMENT OF TRANSPORTATION FEDERAL AVIATION ADMINISTRATION CERTIFICATE OF WAIVER OR AUTHORIZATION Department of Homeland Security Customs and Border Protection ADDRESS 1355 Customs Drive March ARB, CA 92518 This certi?cate is issued for the operations speci?cally described hereinafter. No person shall conduct any operation pursuant to the authority of this certi?cate except in accordance with the standard and special provisions contained in this certi?cate, and such other requirements of the Federal Aviation Regulations not speci?cally waived by this certi?cate. OPERATIONS AUTHORIZED eration of the Predator-B UA era Ions operational area. LIST OF WAIVED REGULATIONS BY SECTION AND TITLE STANDARD PROVISIONS 1. A copy of the application made for this certi?cate shall be attached and become a part hereof. 2. This certi?cate shall be presented for inspection upon the request of any authorized representative of the Federal Aviation Administration, or of any State or municipal of?cial charged with the duty of enforcing local laws or regulations. 3. The holder of this certi?cate shall be responsible for the strict observance of the terms and provisions contained herein. 4. This certi?cate is nontransferable. Note-This certi?cate constitutes a waiver of those Federal rules or regulations speci?cally 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 certi?cate 2009-WSA-92 is effective from December 1, 2010 through November 30, 2011, 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-13 Williams (Region) (Signature) November 29 2010 Air Traffic Manager. Unmanned Aircraft Svstems (Date) (Title) FAA Form 7711-1 (7-74) 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation Unauthorized release may result in civil penalty or other action For US. government agencies, public disclosure is governed by 5 552 and 49 CFR parts 15 and 1520. ATTACHMENT to FAA FORM 7711-1 Issued To: Department of Homeland Security Customs and Border Protection (CBP) Address: 1355 Customs Drive March ARB, CA 92518 eration of the Predator-B UA In an airspace- speci?cally defined in Attachment Fur ose: To rescribe UAS operating requirement? Win the National Airspace System (NAS) for the purpose of opera Iona lg 3. Dates of Use: This COA (2009-WSA-92) is valid from December 1, 2010, through November 30, 2011. Should a renewal become necessary, the proponent shall advise the FAA, in writing, no later than 60 days prior to the requested effective date. General Provisions: 0 The review of this activity is based on our current understanding of UAS operations, and the impact of such operations in the NAS, and therefore should not be considered a precedent for future operations. As changes occur in the UAS industry, or in our understanding of it, there may be changes to the limitations and conditions for similar operations. 0 All personnel connected with the UAS operation must comply with the contents of this authorization and its provisions. 0 This COA will be reviewed and amended as necessary to conform to changing UAS policy and guidance. Safetv Provisions: Unmanned Aircraft (UA) have no on-board pilot to perform see-and-avoid responsibilities, and therefore, when operating outside of restricted areas, special provisions must be made to ensure an equivalent level of safety exists for operations had a pilot been on board. In accordance with 14 CFR Part 91, General Operating and Flight Rules, Subpart J-Waivers, 14 CFR 91.903, Policy and Procedures, the following provisions provide acceptable mitigation of 14 CFR 91.113 and must be complied with: 2009-WSA-92 3 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520.    For the purpose of see-and-avoid, visual observers must be utilized at all times except in Class A and (b) (7)(E) restricted areas, warning areas. The observers may either be ground based or in a chase plane. The UA must remain within a lateral distance of no more than 2.5 NM and 3,000 feet vertically from the visual observer. If the chase aircraft is operating more than 100 ft above/below and or ½ nm laterally of the UA, the chase aircraft PIC will advise the controlling ATC facility. The distances listed are the maximum, at no time will the UA be operated at a distance beyond the visual line of sight for the visual observer. UAS pilots will ensure there is a safe operating distance between manned and unmanned aircraft at all times in accordance with 14 CFR 91.111, Operating Near Other Aircraft, and 14 CFR Part 91.113, Right-of-Way Rules. Additionally, UAS operations are advised to operate well clear of all known manned aircraft operations. The dropping or spraying of aircraft stores, or carrying of hazardous materials (included ordnance) outside of active Restricted, Prohibited, or Warning Areas is prohibited unless specifically authorized in the Special Provisions of this COA. Airworthiness Certification Provisions:   UA must be shown to be airworthy to conduct flight operations in the NAS. Public Use Aircraft must contain one of the following: o A civil airworthiness certification from the FAA, or o A statement specifying that the Department of Defense Handbook “Airworthiness Certification Criteria” (MIL-HDBK-516), as amended, was used to certify the aircraft or o Equivalent method of certification. Pilot / Observer Provisions:   Pilot Qualifications: UA pilots interacting with Air Traffic Control (ATC) shall have sufficient expertise to perform that task readily. Pilots must have an understanding of and comply with Federal Aviation Regulations and Military Regulations applicable to the airspace where the UA will operate. Pilots must have in their possession a current(b) (7)(E) airman medical certificate that has been issued under 14 CFR 67, Medical Standards and Certification, or a military equivalent. 14 CFR Part 91.17, Alcohol or Drugs, applies to UA pilots. Aircraft and Operations Requirements: o Flight Below 18,000 Feet Mean Sea Level (MSL).  UA operations below 18,000 feet MSL in any airspace generally accessible to aircraft flying in accordance with visual flight rules (VFR) require a Special Security Instruction (SSI) TFR (TFR minimum requirements of squawk and talk) or visual observers, either airborne or ground-based. When a TFR is used for see and avoid, it will remain active for the duration of the mission. 2009-WSA-92 4 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. Use of ATC radar alone does not constitute suf?cient collision risk mitigation in airspace where uncooperative airborne operations may be conducted. 0 Flights At or Above 18,000 Feet Mean Sea Level (MSL) 0 When operating on an instrument ATC clearance, the UA pilot-in-command must ensure the following: 1. An ATC clearance has been filed, obtained and followed. 2. Positional information shall be rovide Observer Qualifications: Observers must have been provided with sufficient training to communicate clearly to the pilot any turning instructions required to stay clear of con?icting traffic. Observers will receive training on rules and responsibilities described in 14 CFR Part 91.111, Operating Near Other Aircraft, 14 CFR Part 91.113, Right-of-Way Rules, cloud clearance, in-?ight visibility, and the pilot controller glossary including standard ATC phraseolo and communication. Observers must have in their possession a currenm airman medical certificate that has been issued under 14 a rca andards and Certification, or a military equivalent. 14 CFR Part 91.17, Alcohol or Drugs, applies to UA observers. Pilot-in-Command (PIC) - 0 Visual Flight Rules (VFR) as applicable: 0 The PIC is the person directly responsible for the operation of the UA. The responsibility and authority of the pilot in command as described by 14 CFR Part 91.3 (or military equivalent), applies to the UAS PIC. The PIC operating a UA in line of sight must pass at a minimum the required knowledge test for a commercial pilot certificate, or military equivalent, as stated in 14 CFR Part 61.125, and must keep their aeronautical knowledge up to date. 0 There is no intent to suggest that there is any requirement for the UAS PIC to be quali?ed as a crewmember of a manned aircraft. 0 Pilots ?ying a UA on other than instrument ?ight plans beyond line of sight of the PIC must possess a minimum of a current commercial pilot certi?cate, or military equivalent in the category and class, as stated in 14 CFR Part 61.125. 0 Instrument Flight Rules (IFR) as applicable: . The PIC is the person directly responsible for the operation of the UA. The responsibility and authority of the pilot in command as described by 14 CFR Part 91.3 (or military equivalent), applies to the UAS PIC. The PIC must be a certified pilot (minimum of commercial pilot) of manned aircraft (FAA or military equivalent) in category and class of aircraft ?own. 2009-WSA-92 5 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520.  The PIC must also have a current/appropriate instrument rating (manned aircraft, FAA or military equivalent) for the category and class of aircraft flown.  Pilot Proficiency – VFR/IFR as applicable: o Pilots will not act as a VFR/ IFR PIC unless they have had three qualified proficiency events within the preceding 90 days.  The term “qualified proficiency event” is a UAS-specific term necessary due to the diversity of UAS types and control systems.  A qualified proficiency event is an event requiring the pilot to exercise the training and skills unique to the UAS in which proficiency is maintained. o Pilots will not act as an IFR PIC unless they have had six instrument qualifying events in the preceding six calendar months (an event that requires the PIC to exercise instrument flight skills unique to the UAS).  PIC Responsibilities: o Pilots are responsible for a thorough preflight inspection of the UAS. Flight operations will not be undertaken unless the UAS is airworthy. The airworthiness provisions of 14 CFR Part 91.7, Civil Aircraft Airworthiness, or the military equivalent, apply. o One PIC must be designated at all times and is responsible for the safety of the UA and persons and property along the UA flight path. o The UAS pilot will be held accountable for controlling their aircraft to the same standards as the pilot of a manned aircraft. The provisions of 14 CFR Part 91.13, Careless and Reckless Operation, apply to UAS pilots.  Pilot/Observer Task Limitations: o Pilots and observers must not perform crew duties for more than one UA at a time. o Chase aircraft pilots must not concurrently perform either observer or UA pilot duties along with chase pilot duties. o Pilots are not allowed to perform concurrent duties both as pilot and observer. o Observers are not allowed to perform concurrent duties both as pilot and observer. Standard Provisions: These provisions are applicable to all operations unless indicated otherwise in the Special Provisions section.  The UA PIC shall maintain direct two-way communications with ATC and have the ability to maneuver the UA per their instructions. The PIC shall comply with all ATC instructions and/or clearances. (b) (7)(E)  If equipped, the UA shall operate with an operational mode transponder, with (b) (7)(E) or mode transponder (preferred) set to an ATC assigned squawk. (b) (7)(E) 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. Operations outside of restricted areas, warning areas, rohibited areas desi nated for aviation use and/o airspach in the Special Provisions section. Operations conducted under VFR rules shall operate at appropriate VFR altitudes for direction of ?ight (14 CFR Part 91.159). The UA PIC or chase plane PIC (whichever is applicable) will notify ATC of any in ?ight emergency or aircraft accident as soon as practical. A copy of this COA will be maintained on site by the PIC or designated representative. The Department of Homeland Security Customs and Border Protection and/or its representatives, is responsible at all times for collision avoidance with non- participating aircraft and the safety of persons or property on the surface with respect to the UAS. Special Provisionserations shall be conducted wit In the event of a lost link, CB The UAS operator will immediatel (ATC) and coordinate the lost link profil Air Traffic Control 2009-WSA-92 7 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520. a. If lost link occurs 3. All 0 erations outside of Warnin areas, Restricted 4. Landline Numbers in the event of Lost Link/Emergency/Lost Comm: 2009-WSA-92 8 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USAC 552 and 49 CFR parts 15 and 1520. f. g. h. i. 5. The CBP Predator UAS Area of Res onsibilit This 0 erational are is defined in Attachment a. Mission lannin ,?lin into or? in 7. CBP operations shall be conducted under: a. within the boundaries of the UAS b. opera Iona area eine In ac ment#1. 8. Visual observers must be positioned within 2.5 nautical miles laterally and 3000 feet vertically to exercise see-and-avoid responsibilities required by 14 CFR Part 91.113, Right-of- Way Rules: except Water Operations. 2009-WSA-92 9 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. 9. Departure Procedures. a. Departure procedures will be accordance with paragraph 6 of the- between CBP and KRDR AFB Attachment #4 . 10. Recovery Procedures. UA recovery must be in accordance with paragraph 7 of the LOA between CBP and KRDR AFB (Attachment climb and descent transitions to/fro 12. Launch and recove of the 14. Communications Requirements. Any visual observer, radar monitor, or sensor operator charged with providing collision avoidance for the UA must have direct communication with the UA pilot. 15. Lost Communications. CBP must comply with procedures de?ned in Attachment #3 that will be utilized in the event of lost communications between the UAS pilot and ATC. 2009-WSA-92 1O WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USAC 552 and 49 CFR parts 15 and 1520. 16.Trans onder Failure. If the UAS trans onder fails, the Pl 17.ATC Radar Outa e. lfthe PIC is notified that there is a radar outa 18. Emergency Procedures. CBP must comply with emergency procedures contained in Attachment 19. Radar/Sensor Observer. The radar/sensor operator must be thoroughly familiar with and possess operational experience with the equipment being utilized for observation and detection of other aircraft for collision avoidance urposes. The CBP shall utilize the Air Marine erations Center AMOC accompns e? 20.Fli ht Plannin Re uirements: CBP shall fil 21 . Coordination. CBP must conduct coordination: 2009-WSA-92 1 1 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520. The appropriate number of ground observers shall be in place and have communications with the appropriate controlling agency and Ground Control Station in order to meet the 2.5mile/3000 ft. visual re uirement. e. For oerations that will deart or arriv f. All round observers shall undero additional trainin 2009-WSA-92 12 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520. event of an emer enc 24. Contingency Operations. a. Lost Link Points LLP ar 1) For local 0 erations, the DCPs ecifie or ranSI an or mISSlon opera Ions hat are being conducted in DCPs ma be identified alon the route of ?ight, 2009-WSA-92 13 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520. ht termination is 1) The location of the FT 2) 3) 4) For each FT d. In the event of a contin enc divert or ?i ht terminatio 2009-WSA-92 14 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. 25. CBP will ensure that Crew Resource Management (CRM) training is completed by all crew members before flying operational or training missions. The course 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. 26. The UA PIC shall hold, at a minimu_certi?cate or equivalent. 27. provr specraize raining or as een administered. 28. Department of Homeland Security-CBP accepts all liability for operations that occur outside of FAA ?ight information regions (FIR) and is responsible for coordination with appropriate air navigation service providers. This does not imply that the FAA is aware or authorizes any specific proposed operations that will occur outside FAA Fle. NOTAM: A Notice to Airman 0 Name and Address of pilot filing NOTAM request 0 Location, Altitude or the operating Area 0 Time and nature of the activity Incident Accident and Normal Reporting Provisions: The following information is required to document routine and unusual occurrences associated with UAS activities in the NAS. 2009-WSA-92 1 5 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. The proponent for the COA shall provide the following information to Donald.E.Grampp@faa.gov on a basis: Number of ?ights conducted under this COA. Pilot duty time per ?ight. Unusual equipment malfunctions (hardware/software). Deviations from ATC instructions. Operational/coordination issues. All periods of loss of link (telemetry, command and/or control) 000000 0 The following shall be submitted via email, COA On-line or phone (202-385-4542, cell 443-569-1732) to Donald.E.Grampp@faa.gov within 24 hours and prior to any additional flight under this COA: All accidents or incidents involving UAS activities, including lost link. 0 Deviations from any provision contained in the COA. This COA does not, in itself, waive any Federal Aviation Regulation (FAR) nor any state law or local ordinance. Should the proposed operation con?ict with any state law or local ordinance, or require permission of local authorities or property owners, it is the responsibility of the De artment of Homeland Securit Customs and Border Protection to resolve the matte he Department of Homeland Security ro ec Ion IS ere authorized to operate the Predator Unmanned Aircraft System UAS in the operations area depicted in ?Activity? above and Attachment 1 below. 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. (b) (7)(E) 16 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. (b) (7)(E) 17 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. (b) (7)(E) 18 2009-WSA-92 19 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. (b) (7)(E) Attachment #1 (cont’d) 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. (b) (7)(E) 20 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. (b) (7)(E) 21 2009-WSA-92 22 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520. 2009-WSA-92 23 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520? LATITUDE LONGITUDE LATITUDE LONGITUDE 2009-WSA-92 24 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520? LATITUDE LONGITUDE LATITUDE LONGITUDE 2009-WSA-92 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. (b) (7)(E) 25 2009-WSA-92 26 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CPR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. 2009-WSA-92 27 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520? Attachment #3 ERGENCY PROCQURE Emergency Termination: Unable to sustain ?ight and return to base In the event of Flight Termination, the PIC- Note: As with manned aircraft operations, the UA may not be able to proceed in a controlled fashion to the flight termination location. Lost Link: Loss of command uplink, downlink, or both links between the ground control station and the UA . In the event of a Lost Link condition, the Pl - 2009-WSA-92 28 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action For US government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520? 0 erations withi 2009-WSA-92 29 WARNING: This correspondence may contain Sensitive Security lnforrnation and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action For US government agencies, public disclosure is governed by 5 USC 552 and 49 CFR parts 15 and 1520? 0 erations withi the PIC shall coordinate with Lost Communications: Loss of radio communications between the PIC and ATC In the event of Lost Radio Communications between the PIC and ATC, the PIC EGMENT LOST LINK LATITUDE I LONGITUDE FTP 1 FTP 2 FTP 3 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USE 552 and 49 CFR parts 15 and 1520. FTP 4 FTP 5 - WAYPOINT 1 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 552 and 49 CFR parts 15 and 1520. SEGMENT LOST LINK LATITUDE LONGITUDE WAYPOINT 1 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as de?ned in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For US. government agencies, public disclosure is governed by 5 USE 552 and 49 CFR parts 15 and 1520. FTP LOST LINK LATITUDE I LONGITUDE FTP 12 FTP 13 WAYPOINT 1 LL Point for S38 Attachment #4 WARNING: This correspondence may contain Sensitive Security Information and attachments that are controlled under 49 CFR 15 and 1520. No part of this correspondence may be disclosed to persons without a "need to know", as defined in CFR parts 15 and 1520, except with the written permission of the Administrator of the Transportation Security Administration or the Secretary of Transportation. Unauthorized release may result in civil penalty or other action. For U.S. government agencies, public disclosure is governed by 5 U.S.C 552 and 49 CFR parts 15 and 1520. CBP/USAF GRAND FORKS AFB Letter of Agreement FOR OFFICIAL USE ENFORCEMENT SENSITIVE 1H ?9 GRAND FORKS AIR FORCE BASE, GRAND FORKS, NORTH DAKOTA and DEPARTMENT OF HOMELAND SECURITY (DHS), U.S. CUSTOMS AND BORDER PROTECTION (CBP) UNMANNED AIRCRAFT SYSTEMS (UAS), NORTH DAKOTA UAS OPERATIONS LETTER OF AGREEMENT (LOA) Effective Date: 15 December 2008 SUBJECT: CBP UAS USE OF GRAND FORKS AIR FORCE BASE This Letter of Agreement (LOA) establishes a mutual understanding and cooperation for an operating capability for CBP Air and Marine, Predator UASs operating from Grand Forks Air Force Base GFAFB - KRDR) in support of the border enforcement missio AOR . For the oses of this LOA, GFAFB is Reference authorities include, but are not limited to: a) Grand Forks AFB Instruction 13-101, Air?eld and Air Traffic Operations. b) CBP UAS Supplement to the CBP Aviation Operations Handbook (AOH). c) FAA Certi?cate of Waiver or Authorization (COA), signed 2 December 2008 issued to Dept of Homeland Security, U.S. Customs and Border Protection, fo? Operations. d) FAA UAPO Guidance Document 08-01, Unmanned Aircraft Systems Operations in the U.S. National Airspace System, Interim Operational Approval Guidance, dated 13 March. 2008. e) FAA Order 7610.4 Special Operations, Chapter 12, Section 9, UAS Operations in the NAS, dated 18 January, 2007. (Change 2, 14 Feb 2008) f) CBP NDUASOC Mishap Plan (Interim), dated 11 July 2008 g) 319 ARW Aircraft Mishap Response Plan h) Grand Forks AFB Instruction 24-101, Flight line Driving Program 1. IDENTIFICATION OF AGENCIES FOR PURPOSES OF THIS DOCUMENT a) Of?ce of primary responsibility for Air Traf?c Operations and Air?eld Management at GFAFB is the 319 b) Scheduling agency for the GFAFB is the 319 088/080. c) U.S. Customs and Border Protection, North Dakota UAS Operations Center exercises CBP UAS operational authority. FOR OFFICIAL USE ENFORCEMENT SENSITIVE I 1ND 59} It try-kw Olry Au?s Q. Re *0 5 FOR OFFICIAL USE ENFORCEMENT SENSITIVE 9h :9 Iry ,0 (4&0 s? d) Mission scheduling, reporting, operational and logistical support for CBP UAS operations is provided by the CBP UAS Flight Operations Center (FOC) located at the UAS operating site on Grand Forks AFB, hereafter referred to as the RED RIVER FOC. 8) Primary point of contact for the safe, effective execution of each CBP UAS mission is the Red River FCC and the assigned CBP UAS Pilot-in-Command (UAS PIC). f) All operations will be in accordance with reference authorities cited in this document. Should conflicting written guidance exist, the most restrictive guidance will apply until resolved in writing by all signatories to this LOA, however, SAFETY OF FLIGHT SHALL ALWAYS TAKE PRECEDENCE. 2. RESPONSIBILITIES a. The RED RIVER FOC shallCoordinate this LOA and other applicable agreements with all involved parties to effect site selection, preparation, equipage, usage, and sustainment of CBP UAS operations at GFAFB. Provide the 319 088/080 a schedule of CBP UAS ?ight activi ith updates as appropriate. Any con?icts with the Transient aircraft schedule and the daily CBP UAS Flight Schedule will be sent to 319 088/080 and 319 Ensure appropriate GFAFB and/or other NOTAMs have been accurately published. Notify GFAFB Air Traf?c Control (ATC) anytime a ?ight is cancelled prior to takeoff in order to cancel applicable airspace reservations. Coordinate with the 319 ARW to ensure CBP UAS mishaps at GFAFB are initially responded to, in accordance with (IAW) the CBP UASOC Mishap Plan and the 319 ARW Aircraft Mishap Response Plan. Coordinate with General Atomics-Aeronautical Systems Inc (GA-ASI) for the training of GFAFB ?rst-responders on unique CBP UAS operating/handling characteristics and hazardous materials. ln-process and train applicable CBP UAS site personnel who will drive on the ?ight line, perform ground visual observer duties, or serve as the CBP UAS PIC. Establish written procedures for visitor control and badging, and authorization for photography of CBP UAS-speci?c areas on GFAFB. 10) Ensure the GFAFB Fire Department Dispatch of?ce (at the phone number listed on the daily ?ight schedule) is advised of any UAS ground or in-flight emergency which occurs while GFAFB is closed. NOTE: Another agency, Le. Minneapolis Air Route Traffic Control Center FOR OFFICIAL USE ENFORCEMENT SENSITIVE 2 A FOR OFFICIAL USE ENFORCEMENT SENSITIVE (ARTCC), Air and Marine Operations Center (AMOC) etc. may ful?ll this noti?cation requirement. 11)Advise GFAFB ATC upon completion of all daily CBP UAS operations. 12 WI retamt or mon s. b. The CBP UAS PIC for each flight shall: 1) Receive a one-time, initial GFAFB briefing prior to performing pilot duties for CBP UAS operations. 2) All UAS Ple are required to receive a brie?ng by GFAFB ATC, GFAFB Air?eld Management, and the GFAFB Weather of?ce prior to performing pilot duties. The in-briefs will be annotated on the CBP UAS Site ln-processing Checklist, and will be kept on ?le. 3) Review appropriate GFAFB and other NOTAMs. 4) Decon?ict power-up, uplink, and downlink frequencies and/or procedures with other UAS operators at GFAFB. 5) Use the call sigqor lmissions the traf?c pattern, ensunngt A transponder Mod as assigned by ATC) with Mod 6) Conduct deiartures and arrivals from 7) Maintain a communication link with GFAFB ATC at all times when within GFAFB Aiiroach Control Airsiace. Primai link with GFAFB ATC will be via radio- 8) Ensure the UAS complies with departure, arrival, and Lost Link routing profiles this LOA and the COA. 9) . Th AS will 10) Advise ATC immediately if the UAS experiences Lost Link (an emergency), or if experiencing any other situation or emergency that requires airspace priority. 11) Maintain Lost Link mission routing and initial Lost Link parameters as described in paragraph 8 (Lost Link Procedures). Any changes to published Lost Link routing or parameters must be pre-coordinated with and approved by ATC prior to implementation. FOR OFFICIAL USE ENFORCEMENT SENSITIVE 3 la 0N4 I FOR OFFICIAL USE ENFORCEMENT SENSITIVE I 91? c. GFAFB Air?eld Operations shall: 1) Coordinate with the RED RIVER FOC for desired airspace. Notify-s necessary, of CBP UAS ?ying periods. Advise other military users of GFAFB of scheduled CBP UAS ?ight activity. 2) 3) 4) 319 will provide Red River FOC Transient aircraft schedules and updates. 5) Provide the RED RIVER FOC emergency points of contact for Air Traf?c Controllers and Weather support personnel for after-hours support. NOTE: This information will be included by the RED RIVER FOC on the Daily CBP UAS Flight Schedule. 6) Ensure that any mishaps within GFAFB related to CBP UAS operations are initially responded to IAW the 319 ARW Mishap Plan. 3. GENERAL 3. A qualified UAS PIC, as speci?ed in the COA, shall be at the controls of the UAS at all times. An Instructor Pilot (IP) will be present in the GCS if a pilot is non-current or in training status. The UAS PIC will abide by any guidance, control instruction, and/or direction issued by ATC, CBP Government Flight Representative, or GA-ASI UAS Site Manager to suspend operations due to a safety-of?flight issue. 4. CBP UAS OPERATIONS AT GRAND FORKS AIR FORCE BASE a. General Procedures 1) Staging of CBP UAS aircraft prior to king of the CBP UAS after ?ight will be accom lished in front 0 ny pre/post ?ight activity will ir?of the hangar oors so that the taxiway in front of not be blocked. 2) Associated CBP UAS ?ight and ground equipment will UAS operational site located on the ramp outside of or withimNo equipment will be permanently positioned on the paved portion of the main ramp area adjacent to the CBP UAS operational site. (Attachment 1) FOR OFFICIAL USE ENFORCEMENT SENSITIVE 4 ?Iy 30 FOR OFFICIAL USE ENFORCEMENT SENSITIVE 3) An alternate operating location will be-nd will be available anytime the primary location cannot be used (requires coordination with air?eld manager and other base agencies.) (Attachment 1) b. Flight Operations 1) Associated CBP UAS ?ight equi nt will be at the CBP UAS RED RIVER FOC 2> mus be at? irspace shall be conducted unde as speci?ed in 14 CFR Part 91 and the COA. 4) The UAS PIC shall have direct radio communications with GFAFB ATC for UAS ground and ?ight operations clearance After takeoff (OR. (Attachment 2) 5) A primary radio is required for ATC communication. At all times, the UAS PIC will also keep?in the GCS for communications with ATC. If complete radio failure occurs, a UAS crewmember or the FCC will contact ATC at: GFAFB TOWER: in the GFAF irspace. If approved by the an I le 7) The CBP UAS traffic pattern If unable to comply, ATC SHALL be advised and chan es to ?i ht atterns will be approved. traf?c permining? 8) The CBP UAS shall be considered a? aircraft for Same Runway Separation (SRS) and ircraft for ?Wake Turbulence? separation. 9) A ?Closed traf?c iattern? mai be approved by GFAFB ATC howeve- OR OFFICIAL USE ENFORCEMENT SENSITIVE 5 s/ FOR OFFICIAL USE ENFORCEMENT SENSITIVE to) wiles?one or more deployed ground visual observers are required by the COA. The observers shall irect communication with the UAS PIC when the UAS is within GFAF hand shall immediately inform the UAS PIC of con?icting traf?c. The PIC will coordinate with ATC prior to executing any maneuvers needed to avoid con?icting traf?c. 11 flown to comply with FAA-mandated ground visual observer observation limits speci?ed in the COA. 12) Manned aircraft emergencies shall take priority over unmanned aircraft emergencies. 1 It on-intermittent loss of the comman in rom to the UAS. See paragraph 8 (Lost Link Procedures) for further guidance. 5. TRAFFIC PATTERN PROCEDURES a. The UAS will adhere to standard traf?c atterns as determined GFAFB ATC however, the acute UAS will avoid the flow of manned aircraft ?ights and maneuver, or if required, hold in a ?ight attem as directed GFAFB ATC. The UAS will normally arrive and depart via a iunless directed otherwise by GFAFB ATC. b. The UAS shall remain othenlvise by GFAFB ATC. while in the pattern at GFAFB, unless directed 0. Multiple UAS low approaches or touch-and?go landings for formal UAS syllabus aircrew training, pilot currency/re?currency requirements or for functional, maintenance checks of the UAS and its components may be performed with GFAFB ATC approval. All formal and informal training and maintenance flight checks will be conducted on ->asis with manned aircraft operations within the GFAFB traf?c pattern. aera lmlsaera lmls. ral eal le. d. Unless othen/vise directed GFAFB ATC, standard CBP UA e. In the event holding is required, the UAS will be instructed to hold within the GFAFB FB Tower instructions remainin clear of the Runway FOR OFFICIAL USE ENFORCEMENT SENSITIVE 6 f. ?uthorized by COA may be conducted. 6. DEPARTURE PROCEDURES a. When ready for departure, the UAS PIC will call GFAFB Tower for departure clearance. 1) a. b. Climb to the assigned altitude, and/or proceed on-course? nstructions. 2) UAS DEPARTURE b. Climb to the assigned altitude, and/or proceed on-course? instructions. 7. RECOVERY PROCEDURES 3. nications with GFAFB RAPCON prior to! hen ready to return to GFAFB for recovery. FAF wr prov: appropria recovery instructions. (Attachment 2) 9 area. 1) UAS RECOVERY a. FOR OFFICIAL USE ENFORCEMENT SENSITIVE 7 FOR OFFICIAL USE ENFORCEMENT SENSITIVE b. Low approaches, touch-and-g multi Ie approaches may be coordinated with GFAFB ATC asis with manned aircraft, provided visual observation requirements are met IAW the COA. 2) UAS RECOVER a. b. Low approaches, touch-andgo landin and multi le approaches may be coordinated with GFAFB ATC?basis with manned aircraft, provided visual observation requirements are met IAW the COA. b. Unless othenNise directed by GFAFB ATC standard CBP UA -nstructions will be a In the event holding is required, the UAS will be instructed to hold with-in the GFAFB _n accordance with GFAFB Tower or RAPCON instructions, remainin if the Runway-arrivalldeparture course an? d. Holding will normally be a? MSL. C. 8. FLIGHT TERMINATION, LOST LINK, LOST COMMUNICATION EMERGENCY MISSION PROFILE (LLEMP) PROCEDURES Different scenarios exist for ?Flight Termination, Lost Link, or Lost Communication?. These procedures are based on the location of the UAS when the ?link? with the aircraft is lost. a. In all cases, when a loss of aircraft link occurs. the UAS PIC FOR OFFICIAL USE ENFORCEMENT SENSITIVE 8 FOR OFFICIAL USE ENFORCEMENT SENSITIVE b. If loss of aircraft link occurs between the UAS and the GCS while on the ground, the UAS will follow procedures delineated in Attachment 4 ?Lost Link-Aircraft on the Ground?. c. In the event of a Lost Link situation during GFAFB TRAFFIC PATTERN OPERATIONS touch and goes) the UA FOR OFFICIAL USE ENFORCEMENT SENSITIVE 9 FOR OFFICIAL USE ENFORCEMENT SENSITIVE VERY the UAS POINT FIX RADIAL DME LAT LON FOR OFFICIAL USE ENFORCEMENT SENSITIVE 10 FOR OFFICIAL USE ENFORCEMENT SENSITIVE FAILURE ransponder fails, the UAS PI 10. EMERGENCIES a. For UAS IFE situations, the UAS PIC FOR OFFICIAL USE ENFORCEMENT SENSITIVE 11 11. ADMINISTRATION a. The CBP UAS F00 and GFAFB shall initiate a review of this LO to etermine app me reVISIons or mo I we Ions. preclu proposed revisions or modi?cations to this LOA made by a signatory party at any time; such revisions or modi?cations shall be effective upon written approval by all parties. b. This LOA shall be revised or modified should the FAA COA or a NOTAM be issued (or amended) which substantively changes the UAS operating procedures from GFAFB. c. Public Affairs Guidance 1) Speci?c inquiries regarding the mission of the Red River FOC, CBP aircraft. operating schedules or personnel from the public or the news media shall be referred to the Deputy Director Air Operations (DDAO) NDAB UAS Operations at 2) When it is believed that Red River FOC personnel, CBP UAS or other aircraft are involved in an aircraft incident or accident, take the following action: 3) d. Financial liability rests with the Department of Homeland Security (DHS) for any expenses related to a CBP UAS mishap, reclamation, and subsequent investigation IAW the agreement between DHS and Department of Defense. e. CBP will reimburse all support required by GFAFB and GFAFB contract personnel. If and when applicable, GFAFB ATC overtime dollars will be transferred to GFAFB for support of CBP UAS operations IAW the Base Support Agreement. FOR OFFICIAL USE ENFORCEMENT SENSITIVE 12 FOR OFFICIAL USE ENFORCEMENT SENSITIVE AS Operations 319th Air Refueling Wing North Dakota Air Branch Attachments: 1. CBP primary and alternate location 2. CBP UAS TFR and Arrival/Departure Procedure depiction 3. Lost Link Holding Point depiction 4. CBP UAS Lost Link procedure and Emergency Mission Pro?le FOR OFFICIAL USE ENFORCEMENT SENSITIVE 13 3 H>F?mlmm Hm: ZOE PZHEHUKOKZH Hm: FOR OFFICIAL USE ENFORCEMENT SENSITIVE 15 u>r?mZHm Hm: 10m Mm: Again?ho A 10? Cm? rOmH CZX. m 3i tacomacqom 5 =6 m40. :6 30 208.. bw xi: 395mm 9.88: 08838ban.me 3 828:3 ?33.0: 8 3m :63 832.336: 68:03. 58:: >40 2 :6 8.85.8 woo: 8.9 - 0m30m>mw 105 Cm?w m?wZM??E/?u 3. mac?w mz?uO?wO?wz??UZA. homa Car i 0: 3m. 9.055 3:52, -- iL 10w Oman?>9 HZmOWOmz?wz?m 2w