HDD Design Standards: ASTM F1962 and Other Key References

ASTM F1962 is the standard guide for placing polyethylene pipe and conduit by maxi-horizontal directional drilling under obstacles, including river crossings, and it is the reference most HDD projects name first. The difficulty is that it is not the only document a crossing needs: bore geometry and installation loads sit with that guide, in-service pressure design with the pipeline codes, weld acceptance with API 1104, and the project-specific values that bind them together with the owner specification. This page maps each deliverable to its governing document, shows how to cite standards in a specification, and explains where the standards stop.

What Does the F1962 Guide Cover, and Which Edition Applies?

ASTM F1962 is a standard guide, not a prescriptive code, and that distinction matters when a contractor has to demonstrate compliance. It is published by ASTM International under the full title Standard Guide for Use of Maxi-Horizontal Directional Drilling for Placement of Polyethylene Pipe or Conduit Under Obstacles, Including River Crossings. The guide addresses maxi-HDD placement of polyethylene pipe and conduit, so mini and midi rigs and steel transmission pipe sit outside it.

• Bore geometry for a maxi-HDD crossing, including the relationship between entry and exit angles, cover and bend radius.
• Installation loads for polyethylene pipe, including the treatment of pullback forces.
• Product-pipe limits under installation, including deflection and ovality of the polyethylene pipe.
• Placement under obstacles such as watercourses.

What it does not do is design a steel pipeline. Wall thickness, in-service pressure containment and allowable stress for a steel line follow the pipeline codes, and weld acceptance follows the welding standard. A specification that cites only this guide for a steel crossing has addressed the bore, not the line. Where a steel crossing is involved, weld procedure qualification and weld acceptance sit with the welding scope, and the specification has to state how those records are handed over.

The edition of ASTM F1962 is not fixed: more than one edition is in circulation and a revision work item is active, so a specification has to name the edition it relies on. The editions in circulation include ASTM F1962-22 and the later ASTM F1962-25, where the suffix gives the edition year, and a revision work item, WK93768, is active. That work item proposes an 8% deflection limit for both pressurised and non-pressurised pipe across all DR ratings. Until a revision is published, the deflection limit in the edition named by the specification is the one that governs, so confirm the edition in force before design and record it in the basis of design.

What Do ASCE MOP 108, NASTT Practice and DCA Guidance Add?

The guide is strong on the bore and the polyethylene pipe, and thinner on how the pipeline itself should be designed for the installation. ASCE MOP 108, Pipeline Design for Installation by Horizontal Directional Drilling, is the pipeline-design companion that fills that space, and an updated edition has been published. As with ASTM F1962, confirm the edition in force and record it in the basis of design.

Two further bodies of practice sit alongside the standards. The NASTT HDD Good Practices Guidelines, issued by the North American Society for Trenchless Technology, set out phase-by-phase recommendations from planning to records. DCA practice, from the Distribution Contractors Association, gives the industry its language for rig classes and field execution. Neither is a code, and neither is binding unless a contract references it.

• ASCE MOP 108: pipeline design for HDD installation, complementing the bore guidance.
• NASTT HDD Good Practices Guidelines: what good practice looks like across each phase of a crossing.
• DCA practice: rig classification and contractor-side conventions, useful for scoping and evaluation.
• Owner standards: operator-specific requirements that frequently exceed the published documents.

Which Pipeline Codes Sit Alongside the HDD Standards?

HDD standards cover the crossing; pipeline design codes cover the line. The pipeline-side documents are the ones Table 1 lists alongside the bore guide: ASME B31.4 or B31.8 for pressure design and wall thickness, API 1104 for weld acceptance, and the owner specification for everything the standards leave open. A crossing specification normally has to name both, because the product pipe is a pipeline before it becomes a drilled installation.

These pipeline design codes answer questions the HDD documents were never written to answer. The bore guide assumes a pipe that has already been designed; the pipeline code assumes a route that has already been engineered. The specification is where those two assumptions are reconciled, and it is where most of the practical risk is decided.

Match Every Deliverable to Its Governing Document Before You Write the Specification

An HDD design specification is easiest to build from deliverables: list what the project must produce, then attach the governing standard or document for each item. In our design reviews, the order matters: the document map below comes first, and the citation rules in the next section apply to the map it produces. Table 1 maps each HDD deliverable to the document that governs it, from bore geometry and installation loads to in-service pressure design, welding, field practice and the project-specific values no standard owns.

Deliverable	Governing document	What it covers, and what it does not
Bore geometry, entry and exit angles and reamed hole size for polyethylene pipe	ASTM F1962	Covers maxi-HDD placement of polyethylene pipe and conduit under obstacles, including river crossings, with guidance on geometry, loads and deflection. It does not set steel wall thickness or weld acceptance.
Installation loads and pipe stress during pullback	The same F1962 guide for the polyethylene pipe, with ASCE MOP 108 for the pipeline design side	Covers the installation load framework and the design of the pipeline for HDD installation. It does not replace in-service pressure design under the pipeline codes.
In-service pressure design and wall thickness for a steel pipeline	ASME B31.4 or ASME B31.8	Covers pipeline system design, pressure containment and allowable stress. It does not cover the HDD bore, reaming sequence or drilling fluid programme.
Welding procedures, welder qualification and weld acceptance	API 1104	Covers the welding of pipelines and related facilities and the acceptance of welds. It does not set crossing geometry or installation loads.
Field good practice by phase, from locating to pullback	NASTT HDD Good Practices Guidelines and DCA practice	Covers planning and field good practice across the crossing. It is guidance, not a code, and is not mandatory unless the contract references it.
Project-specific values, tolerances, records and acceptance tests	Owner or project specification	Covers exactly the figures and evidence that the standards deliberately leave open. It does not exist until the owner writes it.

Two points follow. First, the documents overlap and none covers a crossing end to end, so a specification that names one document leaves something unassigned. Second, the last row is the one projects forget: the project-specific values, the tolerances and the acceptance evidence exist only if the owner writes them down.

Table 1 also explains why the installation stress checks for the product pipe have to be read together with the in-service checks. The installation case and the in-service case use different allowable limits, so they have to be checked separately; a pipe can pass one and fail the other.

How Should Standards Be Cited Inside a Project Specification?

In an HDD design specification, a citation is a contract term rather than a bibliography entry. A citation in an HDD specification has to state which requirements are mandatory and what evidence proves compliance, not which standard the engineer read. We have seen tender packages quote a standard by title alone, leaving the contractor to choose the edition, the sections and the acceptance criteria. The gap is easy to test: a citation that survives the question “which edition, which sections, and what evidence closes it?” is ready to issue.

Citation element	What the specification should state	Why it matters
Designation and edition	The exact edition the design is based on, by designation and year, never the undated title alone	Editions change; an undated citation lets the reader choose which requirements apply
Applicable sections	Which sections or requirements are invoked, not just the document title	A guide contains both guidance and requirements, and the specification has to say which is mandatory
Deliverable and acceptance test	The calculation, drawing or record that demonstrates compliance	Without a testable deliverable, compliance is an opinion rather than a result
Companion documents	Which pipeline codes and owner documents also apply to the same item	Standards overlap, so the specification has to set the combination
Order of precedence	What governs when two documents conflict	Conflict between documents is a common source of claims
Records and evidence	What is submitted, when, and in what format	It ties the citation to something an inspector can check

Each of these citation elements has to be recorded in the specification, and the order of precedence between the HDD documents, the pipeline codes and the owner requirements has to be stated.

In our experience, owner specifications that name the edition, the deliverable and the acceptance test produce fewer disputes than those that name a standard and stop there. The citation discipline is unglamorous, and it is the difference between a specification that can be administered and one that has to be argued about.

Where the Standards Stop and the Project Specification Must Begin

Every standard here describes good practice in general; none of them sets the project-specific values, and that gap is what an HDD design specification exists to close. The items below are the ones a standard leaves open.

• Project-specific tolerances: tie-in tolerance, curvature limits and the cover on the alignment.
• Site-specific figures: separation from existing services, minimum cover under the crossed feature, and the scour allowance for a watercourse.
• Construction controls: drilling fluid containment, inadvertent return monitoring and the response plan if returns are lost.
• Installation stress checks: the components of pull load, the allowable limits that apply, and the rig margin required.
• Acceptance evidence: which calculations, survey records and test results are submitted, and by whom.
• Risk allocation: who carries the cost of a lost-returns event, a reamed-hole collapse or a re-drill.

The section also has to say what happens when the ground does not match the investigation. A specification silent on changed conditions leaves the most expensive decisions to be settled after mobilisation.

The documents named on this page are inputs to project-specific design; the design decision itself is made by the engineer for the actual crossing. The gaps this section lists are the items a specification has to fill, and they are the items we ask to see before we map a scope to the standards. Every value that governs the crossing has to be confirmed by a competent engineer against the geotechnical profile on that alignment.

Frequently Asked Questions

What does ASTM F1962 cover?

The F1962 guide covers the use of maxi-horizontal directional drilling to place polyethylene pipe and conduit under obstacles, including river crossings. It gives guidance on bore geometry, installation loads and the limits that apply to the polyethylene product pipe, and it is a guide rather than a prescriptive code.

Does ASTM F1962 apply to steel pipe?

The F1962 guide is written for polyethylene pipe and conduit; steel transmission pipe is governed by the pipeline codes, not by that guide. Steel wall thickness and in-service stress follow the pipeline design codes such as ASME B31.4 or B31.8, and weld acceptance follows API 1104.

Which edition of the standard should a project specify?

Specify the ASTM F1962 edition the design is actually based on, and state it explicitly in the basis of design. Editions such as F1962-22 and F1962-25 differ, and a revision work item is active, so an undated citation leaves the choice of edition to whoever reads the specification next.

Is one standard ever enough for a pipeline crossing?

An HDD crossing is covered by a set of documents rather than by one standard. Bore geometry, installation loads, in-service pressure design, welding and project tolerances sit in different documents, and the owner specification sets how they combine.

How should a project specification cite the standards it relies on?

Cite the designation, the edition, the applicable sections and the acceptance evidence, not just the title. A citation that names only a document leaves the reader to guess which requirements are mandatory and which are advisory.

Where do standards leave gaps that a specification must fill?

They leave the project-specific values open: tolerances, cover, separation, fluid containment and the records that prove compliance. A standard describes what good practice looks like in general; only the specification can say what is acceptable on this crossing.

Key Takeaways

• The F1962 guide governs the placement of polyethylene pipe and conduit by maxi-HDD under obstacles, including river crossings, and it is a guide rather than a code.
• The edition matters: confirm whether F1962-22, F1962-25 or a later edition applies, and record that in the basis of design before the design is frozen.
• ASCE MOP 108, the NASTT HDD Good Practices Guidelines and DCA practice cover the pipeline-design and field-practice sides that the bore guide leaves open.
• Pipeline design codes and welding standards sit alongside the HDD documents, and the specification has to state how they combine.
• A usable citation states the designation, the edition, the applicable sections, the deliverable and the acceptance test.
• The project-specific values and records exist only if the specification creates them, and they must be confirmed by a competent engineer for the actual crossing.

How JSW Supports HDD Design Standards and Specifications

JSW is a pipeline engineering and construction company that plans and builds trenchless crossings with its own engineering team, crews and equipment. Alongside the crossing itself, JSW delivers HDD crossing services, trenchless technologies and บริการติดตั้งท่อส่ง. The pipe string is produced by automatic pipeline welding and pipeline cold bending, so specification and fabrication share one basis.

Because our design team and our construction crews work to the same engineering basis, the HDD design specification we produce reflects what the equipment and the crews can actually deliver. We write the standard clauses, the deliverable list and the acceptance evidence into the same document, price risk items with their triggers, and hand over calculations and as-built records that match what was built.

• Integrated delivery: route review, HDD design specification, installation stress checks, pipe string fabrication and pullback sit in one scope, which removes the interface risk between designer and constructor.
• Auditable engineering: calculations, fluid plans and installation records are documented for construction review and for later integrity management.
• Risk-explicit pricing: contingencies and the conditions that trigger them are stated beside the deliverable they relate to, not absorbed into a lump sum.
• Crossing experience: watercourse, road and rail crossings and congested urban corridors, with permitting and reinstatement inside the scope.