Skip to content
End Of Semester Review
1) Expectations vs. Reality
Before this course, I expected a simple fixed-wing class. I thought we would set up the aircraft quickly, fly early, and then improve little by little. But the class was even more valuable than I expected. It was a hands-on systems class. The “aircraft” was not only the airframe. It was a full system we had to connect and make work together.
This semester taught me something important. Flying is not the only big goal. Reliability comes from many small choices. These include wiring, settings control, safety setup, and careful checks. I also stopped thinking of the labs as separate tasks. Each lab was one step in a real workflow. We built, set up, tested, fixed problems, wrote notes, and prepared the aircraft for the next team.
2) Overview of the Semester
At the start, we learned basic skills that are truly important. Early training helped me get used to checklists and step-by-step procedures. It also taught me careful handling. These skills are useful for fixed-wing work too, even if the aircraft type is different.
Later, we moved into the Believer labs. The work slowly changed from simple learning to real system work. I learned the system layout and how parts connect to each other. I also learned that one change can affect many other parts.
One thing I remember well is how we made changes to match standards. For example, we changed the DATX setup. We removed some switches to match a specific transmitter protocol.
When we worked on communication, firmware, and avionics. I learned that good results need good configuration habits. We must label parts, check software versions, and set each module in a way others can trust.
This was not only about technical skill. It was also about responsibility and quality. If a part is not clearly labeled or checked, it becomes a real risk. It can hurt safety and also slow down the project. By the time we worked on motors, controls, and final assembly, the aircraft felt like one complete system. We brought together structure, electronics, settings, and safety so we can continue the work next time.
3) The Value of Building From Scratch
The best part of this course was building from begining. We did not receive a ready-to-fly kit. We built the airframe and installed electronics by ourselves. This helped me understand the aircraft as one system. I could see how build quality, wiring, receiver setup, and software settings all affect each other.
This is very different from plug-and-play systems. In plug-and-play, things may work quickly, but I may not know why they work. In this class, I learned the reasons behind the system behavior.
I also learned to be open-minded about software. We used a closed and specialized tool, not only open-source tools. This showed me that real UAS work often has limits. Sometimes we use locked computers, standard steps, and tools made for stable performance, not for personal customization. That experience helped me look at systems in a new way. I learned to judge a system by ease of use, consistency, safety, and team performance.
4) Skill Growth & Technical Learning
This semester improved my confidence in four areas. I learned better hardware assembly and clean wiring habits. I learned how the whole system is designed and connected. I learned firmware and configuration management. I improved my troubleshooting skills.
A good example was fixing a receiver configuration problem. The receiver seemed to lose its settings after power cycling. That made binding and setup unstable. We used a clear troubleshooting process, checked the receiver mode, checked what should happen during binding, and watched what mode it entered at startup.
It was going into bootloader mode, not bind mode. That explained why settings were not saved. After we set it correctly, the setup became repeatable. This taught us that we should test one idea at a time, confirm the system state, and focus on repeatable results.
Another big lesson was verification and labeling. I saw how easy mistakes are when labels and notes are missing. After that, I took verification more seriously. I checked what version was installed, made sure the full process was done, and did not “guess” when something was unclear.
I also improved teamwork and communication. I helped classmates not only with steps, but also with the reasons behind the steps. Conversations with team mate made my own understanding stronger. It also helped me connect lab work to real goals like safety, reliability, and easy maintenance.
5) What Surprised You
The biggest surprise was how small design choices can affect safety. I noticed the radio setup did not include a physical arm/disarm switch. That made me think more about human factors, risk, and safe procedures.
Even if there are other switches, the safety setup still matters. The way switches are mapped affects how easily a pilot can make the right choice under stress. I learned that safety is not something we add at the end. Safety must be built into the controls, the procedures, and the configuration from the start.
This also made me want to act like a safety-minded teammate. I want to ask safety questions early and suggest simple solutions.
6) What You’re Most Proud Of
I am most proud of two things. I listened carefully team mates voices. When I fully understand what they said, I knew I was learning more than just steps.
I learned how important system reliability is. When problems were hard to solve, I saw how careful troubleshooting and teamwork can move the project forward. I also noticed that respectful communication and clear standards make a big difference. This reminded me that technical teams improve when people share ideas, stay solution-focused, and follow the same process.
7) Overall Takeaways
This course increased my confidence with UAS hardware in a real way. I now understand that building a UAV is not one skill. It is many skills working together. It includes build quality, electronics discipline, configuration control, and structured troubleshooting.
The course also taught me how to work under limits, how to work with people who have different experience levels, and why documentation matters. In future classes, internships, and projects, I will follow a clear approach. I will keep wiring clean, keep the aircraft easy to maintain, track configuration changes, verify before I assume, and treat safety choices as design choices. Most importantly, this semester helped me become a more complete UAS team member who can build, integrate, troubleshoot, and support others.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.