ForHosting KIT · Developer Utilities

Shaft critical speed calculator from static deflection

This shaft critical speed calculator estimates the first lateral whirling speed from the shaft's measured or calculated static deflection under self-weight or an effective applied load.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter a positive deflection in metres, millimetres, or inches to obtain critical speed in revolutions per minute, frequency in hertz, and angular speed in radians per second. The calculation uses the established static-deflection relationship between gravitational acceleration and displacement. It is intended for rapid engineering screening, preliminary design comparisons, and independent checks before a more detailed rotor-dynamics model is prepared.

Use static deflection to estimate the first whirling speed

A flexible rotating shaft has lateral natural frequencies, and resonance can occur when rotational excitation approaches one of them. For a system dominated by one lateral mode, its first natural frequency can be estimated from the static displacement produced by gravity or an equivalent effective load. This calculator applies ω₁ = √(g/δ), where ω₁ is angular frequency in radians per second, g is standard gravitational acceleration at 9.80665 metres per second squared, and δ is positive static deflection in metres. It then converts angular frequency to hertz by dividing by 2π and to revolutions per minute by multiplying hertz by 60. The relationship explains an important design trend: greater deflection means a lower estimated critical speed, while a stiffer system with less deflection has a higher estimate. Because speed changes with the inverse square root of deflection, reducing deflection by a factor of four approximately doubles critical speed. The result represents an undamped first-mode estimate, not a recommended continuous operating speed or proof that resonance will be harmless.

Choose a deflection that represents the real shaft system

The formula is simple, but the quality of its result depends on the deflection supplied. Use deflection calculated or measured for the actual shaft span, bearing locations, stiffness, rotor masses, and relevant loading distribution. A deflection value for the bare shaft may be unsuitable when a heavy disk, coupling, impeller, or pulley dominates the system. Similarly, a beam calculation with the wrong end conditions can produce a convincing number that describes a different machine. Keep the displacement direction and definition consistent: enter the magnitude of lateral static displacement associated with the effective gravitational or applied load, not shaft elongation, torsional twist, bearing clearance, runout, or vibration amplitude while operating. The calculator accepts metres, millimetres, and inches and converts them internally to metres, which avoids relying on memorized unit-specific constants. If several concentrated masses or a distributed mass shape contribute significantly, a Rayleigh calculation using their individual deflections and weights, a finite-element rotor model, or measured modal testing is more appropriate than compressing the system into one displacement.

Interpret the estimate and set a safe next step

Treat the returned rpm as a screening estimate of the first critical speed. Real rotating assemblies include damping, bearing flexibility, support motion, unbalance, coupling stiffness, fluid forces, gyroscopic effects, manufacturing tolerances, and temperature-dependent properties. Those effects can shift the resonance, change its amplitude, split forward and backward whirl modes, or introduce additional critical speeds. Do not use the computed value alone as an operating limit or as evidence that a machine can safely pass through resonance. Compare it with the full operating-speed range, including startup, shutdown, overspeed, and variable-speed control regions, then apply the design standard, separation margin, and uncertainty policy relevant to the equipment. If normal operation approaches the estimate, escalate to a rotor-dynamics analysis and obtain accurate bearing and mass data. A measured coast-up or coast-down vibration study can help confirm actual resonances on existing equipment. Repeatable API calculations cost $0.002 each and can support preliminary option studies, but engineering approval should incorporate loads, stresses, fatigue, stability, and transient response as well as frequency separation.

Screen a preliminary shaft layout

Convert a beam-model deflection into an approximate first critical speed before investing in a detailed rotor model.

Check a measured sag value

Use a known static lateral displacement to compare the estimated resonance with a machine's planned speed range.

Compare stiffness alternatives

Evaluate how changes in bearing span, shaft diameter, or rotor support that alter deflection affect the estimated critical speed.

What equation does the calculator use?

It uses omega equals the square root of standard gravity divided by static deflection, then converts the result to hertz and rpm.

Which deflection should I enter?

Enter the positive lateral static deflection for the real support condition and effective self-weight or applied load represented by the estimate.

Can I enter shaft runout or operating vibration amplitude?

No. Runout and operating vibration amplitude are not substitutes for the static deflection required by this method.

Does this result define a safe operating speed?

No. It is a first-mode screening estimate. Safe operation requires suitable separation margins and assessment of damping, bearings, excitation, stresses, and transient behavior.

What does an API calculation cost?

Each API calculation costs $0.002. The deterministic solver performs no network calls and gives repeatable results for identical inputs.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/eng/shaft-critical-speed

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/eng/shaft-critical-speed \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"static_deflection":2.5}'
{
  "static_deflection": 2.5
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "eng.shaft_critical_speed",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →