Phugoid Mode

Phugoid mode is a slow longitudinal aircraft oscillation in which airspeed and altitude trade energy. The aircraft may climb and slow, then descend and accelerate, while angle of attack changes much less than it does in the short-period mode.

In a simplified second-order screen, the phugoid is often described by natural frequency and damping ratio:

This model is useful for first-pass interpretation, but the real response depends on trim condition, thrust, drag, flight-path angle, mass, center of gravity, control-law mode and atmospheric disturbances.

Engineering Role

Phugoid behavior matters for speed stability, altitude hold, autopilot tuning, long-period pilot workload, flight-test planning, energy management and model validation. Because the mode is slow, a short test window can miss the real damping or confuse the response with turbulence, thrust changes or pilot correction.

The phugoid is also tied to aircraft performance. Drag, thrust setting, climb gradient, Mach number, configuration and speed schedule can change the apparent damping. A controller that tightly regulates pitch attitude may still allow slow speed-altitude cycling if the energy loop is not properly damped.

Worked Example: Long-Period Modal Screen

A simplified longitudinal model gives the phugoid characteristic equation:

Compare with:

The natural frequency is:

The damping ratio is:

The damped natural frequency is:

The damped period is:

Approximate 2 percent settling time is:

Now consider a speed-hold control-law change that keeps the same natural frequency but increases damping ratio to:

The damped frequency becomes:

The period is:

The approximate settling time improves to:

Engineering comment: the control-law change improves damping without materially changing the long period. That may help altitude and speed capture, but release evidence still needs actuator limits, thrust response, sensor filtering, air-data validity, turbulence sensitivity, pilot mode awareness and degraded-mode behavior.

Distinction from Short-Period Motion

Phugoid mode is different from the short-period mode. The short-period mode is fast and dominated by angle of attack, pitch rate and pitching moment. The phugoid is slower and dominated by energy exchange between speed and altitude.

The distinction matters in flight test. A short-period maneuver may settle within a few seconds, while a phugoid assessment may require multiple tens of seconds or several minutes. Filtering, pilot correction, atmospheric disturbance and thrust variation can easily distort the long-period estimate.

What Changes Phugoid Behavior

Phugoid frequency, damping and period depend on:

• trim airspeed, altitude, weight, center of gravity and configuration;
• drag polar, lift curve, thrust setting and propulsion response;
• static longitudinal stability and elevator control effectiveness;
• Mach number, dynamic pressure and speed schedule;
• flight-path angle, climb or descent condition and energy state;
• autopilot speed hold, altitude hold, pitch-attitude hold and auto-throttle behavior;
• air-data sensor validity, filtering, latency and estimator drift;
• turbulence, wind gradients, icing, stores, damage and pilot input.

Because the phugoid is slow, one visually smooth speed or altitude trace is not enough. A defensible interpretation should include test duration, initial disturbance, control-law mode, atmospheric condition, sensor filtering and uncertainty.

Validation and Common Mistakes

Phugoid mode can be identified from state-space eigenvalues, pitch or speed perturbations, flight-test decay traces, system-identification models, simulation sweeps, frequency-response tests or autopilot capture transients. A defensible record states flight condition, configuration, mass properties, control-law mode, thrust setting, sensor filtering, atmospheric condition, sign convention and uncertainty.

Common mistakes include:

• treating a short test segment as proof of phugoid damping;
• confusing phugoid behavior with short-period pitch response;
• reporting damping ratio without the flight condition and control-law mode;
• ignoring thrust response, drag modeling and speed schedule;
• using air-data measurements without checking filtering, lag or calibration;
• accepting altitude-hold performance without checking speed excursions;
• validating nominal behavior while leaving degraded air-data or auto-throttle modes untested.