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 | < your name here > |
|---|---|
Sub-Team Review (To be checked once reviewed by sub-team representative) |
|
Date of Request |
|
Goal Summary | < Insert your goals here > |
Status? | DRAFT / SUBMITTED / WAITING FOR SUB-TEAM REVIEW / 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”.
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….