Flying Laboratory

Where Aerospace Capability Becomes Evidence

Models earn trust through measurement.

The REAH Flying Laboratory is the physical test platform where engineering assumptions meet heat, vibration, airflow, installation constraints and operational reality. It is being developed to create measured evidence, improve reusable engineering models and establish validation methods that can transfer into customer programmes.

Its purpose is to answer engineering questions that catalogue data and simulation alone cannot resolve: installed thermal behaviour, propulsion interactions, power demand, component substitution and real operating margin.

Rotax-powered gyrocopter installation used as REAH flying-laboratory reference hardware. This is the physical platform; instrumentation integration and validation campaigns remain in development.

Configuration Record — Release 01

The evidence package is tied to a controlled reference configuration so that later measurements can be interpreted and repeated.

Changes to the installed engine, cooling circuit, duct geometry, electrical loads, instrumentation or logging software will create a new configuration revision. Results from different revisions will not be combined without identifying the change.

Proposed Measurement Architecture

Release 01 defines the channel families required to answer the engineering question. Final sensor selection, range and installation approval remain part of the instrumentation gate.

All channels will use a common time base. Calibration reference, engineering units, sample rate, valid range and uncertainty target will be stored with the channel definition rather than left in a separate presentation.

Baseline Test Matrix

The baseline is designed to separate installation effects from modification effects. Actual execution remains subject to aircraft approval, operating limitations, weather and test safety review.

Data Package Structure

Each released dataset will contain four linked records:

1. Configuration — aircraft, propulsion, cooling, electrical and software revision.
2. Channel dictionary — sensor identifier, location, unit, range, sample rate, calibration reference and uncertainty target.
3. Test event log — operating condition, pilot or test marker, environmental context and anomalies.
4. Time-series data — synchronized raw values, quality flags and any derived values with the derivation stated.

Raw measurement, corrected measurement, calculated quantity and simulation output will remain separate fields. A plotted line will never be the only surviving record of a result.

Why This Matters to Customer Programmes

Aircraft programmes routinely depend on assumptions that become visible only after installation:

• published component performance that does not represent installed conditions;
• cooling flow altered by ducts, exits, structure and propeller slipstream;
• electrical and thermal margins reduced by mission equipment;
• locally manufactured or substituted parts that require comparative validation;
• models that remain uncorrelated because representative measurements do not exist;
• suppliers who deliver hardware without transferring the method needed to verify it.

The Flying Laboratory gives REAH a controlled environment for developing the instrumentation, test procedures, correlated models and acceptance logic needed to address those risks.

Why This Platform

The pusher-configuration gyrocopter creates a compact and technically demanding installation. The engine, heat exchangers, cooling exits, structure and propeller flow field interact closely. Low-speed ground operation, climb, high ambient temperature and changing power demand expose precisely the installation effects that simplified component analysis can miss.

The platform is also accessible enough to support repeated instrumentation changes, prototype installation and inspection. That makes it useful for developing methods before transferring them to less accessible UAV and light-aircraft installations.

What the Laboratory Will Enable

1. Baseline characterisation — establish how the unmodified installation behaves across defined ground and flight conditions.
2. Thermal, propulsion and power measurement — capture temperatures, pressures, flow indicators, engine parameters and electrical loads against a common time base.
3. Model correlation — compare measurements with thermal, flow-network and CFD predictions, including discrepancies.
4. Prototype validation — test ducts, cooling arrangements, sensors and other integration hardware comparatively.
5. Component-substitution evidence — define whether an alternative or locally manufactured part meets controlled performance and acceptance criteria.
6. Capability transfer — convert the instrumentation architecture, procedures and analysis into methods that customer teams can retain and repeat.

Evidence Progression

The laboratory advances through explicit evidence gates. Each completed gate creates the foundation for the next.

Evidence Package Release Gates

Evidence Package 01 establishes the test definition. The next releases will add:

1. Integration release — installed channel map, sensor ranges, sample rates, calibration references and configuration photographs;
2. Ground baseline release — reviewed ground-run data, ambient conditions, anomalies and repeatability assessment;
3. Flight baseline release — reviewed flight data within the approved envelope and associated configuration record;
4. Correlation release — measured-to-predicted comparison, uncertainty and model changes;
5. Comparative release — baseline-versus-modified evidence using the same controlled method.

Publishing the definition before results makes the method inspectable and prevents the test from being designed around a preferred conclusion.

The REAH Learning Loop

1. Define the question — state the operational risk and the evidence required to resolve it.
2. Model the system — make assumptions and boundary conditions explicit.
3. Configure the test — install calibrated instrumentation against a controlled aircraft definition.
4. Measure under representative conditions — ground and flight test within the approved operating envelope.
5. Compare evidence with prediction — publish agreement, discrepancy and uncertainty.
6. Improve and transfer — update the model, hardware and repeatable customer method.

From REAH Aircraft to Customer Capability

The value of the laboratory is not limited to one gyrocopter. Each campaign should leave behind reusable capability:

• a better-correlated thermal or airflow model;
• a tested sensor and logging architecture;
• a repeatable ground or flight-test procedure;
• evidence requirements for substituted or locally manufactured components;
• configuration and acceptance records that can be applied to customer aircraft;
• engineers who understand how to repeat the method after REAH leaves.

That is how an internal test platform becomes customer capability rather than an isolated experiment.

Evidence Scope

• Current published evidence covers the physical platform and reference installation; measured ground and flight datasets follow the evidence progression above.
• The hangar image below visualises the planned instrumented configuration.
• Results from this platform strengthen methods and models; customer aircraft retain installation-specific analysis requirements.
• Testing will remain within the aircraft's approved operating envelope and applicable regulations.

Visualisation of the planned instrumented flying-laboratory configuration.