Third-Party Inspection Services in Basrah, Iraq: API Mechanical Integrity Support, NDT Witness Points and Manpower Supply for Upstream and Export Facilities

What Third-Party Inspection in Basrah Actually Involves

On a Basrah contract, third-party inspection means an independent party — contracted by the operator, EPC or buyer rather than by the equipment supplier or fabricator — verifies that materials, welds, fabrication and testing meet the purchase order, the inspection and test plan (ITP), and the governing code before the item is released for shipment or put into service. The work is structured around hold points (inspection cannot proceed until the third-party inspector signs off) and witness points (inspection may proceed on notice but the inspector has the right to attend), both defined in the project's ITP using terminology that buyers and suppliers often use inconsistently if it isn't pinned down early in the contract.

In practice this covers document review (material certificates, weld procedure qualification records, NDT procedures and personnel certification), witnessing or performing NDT (UT, RT, PAUT, MT, PT, visual) at the fabrication or field stage, dimensional and visual inspection against drawings, and reviewing final test results (hydrotest, PMI, hardness surveys) before a release note or certificate of conformance is issued. Basrah campaigns typically bring this scope to fabrication yards, gathering and pumping stations, tank farms and pipeline tie-in points rather than a single facility, since the export supply chain runs across several yards and field locations feeding the terminal system.

Basrah's Industrial and Equipment Base

Basrah is Iraq's principal oil export gateway: crude gathered from the southern fields is processed, metered and pumped through trunk pipelines to the export terminals on the Gulf, with degassing stations, water injection plants and gas-oil separation facilities distributed across the gathering network in between. That produces a fairly consistent equipment population across the region — wellhead and Christmas tree assemblies, gathering and trunk pipelines, pressure vessels and separators at GOSPs, atmospheric storage tanks at tank farms, pumping station piping, and the tie-in and metering skids that connect field infrastructure to the export system. Fabrication and repair work for this equipment is usually carried out at yards in and around Basrah city and the Khor Al-Zubair industrial corridor, which is where most third-party inspection scopes are executed rather than in the field itself, though field NDT (pipeline girth welds, in-service tank floor scanning, hot-tap welds) is a routine part of campaigns as well. The coastal, high-humidity, high-chloride environment near the Shatt al-Arab and the Gulf adds an external-corrosion dimension to almost every carbon steel asset in the region, on top of the internal degradation driven by produced water and sour service in parts of the gathering network.

Codes and Standards Governing This Equipment Mix

Given that equipment population, the codes that actually govern Basrah inspection scopes cluster tightly: API 6A for wellhead and Christmas tree pressure-containing equipment, API 5L for line pipe material and API 1104 for pipeline and flowline girth-weld fabrication and NDT acceptance, ASME B31.3 for process piping inside gathering and pumping stations and ASME B31.4/B31.8 for the pipeline systems themselves, API 510 for pressure vessels, API 653 (with API 650 for new construction) for atmospheric storage tanks, and API 570 for in-service process piping once a facility is operating rather than under construction. NDT method procedures sit underneath these — ASME Section V governs the NDE methods themselves, ASME Section IX governs welding and brazing procedure/personnel qualification, and ASNT SNT-TC-1A or ISO 9712 govern the certification of the personnel performing the UT, RT, PAUT, MT and PT. A full reference set for how these interlock, including where a client's own engineering specification adds requirements on top of the base code, is on the standards page. The practical point for a Basrah scope of work is that the applicable code should be named explicitly per equipment class in the ITP — 'API code inspection' by itself is not specific enough to write acceptance criteria against.

What a Defensible Release and Inspection Report Package Contains

A release package that will hold up under a partner audit, an insurer's review, or a later fitness-for-service question needs more than a pass/fail stamp. At minimum it should carry: the signed ITP showing which hold and witness points were exercised and by whom; material test reports (MTRs) traceable to heat/lot number; welding procedure specifications and procedure qualification records (WPS/PQR) matched to the actual joints welded, with welder qualification records for each welder whose stamp appears on the weld map; the NDT procedures used, with technique sheets, calibration records for the equipment (including current calibration block traceability), and the actual UT/RT/PAUT/MT/PT reports with sketches or weld maps showing indication locations; PMI results where alloy verification is in scope; hydrotest records with pressure, hold time and medium; and a final punch list showing every open item closed or formally dispositioned before the release certificate is signed. Where an indication or a thickness reading falls outside acceptance criteria, the package should show how it was dispositioned — repair, reject, or engineering evaluation — rather than simply noting the deviation. A defect that gets accepted through engineering judgment rather than repair is exactly the case where a documented fitness-for-service assessment under API 579 belongs in the file, not a verbal sign-off.

How Atlantis Deploys an Inspection Team for a Basrah Campaign

Atlantis mobilizes inspectors and NDT technicians from its Houston and Hyderabad teams for the duration of a Basrah contract, with the team sized to the campaign's scope and demobilized once the contract closes rather than maintained indefinitely. A typical engagement starts with scope and ITP review against the client's purchase specification, confirmation of which codes and acceptance criteria apply per equipment class, and matching of technician certifications (method, level, and any client- or AIA-specific written-practice requirements) to the work before mobilization. The team then executes the assigned hold and witness points at the fabrication yard, gathering station, tank farm or pipeline right-of-way for the contract period, reporting through the client's or the EPC's document control system so that release documentation is generated and reviewed in step with the fabrication schedule rather than reconstructed after the fact. Demobilization happens once the scope is closed out and the report package is delivered complete — the deployment is sized to the contract's duration and equipment count, not left open-ended. Projects that also need a broader quality or reliability layer around the inspection scope — write-up of an inspection and test plan, procedure development, or a risk-based inspection programme feeding future inspection intervals — are handled through Atlantis's consulting practice alongside the field deployment.

Manpower Supply for API Inspection Programs

A separate and more common request from operators and EPCs running their own API 510, API 570 or API 653 mechanical integrity programme in Basrah is technician supply rather than a full inspection contract: Atlantis provides qualified NDT technicians and inspection support personnel — UT, PAUT, RT, MT, PT, certified to ASNT SNT-TC-1A or ISO 9712 — to augment the client's existing programme for the length of a turnaround, a defined project, or an ongoing multi-month scope, working under the client's or their Authorized Inspection Agency's (AIA) written practice and procedures rather than under a separate Atlantis inspection scheme.

This is technician supply and inspection execution support — it is not placement of an Authorized Inspector. Atlantis is not an API Authorized Inspector and does not act as inspector of record on any API 510, 570 or 653 programme; that role, and the associated sign-off authority, stays with the client's own API-credentialed inspector or their AIA. What Atlantis supplies is the certified hands performing the UT thickness surveys, PAUT weld scans, RT exposures, and MT/PT surface examinations that feed the inspector of record's assessment, plus the technical support to keep that execution consistent with the programme's written practice.

Three engagement shapes come up most often in Basrah: turnaround crew augmentation, where a fixed roster of technicians mobilizes for a planned shutdown window and covers a defined thickness-survey and weld-inspection scope alongside the client's core team; multi-month programme staffing, where technicians are embedded for the length of an ongoing inspection interval, typically tied to a facility's RBI-driven inspection schedule; and short-notice mobilization, where a smaller crew deploys on compressed lead time to cover an unplanned outage, an emergent repair, or a gap left by an unavailable resource. Programmes considering a formal ASNT Level III oversight layer on top of technician supply — procedure review, personnel qualification audits, programme gap assessment — can pair this with Atlantis's ASNT Level III consulting rather than treating manpower supply and programme oversight as the same scope.

Damage Mechanisms Relevant to Southern Iraq Oil and Gas Assets

The damage mechanisms that show up most often on Basrah inspection scopes track the region's process chemistry and climate rather than being generic. Produced water with dissolved CO2 and, in parts of the gathering network, H2S drives internal corrosion and pitting in flowlines, separator internals and low points in gathering piping — exactly the profile UT thickness mapping and PAUT corrosion-mapping scans are set up to catch. External corrosion under insulation (CUI) on insulated vessels and piping, and coating breakdown on buried or partially buried pipeline sections in the high-humidity coastal environment near the Shatt al-Arab, are recurring findings independent of what's happening inside the pipe. Erosion at chokes, control valves and other flow-restriction points is common where sand production accompanies crude, and weld-related degradation — heat-affected-zone cracking, incomplete fusion missed in original fabrication, or fatigue cracking at vibration-prone small-bore connections — shows up disproportionately on older gathering infrastructure. Where a facility's inspection intervals are set by a formal risk-based programme rather than fixed calendar dates, matching the NDT scope to the mechanisms actually active at each location is the difference between a risk-based inspection (RBI) programme that catches damage early and one that just repeats the same UT grid every turnaround; Atlantis's RBI programme design work exists for facilities that want that scope defined properly rather than inherited from a template.

Documentation and Traceability Requirements

Because Basrah campaigns typically span multiple fabrication yards and field locations feeding one export system, traceability discipline matters more than on a single-site job. Every NDT report needs to tie back to a specific joint or component identifier on the weld map or line list, every technician's certification needs to be current and matched to the method and level stamped on the report, and every piece of NDT equipment (UT flaw detectors, RT sources or generators, MT yokes, calibration blocks) needs a calibration record that's traceable to a recognized standard and current for the inspection date — not just current at the start of the contract. Chain-of-custody matters too: RT film or digital radiographs, PAUT data files, and MT/PT records should be retained and indexed in a way that lets a specific weld be pulled back up months or years later if a failure investigation or an insurance claim requires it. For programmes bringing on outside technicians, verifying that certification records, procedure qualifications and equipment calibration are actually current — not just presented as current — is a standard part of scope definition, and it's the kind of gap an ASNT Level III review catches before it becomes a finding in someone else's audit.

What to Specify in a Basrah Inspection Scope of Work

A scope of work that avoids disputes mid-contract names the applicable code per equipment class rather than a blanket reference, states hold points and witness points separately with the notice period the fabricator or field crew must give before each (a common baseline is 24 to 48 hours' notice for a witness point, though the client's own ITP governs), specifies the NDT methods and acceptance criteria per weld or component category rather than leaving them to be inferred from the base code, and states explicitly what happens on a rejectable indication — repair-and-retest, reject, or route to engineering evaluation — so the inspector isn't making that call unsupported in the field. It should also state language and reporting requirements (report format, turnaround time for report delivery, and who receives copies), and, where technician supply rather than a full inspection contract is intended, should state that clearly so the roles of inspector of record and supporting NDT technician aren't blurred in the contract language. Operators and EPCs scoping a Basrah campaign, whether it's a full third-party inspection contract or technician augmentation of an existing API programme, can work through the scope directly with Atlantis via contact.

Request a consultation