Integrated Test and Evaluation (ITE) Flight Test Series 4

Appendix A Reference Documents Document Number Document Title ACAS XU FTP ACAS Xu Flight Test Plan DCP-O-025 NASA Armstrong Aircrew Flight Operations Manual DO-300 RTCA MOPS for TCAS II Hybrid Surveillance EAFBI 13-100 Edward AFB Instruction Flying and Airfield Operations IT&E ADD-04 Architecture Description Document for FT4 IT&E DMP-001 Flight Test 4 Data Management Plan IT&E FT4 CONOPS.r Flight Test 4 Concept of Operations IT&E FT4 FTRD.REQ.R1 Flight Test 4 Requirements Document IT&E FT4 ORD-02 Flight Test 4 Operational Requirements Document IT&E FTP-01 Flight Test 3 Flight Test Plan NPR 7900.3 Aircraft Management Operations R-2508 R-2508 Complex Users Handbook Title 14 CFR Part 91 General Operating and Flight Rules

Appendix B Acronyms ACAS Airborne Collision Avoidance System ACE Active Coordination Emulation ADRS Aeronautical Data Link a nd Radar Simulator ADS - B Automatic Dependent Surveillance - Broadcast AESA Active Electronically Scanned Array AFRC Armstrong Flight Research Center AFRL Air Force Research Laboratory AFSR Airworthiness and Flight Safety Review AFTC Air Force Test Center APL Applied Physics Laboratory ARC Ames Research Center ARTCC Air Route Traffic Control Center A ll Pur p ose ST ructured E urocontrol Su R veillance I nforma t ion ASTERIX E X change ATAR Air - To - Air - Radar ATC Air Traffic Control C2 Command and Control CA Collision Avoidance CAS Collision Avoidance Systems CAT Collision Avoidance Threshold CDTI Cockpit Display Of Traffic Information CFR Civil Flight Regulations COA Certificate of Authorization COMM Communications CONOPS Concept of Operations CoPE Co - Project Engineers CNPC Control and Non - Payload Communications CPA Closest Point of Approach CPDS Conflict Prediction and Display System CSSA Corrective Self - Separation Alert CV Collision Volume CVSRF Crew Vehicle Simulation Research Facility DAA Detect and Avoid DAIDALUS Detect & AvoID Alerting Logic for Unmanned Systems DATR Dryden Aeronautical Test Range DCP Dryden Centerwide Procedure DGPS Differential Global Positioning System DHS Department of Homeland Security DO Director of Operations DP Descent Point DPMf Deputy Program Manager for DRR Due Regard Radar DSRL Distributed System Research Laboratory EAFB Edwards Air Force Base EAFBI Edwards Air Force Base Instruction EC Experimental Certificate EDM Engineering Development Module/Model EP Entry Point ERAM En Route Automation Modernization FAA Federal Aviation Administration FAR Federal Aviation Regulations FBO Fixed Base Operator FDDRL Flight Deck Display Research Laboratory FOM Figure of Merit FOV Field of View FP Flight Prototype FRR Flight Readiness Review FT3 Flight Test 3 FT4 Flight Test 4 FTP Flight Test Plan GA-ASI General Atomics Aeronautical Systems Inc GCS Ground Control Station GPS Global Positioning System GRC Glenn Research Center HSI Human Systems Integration HITL Human In The Loop HLA High Level Architecture HW Honeywell IAW In Accordance With IFR Instrument Flight Rules IP Initial Point IT&E Integrated Test and Evaluation ITAR International Traffic In Arms Regulations JADEM Java Architecture for DAA Extensibility and Modeling KGS Knots Ground Speed LaRC Langley Research Center LOS Loss of Separation or Line of Sight LVC Live Virtual Constructive MACS Multi Aircraft Control System MD Mission Director MHz Mega Hertz MOA Military Operating Area MOPS Minimum Operational Performance Standards MP Maneuver Point MRU Military Radar Unit NAS National Airspace System NASA National Aeronautics and Space Administration NMAC Near Mid-Air Collisions NMI Nautical Mile NOTAMS Notice To Airmen NPR NASA Procedural Requirements PE s Project Engineers PSSA Preventative Self-Separation Alert PT4 Part Task Four QNH Barometric Pressure Adjusted to Sea Level (at a given station) RA Resolution Advisory RAIF Research Aircraft Integration Facility RGCS Research Ground Control Station RTCA Radio Technical Commission for Aeronautics RUMS Remote User Monitoring System SAA Sense and Avoid SAF Stand Alone Facility SATCOM Satellite Communication SC Special Committee SimMgr Simulator Manager SMO Spectrum Management Office SOR Senior Operations Representative SPORT Space Positioning Optical Radar Tracking SS Self-Separation SSCA Self-Separation Corrective Alert SSI Separation Assurance/Sense and Avoid Interoperability SSPT Self-Separation Proximate Traffic SSWA Self-Separation Warning Alert STANAG Standardization Agreement (NATO) STM Surveillance Tracking Module TBD To Be Determined TC Test Conductor TCAS Traffic Alert and Collision Avoidance System TCOR Test Coordinator TCPA Time to Closest Point of Approach TD Test Director TSPI Time Space Position Information TLX Task Load Index ToR Terms of Reference TRACON Terminal Radar Approach Control Facility TRM Threat Resolution Module UAS Unmanned Aircraft Systems VFR Visual Flight Rules VHF Very High Frequency VID Visual Identification VSCS Vigilant Spirit Control Station WAAS Wide Area Augmentation System WCT Well Clear Threshold

Appendix C Definition of Terms Blunder A planned vertical or horizontal maneuver performed by the intruder, ownship or both aircraft that occurs at some point during the flight test encounter to intentionally stimulate conflict alerting .

The blunder maneuver is a technique by which the researcher uses to obtain data required to refine algorithm parametric logic .

Intruder Intruder aircraft (when properly equipped) provide a target solution for the self - separation algorithm under test. Both low speed, high speed, multi - ship encounters are planned using intruder aircraft. All participating intruder aircraft will be equipped with ADS - B as a minimum.

Ownship Ownship aircraft provide the self - separation algorithm host solution for testing airborne geospatial encounters with target (intruder) aircraft. The ownship may be a UAS or UAS surrogate aircraft. Self - separati on alerting solutions are presented to the ground control station pilot who determines the best course of action based on display alerting evaluation.

Mitigated Flight test encounters that are designed for the controlling UAS pilot to either manually respond to a self - separation or resolution advisory alert or monitor the aircraft response during an automatic resolution advisory alert. Mitigated test encounters are typically planned with vertical, lateral, and timing flight safety margins designed into the flight test encounters to help minimize the potential for an inflight collision.

STANAG In NATO a Standardization Agreement (STANAG) defines processes, procedures, terms, and conditions for common military or technical procedures or equipment between the member countries of the alliance. Each NATO state ratifies a STANAG and implements it within their own military.

Unmitigated The term unmitigated refers to an encounter with no self - separation (i.e., mitigating) maneuver Flight test encounters that d ue to adequate vertical offsets do not require an associated lateral offset for flight safety. Unmitigated encounters typically are non - maneuvering.

Appendix D Flight Test 4 Intruder Summary Matrix

Appendix E VSCS/DAA MOPS Alerting Symbology

Appendix F Flight Test Objective Templates

1. JADEM

2. DAIDALUS

3. CPDS

4. Radar

5. TCAS

6. Tracker

7. SC-228

National Aeronautics and Space Administration National Aeronautics and Space Administration

UAS in the NAS

FT4 Test Objectives

(SSI - ARC)

SSI - ARC FT4 Objectives

1. Validate DAA requirements in stressing cases that drive MOPS requirements, including:

High - speed cooperative intruder, Low - speed non - cooperative intruder, high vertical

closure rate encounter, and Mode C only intruder (i.e. without ADS - B).

2. Validate TCAS/DAA alerting and guidance interoperability concept in the presence of

realistic sensor, tracking and navigational errors and in multiple - intruder encounters

against both cooperative and non - cooperative intruders.

3. Validate ‘Well Clear Recovery’ guidance in the presence of realistic sensor, tracking and navigational errors.

4. Validate DAA alerting and guidance requirements in the presence of realistic sensor, tracking and navigational errors.

5. Collect data to support development and validation of trajectories specified in the DAA

MOPS for DAA system acceptance testing.

6. Collect data to supplement simulation analyses as needed due to highly variable,

preliminary or inconclusive simulation results, leveraging data from other test cases when

possible (e.g., ‘well clear recover’ validation to supplement mini - HitL results if necessary).

Additional Info

• Objectives 5 & 6 are ‘targets of opportunity’ and will rely on data collected in the other

encounters to meet the stated SSI FT4 objectives. No new FT4 requirements will be levied

from these objectives, but encounters may be refined to more closely match those detailed

in the SC - 228 verification test trajectories where practical.

• # of Encounters:

– Objective 1: 18

– Objective 2: 29

– Objective 3: 9

– Objective 4: 16

– Total: 72

– Lower priority encounters: 9

FT4 TEST OBJECTIVES – SSIWest.1.a

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: MOPS Appendix D, Section 2.3 – Aircraft

(a) high speed intruder (mitigated, >10kft MSL) Speed Limitations

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S YES NO YES YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#001 - 003

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to DAA alert.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot to manually select and execute ‘minimum’ maneuver at edge of band (or quantized altitude level).

• Aircraft speeds (non - accelerating): Ownship 200 KTAS, Intruder >500 KTAS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA alert and remains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.1.b

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: MOPS Appendix D, Section 2.3 – Aircraft

(b) high speed intruder (unmitigated, >10kft MSL) Speed Limitations

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S YES NO YES YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#004 - 006

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate removal of DAA alert(s) once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. Well Clear Recovery guidance is provided to the UAS pilot prior to CPA.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 200 KTAS, Intruder >500 KTAS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.1.c

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: MOPS Appendix D, Section 2.3 – Aircraft

(c) high speed intruder (mitigated, <10kft MSL) Speed Limitations

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO NO NO YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#007 - 009

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to DAA alert.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot to manually select and execute ‘minimum’ maneuver at edge of band (or quantized altitude level).

• Aircraft speeds (non - accelerating): Ownship 200 KTAS, Intruder 250 KIAS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA alert and remains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.1.d

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: MOPS Appendix D, Section 2.3 – Aircraft

(d) high speed intruder (unmitigated, <10kft MSL) Speed Limitations

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO NO NO YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#010 - 012

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate removal of DAA alert(s) once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. Well Clear Recovery guidance is provided to the UAS pilot prior to CPA.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 200 KTAS, Intruder 250 KIAS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.1.e

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: ACES Simulation Results – Common

(e) low speed intruder (mitigated, <10kft MSL) non - cooperative encounters

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO NO NO YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#013 - 015

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to DAA alert.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot to manually select and execute ‘minimum’ maneuver at edge of band (or quantized altitude level).

• Aircraft speeds (non - accelerating): Ownship 120 KGS, Intruder 100 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA alert and remains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.1.f

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: ACES Simulation Results – Common

(f) low speed intruder (unmitigated, <10kft MSL) non - cooperative encounters

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO NO NO YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#016 - 018

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate removal of DAA alert(s) once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. Well Clear Recovery guidance is provided to the UAS pilot prior to CPA.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 120 KGS, Intruder 100 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.2.a

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (a) high vertical closure rate 2.2.4.3 Determine Processing, 2.2.4.4

encounter (mitigated TCAS RA maneuver, >10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES

2500ft

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.80 NM

#019

Minimum Altitude Offset: 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder and the UAS pilot complies with TCAS RA guidance.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot disregards DAA guidance and follows TCAS guidance if consistent with test constraints.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts , ± 100 fpm at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. UAS pilot promptly evaluates (and complies with) TCAS RA guidance and avoids NMAC.

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.b

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (b) high vertical closure rate 2.2.4.3 Determine Processing, 2.2.4.4

encounter (unmitigated TCAS RA, >10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES

2500ft

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.80 NM

#020

Minimum Altitude Offset: 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder .

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts , ± 100 fpm at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. DAA alerting and guidance is generated once RA expires (if appropriate).

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.c

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (c) high vertical closure rate 2.2.4.3 Determine Processing, 2.2.4.4

encounter (mitigated TCAS RA maneuver, <10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES

2500ft

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.55 NM

#021

Minimum Altitude Offset : 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder and the UAS pilot complies with TCAS RA guidance.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot disregards DAA guidance and follows TCAS guidance if consistent with test constraints.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts , ± 100 fpm at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. UAS pilot promptly evaluates (and complies with) TCAS RA guidance and avoids NMAC.

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.d

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (d) high vertical closure rate 2.2.4.3 Determine Processing, 2.2.4.4

encounter ( unmitigated TCAS RA, <10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES

2500ft

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.55 NM

#022

Minimum Altitude Offset: 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder .

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts , ± 100 fpm at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. DAA alerting and guidance is generated once RA expires (if appropriate).

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.e

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (e) level - level TCAS RA 2.2.4.3 Determine Processing, 2.2.4.4

encounters (mitigated, >10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES Relative o

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.80 NM

#023 - 031

Minimum Altitude Offset: 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder and the UAS pilot complies with TCAS RA guidance.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot disregards DAA guidance and follows TCAS guidance if consistent with test constraints.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 150/ 180/210 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. DAA alerting and guidance is generated once RA expires (if appropriate).

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.f

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (f) level - level TCAS RA 2.2.4.3 Determine Processing, 2.2.4.4

encounters ( unmitigated , >10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES Relative o

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.80 NM

#032 - 040

Minimum Altitude Offset: 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder .

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 150/ 180/210 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. DAA alerting and guidance is generated once RA expires (if appropriate).

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.g

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (g) level - level TCAS RA 2.2.4.3 Determine Processing, 2.2.4.4

encounters (mitigated, <10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES Relative o

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.55 NM

#041 - 043

Minimum Altitude Offset: 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder and the UAS pilot complies with TCAS RA guidance.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot disregards DAA guidance and follows TCAS guidance if consistent with test constraints.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. DAA alerting and guidance is generated once RA expires (if appropriate).

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.h

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: (h) level - level TCAS RA 2.2.4.3 Determine Processing, 2.2.4.4

encounters ( unmitigated , <10kft). Collision Avoidance Interoperability

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA ADS - B Radar Tracker Mode C S YES NO YES YES YES Relative o

200 ft

o

0 Relative

Ownship

Scenario(s):

Lateral Offset = 0.5 NM

TCAS Alerting Boundary = 0.55 NM

#044 - 046

Minimum Altitude Offset: 200 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A corrective TCAS RA is generated for the primary intruder .

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500 FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. DAA alerting and guidance is generated once RA expires (if appropriate).

5. DAA alert(s) and guidance are removed once ownship is clear of threat.

FT4 TEST OBJECTIVES – SSIWest.2.i

Objective 2: Validate TCAS/DAA alerting and guidance interoperability concept in the MOPS Sections 2.2.4.2.4 Alerting presence of realistic sensor, tracking and navigational errors: ( i ) multi - intruder encounter 2.2.4.3 Determine Processing, 2.2.4.4

(mitigated TCAS RA maneuver, >10kft). Collision Avoidance Interoperability

System Under Test :

Configuration 300 ft

Omnibands Display : VSCS Contributing Sensors TCA Mode C ADS - B Radar Tracker S

1500 ft

YES NO YES YES YES

12.5 NM

500 ft

5.5 NM

1 NM

6 NM

Lateral Offset = 0.5 NM

Scenario(s):

TCAS Alerting Boundary = 0.8 NM

#047

Minimum Altitude Offset: ≥ 300 ft (primary), 500 ft (secondary)

Initial Intruder Course Lateral Offset: 1nmi (primary), 0 nmi (secondary)

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate DAA alerting and guidance do not interfere with UAS pilot’s ability to assess and follow TCAS RA guidance.

Success Criteria 1. A corrective TCAS RA is generated for the primary intruder and the UAS pilot complies with TCAS RA guidance.

(retest if criteria not 2. A timely DAA alert for secondary intruder is provided to the UAS pilot (timely relative to TCAS maneuver initiation).

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot complies with TCAS RA for primary intruder and follows DAA guidance for secondary intruder (after RA initiati on) .

• Aircraft speeds (non - accelerating): Ownship 180 KGS, Primary Intruder 200 KGS, Secondary Intruder (NO ADS - B) 150 KGS.

• Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship & Secondary 0/0/0, Primary Intruder: TBD climb/descent to generate RA.

• Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives and complies with TCAS corrective RA for primary intruder.

( Post - test analysis to 2. Vertical DAA guidance indicates no viable vertical maneuvers in temporal proximity to TCAS RA and while RA persists.

determine if test 3. DAA alerting and guidance for the primary intruder are removed while a TCAS RA is present for the primary intruder.

objectives are met ) 4. UAS pilot receives DAA Warning Alert for secondary intruder with associated guidance.

5. UAS pilot maneuvers according to DAA guidance and remains well clear of secondary intruder.

FT4 TEST OBJECTIVES – SSIWest.3.a

Objective 3: Validate Well Clear Recovery (WCR) guidance in the presence of realistic MOPS Section 2.2.4.3.2 DAA Guidance to sensor, tracking and navigation errors : (a) high speed intruder (mitigated, >10kft MSL) Regain Well Clear Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO NO YES YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#048 - 050

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA Well Clear Recovery guidance to UAS pilot is appropriate (reasonable, timely & responsive).

2. Validate WCR guidance results in pilot maneuvering to avoid collision and regain Well Clear .

Success Criteria 1. DAA Well Clear Recovery guidance is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to Well Clear Recovery guidance .

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: UAS pilot to ignore corrective and warning DAA alerts and respond promptly to DAA WCR guidance.

• Ignore TCAS RA guidance • Aircraft speeds (non - accelerating): Ownship 200 KTAS, Intruder >500 KTAS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA Well Clear Recovery guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA Well Clear Recovery guidance and regains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met )

FT4 TEST OBJECTIVES – SSIWest.3.b

Objective 3: Validate Well Clear Recovery (WCR) guidance in the presence of realistic MOPS Section 2.2.4.3.2 DAA Guidance to sensor, tracking and navigation errors : (b) high speed intruder (mitigated, <10kft MSL) Regain Well Clear Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO YES NO YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#051 - 053

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA Well Clear Recovery guidance to UAS pilot is appropriate (reasonable, timely & responsive).

2. Validate WCR guidance results in pilot maneuvering to avoid collision and regain Well Clear .

Success Criteria 1. DAA Well Clear Recovery guidance is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to Well Clear Recovery guidance .

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: UAS pilot to ignore corrective and warning DAA alerts and respond promptly to DAA WCR guidance.

• Ignore TCAS RA guidance • Aircraft speeds (non - accelerating): Ownship 200 KTAS, Intruder 250 KIAS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA Well Clear Recovery guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA Well Clear Recovery guidance and regains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met )

FT4 TEST OBJECTIVES – SSIWest.3.c

Objective 3: Validate Well Clear Recovery (WCR) guidance in the presence of realistic MOPS Section 2.2.4.3.2 DAA Guidance to sensor, tracking and navigation errors : (c) low speed intruder (mitigated, <10kft MSL) Regain Well Clear Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO NO NO YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#054 - 056

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA Well Clear Recovery guidance to UAS pilot is appropriate (reasonable, timely & responsive).

2. Validate WCR guidance results in pilot maneuvering to avoid collision and regain Well Clear .

Success Criteria 1. DAA Well Clear Recovery guidance is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to Well Clear Recovery guidance .

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: UAS pilot to ignore corrective and warning DAA alerts and respond promptly to DAA WCR guidance.

• Ignore TCAS RA guidance • Aircraft speeds (non - accelerating): Ownship 120 KGS, Intruder 100 KGS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA Well Clear Recovery guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA Well Clear Recovery guidance and regains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met )

FT4 TEST OBJECTIVES – SSIWest.4.a

Objective 4: Validate DAA alerting and guidance requirements in the presence of realistic MOPS Sections 2.2.4.2.4 Alerting sensor, tracking and navigational errors: a) nominal speed encounter (mitigated, >10kft) 2.2.4.3 Determine Processing Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S YES YES YES YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#057 - 059

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to DAA alert.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot to manually select and execute ‘minimum’ maneuver at edge of band (or quantized altitude level).

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA alert and remains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.4.b

Objective 4: Validate DAA alerting and guidance requirements in the presence of realistic MOPS Sections 2.2.4.2.4 Alerting sensor, tracking and navigational errors: b) nominal speed encounter (unmitigated, >10kft) 2.2.4.3 Determine Processing Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S YES YES YES YES YES Relative o

500 ft

Ownship

o

0 Relative

Scenario(s):

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

#060 - 062

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate removal of DAA alert(s) once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. Well Clear Recovery guidance is provided to the UAS pilot prior to CPA.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.4.c

Objective 4: Validate DAA alerting and guidance requirements in the presence of realistic MOPS Sections 2.2.4.2.4 Alerting sensor, tracking and navigational errors: c) maneuvering intruder (mitigated, >10kft) 2.2.4.3 Determine Processing Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S YES YES YES YES YES

500 ft

3 nmi

Relative o

2 nmi

Lateral Offset = 0 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#063 - 064

Minimum Altitude Offset ≥ 500 ft

Initial Intruder Course Lateral Offset: TBD ft.

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to DAA alert.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot to manually select and execute ‘minimum’ maneuver at edge of band (or quantized altitude level).

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA alert and remains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.4.d

Objective 4: Validate DAA alerting and guidance requirements in the presence of realistic MOPS Sections 2.2.4.2.4 Alerting sensor, tracking and navigational errors: d) maneuvering intruder (unmitigated, >10kft) 2.2.4.3 Determine Processing Configuration System Under Test : Display : VSCS Omnibands Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO YES YES YES YES

500 ft

3 nmi

Relative o

2 nmi

Lateral Offset = 0 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#065 - 066

Minimum Altitude Offset ≥ 500 ft

Initial Intruder Course Lateral Offset: TBD ft.

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate removal of DAA alert(s) once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. Well Clear Recovery guidance is provided to the UAS pilot prior to CPA.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Intruder 180 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.4.e

Objective 4: Validate DAA alerting and guidance requirements in the presence of realistic MOPS Sections 2.2.4.2.4 Alerting sensor, tracking and navigational errors: e) multiple intruder (mitigated, >10kft) 2.2.4.3 Determine Processing Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors :

500 ft

TCA Mode C ADS - B Radar Tracker

500 ft

S NO YES YES YES YES o o o Scenario(s):

Lateral Offset = 0.5 NM

#067 - 069

SS Alerting Boundary = 0.75 NM

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to DAA alert.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot to manually select and execute ‘minimum’ maneuver at edge of band (or quantized altitude level).

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Primary Intruder 180 KGS, Secondary Intruder 150 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA alert and remains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met ) Additional Information

FT4 TEST OBJECTIVES – SSIWest.4.e

Objective 4: Validate DAA alerting and guidance requirements in the presence of realistic MOPS Sections 2.2.4.2.4 Alerting sensor, tracking and navigational errors: e) multiple intruder ( unmitigated , >10kft) 2.2.4.3 Determine Processing Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors :

500 ft

TCA Mode C ADS - B Radar Tracker

500 ft

S NO YES YES YES YES o o o Scenario(s):

Lateral Offset = 0.5 NM

#070 - 072

SS Alerting Boundary = 0.75 NM

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

met) Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KGS, Primary Intruder 180 KGS, Secondary Intruder 150 KGS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) Additional Information

Additional (lower priority) encounters

FT4 TEST OBJECTIVES – SSIWest.1.h

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: <MOPS reference>

(h) high vertical closure rate encounter (unmitigated, >10kft MSL)

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO NO YES YES YES

3500ft

Relative o

500 ft

Ownship

o

0 Relative

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate removal of DAA alert(s) once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. A timely DAA warning alert is provided to the UAS pilot prior to CPA.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 150 KTAS, Intruder 180 KTAS • Encounter Length: 1 min (IP to CPA) • Stable Conditions: stable at the IP (1 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: Ownship 0/0/0, Intruder - 2500FPM/0/0 • Tolerance: ± 8 sec, ± 5 kts , ± 100 FPM at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) Additional Information SSI - INTERNAL: This is very similar to the single intruder TCAS interoperability encounter with high vertical closure rate. This should be a ss essed as

FT4 TEST OBJECTIVES – SSIWest.1.i

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: <MOPS reference>

( i ) Mode C only intruder (mitigated, <10kft MSL)

Configuration System Under Test : Omnibands Display : VSCS Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO YES NO YES YES

500 ft

Ownship

o

0 Relative

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate selected DAA maneuver results in remaining well clear, and removal of the alert once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. UAS pilot maneuvers in response to DAA alert.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: Pilot to manually select and execute ‘minimum’ maneuver at edge of band (or quantized altitude level).

• Aircraft speeds (non - accelerating) : Ownship 150 KTAS, Intruder 150/180/210 KTAS • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. UAS pilot maneuvers in response to DAA alert and remains well clear of intruder.

determine if test 3. DAA alert(s) and guidance are removed once ownship is clear of threat.

objectives are met ) Additional Information SSI - INTERNAL: Unclear if this geometry is of any utility in flight test… radar tracks are provided to the fusion tracker usually far beyond RDR… as

FT4 TEST OBJECTIVES – SSIWest.1.d FT4 TEST OBJECTIVES – SSIWest.1.j

Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: MOPS Appendix D, Section 2.3 – Aircraft Objective 1: Validate DAA requirements in stressing cases that drive MOPS requirements: <MOPS reference> high speed intruder (unmitigated, <10kft MSL) Speed Limitations (j) Mode C only intruder (unmitigated, <10kft MSL) Configuration System Under Test : Configuration System Under Test : Omnibands Omnibands Display : VSCS Display : VSCS Contributing Sensors : Contributing Sensors : TCA Mode C ADS - B Radar Tracker S NO YES NO YES YES

500 ft

Ownship

o

0 Relative

Lateral Offset = 0 NM

Lateral Offset = 0 NM

SS Alerting Boundary = 0.75 NM

SS Alerting Boundary = 0.75 NM

Minimum Altitude Offset ≥ 500 ft

Minimum Altitude Offset ≥ 500 ft

Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear. Test Objectives (TO) 1. Validate DAA alert timing allows pilot sufficient time to assess options and maneuver to remain well clear.

2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive). 2. Validate DAA guidance to UAS pilot is appropriate (reasonable, timely & responsive).

3. Validate removal of DAA alert(s) once clear of threat. 3. Validate removal of DAA alert(s) once clear of threat.

Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot. Success Criteria 1. A timely (corrective initially) DAA alert is provided to the UAS pilot.

(retest if criteria not 2. Well Clear Recovery guidance is provided to the UAS pilot prior to CPA. (retest if criteria not 2. Well Clear Recovery guidance is provided to the UAS pilot prior to CPA.

met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data). met) 3. Data collected: LVC log file, SAAProc log files, TCAS log files for ownship and intruder, SAAP file (‘raw’ surveillance data).

Test Method • MANUEVER: none. Test Method • MANUEVER: none.

• Aircraft speeds (non - accelerating): Ownship 200 KTAS, Intruder 250 KIAS • Aircraft speeds (non - accelerating) : Ownship 150 KTAS, Intruder 150/180/210 KTAS • Encounter Length: 2 min (IP to CPA) • Encounter Length: 2 min (IP to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Stable Conditions: stable at the IP (2 minutes prior to CPA) • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed. • Test Termination Criteria: targets diverging, range > 0.75 nmi ., no DAA alerts displayed.

• Climb/Roll/Pitch Rates: 0/0/0 • Climb/Roll/Pitch Rates: 0/0/0 • Tolerance: ± 8 sec, ± 5 kts at IP crossing. • Tolerance: ± 8 sec, ± 5 kts at IP crossing.

Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance Evaluation Criteria 1. UAS pilot receives DAA corrective alert with associated guidance ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat. ( Post - test analysis to 2. DAA alert(s) and guidance are removed once ownship is clear of threat.

determine if test 3. CPA prediction accuracy sufficient for DAA function. determine if test 3. CPA prediction accuracy sufficient for DAA function.

objectives are met ) objectives are met ) Additional Information Additional Information National Aeronautics and Space Administration National Aeronautics and Space Administration

UAS in the NAS

FT4 Test Objectives

(DAIDALUS)

DAIDALUS MOPS Traceback

The sections in the MOPS we will be validating for FT4 are as

follows :

• 2.2.4.2.1 DAA Well Clear Definition

• 2.2.4.3 Determine Processing

• 2.2.4.4 Collision Avoidance Interoperability

• Appendix D. UAS Maneuver Requirements

• Appendix G. DAA Alerting Logic Reference Implementation

Although we are not validating the sensors themselves, we are

characterizing how the sensors impact state estimation, include

2.2.3 DAA Surveillance Subsystem

Fly Through

TEST OBJECTIVES Demonstrate performance in a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S1

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 10000ft - 20000ft

Ownship

INT 10000ft - 20000ft

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#073

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. Establish baseline for DAIDALUS Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: 0 • Roll Rate: 0 • Pitch Rate: 0 • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each DAA alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S2

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#074

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. Establish baseline for DAIDALUS Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S3

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

Relative o

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#075

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a crossing scenario 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the crossing intrude r a ircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S4

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#076

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in an Overtaking scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S5

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

o 180 Relative

INT 10000ft - 20000ft

Ownship

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#077

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a n overtaking scenario 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the overtaken intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S6

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 10000ft - 20000ft

Ownship

INT 10000ft - 20000ft

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#078

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S7

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#079

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a front quartering scenario 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S8

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

Relative o

90 UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

3 00 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#080

Minimum Altitude Offset ≥ 3 00 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a crossing scenario 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – NO • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Ownship : 150 - 180kgs • Intruder: 150 - 180kgs Success Criteria • Data collected from MACS display (see data requirements) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM

Ownship Vertical Maneuvers

TEST OBJECTIVES Demonstrate performance in a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S17

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 10000ft - 20000ft

Ownship

INT 10000ft - 20000ft

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#083

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance 2. SAA fusion processor correctly correlates tracks 3. Determine suitability of sensor for vertical guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • ALT and VS bands provide vertical separation solution Test Method • MANEUVER – Follow ALT or VS bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Spped : Own - 150 - 180kgs, Intruder - 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • UAS Maneuvers away from intruder to remain well clear • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter then maneuvers back to course Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS vertical guidance during a Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S18

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#084

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance 2. SAA fusion processor correctly correlates tracks 3. Determine suitability of sensor for vertical guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • ALT and VS bands provide vertical separation solution Test Method • MANEUVER – Follow ALT or VS bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Spped : Own - 150 - 180kgs, Intruder - 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • UAS Maneuvers away from intruder to remain well clear • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter then maneuvers back to course Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS vertical guidance during a Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S19

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

Relative

UAS 10000ft - 20000ft

o

INT 10000ft - 20000ft

Ownship 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#085

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance 2. SAA fusion processor correctly correlates tracks 3. Determine suitability of sensor for vertical guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • ALT and VS bands provide vertical separation solution Test Method • MANEUVER – Follow ALT or VS bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Spped : Own - 150 - 180kgs, Intruder - 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • UAS Maneuvers away from intruder to remain well clear • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter then maneuvers back to course Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS vertical guidance during a Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S20

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#086

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance 2. SAA fusion processor correctly correlates tracks 3. Determine suitability of sensor for vertical guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • ALT and VS bands provide vertical separation solution Test Method • MANEUVER – Follow ALT or VS bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Spped : Own - 150 - 180kgs, Intruder - 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • UAS Maneuvers away from intruder to remain well clear • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter then maneuvers back to course Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS vertical guidance during a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S21

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

o 0 Relative

INT 10000ft - 20000ft

Ownship 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#087

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance 2. SAA fusion processor correctly correlates tracks 3. Determine suitability of sensor for vertical guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • ALT and VS bands provide vertical separation solution Test Method • MANEUVER – Follow ALT or VS bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Spped : Own - 150 - 180kgs, Intruder - 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • UAS Maneuvers away from intruder to remain well clear • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter then maneuvers back to course Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS vertical guidance during a Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S22

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#088

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance 2. SAA fusion processor correctly correlates tracks 3. Determine suitability of sensor for vertical guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • ALT and VS bands provide vertical separation solution Test Method • MANEUVER – Follow ALT or VS bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Spped : Own - 150 - 180kgs, Intruder - 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • UAS Maneuvers away from intruder to remain well clear • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter then maneuvers back to course Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS vertical guidance during a Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S23

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

Relative

o UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#089

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance 2. SAA fusion processor correctly correlates tracks 3. Determine suitability of sensor for vertical guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • ALT and VS bands provide vertical separation solution Test Method • MANEUVER – Follow ALT or VS bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec • Spped : Own - 150 - 180kgs, Intruder - 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • UAS Maneuvers away from intruder to remain well clear • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter then maneuvers back to course Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM

Horizontal Blocking Intruder

TEST OBJECTIVES Demonstrate that DAIDALUS will not guide UAS horizontally into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S25

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 10000ft - 20000ft

Ownship

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

0.7 NM 300 ft.

Lateral Offset = 0.5 NM

300 ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#091

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance to the UAS - provides solution away from primary and secondary intruders 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS does not guide the operator into a secondary encounter Test Method • MANEUVER – Follow ALT/VS/Heading bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • Speed: 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition Additional Information Follow heading bands to avoid intruder The closest point of approach (CPA) for intruder 1 is 0.5NM.

Intruder 2 should be on parallel path at a range of .7nm - 1nm at same GS TEST OBJECTIVES Demonstrate that DAIDALUS will not guide UAS horizontally into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S26

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 0.7 NM 300 ft.

Lateral Offset = 0.5 NM

300 ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#092

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance to the UAS - provides solution away from primary and secondary intruders 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS does not guide the operator into a secondary encounter Test Method • MANEUVER – Follow ALT/VS/Heading bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • Speed: 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow heading bands to avoid intruder The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate that DAIDALUS will not guide UAS horizontally into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S27

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : Relative o

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 300 ft 0.7 NM 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#093

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance to the UAS - provides solution away from primary and secondary intruders 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS does not guide the operator into a secondary encounter Test Method • MANEUVER – Follow ALT/VS/Heading bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • Speed: 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow heading bands to avoid intruder The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate that DAIDALUS will not guide UAS horizontally into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S28

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 300 ft 0.7 NM 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#094

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance to the UAS - provides solution away from primary and secondary intruders 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS does not guide the operator into a secondary encounter Test Method • MANEUVER – Follow ALT/VS/Heading bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • Speed: 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow heading bands to avoid intruder The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate that DAIDALUS will not guide UAS horizontally into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S29

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 10000ft - 20000ft

Ownship

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

0.7 NM 300 ft.

Lateral Offset = 0.5 NM

300 ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#095

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance to the UAS - provides solution away from primary and secondary intruders 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS does not guide the operator into a secondary encounter Test Method • MANEUVER – Follow ALT/VS/Heading bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • Speed: 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow heading bands to avoid intruder The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate that DAIDALUS will not guide UAS horizontally into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S30

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 0.7 NM 300 ft.

Lateral Offset = 0.5 NM

300 ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#096

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance to the UAS - provides solution away from primary and secondary intruders 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS does not guide the operator into a secondary encounter Test Method • MANEUVER – Follow ALT/VS/Heading bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • Speed: 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow heading bands to avoid intruder The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate that DAIDALUS will not guide UAS horizontally into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S31

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors : Relative o

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 300 ft 0.7 NM 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#097

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct guidance to the UAS - provides solution away from primary and secondary intruders 2. SAA fusion processor correctly correlates tracks Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS does not guide the operator into a secondary encounter Test Method • MANEUVER – Follow ALT/VS/Heading bands • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • Speed: 150 - 180kgs • Vertical Speed: 500 - 1000fpm Success Criteria • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow heading bands to avoid intruder The closest point of approach (CPA) is 0.5NM

Vertical Blocking

TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S33

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : o 0 Relative

Altitude

Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

0.7 NM

INT 2 10000ft - 20000ft

300 ft.

Lateral Offset = 0.5 NM

Scenario(s): 0 ft.

SS Alerting Boundary = 0.75 NM

500 ft #099

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which causes DAIDALUS to indicate a vertical maneuver to stay well clear 4. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow ALT/VS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Descent Rate: 1000fpm • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) for intruder 1 is 0.5NM Intruder 2 should be on parallel path at a range of .7nm - 1nm at same speed 3500ft below ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S34

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 0.7 NM 300 ft.

Lateral Offset = 0.5 NM

Scenario(s): 0 ft.

SS Alerting Boundary = 0.75 NM

500 ft #100

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which causes DAIDALUS to indicate a vertical maneuver to stay well clear 4. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow ALT/VS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Descent Rate: 1000fpm • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) for intruder 1 is 0.5NM Intruder 2 should be on parallel path at a range of .7nm - 1nm at same speed 3500ft below ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S35

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : Relative o

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

300 ft.

Ownship 0.7 NM 3000 ft.

Lateral Offset = 0.5 NM

500 ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#101

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which causes DAIDALUS to indicate a vertical maneuver to stay well clear 4. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow ALT/VS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Descent Rate: 1000fpm • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) for intruder 1 is 0.5NM Intruder 2 should be on parallel path at a range of .7nm - 1nm at same speed 3500ft below ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S36

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 300 ft.

0.7 NM

Lateral Offset = 0.5 NM 300

Scenario(s): 0 ft.

SS Alerting Boundary = 0.75 NM

500 ft #102

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which causes DAIDALUS to indicate a vertical maneuver to stay well clear 4. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow ALT/VS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Descent Rate: 1000fpm • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) for intruder 1 is 0.5NM Intruder 2 should be on parallel path at a range of .7nm - 1nm at same speed 3500ft below ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S37

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors : o 0 Relative

Altitude

Ownship

UAS 10000ft - 20000ft

0.7 NM INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

300 ft.

Lateral Offset = 0.5 NM

Scenario(s): 0 ft.

SS Alerting Boundary = 0.75 NM

500 ft #103

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which causes DAIDALUS to indicate a vertical maneuver to stay well clear 4. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear • Test Method • MANEUVER – Follow ALT/VS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Descent Rate: 1000fpm • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) for intruder 1 is 0.5NM Intruder 2 should be on parallel path at a range of .7nm - 1nm at same speed 3500ft below ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S34

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

Ownship 0.7 NM 300 ft.

Lateral Offset = 0.5 NM

Scenario(s): 0 ft.

SS Alerting Boundary = 0.75 NM

500 ft #104

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which causes DAIDALUS to indicate a vertical maneuver to stay well clear 4. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow ALT/VS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Descent Rate: 1000fpm • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) for intruder 1 is 0.5NM Intruder 2 should be on parallel path at a range of .7nm - 1nm at same speed 3500ft below ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S39

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors : Relative o

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

300 ft.

Ownship 0.7 NM 3000 ft.

Lateral Offset = 0.5 NM

500 ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#105

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which causes DAIDALUS to indicate a vertical maneuver to stay well clear 4. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow ALT/VS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Descent Rate: 1000fpm • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) for intruder 1 is 0.5NM Intruder 2 should be on parallel path at a range of .7nm - 1nm at same speed 3500ft below ownship

High/Low Altitude Maneuvering

TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S41

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : Ownship

Altitude

UAS 5000ft - 10000ft

INT 1 5000ft - 10000ft

300ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#107

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary at TCAS SL5 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Heading, Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S42

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : Ownship

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

300ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#108

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary at TCAS SL6 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S43

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : Ownship

Altitude

UAS 5000ft - 10000ft

INT 1 5000ft - 10000ft

300ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#109

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary at TCAS SL5 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S43

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : Ownship

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

300ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#110

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary at TCAS SL6 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S43

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 5000ft - 10000ft

INT 1 5000ft - 10000ft

Ownship

Lateral Offset = 0.5 NM

300ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#111

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary at SL5 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S43

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

Ownship

Lateral Offset = 0.5 NM

300ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#112

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary at SL6 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S43

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 5000ft - 10000ft

INT 1 5000ft - 10000ft

Ownship

Lateral Offset = 0.5 NM

300ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#113

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary SL5 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S43

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

Ownship

Lateral Offset = 0.5 NM

300ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#114

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate TCAS RA boundary in relation to well clear boundary SL6 Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear once TCAS RA is displayed • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Achieve TCAS RA Expected Results Ownship alerting • Progress through each alerting condition • Receive RA before the well clear boundary Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM

High Speed Maneuvering

TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S43

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) Contributing Sensors : YES YES YES YES

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

Ownship

Lateral Offset = 0.5 NM

300ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#115

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate DAIDALUS performance with maneuvering high speed intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, alt or VS bands to remain well clear • Speed: 400KGS • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements Expected Results Ownship alerting • Progress through each alerting condition Additional Information Follow Heading, Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S43

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

Ownship

Lateral Offset = 0.5 NM

300ft Scenario(s):

SS Alerting Boundary = 0.75 NM

#116

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate DAIDALUS performance with maneuvering high speed intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec Success Criteria • UAS Maneuvers away from intruder before TCAS - RA • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) • Data type 1 • Data type 2… Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S42

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors : Ownship

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

300ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#117

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate DAIDALUS performance with maneuvering high speed intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec Success Criteria • UAS Maneuvers away from intruder before TCAS - RA • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) • Data type 1 • Data type 2… Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S43

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) Contributing Sensors : YES YES YES YES Ownship

Altitude

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

300ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#118

Minimum Altitude Offset ≥ 300 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Demonstrate DAIDALUS performance with maneuvering high speed intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading/alt/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Climb Rate: • Roll Rate: • Pitch Rate: • Tolerance: ± 10 sec Success Criteria • UAS Maneuvers away from intruder before TCAS - RA • Alerting progress from each alerting level • Data collected at the LVC (Time Synced) • Data type 1 • Data type 2… Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM

Maneuvering/Blocking

TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S38

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) Contributing Sensors : YES NO YES YES

Altitude

0.7 NM Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#123

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S38

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

0.7 NM Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#124

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S38

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

0.7 NM

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#125

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S38

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

0.7 NM

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#126

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S38

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

0.7 NM Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#127

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S38

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) Contributing Sensors : YES YES YES YES

Altitude

0.7 NM Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#128

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S38

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

0.7 NM

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#129

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship TEST OBJECTIVES Demonstrate DAIDALUS will not guide UAS vertically into path of another known intruder. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S38

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

Ownship

UAS 10000ft - 20000ft

INT 1 10000ft - 20000ft

0.7 NM

INT 2 10000ft - 20000ft

300 ft 300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#130

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting and guidance to the UAS operator.

2. SAA fusion processor correctly correlates tracks 3. Fly an encounter which blocks a descent maneuver Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, preventive, corrective alerts • DAIDALUS does not guide the operator into a secondary encounter/loss of well clear Test Method • MANEUVER – Follow HDG/ALT/VS bands to stay well clear • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter causes DAIDALUS to provide preventive/corrective guidance • UAS operator follows DAIDAULUS guidance Expected Results Ownship alerting • Progress from no factor to corrective guidance • Guidance will indicate a vertical solution to remain well clear.

• Guidance will not indicate a turn towards the secondary intruder Additional Information Follow Alt or VS bands to avoid intruder.

The closest point of approach (CPA) is 0.5NM for intruder 1 Intruder 2 should be on parallel path .7nm - 1nm at same velocity as ownship

Well Clear Recovery

TEST OBJECTIVES Demonstrate performance in a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S1

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 10000ft - 20000ft

Ownship

INT 10000ft - 20000ft

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#131

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Fly into the encounter until recovery bands are displayed (typically just outside of well clear volume) or until prescribed dista nc e TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S2

Display : Native Display (as opposed to VSCS, TCAS on HUD) NO YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#132

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S3

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

Relative o

90 UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#133

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S1

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) NO YES YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 10000ft - 20000ft

Ownship

INT 10000ft - 20000ft

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#136

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S2

Display : Native Display (as opposed to VSCS, TCAS on HUD) NO YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#137

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S3

Display : Native Display (as opposed to VSCS, TCAS on HUD) NO YES YES YES Contributing Sensors :

Altitude

Relative o

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#138

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S4

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES NO Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#139

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S4

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES NO Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

o 180 Relative Ownship

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#140

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct well clear recovery guidance 2. SAA fusion processor correctly correlates tracks 3. Evaluate performance of well clear recovery guidance Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • Recovery guidance will show quickest time to recovery of well clear Test Method • MANEUVER – Maneuver once well clear recovery guidance is displayed or at .7nm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • DTHR: .7nm – 1nm Success Criteria • Data collected from MACS display (see data requirements) • Well clear recovery guidance is displayed • Operator follows well clear guidance Expected Results Ownship alerting • Progress through each alerting condition • Well clear recovery guidance provides options for shortest time to recover well clear from intruder Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM

Low Speed Intruders

TEST OBJECTIVES Demonstrate performance in a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S1

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

o

0 Relative UAS 5000ft - 20000ft

Ownship

INT 5000ft - 20000ft

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#141

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS will account for low GS of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, Alt or VS bands • Speed: ~100kgs • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter generates corrective self - separation alerts and guidance • Operator maneuvers in accordance with DAIDALUS guidance Expected Results Ownship alerting • Progress through each alerting condition • Corrective Self - separation guidance provides guidance away from intruder Additional Information Follow heading, Alt, or VS bands to remain well clear TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S2

Display : Native Display (as opposed to VSCS, TCAS on HUD) NO YES YES YES Contributing Sensors :

Altitude

UAS 5000ft - 20000ft

INT 5000ft - 20000ft

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#142

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS will account for low GS of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, Alt or VS bands • Speed: ~100kgs • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter generates corrective self - separation alerts and guidance • Operator maneuvers in accordance with DAIDALUS guidance Expected Results Ownship alerting • Progress through each alerting condition • Corrective Self - separation guidance provides guidance away from intruder Additional Information Follow heading, Alt, or VS bands to remain well clear TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S3

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

Relative o

90 UAS 5000ft - 20000ft

INT 5000ft - 20000ft

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#143

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS will account for low GS of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, Alt or VS bands • Speed: ~100kgs • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter generates corrective self - separation alerts and guidance • Operator maneuvers in accordance with DAIDALUS guidance Expected Results Ownship alerting • Progress through each alerting condition • Corrective Self - separation guidance provides guidance away from intruder Additional Information Follow heading, Alt, or VS bands to remain well clear TEST OBJECTIVES Demonstrate performance in a Head - on scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S1

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

o 0 Relative

UAS 5000ft - 20000ft

Ownship

INT 5000ft - 20000ft

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#144

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS will account for low GS of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, Alt or VS bands • Speed: ~100kgs • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter generates corrective self - separation alerts and guidance • Operator maneuvers in accordance with DAIDALUS guidance Expected Results Ownship alerting • Progress through each alerting condition • Corrective Self - separation guidance provides guidance away from intruder Additional Information Follow heading, Alt, or VS bands to remain well clear TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S2

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 5000ft - 20000ft

INT 5000ft - 20000ft

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#145

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS will account for low GS of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, Alt or VS bands • Speed: ~100kgs • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter generates corrective self - separation alerts and guidance • Operator maneuvers in accordance with DAIDALUS guidance Expected Results Ownship alerting • Progress through each alerting condition • Corrective Self - separation guidance provides guidance away from intruder Additional Information Follow heading, Alt, or VS bands to remain well clear TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S3

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

Relative o

90 UAS 5000ft - 20000ft

INT 5000ft - 20000ft

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#146

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS will account for low GS of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, Alt or VS bands • Speed: ~100kgs • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter generates corrective self - separation alerts and guidance • Operator maneuvers in accordance with DAIDALUS guidance Expected Results Ownship alerting • Progress through each alerting condition • Corrective Self - separation guidance provides guidance away from intruder Additional Information Follow heading, Alt, or VS bands to remain well clear TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S4

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 5000ft - 20000ft

INT 5000ft - 20000ft

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#147

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a head - on scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS will account for low GS of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the head - on intruder ai rcraft. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading, Alt or VS bands • Speed: ~100kgs • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Encounter generates corrective self - separation alerts and guidance • Operator maneuvers in accordance with DAIDALUS guidance Expected Results Ownship alerting • Progress through each alerting condition • Corrective Self - separation guidance provides guidance away from intruder Additional Information Follow heading, Alt, or VS bands to remain well clear

Intruder Acceleration

TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S2

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Increase speed 50 - 80kts gs

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#148

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a front quartering scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS correctly accounts for increase in speed of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS adjusts corrective guidance to account for updated intruder state information Test Method • MANEUVER – Follow heading bands to remain well clear.

• Intruder speed: Increase ground speed 50 - 80 kts ground speed to place CPA inside the well clear volume • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Intruder’s CPA moves from outside the well clear volume to inside the well clear volume • Appropriate corrective guidance is provided • Operator maneuvers to remain well clear Expected Results Ownship alerting • Progress through each alerting condition • Guidance changes from proximate to corrective after intruder acceleration Additional Information Follow heading, alt or vs bands to remain well clear The closest point of approach (CPA) before the increase in speed should be .7nm - 1nm, CPA after speed increase should be .5nm TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S3

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Relative Altitude

o

Increase speed 50 - 80kgs

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#149

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a front quartering scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS correctly accounts for increase in speed of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS adjusts corrective guidance to account for updated intruder state information Test Method • MANEUVER – Follow heading bands to remain well clear.

• Intruder speed: Increase ground speed 50 - 80 kts ground speed to place CPA inside the well clear volume • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Intruder’s CPA moves from outside the well clear volume to inside the well clear volume • Appropriate corrective guidance is provided • Operator maneuvers to remain well clear Expected Results Ownship alerting • Progress through each alerting condition • Guidance changes from proximate to corrective after intruder acceleration Additional Information Follow heading, alt or vs bands to remain well clear The closest point of approach (CPA) before the increase in speed should be .7nm - 1nm, CPA after speed increase should be .5nm TEST OBJECTIVES Demonstrate performance in Front - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S2

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Increase speed 50 - 80kgs

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#150

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a front quartering scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS correctly accounts for increase in speed of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS adjusts corrective guidance to account for updated intruder state information Test Method • MANEUVER – Follow heading bands to remain well clear.

• Intruder speed: Increase ground speed 50 - 80 kts ground speed to place CPA inside the well clear volume • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Intruder’s CPA moves from outside the well clear volume to inside the well clear volume • Appropriate corrective guidance is provided • Operator maneuvers to remain well clear Expected Results Ownship alerting • Progress through each alerting condition • Guidance changes from proximate to corrective after intruder acceleration Additional Information Follow heading, alt or vs bands to remain well clear The closest point of approach (CPA) before the increase in speed should be .7nm - 1nm, CPA after speed increase should be .5nm TEST OBJECTIVES Demonstrate performance in Crossing scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S3

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) Contributing Sensors : YES YES YES YES

Altitude

Relative o

90 Increase speed 50 - 80kgs

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

300 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#151

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a front quartering scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS correctly accounts for increase in speed of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS adjusts corrective guidance to account for updated intruder state information Test Method • MANEUVER – Follow heading bands to remain well clear.

• Intruder speed: Increase ground speed 50 - 80 kts ground speed to place CPA inside the well clear volume • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Intruder’s CPA moves from outside the well clear volume to inside the well clear volume • Appropriate corrective guidance is provided • Operator maneuvers to remain well clear Expected Results Ownship alerting • Progress through each alerting condition • Guidance changes from proximate to corrective after intruder acceleration Additional Information Follow heading, alt or vs bands to remain well clear The closest point of approach (CPA) before the increase in speed should be .7nm - 1nm, CPA after speed increase should be .5nm TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion

S4

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

Ownship

400 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#152

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a front quartering scenario 2. SAA fusion processor correctly correlates tracks 3. DAIDALUS correctly accounts for increase in speed of intruder Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track • DAIDALUS adjusts corrective guidance to account for updated intruder state information Test Method • MANEUVER – Follow heading bands to remain well clear.

• Intruder speed: Increase ground speed 50 - 80 kts ground speed to place CPA inside the well clear volume • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec Success Criteria • Data collected from MACS display (see data requirements) • Intruder’s CPA moves from outside the well clear volume to inside the well clear volume • Appropriate corrective guidance is provided • Operator maneuvers to remain well clear Expected Results Ownship alerting • Progress through each alerting condition • Guidance changes from proximate to corrective after intruder acceleration Additional Information Follow heading, alt or vs bands to remain well clear The closest point of approach (CPA) before the increase in speed should be .7nm - 1nm, CPA after speed increase should be .5nm

High Descent Rate

TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

3000fpm Ownship o 0 Relative

500 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#153

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Evaluate effectiveness of Time to Co - Altitude variable on alerting Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading , VS, or Alt bands • Intruder VS: 3000fpm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • TCOA: 0 Success Criteria • Data collected from MACS display (see data requirements) • Corrective self separation guidance is provided • Intruder reaches 3000fpm • Operator maneuvers to stay well clear Expected Results Ownship alerting • Progress through each alerting condition • Alerting and guidance shown earlier when TCOA is 20 Additional Information Follow heading or vertical bands TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S4

Display : Native Display (as opposed to VSCS, TCAS on HUD) YES YES YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

1000fpm o Ownship 0 Relative

500 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#154

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Evaluate effectiveness of Time to Co - Altitude variable on alerting Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading , VS, or Alt bands • Intruder VS: 1000fpm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • TCOA: 0 Success Criteria • Data collected from MACS display (see data requirements) • Corrective self separation guidance is provided • Intruder reaches 3000fpm • Operator maneuvers to stay well clear Expected Results Ownship alerting • Progress through each alerting condition • Alerting and guidance shown earlier when TCOA is 20 Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S4

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) Contributing Sensors : YES YES YES YES

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

3000fpm o Ownship 0 Relative

500 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#157

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Evaluate effectiveness of Time to Co - Altitude variable on alerting Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading , VS, or Alt bands • Intruder VS: 3000fpm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • TCOA: 0 Success Criteria • Data collected from MACS display (see data requirements) • Corrective self separation guidance is provided • Intruder reaches 3000fpm • Operator maneuvers to stay well clear Expected Results Ownship alerting • Progress through each alerting condition • Alerting and guidance shown earlier when TCOA is 20 Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

TCAS ADS - B Radar Fusion S4

Display : Native Display (as opposed to VSCS, TCAS on HUD) Contributing Sensors : YES YES YES YES

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

1000fpm o Ownship 0 Relative

500 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#158

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Evaluate effectiveness of Time to Co - Altitude variable on alerting Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading , VS, or Alt bands • Intruder VS: 1000fpm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • TCOA: 0 Success Criteria • Data collected from MACS display (see data requirements) • Corrective self separation guidance is provided • Intruder reaches 3000fpm • Operator maneuvers to stay well clear Expected Results Ownship alerting • Progress through each alerting condition • Alerting and guidance shown earlier when TCOA is 20 Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S4

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

3000fpm o Ownship 0 Relative

500 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#163

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Evaluate effectiveness of Time to Co - Altitude variable on alerting Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading , VS, or Alt bands • Intruder VS: 3000fpm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • TCOA: 20 Success Criteria • Data collected from MACS display (see data requirements) • Corrective self separation guidance is provided • Intruder reaches 3000fpm • Operator maneuvers to stay well clear Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM TEST OBJECTIVES Demonstrate performance in Rear - Quartering scenario. Section A.5.1 DAA MOPS / Version: July 28, 2015 Configuration System Under Test : DAIDALUS

S4

TCAS ADS - B Radar Fusion Display : Native Display (as opposed to VSCS, TCAS on HUD) YES NO YES YES Contributing Sensors :

Altitude

UAS 10000ft - 20000ft

INT 10000ft - 20000ft

1000fpm o Ownship 0 Relative

500 ft

Lateral Offset = 0.5 NM

Scenario(s):

SS Alerting Boundary = 0.75 NM

#164

Minimum Altitude Offset ≥ 400 ft

Test Objective (TO) 1. The DAIDALUS algorithm as displayed on the native display will show the correct alerting to the UAS in a rear - quartering scenario 2. SAA fusion processor correctly correlates tracks 3. Evaluate effectiveness of Time to Co - Altitude variable on alerting Evaluation Criteria The alerting displayed to the UAS will provide adequate SA to the UAS Pilot Operator as to the status of the intruder aircraf t. DAIDALUS Display provides the following: • TO - 1 Alerting shall progress from NO FACTOR, Proximate, SS, CA… • TO - 2 TCAS and ADS - B tracks are correctly fused into 1 single track Test Method • MANEUVER – Follow heading , VS, or Alt bands • Intruder VS: 1000fpm • Encounter Length: 3 min • Stable Conditions: 2.5 min before CPA • Tolerance: ± 10 sec • TCOA: 20 Success Criteria • Data collected from MACS display (see data requirements) • Corrective self separation guidance is provided • Intruder reaches 3000fpm • Operator maneuvers to stay well clear Expected Results Ownship alerting • Progress through each alerting condition • Ownship maneuvers away from encounter prior to TCAS - RA and then maneuvers back to course Show images of expected alerting Additional Information Do not follow guidance. Follow predescribed path, hold constant altitude and speed.

The closest point of approach (CPA) is 0.5NM National Aeronautics and Space Administration National Aeronautics and Space Administration

UAS in the NAS

FT4 Test Objectives

CPDS

Version 3, Feb. 1, 2016

TEST OBJECTIVES S/N 165 DAA guidance against non - cooperative intruder being detected during ownship DAA maneuver Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 2: ADS - B and TCAS Selected traffic on Winconverter must be the ADS - B of the non - cooperative intruder Synthetic ownship altitude offset of - 500 ft Scenario(s):

#165

Test Objective (TO) 1. Obtain data that can be used to define the real boundaries (due to processing latencies etc.) of the space where a non - cooperati ve intruder will become detectable during an ownship turn.

Evaluation Criteria • Relative location of intruder at the moment of detection • Progression of DAA alert status • Progression of detection during and after ownship turn Test Method • Ownship and intruder are in a stable relative formation described by range, bearing and altitude (1.5 nmi , 120 deg , - 500 ft ) • Ownship changes heading 30 degrees using rate 1 turn in the direction which will get intruder into radar FOV • Ownship continues on new heading until non - cooperative intruder is either • no longer detected or • DAA alert state has reverted to NORMAL or • UAS pilot deems maneuver required for safety • Encounter Length: TBD • Stable Conditions: stable relative formation described by range, bearing and altitude • Tolerance: 0.1 nmi range and 2 degrees bearing Success Criteria • No detection of the non - cooperative intruder before ownship turn • Detection of non - cooperative occurs during ownship turn • Predicted DA Alert states occur • A735B data recorded Expected Results Ownship alerting • SSWA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 166 DAA guidance against non - cooperative intruder being detected during ownship DAA maneuver Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 2: ADS - B and TCAS Selected traffic on Winconverter must be the ADS - B of the non - cooperative intruder Synthetic ownship altitude offset of - 500 ft Scenario(s):

#166

Test Objective (TO) 1. Obtain data that can be used to define the real boundaries (due to processing latencies etc.) of the space where a non - cooperati ve intruder will become detectable during an ownship turn.

Evaluation Criteria • Relative location of intruder at the moment of detection • Progression of DAA alert status • Progression of detection during and after ownship turn Test Method • Ownship and intruder are in a stable relative formation described by range, bearing and altitude (2.0 nmi , 120 deg , - 500 ft ) • Ownship changes heading 30 degrees using rate 1 turn in the direction which will get intruder into radar FOV • Ownship continues on new heading until non - cooperative intruder is either • no longer detected or • DAA alert state has reverted to NORMAL or • UAS pilot deems maneuver required for safety • Encounter Length: TBD • Stable Conditions: stable relative formation described by range, bearing and altitude • Tolerance: 0.1 nmi range and 2 degrees bearing Success Criteria • No detection of the non - cooperative intruder before ownship turn • Detection of non - cooperative occurs during ownship turn • Predicted DA Alert states occur • A735B data recorded Expected Results Ownship alerting • SSWA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 167 DAA guidance against non - cooperative intruder being detected during ownship DAA maneuver Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 2: ADS - B and TCAS Selected traffic on Winconverter must be the ADS - B of the non - cooperative intruder Synthetic ownship altitude offset of - 500 ft Scenario(s):

#167

Test Objective (TO) 1. Obtain data that can be used to define the real boundaries (due to processing latencies etc.) of the space where a non - cooperati ve intruder will become detectable during an ownship turn.

Evaluation Criteria • Relative location of intruder at the moment of detection • Progression of DAA alert status • Progression of detection during and after ownship turn Test Method • Ownship and intruder are in a stable relative formation described by range, bearing and altitude (2.5 nmi , 120 deg , - 500 ft ) • Ownship changes heading 30 degrees using rate 1 turn in the direction which will get intruder into radar FOV • Ownship continues on new heading until non - cooperative intruder is either • no longer detected or • DAA alert state has reverted to NORMAL or • UAS pilot deems maneuver required for safety • Encounter Length: TBD • Stable Conditions: stable relative formation described by range, bearing and altitude • Tolerance: 0.1 nmi range and 2 degrees bearing Success Criteria • No detection of the non - cooperative intruder before ownship turn • Detection of non - cooperative occurs during ownship turn • Predicted DA Alert states occur • A735B data recorded Expected Results Ownship alerting • SSWA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 168 DAA guidance against non - cooperative intruder being detected during ownship DAA maneuver Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 2: ADS - B and TCAS Selected traffic on Winconverter must be the ADS - B of the non - cooperative intruder Synthetic ownship altitude offset of - 500 ft Scenario(s):

#168

Test Objective (TO) 1. Obtain data that can be used to define the real boundaries (due to processing latencies etc.) of the space where a non - cooperati ve intruder will become detectable during an ownship turn.

Evaluation Criteria • Relative location of intruder at the moment of detection • Progression of DAA alert status • Progression of detection during and after ownship turn Test Method • Ownship and intruder are in a stable relative formation described by range, bearing and altitude (1.5 nmi , 130 deg , - 500 ft ) • Ownship changes heading 30 degrees using rate 1 turn in the direction which will get intruder into radar FOV • Ownship continues on new heading until non - cooperative intruder is either • no longer detected or • DAA alert state has reverted to NORMAL or • UAS pilot deems maneuver required for safety • Encounter Length: TBD • Stable Conditions: stable relative formation described by range, bearing and altitude • Tolerance: 0.1 nmi range and 2 degrees bearing Success Criteria • No detection of the non - cooperative intruder before ownship turn • Detection of non - cooperative occurs during ownship turn • Predicted DA Alert states occur • A735B data recorded Expected Results Ownship alerting • SSWA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 169 DAA guidance against non - cooperative intruder being detected during ownship DAA maneuver Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 2: ADS - B and TCAS Selected traffic on Winconverter must be the ADS - B of the non - cooperative intruder Synthetic ownship altitude offset of - 500 ft Scenario(s):

#169

Test Objective (TO) 1. Obtain data that can be used to define the real boundaries (due to processing latencies etc.) of the space where a non - cooperati ve intruder will become detectable during an ownship turn.

Evaluation Criteria • Relative location of intruder at the moment of detection • Progression of DAA alert status • Progression of detection during and after ownship turn Test Method • Ownship and intruder are in a stable relative formation described by range, bearing and altitude (2.0 nmi , 130 deg , - 500 ft ) • Ownship changes heading 30 degrees using rate 1 turn in the direction which will get intruder into radar FOV • Ownship continues on new heading until non - cooperative intruder is either • no longer detected or • DAA alert state has reverted to NORMAL or • UAS pilot deems maneuver required for safety • Encounter Length: TBD • Stable Conditions: stable relative formation described by range, bearing and altitude • Tolerance: 0.1 nmi range and 2 degrees bearing Success Criteria • No detection of the non - cooperative intruder before ownship turn • Detection of non - cooperative occurs during ownship turn • Predicted DA Alert states occur • A735B data recorded Expected Results Ownship alerting • SSWA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 170 DAA guidance against non - cooperative intruder being detected during ownship DAA maneuver Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 2: ADS - B and TCAS Selected traffic on Winconverter must be the ADS - B of the non - cooperative intruder Synthetic ownship altitude offset of - 500 ft Scenario(s):

#170

Test Objective (TO) 1. Obtain data that can be used to define the real boundaries (due to processing latencies etc.) of the space where a non - cooperati ve intruder will become detectable during an ownship turn.

Evaluation Criteria • Relative location of intruder at the moment of detection • Progression of DAA alert status • Progression of detection during and after ownship turn Test Method • Ownship and intruder are in a stable relative formation described by range, bearing and altitude (2.5 nmi , 130 deg , - 500 ft ) • Ownship changes heading 30 degrees using rate 1 turn in the direction which will get intruder into radar FOV • Ownship continues on new heading until non - cooperative intruder is either • no longer detected or • DAA alert state has reverted to NORMAL or • UAS pilot deems maneuver required for safety • Encounter Length: TBD • Stable Conditions: stable relative formation described by range, bearing and altitude • Tolerance: 0.1 nmi range and 2 degrees bearing Success Criteria • No detection of the non - cooperative intruder before ownship turn • Detection of non - cooperative occurs during ownship turn • Predicted DA Alert states occur • A735B data recorded Expected Results Ownship alerting • SSWA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 171 Get data on Collision Avoidance Interoperability Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 1: ADS - B and TCAS Intruder 2: ADS - B and TCAS Selected traffic must be ADS - B of intruder 2 Scenario(s):

#171

Test Objective (TO) 1. Obtain data on multi - intruder encounter in which ownship DAA maneuver results in a TCAS RA with another target.

Evaluation Criteria • Timeliness, correctness, stability and persistence of the DAA alert states (2.2.4.2) • Timeliness, correctness, stability and persistence of the depicted conflict space (coasting) • Timeliness, correctness, stability and persistence of the depicted heading bands • Occurrence of (unexpected) overlapping alerts (2.2.4.4) Test Method • Encounter Length: 180 seconds • Intruder 1 trajectory triggers CSSA • Ownship turns to avoid loss of well clear and consequently triggers RA • Ownship follows RA • Tolerance: TBD Success Criteria • CSSA occurs with intruder 1 • Ownship maneuver prevents TCAS RA with intruder 1 • No loss of well clear occurs with intruder 1 • TCAS RA occurs with intruder 2 • A735B data recorded Expected Results Ownship alerting • CSSA with intruder 1 • TCAS RA with intruder 2 Additional Information The ownship DAA maneuver does not result in a predictable endstate , i.e. an exact heading change. The geometry must be set up in such a way that the RA with intruder 2 will occur for a larger heading range beyond the minimum heading required to prevent a loss of well clear with intruder 1.

TEST OBJECTIVES S/N 172 Get data on Collision Avoidance Interoperability Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES YES Ownship : TCAS in TARA mode Intruder 1: ADS - B and TCAS Intruder 2: ADS - B and TCAS On Winconverter , intruder 1 must be selected until RA After RA, intruder 2 must be selected Scenario(s):

#172

Test Objective (TO) 1. Obtain data on multi - intruder encounter in which ownship TCAS RA maneuver against intruder triggers DAA CSSA for another target.

Evaluation Criteria • Timeliness, correctness, stability and persistence of the DAA alert states (2.2.4.2) • Timeliness, correctness, stability and persistence of the depicted conflict space • Timeliness, correctness, stability and persistence of the depicted heading bands • Occurrence of (unexpected) overlapping alerts (2.2.4.4) Test Method • Encounter Length: 180 seconds • Intruder 1 horizontal maneuvers to trigger RA • Ownship does not maneuver based on CSSA which may precede RA • Ownship follows RA • After clear of conflict from TCAS ownship uses DAA information to prevent loss of well clear • Tolerance: TBD Success Criteria • No ownship maneuver before RA • RA occurs as predicted • Following RA triggers CSSA • Ownship maneuver resolves CSSA and both targets become PSSA • No SSWA occurs for intruder 2 • A735B data recorded Expected Results Ownship alerting • TCAS descend RA with intruder 1 • CSSA with intruder 2 • No loss of well clear is expected to occur with intruder 2 • Ownship altitude change to around 9600 ft will make both intruders PSSA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 173 Get data on Collision Avoidance Interoperability Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 1: ADS - B and TCAS Intruder 2: ADS - B and TCAS On Winconverter , intruder 1 must be selected until RA After RA, intruder 2 must be selected Scenario(s):

#173

Test Objective (TO) 1. Obtain data on multi - intruder encounter in which ownship TCAS RA maneuver against intruder triggers DAA CSSA for another target.

Evaluation Criteria • Timeliness, correctness, stability and persistence of the DAA alert states (2.2.4.2) • Timeliness, correctness, stability and persistence of the depicted conflict space • Timeliness, correctness, stability and persistence of the depicted heading bands • Occurrence of (unexpected) overlapping alerts (2.2.4.4) Test Method • Encounter Length: 180 seconds • Intruder 1 vertical maneuver to trigger RA • Ownship does not maneuver based on CSSA which may precede RA • Ownship follows RA • After clear of conflict from TCAS ownship uses DAA information to prevent loss of well clear • Tolerance: TBD Success Criteria • No ownship maneuver before RA • RA occurs as predicted • Following RA triggers CSSA • Ownship maneuver resolves CSSA and both targets become PSSA • No SSWA occurs for intruder 2 • A735B data recorded Expected Results Ownship alerting • TCAS descend RA with intruder 1 • CSSA with intruder 2 • No loss of well clear is expected to occur with intruder 2 • Ownship altitude change to around 9600 ft will make both intruders PSSA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 174 Get data on Collision Avoidance Interoperability Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES NO Ownship : TCAS in TARA mode Intruder 1: ADS - B and TCAS Intruder 2: ADS - B and TCAS On Winconverter , intruder 2 must be selected Scenario(s):

#174

Test Objective (TO) 1. Obtain data on multi - intruder encounter in which ownship TCAS RA maneuver against intruder t riggers DAA SSWA for another target.

Evaluation Criteria • Timeliness, correctness, stability and persistence of the DAA alert states (2.2.4.2) • Timeliness, correctness, stability and persistence of the depicted conflict space • Timeliness, correctness, stability and persistence of the depicted heading bands • Occurrence of (unexpected) overlapping alerts (2.2.4.4) Test Method • Encounter Length: 180 seconds • Intruder 1 horizontal maneuvers to trigger RA • Ownship does not maneuver based on CSSA which may precede RA • Ownship follows RA • After clear of conflict from TCAS ownship uses DAA information to prevent loss of well clear or restore well clear • Tolerance: TBD Success Criteria • No ownship maneuver before RA • RA occurs as predicted • Following RA triggers SSWA • Ownship maneuver resolves SSWA • A735B data recorded Expected Results Ownship alerting • TCAS descend RA with intruder 1 • SSWA with intruder 2 • Loss of well clear likely to occur • Ownship returning to its altitude resolves SSWA Additional Information Anything not covered above.

TEST OBJECTIVES S/N 175 Get data on Collision Avoidance Interoperability Section 2.2.4. DAA MOPS / Version: July 28, 2015 Configuration System Under Test : CPDS Display : CPDS CDTI and VPD Contributing Sensors : TCAS ADS - B Radar Fusion YES YES YES YES Ownship : TCAS in TARA mode Intruder 1: ADS - B and TCAS Intruder 2: ADS - B and TCAS On Winconverter , intruder 2 must be selected Scenario(s):

#175

Test Objective (TO) 1. Obtain data on multi - intruder encounter in which ownship TCAS RA maneuver against intruder triggers DAA SSWA for another target.

Evaluation Criteria • Timeliness, correctness, stability and persistence of the DAA alert states (2.2.4.2) • Timeliness, correctness, stability and persistence of the depicted conflict space • Timeliness, correctness, stability and persistence of the depicted heading bands • Occurrence of (unexpected) overlapping alerts (2.2.4.4) Test Method • Encounter Length: 180 seconds • Intruder 1 vertical maneuver to trigger RA • Ownship does not maneuver based on CSSA which may precede RA • Ownship follows RA • After clear of conflict from TCAS ownship uses DAA information to prevent loss of well clear or restore well clear • Tolerance: TBD Success Criteria • No ownship maneuver before RA • RA occurs as predicted • Following RA triggers SSWA • Ownship maneuver resolves SSWA • A735B data recorded Expected Results Ownship alerting • TCAS descend RA with intruder 1 • SSWA with intruder 2 • Loss of well clear likely to occur • Ownship returning to its altitude resolves SSWA Additional Information Anything not covered above.

National Aeronautics and Space Administration National Aeronautics and Space Administration

UAS in the NAS

FT4 Test Objectives

(Radar)

TEST OBJECTIVES GA Radar Statistical Run #1 Section DAA MOPS / Version: R4, R7, R9, R11, R13 - 16, R22 - 25,R28, R29, R30, R33, R34, R35 Configuration System Under Test : Radar Display : CPDS TCAS ADS - B Radar Fusion Contributing Sensors : No YES YES No

1000 ft NM

3 NM

22 °

5 00 ft

22 °

Ownship

3 NM

Scenario(s):

Lateral Offset = N/A

Intruder 1 Equipage: DGPS

#176

SS Alerting Boundary = N/A

Intruder 2 Equipage: DGPS

Minimum Altitude Offset = 500ft

Test Objective (TO) Track Radar Range and Accuracy against two intruders Evaluation Criteria Range and angular accuracy are within the limits defined in SC228. No track losses, track splits or false targets during the test.

Test Method • MANEUVER: Ownship and Intruders fly without maneuver • Rel. Bearing: Intruder 1 = 0<IBA<30 , Intruder 2 = 0<IBA< - 30 • Progressive Closure: Ownship = 160 KGS, Intruder 1 = 160 KGS, Intruder 2 = 160 KGS • Altitude: >10k MSL • Encounter Length: TBD min • Stable Conditions: TBD min before CPA • Climb Rate: 0 ft /min • Tolerance: TBD Success Criteria • Intruders are acquired at least at 8nm and from own ship and tracked until 1nm. Intruder aircrafts should maintain heading within + 5 degrees of the required heading.

Expected Results Intruders are acquired at greater than 12 nm and tracked until 0.5nm, results should be comparable to ADS - B Additional Information Requirement : 16 scenarios 0<IBA<30 TEST OBJECTIVES GA Radar Statistical Run #2 Section DAA MOPS / Version: R4, R7, R9, R11, R13 - 16, R22 - 25,R28, R29, R30, R33, R34, R35 Configuration System Under Test : Radar Display : CPDS TCAS ADS - B Radar Fusion Contributing Sensors : No YES YES No

1000 ft

NM

2NM

14 °

1000 ft

14 °

Ownship

2NM

Scenario(s):

Lateral Offset = N/A

Intruder 1 Equipage: DGPS

#177

SS Alerting Boundary = N/A

Intruder 2 Equipage: DGPS

Minimum Altitude Offset = 1000 ft

Test Objective (TO) 1. Track Radar Range and Accuracy against two intruders Evaluation Criteria Range and angular accuracy are within the limits defined in SC228. No track losses, track splits or false targets during the test.

Test Method • MANEUVER : Ownship and Intruders fly without maneuver • Rel. Bearing: Intruder 1 = 0<IBA<30 , Intruder 2 = 0<IBA< - 30 • Progressive Closure: Ownship = 160 KGS, Intruder 1 = 160 KGS, Intruder 2 = 160 KGS • Altitude: >10k MSL • Encounter Length: TBD min • Stable Conditions: TBD min before CPA • Climb Rate: 0 ft /min • Tolerance: TBD Success Criteria • Intruders are acquired at least at 8nm and from own ship and tracked until 1nm. Intruder aircrafts should maintain heading within + 5 degrees of the required heading.

Expected Results Intruders are acquired at greater than 12 nm and tracked until 0.5nm, results should be comparable to ADS - B Additional Information Requirement : 16 scenarios 0<IBA<30 TEST OBJECTIVES GA Radar Statistical Run #3 Section DAA MOPS / Version: R4, R7, R9, R11, R13 - 16,

`

R22 - 25,R28, R29, R30, R33, R34, R35 Configuration System Under Test : Radar Display : CPDS TCAS ADS - B Radar Fusion Contributing Sensors : No YES YES No

500 ft

NM

1NM

7 ° 1000 ft

7 °

Ownship

1NM

Scenario(s):

Lateral Offset = N/A

Intruder 1 Equipage: DGPS

#178

SS Alerting Boundary = N/A

Intruder 2 Equipage: DGPS

Minimum Altitude Offset = 500 ft

Test Objective (TO) 1. Track Radar Range and Accuracy against two intruders Evaluation Criteria Range and angular accuracy are within the limits defined in SC228. No track losses, track splits or false targets during the test.

Test Method • MANEUVER : Ownship and Intruders fly without maneuver • Rel. Bearing: Intruder 1 = 0<IBA<30 , Intruder 2 = 0<IBA< - 30 • Progressive Closure: Ownship = 160 KGS, Intruder 1 = 160 KGS, Intruder 2 = 160 KGS • Altitude: >10k MSL • Encounter Length: TBD min • Stable Conditions: TBD min before CPA • Climb Rate: 0 ft /min • Tolerance: TBD Success Criteria • Intruders are acquired at least at 8nm and from own ship and tracked until 1nm. Intruder aircrafts should maintain heading within + 5 degrees of the required heading.

Expected Results Intruders are acquired at greater than 12 nm and tracked until 0.5nm, results should be comparable to ADS - B Additional Information Requirement : 16 scenarios 0<IBA<30 TEST OBJECTIVES GA Radar Statistical Run #4 Section DAA MOPS / Version: R4, R7, R9, R11, R13 - 16, R22 - 25,R28, R29, R30, R33, R34, R35 Configuration System Under Test : Radar

500 ft

Display : CPDS TCAS ADS - B Radar Fusion Contributing Sensors :

1000 ft

No YES YES No Scenario(s):

Lateral Offset = N/A

Intruder 1 Equipage: DGPS

#179

SS Alerting Boundary = N/A

Intruder 2 Equipage: DGPS

Minimum Altitude Offset = 500 ft

Test Objective (TO) 1. Track Radar Range and Accuracy against two intruders Evaluation Criteria Range and angular accuracy are within the limits defined in SC228. No track losses, track splits or false targets during the test.

Test Method • MANEUVER: Ownship and Intruders fly without maneuver • Rel. Bearing: Intruder 1 = 0<IBA<30 , Intruder 2 = 0<IBA<30 • Progressive Closure: Ownship = 160 KGS, Intruder 1 = 160 KGS, Intruder 2 = 160 KGS • Altitude: >10k MSL • Encounter Length: TBD min • Stable Conditions: TBD min before CPA • Climb Rate: 0 ft /min • Tolerance: TBD Success Criteria • Intruders are acquired at least at 8nm and from own ship and tracked until 1nm. Intruder aircrafts should maintain heading within + 5 degrees of the required heading.

Expected Results Intruders are acquired at greater than 12 nm and tracked until 0.5nm, results should be comparable to ADS - B Additional Information Requirement : 16 scenarios 0<IBA<30 TEST OBJECTIVES GA Radar Statistical Run #5 Section DAA MOPS / Version: R4, R7, R9, R11, R13 - 16, R22 - 25,R28, R29, R30, R33, R34, R35 Configuration System Under Test : Radar Display : CPDS TCAS ADS - B Radar Fusion Contributing Sensors : No YES YES No

NM

4 NM

30 °

30 °

Ownship

4 NM

Scenario(s):

Lateral Offset = N/A

Intruder 1 Equipage: DGPS

#180

SS Alerting Boundary = N/A

Intruder 2 Equipage: DGPS

Minimum Altitude Offset = 1000 ft

Test Objective (TO) 1. Track Radar Range and Accuracy against two intruders Evaluation Criteria Range and angular accuracy are within the limits defined in SC228. No track losses, track splits or false targets during the test.

Test Method • MANEUVER: Ownship and Intruders fly without maneuver • Rel. Bearing: Intruder 1 = 0<IBA<30 , Intruder 2 = 0<IBA< - 30 • Progressive Closure: Ownship = 160 KGS, Intruder 1 = 160 KGS, Intruder 2 = 160 KGS • Altitude: >10k MSL • Encounter Length: TBD min • Stable Conditions: TBD min before CPA • Climb Rate: 0 ft /min • Tolerance: TBD Success Criteria • Intruders are acquired at least at 8nm and from own ship and tracked until 1nm. Intruder aircrafts should maintain heading within + 5 degrees of the required heading.

Expected Results Intruders are acquired at greater than 12 nm and tracked until 0.5nm, results should be comparable to ADS - B Additional Information R4, R7, R9, R11, R13 - 16, R22 - 25,R28, R29, R30, R33, R34, R35 TEST OBJECTIVES GA Radar Statistical Run #6 Section DAA MOPS / Version: R4, R7, R9, R11, R13 - 16, R22 - 25,R28, R29, R30, R33, R34, R35 Configuration System Under Test : Radar Display : CPDS TCAS ADS - B Radar Fusion Contributing Sensors : No YES YES No

NM

2NM

14 °

14 °

Ownship

2NM

Scenario(s):

Lateral Offset = N/A

Intruder 1 Equipage: DGPS

#181

SS Alerting Boundary = N/A

Intruder 2 Equipage: DGPS

Minimum Altitude Offset ≥ 1000 ft.

Test Objective (TO) 1. Track Radar Range and Accuracy against two intruders Evaluation Criteria Range and angular accuracy are within the limits defined in SC228. No track losses, track splits or false targets during the test.

Test Method • MANEUVER: Ownship climb , Intruders fly without maneuver • Rel. Bearing: Intruder 1 = 0<IBA<30 , Intruder 2 = 0<IBA< - 30 • Progressive Closure: Ownship = 160 KGS, Intruder 1 = 160 KGS, Intruder 2 = 160 KGS • Altitude: ≥ 10k MSL • Encounter Length: TBD min • Stable Conditions: TBD min before CPA • Climb Rate: TBD ft /min • Tolerance: TBD Success Criteria • Intruders are acquired at least at 8nm and from own ship and tracked until 1nm or within Radar’s FOV. Intruder aircrafts should maintain heading within + 5 degrees of the required heading.

Expected Results Intruders are acquired at greater than 12 nm and tracked until 0.5nm, results should be comparable to ADS - B Target below the own ship will leave Radar’s FOV earlier than target above ownship Additional Information Requirement : 16 scenarios 0<IBA<30 TEST OBJECTIVES GA Radar Statistical Run #7 Section DAA MOPS / Version: R4, R7, R9, R11, R13 - 16, R22 - 25,R28, R29, R30, R33, R34, R35 Configuration System Under Test : Radar Display : CPDS TCAS ADS - B Radar Fusion Contributing Sensors : No YES YES No

1000 ft

2000 ft NM

1NM

7 °

7 °

1000 ft

Ownship