IFMP Authorized Surveying Officers Certification common mistakes
IFMP Authorized Surveying Officers Certification · Understand the traps and how to avoid them.
Treating chart datum as mean sea level or as the ellipsoid when computing reduced depths, so soundings are reduced to the wrong reference surface.
Candidates learn 'sea level' as an everyday reference and conflate chart datum (usually a low-water datum such as LAT), the ellipsoid, and mean sea level, then apply the wrong offset in depth reduction.
What to do instead
Before any reduction, explicitly identify the vertical reference for the survey and for the chart, and state the transformation between them; practice computing reduced depth = observed depth minus the correct datum offset for the specific datum in use.
Applying a single straight baseline between the wrong basepoints, or drawing an equidistance line without first establishing which basepoints are actually relevant.
Candidates memorize the equidistance method but skip the step of selecting controlling basepoints, and they forget that straight baselines require specific geographic conditions and legal proclamation.
What to do instead
Work every delimitation problem in a fixed order: identify the applicable baseline regime, list candidate basepoints, eliminate those not controlling, then construct the line; justify each basepoint in writing.
Confusing territorial sea, contiguous zone, and exclusive economic zone distances and the rights attached to each when answering boundary questions.
The distances (12, 24, 200 nautical miles) are easy to mix up under time pressure, and candidates memorize numbers without the associated sovereign rights, leading to wrong answers on rights-based questions.
What to do instead
Build a one-page reference table pairing each zone with its breadth, its outer limit measurement basis, and the specific rights and duties; rehearse distinguishing 'sovereignty' from 'sovereign rights' from 'enforcement jurisdiction'.
Producing a survey plan that omits the line spacing rationale, the required object detection capability, or the specified order/standard, so coverage cannot be defended.
Candidates focus on the line plan drawing itself and treat the specification, spacing justification, and detection requirements as boilerplate rather than the substance of the plan.
What to do instead
Use a fixed plan checklist: standard/order, depth range, scale, line spacing with the formula and its inputs, object detection requirement, positioning accuracy, and contingency; verify each item is present before finishing.
Mixing coordinate reference systems or epochs, e.g. combining GNSS positions in a global frame with chart data in a local datum without a documented transformation.
Candidates treat datum as a label on the project rather than a computational step, and they underestimate how datum shifts and epoch differences propagate into positions and soundings.
What to do instead
For each dataset, record CRS, datum, and epoch; require an explicit, documented transformation with parameters and residuals before combining data; spot-check known control points after transformation.
Accepting soundings or positions without applying sound velocity, tide, draft, or attitude corrections, or applying them once and never updating.
Candidates see corrections as a post-processing afterthought rather than part of acquisition, and they assume a calibration or correction holds for the whole survey.
What to do instead
Maintain a correction log tied to time and location; apply sound-velocity profiles at intervals tied to observed variability, and verify tide, draft, and attitude corrections are applied per line or per epoch with recorded values.
Describing a calibration as 'done' without recording the reference standard, the before/after values, environmental conditions, or acceptance criteria.
Candidates equate performing the calibration procedure with documenting it, and they do not connect calibration evidence to the traceability and uncertainty requirements of the deliverable.
What to do instead
For every calibration, record instrument, standard used and its traceability, environmental conditions, pre- and post-adjustment readings, pass/fail against stated tolerance, and the person and date; treat the record as part of the survey data.
Reporting a cleaned dataset as validated without documenting the QC tests performed, the thresholds used, or how anomalies were resolved.
Candidates believe visual inspection in processing software constitutes QC, and they do not distinguish between correcting data and demonstrating that the correction was justified.
What to do instead
Produce a QC report listing each test, its threshold, the result, and the disposition of every flagged feature; keep rejected soundings and the reason for rejection so the validation is auditable.
Issuing a chart or report deliverable that leaves the horizontal and vertical datums, units, or scale ambiguous, or that omits the metadata a user needs to interpret it.
Candidates concentrate on the depicted content and assume the surrounding conventions are obvious, so datum statements, units, and uncertainty information get dropped or left implicit.
What to do instead
Apply a deliverable checklist covering datum statements, units, scale, accuracy/uncertainty, source and date, and revision status; have a second person verify the metadata against the project specification before issue.
Writing a risk assessment that lists generic hazards without linking them to specific survey operations, controls, or a stop-work trigger.
Candidates treat the risk assessment as a compliance document to be filled in rather than an operational tool, so hazards are copied generically and controls are not tied to the actual task or conditions.
What to do instead
For each phase of the operation, identify the specific hazard, rate likelihood and consequence, name the control and the responsible person, and define the condition that triggers stopping work; review it against the day's forecast and plan.
Failing to distinguish a legal obligation from good practice, or answering an ethics scenario by choosing the option that protects the client rather than the accurate record.
Candidates blur regulatory requirements, contractual terms, and professional ethics, and they default to client-pleasing answers instead of the duty to maintain accurate and complete survey records.
What to do instead
Classify each requirement as legal, contractual, or professional-ethical before answering; for ethics scenarios, identify the affected parties and the professional duty to accuracy and disclosure, and choose the response that preserves the integrity of the record.