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:
EFS to fill out Card #1, #2, #3 (Opflow, Tracking Antenna, Obstacle Avoidance)
đź“‹ 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 | Jan 16, 2024 |
Goal Summary |
|
Status? | WAITING FOR SUB-TEAM REVIEW |
Desired Airframe | Houston / Pegasus |
Location + Time | WrestRC 1300-1800 |
🥅 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.
Mechanical
- Pegasus cleared to fly (mechanically)
- sensor mount ready
- Motors + frame rigid
- Houston cleared to fly (mechanically)
- sensor mount attached
- arms + plates rigid
Electrical
- Pegasus cleared to fly (electrically)
- harnessing secure
- Houston cleared to fly
- Harnessing secure
Embedded Flight Software
- Software ready
- Opflow, lidar (s) properly setup
- Test area SME available
- Test procedure is clear
- Possible deviations from test understood and considered
- Software ground tested
- Ground tests complete on all airframes (on battery over telemetry)
Autonomy
- LTE telemetry ready
đź«‚ 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 # (opt) | Sub-team | Driving | Role |
---|---|---|---|---|
Director | Y - 5pass SUV | |||
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 |
---|---|---|
0900 | Start charging batteries 4x 6s 5000mah (pegasus) 3x 3s 4000mah (houston) | |
1000 | Briefing @ WARG Bay | |
1030 | Final flight inspections | |
1130 | Lunch break! | |
1230 | Begin loading vehicles | |
1300 | Arrival at Flight Test Location | |
1330 | Flight Test Card #1…… (eg: Capturing data, tuning, etc) | |
 1400 | Flight Test Card #2 | |
 1430 | Flight Test Card #…….N | |
1500 | Packup | |
1600 | Debrief | |
1700 | <> |