Helical Gears

§1The helix and why it helps

On a spur gear a tooth meets its mate all along its face at one instant — a small impact repeated every tooth, which is the source of gear whine. A helical tooth is angled, so contact begins at one end and sweeps across.

Because the load is picked up and released gradually, and because more than one tooth is always partway through its sweep, helical gears run markedly quieter and can carry more load at higher speed than an equivalent spur pair. The extra overlap that the helix provides — the face contact ratio, added on top of the profile contact ratio the spur page describes — is what smooths the mesh. The single complication is that the angled tooth pushes sideways as well as round, and that axial thrust (§4) has to go somewhere.

Contents

§2Normal and transverse planes

A helical tooth is described in two planes, and keeping them straight is the whole of helical arithmetic: the normal plane (perpendicular to the tooth) and the transverse plane (perpendicular to the axis, the plane you see end-on).

m_t = m_ncos β tan φ_t = tan φ_ncos β d = m_t z = m_n zcos β

The cutter works in the normal plane, so the normal module m_n is the standard tool size; but the pitch diameter is set in the transverse plane, so it uses the transverse module m_t, which is always the larger of the two. Everything the spur page said about pitch circles and ratio still holds — provided the transverse values are used. For the worked pair (m_n = 3 mm, β = 20°) the transverse module is 3/cos 20° = 3.193 mm.

Contents

§3Geometry of a helical pair

With the transverse module in hand, the pair is dimensioned exactly like a spur pair.

Example 1 — a helical pair

Pinion z₁ = 20, gear z₂ = 40, normal module 3 mm, helix angle 20°. Transverse module 3.193 mm, so pitch diameters are 20 × 3.193 = 63.85 mm and 40 × 3.193 = 127.70 mm. Centre distance C = m_n(z₁+z₂)/(2 cos β) = 180/(2 × 0.9397) = 95.78 mm. Note the helix angle gives the designer a free adjustment: nudging β changes the centre distance continuously, so a helical pair can be tuned to an existing housing that no spur tooth count would fit.

Contents

§4Axial thrust

The angled tooth resolves the mesh force into three: the tangential load that does the work, the radial load that separates the shafts, and the axial thrust along the shaft — unique to the helix.

F_a = F_t tan β F_r = F_t tan φ_ncos β F_t = tangential (torque / pitch radius)

Example 2 — thrust from a 2 kN tangential load

With a tangential load F_t = 2000 N and β = 20°, the axial thrust is F_a = 2000 × tan 20° = 728 N — over a third of the working load, pushing straight along the shaft. That thrust must be caught by a thrust bearing or a shoulder, and it is the reason helix angles are usually kept between 15° and 30°: steeper is quieter and smoother but throws ever more load at the bearings. The cure for eliminating it entirely is the double-helical gear (§6).

Contents

§5Equivalent number of teeth

For tooth strength and cutter selection, a helical tooth behaves like a spur tooth on a larger imaginary gear — the equivalent, or virtual, gear formed by the normal section.

z_v = zcos³ β

For the pinion above, z_v = 20/cos³ 20° = 24.1 — so a 20-tooth helical pinion is as strong at the root, and is cut as if it were, a 24-tooth spur pinion. This matters twice: it lets the spur strength methods and Lewis form factors be reused directly, and it pushes the undercut limit down, so a helical pinion can carry fewer actual teeth than a spur one before undercutting — another reason the helix earns its keep in compact drives.

Contents

§6Single, double and crossed

Three arrangements cover most helical work.

Single helical

One helix; simplest and cheapest, but carries the full axial thrust to the bearings.

Double (herringbone)

Two opposite helices on one gear; the thrusts cancel internally, leaving none for the bearings. Used for heavy, high-speed drives.

Crossed helical

Two helical gears on non-parallel, non-intersecting shafts; point contact only, so light duty — a motion drive, not a power one.

The herringbone is the standard answer wherever the thrust of a single helix would be a burden — it keeps the smooth, quiet, high-capacity mesh while returning the thrust to zero, at the cost of a more expensive gear to cut. Crossed helicals, by contrast, trade nearly all load capacity for the freedom to connect skew shafts, a role that otherwise falls to the worm (its own page).

Contents

§7Quick reference

The working core of the page on one card rack.

Planes

m_t = m_n/cos β

d = m_n z/cos β

Forces

F_a = F_t tan β

F_r = F_t tan φ_n/cos β

Strength

z_v = z/cos³ β

Helix angle

15°–30° typical

steeper = smoother, more thrust

Thrust cure

double helical (herringbone)

→ net thrust zero

Contents

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Helical Gears. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to carry the subject from function and assumptions through design evidence, verification and controlled release. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Apply Helical Gears by beginning with the duty, not the component or software command. Convert the key ideas—helical, gears, helix, normal, transverse—into measurable requirements and interfaces. Record operating and non-operating environments, duty cycle, expected life, loads, energy sources, human interaction and reasonably foreseeable abnormal conditions. When a value is not a project requirement or verified supplier datum, identify it as an assumption or illustrative value.

Create a calculation and evidence trail that another competent person can audit. Every input should carry a source, unit, revision and uncertainty or tolerance where relevant. Every model should state its boundary conditions and limitations. Keep nominal capacity separate from design capacity, and keep verification margin separate from an arbitrary safety factor. If a code or standard governs the work, confirm the applicable edition and contractual status rather than copying a number from a secondary summary.

Design for manufacture, assembly, inspection, operation and maintenance at the same time. A technically valid geometry can still fail because it cannot be fixtured, measured, cleaned, guarded, reached or replaced. Review process capability, datum or reference strategy, tolerance accumulation, access, error-proofing and changeover. Where people interact with plant, apply the hierarchy of controls and consult those who will operate, clean, maintain and recover the equipment.

Plan verification before release. Define the characteristic, method, equipment, sample or test condition, acceptance criterion, record and responsible person. Validation then asks a different question: whether the resulting system is effective and suitable in the intended use context. A passed drawing check or analysis does not by itself validate usability, maintainability or production performance.

Step-by-step operating method

Define the duty. Capture the required function, interfaces, operating environment, life, loads and unacceptable outcomes.
Establish the model. Identify governing principles, units, material or process data, assumptions and uncertainty.
Develop alternatives. Compare feasible concepts against performance, manufacturability, safety, maintainability and cost.
Verify the design. Use analysis, test, inspection or demonstration with acceptance criteria defined before execution.
Release and learn. Baseline the design, control changes, retain evidence and feed operating results into the next revision.

Illustrative design review record

Illustrative values only. Build a one-page record with the required function, input sources, assumptions, governing load or process condition, failure consequences, selected concept, verification method and acceptance criterion. Mark every numerical input as project requirement, verified supplier data, measured value, calculation output or assumption. Review the weakest evidence first. If an assumption can change safety, compliance, interchangeability or capacity, it must be resolved before release rather than buried in a calculation note.

Evidence class	Question	Release expectation
Requirement	What must the design do and under which conditions?	Approved and traceable
Input	Where did the load, property, tolerance or process limit come from?	Source, unit and revision recorded
Analysis	Which model and assumptions connect input to result?	Checkable calculation or simulation
Verification	How will conformity be demonstrated?	Method and acceptance criterion agreed
Validation	Will the solution work for intended users and conditions?	Representative use evidence

Common failure modes and recovery actions

1. Watch for

Starting detailed design before interfaces and operating limits are agreed.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Using catalogue or typical values as though they were certified project inputs.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Checking nominal performance while ignoring tolerances, degradation and foreseeable misuse.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Confusing verification of requirements with validation of user need.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Releasing drawings or procedures without configuration, inspection and change controls.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.