An OTDR gainer is an apparent negative-loss event, not an optical amplifier hidden inside a passive splice. Before cutting out a single-mode splice because one trace reports excessive loss, obtain a usable measurement from the opposite end. Compare the same physical event at the same wavelength, retaining the sign of each result. A disagreement between directions can come from different backscatter levels in the adjoining fibers.
This guide helps a maintenance engineer make one decision: retest, accept against the agreed criteria, or authorize re-splicing. It includes a signed-loss example, a record for reviewing disputed events, and the product information to request if a replacement pigtail is actually needed. It addresses resolved events on a point-to-point single-mode path. Closely spaced panel events and measurements through branching splitters need separate treatment.
Why a splice can look like a gain
An optical time domain reflectometer (OTDR) estimates event loss using returned light. The Fiber Optic Association explains that a change in backscatter across a splice can bias that estimate: an event may look unusually lossy from one end and show a gain from the other. Averaging suitable measurements from both directions compensates for this directional effect. The underlying passive splice has not created optical power. See the FOA OTDR reference.
For the reviewer, the distinction is practical. “High one-way OTDR loss” and “confirmed defective splice” are different findings. Repeating the same one-way measurement after every re-splice can keep producing the same misleading result. Equally, a gainer does not prove that the joint is good. Obtain evidence that supports the decision before releasing the link or consuming more spare fiber.
Ask the technician to preserve the original trace before changing anything. A screenshot helps discussion, but the native trace and its settings allow the event placement and analysis to be reviewed later. Treat the first reading as a reason to investigate, rather than an automatic instruction to repair.
Pair the event before averaging the numbers
Start with fiber identification. Record the cable, fiber number, endpoint A, endpoint B and the suspected joint. The event order reverses when the instrument moves to the other end, so matching “event 3” with “event 3” is not sufficient. Use the route and splice records to identify the same location in both traces.
Then check measurement suitability. The two results must represent the same event at the same wavelength, with settings appropriate to resolving it. Keep each wavelength as a separate pair. Do not average a 1310 nm reading in one direction with a 1550 nm reading in the other and call it a bidirectional result.
The FOA guidance on OTDR traces also describes launch and receive fibers and the resolution limits around reflective events. These matter particularly near a panel. A short pigtail splice and its adjacent connector may not be separately resolved. Adding a long launch lead does not increase the physical spacing between those two events inside the installation.
Use this evidence check before doing arithmetic:
- Physical event: confirm the cable, fiber and joint identity from both ends. Resolve any identification mismatch first.
- Wavelength: use the same wavelength for the paired readings. Retest the missing direction at that wavelength.
- Trace quality: confirm enough usable trace around the event for analysis. Improve the setup or report the measurement limitation.
- Instrument setup: retain pulse width, range, averaging and relevant instrument settings. Retrieve the native trace if these are missing.
- End connections: use a suitable launch/receive arrangement and inspected connections. Correct the setup before judging the installed joint.
- Acceptance basis: obtain the project’s applicable method, limits and uncertainty treatment. Do not invent a limit when approved criteria are missing.
This checklist is a proposed review record, not a replacement for an instrument manual or the network owner’s acceptance procedure. If only one end is accessible, state that limitation explicitly. A missing reverse trace is not a zero-loss measurement.
Worked example: keep the negative sign
For a suitable pair, calculate the arithmetic mean of the two signed event-loss values in dB:
Bidirectional event-loss estimate = (A-to-B loss + B-to-A loss) / 2
The following values are illustrative arithmetic only. They are not measurements from a BWNFiber product, a customer site, or a performance guarantee.
| Reading | Example value |
|---|---|
| A-to-B event loss | +0.34 dB |
| B-to-A event loss | −0.18 dB |
| Signed sum | +0.16 dB |
| Bidirectional estimate | +0.08 dB |
Do not change −0.18 dB to +0.18 dB before averaging. Doing so would produce 0.26 dB and answer a different question. Do not discard the negative reading just because a spreadsheet expects positive losses.
The 0.08 dB result still does not establish acceptance by itself. It must be compared with the specified criterion using a valid method and the required treatment of measurement uncertainty. If the event is unresolved, the arithmetic cannot turn it into a reliable isolated-splice measurement. A negative average likewise calls for a review of the event pairing, trace quality and uncertainty; it is not evidence that a passive joint supplies gain.
Record the calculation alongside both original readings. A later reviewer should be able to reconstruct the result without asking which number was changed, rounded or omitted.
Decide what to do with the result
Separate a measurement problem from a repair decision. We recommend recording one of three outcomes for the disputed event, with the evidence that supports it.
Retest or investigate. Use this outcome when event matching is uncertain, the trace is noisy, the adjacent connector obscures the splice, or the test conditions are incomplete. Specify the missing evidence and the person responsible for obtaining it. Repeating an unchanged setup without a reason is not a diagnostic plan.
Accept against the approved criteria. Use this only when the measurement is valid, the applicable event criterion is satisfied, and the remaining required link checks are complete. The approval record should name the criterion rather than merely say “looks good.” Keep any unresolved limitations visible to the approving engineer.
Authorize targeted repair. Use this when valid evidence identifies a defect or an unacceptable event under the agreed procedure. Record the location and proposed intervention. Preserve the before-and-after evidence so a replacement can be evaluated against the original problem.
A splice assessment is also distinct from end-to-end insertion-loss testing. FOA differentiates OTDR event analysis from the direct loss measurement made with a source and power meter. Complete the required link-level test rather than substituting a favorable event average for the entire acceptance package. The fiber loss-budget guide provides related planning context; use the approved project budget for the actual link.
If replacement is needed, specify the pigtail precisely
Once a repair is justified, connect the replacement order to the recorded defect. A connector family alone is not a complete specification for the fiber that will be spliced into the installed cable. Ask for the exact fiber designation and the applicable datasheet, including mode-field information where it is needed for the engineering review. Do not infer these properties from a jacket color or a catalog photograph.
For an SC/APC termination, our SC APC/UPC Optic Pigtail product page lists an SC/APC single-mode simplex 0.9 mm option. This is a candidate for a compatible termination repair, subject to the installed interface, fiber specification and tray requirements. It is not a product that eliminates OTDR gainers, and this article does not claim a tested match to your installed cable.
The product page includes several connector and fiber options. Request a configuration-specific drawing or datasheet rather than treating the full options table as one supplied assembly. For this application, the product’s role is to provide the connectorized tail for the approved repair. The paired OTDR evidence remains part of deciding whether the repair was necessary and how to assess the resulting joint.
Include these details in the inquiry:
- Installed cable fiber specification and any available manufacturer datasheet.
- Required SC interface and APC polish, confirmed against the mating interface.
- Pigtail fiber designation, buffer or jacket construction, length and tray routing requirements.
- Applicable test wavelengths, acceptance method and the order-specific records required.
- Quantity, labeling and the drawing revision to use for sample and production approval.
A supplier’s connector insertion-loss result does not establish the loss of a field splice that has not yet been made. Keep factory assembly evidence and installation acceptance evidence as separate records. If a sample is used, record its configuration so the eventual order can be compared with it.
Close the repair ticket with a reproducible record
The final record should connect the original observation, the decision and any physical change. Store the native A-to-B and B-to-A traces, event mapping, wavelength-specific calculation, relevant instrument settings, approved criterion and the responsible reviewer’s disposition. If a pigtail was replaced, add the supplied configuration and the post-repair results.
Avoid closing the ticket with only a new screenshot. A smaller number after a setting change does not, by itself, prove that the splice improved. State whether the change was a corrected measurement, a physical repair, or both. That distinction helps the next technician compare like with like when the link is checked again.
For an SC/APC replacement review, send the interface details, installed fiber datasheet and required pigtail configuration to [email protected], or use the inquiry form on the SC pigtail detail page. Contact phone: +86-13615744790. Include the disputed-event evidence if it affects the specification; request confirmation before placing the order.
Sources and scope
The technical basis is the Fiber Optic Association’s OTDR reference, accessed September 28, 2026. It is an established educational reference, not a new industry announcement. Product options and the photograph come from the official SC APC/UPC Optic Pigtail page, checked on the same date. The worked calculation and review record are editorial examples; no customer results, universal acceptance limit or instrument-specific procedure are claimed.
