Chandrasekhar Dynamical Friction Orbit Decay Calculator

Chandrasekhar dynamical friction formula used by this calculator

For a uniform background and the usual Maxwellian approximation, the calculator turns the Chandrasekhar drag law into a characteristic timescale. A common estimate is

Formula: t = v^3 / (4 π G^2 M ρ lnΛ)

where:

• t is the characteristic dynamical friction timescale.
• v is the speed of the massive body relative to the background.
• G is the gravitational constant.
• M is the mass of the moving body.
• ρ is the mass density of the background medium.
• lnΛ (often written lnΛ) is the Coulomb logarithm, capturing the effective range of impact parameters that contribute to the drag.

The calculator converts your astrophysical inputs to SI units, evaluates the timescale, and then reports the answer in years so you can compare it directly with galactic or cluster evolution. It also multiplies the timescale by the input speed to give a travel distance, which is a useful way to judge whether the body is likely to move only a fraction of an orbit or to drift a long way before friction becomes overwhelming.

Chandrasekhar dynamical friction units and conversions

This Chandrasekhar dynamical friction calculator expects the same compact astrophysical units that are common in papers and lecture notes:

• Mass M: solar masses (M☉).
• Background density ρ: solar masses per cubic parsec (M☉/pc³).
• Velocity v: kilometres per second (km/s).
• Coulomb logarithm lnΛ: dimensionless.

Internally, the script converts these quantities to SI units by applying:

• 1 M☉ ≈ 1.9885 × 10³⁰ kg.
• 1 pc ≈ 3.0857 × 10¹⁶ m, so 1 pc³ ≈ (3.0857 × 10¹⁶ m)³.
• 1 km/s = 10³ m/s.

The gravitational constant is taken as G ≈ 6.6743 × 10⁻¹¹ m³ kg⁻¹ s⁻². After computing the timescale in seconds, the calculator converts it to years using 1 year ≈ 3.154 × 10⁷ s. The travel distance is obtained from

Formula: d = v t

and then reported in convenient astrophysical units so the answer can be read as a drift length rather than just a clock value.

Interpreting the Chandrasekhar dynamical friction results

The timescale shown by this Chandrasekhar dynamical friction calculator is a characteristic sinking time, not a fully self-consistent merger clock. It is best read as the scale on which repeated gravitational encounters and the resulting wake can noticeably drain orbital energy.

In practice, the output usually falls into three useful regimes:

• t much shorter than 1 Gyr: the body experiences rapid orbital decay. Massive clusters or satellites will spiral in on timescales short compared with galactic evolution, and their current configuration is likely transient.
• t of order a few Gyr: decay is important over a Hubble time, but objects may complete many orbits before merging. This regime is common for satellite galaxies in Milky Way–like haloes.
• t comparable to or longer than the age of the Universe (≈ 13.8 Gyr): dynamical friction is weak. The orbit is effectively stable against decay on cosmological timescales, and other processes may dominate the evolution.

Because the estimate scales as v³/(MρlnΛ), the velocity input has a particularly strong effect. A modest change in speed can move the result by a large factor, while changes in mass, background density, or lnΛ act linearly.

The travel distance provides a second check. If the distance is much larger than the current orbital radius, the body can complete many passages before the drag really reshapes the orbit. If it is similar to or smaller than the orbital size, the decay is already important on roughly an orbital timescale.

Worked example: a satellite galaxy in a dense halo

A useful Chandrasekhar dynamical friction example is a satellite galaxy moving through an inner halo. Suppose the body has M = 10⁸ M☉, the background density is 0.1 M☉/pc³, the speed is 200 km/s, and lnΛ = 10.

This combination represents a fairly massive object in a dense environment, so the drag is not negligible. The mass term and the density term both push the timescale downward, while the cubic velocity dependence makes the estimate very sensitive to whether the orbit is a little slower or faster than the chosen value.

If you raise the mass or the local density, the orbit sinks more quickly. If you raise the speed, the decay time grows sharply and the travel distance expands as well. That is why this example is a good starting point for testing how the Chandrasekhar estimate responds to different halo conditions.

Comparing Chandrasekhar dynamical friction with other timescales

The Chandrasekhar timescale is most informative when you place it beside other dynamical clocks in the same system. The table below gives a qualitative comparison for galaxy and cluster problems.

Use the comparison to decide whether friction, orbital motion, or internal relaxation is likely to dominate the next stage of evolution. If the friction time is much longer than the orbital period, the orbit changes only gradually; if it is much shorter, sinking and circularisation can become important quickly.

Chandrasekhar dynamical friction assumptions and limitations

This Chandrasekhar dynamical friction calculator follows the classic textbook idealisation, so its answer should be treated as a scaling estimate rather than a full orbital integration. Key assumptions include:

• Homogeneous, isotropic background: the method assumes the body moves through a smooth medium with no strong density jumps or preferred directions. Real galaxies have disks, bulges, haloes, streams, and clumps that can change the drag.
• Maxwellian velocity distribution: the background velocities are taken to be Maxwellian. Cold streams, rotating disks, or anisotropic halo populations can alter the wake and shift the effective friction.
• Weak, cumulative encounters: the Coulomb logarithm compresses many small-angle gravitational encounters into one factor. Close, rare interactions with other massive objects are not modeled separately.
• Straight-line or gently curving motion: the estimate works best when the path changes slowly compared with the interaction scale. Highly eccentric or rapidly precessing orbits usually need a dedicated integrator.
• Single-component background: the calculator accepts one density ρ, so it cannot distinguish between stars, gas, and dark matter components that each contribute in different ways.

For that reason, the result is most useful for comparing scenarios and understanding parameter sensitivity. If you need an exact sinking history in a complicated potential, an N-body calculation or detailed orbit integration is the better tool.

Practical usage tips for Chandrasekhar dynamical friction estimates

When you use this Chandrasekhar dynamical friction calculator, start by choosing inputs that match the environment you want to study rather than trying to force every system into the same default values:

• Use masses from about 10⁵–10¹⁰ M☉ for typical dwarf galaxies, globular clusters, or massive black holes.
• Adopt densities between roughly 10⁻⁴ and 0.1 M☉/pc³ for diffuse haloes, and up to a few M☉/pc³ for dense inner regions.
• Set velocities in the range 50–300 km/s for orbits in Milky Way–like galaxies, or higher for galaxy clusters.
• Choose lnΛ between about 5 and 15; using 10 is a reasonable default when detailed modelling is unavailable.

If you want to understand which input matters most, vary one quantity at a time and watch how the timescale changes. In this formula, speed is especially influential because it enters as v³, while mass, density, and lnΛ move the answer in a linear way. That makes the calculator useful for quick sensitivity checks before you commit to a longer calculation or simulation.

Students can use the tool to see how a denser halo or a heavier satellite changes the sinking time, while researchers can use it for back-of-the-envelope checks before running a more detailed model.