It was a Tuesday morning in March 2019 when I nearly cost my company a client.
I was standing on a rooftop in a light drizzle, holding an Anritsu MT8222A BTS Master, looking at a small cell node that a regional carrier was about to launch. This was my first solo deployment after two months of shadowing Todd Pepsi, the senior engineer who trained me. Todd had drilled the pre-test checklist into my head until I could recite it in my sleep.
And then I made the call that I didn't need the checklist that day.
Spoiler: I needed it.
I've been handling RF field testing and network verification for about six years now, and I'm the person who maintains our team's checklist—the one that lives in every kit and every truck. I got that job because I made a series of well-documented, expensive mistakes. The most expensive—$2,800, the one that still makes me wince—involved the gunmetal-gray MT8222A in my left hand and an Anritsu OTDR sitting in the back of the truck.
Here's the background. I worked for a small contracting firm that does RF deployments for regional wireless carriers. These are the carriers who don't have full in-house engineering teams, so they rely on subcontractors like us to verify that a site is ready to launch.
The task was straightforward: verify the antenna system on a new small cell. Run cable and antenna analysis with the MT8222A, scan the RF environment, then certify the fiber backhaul with the OTDR. Each measurement had a documented procedure. Each procedure existed because someone—usually Todd—had made a mistake without it.
I skipped two of those procedures that day.
First, the MT8222A. The cable and antenna test function on this unit is genuinely solid. You pick the measurement, set the frequency range, run an OSL calibration with the open/short/load standards, and then connect the line under test. The OSL step takes about ninety seconds.
I set the frequency range based on what the previous site had used. Different band, different antenna. The correct range was defined by the 3GPP band configuration for this particular LTE deployment—which I had on my phone, in the site document, and never bothered to open. That was red flag one. Then I skipped the OSL calibration because, in my head, the unit had already been calibrated at the factory, so what was the point of doing it again in the field?
(Should mention: the point was accuracy. OSL calibration is how the MT8222A learns the characteristics of your specific test port cable at the frequencies you're actually measuring. Skip it, and you're measuring the errors of your test setup instead of the antenna.)
The upside of doing the OSL cal: ninety seconds. The downside of skipping it: a bad measurement that could cost thousands. I knew the math. I did it anyway. That's the part that's hard to explain.
I ran the test. VSWR on sector 3 came back at 1.32:1. Looked great. I logged it and moved on to the fiber work.
The OTDR mistake was subtler. An OTDR measures distance by converting round-trip time into distance using the fiber's group index of refraction. I needed the exact value for the specific fiber on this site. I didn't have the datasheet handy, so I entered a value from memory. Off by maybe 0.0005. Doesn't sound like much, but on a 3,000-foot fiber run it shifts every distance reading by enough to mislabel which splice or connector is which.
I marked a splice at 1,847 feet. It was actually at 1,912 feet. Didn't think it mattered at the time.
I want to say the fiber was ITU-T G.652 standard single-mode, which is the most common spec you'll see in this kind of work—but I should've confirmed the exact group index from the fiber datasheet instead of guessing. That's the part that matters. The G.652 recommendation gives nominal values for 1310 nm and 1550 nm, but actual fiber varies by manufacturer.
The site went live a week later. Three days after that, my phone rang.
It was Phil, the client's RF engineer. "Hey, we're seeing some odd VSWR readings on sector 3. Your report said 1.32:1. Our integrated test shows 2.1:1. That's a big gap."
I got defensive. I said something brilliant like, "Well, our equipment is calibrated, so maybe you adjusted the antennas during commissioning?" There was a long silence.
"We haven't touched the antennas."
Sinking feeling. I told him I'd come out the next day and re-test.
On the drive home, I called Todd Pepsi. He listened to the whole story without interrupting. Then he asked, "Did you cal before you tested?"
I said yes. I lied.
Todd decided to come with me the next morning. I was annoyed. He packed the calibration kit without saying a word.
On site, he ran the OSL calibration first—right in front of me, taking his time, demonstrating that it takes under two minutes. Then he set the frequency range from the actual site documentation. Then he ran the same cable and antenna test I'd run a week earlier.
VSWR on sector 3: 2.1:1 at multiple points in the band. Exactly what Phil's team saw.
I stared at the screen. My clean 1.32:1 reading was garbage. Without calibration, the MT8222A had been measuring the impedance mismatch of my own test cable, not the antenna system. The actual antenna had a damaged jumper on sector 3—a cable nicked during installation, probably by our crew.
Todd then pulled up my saved OTDR trace. He looked at the refractive index setting and just shook his head. He pointed to the splice I'd labeled at 1,847 feet. "This is actually at 1,912. If they'd acted on this, they'd have dug up the wrong access point."
Total damage: $2,800 in re-testing labor, a one-week delay on the site launch, and a client who didn't trust a word we sent them. That last item isn't on the invoice, but it's the most expensive one on the list.
Phil didn't fire us. He stayed professional about it. But I could hear the shift in his voice. We went from "the team that does good work" to "the team that needs supervision."
The repair itself was simple: replace the jumper, re-test, done. It was the relationship that took months to rebuild.
That was almost six years ago. I've made a few mistakes since then, but nothing with that price tag. Now I'm the one who trains new techs, and there's a laminated checklist that sits in every test kit we own.
It's not complicated. Open/short/load calibration before every cable and antenna test. Frequency range verified against the site's documented band plan. Refractive index pulled from the fiber datasheet, not from memory. Ninety seconds to run through. It has caught more than 30 potential errors in the last 18 months alone.
The most frustrating part of this whole story: I was warned, multiple times, exactly what would happen. Todd showed me bad measurements. He explained the why behind each step. I nodded, and then I went and did it anyway. You'd think a clear warning would be enough to change behavior. Some of us apparently need to spend $2,800 to actually learn.
What most people don't realize is that field testing errors are almost never the equipment's fault. The Anritsu hardware is solid—both the MT8222A and the OTDR are accurate when set up properly. The issue is almost always the operator cutting a corner to save ten minutes.
And here's the other lesson, the one that shapes how I talk to every new tech: this client was a small regional carrier. Not a giant national account. But they gave us a shot, and I repaid that with sloppy numbers. Todd put it bluntly on the drive back: "Small doesn't mean unimportant. It means potential. You treat every job like it's the only job, because to that client, it is the only job."
People ask whether the Anritsu MT8222A is worth considering these days, given how much newer test equipment exists. My honest answer: yes. But the same caveat applies to any test instrument—the procedure matters more than the product.
From the outside, a professional-grade tester like the MT8222A looks like it should simply produce correct numbers. The reality is that it's a tool that faithfully reports whatever setup you give it. Bad setup, bad numbers.
The MT8222A is a workhorse. The battery holds up in the field, the interface is intuitive, and the measurement quality is excellent when you follow the setup steps. We use it for spectrum analysis, cable and antenna testing, and base station verification. It's a genuinely capable network tester.
The Anritsu OTDR is the same story. It produces clean, repeatable traces when configured correctly. In my experience, there's no such thing as the "best" network tester in the abstract. The best tester is the one the operator sets up correctly, every single time.
There's something satisfying about running a clean test when you know the setup was done right. The trace looks right. The markers line up. You get that quiet confidence that only comes from following the steps. Took me a while to get there, but I wouldn't trade it.
If I could go back to March 2019 and say one thing to myself, it would be the same two sentences Todd wrote in his incident report:
"Run the checklist. Every time."
It's tempting to look at a serious instrument like the MT8222A and assume it'll make you look good. It will—if you treat it with respect. Same for the OTDR. These tools don't sugarcoat anything. They give you exactly what you ask for. Garbage in, garbage out.
That $2,800 mistake wasn't the equipment's fault. It was mine. And the proof is that I haven't wasted anything close to that since. The checklist is laminated. The techs use it. And the clients—especially the smaller ones—get reports they can actually trust.
That's what "best" means in network testing. Not the newest model. Not the most features. A technician who respects the measurement.