3.6.12 · D33D Geometry

Worked examples — Skew lines — shortest distance

2,922 words13 min readBack to topic

This page is a complete gym. The parent note built the one formula Here we throw every kind of input at it — clean skew lines, lines that secretly intersect, parallel lines where the formula explodes, one direction vector that is a coordinate axis, a degenerate zero-gap case, a real-world word problem, and an exam twist with an unknown constant. Before we start, two pieces of vocabulary so nothing is used before it is earned.


The scenario matrix

Every problem this topic can throw is exactly one row below. The examples that follow are labelled with the cell they hit, so together they cover the whole table.

# Case class What is special about the input What could go wrong
A Generic skew , triple product pick wrong points → panic (you shouldn't)
B Secretly intersecting triple product , not parallel miscalling it "skew"
C Parallel (distinct) lines ⇒ cross dividing
C' Coincident lines parallel AND share every point both top and bottom vanish,
D Axis-aligned direction a is , or forgetting a component is , not "missing"
E Degenerate gap () gap arrow is ⇒ they touch is automatic? yes
F Sign of triple product negative numerator comes out forgetting the $
G Real-world word problem two flight paths / girders translating words → vectors
H Exam twist: unknown constant find so lines intersect solving triple product

A — Generic skew (with the perpendicular picture)

Forecast: guess whether is bigger or smaller than before computing. (The lines aren't far apart, so it's small.)

The figure below is worth reading carefully before the algebra. Notice three features: the magenta line is , the violet line is , and the short orange stick is the one segment joining them at a right angle to both. The dot (magenta) is the closest point on ; the dot (violet) is the closest point on . The printed label on the orange stick is the very number we are about to compute by hand — so once you finish step 5, come back and confirm the two agree.

Figure — Skew lines — shortest distance
  1. Gap arrow . Why this step? This is the arrow (from a point of to a point of ) that we will project onto the perpendicular direction.
  2. Cross product (perpendicular-to-both direction): =\hat i((-1)(-1)-2\cdot2)-\hat j(3\cdot(-1)-2\cdot1)+\hat k(3\cdot2-(-1)\cdot1).$$ $=\hat i(1-4)-\hat j(-3-2)+\hat k(6+1)=-3\hat i+5\hat j+7\hat k.$ *Why this step?* By definition this arrow is $\perp$ both wires — the direction of the orange stick in the figure.
  3. Length of the cross . Why this step? We divide by this to turn a raw projection into a true length.
  4. Triple product (dot the gap into the cross): . Why this step? The dot picks out how much of the gap lies along the perpendicular.
  5. Distance .

Verify: — matches the forecast, matches the orange-stick label in the figure, and so the lines truly don't meet. Sanity: units are the same as the coordinates (pure length). ✓


B — Secretly intersecting (triple product )

Forecast: the directions differ, so if they're skew. Watch the numerator.

  1. Directions not parallel? is not a multiple of (ratios differ). Good, not parallel. Why this step? Parallel would send us to the C-formula; we must rule it out first.
  2. Gap arrow . Why this step? Same as always — the arrow whose along-perpendicular component becomes the distance.
  3. Cross product Why this step? This is the common-perpendicular direction; it is nonzero here, confirming the lines aren't parallel so the skew formula is legal.
  4. Triple product . Why this step? A zero numerator (with nonzero denominator) forces : the three vectors are coplanar ⇒ the lines intersect.
  5. Find the meeting point. Set . Why this step? tells us they meet; to find where, we equate the two parametrised points and solve for the dials . From : . From : . Substitute: , . Check : and . ✓ Point .

Verify: put into : ; put into : . Identical → they intersect, , not skew. ✓


C — Parallel (distinct) lines (the formula that doesn't explode)

Forecast: notice — parallel. The skew formula would give , so use the point-to-line version.

  1. Confirm parallel . Take . Why this step? If the directions are proportional the cross of directions is , breaking the main formula; distance then = perpendicular distance from a point of to , using Distance from a Point to a Line (3D).
  2. Gap arrow . Why this step? We need one arrow from to ; crossing it with next will extract the part perpendicular to the common direction.
  3. Cross Why this step? equals times the perpendicular gap, so dividing by leaves exactly that gap.
  4. Distance . Why this step? This is the final arithmetic that turns the two magnitudes into one clean length.

Verify: . ✓ Positive length, as required.


C' — Coincident lines (the pure trap)

Forecast: the directions are proportional, so this looks like case C. But watch what happens to the gap arrow — if it also lies along , the lines are literally the same line, and .

  1. Directions proportional? . Parallel — take . Why this step? Proportional directions rule out the main skew formula (cross of directions ); we must next check whether the two lines are merely parallel (case C) or the same line.
  2. Gap arrow . Why this step? If this gap is itself a multiple of , then already lies on , so the two "lines" trace the identical set of points.
  3. Is the gap along ? . Yes — proportional. Why this step? Parallel direction and a gap along that direction together mean the lines coincide.
  4. Point-to-line cross . Why this step? The cross of any vector with a parallel vector is zero — so both the main formula () and the parallel formula () collapse to .
  5. Conclusion : the lines are coincident (one and the same). Every point of is a point of .

Verify: the point should sit on . Solve : from the first, ; check ✓ and ✓. So is on ⇒ coincident ⇒ . The genuine is resolved not by arithmetic but by recognising "same line." ✓


D — Axis-aligned direction (a component is exactly zero)

Forecast: these are like a lamp-post and a floor rail one metre apart — expect .

  1. Directions , . Not parallel (different axes). Treat the zeros as real components, not "blanks." Why this step? A common slip is writing ; it is genuinely , and the zeros must ride through every dot and cross that follows.
  2. Gap . Why this step? Same routine — the arrow from a point of to a point of that we will project.
  3. Cross . Why this step? This is the common-perpendicular direction; here it comes out along , i.e. the horizontal direction linking the post and the rail.
  4. Triple product ; . Why this step? The dot extracts the along- part of the gap (which is ), and the unit-length cross means no rescaling is needed.
  5. . Why this step? Final division of numerator by denominator gives the pure length.

Verify: the two lines are the -axis-parallel line at and the -axis-parallel line at ; their nearest points and are exactly apart. Matches forecast. ✓


E — Degenerate gap: the lines share a point

Forecast: both lines start at the same point , so they obviously meet there — must be .

  1. Gap . Why this step? Whatever we later dot this zero arrow with is , so the numerator vanishes before we even compute the cross — worth spotting early to save work.
  2. Triple product . Why this step? Confirms the numerator is zero regardless of the perpendicular direction; the distance can only be provided the denominator is nonzero, which we check next.
  3. Cross (nonzero, they aren't parallel): , length . Why this step? A nonzero denominator distinguishes this genuine "" from the coincident-line "" of case C'.
  4. . Why this step? Clean division confirms the lines touch at exactly one shared point — intersecting, not skew.

Verify: shared point lies on both lines ( and ), so distance is genuinely — not the trap, because the denominator is nonzero. ✓ This is intersecting, not skew.


F — Negative triple product (why the absolute value matters)

Forecast: you'll get a negative number in the middle — do not report a negative distance.

  1. Gap . Why this step? The usual arrow from a point of to a point of , ready to project.
  2. Cross . Why this step? The common-perpendicular direction; nonzero, so the lines aren't parallel and the main formula applies.
  3. Triple product . Why this step? Here the gap leans against the cross direction, so the signed projection is negative — a normal, harmless outcome.
  4. Length of the cross . Why this step? We divide by this to convert the projection into a true length.
  5. . Why this step? The absolute value discards the sign (orientation), because distance is never negative.

Verify: the sign only told us the gap points opposite to ; distance is a length, so we take and get . ✓


G — Real-world word problem (two flight paths)

Forecast: the "1 km" vertical offset suggests is order-1 km.

  1. Translate to vectors ; . These come straight from Equation of a Line in 3D. Why this step? A word problem must first become the five ingredients before any formula can act.
  2. Gap . Why this step? The arrow between the two starting positions, whose perpendicular part is the closest approach.
  3. Cross . Why this step? The direction perpendicular to both flight paths — the line of shortest approach.
  4. Triple product ; . Why this step? Numerator (signed gap along the perpendicular) over denominator (perpendicular's length) is the whole formula.
  5. km. Why this step? Final division gives the physical closest-approach distance in km.

Verify: km — same order as the offset, and a sensible positive separation for two non-parallel paths. ✓


H — Exam twist: choose the constant so lines meet

Forecast: "intersect" ⇔ triple product ; solve a linear equation for .

  1. Gap . Why this step? Only the gap depends on , so writing it symbolically lets flow into the triple product.
  2. Cross . Why this step? The cross is fixed (independent of ), so we compute it once.
  3. Set triple product to zero: . Why this step? Zero triple product + non-parallel directions = coplanar = intersecting (a plane holds both), so this equation pins down .
  4. Directions non-parallel? vs — yes, not multiples. So genuinely means intersect. Why this step? If they had been parallel, would instead mean coincident (case C'); ruling that out confirms a true crossing.

Verify: with , gap , triple product . ✓ For any other the lines are skew.


Recall Which formula does each case need?

Case C (parallel, distinct) uses the point-to-line formula? ::: Yes — cross of directions is , so use . Case C' (coincident): how do you resolve the ? ::: Not by arithmetic — recognise that a point of one line lies on the other, so the lines are identical and . Zero triple product with non-parallel directions means? ::: The lines intersect (coplanar), , not skew. Why report not in case F? ::: Distance is a length ; the sign only records orientation of the gap. In case E, is ever a danger? ::: No — the denominator is nonzero when lines aren't parallel; only the numerator is .