Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

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

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

 Card 1: Task 2 parthing

Test #1: Test autonomy pathing task 2 code

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 image collection

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 >

 Additional 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:

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

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

Flightline Team

Name

Phone #

Role

Reason

Pre-Flight Preparation

Checklists

Incident Procedures

⏲️ Flight Test Timeline

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

  • No labels