/
2024-??-?? Flight Test

2024-??-?? Flight Test

Owned by Aaron Wang
Last updated: 2024-02-25
2 min read

Remember to update the name of your flight test to be <UNDATED> Team [Drone]: Testpoint

EG, a full flight test request would have the name <UNDATED> EFS [Houston]: Data Collection

Sections for requesting team to fill out:

  • Admin preparation

  • Test Cards / Test Plan

  • Mandatory Attendees

Sections for flight test coordinator to fill out:

  • Flightline team

  • Location

  • Status

  • Drone

Sections for flightline team to fill out:

 

Admin Preparation

Your status should read “submitted” when you submit the FTR to our Flight Test Coordinator.

Once the coordinator approves, and a date/location/drone has been assigned, the status will change to “waiting for sub team review”. Once all sub-teams have reviewed and signed off, the status will change to “approved”

Requested By

@Aaron Wang

Sub-Team Review

(To be checked once reviewed by sub-team representative)

Mechanical
Electrical
EFS
Autonomy
Operations

Date of Request

Feb 14, 2024

Goal Summary

  • Test autonomy task 2 pathing with LTE

  • Landing pad image collection

Status?

Draft

Desired Airframe

Houston / Pegasus / Tubie

Desired Date(s)

Approx Date range for help out with FTC Scheduling

Testplan - to be filled out by requesting team

Create ONE table per test-item. Eg: “Landing pad images over asphalt”, “landing pad images over grass”, “landing pad images over grass, high” should all be unique tables.

Use each expand to capture one series of tests, eg “Landing pad detection” or “Auto-tuning”.

Test #1: Test autonomy pathing task 2 code

Procedure

Goals / Objectives

Knockoff criteria

  1. run pathing repository and LTE communication

Setup and instructions at

Pathing Repository

Testing the Pathing Repository | ELRS

 

  1. Run path_2024 with the task 2 waypoints csv

ensure waypoints are correctly loaded into mission planner and communicated to drone

 

 

Test #2: Landing pad (TODO)

Procedure

Goals / Objectives

Knockoff criteria

  1. Hover altitude <x>

  • Obtain images of <x>

  • Verify colour calibration

  • < anything else you’re evaluating >

< list of reasons why you would want to stop the test >

  1. Translation motion:

Move N->E @ 45m/s groundspeed with landing pad in center 5% of frame

  • blablabla

< etc >

Necessary Preparation

Explain what capacity you need, what needs to be mounted, etc.

Necessary items:

  •  

Flight characteristics needed:

  •  

Comms / Support needed:

  •  

Mandatory Attendees

This is a section for all attendees from your subteam which will be present for this flight test. (because they are testing their products, or otherwise)

Name

Phone #

Sub-team

Role

Name

Phone #

Sub-team

Role

 

 

 

 

This section and remaining to be filled out by FTC and Flightline Team

Flightline Team

Name

Phone #

Role

Reason

Name

Phone #

Role

Reason

 

 

 

 

Pre-Flight Preparation

Checklists

Incident Procedures

Flight Test Timeline

Date/Time

Action

Notes

Date/Time

Action

Notes

0X00

Briefing @ WARG Bay

 

0X00

Arrival at Flight Test Location

 

0X00

Flight Test Card #1…… (eg: Capturing data, tuning, etc)

 

 

Flight Test Card #2

 

 

Flight Test Card #…….N

 

0X00

Debrief

 

 

 

 

 

 

 

DEBRIEF

Related content