What is a Test Cell Correlation?

When an engine comes off a test cell, the numbers it produces — thrust, fuel flow, shaft horsepower, exhaust gas temperature — are only as trustworthy as the cell that measured them. That raises an obvious question. There are OEM test facilities and there are third-party MRO shops, all of them running engines and all of them generating data. So how does anyone actually know a given cell's numbers are good?

That's the job of a test cell correlation. A correlation provides evidence that the data coming out of one facility is traceable to a known-good facility — usually an engine OEM, or a facility the OEM has already correlated. It's the difference between a number you hope is right and a number you can defend.

We've covered test cells and the role they play in verifying engine performance before. This post goes a step further into the correlation itself: what it is, where the requirement comes from, and how the process actually runs.

Why a Correlation Matters

Think of it this way. If two facilities test the same engine and get meaningfully different results, at least one of them is wrong — and you can't tell which without a reference point. A correlation establishes that reference point. It ties your facility back to a baseline that's already trusted, so the data your cell produces carries the same weight as the data from the facility you correlated against.

For an MRO, this isn't a paperwork exercise. It's what lets your test results stand up — to your customers, to the operators flying the engines you service, and to the FAA. A cell without a current correlation is a cell whose numbers come with an asterisk.

Where the Requirement Comes From

The regulatory anchor is 14 CFR §43.2(a), which addresses records of overhaul and rebuilding. In plain terms, the rule requires that an article has been tested in accordance with approved standards and technical data — or with current standards and technical data acceptable to the Administrator — developed and documented by the holder of the type certificate, supplemental type certificate, or a Part 21 approval.

The phrase that matters there is "approved standards." Testing in an approved facility — one known to produce accurate, repeatable data — is how you satisfy that. And the way a facility becomes known to produce accurate, repeatable data is by being compared against a baseline. The baseline is an OEM facility, or one the OEM has correlated; your facility, the reference facility, has to be traceable back to it.

The FAA also publishes guidance specifically on this in AC 43-207, which walks through correlation and operation procedures for test cells used in the in-service acceptance testing of turbofan and turbojet engines. If you've searched this topic, you've probably seen that advisory circular — it's the FAA's own roadmap for how this is expected to be done. You can find it and other relevant material in our reference documents.

How a Correlation Actually Works

At its core, a correlation is a controlled comparison. The same engine — or a dedicated correlation engine with well-understood behavior — is run in the baseline facility and in your facility, and the results are compared across the operating range. the same principle applies to APU test cells, though the parameters differ.

What you're looking for is agreement. Does your cell produce the same shaft horsepower and torque at the same engine speed? Do the pressures line up? Are the corrected performance numbers landing where the baseline says they should? When the two facilities track each other within accepted limits across the range, you have a successful correlation. When they don't, the gap tells you something in your facility — a measurement system, a piece of instrumentation, the way data is being corrected — needs attention before the cell can be trusted.

That's the real value of the exercise. A correlation doesn't just produce a certificate. It surfaces the quiet problems in a test cell that would otherwise go unnoticed until they showed up as bad data.

The Measurement Systems That Drive the Result

Test cells are complex, and so are the subsystems feeding them. A few of the big contributors to whether a correlation goes well:

Data reduction system. This is a primary one. The data reduction system takes the raw measurements and corrects them to standard-day conditions so results are comparable regardless of the weather outside. If this system is off, everything downstream is off with it.

Pressures. Fuel flow and engine pressure measurements matter both for the correlation itself and as troubleshooting tools — they help you understand the behavior of the facility and the engine when something doesn't look right.

Engine speed. A straightforward but telling check. Is your facility reading the same engine speed as the reference facility, and producing the same shaft horsepower and torque at that speed? If it is, you're well on your way to a clean correlation.

There's more to it than these three — you can read more on our facility measurement systems page — but they're a good illustration of why correlation is a measurement-systems validation exercise at heart. The test is the reason; the measurement systems are what's actually being validated.

Where Prime Propulsion Fits

A correlation is a regulatory requirement, a measurement-systems validation, and a fair amount of coordination — and it's a lot more straightforward with someone who's done it before guiding the process.

Our in-house DER has experience on both sides of this: as an FAA employee and as a consultant guiding companies through correlations to a successful approval. We help facilities scope the effort, run the comparison the right way, work through the measurement-system issues that surface, and get to an approval without the false starts.

If you have questions about correlating your test cell, or you're not sure where your facility stands, contact us — we're happy to help. You can also learn more about our test cell correlation services.

Our DER-led team specializes in PMA, STC, Test Cell Correlations, and Repair Specification support.