Apr 30, 2023 Flight Test

Make sure to update the Title following the format “Jan 01, 2020 Flight Test”

 Flight Preparation

Requested by:

Required Sub-teams

Mech
Electrical
EFS
CV
Operation
Sys-Int

Requested Date

Jan 25, 2023

Location and Time

WRESTRC From 12:00 pm to 6:00pm

Summary & Goals

Validate the ICRAUS Airframe;

Test Houston autonomy with QR Code integration

Approved?

Yes / Pending / No

 Required Persons During Test

Name

Phone #

Role

Reason

Name

Phone #

Role

Reason

 

 

Flight Test Lead

  • Creating documentation

  • Booking the test flight

  • Creating a thread in #flight-staging

 @Anthony Luo

 

 Pilot in Command

  • Aircraft preparation

  • Filling out documentation

 

 

Safety

  • Making sure everyone is safe

  • Bringing Med kit

@Megan Spee

 

Secondary Pilot

 

 Other Attendees

Name

Role

Name

Role

 

 

 

 

Drivers & Seat Arrangement

Driver

Vehicle Type

Passenger

Driver

Vehicle Type

Passenger

 

 

 

 

 

 

 

 

 

 

 Success criteria

Tests

Success Criteria

Requirements

Outcome

Tests

Success Criteria

Requirements

Outcome

Quad mode take off

  • The drone is able to take off and obedient to the control

  • correct configuration

Video transfer system

  • we see the the first person view video from ground station and goggles

  • system set up

 

Push Propeller Test

  • the back propeller function correctly and help the drone move more quickly

  • motor test

 

Testing Timeline

Date/Time

Action

Date/Time

Action

Apr 28, 2023

Aircraft Assembly

Apr 28, 2023

Pre-flight Preparation

Apr 30, 2023 10:00 am

Required persons for preflight preparation show up at bay

Flight test lead breifly assign task for preparation work

Apr 30, 2023 11:30 am

Flight brief from flight test lead

Apr 30, 2023 11:45 am

Loading onto the Car

Take your water bottle with you. Go washroom before we leave!

Apr 30, 2023 12:00 pm

Drive to the test ground

Apr 30, 2023 12:30 pm

Flight Testing

Apr 30, 2023 4:00 pm

Debrief

Test#1

Quad Sanity Check

  • Purpose is the validate the software configuration and hardware setup

  • If anything goes wrong, then it needs to be fixed before the next flight test

Test#2

Quad with Push Propeller Aisstant

  • No fully fixed wings

  • instead we fly with in quad mode with push propeller on to assist our drone fly faster

Aircraft Incident Procedures

Emergency Procedures:

  • Imminent Emergency: 911

  • Privacy offence: Local police

  • Fly away or loss of control - Local Aviation Authority (Refer to CFS)

    • This applies to both vertical and horizontal fly aways

Control Station Failure

In the event of a control station failure, the following steps should be taken:

  • Attempt to restart the transmitter

  • Use spare transmitter to communicate to drone

  • If unable to establish communication with the drone, follow lost link procedures

Equipment Failure

  • Battery

    • Do not fly if the battery appears dead or a problem is suspected. Puffy batteries should be ignored

  • Transmitter should be verified before flight

  • Props

    • Ensure in flight worthy condition (ex: no dings, etc)

  • Control Surfaces

    • Smooth, verify servo control, pushrod integrity

In the event of an RPA failure, the drone should be disarmed - this will stop all motors. The following steps should be followed:

  • Secure the area where the RPA will land

    • Do NOT fly the drone over an area where the RPA can unexpectedly land for this reason. Thus, flying over people is NOT permitted in this drone

  • Secure the drone and disconnect the battery

  • Do NOT fly the drone until inspected

In the event of loss of transmitter link, the pixhawk will activate return to home mode. If the RTH mode does not engage, initiate fly away procedures

In the event a fly-away occurs (both vertical and horizontal), the following procedures should be taken:

  • Attempt to regain communication by following lost link procedures

  • If unsuccessful, record last heading, speed, and altitude

    • Additionally, know the last battery level to estimate flight time

  • Alert local aviation authorities about new flight path and potential conflicts

The flight may be terminated by disarming the drone - this will stop all motors. This should be used with caution as the aircraft will be rendered inoperable and unable to glide under control.

Week-Before To-Do List

Drone Registration

Drone Registration Number:

Flight test location booked
Pilot scheduled
Test Plan (What we are testing)
This should also include the flight path where applicable
Subteam action items (for flight readiness)
Transportation logistics finalized
Booking SDC vehicles
Assigning drivers
Renting any needed equipment (trailer? generator? etc.)

Day-Before To-Do List

SDC Vehicle key collected (if required)
Batteries Planned for (DON'T LEAVE CHARGING OVERNIGHT)
On-site kit together
Airfame assembled
ESCs/flight controller wired
Radio equipment tested
Motors tested
Wiring secured (Harnessing)
End-to-end test (neglecting props)
Check the center of gravity
All components not on the airframe that are required should be in the flight box (e.g. props & prop nuts)
Airframe payload
Spare parts
Flight Code Flashed
Ground station Software updated

Pre-Departure Checklist

Pre-flight Safety Checklist

Post-Flight Checklist

Item

Owner

Item

Owner

ALL MEMBERS PRESENT

 

 

Flight Test Post Mortem

General list of events

  1. Saturday full throttle tests

  2. Saturday signal integrity checks

  3. Saturday camera equipment not working in 1401. worked in bay later.

  4. Sunday QStabilize WO @ e7

  5. Sunday QAltHold (QHover) WO

  6. Sunday QLoiter WO

  7. moved to innovation park ion station parking lot thing.

  8. qautotune w/wings.

  9. experienced rapid descent nearing completion of autotune D for roll.

    1. had a battery failsafe, aircrfat was configured to take no action.

    2. 3d prints only items broken

    3. rear-right dipped a bit.

 

RCA for Red Items

Create a RCA and keep it as a child page.

Action Items

Other Resources

Future timeline:

Packing starts Tuesday → fully packed on vehicles Tuesday Eve.

Run Autotune before then, ideally.

Booking WRESTRC Field

WRESTRC