Week 12 · overview
Week 12: Checklists, Emergency Planning, and Documentation
This week, you will build checklist and incident-response packet for a bounded Drone Engineering scenario. The work stays in classroom-safe analysis, supplied evidence, simulation, planning, and documentation. It does not authorize real flight or unsupervised hardware work.
The engineering problem
A team discovers a missing propeller guard and a confusing battery label during preflight review.
The core idea is that checklists are not paperwork. They are memory support for risky systems. Students will connect that idea to preflight, launch, mission, recovery, postflight, incident, and maintenance records each catch a different failure type.
Evidence you keep
| Sequence | Evidence artifact |
|---|---|
| Lesson 1 | Mechanism explanation and first evidence table |
| Lesson 2 | Boundary note and no-go or revision condition |
| Lesson 3 | Review-ready decision table |
| Flight Log | Checklist and incident-response packet with limitation statement |
Vocabulary and decision lens
Important language this week includes: system boundary, evidence, limitation, no-go condition, revision rule, and checklists, emergency planning, and documentation.
Decision lens: revise the checklist when evidence shows a repeated near miss, unclear wording, or a step that cannot be observed.
Approximate time: 3 to 4 class periods, about 160 to 200 minutes of reading, analysis, evidence writing, and review.