10:30

Member arrive @ WARG Bay

10:50

Briefing @ WARG Bay

11:30

Arrival at Flight Test Location

12:00

Flight Test Operation #1: Tested houston auto mission, RPi not plugged into drone

• We didn’t connect RPi since we wanted to first ensure that Houston was successfully able to run an auto mission and see where it went so we can position landing pads accordingly.

12:45

Flight Test Operation #2: Ran Houston with auto mission, RPi plugged in and used camera settings in run.sh scripts. Collected and saved images.

• We powered the RPi and started to collect images while the drone is in flight. Noticed that the images were very purple.

1:30

Flight Test Operation #3: Ran Houston with auto mission, RPi plugged in and used default camera settings. Did not save images Amy Hu do you know the reason why.

• Powered the RPi and collected images but noticed that it didn’t collect images.

2:00

Flight Test Operation #4: Ran Houston with auto mission, RPi plugged in and used default camera settings. Collected and saved images.

• Powered the RPi and collected images. Noticed that images looked more normal.

2:30

Flight Test Operation #5: Ran Houston with auto mission, RPi plugged in and used new camera settings. Collected and saved images.

• Powered the RPi and collected images. Noticed that images were more purple with the new settings.

3:30

Debrief

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