NSPS CST Level II common mistakes
NSPS CST Level II · Understand the traps and how to avoid them.
Treating the CST Level II field track as a repeat of Level I and answering setup/rod-reading questions from habit instead of reading what the Level II element actually asks (e.g., applying a Level I single-setup procedure where the item requires a traverse closure or a field-book check).
Candidates who passed Level I recently assume Level II is the same body of knowledge with harder arithmetic, so they skim the stem and pattern-match to the familiar Level I procedure rather than identifying which work element is being tested.
What to do instead
Before answering, write down which Level II work element the item maps to and what deliverable it produces (raw field data, reduced data, a closure check, a stakeout record). If the element is not identifiable from the stem, re-read the stem rather than guessing from the numbers.
Reporting a traverse or level-loop result without performing and stating the closure/check, or accepting a misclosure that exceeds the stated tolerance without flagging it.
The arithmetic is the visible work, so candidates stop when the coordinates or elevations are computed and skip the comparison step that Level II items are actually built around. Field habit of 'close enough' carries over into an exam that grades the check, not the number.
What to do instead
Make the closure check a mandatory final step on every traverse or loop item: compute linear misclosure or loop error, compare to the tolerance given, and state accept/reject explicitly. If no tolerance is given, state the assumption you used.
Mixing angular units or bearing conventions mid-calculation - carrying decimal degrees into a DMS entry, or converting a quadrant bearing to an azimuth in the wrong direction (e.g., SW treated as 180+angle instead of 180+angle measured correctly, or NE/SW confusion).
Field instruments and field books present angles in DMS while calculators and software work in decimal degrees; candidates convert once at the start and then re-enter values inconsistently, and bearing-to-azimuth quadrant rules are memorized as a table rather than derived.
What to do instead
Standardize on one unit for the whole item and convert only at entry and final answer. For bearings, sketch the quadrant on scratch paper and derive the azimuth from the sketch each time instead of recalling a rule; verify by checking the azimuth falls in the correct 90-degree band.
Ignoring instrument and setup error sources when the item asks for an expected error budget - e.g., omitting centering/setup error, misreading the stated accuracy of the total station or level, or treating a manufacturer's angular accuracy as the total positional error.
Candidates conflate instrument specification accuracy with achievable field accuracy, and error-propagation items look like pure math so the physical setup contributions (centering, height of instrument, target height, refraction) get dropped.
What to do instead
Build a checklist for error-budget items: angular error, distance/EDM error, centering error, HI/HT measurement error, and environmental effects. Include each contribution the stem supplies, combine in quadrature where independent, and state which terms you excluded and why.
Answering construction-layout and stakeout items with the design coordinates rather than the values the field crew needs (e.g., giving the design elevation instead of the cut/fill, or giving the point coordinate instead of the offset and station).
The computation produces design values first, and candidates submit the intermediate result because it is the number they just calculated; the conversion to a field instruction feels like an extra step rather than the answer.
What to do instead
For every layout item, finish with the question 'what does the operator dial or stake?' Convert to cut/fill, offset, station, or deflection angle as appropriate, and sanity-check the sign and magnitude against a rough sketch of the site.
Misreading the field-book or data-recorder output in a given scenario - confusing backsight and foresight columns, treating a side-shot as part of the loop, or summing the wrong column for a rise-and-fall reduction.
Field notes are compact and column order varies by convention; candidates read the numbers they expect to see rather than the header, and time pressure discourages re-deriving one line as a check.
What to do instead
Before computing, label each column aloud (BS, FS, HI, elevation) from the stem's own headers. Verify the reduction by checking that the sum of backsights minus foresights equals the last elevation minus the first, and re-do one intermediate line if it does not.
On the office track, applying a CAD or software default without checking it against the project standard - layer, units, coordinate system, or point-code scheme - so the deliverable is internally consistent but non-compliant with the stated specification.
Office-track candidates are fluent in the tool and trust its defaults; exam items deliberately state a project standard (units, datum, naming) that differs from the default, and the mismatch is easy to overlook when the geometry looks right.
What to do instead
For each office item, extract the stated project requirements (units, datum/coordinate system, layer or feature-code standard, file format) into a short list before evaluating the answer choices, and eliminate any option that violates one of them even if the geometry is correct.
Confusing coordinate-system and datum transformations - treating a state-plane or grid coordinate as ground distance, or applying a datum shift without accounting for scale factor and convergence.
Grid-versus-ground is a small numerical difference that is invisible in a single point and only shows up over distance, so candidates who have not had to reconcile a survey to a mapping product treat the two as interchangeable.
What to do instead
Whenever an item involves grid coordinates, explicitly identify whether the requested answer is grid or ground, apply (or remove) the combined scale factor, and note convergence when azimuths are involved. State the direction of the correction in the answer.
Producing a map or deliverable that is technically computed but cartographically or contractually incomplete - missing metadata, legend, scale statement, north arrow, or the required accuracy statement - and choosing the option that only fixes the geometry.
Candidates focus on the computation because that is where the difficulty appears, and treat documentation and map furniture as cosmetic rather than as graded deliverable requirements.
What to do instead
Keep a deliverable-completeness checklist (datum and coordinate system, units, scale, legend, metadata/accuracy statement, date and source) and run every map or plan item against it before selecting an answer.
Managing time by sinking minutes into one long computation instead of flagging it and clearing the items that test a definition or a single check, leaving easy office-track or field-track items unanswered at the end.
Level II items mix short conceptual questions with multi-step computations, and candidates who start at question one and work strictly in order hit the long computation early and lose the easy points behind it.
What to do instead
Do a first pass answering every item that resolves in under a minute, mark computational items, then return to them with the remaining time. On any computation, set a hard time limit and move on when it expires; never leave a blank, since an eliminated-choice guess costs nothing.