Escape Velocity

The question this escape-speed model answers

The page answers a specific textbook question: what initial speed at the surface follows from the classical spherical-body relation when the body mass and radius are supplied? It treats the body as a Newtonian gravitating source and the starting point as its surface. The handler does not determine whether a vehicle can reach that speed, whether the body has an atmosphere, or how a trajectory unfolds after departure.

The word velocity is common in the name, but the returned quantity is a nonnegative speed magnitude. Direction is not entered, and no launch angle or position vector is modeled. The result is the threshold in the ideal energy picture, not a prediction of a real launch event. Keeping that distinction visible prevents a simple formula from becoming a mission-planning claim.

• Inputs are mass and surface radius.
• Output is classical speed magnitude.
• The body is spherical in the model.
• Scope ends before launch and mission planning.

The energy interpretation

In the classical picture, an object at a body's surface has gravitational potential energy relative to a chosen zero at infinite distance. An initial kinetic energy can exactly offset that binding energy when the object reaches infinite distance with zero residual speed. Solving that balance produces v equal to the square root of 2 G M divided by r. The calculator evaluates the solved relation rather than showing a time-dependent path.

This interpretation assumes that only the central body's gravitational field matters and that the object begins at the stated surface radius. It does not include energy lost to drag, energy supplied by engines over time, or gravitational effects from other bodies. Those omitted terms are not accidental. They define the idealized textbook boundary of the result.

• Escape speed comes from an ideal energy balance.
• Potential energy is referenced to infinity.
• The object reaches infinity with zero ideal residual speed.
• No time history is integrated.

Mass increases the required speed

Central-body mass M appears inside the square root in the numerator. Holding radius fixed, multiplying mass by four multiplies escape speed by two. Doubling mass increases speed by the square root of two, not by two. This scaling reflects the strength of the central gravitational field in the ideal formula and is useful for comparing hypothetical spherical bodies.

The mass field is bounded from 1 kg through 1e30 kg. A positive minimum avoids a zero-source special case and follows the requested central-body interpretation. The range is a computational contract, not a catalog of physically spherical objects. The handler does not infer density, composition, rotation, or whether the body can exist in the assumed form.

• Mass appears under a square root.
• Four times mass gives twice the speed.
• The mass input is strictly positive.
• Body composition is not modeled.

Radius reduces the required speed

Radius r appears in the denominator under the square root. Holding mass fixed, quadrupling radius halves the classical surface escape speed. A larger surface radius places the starting point farther from the body's center and therefore reduces the ideal gravitational binding at that starting point. The result is sensitive to the geometric definition of radius, which must be the distance from the center to the modeled surface.

The accepted radius range is 1 m through 1e12 m. A radius of zero is rejected because the relation would be singular and would not define a surface distance. The broad endpoints are validation limits only. The page does not check whether the mass and radius imply a plausible density or a body with a stable spherical surface.

• Radius appears in the denominator.
• Four times radius gives half the speed.
• Radius is measured from the centre.
• Plausibility and density are not checked.

The gravitational constant and units

The handler uses G = 6.67430e-11 N m^2/kg^2. Substituting G, M in kilograms, and r in metres gives a quantity with units m^2/s^2 inside the square root. The square root therefore produces m/s. Keeping the constant explicit makes the calculation reproducible and prevents a rounded constant from changing a comparison or known answer.

The constant is universal in the Newtonian model; it is not a local acceleration value. A body's surface acceleration would involve G M / r^2 and is a separate relation. This page uses G directly to calculate a speed scale. It does not add a measured local gravity field, a latitude correction, or a rotational contribution.

• G is fixed at 6.67430e-11.
• The radicand has units m^2/s^2.
• The square root gives m/s.
• Local rotation and gravity corrections are absent.

The surface relation and its boundary

The formula is v = sqrt(2 G M / r). It is derived for a test object in a Newtonian field of a spherical source, starting at radial distance r. The calculator applies it exactly as a magnitude relation. The spherical-body surface assumption is the idealized textbook boundary near the formula: no irregular shape, finite-atmosphere effect, or additional source is included.

The formula does not describe acceleration during a powered ascent. It identifies the ideal initial speed that corresponds to zero total specific mechanical energy for the stated starting radius. A vehicle can exchange energy with an engine, atmosphere, rotation, and other bodies, so a real mission question needs more inputs. The current page deliberately has none of them.

• The formula is a Newtonian energy result.
• The start point is the modeled surface.
• No powered ascent is simulated.
• The spherical-body boundary is explicit.

An Earth-scale example

For a body with M = 5.972e24 kg and r = 6,371,000 m, the radicand is 2 G M / r. Taking its square root gives approximately 11,186 m/s, or 11.186 km/s. The second output is a unit conversion: divide the metres-per-second value by 1,000. The example demonstrates the constant, scale, and conversion, not a launch result.

The example treats the body as a nonrotating ideal spherical source and ignores atmosphere, terrain, and all vehicle behavior. It does not state how much propellant is needed or whether a vehicle can achieve the number. A clear report calls it a classical surface escape speed and keeps that adjective with the value.

• Mass: 5.972e24 kg.
• Radius: 6,371,000 m.
• Speed: about 11,186 m/s.
• Converted speed: about 11.186 km/s.

Metres per second and kilometres per second

The primary result is returned in metres per second because the SI formula produces that unit directly. The second result divides by 1,000 to give kilometres per second, a convenient astronomical scale. Both entries refer to the same speed magnitude. The conversion is exact at the arithmetic level apart from ordinary floating-point representation and does not introduce a different physical model.

Unit labels matter because a value such as 11.186 can be misread as m/s when it is actually km/s. The steps show the conversion explicitly. The handler does not convert to miles per hour, orbital period, or distance traveled. Any further conversion would be a separate unit operation and should preserve the original classical scope.

• Primary unit: m/s.
• Secondary unit: km/s.
• Conversion divides by 1,000.
• No trajectory quantity is inferred.

Zero is not an allowed body input

Unlike a force calculator with a zero-mass boundary, this page requires a central-body mass and radius greater than zero. A zero mass would produce a zero speed but would no longer represent the intended gravitating body. A zero radius would be singular. Positive lower bounds keep the inputs aligned with the spherical-body surface question and prevent a division-by-zero path.

The minimum values are inclusive: M = 1 kg and r = 1 m are accepted and produce a finite result. They are mathematical endpoints, not evidence that a one-kilogram spherical body with a one-metre radius is a relevant physical object. The formula remains valid as a bounded computation while its physical interpretation depends on the model assumptions.

• Mass minimum is 1 kg.
• Radius minimum is 1 m.
• Zero inputs are rejected.
• Minimum acceptance is not physical endorsement.

Escape speed is not orbital speed

Escape speed and circular orbital speed are related but different quantities. A circular orbit at a given radius requires a particular tangential speed and remains bound in the ideal two-body picture. Escape speed is higher by a factor of square root of two at the same radius and represents the zero-energy threshold. The calculator returns only escape speed and does not calculate a circular orbit, period, inclination, or trajectory.

The distinction is important because a number can be correctly calculated and incorrectly labeled. The page's input fields do not include orbital direction, altitude history, or an initial state. Do not use the result as an orbit-insertion claim or a mission plan. A separate orbital model must define the desired path and all relevant energy and momentum conditions.

• Escape speed is an energy threshold.
• Circular orbital speed is lower at the same radius.
• No orbit is calculated.
• No insertion or trajectory claim is made.

What atmosphere and rotation would change

The ideal relation does not include an atmosphere. Drag can remove mechanical energy during ascent, and the required propulsive performance depends on how energy is delivered. The relation also does not include body rotation, which can affect the ground-relative speed and launch geometry. These are real-system effects, but they are not corrections that can be inferred from only M and r.

The calculator likewise omits terrain, winds, vehicle mass changes, thrust direction, gravity losses, and guidance. Mentioning those factors clarifies the boundary; it does not invite the user to approximate them by changing the two inputs. The ideal output remains useful as a reference energy scale and not as a launch-performance guarantee.

• Atmospheric drag is omitted.
• Rotation is omitted.
• Vehicle mass and thrust are omitted.
• The output is not launch performance.

Validation and finite results

The handler requires finite JavaScript numbers within the inclusive mass and radius ranges. Numeric strings, missing values, NaN, infinities, zero, negative inputs, and values above the stated maxima are rejected. Direct validation keeps the formula safe when called without the browser and ensures that the square-root radicand is formed from a positive, finite setup.

The radicand, square-root speed, converted speed, and result entries receive finite checks. The conversion to kilometres per second is performed only after the primary speed is valid. The engine does not clamp an invalid body size, substitute Earth values, or evaluate expressions. Rejection preserves the intended model instead of hiding a malformed input.

• Mass and radius must be finite.
• Both inputs have positive inclusive minima.
• The radicand and outputs are guarded.
• Invalid values are rejected rather than substituted.

A reproducible astronomy report

A report should identify the ideal central body, record M and r with units, state G, and show the square-root substitution. Keep both m/s and km/s labels attached to the result. State that the starting point is the modeled surface and that the output is a speed magnitude. These details allow another reader to check the calculation without mistaking a radius for an altitude or a converted unit for a new result.

The report should repeat the classical spherical-body boundary. It should say that launch vehicle performance, atmosphere, rotation, trajectory, and mission planning were not modeled. This is not a disclaimer added after the mathematics; it defines what the two-field formula can honestly support.

• Record mass, radius, G, and units.
• Show the radicand and square root.
• Label both speed units.
• Attach the no-mission-planning boundary.

Appropriate educational use

The calculator is useful for astronomy and physics exercises involving gravitational binding, scaling, and energy conservation. It can demonstrate why a more massive body or a smaller radius changes the speed threshold and why km/s is a convenient scale. It also gives a clear test of fixed constants and square-root unit conversion.

It should not be used to choose a launch system, estimate propellant, approve a mission, or forecast a trajectory. Those tasks require variables and models absent here. Keep this page in the role of a classical spherical-body surface relation, and use a separately reviewed aerospace or orbital analysis for any operational conclusion.

• Good for gravitational-energy lessons.
• Good for square-root scaling checks.
• Not a launch calculator.
• Not a mission or trajectory planner.

Final interpretation checklist

Check that M is central-body mass in kilograms and r is centre-to-surface radius in metres. Confirm that the fixed G value is used, that 2 G M is divided by r, and that the square root is taken before converting units. Test the inclusive positive endpoints and retain the label classical surface speed. These checks establish the arithmetic but not the physical realism of the selected body.

Then ask whether the desired conclusion remains the ideal threshold described by the formula. If so, the result is clear. If it asks about launch timing, propellant, atmosphere, orbit insertion, or mission success, stop at the boundary. The page calculates v = sqrt(2 G M / r); it makes no launch or mission-planning claim.

• Check mass and radius definitions.
• Check G, units, and square root.
• Keep the surface relation explicit.
• Do not turn escape speed into mission advice.

Specific energy behind the square root

The surface escape relation can be understood per unit mass of the departing object. Its initial kinetic energy per unit object mass is one half v squared, while the classical gravitational potential relative to infinity is -G M/r. Setting the total specific energy to zero gives one half v squared = G M/r and therefore v = square root of 2 G M/r. The test object's own mass cancels from this threshold, which is why it is not an input field.

This cancellation does not mean vehicle mass is irrelevant to a real launch. A real vehicle must accelerate its own structure and propellant, and its propulsion system delivers energy over time with losses. The ideal threshold describes a specific-energy scale for a test object in a fixed central field. It does not calculate propellant, thrust, acceleration, or a changing mass.

The reference at infinity is also an ideal convention. Reaching a finite altitude with a nonzero speed is a different energy state, and a body can be in a bound orbit while moving quickly. The calculator returns the threshold defined by its formula and does not convert it into an altitude, orbit, or mission event.

• The result follows from zero total specific energy.
• The test-object mass cancels.
• Real propulsion still needs vehicle data.
• Infinity is the potential reference.

Surface, altitude, and rotation distinctions

The radius field represents the starting distance from the central body's centre. Calling it a surface radius fixes the starting location in the catalog contract. If an object begins above the surface, the relevant radial distance is larger and a separate calculation could use that radius. The handler does not accept altitude and radius together or decide how terrain changes the starting point.

The ideal formula also ignores rotation. A point on a rotating body already has inertial velocity relative to a nonrotating frame, and the direction and latitude can matter to a real launch. None of that changes the classical two-field relation as implemented here because no rotational state is entered. The result should not be described as a ground-relative launch requirement.

A spherical source is another explicit simplification. An irregular body can have a surface whose distance and gravitational potential vary with location. The page uses one central mass and one radius, so it cannot represent local topography, oblateness, or a nonuniform field.

• r is a centre-to-surface distance.
• Altitude is not a separate field.
• Body rotation is omitted.
• Irregular shape is not modeled.

Comparisons and careful handoff

When comparing two ideal bodies, record whether the change came from mass, radius, or both. A body with four times the mass and the same radius has twice the escape speed, while a body with four times the radius and the same mass has half the speed. These comparisons are valid for the formula and make useful teaching examples, but they do not imply that the bodies share composition, atmosphere, or physical feasibility.

Input precision should also be treated honestly. A mass and radius with limited measurement precision cannot support unlimited meaningful digits in the calculated speed. The handler protects finiteness but does not propagate uncertainty or round according to a measurement standard. Preserve the original values and their context outside the page.

If the output is passed to a larger aerospace or astronomy calculation, label it as the classical spherical-body surface relation. Carry forward that it excludes atmosphere, rotation, propulsion, trajectory, and mission planning. The value can be a reference scale without being a launch recommendation.

• Compare mass and radius changes separately.
• Input precision limits interpretation.
• Uncertainty is outside the one-value result.
• Handoff must keep mission limits visible.

The gravitational scale in the result

The combination G M sets a gravitational scale for the central body. Dividing it by radius gives a specific potential scale, and multiplying by two before the square root gives the escape-speed relation. This interpretation helps a learner see why mass and radius appear together rather than treating the formula as an arbitrary calculator rule. The handler uses the combination only for the requested speed and does not return a gravitational parameter as a separate result.

The speed is independent of the departing object's mass in the ideal threshold, but it is not independent of the source body's distribution if the spherical assumption fails near the surface. A lumpy or rotating body can require a more detailed potential description. The current page intentionally does not add those terms or pretend that one radius represents every departure location.

Keeping the scale interpretation separate from mission performance is useful. The result describes the central field's ideal energy threshold, while a vehicle problem concerns how a machine changes its own state through time. The two questions share units but not an input contract.

• G M sets the central gravitational scale.
• The departing mass cancels in the ideal threshold.
• Source shape can change a real potential.
• Field scale is not vehicle performance.

Documenting the ideal result

A useful worksheet can list the body mass and radius, calculate the speed, and compare it with another ideal body. It should identify the source of each number and retain enough context to distinguish a surface radius from an altitude. The output in both speed units is a conversion pair, not two independent measurements.

If a later analysis uses the speed as a reference, it should add its own initial velocity, direction, frame, atmosphere, rotation, propulsion, and trajectory assumptions. The current calculator cannot tell whether those additions are appropriate. Its finite guards establish only that the two-field arithmetic returned a usable number.

The final label should remain classical spherical-body surface escape speed. That label communicates the useful result and the boundary at once. It also prevents a reader from treating a clean number as a mission schedule or a launch approval.

• Keep source values with the conversion pair.
• Add trajectory assumptions only in a separate model.
• Finite output is not complete evidence.
• Use the full classical surface label.