Mission 2: Autonomous Flight Skills Mission

Duration: 3 minutes | Type: Autonomous Programming

Navigate to: Comprehensive Examples | Missions Overview | Main Documentation

Mission 2: Autonomous Flight Skills Mission

⏱️
Duration
3 minutes
🎯
Type
Fully Autonomous
🔄
Rounds
Up to 3 matches per event
📊
Attempts
Best score counts
Difficulty
Hard
🏆
Scoring
Variable (task-based)
👥
Team Size
3 Flight Team Members

📋 Key Requirements

  • Fully autonomous operation
  • No manual control during match
  • Sensor-based navigation
  • Error recovery in code

✅ Success Criteria

  • Complete all scoring tasks
  • Consistent performance (90%+ success rate)
  • Handle unexpected situations
  • Maximize points within time limit
Duration: 3 minutes | Type: Autonomous Programming

Students program their Drone to operate fully autonomously, earning points by completing specific tasks during the Autonomous Flight Skills Mission

Scoring Information

Scoring Tasks and Points

Scoring Task Points per Task Max per Match
Take Off 5 Points 1
Fly Under Red Arch Gate 5 Points 2
Fly through Yellow Keyhole 15 Points 2
Identify Color Mat #1 15 Points 1
Fly through Panel (in front and out the side) 40 Points 2
Landing: Cube 10 Points Only one of three landing options, once per Match
Landing: Pad 5 Points Only one of three landing options, once per Match

Note: Each Team (Drone) can earn points for only one Time Warp Flight Path per match. Teams are allowed up to 3 matches per event, with the best score counting toward rankings.

Objectives & Key Rules

Key objectives and rules for this mission:

  • Program drone to operate fully autonomously
  • Complete specific scoring tasks
  • Maximize points within 3-minute time limit
  • Achieve consistent performance (up to 3 attempts)

Key Rules

  • Fully autonomous - no manual control during match
  • 3-minute match duration
  • Up to 3 matches per event
  • Best score counts
  • Must pass Flight Clearance Inspection

Strategy Guide

Follow these strategic approaches to maximize your success:

  • Test and calibrate all sensors before each match
  • Implement error recovery in your code
  • Use multiple sensors for redundancy
  • Test code thoroughly in practice
  • Document sensor values that work consistently
  • Have backup code versions ready
  • Practice the full 3-minute sequence multiple times

Code Example

Example code for Mission 2:

# Autonomous Flight Skills Mission
# Fully autonomous operation - no manual control

from codrone_edu.drone import *

drone = Drone()
drone.pair()

# Pre-flight: Calibrate sensors
# - Color sensor calibration
# - Distance sensor testing
# - Gyro sensor initialization

drone.takeoff()

# Autonomous sequence begins
# Task 1: Navigate to first scoring zone
drone.set_pitch(30)
drone.move(2)
drone.hover(1)

# Use sensors for precise positioning
# (Example: Color sensor for line following)
# (Example: Distance sensor for obstacle detection)

# Task 2: Complete scoring action
# (Specific actions depend on field layout)
drone.set_roll(20)
drone.move(0.5)
drone.set_roll(0)
drone.hover(1)

# Task 3: Navigate to next zone
drone.turn_right(90, 0.5)
drone.set_pitch(30)
drone.move(1.5)
drone.hover(1)

# Continue autonomous sequence...
# (Complete all tasks within 3 minutes)

# Return to landing zone
drone.set_pitch(-30)
drone.move(2)
drone.land()
drone.close()

# Key: Test this entire sequence multiple times!

💡 Need More Examples?

For comprehensive autonomous flight examples covering line following, obstacle avoidance, multi-sensor fusion, and complete mission sequences, see our Comprehensive Autonomous Flight Examples guide.

Pro Tips for Best Score

  • Calibrate sensors before EVERY match
  • Test full 3-minute sequence at least 10 times
  • Implement error recovery (what if sensor fails?)
  • Use consistent sensor values that work
  • Keep code organized and well-commented
  • Have multiple code versions for different strategies

Common Mistakes to Avoid

  • Not calibrating sensors before match
  • Code fails partway through (no error recovery)
  • Running out of time (poor time management)
  • Not testing full sequence enough
  • Sensor values that work inconsistently