Requesting team: Leads/Directors/Comp 24 team
Items TBD:
Test Procedures/Test Cards
Sections for flightline team to fill out:
Incident Procedures, communication preferences.
Test Cards
đź“‹ Admin Preparation
Flight test approved
Requested By | |
---|---|
Sub-Team Review (To be checked once reviewed by sub-team representative) |
|
Date of Request |
|
Goal Summary | Test full pegasus system Test groundside tracking antenna software |
Status? |
|
Desired Airframe | Pegasus, Houston |
Desired Date(s) | April 6 |
🥅 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”.
Explain what capacity you need, what needs to be mounted, etc.
Necessary items:
Pegasus
Houston
Flight characteristics needed:
Comms / Support needed:
đź«‚ 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 |
---|---|---|---|
Organization/transportation/media collection | |||
Hardware | |||
Autonomy rep (to test pathing task 1 and 2) | |||
This section and remaining to be filled out by FTC and Flightline Team
Flightline Team
Name | Phone # | Role | Reason |
---|---|---|---|
PIC | Practicing for Comp | ||
Pre-Flight Preparation
Checklists
Incident Procedures
⏲️ Flight Test Timeline
Date/Time | Action | Notes |
---|---|---|
1030 | Left Warg Bay | Was happy |
11:08 | 1-1 | |
11:10 | 1-1.5 | |
11:12 | 1-2, @ 20m | |
11:17 | 1-3 | |
11:20 | 2-1 | |
11:27 | 2-2 | Noticed drifting, position and yaw |
 |  | |
 |  |