FOA CFOS/O common mistakes
FOA CFOS/O · Understand the traps and how to avoid them.
Treating the 1,625 nm OTDR wavelength as interchangeable with 1,550 nm when measuring a link's end-to-end loss, then quoting the 1,550 nm figure as the acceptance result.
Candidates memorize 'OTDR for loss' without learning that 1,625 nm is used to find macrobends, not to certify attenuation, and that the 1,310/1,550 nm pair is what most single-mode acceptance specs reference. The longer wavelength shows higher loss on a bent fiber, so mixing the numbers produces confusing or failing results.
What to do instead
Build a one-page wavelength map: 850/1,300 nm multimode, 1,310/1,550 nm single-mode loss and length, 1,625 nm bend detection only. Before any test, write the acceptance wavelength on the test record and confirm the OTDR is set to it. If 1,625 nm is used, label the trace as a bend check, not a loss certification.
Reading the OTDR event table as the final answer and reporting splice loss straight from the table without checking the LSA (least-squares approximation) setting and the bidirectional average.
The default 3-point or 5-point method is sensitive to backscatter direction and to the splice's position relative to the pulse, so a single-direction table can show a gainer or a phantom loss. Candidates who trust the table skip the two-direction measurement that the standard requires.
What to do instead
For each splice, capture traces from both ends with the same pulse width and range, set the analysis method to LSA, and average the two directional values. Report the averaged value; if the two directions disagree by more than about 0.1 dB, re-clean and re-measure before accepting the splice.
Choosing a launch cable shorter than the OTDR dead zone and then trying to measure the first connector's loss from the trace.
The front-panel connector sits inside the OTDR's attenuation dead zone, so the event table merges the launch connector and the first field connector into one event. Candidates see a number and assume it is valid.
What to do instead
Use a launch fiber at least as long as the specified dead zone for the chosen pulse width (commonly 1 km or more for single-mode acceptance testing), and a receive fiber of similar length. Verify the first and last field connectors appear as separate events before recording any loss.
Setting a single fixed pulse width for an entire span, then claiming the far-end connector and the last splice meet spec.
Long pulses reach far but blur closely spaced events; short pulses resolve events but run out of dynamic range. Candidates pick one setting to save time and never notice that the tail of the trace is noise-limited.
What to do instead
Run two acquisitions per fiber: a short pulse for near-end resolution and a long pulse for end-to-end and far-end events. Confirm the far-end Fresnel peak is at least 3–5 dB above the noise floor on the long-pulse trace before accepting far-end numbers.
Cleaning a connector by wiping the ferrule endface on a dry sleeve or on a shirt, then mating it and testing loss only.
Dry wiping can leave grit that scratches the endface, and loss testing at 1,310 nm often passes even with contamination that later causes reflectance or intermittent failures. Candidates equate 'loss passes' with 'clean'.
What to do instead
Use a one-click cleaner or a lint-free wipe wet with approved solvent followed by a dry wipe, inspect with a video scope at 200× or better, and accept only against a defined endface criteria zone. Re-inspect after every mating and log the inspection result with the loss test.
Pulling cable by attaching a pull rope to the strength members with a knot or by pulling on the jacket, and ignoring the cable's maximum tensile rating.
Knots concentrate stress and cut into aramid yarn; jacket pulls transfer load to the buffer tubes and can stretch or ovalize them. Candidates do it because it is fast and the cable 'looks fine' afterward.
What to do instead
Use a proper pulling grip or swivel attached to the strength members per the manufacturer's instructions, keep tension below the rated short-term load, and monitor with a tension meter or breakaway link on long pulls. Record pull tension and sidewall pressure at each bend.
Air-blowing a microduct run without checking duct condition, bend radius, and lubricity, then blaming the fiber when the install stalls halfway.
Blowing depends on a continuous smooth bore, gentle bends, and correct air pressure and feed rate. Candidates push maximum pressure from the start and stop feeding when resistance appears, which packs fiber into a bend.
What to do instead
Pre-survey the duct for kinks, debris, and tight bends; verify the duct inner diameter against the fiber count; start at low pressure and increase gradually while keeping a steady feed rate. If resistance rises, stop, reverse slightly, and re-feed rather than forcing.
Selecting an OSP cable type by fiber count alone, installing a loose-tube gel-filled cable in a location that requires a toneable or dry, riser-rated design, or using indoor cable outdoors.
Candidates memorize cable names without mapping them to environment: gel-filled loose tube for direct-buried and duct, dry loose tube or tight-buffer for areas needing water blocking without gel, armored for rodent or crush protection, and appropriate ratings for the pathway. The mismatch only shows up at inspection or after water ingress.
What to do instead
Build a selection matrix with rows for environment (aerial, duct, direct-buried, indoor), water-blocking method, armor, and fire rating, and match the cable datasheet to the pathway before ordering. Confirm the jacket print and listing on the reel against the spec.
Fusion splicing without verifying cleave angle and endface quality, and accepting a splice based on the splicer's estimated loss alone.
A poor cleave produces bubbles, voids, or offset that the splicer's estimate can under-report. Candidates chase the estimated number instead of the cause, re-arc repeatedly, and leave a weak splice that fails in thermal cycling.
What to do instead
Check cleave angle (typically within 0.5°) and endface on a scope before splicing, keep the fiber and V-grooves clean, and use the splicer's arc-check and cut-back features. Treat estimated loss above the project threshold as a reject and re-cleave rather than re-arcing.
Working in a live OSP environment without verifying the fiber is dark, or opening a splice closure without confirming laser safety and traffic status.
Candidates focus on the craft task and skip the administrative and safety steps: no fiber identification, no confirmation of which strand carries traffic, no eye protection when inspecting with a scope. The result is either an outage or an eye injury from an invisible source.
What to do instead
Before any work, obtain the fiber assignment and confirm the circuit is out of service with the owner; treat all fibers as live until proven dark with a power meter. Never look into a fiber or connector without confirming it is dark, use a scope with an IR-safe viewing system, and follow the site's lockout and confined-space or bucket-truck rules.