Posts

Capstone Poster

Image
As our semester in AT419 came to a close, Thomas Gonya, Todd Horn, and I put together a poster on crew resource management in UAS. We chose this as our poster topic because Thomas and I were the two leaders of the class. In the professional world my goal is to move up into a crew management or operations management position, so having the opportunity to lead the class this semester was great experience for me.  The poster size limited us on how much information we could include, but I will run through the different sections of the poster:  For the top left section of our poster, we researched crew resource management and what exactly it entails. We did not create the star image ourselves, rather we found it during our research. This section is smaller than others and is primarily used to set a foundation for the rest of the poster. The second part of our poster elaborates on how we used the skills described above in our daily operations. The included pictures

First Successful Bramor Flight

Image
On March 27th, we completed our first flight with the C-astral Bramor. The operation ran smoothly with a successful data collection and landing. The weather for the day was around 50 degrees and winds were below 5 mph, creating excellent flight conditions. In order to assure safe procedures and proper flight execution, we followed our checklists closely. It was very beneficial to perform the dry runs from a couple weeks back. Because we ran those dry runs, we felt secure in how the operation was going to run, and eliminated confusion from happening in the field. To begin the flight day, I arrived early to the classroom along with Evan to plan out the mission, as well as go back over the recovery and parachute procedures for the aircraft. While we were there, Ian and Todd were packing a fresh parachute for this flight mission. The parachute must be packed no more than 24 hours in advance of the flight time. After these tasks were complete, Evan (PIC) and I (co-pilot) completed the in-

Progress Report #8

Image
This week in class, our new aircraft the C-Astral Bramor. This is a catapult launched and parachute recover fixed wing aircraft. I only have a small range of fixed-wing UAV experience, so this is a great learning opportunity for me. During the first day of class, we all unboxed the aircraft and simulated a mission which involved: lab checklists, preflight construction, preflight checklists, and flight area mapping. As operations manager, I led the preflight operations (as pictured below). I led the team through the paper checklists provided by c-astral, however at certain points, parts of the checklists were confusing. Luckily, c-astral's ground control station includes a helpful expanded guide on checklists procedures giving us an extra sentence or two about things to do. Unfortunately, I did not capture pictures or screenshots of this. There were times however, when even the expanded checklists were confusing, and we had to seek the help of our professor. Demonstrat

Progress Report #7

Image
This week's post highlights some of the comparisons between two applications that we are using Drone Logbook and Measure. Both of these apps are used as a ground control station link between your phone/tablet and the aircraft you are flying. In this post, I hope to highlight some of the key features of each app, and at the end I will offer some insight into my team's opinion on the apps. We begin by comparing the startup pages. First, the measure app has a clean startup screen where you are given four simple options: "airspace map" where you can view surrounding airspace and where you are legal to fly, "settings" where you can adjust in-app settings, "fly" which takes you to the flight deck allowing you to see through the lens of the UAV (if applicable) and view real-time flight data, and "flight plan" where you are able to draw out the polygon that you are wanting to fly and adjust the overlap, speed, etc. This startup screen is a v

Progress Report #6

Image
Every year, the School of Aviation and Transportation Technology holds a poster symposium which features student-led projects from the idea. As a capstone class, we aim to submit ~3-4 posters to this symposium to demonstrate some of the things that we have been working on in this capstone project. We want to demonstrate to people that UAS is much more than a "push button and fly" operation. We want to display the importance of things such as crew resource management, flight operations and implemented training, GPS, and applying geospatial data. So as a class, we brainstormed that those were the topics that we most wanted to cover. From there, we divided up into teams of two, the team names and focus areas are listed below: Team 1: Kyle and Thomas - operation management (structure of class) Team 2: Ian and Todd - Flight operation Training Team 3: Dylan and Ryan - GPS Team 4: Evan and Krysta - Applied Geospatial Data However, there may be some alterations to be

Progress Report #5

This week, we put our mission planning to the test with a simulated "dry-run" or run through of a mission. The mission that we chose this week was a flood event of the Wabash river. As the operations manager, I created a simulated scenario to give to the class. I told them "The Wabash river experienced flooding due to the intense rain fall overnight, and we need to find the extent of the flooding." I did not share with them how we were going to capture the data.  The walk-through was very productive, as we tossed around multiple ideas on what we need to capture, how we were going to capture it, etc. With Dr. Hupy guiding us, we established that we did not need to capture a specific flooding event, rather we could use the A800 high resolution camera to capture imagery of our entire area. This payload will allow us to create a detailed model of the area, including any elevation change. From there we can throw the data into one of our many softwares and simulate a &

Progress Report #3 (Updated w/ Week 4)

This week, after the completion of the flight area shape files, I finalized the weekly flight schedule. There is a good spread of people flying each day of the week, so once we are able to begin flying I will be able to assign who to out in the field each day. Tomorrow the weather is supposed to be dangerously cold, so much so that Purdue may cancel their classes. If this is the case, then we will push back our Wednesday plans to next week. However, if we do have class as scheduled we will have a "dry run", or a simulated situation. Evan, Thomas, and I will work together to create a situation such as recent flooding and let the class figure out what needs to be accomplished for the mission to be successful. This may include sensor integration, flight planning, designating takeoff and landing zones, etc. Hopefully we are able to complete that this week. Update:  Week four was a slow week because we decided to not require a meeting on Monday. We had planned to test out a dry-