Week 7

Since we are still unable to fly in the field we are still working on posters and doing dry runs. This week poster work was the main focus. Me, Kyle, and Thomas are doing our poster on crew resource management and the big differences between Purdue's Drone Logbook and Measure. When looking at both the sites, Drone logbook seemed to have many more features. Checklists, times flown, operators, drones, inventory lists...etc the list goes on. It may need some more work to be more user friendly but it does have many useful features. We haven’t been able to use Measure so we don’t know what can go on the site. This impeded our ability to accurately judge both, the only aspect that we didn’t like was its lack of features. The site didn’t seem to have any tools, or at least any that we could find. We looked on Measures website to see what they claimed to have and still found nothing. On drone logbook we found a graphic with lots of claimed to have features. (Fig 1)

To us, this showed that drone logbook was able to advertise what their software could do, while Measures advertisement is much more broad and less specific. There were no specific graphics on their site that showed what it could do. But all this could only be due to the fact that we have not been able to utilize the software. We haven’t been able to fly yet so there could be features that are only accessible once flights have started. We will find out more once we have flights in. Below (Fig 2) is the beginning of what our poster is going to look like, we still need more data on CRM and both software's before we can make more concrete conclusions.

Week 6

In week 6, I was able to inventory the rest of the batteries for the DJI M600. The flight teams have been created based on what day/time they were able to fly, with the exception of Krysta. She has a revolving work schedule, meaning she sometimes works different days of the week. After looking at the times for our class to fly, there may need to be some changes. Most days a group of 3 or more can only be together for 1 hour. This is unreasonable because just getting the equipment and ground control station setup can take an hour. Those who are able to fly the most will be on the Bramor airframe. This is due to the complexity of the preflight checklist. I want to keep a flight crew specially for the bramor. This airframe is very costly and cannot afford small mistakes. One way of working everyone into the Bramor team is to switch out one of the team members on it. So if the team were to have 3 people. Person 1 & 2 would always be on the team but person 3 would be switched out with the other members. This would ensure everyone would have the chance to gain familiarity with it without significantly increasing the chance of an incident. There is still the issue of people simply not having the time to be able to fly, but that will have to be discussed in more depth. Since the weather is still unflyable we have been tasked with creating posters for the SATT poster symposium. In my group is Kyle and Thomas. Our poster idea revolves around flight crew and crew resource management (CRM). For our poster we will talk about how CRM is utilized in UAS operations, this is a key role for these type of operations. We have not been able to discuss the poster more throughly, but we will be working on it solely next week.

Week 5

During week 5, we had a dry run test for mission operation. What this consisted of is a theoretical mission that needed to be completed. As a team, we decided where the best location of our test site (West Lafayette Amphitheater) would be for a major flood. As a team, we chose what platform we would use, what day would be best suited, and how we would perform the mission. We picked out one of the shape files on our map then proceeded to choose a location where we would launch our aircraft. Since the mission would be to capture flooding, we would be utilizing an RBG camera with the highest resolution as possible. Which meant using the Bramor with its normal RBG camera. Theoretically before hand we would have video of the site area. Since we would have both, we would be able to compare the results before and after. We could also compare our results to the Tippecanoe GIS maps. The test run was a great idea and showed us a lot of could be flaws in our operation. We still need to work out minor flaws but the dry run was a success in showing us how we would do this operation if it came to be. 

During this week I also continued to pack parachutes for the Bramor. Since the parachute is the main method of landing for the Bramor, it is of paramount importance to get this up and running. Still waiting on the Bramor to create a checklist and its appropriate documents. 

Week 4

Due to inclement weather, class was cancelled on the day we planned to try out a dry run of our operation. What we had planned to do was get everyone together and simulate an operation. We would simulate us going out into the field to gather data from our test site. Since we wouldn't be flying, we would load an SD card onto the platform with data already on it. Then we would act as if we just came from from the field with all of our data. The flight team would then organize the data correctly and put it into the correct folder for data processing. This dry run would show us, as a class, what processes could be further developed or improved. A dry run would also give us a good feel as to how the operation should feel once we get into the real flights.
As for the flight engineering, Ryan has made an M600 checklist that he has put on drone logbook. We have reviewed the checklist but still need a dry run to test it out.