SCENARIO 1 OF 2
An engineering team builds a working prototype, tests it, and discovers it fails to meet one of the original requirements. What should happen next?
Un equipo de ingeniería construye un prototipo funcional, lo prueba, y descubre que no cumple con uno de los requisitos originales. ¿Qué debería pasar después?
A quick scenario check — tap the option you think applies, then see why.
Una revisión rápida de escenario — toca la opción que crees que aplica y luego mira por qué.
Describe the steps of the engineering design process (problem definition, requirements and constraints, prototyping, testing, iteration) and explain why real aerospace engineering treats failure as expected data, not something to avoid discussing.
Every aircraft and every drone a student will ever fly or study started as a problem an engineer had to define and solve using this exact process — understanding the process itself, not just the finished designs it produces, is what makes engineering a repeatable discipline rather than pure luck or intuition.
Teach It / Enséñalo
ENTIENDE
El proceso de diseño de ingeniería es un enfoque estructurado y repetible que los ingenieros usan para resolver problemas reales, y generalmente sigue los mismos pasos centrales sin importar si el problema es diseñar una nueva ala de aeronave o un pequeño soporte de UAS. La DEFINICIÓN DEL PROBLEMA viene primero: establecer claramente qué es lo que realmente hay que resolver, para quién, y por qué. Los REQUISITOS describen lo que la solución debe realmente hacer — criterios específicos y comprobables contra los cuales se juzgará el diseño terminado. Las RESTRICCIONES describen los límites reales del mundo dentro de los cuales debe funcionar la solución (presupuesto, materiales disponibles, límites de peso, capacidad de fabricación, tiempo). Luego los ingenieros pasan al PROTOTIPADO — construir una versión temprana, a menudo simplificada, de la solución específicamente para aprender de ella. Las PRUEBAS evalúan el prototipo contra los requisitos originales bajo condiciones reales o realistas. La ITERACIÓN significa usar lo que revelaron las pruebas para mejorar el diseño y repetir el ciclo de prototipo-prueba. El PENSAMIENTO SISTÉMICO significa reconocer que cambiar una parte de un diseño afecta a otras partes. El ANÁLISIS DE FALLAS — estudiar exactamente por qué y cómo falló un diseño en una prueba — se trata como datos valiosos en la ingeniería real, no como algo de lo que avergonzarse. Finalmente, el trabajo de ingeniería real requiere una cuidadosa RECOPILACIÓN DE DATOS durante las pruebas y una DOCUMENTACIÓN TÉCNICA clara durante todo el proceso.
¿Tiene sentido?
AVIATION WORDS · Palabras de aviación
DILO EN INGLÉS · SAY IT IN ENGLISH
“Engineers solve problems by defining what's needed, building a test version, seeing what fails, and improving it — failure during testing is expected and useful, not something to hide.”
Ejemplo guiado
Consider a team designing a small UAS delivery drone: the PROBLEM is delivering small packages to residential addresses; a REQUIREMENT might be "must carry a 3-pound package for 5 miles"; a CONSTRAINT might be "must comply with Part 107 weight and altitude limits." An early PROTOTYPE might use an oversized frame just to test the lift and flight-control concept, without worrying yet about final weight. TESTING might reveal the prototype can't achieve the required range — an engineering team would then ITERATE, perhaps trying a more efficient motor or a lighter frame material, and test again.
Real Aviation Application / Aplicación real en aviación
This exact process — define, set requirements and constraints, prototype, test, iterate — is how real aerospace companies design everything from a small aircraft bracket to an entire new aircraft type, and it's also the same process students use in classroom engineering design challenges, like building and testing a model glider or a simple UAS component.
Ask Your Teacher / Pregúntale a tu maestro
- Can you walk through a real example of how a specific aircraft part went through this design process?
- How do engineers decide which tradeoffs are acceptable when two requirements conflict?
- What's the difference between a prototype and a final production design?
HAMPTON'S .02 CENTS
Students in a classroom engineering challenge often treat a failed first prototype as the end of the assignment rather than the expected first step. Reframe explicitly: if your first design worked perfectly on the first try, you probably didn't test it rigorously enough — real engineering expects iteration.
It Would Behoove You… This process applies directly to any hands-on engineering challenge in this app or your classroom — try applying these exact steps (problem, requirements, constraints, prototype, test, iterate) the next time you build something, like the paper glider from the Four Forces lesson.
Hands-On Activity: Iterative Design Challenge: Protective Package Drop / Desafío de diseño iterativo: caída de paquete protector
Objective: Practice the full engineering design process — define, design, build, test, redesign — by building a structure that protects a fragile object during a drop, then improving it after a real test failure.
Materials: Raw egg or similarly fragile small object (one per team), Assorted craft materials: straws, tape, cardboard, cotton balls, rubber bands, paper, A drop location at a safe, supervised height (e.g., second-floor railing or ladder, with teacher control of the drop), Stopwatch or phone timer (optional, for a timed build phase)
Safety: The teacher must control and perform all drops from height, never students. Clear the landing area of people before every drop. Use only soft-landing surfaces (tarp, grass) if possible to reduce mess and slip hazard. Eggs must be checked for cracks before handling and disposed of properly after the activity.
- DEFINE THE PROBLEM: as a team, write a one-sentence problem statement and list your real constraints (limited materials, limited time, must survive the drop).
- DESIGN: sketch your protective structure before touching materials — identify what part of the design protects against impact and why.
- BUILD: construct your first prototype using only the provided materials within the time limit.
- TEST: the teacher drops each team's prototype from the designated height. Record whether the object survived.
- EVALUATE AND REDESIGN: for any prototype that failed, identify specifically what failed and why, then redesign and rebuild using the same iterative process.
- RETEST: the teacher drops each redesigned prototype and records the second result.
- DEBRIEF: each team explains, out loud, exactly what they changed between version 1 and version 2 and why they believe it worked or didn't.
Expected Outcome: Most teams' first prototype will not fully protect the object; the redesign step, informed directly by the specific failure observed, should produce a measurably better (even if still imperfect) second result — the actual point of the activity is to make the design process's iterative nature completely concrete.
Standards Alignment
CLASSROOM: Introduction to Engineering & Design
FAA: 14 CFR Part 21 — Certification Procedures for Products and Articles (the real-world regulatory process an aircraft design must pass through)
CERTIFICATION: AMT
SOURCES: NASA Engineering Design Process; 14 CFR Part 21 — Certification Procedures for Products and Articles