The Solo Transport Challenge

INTRODUCTION

2.1. THRUST

2.1.1.The principal thrust of the 3DR Solo Transport Challenge is the safe application and execution of Systems Engineering principles to develop and operate a Solo UAS to successfully accomplish the mission tasks.

2.2. SCORED ELEMENTS

2.2.1. The five scored elements of this competition are:

2.2.1.1 Flight Plan Report

2.2.1.2 Oral Briefing of a Flight Readiness Review (FRR)

2.2.1.3 Flight Mission Demonstration-Waypoint Challenge and Target Challenge

2.2.1.4 Overall Safety Score

2.3. OPPORTUNITIES

2.3.1. Student teams will be judged based on their performance and that of their system. Trophies will be awarded for top performances. Opportunities for interaction with UAS engineers, scientists and leadership will be provided.

2.4. RULES

2.4.1. The Transport competition will be based upon the competition rules outlined within this site containing administrative and performance objectives. These rules may be updated with clarifications or updates and posted as the official rules for competition.

4. MAJOR ELEMENTS OF THE COMPETITION

4.1.REGISTRATION PROCESS

4.1.1 It is required that all student members of the team become student members of Academy of Model Aeronautics (AMA).

4.1.2 It is required that all student members of the team become familiar with the 3DR Solo platform. Including the radio controller, software, applications, features and components.

4.2. PROOF-OF-FLIGHT

4.2.1 Prior to the competition, a proof-of-flight video shall be submitted as proof that the team’s aircraft can attain, sustain, and land in a safe manner.

4.2.2 The proof-of-flight video does not need to have the craft in full autonomous configuration. It is acceptable to demonstrate a Radio Controlled (RC) flight.

4.2.3 The proof-of-flight video shall identify the school and the team name. The video shall show the vehicle demonstrating safe Takeoff, Flight, and Landing.

4.2.4 A text file containing a link to the team’s video posted on the internet (www.youtube.com) is preferred) shall be submitted by the specified date and time deadline

4.3. SAFETY INSPECTIONS

4.3.1 Safety inspections shall include a physical inspection, and may include a fail-safe check, and flight termination check.

4.3.2 Safety inspections shall be performed on all aircraft by designated competition safety inspectors prior to being allowed to make any competition flight.

4.3.3 The safety inspections are not a scored element. All decisions of the safety inspector(s) shall be final.

4.3.4 Physical inspection of the aircraft shall include:

4.3.4.1 Verify all components adequately secured to vehicle.

4.3.4.2 Verify rotor structural attachment integrity.

4.3.4.3 Visual inspection of all electronic wiring.

4.3.4.4 Check general integrity of any payload system

4.3.4.5 Verification of fail-safe mode operation covered by manual override and pilot-commanded flight termination may be requested by the judges.

4.4. FLIGHT READINESS REVIEW (FRR) BRIEFING

4.4.1 The FRR shall be an oral briefing presented to a team of judges during which the teams substantiate, with data, their plans to safely accomplish the mission.

4.4.2 The intention is to demonstrate to the judges that the team is ready to compete safely, with low risk, in the flight mission phase of the competition. The FRR shall address the mission tasks the team plans to achieve during flight.

4.4.3 Following the FRR briefing, there will be a question and answer period, followed by an inspection of the team’s UAS, including aircraft, ground station, test data, safety checklists, and other supporting evidence.

4.4.4 All team members present are encouraged to participate.

4.4.5 The FRR Briefing will be held at the flying location and will be oral only. Teams may use their aircraft or ground control station to demonstrate various aspects of the briefing. TEAMS MAY NOT POWER UP THE AIRCRAFT.

4.4.6 The FRR Briefing is a scored element worth TWENTY-FIVE Points. The FRR briefing will be assessed on the team’s ability to effectively articulate the scope and depth of the developmental testing performed, the ability of the system design to perform the planned flight tasks, and the preparations made to improve the chances of a successful Flight Mission.

4.4.6.1 The FRR briefing shall not exceed 15 minutes in duration, followed by a maximum period of 5 minutes where the judges will ask questions and the team shall answer. A judge will time the presentation, provide a 2 minute warning, and cut off extended presentations as needed.

4.4.6.2 The breadth of the presentation will be scored based upon inclusion of the following elements with relative worth in percent:

4.4.6.2.1 Team member introductions including flight mission roles and experience. (10 %)

4.4.6.2.2 A brief system overview relating to flight tasks planned, expected performance, and any risk evaluation. (10%)

4.4.6.2.3 System Safety with identified design and operational strategies. (10%)

4.4.6.2.4 Developmental Test Results including: test plan schedule (through ground testing to flight testing to mission performance testing), results of testing, and any corrective action taken to improve the effectiveness on mission completion. (30%)

4.4.6.2.5 Evidence of Mission Accomplishments. (10%)

4.4.6.2.6 Pre-Mission Briefing, including personnel resourcing for the flight, communication procedures, Go/No-Go criteria and fallback plans should a technical issue arise during flight mission. (20%)

4.4.6.2.7 Team member participation and communication skills (clarity, accuracy, logic, precision, relevance, depth, and suitability). (10%)

4.4.6.2.8 Judges will ask 5 questions. Each question will be worth 1 point. Any team member may answer.

4.5. FLIGHT MISSION REQUIREMENTS

4.5.1 The flight Mission evaluates the teams’ ability to conduct a mission operation with their vehicle. This is the culminating event and a scored element of the competition.

4.5.2 A lead judge will be assigned to each team at the flight line. It is important that all team members follow the instructions of the judges. There will be additional judges assigned who are focused on different aspects of the competition (imagery, autonomy, safety, teamwork, etc.) depending on which tasks the team is planning to accomplish.

4.5.3 Only systems presented in the FRR, inspected by safety inspectors, and included in the preflight brief will be permitted to fly.

4.5.4 OPERATIONAL TIMELINE

4.5.4.1 Setup Time = 15 minutes maximum. Setup time begins when the team arrives at the flight line. A lead judge will be assigned to each team and will start a dedicated stopwatch after communicating with the team Captain. After the maximum time, the judge may declare mission start, regardless of the team’s readiness to launch the mission.

4.5.4.2 Flying Time = 30 minutes maximum.

4.5.4.2.1 Flying Time shall start at the declaration by the Lead Judge who will have a dedicated Mission Clock Stopwatch.

4.5.4.2.2 A team may elect to cycle through the takeoff and landing sequence during the flying time more than once for a variety of valid reasons (change batteries, load payload, etc). No points will be lost, but flying time continues to be used.

4.5.4.2.3 Flying time stops when the vehicle has completed flight (landed, crashed, or terminated) and the team has turned off transmitters. The lead judge will confirm with the team captain that the flying time period has stopped and the post processing time period starts.

4.5.4.2.4 Teams that are still flying after 30 minutes will be assessed a penalty of one point for each minute over the 30 minute time limit.

4.5.4.2.5 Teams that are still flying after 40 minutes will be disqualified.

4.5.4.3 Post Processing Time = 20 minutes maximum.

4.5.4.3.1 Post Processing Time begins immediately after the flying time stops. This time is for data processing. No RF transmission shall be performed during Post Processing Time.

4.5.4.3.2 Post Processing time stops when the team captain hands in the scoring sheets, or when the maximum post processing time is exceeded.

4.5.5 MISSION LIMITATIONS

4.5.5.1 Mission Boundaries

4.5.5.1.1 During the entire mission, aircraft shall remain in controlled flight and within the no-fly- zone boundary. A specific no-fly-zone boundary definition will be provided to teams following their FRR. Any vehicle appearing uncontrolled or moving beyond the no-fly-zone boundary during autonomous flight will be subject to immediate manual override. Failure of manual override will result in flight termination.

5. SYSTEM REQUIREMENTS

5.1. TEAMS WILL NEED TO PROVIDE THEIR OWN LAPTOP. ONLY A SINGLE LAPTOP WILL BE ALLOWED ON THE FLIGHT LINE WITH THE TEAM OR DURING THE ORAL PRESENTATION.

5.1.1 All teams must use Mission Planner GCS Software. Version is not important.