Versions Compared

Old Version 1

changes.mady.by.user Anthony Luo

Saved on

compared with

New Version 2

changes.mady.by.user Anthony Luo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tip

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

Panel
panelIconId23f1
panelIcon:stopwatch:
panelIconText⏱️
bgColor#DEEBFF

Sections for requesting team to fill out:

  • Admin preparation

  • Test Cards / Test Plan

  • Mandatory Attendees

Panel
panelIconId1f6a6
panelIcon:vertical_traffic_light:
panelIconText🚦
bgColor#E6FCFF

Sections for flight test coordinator to fill out:

  • Flightline team

  • Location

  • Status

  • Drone

Panel
panelIconId2708
panelIcon:airplane:
panelIconText✈️
bgColor#FFFAE6

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

< your name here >

Sub-Team Review

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

  •  Mechanical
  •  Electrical
  •  EFS
  •  Autonomy
  •  Operations

Date of Request

Goal Summary

< Insert your goals here >

Status?

Status
titleDraft
/
Status
colourPurple
titleSubmitted
/
Status
colourYellow
titleWaiting for Sub-Team Review
/
Status
colourGreen
titleApproved

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

Panel
panelIconId1f6d1
panelIcon:octagonal_sign:
panelIconText🛑
bgColor#FFFAE6

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”.

Expand
titleCard 1: Template flight test series

Test #1: Landing pad images over asphalt

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 >

Test #2: Landing pad images over asphalt

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 >

Expand
titleAdditional template expands

Test #1: Landing pad images over asphalt

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:

  • Jetson

  • CV camera

  • < rfd900 >

  • etc

Flight characteristics needed:

  • Flight speed

  • flight distance

  • max altitude

  • < etc >

Comms / Support needed:

  • Autonomous/repeatable missions

  • ability to hold location within +/- X meters

  • FPV Video from the drone?

  • etc….