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 4 Next »

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

Hardy Yu

Sub-Team Review

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

  • Mechanical
  • Electrical
  • EFS
  • Autonomy
  • Operations

Date of Request

Goal Summary

Houston AutoTune / Pilot Training w/ Houston

Status?

APPROVED

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:

Test #1: Houston AutoTune

Prerequisite

Objective

Knock off Criteria

  • Autotune research done

  • rpi, camera removed

  • aircraft ready

  • get pilots/GSO familiar with the procedure of how to autotune

  • autotune done

  • or we crash

  • or we runout of battery

Procedure

  1. Add AutoTune channel on Mission Planner

  1. Takeoff in AltHold and fly to a comfortable altitude

  1. Turn on autotune aux

  1. Be mindful of altitude of the drone and don’t let the drone fly too far away as well

  1. When autotune finished, disarm the drone while the autotune AUX is ON!!!

Test #2: Pilot Training

Prerequisite

Objective

Knock off Criteria

  • aircraft ready

  • stabilze mode quad drone control tranining

  • runout of batteries

  • crash

  • tried

Procedure

 Card 2:

Test #1: Pilot Training - Yuchen Lin

Prerequisite

Objective

Knock off Criteria

  • aircraft ready

  • stabilze mode quad drone control tranining

  • runout of batteries

  • crash

  • tried

Procedure

Test #2: Pilot Training - Hardy Yu

Prerequisite

Objective

Knock off Criteria

  • aircraft ready

  • stabilze mode quad drone control tranining

  • runout of batteries

  • crash

  • tried

Procedure

Necessary Preparation

Necessary Preparation

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

Necessary items:

  • N/A

Flight characteristics needed:

  • Require long flight endurance (needs more batteries)

Comms / Support needed:

  • TBD

🫂 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

 Hardy Yu

 

 

 GSO FTC

Yuchen Lin

PIC


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

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