NSPS CST Level IV study materials
NSPS CST Level IV study resources

NSPS CST Level IV: NSPS CST Level IV - Field Track

NSPS CST Level IV · Work through your exam, one topic at a time.

All guide sections

NSPS CST Level IV - Field Track

Field Track tests advanced field judgment: control, data collection, construction layout, boundary evidence, safety, and crew-level QA/QC. At Level IV, expect scenario questions where you must choose the field procedure that protects positional accuracy and defensible records, not merely operate an instrument.

Core field controls

  • Establish and verify control before production. Check backsight distance and angle, occupy a known point, and compare redundant shots; do not use a single stored coordinate without evidence.
  • Instrument checks include optical plummet, bubble, prism constant, EDM scale, and level collimation. Record calibration and environmental conditions.
  • Coordinate discipline: distinguish ground, grid, and project coordinates; record datum/epoch, units, and localization parameters.
  • Data QA: daily raw-file review, duplicate observations, closure checks, and photo/field-note linkage to point numbers.
  • Construction staking: verify plan and revision, compute cut/fill from design minus existing, mark offset and reference, and check by independent shot.
  • Boundary evidence: document monument condition, access, and ties; do not alter evidence or substitute convenience for records.

Worked example

A proposed pad elevation is 102.35 ft. A field shot at the stake location reads 104.10 ft. Cut = existing − design = 104.10 − 102.35 = 1.75 ft. The stake is marked “CUT 1.75.” Before leaving, the crew turns to a second control point and checks the stake with an independent measurement. If the check differs by more than project tolerance, re-observe rather than adjust the design.

Traps

  • Reversing cut/fill or using design minus existing.
  • Mixing feet and meters, or ground and grid distances.
  • Accepting a backsight only by distance, not angle.
  • Ignoring prism constant or rod zero error.
  • Recording coordinates without datum/epoch metadata.
  • Letting construction pressure override verification.