The Mandatory Datum Standard: NAVD 88
FEMA policy mandates that all elevation data submitted for Flood Insurance Rate Maps (FIRMs), Letters of Map Amendment (LOMAs), and Elevation Certificates be referenced to the current National Geodetic Survey (NGS) benchmark network, which is now expressed in NAVD 88.
However, a large volume of existing engineering plans, municipal records, and older FIRM panels still carry elevations in NGVD 29. When a project references both, the uncorrected difference between these two datums constitutes a systematic elevation error that directly affects:
- Base Flood Elevation (BFE) compliance determination
- Lowest floor elevation certification
- Flood insurance premium calculation
- LOMA and LOMC eligibility
The Physical Magnitude: How Large Is the Shift?
FEMA Region II's official datum guidance provides county-level NAVD88 ↔ NGVD29 conversion factors. Representative examples from New Jersey show:
| County | Offset (feet) | Offset (meters) | Direction |
|---|---|---|---|
| Burlington, NJ | +1.3 ft | +0.40 m | NGVD29 is higher |
| Ocean, NJ | +1.1 ft | +0.34 m | NGVD29 is higher |
| Atlantic, NJ | +1.0 ft | +0.30 m | NGVD29 is higher |
A 0.3–0.4 meter vertical error is often the margin between a structure being above or below the BFE — determining whether a building must carry mandatory flood insurance.
Official Transformation: VERTCON 3.0 via NCAT
The authoritative tool for converting between NGVD29 and NAVD88 is VERTCON 3.0 (NOAA Technical Report NOS NGS 68), implemented in the NGS NCAT (National Coordinate Conversion and Transformation Tool). The mathematical basis is:
where ΔH is obtained from VERTCON 3.0 grid interpolation at the point's latitude (φ) and longitude (λ).
A flat "constant offset" applied uniformly across a project area — without using the grid — violates NGS methodology and is considered professionally inadequate.
Legal and Insurance Consequences
The USACE explicitly warns that using a FIRM BFE expressed in NGVD29 alongside a lowest-floor elevation from an Elevation Certificate in NAVD88 "could be significant if they are not first converted to the same vertical datum."
Documented consequences of datum non-compliance include:
- Flood insurance premium miscalculation (over- or under-charging)
- Non-compliance building permits issued for structures below BFE
- LOMA rejections requiring costly re-survey
- E&O claims against licensed surveyors and engineers
- Municipal liability for incorrect FIRM-based zoning decisions
✅ Pre-Submission Compliance Checklist
- Identify the datum reference of the governing FIRM panel (NGVD29 or NAVD88)
- Identify the datum of any benchmarks used in the survey
- If datums differ, use NCAT/VERTCON 3.0 to compute site-specific ΔH
- Apply correction: H_NAVD88 = H_NGVD29 + ΔH (or inverse)
- Document the applied conversion on the Elevation Certificate
- Never apply a flat county-average offset without grid-based verification
- Cross-check the adjusted lowest floor elevation against the BFE in the same datum
Frequently Asked Questions
What happens if I mix NGVD29 and NAVD88 in the same flood determination?
The FHA, FEMA, and USACE all explicitly warn this leads to erroneous BFE comparisons. The result is an incorrect compliance determination — either falsely exempting a structure from mandatory flood insurance or requiring insurance where none is needed. Both outcomes create professional liability exposure.
Is VERTCON 3.0 the only acceptable FEMA transformation method?
Yes for NSRS-compliant work. NGS designates VERTCON 3.0 (accessible via NCAT) as the official and authoritative tool for NGVD29↔NAVD88 orthometric height transformation. County 'flat offsets' from older FEMA region guidance may be used for preliminary estimates but are not accepted for final certification.
What are the EPSG codes for NAVD88 and NGVD29?
NAVD 88 height is EPSG:5703. NGVD 29 height is EPSG:5702. Always specify these in project metadata to prevent ambiguity.