Worked examples — Lines and planes in 3D — vector equations
Before anything else, three symbols you must own, because every example leans on them:

The scenario matrix
Every problem this topic can throw is one of these cells. The example that covers each cell is named in the last column.
| # | Case class | The trap / twist it tests | Covered by |
|---|---|---|---|
| C1 | Line through 2 points, all directions nonzero | plain symmetric form | Ex 1 |
| C2 | Line with a zero component in | you CANNOT divide by 0 | Ex 2 |
| C3 | Plane from point + normal, negative constant | sign of , distance sign | Ex 3 |
| C4 | Plane through 3 points | build normal via cross product | Ex 4 |
| C5 | Degenerate 3 points (collinear) | cross product ⇒ no plane | Ex 5 |
| C6 | Point-to-plane distance, point on the "other side" | absolute value handles both sides | Ex 6 |
| C7 | Point-to-line distance in full 3D | why the cross product, not projection alone | Ex 7 |
| C8 | Line parallel to a plane vs hitting it | dot of with : zero or not | Ex 8 |
| C9 | Word problem (drone flight path) | translate English → vectors | Ex 9 |
| C10 | Exam twist: two lines — parallel, intersecting, or skew? | limiting/degenerate classification | Ex 10 |
Example 1 — C1: Line through two points, clean case
Step 1 — direction. . Why this step? A line's direction is the displacement from one of its points to another — literally the arrow from to .
Step 2 — vector form. Anchor at , with the position vector of a generic point on the line: . Why this step? Every point is "start at , walk copies of " — the parameter sweeps the whole line, and is wherever you land.
Step 3 — parametric form (read off each coordinate of ): Why this step? The vector equation is really three equations stacked — one per coordinate. Peeling them apart lets us plug in a single value of and read off a concrete point .
Step 4 — symmetric form. Solve each for and equate (allowed because all of ): Why this step? Every point shares one ; setting the three " expressions" equal removes .
Verify: Plug into parametric: . ✓ And gives . ✓
Example 2 — C2: Zero component, the divide-by-zero trap
Step 1 — spot the zero. : the third slot is . Why this step? Symmetric form divides by each component. Division by is undefined — the formula silently breaks here.
Step 2 — what a zero direction MEANS. If for all , the line never changes height. It lives entirely on the flat sheet . Why this step? Interpreting the zero geometrically tells us what to write instead.
Step 3 — correct symmetric form. Use symmetric form only on the coordinates with nonzero direction, and state the frozen one separately: Why this step? The two nonzero-direction coordinates still share the same , so their ratios are equal; the frozen coordinate carries no at all, so it must be written as a standalone constraint rather than jammed into a fraction.
Verify: Take : . Check and — equal ✓ and ✓.
Example 3 — C3: Plane from point + normal, negative constant
Step 1 — normal form. Write as its position vector . Then gives . Why this step? Any in-plane arrow is perpendicular to , so its dot product with is zero.
Step 2 — simplify. . Why this step? The constant is . Here it landed positive despite the negative in .
Step 3 — distance from , whose position vector is : Why the absolute value? Distance is never negative; handles whichever side of the plane sits on.
Verify: , ; . Also satisfies the plane: ✓.
Example 4 — C4: Plane through three points

Step 1 — two spanning directions. , . Why this step? A plane is "one point plus two independent walking directions." These are the two directions.
Step 2 — normal via cross product. The Cross product gives the arrow perpendicular to both: Why this step? By definition and — exactly the normal we need.
Step 3 — Cartesian equation. Using point : , i.e. Why this step? Once we have the normal, the plane is just "all points whose arrow from is perpendicular to " — i.e. . Multiplying that dot product out and collecting terms turns the geometry into a single tidy Cartesian equation whose coefficients ARE the normal.
Verify: Each point must satisfy it. : ✓. : ✓. : ✓.
Example 5 — C5: Degenerate — three points that DON'T make a plane
Step 1 — spanning directions. , . Why this step? Same recipe as Ex 4 — but watch the two directions.
Step 2 — cross product. Why this step? The cross product is exactly when the two directions are parallel. Here .
Step 3 — interpret. A zero normal means "no unique perpendicular exists." The three points are collinear — they all lie on the single line . Three collinear points define infinitely many planes (a whole hinge of them), so there is no one plane. Why this step? The algebra () is the warning light for a degenerate geometric setup.
Verify: Is on line through ? — yes, . Collinear confirmed ✓.
Example 6 — C6: Point-to-plane distance, both sides

Step 1 — set up. , , . Why this step? The distance formula needs three ingredients: the normal (read straight off the coefficients), the constant (the right-hand side), and the normal's length (to convert a raw dot-product difference into an actual distance). Gathering them first keeps both point-computations clean.
Step 2 — signed value for . With : . So . Why this step? The numerator measures how far 's "height along " exceeds the plane's height. Its sign tells you which side.
Step 3 — signed value for . With : . So . Why this step? gives a negative signed value while gave positive ⇒ they sit on opposite sides of the plane.
Verify: Signs vs differ ⇒ opposite sides ✓. Distances and are both positive as distances must be ✓.
Example 7 — C7: Point-to-line distance in 3D
Step 1 — the vector from a line point to . Take (position vector ) and : . Why this step? Distance to a line is the perpendicular drop from ; we start from any known line point.
Step 2 — why the cross product. We want (the perpendicular height), where is the angle to the line. The Cross product magnitude gives exactly , so dividing by isolates the height: Why not just project? Projection gives the along-line component; we need what's left over perpendicular — the cross product captures that directly.
Step 3 — compute. . Magnitude . And . So . Why this step? This just executes the formula from Step 2 with our numbers: form the cross product, take its length, and divide by . Because here, the cross-product length IS the distance — no rescaling needed.
Verify: Distance from to the -axis should be ✓ — the -coordinate is irrelevant, as expected.
Example 8 — C8: Line parallel to a plane vs hitting it
Step 1 — the deciding test. A line is parallel to a plane when its direction is perpendicular to the normal, i.e. (the direction has no component along , so it never gains "height"). Why this step? Moving along is the only way to leave/approach the plane; measures that motion.
Step 2 — test . . So is parallel to the plane. Why this step? We apply the Step-1 test to 's specific direction . Getting exactly confirms the direction has no along-normal component, so the line stays at constant height relative to — it can never approach or leave the plane. Since passes through the origin and , that origin is off the plane, so never touches it.
Step 3 — test . . Nonzero ⇒ crosses the plane. Find where: , intersection at . Why this step? Nonzero dot means the line steadily changes height along , so it must hit any given height exactly once — see Intersection of lines and planes.
Verify: : ✓ (parallel). intersection : ✓.
Example 9 — C9: Word problem (drone flight)
Step 1 — model the path. Direction . Path: , so , where is the drone's position at "clock reading" . Why this step? "Straight flight through two known points" is exactly a line — point + direction.
Step 2 — model the fence and find . Fence is . Set . Why this step? Crossing means the -coordinate equals the fence height; solve for the single unknown .
Step 3 — crossing point. , , . Point m. Why this step? The value is the "clock reading" at which the drone reaches the fence; substituting it back into the path's and equations converts that time into the actual location in space where the crossing happens.
Step 4 — distance travelled to fence. . Distance m. Why this step? Distance flown is (fraction of the way ) (length of one direction step).
Verify: At , ✓ (on fence). m, and ✓.
Example 10 — C10: Exam twist — parallel, intersecting, or skew?
Step 1 — parallel check (both pairs). Directions parallel ⇔ one is a scalar multiple of the other. Pair A: — parallel directions. Pair B: vs — not parallel. Why this step? Parallel directions collapse three possibilities to two (same line, or parallel-and-distinct).
Step 2 — resolve Pair A. Directions parallel: are they the same line? Check if 's point lies on : need . From row 1, ; then row 2 gives . Contradiction ⇒ point not on . So parallel and distinct (never meet). Why this step? Same direction + a shared point ⇒ identical line; same direction + no shared point ⇒ parallel distinct.
Step 3 — resolve Pair B (not parallel). Solve for a meeting point: gives ; gives . Match: , , and : . The last is impossible ⇒ no intersection. Not parallel + no intersection = skew. Why this step? When directions aren't parallel, either the equations have a solution (they meet) or they're inconsistent (skew).
Verify: Pair A directions: ✓ parallel; point test vs inconsistent ✓ distinct. Pair B: the -equation is false ✓ ⇒ skew.
Recall Active recall — cover the answers
- Direction component is : how do you write symmetric form? ::: split that coordinate off as ; use ratios only for nonzero components.
- Cross product of two spanning directions is — what does it mean? ::: the points are collinear; no unique plane exists.
- One dot product decides line-vs-plane parallelism — which? ::: means parallel; nonzero means it crosses.
- Two 3D lines, not parallel, never meet — what are they called? ::: skew.
- Which side of a plane is a point on? ::: sign of : positive vs negative = opposite sides.
Connections
- Lines and planes in 3D — vector equations — the parent toolkit these examples exercise.
- Cross product — builds normals (Ex 4, 5) and point-to-line distance (Ex 7).
- Vectors and scalar (dot) product — the parallel/side tests (Ex 3, 6, 8).
- Vector projection — geometry behind the distance formulas.
- Intersection of lines and planes — Ex 8, 9, 10.
- Systems of linear equations — solving for meeting parameters (Ex 8–10).
- Parametrisation and parameters — the roles of .