ARGO Lab

How AeroLab becomes ARGO engineering

The Phase 6 Engineering Lab (Lessons 36–39) accepts wing area, wingspan, mass, and propulsion values and estimates lift, drag, wing loading, aspect ratio, and lift-to-drag ratio for an ARGO demo aircraft. Phase 7 (Lessons 40–47) goes a level deeper into the flow itself — potential flow, circulation-based lift, boundary layers, separation, lifting-line theory, and wingtip vortices — all still educational models, not CFD. The ARGO database itself has no numeric specifications yet, so every value across both phases is clearly labeled as either database data (currently none), your own entry, or an estimated/modelled result, never inventing a number in between. None of the lessons and simulations below are wired to a specific ARGO aircraft’s real specifications yet — every value in them is clearly labeled as educational, placeholder, or user-entered.

Phase 8 (Lessons 48–55) turns those tools into a conceptual aircraft-design workflow: define the mission, estimate mass, size the wing, shape its geometry, check aerodynamic performance, match propulsion, check stability, and optimize against constraints. It is an educational design laboratory, not certification-level design software, and every number in it comes from your own inputs or generic teaching defaults — no ARGO aircraft specifications are invented.

Phase 9 (Lessons 56–63) integrates that work into one conceptual aircraft-lab workflow: configuration, aerodynamic integration, propulsion and energy, performance, stability and control, mission and systems, a trade study, and a capstone that produces an engineering summary. Every value is tagged by where it came from (your input, calculated, estimated, modelled, ARGO database, or unavailable). It is still an educational laboratory — not a 6-DOF flight-dynamics solver, not certification-level software — and the ARGO database still has no numeric engineering specifications, so none are invented.