Weekly writing:
This week, the AT219 course began, and students got back into the swing of the coursework. Punch lists and project assessments were conducted in the lab section of the course, and groups picked up where they left off from the prerequisite course. In other news, I began instructing for a new flight student, and I believe we will be a good pair. This semester will be marked by increased hands on learning for me ijn the AT219 course and in others, and I aim to make the most of my final semester here at Purdue (even though I will likely hang around the area for a few months more).
Overview
Resources and Tools
Tasks
Group Blog
In this section, we will transition and redistribute team members to new groups, update the blogs, and assess the quality of the handoff.
Group Members: Venky, Eli, Jacob, and Nolan.
Update Group Blog Access
Develop three new groups of equal size. Work with instructors to update access to the . Verify that you have access to the correct group blog and update (or add) the team member names.
* Do not delete previous team member names; just add a new section for spring 2026 team members. Assess Group Blog
Take 15 minutes to review your new team blog and answer the following questions:
What did the prior group do exceptionally well that your team would like to continue? They had a large number of pictures and visuals which made things easy to understand from the outside looking in. They are also very organized, which is a product of guidance from the professor. In regard to their aircraft, it is evident that they took care in sealing the two sides of the fuselage together. They are fairly far, but work needs to be done. What did the prior group do poorly that your team will improve upon moving forward? The prior group did not put their name on the box, and this was poor. Furthermore, they did not remedy the damage to the right aileron, which was apparently a product of shipping. These are only small points, and upon initial inspection, everything seems to be in order. What gaps can you identify in the blog that your team will need to work to fill in? (wiring diagrams, parts list, etc.) In regards to the blogs of the group for the assignments from the fall, it appears as though most of the information expected to be there was. It is apparent that there were two labs Group 4 had that this lab did not, and those were lab 5 and lab 8. However, on the work that was completed in this subpage, it is apparent that adequate work was completed. Is this a document that you would find sufficient to pass off in the workplace? Could someone easily pick up where the prior team left off? This document would indeed be sufficient to pass of in the workplace because of the concise manner in which the information was written. In addition, there was no serious amount of information included which was not applicable to the tasks at hand, and this was appreciated when digging through the files. Information was completed step by step, to the point, and with the intention of success in the future. Punch List
Now that the product has been handed off to a new team, it’s important to understand exactly what needs to be done to complete the build. In this section, you will create a punch list outlining exactly what remains to be completed before your team is ready to perform a ground test in . A is a document that outlines the final tasks or repairs that must be completed before the product is accepted by the client and payment is made. This term is common in both construction and manufacturing. Often, the punch list is created by the final quality assurance inspector or equivalent as the project nears completion, but before the work crew moves offsite or onto a new project. In the space below, create a punch list for the aircraft now assigned to your group. You may format the punch list however you wish, but it must be clear and complete and include an assessment of:
They need to re-flash the software Right aileron: damage to trailing edge (needs fiberglass tape) Furthest aft fuselage compartment is difficult to open All of the parts appear present Missing documentation (refer to ) Expected time to complete outstanding tasks 10 minutes they should have done the labs and just not in the group coda the re-flashing should take about 10 min as well GROUP03_CURRENT_PARAMS.json
38.6 KB
Health Status with all sensors correctly installed on cube All sticks can move freely in all directions Receiver and Transmitter bound All models are downloaded on the DATX DAB010 is downloaded (not sure if it is the same as DAB10) Deliverables
Upload a of your group’s Lab 01 blog page to Brightspace. Upload a JSON file of the current parameters. One copy per group, please.