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 | |
|---|---|
Sub-Team Review (To be checked once reviewed by sub-team representative) |
|
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”.
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 |
|---|---|---|---|
|
| GSO FTC | |
PIC | |||
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