Tightness testing in Panama: method, scope and procedure

A tightness test evaluates an identified system under a method’s conditions. For useful decisions, the report should separate three things: technical scope, test result and the procedure before the authority.

What the scope should identify

The document should state the evaluated tank, line or component, product, capacity, relevant conditions, equipment and method. A visual inspection may detect damage, water or corrosion, but it is not a tightness test.

How MESA 2-D works

According to the consulted independent evaluation, MESA 2-D is nonvolumetric. It applies vacuum to the tank ullage, listens for acoustic signals that may indicate air ingress and uses a separate sensor to detect water ingress.

What the published rate means

The listing records evaluated performance at a leak rate of 0.1 gallon per hour, with 100% probability of detection and 1.6% probability of false alarm, under the stated conditions. It is not an individual volumetric measurement or a universal Panama regulatory obligation.

Who decides certification

Panamá Digital identifies the Fire Department, through DINASEPI, as the entity that inspects and certifies operation of fuel-storage facilities. A BCBRP document revised in 2014 calls the procedure an annual inspection and states a one-year validity; confirm the current scope with DINASEPI.

When to evaluate again

There is no universal answer for every system. The need may arise from the applicable procedure, an intervention, a finding, history or the response plan. Before scheduling, confirm the current requirement and which components must be included.

If the result does not meet the criterion or is inconclusive, review the report, follow the facility response procedure and define the next step. The test does not always locate the ingress or release point by itself.

From the objective to a verifiable scope

Begin by writing the question: does the site need one tank assessed, a line, a group of assets or a response to an observation? Identify each component by number, product, capacity, location and connection to dispensers. The provider should return the same identification in the report. This discipline prevents a broad phrase such as “station test” from hiding exclusions.

If MESA 2-D is proposed, compare the system against published conditions and record which ones applied during the visit. The published 0.1-gallon-per-hour rate and probabilities describe the independent evaluation under defined conditions. They are neither a measured rate in every tank nor a Panamanian legal tolerance.

Controlling the site visit

• Confirm safe access, asset identity and operational authorization.
• Record product, level and recent events that may affect testing.
• Verify equipment status and the applicable procedure version.
• Document start, interruptions, abnormal conditions and closeout.
• Keep the result separate from any later diagnosis.

Our technical preparation guide helps collect information without altering the system to seek a particular result. Preserve and investigate alarms instead of clearing them to make a console look clean.

After the result

A favorable result is filed with scope and limitations. An adverse or inconclusive one requires review of data, conditions and exclusions before deciding on repairs. The adverse-result response guide keeps the finding separate from its cause.

For the facility file, connect the report, photographs, work order and any later closeout. The Fire Department requirements sheet is a starting point, but its currency must be confirmed for the specific procedure.

Frequently asked questions

Is the technical test the certification?

No. It contributes evidence within a scope. BCBRP/DINASEPI performs the inspection and determines the procedure.

Does one test include tanks and lines?

Only when the scope and method expressly say so. Do not infer coverage from the report title.

Can a favorable result be guaranteed?

Not responsibly. Preparation, method and documentation can be controlled; the condition of an unevaluated system cannot be promised.

Application record: tightness-testing scope

Before applying this guide to a facility, identify each included or excluded tank, line and component. Write the decision as a verifiable question: which criterion the method assesses and which procedure the report supports. A recommendation without an asset, question and date is difficult to audit and may continue circulating after the facility has changed.

• Input: listing, conditions, data, result and consulted authority.
• Source: retain the title, issuer, edition or date, link and section used.
• Owner: assign who confirms data, who authorizes action and who verifies closeout.
• Status: use confirmed, pending, not applicable or out of scope; do not fill evidence gaps by assumption.

Retain the version that supported the decision and record differences between the plan and field conditions. If the objective changes, an asset is repaired or the result is inconclusive, reopen the record instead of reusing the earlier conclusion. This keeps the article a working framework rather than a substitute for the manual, design, risk assessment or responsible authority.

Continue learning in Master University. To review a real case, share the inventory, legible photographs, objective and available documents through our contact page; a responsible technical recommendation begins with scope.