Skip to content
What issues were identifiedWe didn’t glue some of the parts, and this included the two halves of the fuselage as well as many components.Why the reviewing group flagged themThey flagged this because glueing the two parts is very important to ensure no structural damage to the aircraft while in flight.Whether the issue is cosmetic, structural, alignment-related, or proceduralMost of our issues were structural and procedural. Our group was behind compared to the other groups, and we believe this was do to members of our group getting busy towards the end and couldn’t get the tasks done.
Specific steps required to fix or mitigate the issueTools or materials neededWhether disassembly is required
Why correction is not possibleHow the risk will be minimized moving forward
What work was done Reference and follow your wiring diagram throughout the buildInclude photos of relevant stepswe first reviewed the other groups punch list We glued the two parts of the believer together sanded down extra glue residuewe glued the landing pads together aft landing pad installedfoward landing pad installed glue residue formed on foward mkost bay for landing padScraped out the residue to ensure the pad can fit securely. secured two fastening hooks for the wings on both sidewe guled the control horns to all control installing rudervator servos to tail section hooks installed on ruddervator control horns installed on wings to later be connected to servos venky overglued the control horns so we now need to remove Venky from the groupwe screwed screws from the black thing into the white thing ( assembly of servo linkages) installing servo linkages to tail section to later attach to the ruddervator seeing how motor will fit into motor mount to prepare for soldering adding push rods to the tail to eventually give movement to the ruddervatorleft off here
Lab 03 - Build Believer
15 points
Nathan Tyler Rose
Last edited 26 days ago by Jacob Daniel Sieber.
Weekly writing:
This week in AT209, the MFE Believer was built further. The two halves of the fuselage were glued together, and many other parts were inserted in various places on the aircraft. While it is evident that more work needs to be done, it feels good to have so many steps taken in the right direction. I am very optimistic about the pace my group is working at, and flying an aircraft that the pilot built will be a very fulfilling moment. I am sure of it.
Second weekly writing:
This week, my group continued to work on the MFE believer project, and the main focus was on electronic parts. It is my opinion that our progress is leading us quite far, but we are still largely behind schedule. My group members and I have come in on a number of days outside of class to complete the aircraft construction, but we cannot seem to ever find the time to complete it. It is mildly frustrating to be so behind, but the finished project will be worth it. As a side note, the skills of my peers and I on fixed wing simulators continue to increase.
Third weekly writing:
This week, we continued to build the group MFE Believer. Another simulator assignment was completed about the basics of flight with fixed wing aircraft, and these skills will be important to know in the very near future. Our drone in particular requires only a few hours more work to be flight ready, as the electronics are all that is left to construct. I have fallen ill at the end of this week, but I will return with vigor come next Monday.
209 lab link with blog:
Lab Overview
In lab 1, students swapped aircraft and conducted a peer review of another group’s Believer build. Each group identified defects, concerns, workmanship issues, and positive build practices on one other aircraft and documented their findings.
In this lab, students will return to their own aircraft and use the feedback provided by another group to critically assess their current build status. The goal is to identify deficiencies, understand root causes, and develop a clear corrective plan before continuing further assembly.
Feedback Review
Carefully review the written feedback provided by the other group.
Discuss the comments as a team to ensure everyone understands:
You are expected to take the feedback seriously. Even if you disagree with a comment, you must be able to justify why it is not an issue based on the build instructions, measurements, or aircraft configuration.
For every issue listed, develop a clear corrective plan, including:
Essentially, the main issue was that parts needed to be glued together. The steps taken to remedy this issue essentially included obtaining the proper parts and glue gun, then successfully merging them. The tools needed for this process were basically the hot glue gun and the occasional screw driver when completing small part assemblies. Dissasembly was not required.
If an issue cannot be fully corrected, the group must explain:
No issues could not be fully corrected, but not all issues were addressed.
The build
Continue the physical build of your Believer and document all work in detail.
Your documentation should clearly reflect
The goal is not just to complete steps, but to ensure the aircraft is being assembled cleanly and deliberately.
Apply the feedback and lessons learned from the peer review to the remainder of the build. The expectation is that build quality improves moving forward and that previously identified issues do not reappear later in the project.
Progress Made 1/29
We still need to finish the build; however, we took the feedback and accepted it gratefully. We got through most of the feedback. The only thing our group deemed useless was when they mentioned that our engine mounts were wrong and after communication with Anestis we realized there are two parts to the engine mounts and we have it correct. Due to time we couldn’t get to any of the soldering. We got to installing the surface control to the servo via mechanical linkage. We have a step by step instruction of what we did in above which was typed by our scribe, Ryan Pirro.
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.