How cruise control closes the loop
A driver’s foot does more than press the accelerator: it continually corrects the car’s speed. If the car slows on a rise, the driver presses harder; if it gathers speed on a descent, the driver eases off. Ralph Teetor’s 1948 invention handed that repeating task to a mechanism.
The driver selects a pace, and the system compares the car’s actual speed with that target. When speed drops, it opens the throttle—the valve that controls how much air and fuel the engine can use. When speed rises, it reduces the throttle. This is a feedback loop: the system measures the result of its action and adjusts again, rather than holding the accelerator in one fixed position.
A mechanical answer to a human annoyance
Teetor had been blind since age five. The commonly told origin story connects his idea to the difficulty of riding with a driver who varied speed while talking. The practical problem was not that a person could not read a speedometer, but that keeping a steady pace required constant small corrections—and could make a long drive tiring.
Early cruise-control designs used mechanical speed-sensing parts and connections to the throttle; later systems used other ways to move it. The essential idea remained the same: let the car’s changing speed, not a driver’s ankle, trigger the correction.
What the system does—and does not do
Cruise control can keep a chosen pace on suitable roads, but it does not steer or judge traffic. In many systems, braking cancels the setting, leaving the driver responsible for slowing down and responding to hazards. On a steep hill, the car may also gain or lose speed because the system’s ability to adjust engine power has limits.
Teetor’s contribution was therefore not simply a device that held the accelerator down. It was a way to make the car continually adjust its own power—so the driver could devote less attention to preserving one number on the speedometer.
