## Materials and Methods
Through this and related efforts, UAF achieved a majority of the initial technical and operational goals outlined in the mission sets. UTM TCL1 campaign: Using the crawl, walk, run approach, testing began with relatively sparse UAS operations in either remote or lightly populated urban areas. The basic requirements for this phase included the ability for a UAS crew to request and reserve a defined volume of airspace, for the UAS to be capable of reporting its position to NASA, for mission durations to be tracked, and for the system status of UAS to be logged (ready, airborne, rogue, landed, and mission terminated). The interface for communications was provided through a UAS System Services (USS) provider. Selected excerpts from the NASA TCL1 Statement of Work (SoW) are provided in Appendix A. \begin{table}
\begin{tabular}{c c c c} \hline \hline
**UTM Phase** & **Dates and Location** & **Program Focus** & **UAS Employed** \\ \hline \multirow{3}{*}{TCL1} & May 2016 & Demonstration of simultaneous & Aeromao Aeromapper \\  & UAF PFRR & flight and tracking of multiple UAS & ING Responder \\  & & at test sites across the country. & S800 Parmigan \\ \hline \multirow{3}{*}{TCL2a} & October 2016 & Demonstration of multiple agencies & \\  & Reno-Stead Airport & and operators employing dissimilar & UAF: S800 Parmigan \\ \hline \multirow{3}{*}{TCL2b} & & Demonstration of multiple UAS & \\  & & being employed in proximate & \\  & May/June 2017 & airspace, including & S900 Hexacopter \\  & UAF Campus and PFRR & & Exploration of potential automated & S1000 October \\  & & Sense And Avoid (SAA) protocols & DJI Inspire 1 \\  & & and technologies. & DJI Martice 100 \\ \hline \multirow{3}{*}{TCL3} & & Same as TCL2b. Increased emphasis & ING Responder \\  & & placed on UAS tracking and & S800 Parmigan \\ \cline{1-1}  & May 2018 & automated UAS deconfiction with & S900 Hexacopter \\ \cline{1-1}  & UAF Campus & manned aircraft and other UAS via & S1000 October \\ \cline{1-1}  & & SAA technology. & DJI Inspire 1 \\ \cline{1-1} \cline{2-5}  & & & DJI Martice 100 \\ \hline \hline \end{tabular}
\end{table} 
Table 1: UAF/ACUASI participation in UTM TCL1-3 campaigns. Figure 5: FAA UTM Pilot Program (UPP) conceptual overview [17]. The UTM TCL1 campaign and flight demonstration occurred in May/June 2016. The overarching focus for this effort was to demonstrate the ability for the UTM system to support coordination with UAS operators located across the country and to simultaneously track these geographically diverse operations. All six participating FAA UAS test sites (Alaska, Nevada, Texas, North Dakota, Virginia, and New York), Figure 6, each flew four UAS, for a total of 24 UAS simultaneously flown across the country. The flight paths of all UAS were depicted in real-time at the NASA Ames Research Center UTM program office, Figure 7.  
UAF's flight operations manager coordinated and controlled flight operations via radio communications with ground pilot teams and UAF's test manager. The test manager coordinated overall activities with NASA UTM personnel (telephone and internet), USS provider (voice and written notes), and the flight operations manager (radio). Details of the UAS/USS/UTM data communications are provided in Figure 9.  
The TCL1 demonstration was scheduled for the period of 19-21 April 2016, with the primary flight operations scheduled for 19 April/0800-1200 (AST). The flight operations period was divided up into three time windows: 0800-0900 hrs, 0900-1000 hrs, and 1000-1100 hrs. During each of these windows, each test site attempted to simultaneously operate four UAS locally. NASA stated criteria for a fully successful campaign was to have a total of 24 UAS at the six test sites performing concurrent flight operations. UAF employed a variety of UAS types for the TCL1 campaign. * Single-rotor UAS. The ING Responder is a helicopter design based on the Gaui X7 frame and PixHawk autopilot. * Multi-rotor UAS. The ACUASI Parmigan is a hexacopter based on the DJI S800 frame and 3 DR APM (PixHawk predecessor) autopilot.