IC TRACK · INTRODUCTION TO INTERNAL CORROSION

Introduction to Internal Corrosion: Types and Consequences

What internal corrosion is, why it differs from external, and what's at stake when we miss it.

Basics & Theory ~10 minutes PDH/CEC eligible

Why this module exists

First time at the pig receiver

You get the call mid-morning. A pig tool just finished a run, fluids and solids are coming out of the receiver, can you grab samples for IC analysis? You drive over with whatever’s in the truck — maybe a real sampling kit, maybe a stack of clean bottles and a notebook. The operator cracks the receiver, and out comes the gunk: dark sludge, water with a faint smell, scale flakes, maybe a sulfur tang in the air.

Now you’re standing there making decisions:

What do you test right here, before it changes?
What do you bottle up to send to the lab?
What do you tell the lab to look for?
What does any of this tell you about what’s happening inside that pipe?

For most techs, this is the moment internal corrosion stops being abstract. Outside of a planned dig, you don’t get to look at the steel. You get a sample in your hand, a chain-of-custody form to fill out, and a list of questions you don’t yet know how to ask.

The chemistry inside that bottle starts changing the moment the pig leaves the receiver. Dissolved gases start escaping. Oxygen creeps in. Bacteria die or multiply depending on what you put them in. The lab gets a sample that doesn’t quite represent what was in the pipeline an hour ago. Field testing on-site catches the fluids before that change — and that’s a thread we’ll come back to a lot in this set of modules and beyond.

This whole set is built to make the next pig-receiver call feel less lost. By the time you finish the eighth module here, you’ll be able to look at what came out of a receiver, ask the right questions, and start matching what you see to what’s likely driving the damage. Later in the track, a whole group of modules is dedicated to sampling methods specifically — but that comes after you understand what you’re actually sampling for.

That’s what this module sets up. A working idea of what internal corrosion is, who works on it, where it shows up, and why getting it right matters. The opener earns the rest. Let’s go.

What internal corrosion is, in plain English

Definition. Internal corrosion is the deterioration of pipe metal driven by the chemistry of the fluids inside the line. The inside part is what makes it a separate animal from external corrosion.

External corrosion follows the soil, the coating, and what’s happening on the outside surface of the pipe. Internal corrosion follows the gases, the fluids, and the solids — what’s flowing through, what’s settling out, what’s reacting with the steel. Same kind of metal loss outcome in the end. Same kind of failure. But a completely different cause map, a different toolkit, and often a different team running the work.

Pipeline operators manage both. Many companies have an external corrosion group and an internal corrosion group that talk to each other but run separate programs. RCS works on both sides — there’s a full External Corrosion track here if your work covers that side too. This track is about the inside half.

Water is everywhere it can be

If you’re trying to figure out where internal corrosion can happen in a line, start by asking where can water collect. That single question narrows the search by a lot. Water vapor condenses on cool pipe walls. Producers have liquid upsets that show up downstream as a slug of water in a “dry” gas line. Sales-quality crude still carries a fraction of a percent of basic sediment and water. Tank bottoms hold water that eventually moves out into the connected pipelines. The reservoir didn’t come up dry, the storage field didn’t deliver dry gas in late season, and the dehy unit isn’t perfect.

If there’s water collecting somewhere, there’s a place corrosion can happen. The fluids in the line bring the chemistry; the water brings the reaction.

Threat versus problem

Two words worth pinning down before we go further. A corrosion threat is a mechanism that could damage the asset. A corrosion problem is when that threat damages the asset to the point it can’t safely do its job. The whole job of internal-corrosion work is to keep threats from becoming problems — through assessment, mitigation, and monitoring. Those three actions are the spine of this whole track, and we’ll come back to them more than once.

The four big drivers

When techs encounter internal corrosion in the field, it usually comes back to one (or a combination) of four big chemical drivers. We’re naming them here — not teaching them. Each one gets its own deep-dive module ahead. The point of this section is to make sure you know the categorical landscape before the rest of the set walks you through it.

CO₂ (sweet). Carbon dioxide dissolves in water and forms a weak acid that’s surprisingly aggressive against carbon steel. Most common acid-gas corrosion in upstream production and wet-gas gathering.
H₂S (sour). Hydrogen sulfide dissolves in water to form another weak acid — and brings a second problem on top: it lets atomic hydrogen enter the steel itself, which drives a whole family of cracking and blistering damage beyond just metal loss.
O₂ (oxygen). Oxygen has no business in most of these lines, but it sneaks in anyway — through process upsets, leaks upstream of pumps, tank breathing, injection chemicals, recently opened lines. Even ppb levels can be aggressive. And oxygen amplifies almost every other mechanism on this list.
Bacteria (microbial). Microbes live in produced fluids, soil, water, even on the inside of pipelines. Some produce H₂S as a metabolic byproduct. Some produce organic acids. Some just trap moisture and create concentration cells. Microbiologically influenced corrosion (MIC) is estimated to drive a meaningful share of internal pipeline failures.

Two more things show up alongside these four often enough to name them here. They’re not separate drivers — they’re recognition cues:

Erosion-corrosion — when high-velocity fluid, sometimes with entrained solids, peels off the protective films that would otherwise slow the corrosion reaction. Common at elbows, tees, valve outlets, pump discharges.
Top-of-line corrosion (TLC) — a wet-gas phenomenon. Water vapor condenses on the cool top of a horizontal pipe, dissolves CO₂ from the gas, and corrodes the 12 o’clock position aggressively. Inhibitor at the bottom of the pipe can’t reach it.

Two damage modes at survey level

The damage you see from any of these drivers tends to fall into two big patterns:

Uniform metal loss — the pipe wall gets thinner more or less all over. Easier to predict, easier to manage with a corrosion allowance, easier to catch with a wall-thickness inspection.
Localized attack — pits, cracks, mesa-shaped patches concentrated in spots. Harder to predict, harder to find, and disproportionately dangerous because all the damage gets concentrated in a small area of pipe.

That’s the framing for now. Each driver, each damage mode, each pattern gets a full module later in this set. The point here is not to teach the chemistry — it’s so the next time you hear “the gathering line has a sweet corrosion issue at the inlet separator” you know roughly what that means and which module in the track is going to fill in the rest.

Where it shows up across pipeline services

Different pipeline services have different threat profiles. A field tech can narrow down the likely drivers before opening a line, before sampling, before sending anything to the lab — just by knowing what the line carries and how it operates.

Production and gathering

Wet, mixed fluids — water, oil, gas all flowing together. Water cut starts low when a field is young and rises over the field’s life. Once the water cut is high enough that water wets the pipe surface, every driver on the list is in play: CO₂ corrosion if produced gas has CO₂, H₂S corrosion in sour service, MIC and under-deposit attack anywhere water and solids accumulate, and cracking damage where H₂S is high enough. Oxygen is usually rare here (the reservoir is anaerobic), but it can sneak in through leaks upstream of pumps or with injected fluids.

Production and gathering have the highest threat profile of any service category. They also have the most variability — every well, every pad, every gathering system has its own chemistry, flow regime, and operating pattern.

Transmission (gas, oil, refined products)

Transmission lines carry “sales-quality” gas that’s already been processed somewhere upstream. Tariff agreements set what producers can deliver into the line at each sales point — every operator writes their own, and actual values vary line by line. Rough industry-typical orientation magnitudes look something like this:

Gas: CO₂ in the low single-digit mol% range, H₂S in single-digit parts-per-million by volume, water vapor in the single-digit pounds per million standard cubic feet, oxygen below half a percent
Crude oil: basic sediment and water (BS&W) generally a fraction of a percent
Refined products: similar order-of-magnitude limits per product

Two governance systems run in parallel here — don’t confuse them.

The tariff agreement is the gas-quality contract at each sales point. Producer delivers gas out of spec → producer gets shut in until they fix it. Tariffs are negotiated company-to-company; sometimes brief out-of-spec gas gets accepted for business reasons. Above the tech’s head.

The IC program is the operator’s system-wide corrosion governance. Broader than any single tariff. Sets sampling cadence, when to add coupons, when to escalate to remediation. The IC program can be stricter than the tariff (and often is) but never looser. This is what you actually work against day to day. Know the tariff for context; let the IC program tell you what to do.

Mostly clean and dry, but upset conditions matter. Producers can deliver gas that’s briefly out of spec. Tanks upstream can pass slugs of water through. Pressure cuts at sales points can drop temperature into condensation territory. And “black powder” — fine iron sulfide particles from H₂S reacting with steel upstream — accumulates in some transmission systems and clogs filters and meters even though the gas is technically within spec.

Oil transmission deals primarily with under-deposit attack and microbial activity at low points and in dead legs. Refined-product transmission is generally cleaner, but rainwater entering a floating-roof tank can introduce oxygen and shorten the corrosion-free runway downstream.

Facilities, processing, and storage tanks

Inside a processing facility — separator vessels, dehydration units, treaters, storage tanks — threats vary by piping section. Some piping flows constantly. Some is normally shut-in (operational dead legs). Some is permanent dead leg from a removed pump or vessel that was never disconnected. Stagnant sections are MIC and under-deposit magnets. Utility lines carrying methanol, glycol, or process chemicals have their own profiles.

Above-ground storage tanks accumulate water and sediment in the bottom over time. The water is the corrosion threat, not the oil or refined product above it. Tanks with floating roofs can take in rainwater (which carries dissolved oxygen). Tank bottoms get the worst of all of it — water, sediment, sometimes biofilm — with poor mixing.

Where to look in the field — quick scan

Pulling it all into a recognition cheat sheet:

6 o’clock of horizontal sections — water and solids settle here
Low points in elevation — water collects, anything pigging missed accumulates
Dead legs and bypass lines — no flow, biofilms thrive
Drips on gas lines — designed liquid catches that don’t always get cleaned
Tank bottoms — water and sludge layer above the steel
Top of cool wet-gas lines — TLC at the 12 o’clock
Downstream of pressure cuts — temperature drop into condensation territory
Recently opened sections after maintenance — possible oxygen excursion

Knowing the service type narrows the kind of drivers in play. Knowing where to look within that service narrows where to find them. Together they make the next pig-receiver call, sample call, or inspection dig a lot less random.

Why this matters

You’re already in this work, so we’re not going to lecture you on why pipeline integrity matters. The point of this section is to put a few concrete numbers and frameworks around it so the rest of this set lands with the right weight.

The safety side

Most internal corrosion failures aren’t catastrophic blowouts. They’re slow leaks discovered during routine inspection — and that’s exactly what makes inspection programs valuable. The tech’s job is finding the developing problem before it becomes a release event.

The headline incidents are the rare ones. Bellingham, Washington, 1999 — a gasoline pipeline ruptured, the spill ignited, three people were killed including two ten-year-old boys playing near the creek. Carlsbad, New Mexico, the next year — a 30-inch natural gas transmission line ruptured and twelve people lost their lives. The NTSB attributed the Carlsbad failure specifically to internal corrosion. Those events are why the regulatory framework around internal corrosion exists. They’re the reminder that what looks like a slow, quiet problem can turn loud in a hurry.

Day-to-day, IC work happens before any of that. The tech is the one taking the samples, pulling the coupons, walking the sites — finding the developing problems while they’re still small.

The asset and cost side

Pipelines are long-lived capital assets. A buried transmission line is engineered for decades of service, and the operator’s whole business model assumes those decades happen. Internal corrosion is one of the biggest things that takes years off the back end of an asset’s life. Catching a corrosion problem early means you fix it cheap. Catching it late means cut and replace pipe. Catching it when it leaks means cleanup, lost throughput, regulatory consequences, and a mountain of paperwork. The earlier in that chain a tech catches something, the more value the operator gets out of the line.

The headline industry numbers come from two studies that anyone working corrosion has heard of:

A 2002 Federal Highway Administration study put the annual direct cost of corrosion in the U.S. at about $276 billion, with indirect cost roughly equal — somewhere near $552 billion total. Pipeline corrosion was a substantial slice.
A 2016 global follow-up study estimated the worldwide annual cost of corrosion at about $2.5 trillion, with somewhere between 15 and 35 percent of that saveable through better-practice corrosion control. That saveable share — hundreds of billions of dollars a year, globally — is the part this work directly affects.

Per-incident costs are easier to feel: replacement and repair, downtime, lost throughput, cleanup, penalties, insurance impacts. A single significant leak on a major line can run into tens of millions in direct cost alone, before counting the cost of unplanned downtime in the production schedule.

The regulatory side

Federal pipeline regulation requires integrity management programs that specifically address internal corrosion. 49 CFR Part 192 (gas pipelines) and Part 195 (hazardous liquids pipelines) lay out the framework. Subpart O of Part 192 requires gas-transmission operators to identify, assess, and mitigate internal corrosion threats on their covered lines. PHMSA — the federal Pipeline and Hazardous Materials Safety Administration — audits these programs and issues enforcement when they fall short.

None of that compliance work happens without IC techs in the field running coupons, taking samples, pulling probes, doing inspections, and writing the data into integrity-management records. The rules require the work; the techs do the work.

You don’t have to memorize any of the numbers above. The point is that internal corrosion work sits at the center of three things — safety, asset value, and regulatory compliance — and a tech who can recognize what’s happening inside the pipe is somebody every operator needs.

How IC work actually gets done

Before we get into the questions the work organizes around, a quick orientation on who does what and what a typical day actually looks like.

The three roles

Internal corrosion work usually involves three people who don’t always sit in the same room:

The corrosion tech — that’s you, or the role you’re working toward. Collects the data, executes the mitigation program, feeds back results. Hands on the samples, hands on the coupons, hands on the truck. The data quality of the whole program depends on this role doing the work carefully.
The integrity engineer (or corrosion specialist) — designs the program and decides what to do with the findings. Looks at the data the tech brings back, picks the inhibitor or biocide, sets the dosing rate, decides when to pig, sets the monitoring cadence. This role makes the calls; the tech executes them. Not a hierarchy preference — it’s how the field is set up.
Operations — runs the line day to day. Knows what the system did this week, what slugged through last month, what the field guy radioed in this morning. Feeds back what they see during normal operations. Operations is the front-line source for “something looks different than usual” signals.

You’re learning enough through this track to talk to all three. That’s the audience framing for everything ahead. You don’t need to be the integrity engineer to be valuable; you need to bring data that helps the integrity engineer make a good decision, and you need to know what operations is telling you when they call.

The tech’s day, in three words

Sample, observe, document. Field hands, gloves, a sampling kit, a notebook. Pulling fluids and gas at sampling points and pig receivers. Watching pig runs and drip-station blowdowns. Collecting bacteria swabs. Installing and retrieving coupons (often under pressure, with the line still in service). Hauling samples to the lab. Reading the lab reports that come back. Walking compressor stations and well sites with operators. Driving between locations.

If any of that sounds familiar from your current work, you’re already partway in. A lot of techs come to IC work having already done pieces of it without calling it that — pulled a pig and looked at what came out, watched a drip station blow, taken a fluid sample, walked a compressor station with a wrench in hand. This track gives you the framework for what you’ve already been around. Not a foreign topic; a more deliberate way of doing what you already see.

Where RCS sits

We do this work in the Appalachian shale-gas region — wet gas, intermittent flow, cool winter soil, plenty of CO₂, the occasional sour pocket, a steady drip-station rhythm. The physics is the same wherever steel pipe carries fluid, but the combination of drivers in each basin is different. If you’re in this region, the examples in this track will match what you see on your sites. If you’re elsewhere, the principles still apply — translate the local conditions, swap out the basin-specific details, and the framework holds.

The four essential questions

The whole field of internal corrosion work organizes around four questions. Get good at asking these, in order, and the rest is technique:

Is there potential for an internal-corrosion problem in the asset? What’s the line carrying? What’s the chemistry? Where can water collect? What drivers could be in play? This is the asset-characterization question — and it’s mostly what this module sets up.
Can the cause of the corrosion problem be defined? When something is happening, what driver is doing the work? CO₂? H₂S? Oxygen? Microbes? Some combination? This is the question the next several modules in this set walk through, one driver at a time.
How can the corrosion be prevented or mitigated? Inhibitors, pigs, dehydration, materials selection, design changes, biocides, operational adjustments. This is the question the Mitigation tier modules later in the track cover. And remember — the integrity engineer designs the program; the tech executes it.
Is the mitigation response effective? Coupons, probes, in-line inspection, fluid sampling, surface analysis. This is the question the Assessment and Integrity Management tier modules later in the track cover.

Internal-corrosion work is the disciplined practice of cycling through those four questions on every line, every system, every season. Assess, mitigate, monitor, repeat — and back to assess when conditions change. That’s the spine of the work, and it’s the spine of this whole track too.

For now, you’re learning how to ask Question 1 well. That’s the foundation. Everything else builds on top.

What’s ahead in this track

This module sits at the front of the IC track. Here’s the broader shape so you know where you are:

Basics & Theory tier (where you are) — the entry tier for the IC track, 22 modules across three sets. The first set, Corrosion Mechanisms in Pipeline Fluids (8 modules, IC-001 through IC-008), is the one you’re in right now — this module opens it, IC-002 frames the chemistry, then the rest walk each driver in turn (CO₂, H₂S, oxygen, microbes) plus erosion-corrosion and top-of-line corrosion. Finishing these 8 earns your first certificate. After that, two more sets close out the tier: Environmental & Flow Factors (7 modules) and System Differences & Risk Foundation (7 modules). Earning the Basics & Theory tier medal means clearing all 22.
Assessment tier — how to know what’s happening. Sampling methods, coupon procedures, microbiological monitoring, in-line inspection, gas analysis, the lab side of the work. This is where the field skills get sharp.
Mitigation tier — how to control it. Inhibitors, biocides, scavengers, pigging programs, design choices, operational adjustments. The integrity engineer designs these; the tech delivers them in the field.
Integrity Management tier — putting it all together. How a corrosion control program lives across years and changing operating conditions. Where IC work fits inside the operator’s broader integrity management process.

This is built for techs who want to do the work, not pass a test. Each module ahead is a piece of that.

Back to the pig receiver

Remember the scene from the start of this module — the new tech standing at the pig receiver with a sample bottle, a chain-of-custody form, and a list of questions they didn’t yet know how to ask. Let’s walk back to that moment with what you’ve picked up.

The dark sludge in the receiver — that’s a deposit. Solids, biofilm, and water mixed together. Under-deposit habitat. Possibly microbial. Worth a closer look.

The faint sulfur smell — H₂S somewhere in the system. Sour-service signal. That changes what mechanisms are in play, what damage modes are possible, and what the lab needs to test for.

The faint orange tint to the water — possibly iron oxide. Possible oxygen excursion somewhere upstream. Worth confirming where O₂ could have come in.

The flakes of black scale — likely iron sulfide. Same pattern as the smell.

And the chemistry inside that bottle — already changing. That’s the race against chemistry change from the start of this module. It’s why field testing on-site catches things lab analysis can miss.

By the time you finish the eighth module in this set, all of this becomes second nature: see the sample, name the likely driver, ask the right next question. The next module — IC-002 — gives you the chemistry foundation. From there, the rest of the set walks through each driver in turn. By the end, the pig receiver is a place you can read.

Key takeaways

Internal corrosion is the inside problem. You don’t find it walking the right-of-way. It needs sampling, monitoring, and inspection programs to find at all. That’s why the corrosion-tech role exists.
The categorical landscape. Pipeline operators manage two corrosion families: IC inside, EC outside. Different programs, different tools, often different teams.
The four big chemical drivers. CO₂, H₂S, oxygen, and microbes — most field IC usually comes back to one of these four or a combination. Each gets its own deep-dive module later.
Two damage modes. Uniform metal loss versus localized attack. The track ahead teaches both.
Where to look. 6 o’clock of horizontals, low points, dead legs, drips, tank bottoms, top of cool wet-gas lines, downstream of pressure cuts, recently opened sections.
Why it matters. Safety, asset value, and regulatory compliance. Most IC failures are slow leaks caught during routine inspection — and that’s exactly the point of the work.
The three-role frame. Tech collects data and executes; integrity engineer designs the program; operations runs the line. You’re learning enough to talk to all three.
The four essential questions organize all IC work: is there potential, what’s the cause, how to mitigate, is mitigation working. IC-001 sets up Question 1.
What’s next. IC-002 frames the chemistry. The rest of this set (Corrosion Mechanisms in Pipeline Fluids) walks each driver and earns your first certificate. Two more sets close out the Basics & Theory tier. Then the Assessment, Mitigation, and Integrity Management tiers.

You don’t have to memorize any of this list. You just have to know it lives in your head somewhere, so the next pig-receiver call doesn’t catch you cold.

References & Further Reading

Books

Internal Corrosion Field Guide — pipeline-tech mental model; canonical reference for this track
Peabody’s Control of Pipeline Corrosion — broader corrosion-engineering reference

Federal regulation (United States)

49 CFR Part 192 — Gas Pipelines
49 CFR Part 195 — Hazardous Liquids Pipelines

Industry standards

NACE SP0106 — Control of Internal Corrosion in Steel Pipelines and Piping Systems
NACE SP0775 — Corrosion coupons in oilfield operations
NACE TM0194 — Field monitoring of bacterial growth in oil and gas systems
NACE MR0175 / ISO 15156 — Materials for sour-service environments
API RP 1160 — Managing System Integrity for Hazardous Liquid Pipelines
API RP 80 — Definition of Onshore Gas Gathering Lines

Reports and studies

2002 FHWA Cost of Corrosion Study
2016 IMPACT Study — Global cost of corrosion
NTSB Pipeline Accident Reports — Bellingham, Washington (1999); Carlsbad, New Mexico (2000)

Apply — three orientation scenarios

Get oriented before you get technical.

Three scenarios — and none of them is about diagnosing a corrosion mechanism. That’s IC-002 onward. These three are about getting your bearings before the technical density picks up. What questions do you ask on a site you’ve never seen? Which modules in the track will actually answer the questions you have right now? And when you do have a finding, how do you describe it to the person upstream of you who’s going to decide what to do about it?

How to use this lesson. Read the setup. Think through your answer before clicking. Each step reveals our reasoning. There’s no single “right” answer on most of these — the point is to compare your thinking against ours.

Scenario 1 · First day on a new site

Walking up to a compressor station you’ve never worked.

Setup. You’ve just picked up internal corrosion work on a new operator’s gathering system. First site is a compressor station with three reciprocating units, two sample taps you’ve been told about, a drip downstream of the discharge, and a small slug catcher feeding the suction header. Operations is friendly but busy. You have a sampling kit, a notebook, and a half-day before you need to be back at the truck. Nobody is going to walk you through it — you’re expected to know what you’re doing.

Before you uncap a single bottle: what are the three things you’d want to know about this site? Where would you go to find each one?

The first thing — what’s in the fluid

Before you can sample meaningfully, you need to know what’s flowing through the line. Composition tells you which drivers are even possible.

What you’re looking for:

CO₂ content in the gas (mol% or parts per million)
H₂S content — sweet, sour, or somewhere in between
Water content — is this technically dry gas or known wet gas? Any condensate fall-out at this station?
Liquid hydrocarbon content — is this two-phase, three-phase, or mostly dry?

Where to find it: the gas analysis on file with the operator (somebody at the office has it), the tariff agreement for the line, recent producer test reports if it’s gathering, or the operator’s IC program records if they have one. Operations at the station may not have it on hand, but they’ll know who does.

The second thing — where the water goes

Internal corrosion follows the water. Before sampling anything, walk the elevation. Where can water collect on this site?

The drip downstream of the discharge — designed to catch liquids, but is it actually being drained?
The slug catcher feeding the suction header — same question
Any low points in the piping between separator vessels and the compressors
Any dead legs from removed equipment, valved-off spurs, or bypass lines
The suction-side scrubber bottom, if there is one

Even on a “dry gas” station, water comes from upstream slugs, from condensation when pressure drops, and from any drips that haven’t been blown down. The places water collects are where IC will be doing its work — and they’re often the places you should be sampling.

The third thing — what’s the history

The site existed before you got there. It has a story. Ask:

Has anyone done IC sampling at this site before? When? What did they find?
Is there an inhibitor or biocide program running on the upstream lines feeding this station?
Have any of the feeders been pigged recently? What came out?
Any prior in-line inspection on the discharge side? Any anomalies flagged?
Has operations ever reported anything unusual — black powder in filters, fluid carryover, drips needing more frequent blowdown?

Your integrity engineer or corrosion specialist will likely have a chunk of this in records. Operations at the station knows the day-to-day. Together they give you the site’s history — and the history is half the story before you ever pull a sample.

Composition. Water collection. History. Three questions, asked before you ever uncap a bottle. They turn a cold site into a site you can read.

Scenario 2 · Build your road map

Connect your current questions to the modules ahead.

Setup. Eight modules sit ahead of you in this set — Corrosion Mechanisms in Pipeline Fluids, the first of three sets inside the Basics & Theory tier. After this tier, three more tiers build out the rest of the IC track. You almost certainly already have specific questions about IC work that brought you here. Most learners do.

Take a minute. What are the questions you walked in with? Where in the track do you expect each one to land?

Common questions and where they land in this set

Sample of questions we hear from techs starting this track, with the module that picks them up:

“What’s actually happening at the metal surface when corrosion is occurring?” → IC-002 — the chemistry foundation
“What’s the difference between sweet and sour service, and why does it matter at my sites?” → IC-003 for sweet (CO₂), IC-004 for sour (H₂S)
“Where does oxygen come from in a system that’s supposed to be sealed?” → IC-005
“What’s the deal with bacteria in pipelines? Is MIC really 40% of failures or is that a number people throw around?” → IC-006
“Why does the elbow downstream of that pump keep showing up on every inspection?” → IC-007 on erosion-corrosion
“Why is the top of this wet-gas line corroding when the inhibitor is dosed at the bottom?” → IC-008 on top-of-line corrosion

Questions that land later in the track

Some questions point past this set:

“How do I install a coupon in a live line? How long do I leave it? What does the lab actually tell me when I send it back?” → Assessment tier
“What’s actually in those inhibitor products? How do I know if the dose is right?” → Mitigation tier
“How do I tell if the mitigation program is actually working over time, not just on paper?” → Integrity Management tier

If your questions are mostly in this group, this set still earns the time — it builds the vocabulary the rest of the track uses. But know that the most field-tactical answers live a tier or two down.

Questions this track won’t answer

Be honest about the boundary too. This track:

Won’t make you the integrity engineer designing the mitigation program. That’s a different role with a longer arc.
Won’t replace product-specific training from a chemical vendor on their exact inhibitor line.
Won’t make you a metallurgist. We name the damage patterns; we don’t teach steel chemistry at the failure-analysis level.
Won’t substitute for the operator-specific procedures at your company. Every operator runs the work slightly differently.

It will give you the framework — the mental model and the vocabulary — that everything else builds on. That’s its job.

Knowing where your specific questions land makes the rest of the set feel less like a march and more like a path. The learners who finish the track are the ones who can see themselves in it.

Scenario 3 · Talk to the integrity engineer

Describe what you found in plain language.

Setup. About a month ago, you pulled samples from a pig receiver on a gathering line that feeds a small treating facility. The receiver had a couple inches of dark sludge, water with a faint sour smell, and visible black scale flakes in the deposit. You bottled fluid and solid samples for the lab and inoculated SRB (sulfate-reducing bacteria) serial-dilution vials at the time. The lab report came back about a week later. Today at the 28-day SRB read, three vials came back positive. You’re now calling the integrity engineer to flag what you’ve seen and let them decide whether the mitigation program needs adjusting.

What do you actually say? What do you include — and what do you leave out?

What to include — the facts, in order

Lead with the data, not your interpretation. Say what you saw, what you measured, and what came back. Something like:

Site and line. “I’m calling about the pig receiver on the [line name] — the 28-day SRB read just came back this morning and I want to flag what we have.”
What was there at the pig run. “About a month ago: two inches of dark sludge in the receiver barrel, water phase with a faint sour smell, visible black scale flakes mixed in.”
On-site measurements at the time. “pH on the water came in at 6.8.”
Lab report (back about three weeks ago). “I’ll forward the lab numbers — full chemistry, dissolved iron, dissolved sulfide, and microbial counts.”
SRB serial-dilution read. “Three vials came back positive at the 28-day read this morning. I can send the photos.”
Operations input. “Line was last pigged eight weeks before that run; operations said they noticed more debris in the receiver than usual.”

That’s the call. Six short pieces. The integrity engineer can build a picture from that.

What to leave out — and why

Don’t diagnose. Don’t speculate on the mechanism. Don’t recommend a treatment change. Specifically:

Don’t say “this is MIC.” Positive SRB vials confirm bacteria are present in the sample, not that they’re driving corrosion at the pipe wall. Multiple lines of evidence are needed before naming MIC as the active mechanism — that’s IC-006 territory.
Don’t say “we need to switch biocides” or “we need to up the inhibitor.” The integrity engineer makes the mitigation call, not you. Bringing them facts gets you respect; jumping past your role costs it.
Don’t downplay either. Positive SRB plus visible black scale plus sour smell on a line that was pigged eight weeks ago is worth the call. Let the integrity engineer decide if it’s worth a deeper look.

What to expect back

The integrity engineer will probably ask a few clarifying questions — fluid temperature, when the last inhibitor dose hit this line, recent operating changes upstream. They might ask you to pull a follow-up sample at a different point in the system, or to swab a coupon if there’s one in the line. They might just thank you and say they’ll wait for the lab results.

Either way, you’ve done your job — given them the data they need to make the call. That’s the three-role frame working as it’s supposed to.

Bring data, not diagnosis. Bring observations, not opinions. The integrity engineer is upstream of you for a reason — and feeding them a clear picture is how the work gets done well.

None of these three scenarios was about naming a corrosion mechanism. That’s deliberate. The opener earns its lighter weight — orientation and identity first, mechanism diagnosis later. The next module starts the chemistry. From here, head to the quiz to lock the vocabulary in, then we’ll see you in IC-002.

Three habits to carry into IC-002: ask the three orienting questions before you sample (composition, water, history); know where your own questions land in the track; bring data, not diagnosis, when you call your integrity engineer.