Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

FTC: Make sure to update the Title following the format “2020-01-30 Flight Test”

📋 Flight Preparation

Requested by:

Required Sub-team integration efforts

  • Mech
  • Electrical
  • EFS
  • CV
  • Operation
  • Sys-Int

Date of Request

Location and Time

Goal Summary

Landing pad images collection with Houston for software settings finalization.

Approved?

Yes ✅ / Pending 🟨 / No 🛑

👥 Mandatory Attendees

Name

Phone #

Role

Reason

 

Flight Test Director

  • Creating documentation

  • Booking the test flight

  • Creating a thread in #flight-staging

  • Responsible for coordinating operations from start of brief to end of de-brief

 Hardy Yu

Ground Station Operator

  • Aircraft preparation

  • Filling out documentation

  • Operation of aircraft

  • Coordination between mission plans

Safety

  • Making sure everyone is safe

  • Bringing Med kit

  • Incident procedure

Amy Hu

Autonomy representative

  • Review landing pad images and update camera settings.

Mihir Gupta

Autonomy representative

  • Review landing pad images and update camera settings

👥 Auxilliary Attendees

Name

Role

Daniel Puratich

Electrical Support

Flight Test Logistics/Director Support

Tc basic

Availability: morning only until 11:30am.

David Wu

AUTO-ML team member

Saturday Morning until 12 pm

Rosanne Zhu

Vibhinn Gautam

🚗 Drivers & Seat Arrangement

Driver

Vehicle Type

Passenger

 

 

 

🥅 Goals/Objectives

Objective

Priority

Owner(s)

Test raspberry pi 3 on Houston

Autonomy

Collect landing pad images and update camera settings

Autonomy

⏲️ Flight Test Timeline

Date/Time

Action

10:30

Member arrive @ WARG Bay

10:50

Briefing @ WARG Bay

11:30

Arrival at Flight Test Location

0X00

Flight Test Operation #1…… (eg: Capturing data, tuning, etc)

Flight Test Operation #2

Flight Test Operation #…….N

0X00

Debrief

🧯 Incident Procedures

Incident

Location

Procedure

Crash

WRESTRC

  • Identify last known location & flight path of the aircraft

  • Divide into teams of 3 and decide on communication protocol

< otherwise >

Flyaway

Outline the procedure for flyaways. List relevant contact information for local authorities and plans of action to recover control of the aircraft

Fire

WRESTRC

  • Designate 911 contact

  • Describe incident (Drone crashed, contains LiPo batteries)

  • Give location of team (Skid pad at the Waterloo Region Emergency Services Training Center)

  • Give best approximation of the location of the drone

< otherwise >

Injury

  • Apply first aid as required.

Property Damage

🔧 Week-Before To-Do List

 Week Before Checklist
  • Raspberry Pi 3 can collect images with the $200 CV Camera
    • Test the imaging repository with the Raspberry Pi and confirm images are taken and stored on the SD card with a SD card reader
    • Edit the rc.local and ensure that image collection code runs on Raspberry Pi startup
  • Raspberry Pi can be powered onboard the drone. Need help from the Electrical team.
  • Raspberry Pi and $200 CV Camera are mounted onto Houston. The $200 CV Camera needs to be pointing in the downwards direction.. Need help from the Mechanical team.
  • 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

 Day Before Checklist
  • SDC Vehicle key collected (if required)
  • Batteries Planned for (DON'T LEAVE CHARGING OVERNIGHT)
    • Drone batteries & spares
    • Transmitter batteries
    • Battery tester/indicator
  • On-site kit together
    • First Aid Kit
    • Ground station / Laptop
    • Antenna / Receivers
    • Transmitter
    • Extra Water
    • Power cords / Extension cables
    • Wrenches
    • Allen keys
    • Knives
    • Tape
    • Rope/string
    • Zip/Velcro ties
    • Radios
    • Safety goggles
    • Fire extinguisher
    • Spare foam
    • hot glue gun w/ hot glue stick
    • harnesses
  • Airfame assembled
  • ESCs/flight controller wired
  • Radio equipment tested
    • Channel mappings
    • Flight modes
  • 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
    • Props
    • Airframe components (landing struts, arms, etc)
      • wings nuts
      • prop nuts
      • any detached components such as angle mount
      • props for other aircrafts such as Houston
    • Hardware to assemble these components
    • Electronics
      • ESCs
      • Motors
      • Flight controllers
      • Receiver
  • Flight Code Flashed
  • Ground station Software updated

↪️ Pre-Departure Checklist

 Pre-Departure Checklist
  • Confirm the Raspberry Pi is securely attached to the drone.
  • Confirm the image collection software runs when the Raspberris powered on.
  • Take the WARG laptop, CamLink, HTMI cable, key board and mouse.
  • Take the WREST RC entrance card
  • Grab Pre-departure Items
    • Battery charger and associated cables(30tx to 60tx)
  • Check battery status
    • Charge if required, otherwise place into flight box
  • Systems test
    • Check flight controller orientation
    • Check motor spin & rotation direction
    • Check transmitter mappings
    • Verify communication links (VTX/RX, Controller, Groundstation)
    • Verify the mission planner is logging data
  • Only attach props directly before flight (keep off at all other times)
  • Get snacks
  • Mission Briefing
    • Read the flight plan to the team (that was made a week ago)
    • Purpose of flight
    • Plan of action
    • Success criteria
    • Delegate and brief on flight line roles
    • Safety Briefing
    • Key flight characteristics to observe
    • Key system characteristics to observe
    • Measurements to be made

🚩 Pre-flight Safety Checklist

 Pre-Flight Inspection
  • Air Frame
    • Check all antennas, ensuring they are secure and in good condition
    • Check the battery emplacement and secure attachment and ensure there are no cracks
    • Check that all lights are operating normally
    • Check that all sensors are secured and clear of any obstructions
    • Check that the GPS is receiving satellites and providing a navigation solution
    • For fixed wing aircraft, Check:
      • Wings, ensuring they are securely attached to fuselage
      • Wing leading edge surfaces
      • Top and bottom of wing surfaces
      • Wing tip surfaces
      • Read of wing and all flight control surfaces for freedom of movement, security and any skin damage
    • For rotary aircraft:
      • Inspect top and bottom of air frame arms for cracks, loose parts, or signs of damage
      • Check fluid levels and ensure no leaks if applicable
  • Control Surfaces
    • Ensure Elevator moves correctly
    • Ensure Ailerons move correctly
    • Ensure Rudder moves correctly
  • Landing Gear
    • Check landing gear is secure
    • Inspect skids or wheels, especially attachment points
  • Power plant
    • Cowling or motor casing
    • Security of engine mounts
    • Presence of any cracks
    • All wiring and connectors, ensure no cracks, loose connectors, or chaffing
  • Propellers / Rotors
    • Ensure propeller is secured
    • Check for nicks, chips or cracks
    • Ensure prop direction is correct
  • Batteries
    • Inspect to ensure there is no signs of swelling, external leaking or other defects
    • Battery wiring and connectors from the battery are connected securely
    • Batteries (and spares) are adequately charged
    • Wires are not pinched
  • Control Station / Receivers / Transmitter
    • The battery and spare batteries if required are adequately charged
    • Control Station device and cables are properly connected and functioning
    • All flight interfaces are functioning normally
  • Safety
    • Good visibility and safe wind speed
    • Surrounding is free of obstacles
    • Crew far from drone
    • General Site Survey
      • Are there other people on the property
  • Ground Recording / drone footage on
  • Autopilot
    • Control surfaces respond to autopilot in the correct manner
    • Transitions between flight modes have expected effect
    • Return-to-home systems, if present, have been configured

😎 Post-Flight Checklist

Item

Owner

  • Use Flight-Post Mortem to Debrief

ALL MEMBERS PRESENT

  • Discard of damaged batteries

  • Discharge used batteries for better longevity

Flight Test Debrief

Flight Test Timeline

Analytics (hopefully applicable)

Flight Test Post Mortem // Final Thoughts // Condensed Summary

  • ,

RCA for Red Items

Create a RCA and keep it as a child page.

Action Items

  •  

Other Resources

Booking WRESTRC Field

How to Book the Flight Grounds

  • No labels