## Materials and Methods
Relatively short flight times for the Parmigan required the UAS be recovered half-way through each flight window, then relaunched with a fresh battery. Figure 8: (**A**) NASA TCL1 Campaign Flight Assets and Locations; (**B**) ACUASI Parmigan S800, ING Responder. Figure 9: UTM architecture for UAF TCL1 [22] (p. 9). * Fixed-wing UAS. The Aeromao Aeromapper was the only fixed-wing UAS used for TCL1 and gave UAF an asset with further reach and significantly different flight performance characteristics. UAF utilized the Simulyze UTM Client interface to pass UAS data to the NASA UTM system. Simulyze was employed by several test sites and their system was well known by NASA. UAF's selected implementation was a single instance of the client simultaneously coordinating data for all four UAS. Figure 9 is a schematic depicting the system architecture. This same UTM structure was utilized by UAF during the NASA UTM TCL2 and TCL3 campaigns. A single instance of the Simulyze UTM manager was employed to input mission data (e.g., UAS vehicle identification, mission start/stop times, and status) in most cases. During some missions, multiple instances of the UTM manager were employed due to simultaneous operations involving distant locations or large numbers of UAS. As the campaign progressed, the Simulyze UTM Manager was deployed as a helpful situational awareness tool to pilots (e.g., visual indication of flight area boundaries and incursions by an aircraft or other UAS). UTM TCL2 campaign: This phase of the program consisted of two separate flight campaigns. The first event included a selectively identified (by NASA) set of agencies participating in a centralized flight demonstration held at Reno-Stead Airport in October 2016. The major portion of the TCL2 campaign was a follow-on series of events occurring at each selected UAS test site in May/June 2017. During the Reno-Stead demonstration, NASA coordinated three sets of tightly integrated flight scenarios (Figure 10A) to be conducted between five different flight crews involving dissimilar UAS, all operating within close quarters. This provided insights into the level of coordination (both manual and autonomous) that might be required for future scenarios involving multiple different agencies and pilots conducting mixed operations utilizing a mix of UAS with various performance characteristics. UAF participated in two of the three combined scenarios using the ACUASI Parmigan S800 hexacopter, Figure 10B. The second phase of the UTM program focused on sets of identified functional objectives. The overall set of mission tasks were spread between the various partner entities with consideration to workload, technical approach, teaming arrangements, and geographical and environmental considerations. Highlights from the TCL2 SoW are listed in Appendix A. UAF was selected to work directly on the communication, navigation, surveillance (CNS), and geofencing technologies/conformance monitoring sections of the SoW. The team also indirectly supported other NASA priorities, including USS technologies and procedures and human factors related to UTM data creation and display. Over the period of 15 May-9 June 2017, several flights were conducted at PFRR and UAF main campus locations as part of system capability testing, shakedown tests, and demonstration. UAF's  
Figure 10: **(A)** NASA TCL2 campaign at Reno-Stead, October 2016 [23] and **(B)** ACUASI Parmigan S800 UAS. [23]. TCL2 primary flight campaign demonstration occurred 5-9 June. UAS assets used for the missions included ACUASI's Ptarmigan S800 hexacopter, S900 hexacopter, S1000 octocopter, ING Responder helicopter, DJI Inspire 1 quadcopter, and DJI Matrice 100 quadcopter. The TCL2 flight campaign consisted of four scheduled flying days with a built-in makeup day. Flight profiles were scheduled for both an AM block and a PM block to support testing logistics. Day 1 scenario.