11.6 Avoid Common Wrong-Answer Patterns
Key Takeaways
- FS distractors are engineered from plausible surveying mistakes: wrong units, wrong sign/quadrant, wrong domain assumption, premature rounding, or incomplete evidence reading.
- An error log must record the CAUSE of each miss, not just the correct answer, so patterns become visible and fixable.
- Many misses come from reaching for the first familiar formula instead of matching the formula to the scenario.
- A pre-answer checklist-units, datum, quadrant, record priority, professional duty-catches the most common engineered distractors.
The distractors are designed around your mistakes
A wrong answer is useful only if you learn why it happened. On the FS exam, many misses are not pure content gaps-they are pattern errors the question writers anticipate and offer as choices. The five recurring families:
| Pattern | Typical trigger | Example distractor |
|---|---|---|
| Wrong units | SI vs. U.S. Customary mix | Answer in meters when choices are feet; sq ft vs. acres |
| Sign / quadrant | Latitude/departure signs | Bearing in the opposite quadrant |
| Wrong domain assumption | Right formula, wrong situation | Using simple-curve geometry on a vertical curve |
| Premature rounding | Chained computations | Slightly off final value |
| Incomplete evidence reading | Boundary/records items | Ignoring senior rights or monument priority |
The FS exam mixes SI and U.S. Customary units on purpose, so a unit-conversion distractor is almost always present. Likewise, a coordinate problem almost always offers the sign-flipped (wrong-quadrant) result as a choice. Recognizing that the wrong options are engineered changes how you read the answer list: a choice that looks 'clean' may be the trap built from the most common error.
Match the formula to the scenario-don't reach
The most damaging habit is grabbing the first familiar formula instead of confirming it fits the situation. A few high-frequency mismatches across the domains:
- Computations: applying horizontal-curve relationships (radius, degree of curve, tangent) to a vertical-curve problem (parabolic, defined by grades and length), or using a closed-traverse balancing rule on an open traverse. Confirm the curve type and traverse type first.
- Geodesy / SPCS: using ground distance where the problem wants grid distance, forgetting the combined scale factor (grid = ground x scale x elevation factor). This is one of the most-tested geodesy traps.
- Leveling: mixing orthometric height (H) and ellipsoid height (h); remember H = h - N (geoid height). GNSS gives h; you need the geoid model to get H.
- Boundary: answering on measurements when the law says monuments control, or applying simultaneous-conveyance proration to a sequential conveyance (senior rights take their full deed first).
- Statistics: confusing the standard deviation of a single observation with the standard deviation of the mean (the latter divides by sqrt(n)).
For every item, force the scenario-first habit from Section 11.1: name the domain and governing rule before the formula. That one pause defeats most wrong-domain distractors.
Run an error log and a pre-answer checklist
Keep an error log during all practice. For each miss, record four fields: the question topic, the cause category (units / sign / wrong-domain / rounding / evidence / careless / true knowledge gap), the correct concept, and the fix. Do not simply copy the right answer-that teaches nothing. Review the log weekly and you will see your personal pattern: most candidates have two or three recurring causes that account for the majority of their misses. Drilling those causes is the highest-leverage prep there is.
Then install a pre-answer checklist-five quick checks before you lock any answer:
- Units: Do my units match the answer choices (feet vs. meters, sq ft vs. acres, decimal degrees vs. DMS)?
- Datum / height type: Is this orthometric or ellipsoid height? Grid or ground distance?
- Quadrant / sign: Does my bearing point the direction the sketch implies?
- Record priority: For boundary items-did I respect senior rights and monument-over-measurement priority?
- Professional duty: For business/ethics items-what does the standard of care or responsible-charge rule require?
This checklist directly targets the five distractor families above. A candidate who runs it reflexively converts the exam's engineered traps into easy catches, and turns a log full of past mistakes into a set of exam-day safeguards.
A domain-by-domain trap recap
Each knowledge area has a signature trap that recurs across FS forms. Commit this recap to memory so you recognize the trap as you read, before you reach for a formula:
| Domain | Signature trap | Safeguard |
|---|---|---|
| Computations | Wrong curve/traverse type; premature rounding | Confirm scenario type; round last |
| Geodesy / SPCS | Ground vs. grid distance; missing scale factor | Apply combined factor; H = h - N |
| Field / GNSS | Wrong GNSS method; orthometric vs. ellipsoid height | Match method to accuracy need |
| Boundary law | Measurements over monuments; sequential vs. simultaneous | Monuments and senior rights control |
| Mapping / GIS | Contour misreads; projected vs. geographic CRS | Contours never cross; check the CRS |
| Business / ethics | Confusing negligence, scope, and responsible charge | Apply the standard of care |
| Statistics | sigma of one observation vs. sigma of the mean | Divide by sqrt(n) for the mean |
This is good news, because it means the traps are predictable and therefore preventable. 1), runs the pre-answer checklist, and reviews a cause-tagged error log weekly will see the same handful of traps over and over-and will stop falling for them. Turning that recognition into a reflex is the single highest-leverage thing you can do in the final weeks: it raises your score without learning a single new formula, simply by refusing to hand the test the errors it was built to catch.
What is the main purpose of a wrong-answer (error) log during FS review?
A candidate knows the curve formulas but applies horizontal-curve geometry to a vertical-curve problem. Which error pattern is this?
Which pre-answer check most directly catches a common geodesy distractor on the FS exam?