Worked examples — Orbit determination — Gauss's method, Gibbs method
This page is the drill hall for the parent topic. The parent told you the machinery; here we run it on every kind of input you can meet: clean data, degenerate data, coplanarity-failing data, near-circular vs eccentric orbits, and an exam-style twist. Every symbol below was already earned in the parent note; where a step needs a fact from Angular Momentum & Eccentricity Vector, Lagrange Coefficients (f and g), Classical Orbital Elements or Coordinate Frames (ECI, topocentric) we point there.
The scenario matrix
Every cell below is hit by at least one worked example. "Cell" = the code in the last column.
| # | Scenario class | What is special about the input | Expected behaviour | Cell |
|---|---|---|---|---|
| 1 | Baseline Gibbs | 3 clean coplanar points, moderate eccentricity | clean | G-base |
| 2 | Coplanarity PASS check | verify the triple product is tiny | angle | G-coplanar-ok |
| 3 | Coplanarity FAIL | one point nudged out of plane | machine must refuse | G-coplanar-bad |
| 4 | Near-circular limit | radial term | G-circular |
|
| 5 | Sign / quadrant of result | velocity components with mixed signs | direction sanity | G-signs |
| 6 | Degenerate: collinear points | 3 points on a straight line | , blow-up | G-degenerate |
| 7 | Gauss root selection | the 8th-degree polynomial | pick the ONE physical root | Ga-root |
| 8 | Word problem (radar pass) | real numbers, full pipeline | element sanity | word |
| 9 | Exam twist | "which ? which root?" traps | avoid the trap | twist |
We use Earth throughout: .
Example 1 — Baseline Gibbs G-base
Forecast: Guess before computing — is nearer , , or km/s for a low-Earth orbit? (Low-Earth circular speed is about km/s, so expect a few km/s per component.)

- Magnitudes. km. Why this step? The scalars are the weights inside and ; nothing downstream works without them. (Check the third: km.)
- The three helper vectors (definitions straight from the parent): Why this step? and carry the orbit's scale (their length ratio gives the semi-latus rectum ); carries the direction toward perigee. In figure s01 the three black arrows are from the focus, and the red arrow is — notice it points along the eccentricity direction toward perigee.
- Velocity formula. Why this step? The bracket splits velocity into its only two possible directions on a conic: the transverse part (from , perpendicular to ) and the radial part (from , along/against ).
- Result: km/s.
Verify: km/s — squarely in the "few km/s per component, ~7 total" band we forecast for LEO. Units: ✓.
Example 2 — Coplanarity PASS G-coplanar-ok
Forecast: Should the "out-of-plane angle" be exactly or just tiny? (Real data has rounding, so expect tiny, not exactly zero.)
- Form the unit vectors . Why this step? Direction is all that matters for coplanarity; lengths would just scale the test.
- Build the unit normal of the plane through points 2 and 3, then dot with point 1: Why this step? is perpendicular to the plane of points 2 and 3, but its length is not 1 (it equals of the angle between them). Dividing by makes it a genuine unit normal, so the dot product lands safely in and is the sine of point 1's out-of-plane angle. Skipping this normalization would feed a number outside and the formula would be invalid.
- Convert to an angle: — the tilt of point 1 out of the plane of 2 and 3. Why this step? turns the perpendicular-component ratio directly into an angle; means perfectly coplanar.
Verify: , giving well under ✓ — safe to proceed.
Example 3 — Coplanarity FAIL G-coplanar-bad
Forecast: Will Gibbs still spit out some velocity? (Yes — algebra never complains. YOU must complain.)
- Recompute the normalized coplanarity number with . Why this step? This is the guard clause, and using the unit normal keeps so is legal. If the resulting angle is large, no Keplerian orbit threads all three points, so any is meaningless.
- Convert to an angle .
Verify: The out-of-plane angle jumps to tens of degrees — far above the threshold. Reject the data — do not run Steps 2–4 of Gibbs. (This is the [!mistake] the parent warns about: geometry that cannot be one orbit.)
Example 4 — Near-circular limit G-circular (figure)

Forecast: For a perfect circle, is there any radial velocity? (No — on a circle you never move toward or away from the focus, so the radial term should vanish.)
- Build the three points: , so km. Why this step? Equal magnitudes are the algebraic signature of a circle; they will make the sum collapse.
- Look at . With , every bracket is zero, so . Why this step? was the radial/perigee term. A circle has : no perigee direction, no radial motion — exactly why dies. In figure s02 the red arrow is ; it lies exactly tangent to the circle (perpendicular to ), showing zero radial component.
- Velocity reduces to the transverse term only: . Why this step? In the Gibbs formula the radial direction enters only through . Once (Step 2), the bracket keeps just , which is perpendicular to — the transverse direction. So the drop-out of the radial piece is a direct algebraic consequence of , not a coincidence.
Verify: Numerically km/s, matching circular speed km/s ✓, and the radial component ✓.
Example 5 — Signs of the result G-signs
Forecast: "Climbing" here means altitude — the radial speed . Positive ⇒ moving away from Earth's centre (altitude rising); negative ⇒ falling. Guess the sign before computing.
- Radial speed . Sign ⇒ climbing (altitude increasing), ⇒ falling. Why this step? The sign of the radial component is the ONE number that tells you pre- vs post-perigee, independent of quadrant.
- Check near-perpendicularity: for a nearly circular case ; here the orbit has some eccentricity so a small nonzero value is expected. Why this step? If is a small fraction of , the motion is mostly transverse, confirming a low-eccentricity orbit.
Verify: km/s (small, positive) ⇒ the body is climbing — its altitude is increasing, so it is on the post-perigee side heading toward apogee; and confirms motion is mostly transverse ✓ — consistent with a low-eccentricity orbit.
Example 6 — Degenerate: collinear points G-degenerate
Forecast: A straight radial line cannot be a closed orbit around a focus — so something must divide by zero. What?
- Every cross product of two parallel vectors is : . Why this step? is a sum of exactly these cross products, so and .
- The prefactor then has in the denominator → undefined. Why this step? This is the machine's honest way of saying "collinear points define no orbital plane." Also , so is — doubly degenerate.
Verify: exactly ✓ ⇒ Gibbs is undefined. Interpretation: collinear points give no unique conic, so reject — you need genuinely spread-out geometry.
Example 7 — Gauss root selection Ga-root
Forecast: An 8th-degree polynomial has up to 8 roots. How many are physically legal for a satellite?
- Solve numerically; keep only real roots. Why this step? is a distance — complex roots are non-physical artefacts.
- Discard non-positive roots and any with Earth radius ( km). Why this step? A satellite cannot sit inside the Earth; negative distances are meaningless. This is the parent's [!mistake] "take any root."
- The surviving positive real root near km is .
Verify: The polynomial has exactly one positive real root km km ✓; all others are negative or complex and are discarded.
Example 8 — Word problem: full radar pass word
Forecast: Radar caught a LEO satellite. Do you expect near (nearly circular) or near (highly elliptical)?
- Run Gibbs (Example 1) to get km/s. Why this step? Classical Orbital Elements all flow from the state ; you need velocity first.
- Angular momentum , then . Why this step? From Angular Momentum & Eccentricity Vector, fixes the plane and scale.
- Eccentricity vector , then . Why this step? is the shape number the operator asked for.
Verify: Computation gives and — small, so nearly circular as forecast for a LEO ✓. (Units of : km·(km/s)=km²/s ✓; is dimensionless ✓.)
Example 9 — Exam twist twist
Forecast: Two traps are baked in. Name them before reading on: one is about which point, the other about which root.
- Trap 1 — wrong point. The symmetric sums are built centred on the middle point, so the boxed formula yields only. Feeding it as "" is invalid — you would have to re-centre the whole construction on point 1, which the standard formula does not do. Why this step? Using or is exactly the parent's [!mistake]; the algebra is not symmetric under relabelling, so the student's is a mislabelled/invalid output. Fix: report the velocity only at the middle point, km/s from Example 1.
- Trap 2 — root choice. Both roots are positive and above Earth's radius, so you cannot reject on radius alone. Back-substitute each candidate into the slant-range equations and keep the one giving all positive . Why this step? Recall from Coordinate Frames (ECI, topocentric) that each satellite position is , where is the known observer position, the measured line-of-sight unit vector, and the slant range (distance to the target). A physical range must satisfy — you cannot look behind yourself to see the satellite.
- Break the tie by orbital speed. Convert each root to the orbital speed it implies via the near-circular estimate . For km, km/s (sensible LEO). For km, km/s — far too slow for the tightly-spaced short arc that produced these observations. Why this step? A short observed arc means the body swept a large angle quickly, which is impossible at km/s. This rules out the huge root physically, independent of the range test.
Answer: Correct velocity is km/s (middle point, not ); correct range solution is km (positive , sensible speed), and km is discarded.
Verify (numeric portion): For the near-circular data, the correct centred computation reproduces km/s (Example 1), while any relabelling changes the answer — confirming the formula is point-specific ✓. Root km implies orbital speed km/s km/s, absurd for the observed short arc, so it is discarded ✓.
Recall Quick self-test on the matrix
When does ? ::: When the three points are collinear (all cross products vanish). What makes ? ::: A circular orbit, ⇒ every bracket is zero, no radial motion. Which velocity does Gibbs give? ::: Only , at the middle point. How do you break a tie between two positive real Gauss roots? ::: Keep the root giving all positive slant ranges (and a sensible orbital speed). What is the coplanarity red flag threshold? ::: Out-of-plane angle above about . Why must be normalized before ? ::: Its length is (angle), not 1, so without dividing by it the coplanarity number can fall outside .