Article

External Aerodynamics Is the Easy Part: Avoiding the Simulation-on-Simulation Trap

June 12, 2026

The newest design pipelines optimise shape with machine-learning surrogates trained on CFD: simulations built on simulations. The visible results are impressive. But the difference between a great design and a great programme lies below the waterline, in a century of flight and test knowledge the industry has already paid for. The examples here come from aerospace; the iceberg belongs to every complex engineered system.

A familiar pattern

You have probably seen the demonstration. A gleaming airframe turns on the screen, a GPU solver or neural surrogate hums in the background, and an optimiser explores “millions of designs”. Drag falls, lift-to-drag climbs, and a design loop that once took weeks now takes minutes. It is impressive work.

Look closely, though, at what is being optimised: external aerodynamics, structures and shape, judged by a model that is often trained on another model. What is not on screen is where the fuel goes, how the engine breathes at 45,000 ft on a cold day, how the environmental control system threads its high-pressure ducts through the structure, or what a wing at gauge thickness does when the air starts to push back. External aerodynamics is the most automatable part of the job precisely because it is the most mature and self-contained. That makes it the right place to start, but never, on its own, the reason a programme succeeds.

Simulation on simulation

The real problem is one of knowledge. A RANS CFD code, itself a model, generates a database; a surrogate is fitted to that database; and an optimiser pushes the surrogate into regions where it is extrapolating. Each layer inherits the blind spots of the one beneath it and adds a few of its own.

Chart showing model-form error and uncertainty growing across generations of models: wind tunnel, validated CFD, reduced-order model, ML surrogate, optimizer-driven surrogate, final design
Fig. 1 Each modelling layer inherits the blind spots of the layer beneath it and adds its own. An optimiser will, by construction, exploit exactly the regions where the surrogate is most wrong. Values are notional: in an unanchored pipeline, nobody knows the real numbers.

An optimiser is an adversary, not a colleague. It seeks out the places where the surrogate’s error is largest, because that is where the apparently free performance hides, and so its answer is optimal mainly with respect to the error. Experienced design houses use RANS too, but inside a validation pyramid anchored by wind-tunnel and flight-test data. When the only ground truth in the loop is another simulation, “validated” quietly becomes “converged”.

When the only ground truth in the loop is another simulation, “validated” quietly becomes “converged”.

The iceberg below the render

Even a perfect external optimisation is a minority share of the engineering. The rendering floats on an iceberg of work that decides whether the product flies, keeps flying and can be built at rate, and every piece of it is a solved problem somewhere in the industry. Swap the airframe for a turbine, a car, a ship or a medical device, and the iceberg barely changes shape.

Iceberg diagram: external aerodynamics, structural analysis, and optimization above the waterline; systems integration including flight deck, avionics, and environmental control systems, propulsion-airframe coupling, aeroelasticity, sub-component analysis, manufacturability, certification and change-approval processes, program success, a century of flight test lessons, and hundreds of other considerations below it
Fig. 2 The design iceberg. The visible disciplines are the most automatable in the chain; the depth below the waterline is what turns a design into a programme.

Below the waterline sits systems integration: fuel volume, landing gear, flight-deck effects, avionics cooling, and the environmental control system with its ducts and manifolds at wildly different temperatures, its complex valves and its stress concentrations where ducts pass through structure. There is propulsion–airframe coupling, from inlet distortion at high angle of attack to exhaust interactions and engine-bay heat, failure modes discovered in test cells rather than drag runs. There is aeroelasticity: the CAD surface is rigid, the built wing is not, and flutter, control reversal and divergence all depend on stiffness, mass and temperature. And there are handling qualities, because a drag-minimal shape can have an unacceptable pitch break or a deep stall, judged against specifications written in flight test.

Deeper still are the custom analyses of individual parts, the wing-root fitting, the fasteners around a cut-out, the bracket that changes a load path three frames away, each examined because each has mattered before. There is manufacturability: can the surface be tooled, the spar laid up, and does the “optimal” panel cost ten times the drag it saves? There are the processes of certification, change approval and configuration traceability that keep fleets safe for decades; the business realities of weight, cost, schedule and dispatch reliability that decide whether a programme succeeds; and hundreds of further concerns, from lightning and bird strike to fuel slosh and crashworthiness, each with its own library of hard-won lessons.

Where vehicles actually fail: altitude and temperature

Vehicles are certified, and lost, at the edges of the envelope, not at the cruise point where every CFD render lives. Altitude and temperature move almost every margin at once, and decades of flight and experimental testing have already mapped what an external-flow pipeline cannot see. Engine relight limits were found by deliberately flaming out engines in flight. Icing reshapes leading edges into geometry no optimiser ever evaluated, and takes probes and vanes with it. A design that closes on a standard day can fail to climb off a 45 °C runway at altitude. And seals, lubricants, batteries and mismatched materials are qualified from −55 °C to +70 °C because each of those limits was once discovered the hard way.

A century of lessons already paid for

Each new generation of engineers rediscovers configurations that long-established design houses recognise at a glance: forward-swept wings, channel and ducted layouts, ultra-high-aspect-ratio wings. None of them is forbidden; several have matured into successful aircraft, and a team with fresh tools may be the one that finally makes a shelved idea work. But only if it knows why the idea was shelved.

Those lessons are written down, though not all of them in public. The fundamentals live in the open literature: NACA and NASA reports, AGARD volumes, accident dockets. The deepest layers, flight-test campaigns, qualification histories and design manuals refined over decades, are rightly protected as intellectual property and often controlled under export regulations such as ITAR. That protection is a measure of how valuable the knowledge is, and it is exactly why the engineers who carry it are such an asset. (A related essay: “The Flaw in Stating Teams Are Using Outdated Tools”, on why tools that look dated often embody validated physics.)

What credible looks like

None of this is an argument against fast, surrogate-driven exploration. It is valuable early on, for trade studies, and as a partner to experiment. The credible version simply keeps its feet on the ground. It anchors every generation of model in experiment, because a surrogate corrected by a few experimental points beats one trained on an ocean of unvalidated CFD, the philosophy behind training PINNs on wind-tunnel data. It carries uncertainty rather than single numbers, keeps the search inside trusted regions and treats excursions as test requirements rather than results. It optimises the system rather than the skin: a 2% drag gain that costs 8% of the fuel volume, or routes a bleed duct through a stress hot spot, is no gain at all. It treats manufacturability, certification and configuration management as design inputs rather than paperwork for later. It studies the public literature and earns the rest through experience, partnerships and test programmes of its own. And it builds and breaks hardware early, in the wind tunnel, on the iron bird and with sub-scale demonstrators, because that is where a simulation chain is caught out.

A healthy question for any workflow

“When did our toolchain last disagree with a physical test, and what did we change because of it?” A team with a ready answer is a team whose predictions can be trusted.

Conclusion

External aerodynamics, structures and optimisation are the photogenic tenth of an engineered product. The other nine-tenths is where programmes succeed, encoded in a century of test and field experience: the fundamentals in the open literature, the deepest layers protected as intellectual property and under export controls, and all of it carried by established organisations and the engineers they trained. The same holds for turbines, vehicles and ships. No one has to choose between speed and depth. The depth has already been paid for, and the door to it is the people who hold it. Pair a modern toolchain with a century of inherited judgement and you get something neither could deliver alone.

Speed is a feature. Validation is the product.