Conveyors worked example
Carrier Spacing Speed Check at 99% carrier loading efficiency: a worked example
This scenario runs the carrier spacing speed check calculation on the strong side: 99% carrier loading efficiency, with every other input held at its documented default. a conveyor system designer needs to validate carrier spacing before fixing chain speed or carrier count
The inputs for this scenario
- Target loaded carriers per hour: 420 carriers / hr (unchanged)
- Carrier center-to-center spacing: 24 in (unchanged)
- Carrier loading efficiency: 99 % (raised for this scenario; the documented default is 95)
Working through the calculation
- Applying the documented formula (Required carrier rate = target loaded carriers รท loading efficiency) to the inputs above produces each figure below.
- At this operating point the engine returns 14.14 ft / min for required carrier conveyor speed, the number this scenario is built around.
- At this operating point the engine returns 424 carriers / hr for efficiency-adjusted carrier rate.
- At this operating point the engine returns 24 in for carrier pitch.
- At this operating point the engine returns 99 % for loading efficiency.
How this compares with the baseline
- Against the tool's baseline example, where carrier loading efficiency sits at 95% and the headline result is 14.74 ft / min, this scenario comes in 4.04% below the baseline at 14.14 ft / min.
- Use it when commissioning an overhead or power-and-free line, rebalancing takt, or checking whether a requested output rate is physically achievable at the current carrier pitch. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Required carrier conveyor speed: 14.14 ft / min (headline result)
- Efficiency-adjusted carrier rate: 424 carriers / hr
- Carrier pitch: 24 in
- Loading efficiency: 99 %
Run it with your numbers
- Every input above is editable in the live Carrier Spacing Speed Check calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.