Directional Drilling Insurance in Maryland

Two provisions make Maryland different from its neighbors for a directional drilling contractor, and neither is about money. The first is that the statute defines the cross-bore — the failure that horizontal drilling invented and that most states have never named. The second is that an excavator who works without a ticket is deemed negligent by the statute itself, before anyone has argued about fault.

What follows is Title 12 of the Public Utilities Article as it bears on a fiber bore: what the definitions reach, the start-work band and what the ticket has to disclose, the standing Authority that hears complaints and can sit without you, the penalties and the three-year rule that decides whether an old matter still counts, and where the contract statute speaks and where it goes quiet. Title 12 sets the band, the hearing and the lookback. The work all three are measuring is on the Directional Drilling Insurance pillar and the pollution liability page.

The statute names the failure that finds you late

Public Utilities §12-101 carries a definition that almost no other damage prevention statute carries. A cross-bore is defined as an intersection of an existing underground facility by a second underground facility resulting in contact between the two facilities that results in the original facility being damaged, dislocated, or disturbed.

That is the horizontal drilling loss written into law. A bore driven through an existing lateral does not announce itself: nothing surfaces, nothing goes dark, and the crew finishes the shot and moves down the route. The damage is found later — when the compromised facility is cleared, or when it fails — and by then the questions are documentary. What did the locate show. Where was the mark relative to the facility as found. What depth was recorded on that rod.

Two other definitions in the same section tell you the legislature was thinking about locates as evidence. Clear evidence means a visible indication that an underground facility or structure is not marked as required under §12-126. A contract locator is a person contracted by an owner specifically to determine the approximate horizontal location of the owner’s facilities as specified in the ticket issued by the one-call system. The statute distinguishes between what was marked, what was visibly not marked, and who was retained to decide — which is the same three-way distinction a claim file has to resolve years later.

The reach of the Act over fiber is settled in the same section. An underground facility is an item buried, placed below ground, or submerged for use in connection with the storage or conveyance of water, sewage, oil, gas, or other substances, or the transmission or conveyance of telecommunications, cable television, or electricity. And excavation means an operation in which earth, rock, or other material is moved, removed, or otherwise displaced using any tool, equipment, or explosive, expressly including grading, trenching, digging, ditching, dredging, drilling, boring, augering, tunnelling, scraping, cable or pipe plowing, pipe bursting, and driving a mass of material. Boring and cable plowing are both named.

A start-work date you choose, inside a band

Maryland does not express its notice requirement as a waiting period. Under §12-124(a), before performing excavation or demolition a person must initiate a ticket request with the one-call system serving the area, and must select a start work date that commences not sooner than 3 business days after the ticket is initiated and not later than 12 business days after the ticket is initiated. A business day is a calendar day other than a Saturday, Sunday, or legal holiday.

The practical difference between that and a simple waiting period shows up on a route worked in segments. The band runs from the moment the ticket was initiated, and the date you nominate has to fall inside it. Work that slides past the twelfth business day is not late in the sense of being tardy — it is outside the ticket, and the ticket is the thing §12-135 measures you against.

What the ticket has to say is broader than where you are digging. Section 12-124(b) requires the notice to indicate the location of the proposed work, the type and extent of work to be performed, and — the item most often missed on a linear build — whether the work is within rights-of-way owned or controlled by the Department of Transportation, an administration of the Department of Transportation, or the Maryland Transportation Authority, and if so, the entity and the permit or authorization number obtained from it. A fiber route along or across a state highway is inside that provision, and the permit number belongs on the ticket rather than only in the project file.

Section 12-124(a)(3) supplies a mechanism worth knowing when a specialty crew joins a route someone else opened: a person may add a temporary excavator to an existing ticket. A bore subcontractor arriving mid-project does not necessarily need its own ticket, but it does need to be on one, and being on one is a documented act rather than an assumption.

Deemed negligent, before anyone argues

Section 12-135(a)(1) is the provision that should change how a Maryland crew treats its paperwork. A person that performs an excavation or demolition without first providing the notice required under §12-124(a) is deemed negligent and is subject to a civil penalty assessed by the Authority.

The word is deemed. The statute does not say the failure may be considered evidence of negligence, or that it creates a presumption a contractor can rebut with proof of care. It characterizes the conduct. In a damage claim arising out of an unticketed excavation, the argument does not begin at zero — it begins with a statutory label already attached, and the care the crew genuinely exercised is offered against that label rather than in place of it.

There is no cure for it afterwards, either. A ticket pulled after the fact does not retroactively satisfy a requirement expressed as something to be done before performing the work. This is the reason a missing or expired ticket is a coverage-relevant fact and not merely a compliance one: it changes the posture of the underlying liability claim that the policy will be asked to respond to.

The Authority hears it, and can sit without you

Enforcement runs through the Maryland Underground Facilities Damage Prevention Authority rather than through a court in the first instance. Under §12-112, the Authority accepts and reviews complaints for violations of the subtitle and may recommend necessary enforcement actions. It hears complaints either at the request of a probable violator or after notifying a probable violator that it has scheduled a hearing on its own motion, and after a hearing it assesses a civil penalty under §12-135. It may also reach a settlement instead of assessing a civil penalty.

And then the provision that decides how seriously a notice of hearing should be taken: if a probable violator fails to appear at a scheduled hearing, the Authority may vote to proceed to hear the complaint in that person’s absence. A contractor that ignores the notice does not delay the matter. It loses the only opportunity to put its own record in front of the body that will decide.

Two thousand, four thousand, and a three-year clock

The dollar amounts are modest, which is exactly why the rest of the section matters more. Under §12-135(a)(3), the civil penalty for failing to give notice may not exceed $2,000 for the first offense and $4,000 for each subsequent offense; §12-135(a)(4) applies the same ceilings to a violation of any other provision of Part IV of the subtitle.

How the number is reached is the part a contractor can influence. Section 12-135(a)(2) requires the Authority to calculate the penalty considering the severity of the violation, the intent and good faith of the violator, and the past history of violations. Good faith is a listed input rather than an argument made in mitigation, which means the documented existence of a damage prevention program is relevant to the assessment itself.

Section 12-135(a)(5) gives the Authority an alternative to money altogether: instead of or in addition to a civil penalty it may require a person to participate in damage prevention training, to implement procedures to mitigate the likelihood of damage to underground facilities, or may impose other similar measures. For a growing crew, an order to build procedures is a more consequential outcome than a four-thousand-dollar assessment, and it is one the Authority can reach directly.

The three-year rule, and the two ways it fails to help you. Under §12-135(a)(6), the Authority may not treat an offense as a subsequent offense if it occurred at least 3 years after the earlier offense — unless the earlier offense is unresolved, regardless of the age of the earlier offense, or the person has not met the conditions of an assessed penalty. The reset is real, but it belongs only to a contractor that actually closed the earlier matter out. An old unresolved complaint stays live by the statute’s own words, and an ordered training that was never completed keeps a file open that the calendar would otherwise have retired.

Settled before the crew mobilized

The contractors who reach us in Maryland are usually mid-project, holding a certificate a prime has refused and an agent who cannot explain why re-issuing it will not help. Most of the argument here was settled before the crew ever mobilized. Because §12-135(a)(1) attaches a statutory characterization to an unticketed excavation, and because a cross-bore defined in §12-101 surfaces as a claim long after demobilization, the initiation timestamp on the ticket carries more weight than anything produced afterward. Start with the ticket and its date.

Pollution liability is the placement Title 12 never touches. The subtitle governs damage to facilities and the penalties for causing it; drilling fluid surfacing into a stream, a tidal reach or a storm system is an environmental loss the general liability form excludes. Contractors equipment matters because an order to implement procedures under §12-135(a)(5) reaches how you work rather than what you owe, and because the statute addresses your exposure to the facility owner and says nothing about your own rig. General liability is specified against the contract, for the reason set out immediately below.

A statute that reaches your defense costs, and a question it leaves open

Maryland’s anti-indemnity statute does something most do not, and the part it does is worth reading before signature.

Two obligations, addressed separately. Courts and Judicial Proceedings §5-401(a)(1) voids as against public policy a covenant in a contract relating to architectural, engineering, inspecting, or surveying services, or the construction, alteration, repair, or maintenance of a building, structure, appurtenance or appliance, including moving, demolition, and excavating connected with those services or that work, that purports to indemnify the promisee against liability for damages caused by or resulting from the sole negligence of the promisee or indemnitee. Subsection (a)(2) then separately voids a covenant purporting to require the promisor to defend or pay the costs of defending the promisee against liability for damages resulting from that same sole negligence.

That separation is not cosmetic. The duty to defend and the duty to indemnify are different obligations that arrive at different times — the first when a claim is made, the second if liability is established — and in states that void only indemnity, a contractor can find itself funding a defense for years in a matter it will ultimately owe nothing on. Maryland names both.

The line is sole negligence, and that is a narrower line than some neighbors draw. Where the promisee is partly at fault and the promisor is also at fault, §5-401 is not what answers the question, and a broad indemnity clause can survive it. Subsection (a)(3) also preserves the validity of insurance contracts, workers’ compensation, and a general indemnity agreement required by a surety as a condition of executing a bond — so the bond paperwork on a public job is outside what this section voids.

Where it stops. What remains unsettled is whether a fiber bore sits inside that enumeration at all. The words the legislature chose describe buildings and the things attached to them, with excavation drawn in by its connection to that work — and a bore under a highway shoulder is some distance from that picture. We have not located a Maryland decision construing that language as applied to utility, linear or fiber work, and we will not invent one by inference. Everything above this paragraph is on the page because the statute says it. This last question is on the page because it does not, and a broad indemnity clause in your subcontract is therefore a document to read closely rather than a risk the statute has already handled for you.

Title 12 sets a start-work band, an Authority hearing and a three-year lookback. None of that describes a contractor licensing position, the Maryland markets or the non-drilling crews, and all three are on our Maryland fiber contractor insurance page.

Why Fiber Optic Guard Insurance

What we actually do on a Maryland file: confirm the start work date falls inside the three-to-twelve business day band measured from ticket initiation, because §12-135(a)(1) attaches its characterization to the absence of that notice and nothing later cures it; check that a state highway route carries its permit number on the ticket itself under §12-124(b); make sure a bore crew arriving mid-project was added as a temporary excavator rather than assumed onto someone else’s ticket; build the locate file for a cross-bore claim that will arrive late, because §12-101 tells you the legislature expects that event; and read the subcontract against what §5-401 actually voids, remembering that it stops at sole negligence and separately reaches the defense obligation. If your contract carries a broad indemnity or defense clause, send it.

Frequently asked questions about Maryland directional drilling insurance