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 3 Current »

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 Autonomy Landing Pad Data Collection

Status?

APPROVED

Desired Airframe

Houston

Desired Date(s)

2023-11-26

🥅 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: Landing Pad Automission

Prerequisite

Objective

Knock off Criteria

  • aircraft ready

  • camera mount from mech finished

  • camera focus properly adjuested

  • video logging

  • rpi is at operating tempurature

  • capture more good quality image from the air that will be used for model training

  • run out of batteries

  • autonomy rep call done

Procedure

  1. spreading landing pads to proper locations

  1. initiate camera logging

  1. set up auto mission in the mission planner

  1. push mission to the pixhawk

  1. takeoff and run auto in mission planner

  1. repeat

Prerequisite

Objective

Knock off Criteria

Procedure

Necessary Preparation

Necessary Preparation

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

Necessary items:

  • Cv camera and power supply securely mounted onto the drone

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

Amy Hu

Autonomy rep

Driver

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

 

 

 

 

 

 

 

 

💻 DEBRIEF

Debrief by Hardy Yu

 Timeline

 

 Data & Data Analysis

 What Went Well?

 What was less than ideal but turned out okay?

 What major issues occurred?

All of these major issues should be addressed via Root Cause Analysis Forms:

 Action Items Following Test

  • No labels