Operational excellence will be graded by the judges as a subjective measure of team performance. This will evaluate things like operation professionalism, communication between members, reaction to system failures, attention to safety, and more.

3.7.1 Operational Excellence Scoring

A sliding score from 0 to 50 points will be given to each team for Operational Excellence based on the above metrics.

The UAS's dependency on human intervention is measured by the number of operators from the competition team that are needed to run the mission demonstration. Up to six operators will be allowed. The team must have at least two operators, a Safety Pilot and a GCS Operator who are dedicated to manual flight override and autopilot operation respectively. The Safety Pilot and GCS Operator cannot perform any other tasks while their UAS is in flight. If the Safety Pilot or GCS Operator performs other tasks during UAS flight, the team's mission will be terminated.

Team members who don’t have an operator role can only assist with setup, teardown, and during a timeout. During the mission they must stand to the side, not communicate or assist the operators, and observe only. Teams must decide ahead of the mission who is an operator and who is an observer, these assignments cannot be changed once the mission starts, and must communicate the assignments to the judges ahead of the mission.

3.3.2 Operators Scoring

The Operators task will be scored via the following equation - where O signifies the number of operators used. As shown, a maximum of 200 points will be given for this task.

3.0.1 Flight Performance Requirements

The following are minimum requirements for UAS flight performance to participate in the Mission Demonstration:

• Fly at least 3 miles at fully loaded weight in a single flight.

• Fly waypoints with a max error of 50ft, and the threshold must be configured in the autopilot.

• Turn radius of 150ft and be able to stay within the Mission Flight Boundary.

• Angle of climb and angle of descent of 20 degrees.

• Stay above 50ft AGL when more than 200ft away from the runway.

• Able to takeoff and land in runway approximately 70ft by 500ft.

3.0.2 Runways for VTOL and HTOL

To support multiple teams flying at the same time, there will be two independent runways performing missions simultaneously. Each runway is capable of supporting both vertical takeoff and landing (VTOL) and horizontal takeoff and landing (HTOL) aircraft. The runways are paved asphalt and will be approximately 70ft by 500ft. Teams may also use the grass sections adjacent to their assigned runways for takeoff and landing, on the opposite side from the tents, so long as flight paths don’t intersect the other runways or the flight line tents.

3.0.3 Airfield Notes

Airfield GPS coordinates are 38.31633, -76.55578. Airfield elevation is 142ft MSL. Airfield magnetic variation is 11 degrees west. The runway is a paved asphalt surface roughly 70ft wide with no height obstacles. Grass areas within the takeoff/landing area will not be prepared but will be available for use

The airfield and flight boundary includes areas which contain trees that may be taller than 50ft AGL. The Maryland record for tree height is ~140ft (182ft MSL at the airfield). Teams should consider this when setting waypoints over trees.

The following are a series of GPS points which form a polygon that is the mission flight boundary (shown via red line in photo). The UAS must remain within this polygon and the altitude restrictions of [50ft AGL (192ft MSL), 400ft AGL (542ft MSL)]. The UAS may only go below 50ft AGL when taking off or landing, but must not go below 50ft AGL when over one of the other runways occupied by other teams. The UAS is out of bounds if it’s outside of the polygon or the altitude restrictions, at which point the mission will be terminated.

• 38.317297, -76.556176

• 38.315948, -76.556573

• 38.315467, -76.553762

• 38.314709, -76.549363

• 38.314241, -76.546627

• 38.313698, -76.543423

• 38.313310, -76.541096

• 38.315299, -76.540521

• 38.315876, -76.543613

• 38.318616, -76.545385

• 38.318626, -76.552061

• 38.317034, -76.552447

• 38.316742, -76.552945

3.0.4 Ground Control Station Requirements

Teams must have a display, always viewable by the judges, which presents a map showing the flight boundaries, the UAS position, and all other competition elements. This display must indicate the UAS speed in KIAS or ground speed in knots, and MSL altitude in feet. Teams will not be able to fly without this display. If during the mission the judges are unable to see this display, the team's UAS will be required to return to land.

3.0.5 Flight Order of Team Demonstrations

The flight order will be determined by order of successfully qualified Proof of Flight Readiness Video submission. A live flight order will be available on the SUAS website as videos are approved.

The organizers will attempt to fly as many teams as possible, but if time runs out (e.g. due to weather delays, emergency airport traffic) the teams who were last to successfully qualify with their proof of flight will not have the opportunity to fly. As time allows, teams will be given the opportunity to fly again for a second chance in the same flight order. The better of the two demonstrations will count.

3.0.6 Judges

The lead judge stands with the Safety Pilot. The Ground Control Station (GCS) judge sits with the GCS Operator and must have continuous uninterrupted access to a GCS display meeting the GCS Display Requirements.

3.0.7 Order of Tasking

Teams must successfully takeoff and climb above 50ft AGL (192ft MSL) within the first 10 minutes of the mission clock, or the demonstration will be terminated. Upon every takeoff, teams must immediately fly a waypoint lap before attempting other tasks, thereby simulating the trip to the operation area. After the waypoint lap, teams may decide the order of all other tasks.

3.0.8 Termination and Disqualification

Breaking the rules, risking safety, and accumulating too many penalties may cause mission termination and may cause disqualification.

UAS that can fly autonomously are cheaper to operate, which means organizations can leverage more UAS at the same cost, which means better performance and more missions. Autonomy also keeps the UAS airborne during connectivity loss, a very likely occurrence in real world environments.

3.2.1 Takeoff and Landing

Takeoff and landing may be performed autonomously or manually - with additional points given for UAS capable of fully autonomous takeoffs and landings.

A takeoff is considered successful once the UAS is above 50ft AGL and has travelled outside of the immediate airspace surrounding the runway. A landing is considered successful if the UAS touches down without any damage to the UAS and surrounding environment.

In order for a takeoff and landing to be considered fully autonomous, only a singular command can be issued by the Safety Pilot or GCS Operator to commence the respective action. Any intervention past a singular button press or command will be up the the judge's discretion and may result in the takeoff/landing attempt being viewed as not autonomous.

3.2.2 Waypoints

Teams will be given a sequence of waypoints (UTM coordinates and altitudes) that must be flown autonomously and the UAS must get within 50ft of each waypoint. This sequence of waypoints represents a singular lap, may be up to 3 miles in length, and include up to 15 positions. Upon every takeoff, teams must immediately fly a singular lap of the waypoint path before attempting other tasks to simulate navigating to the operating area. A full lap must be re-flown between each air drop attempt, simulating trips between operating areas. Teams may opt to land at any point to reload payloads (no refueling allowed), so long that the UAS navigates through an entire waypoint lap after each subsequent takeoff. Four full waypoint laps will be required to conduct all five deliveries, thus the total waypoint distance flown by the UAS may be up to 12 miles.

An example of a mission flow that conducts four air drops with an intermediary landing for reload would be as follows:

• Takeoff

• Fly Waypoint Lap (Up to 3 Miles)

• Conduct Air Drop

• Fly Waypoint Lap (Up to 3 Miles)

• Conduct Air Drop

• Land to Re-Load Payloads

• Takeoff

• Fly Waypoint Lap (Up to 3 Miles)

• Conduct Air Drop

• Fly Waypoint Lap (Up to 3 Miles)

• Conduct Air Drop

• Land

• Remove UAS from Runway Relinquish Airspace

3.2.3 Autonomous Flight Scoring

A maximum of 50 points will be given out for Autonomous Flight. 20 points will given to UAS that takeoff and land at least once (manual or autonomous) - with an additional of 30 points given if all takeoff/landings throughout the Mission Demonstration are done fully autonomously

UAS must be able to fly missions in a restricted time scenario. This involves setting up the UAS, flying the mission, and tearing down within provided time limits.

3.1.1 Setup Time (15 Minutes)

Teams will be provided at least 15 minutes for setup. At setup time teams will receive all other mission details (such as waypoints) from the judges by paper printout. GPS positions will be given in UTM decimal degrees, and altitudes in feet AGL and MSL. The last 5 minutes of the setup time must include the pre-mission brief. This brief must include a summary of planned tasks, identification of Safety Pilot and GCS Operator, and other information judges should know. Once the judges determine the airspace is available and the setup time has elapsed, the judges will start the regardless of team readiness.

3.1.2 Mission Time (30 Minutes)

Teams will be provided 30 minutes to complete the mission. Mission time stops once the UAS has landed, the UAS has cleared the runway, and the team relinquishes the airspace. No additional points will given for ending the mission early, but exceeding the 30 minute mission time will result in large penalties.

3.1.3 Tear Down Time (10 Minutes)

Teams will be provided 10 minutes to remove all equipment from the flight line tent area.

3.1.4 Timeout (10 Minutes)

A team is allowed one timeout to stop the mission clock, which will cost them the points described in . The timeout must be taken prior to the UAS capturing its first waypoint and will last at least ten minutes.

3.1.5 Air Traffic or Weather Mission Pause

In the event that traffic enters the mission airspace or weather becomes unsafe for flight, the mission will be paused at the point the team is notified and the UAS will be required to return to land until the traffic clears the airspace. Teams will be given a penalty-free timeout of at least 5 minutes during which they are permitted to refuel but not otherwise modify the UAS, load additional payloads, or process data. Once the airspace is clear the UAS will takeoff, return to the position at which the mission was interrupted, and then the mission will resume from that point.

UAS should be able to create imagery maps of an area of interest (example shown below). Teams will have to generate an image which covers a larger area and at a higher resolution than typically possible with a single photograph. The area of interest is defined in and is approximately 10 acres in size. Teams must submit the map via USB within their . Maps received outside of the will receive no points.

3.5.1 Mapping Boundary

The following series of GPS points form a quadrilateral polygon that represent the Mapping Boundary specified for each runway. Please refer to for a view of the Mapping Boundaries on Google Maps.

Runway 1:

• 38.314816, -76.548947

• 38.315460, -76.552653

• 38.316639, -76.55233

• 38.316016, -76.54860

Runway 2:

• 38.314669, -76.547987

• 38.315873, -76.547611

• 38.315208, -76.54384

• 38.314008, -76.544237

3.5.2 Mapping Scoring

A sliding score of 0 to 100 points will be given based on the submitted map's quality. Maps will be evaluated for coverage, projection accuracy, stitching, and other quality signals. A high quality map will be indiscernible from a professional-quality map seen on services like Google Maps. A medium quality map will have noticeable defects like minor stitch errors, varying exposures, minor missing coverage, and other minor issues, but won’t detract from use as a map. A map of insufficient quality will receive no points for the mapping task.

Designing a UAS to be lightweight and compact for transport is critical for ease of deployment, especially in remote or difficult-to-access areas. A smaller, lighter UAS reduces logistical challenges, enabling quicker mobilization, reduced transportation costs, and enhanced operational flexibility for various missions.

3.4.1 UAS All Up Weight

The maximum allowed all up weight of the team's UAS with all onboard Air Drop Objects is 45 LBs. This is inclusive all batteries, payloads, and systems that will be onboard the UAS in its maximum takeoff weight state during its mission demonstration. Max points will be given to UAS with an all up weight of 15 LBs or less.

3.4.2 UAS Volume

UAS should be designed so that can be disassembled/collapsed down to a state more compact than their in-flight state. Three sizing tiers will be used to score the UAS's ability to be transported in various common luggage sizes.

• Personal Item (18 x 14 x 8 in)

• Carry-On (22 x 14 x 9 in)

• Check In (27 x 21 x 14 in)

Teams will be given up to five minutes to demonstrate their ability to unpack their UAS from a fully collapsed state to an in-flight state with motors and surface controls operating. Up to four personnel can be used for the unpacking process. If a team is unable to complete this process within the allotted time period or personnel restriction, they will not achieve any points related to this task.

3.4.3 Easy to Transport Batteries

UAS that are outfitted with batteries that are all <100 Wh in power capacity will receive additional points. There is no limit to the number of batteries that a UAS can be outfitted with. Each individually packaged battery onboard the UAS must be below the 100 Wh limit for this task.

3.4.4 Design for Transport Scoring

The Design for Transport task will be scored during the Safety Inspection via the following rubric. As shown, a maximum of 200 points will be given for this task.

UAS should be able to air drop a payload to an object of interest. As with all other mission elements, the UAS must remain above the 50’ AGL minimum altitude fence while conducting air drop.

Teams will be given four air drop objects at Setup Time. Each air drop object will be a GP908 Strobing Beacon w/ 3 AAA batteries installed. The objects weigh approximately 155g and will be labeled with an identifier for the team. An STL and pictures of the air drop object can be found for download here.

UAS may carry multiple air drop object at the same time, or they can land to pick up payloads. The UAS must refly a full waypoint lap before performing another air drop, regardless of whether the UAS lands or not.

Judges may be in the Air Drop Boundary to score the drops, and the ground may be marked to identify the 25ft drop target radius. The objects marking drop targets may be temporarily occluded while judges evaluate drops from another team and clear any debris.

3.6.1 Air Drop Boundary

The following series of GPS points form a quadrilateral polygon that represent the Air Drop Boundary specified for each runway. Each runway's Air Drop Boundary will include the ODLC objects (same for both runways).. Please refer to A. Flight Area Overview for a view of the Air Drop Boundaries on Google Maps.

Runway 1:

• 38.315386, -76.550875

• 38.315683, -76.552586

• 38.315895, -76.552519

• 38.315607, -76.550800

Runway 2:

• 38.314529, -76.545859

• 38.314731, -76.545792

• 38.314441, -76.544081

• 38.314228, -76.544156

3.6.2 Delivery Requirements

An attempted delivery is classified by any payload that is released by the UAS in flight, with no dependency on the success of the attempted delivery.

Each independent air drop payload must be no heavier than 2lbs and must not contain any ability to sustain flight (propulsion, propellers, etc.). The air drop payload must land undamaged and must be safe for humans to be present in the drop area. The payload must be safe to retrieve and safe to handle. Payloads that are delivered in freefall, with no form of retardant mechanism, will not be deemed successful. If the UAS were to drop multiple payloads at once, only the first dropped payload will be scored appropriately.

Judges must be able to safely and easily retrieve and separate the air drop object from the air drop payload to verify that it’s undamaged. Separation must not require tools or any instructions. If the judge is unable to separate the air drop object, then the drop will not count.

3.6.3 Object Detection, Classification, and Localization (ODCL)

Four objects will be scattered around the air drop boundary. Teams must detect, classify, and localize objects that represent foreign object debris (FOD) on the runway. Four objects will be chosen at random from the following list and teams will not be told which objects are present in the Air Drop Boundary.

• Person/Mannequin

• Car (>1:8 Scale Model)

• Motorcycle (>1:8 Scale Model)

• Airplane (>3m Wing Span Scale Model)

• Bus (>1:8 Scale Model)

• Boat (>1:8 Scale Model)

• Stop Sign (Flat, Upwards Facing)

• Snowboard

• Umbrella

• Sports Ball (Regulation Size Soccer Ball, Basketball, Volleyball, or Football)

• Baseball Bat

• Bed/Mattress (> Twin Size)

• Tennis Racket

• Suitcase

• Skis

3.6.4 Object Detection & Air Drop Scoring

Each of the four air drops will given points as follows - with a maximum points of 100 drops per air drop:

• Air Drop Payload Survives (Within Vicinity of Air Drop Boundary) = 20 Points

• Air Drop Payload Lands within 25' of Object = 50 Points

• Air Drop Payload Delivered to Unique Object = 30 Points

Any air drop payloads that are delivered without the UAS conducting a waypoint lap will not be counted and thus given 0 points.

The team will be penalized as follows throughout the mission demonstration. Penalties are defined as a percentage of achievable component points. Unlike points, penalties do not have a bound. This means going over the allowed time can cost the team full points for mission demonstration. If penalties are greater than points, the team will receive a zero for demonstration. Teams cannot score points while generating a penalty.

3.8.1 Excess Time (0.5% Per Second)

The team will receive a penalty equal to 0.5% of mission demonstration points for every second of mission time over limits.

3.8.2 Timeout (5% of Mission)

The team will receive a penalty equal to 5% of mission demonstration points for utilizing their timeout.

3.8.3 Things Fall Off Aircraft (10% Per Item)

If parts fall off the UAS during flight, teams receive a penalty equal to 10% of demonstration points.

3.8.4 Crash/Collison (50% Per Crash/Collision)

If the UAS crashes during flight or collides with another team's UAS, the team will receive a penalty equal to 50% of demonstration points. If a team is in their runway’s dedicated airspace, then they will not receive a penalty for the collision, and only the offending team will receive a penalty.

3.8.5 Unsafe Operations (50% Per Infraction)

If the UAS or team conducts unsafe flight operations and the team does not respond correctly the commands by the judges (manual takeover, kill switch, etc.), the team will received a penalty equal to 50% of demonstration points.

3.8.6 Out of Bounds (Mission Termination)

Teams are given a flight boundary in the Mission Flight Boundary. If the UAS goes out of these bounds then the mission will be terminated and the UAS will be required to immediately return to land. Teams will be evaluated by human observers and by judges at the GCS.

3.8.7 Manual Takeover (Restart Lap)

With exception to takeoff or landing, the aircraft must fly the rest of the mission autonomously. Any transition to manual flight will require the UAS to return to the start of the waypoint lap (at a minimum). If the UAS lands and takes off again, the UAS must fly the waypoint path again before attempting other tasks.