A centrifugal pump does not stop when the system drives it beyond the last published point on the manufacturer’s curve. The hydraulic system can continue moving the operating point to higher flow and lower head, but the engineer has no validated pump-performance data in that region. Pump selection and operating point troubleshooting must determine whether the apparent runout is real, a curve-entry problem, or the result of a low-resistance operating case that was never reviewed.
The diagnostic objective is to restore a traceable operating point inside the manufacturer’s stated range—not to force the model to converge by extending unsupported data.
What out-of-curve operation means
Runout is the maximum published flow on a centrifugal pump’s Q–H curve. Out-of-curve operation occurs when the calculated duty moves beyond that limit.
The operating point is set by the intersection of the pump curve and system curve. If system resistance falls, the intersection moves to the right. Once it moves beyond the published endpoint, head, efficiency, power, and NPSHR behavior are no longer supported by the available manufacturer data.
Figure 1. Out-of-curve operation: reduced system resistance pushes the duty point beyond the pump's published runout flow.
FluidFlow can flag this condition when the pump entry includes the correct maximum flow limit. The warning simply indicates the calculated duty is outside the configured limits and needs engineering review.
Figure 2. FluidFlow generates a warning when the calculated duty flow exceeds the maximum flow limit specified for the pump.
⚠️ Warning, not intervention: The configured minimum and maximum flow values generate warnings when the calculated duty falls outside those limits. They are not hard constraints — they simply flag that the duty point is outside the defined range. They do not prevent the solver from finding a duty flow beyond those limits. FluidFlow identifies the out-of-range condition; the user remains responsible for investigating it and implementing the appropriate preventive or corrective actions.
Start by validating the pump curve entry
Before changing the system model, confirm that the installed pump data is correctly represented.
The capacity curve is mandatory. Efficiency and NPSHR curves are optional but recommended because they allow the calculated duty to be checked against power, efficiency, and suction requirements. Verify flow and head units before entering data; a unit mismatch can produce a smooth-looking but incorrect curve.
Check the manufacturer’s minimum and maximum flow limits. These should reflect the published operating range rather than arbitrary values selected only to remove warnings.
Figure 3. Adding a zero-head anchor point beyond the maximum flow keeps the fitted Q–H curve from inflecting upward past the endpoint.
FluidFlow fits pump data with a polynomial. The Q–H dataset requires an anchor point beyond the defined maximum flow with zero head to prevent the fitted curve from turning upward and creating a false second operating point. The efficiency curve requires an origin anchor at zero flow and zero efficiency. These mathematical anchors are not operating data and must not be interpreted as an extended vendor curve.
Also verify the reference speed and impeller diameter. If the model applies a different speed or diameter, confirm that the database entry contains the correct reference and allowable limits.
Validate the modeled operating conditions
A pump warning can be a symptom of incorrect boundaries or resistance data. Review the calculation objective, system description, and each operating case before diagnosing the pump.
Check that inlet and outlet boundaries represent known pressure or flow conditions without duplicate constraints. Confirm elevations use one datum. Verify pipe inside diameters, lengths, roughness, scaling, valve positions, equipment pressure-drop data, and active destinations.
After calculation, review the status, flow-direction arrows, highlighted components, and Messages tab before accepting the result. Then review flow, pressure, pressure drop, and temperature as the first numerical screen. FluidFlow provides these results; the engineer must decide whether they reproduce the intended lineup and observed plant condition.
Three common causes of out-of-curve pump operation
1. The pump is oversized for the system
A pump with more head or capacity than the system requires can settle toward the right-hand side of its curve. When resistance falls further, the operating point may cross the published runout limit.
2. A lower-resistance destination is active
A pump selected for a high-elevation or high-pressure route may operate correctly in that lineup. If a lower-resistance destination is opened or the higher-resistance route is isolated, the operating point can move sharply to higher flow.
3. A parallel pump trips
When one pump in a parallel arrangement stops, the remaining pump can pick up additional system flow. The surviving pump’s duty moves along its own curve and can approach or exceed runout. FluidFlow can compare steady-state configurations before and after the lineup change; the trip transient itself is outside its steady-state scope.
How to investigate an out-of-curve warning
Confirm the correct pump curve is applied. Match manufacturer, model, impeller diameter, speed, and fluid basis.
Validate curve units and limits. Check the entered Q–H points, minimum flow, maximum flow, efficiency, and NPSHR data.
Check the polynomial anchors. Remove any false operating point caused by an unstable curve fit.
Validate operating scenario credibility. Confirm the modeled configuration is operationally realistic.
Inspect system curve sensitivity. Identify which components or boundary change move the pump duty point to the right.
Review power and NPSH. An out-of-curve condition must not be assessed on flow and head alone. Compare the calculated duty with the power and NPSHR information supported by the manufacturer data.
Run the full operating envelope. Include normal, minimum resistance, filling, alternate destinations, and parallel-pump stop / trip cases where credible.
Use affinity law cases within their limits
FluidFlow can apply centrifugal pump affinity law scaling for speed and impeller diameter changes. Flow scales directly, head with the square, and power with the cube of the speed or diameter ratio under the similarity assumption.
Figure 4. Pump Affinity Laws.
⚠️. Pump affinity laws assume geometric similarity between the reference pump and the modified configuration. In practice, changes to impeller diameter should typically be limited to approximately 10–20% of the original reference value to ensure geometric similarity.
Applying the affinity laws beyond the 10–20% range may reduce the accuracy of the calculated results, as the resulting pump configuration may no longer be geometrically similar to the original pump.
Figure 5. FluidFlow applies the affinity laws based on the operating speed and impeller size information defined in the booster database.
Post Modeling Analysis
After the steady-state model identifies an out-of-curve duty, investigate field-instrument accuracy, pump condition, motor and control behavior, and operating events that may not be represented in the model.
Pump trips, rapid valve movements, and other short-duration events may temporarily drive the pump outside its published operating range. FluidFlow can compare the steady-state conditions before or after such events, but determining their dynamic effects requires a separate transient-analysis approach.
Use the model to quantify the hydraulic effect of proposed changes, then complete the necessary field checks, mechanical and electrical assessments, vendor review, and transient evaluation. Final corrective actions should be based on the combined modeling results and post-modeling evidence, not the calculated operating point alone.
FAQ
Can a pump operate beyond the end of its curve?
The system can drive the pump beyond the last published point, but no validated manufacturer performance data exists there. Treat the result as out of range, verify the curve entry and system case, and do not extrapolate head, power, efficiency, or NPSHR as if they were guaranteed.
Why does a lower-resistance route cause runout?
Lower system resistance moves the system curve downward. Its intersection with the pump Q–H curve shifts to higher flow and lower head. If that intersection moves past the manufacturer’s maximum published flow, the pump is out of curve.
What should be checked first in FluidFlow?
Confirm the calculation converged, check the Message tab for warnings, and validate the pump database entry: units, Q–H points, maximum flow, speed, impeller diameter, and anchor point. Then verify that the active boundaries and resistance data match the operating lineup being investigated.
Can an anchor point be used as a runout point?
No. The zero-head anchor beyond maximum flow controls the polynomial fit; it is not a tested operating point. Runout remains the manufacturer’s published maximum-flow limit.
Diagnose the intersection, not only the warning
Out-of-curve performance is the result of a pump curve and system curve that no longer intersect inside the published operating range. Validate the data, reconstruct the actual lineup, identify the resistance change, and compare the full hydraulic envelope.
See your out-of-curve warnings before they cost you a pump
Run your own system model in FluidFlow and catch runout, curve-entry errors, and low-resistance operating cases before they turn into a field failure.