A Pump Cable Can Pass Its Ampacity Check and Still Fail the One Moment That Actually Matters

Power cables running to a submersible pump, a remote blower, or any motor sitting a long distance from its MCC at an ETP or STP get sized, overwhelmingly, against one check: ampacity, the maximum current the conductor can carry continuously without overheating its insulation. That check is genuinely necessary and most cable sizing software or tables handle it correctly. It is not, however, the check that determines whether a long cable run will let the motor start reliably, because starting draws a current several times higher than running current for a few seconds, and the voltage drop during that brief spike is a completely separate calculation that a pure ampacity check never performs.

Two different currents, two different checks

Ampacity is a thermal limit, driven by the conductor's steady, continuous full-load current, the number the motor draws hour after hour during normal operation. Starting current is a different animal entirely: an induction motor at the moment of start behaves electrically like a transformer with a shorted secondary, drawing what is commonly called inrush current, often six to eight times the running full-load current, for the brief period before the rotor accelerates to speed. Voltage drop across a cable scales with current, so that same cable, sized perfectly adequate for the steady running current it carries all day, can see a dramatically larger voltage drop during the few seconds of starting, precisely because starting current is so much higher than the number the ampacity check was built around.

Why a cable that passes on paper can still fail to start the motor

A cable run long enough that its running-current voltage drop sits comfortably within an acceptable margin, commonly five percent or less at full load, can still produce a starting voltage drop well into double digits once the much higher inrush current is run through the same resistance. A motor starting against that much lower terminal voltage develops reduced starting torque, because torque falls off faster than voltage as voltage sags, and a pump load that needs real torque to overcome static head at the moment of start can simply fail to accelerate to full speed, stalling at a fraction of rated speed while still drawing near-locked-rotor current, a condition that is hard on the motor winding and can trip protection or, worse, go undetected long enough to cause thermal damage before anything trips at all.

None of this shows up in the ampacity check, because ampacity was never asking about starting conditions in the first place. A motor controller, whether a simple direct-on-line starter or something more sophisticated, is only able to start the motor reliably if the supply circuit, cable included, does not let starting current collapse the terminal voltage below what the motor needs to develop adequate starting torque, and that is a condition the cable's ampacity rating says nothing about one way or the other.

This is the same shape of mistake we described in the piece on L1 tender evaluation: a check that is correctly performed against the number everyone defaults to checking can leave an entirely different, and in this case more consequential, number unexamined, because the two were never built to be reconciled by the same process. There, the checked number was acquisition price while lifecycle cost went unweighted. Here, it is running-current ampacity while starting-current voltage drop goes uncalculated, and a cable that is entirely correct by the first standard can still be the wrong cable by the second.

Picture a remote wet well pump at the far end of a long underground cable run from the main MCC, sized by a contractor using a standard ampacity table matched to the motor's running current, a calculation that checks out cleanly and gets approved. At commissioning, or more often months later as pump wear or a slightly higher static head raises the torque the motor actually needs to start against, the pump begins intermittently failing to start, tripping on overcurrent protection, or taking noticeably longer than expected to reach speed. The symptom reads like a motor or pump mechanical problem, and it often gets chased as one, because nobody goes back to recheck a cable that already passed its sizing calculation. The actual cause, a starting voltage drop that was never calculated separately from the running-current check that did pass, sits upstream of every component anyone is actually looking at.

The diagnosis usually gets expensive before it gets correct. A pump pulled for inspection, a motor sent out for winding checks, a vendor called in to recommission a unit that was never actually faulty, all of it billed against a maintenance budget as if the equipment were the problem, while the cable that was the actual cause sits buried in the ground the entire time, untested, because nothing about its ampacity rating ever looked wrong. The eventual fix, once someone finally calculates starting voltage drop and finds it well outside an acceptable margin, is often cheaper than the round of equipment troubleshooting that preceded it, which makes the sequencing exactly backwards: the five-minute calculation that would have caught the problem gets run last, after everything more expensive has already been tried.

What checking the real condition actually requires

The fix is a second, explicit voltage drop calculation run at starting current rather than running current, using the motor's actual locked-rotor or starting current multiplier, not assumed equal to running current, especially on any cable run long enough that running-current drop is already a meaningful fraction of the allowable margin. Pump and cable manufacturers commonly publish sizing charts and tools that already do this calculation; the gap at most sites is not a missing method but a sizing exercise that stopped at the ampacity table without taking the second step. Where an existing long run is found to have excessive starting drop, remedies range from upsizing the cable to using a reduced-voltage or soft starter that limits inrush current in the first place, each with its own cost trade-off worth weighing against the alternative of chasing phantom pump problems indefinitely.

If your plant has long cable runs to remote pumps or motors that were only ever checked against running-current ampacity, that starting-current calculation is worth running with Spans' electrical engineering team before an intermittent starting failure gets chased as a mechanical problem it was never actually caused by.