Team Lead
Tyler Schubert
Payload-Build Lead
Brett Graham
Aircraft-Build Lead
Hunter Oppedal
Software Lead
Chris Tarantino
Business Lead
David Zink
Electrical Lead
Height- 23.5 inches
Width- 58 inches
Weight- 7 pounds
Flight Distance- 3.2 Miles
Our aircraft is comprised of a Tarot X6 frame with 6 motors on board, and a payload weight of 2.7 kg. It uses an orange cube as its flight controller, integrated with mission planner software, giving us the ability to autonomously conduct missions.
Equipped with one 10,000 Mah 6s battery powering a Pixhawk Cube Orange flight controller giving our team to ability to autonomously operate the aircraft. Utilizing a RealSense dual-edge camera that functions as both a mapping and target identification system. This vehicle is built to dominate the competition.


esting of the payload system was carried out extensively to ensure its reliability and durability under conditions similar to those expected during competition. Initial tests were conducted from the third floor of Embry-Riddle Aeronautical University’s Lehman Building, which stands approximately 25 feet above the ground. This location was chosen as it provided a consistent testing environment to evaluate the integrity of the payload system following design modifications. After each iteration or redesign, the payload was dropped from this height to observe its performance during descent and impact. A key success criterion for these tests was the secure attachment of the beacon, which was held in place by a magnet connected to a metal plate on the descent system. If the beacon remained attached throughout the drop and upon landing, the test was deemed successful. This was because detachment could mean that it was not safe for humans to be in the area. Once the Tarot platform itself became fully operational, further testing was performed to simulate drops from actual competition altitudes, ensuring that the payload system could withstand higher drop heights and dynamic flight conditions. These tests provided critical data to refine the final design and validate the system’s robustness in real-world scenarios. Some examples of the systems tested are shown above.

With the release of the rules for this year's competition, the team prioritized the point system of this year's competition and chose to focus on Object Detection & Air Drop, Autonomous Flight, and Operators. The team attempted to integrate the other mission demonstrations throughout the design and planning phase, but did not prioritize it.
The previous ERAU SUAS team dissolved due to internal management issues, leaving nothing behind for a reconstruction of the team. Over the past year, Mission: Maverick has rebuilt itself from the ground up. It has regained small amounts of funding and slowly grown its team.
Mission Maverick opted to develop a larger VTOL platform to increase payload capacity and improve maneuverability. The team initially planned to use a fixed-wing UA due to its extended range and payload efficiency; however, after analyzing data from last year’s competition, a strategic pivot was made toward a multirotor design. This shift allows for simpler deconfliction strategies using altitude hold (AltHold) and leverages hover capabilities to enable more accurate object identification and payload deployment.
To maximize resource efficiency, the team chose to refurbish an existing Tarot X6 airframe [1] rather than purchase or fabricate a new one. This decision freed up time and budget to focus on critical system features such as target identification and mapping.
The platform is powered by six ARRIS 5008 350KV motors [2], which provide sufficient thrust to carry both the airframe and payload during sustained flight. Each 10,000 mAh battery is estimated to deliver approximately 14 minutes of flight time under conservative conditions. With three batteries available, the UA is expected to successfully complete all four planned payload drops through strategic batteryswapping. The current competition strategy involves performing two payload drops per battery, with one battery kept in reserve to ensure operational flexibility and mission reliability.
The payload system was chosen based on the results of testing and vehicle constraints. Outlined in the testing section, each payload system was reviewed with three constraints: reliability, usability, and safety. The team needed a system that delivered the payload onto the air drop boundary without risking the aircraft and our crew. We understood that systems break in the field, and a complex and heavy system would limit our ability to complete tasks. For example, we designed and tested a winch system that dropped the payload onto the air drop boundary, but if it did not retract the cable, it could prevent us from dropping other payloads onto air drop zones and could even cause the aircraft to crash. The team chose a more simplistic approach, going with a parachute system to limit safety concerns. It also allowed the team to experiment with parachute designs to find the best option. The only major trade-off with a parachute system is that payloads may be affected by changing environmental conditions.

