← All articles

OPTICAL FIBER TROUBLESHOOTING · 1 NOVEMBER 2026

OTDR ghost events and reflection saturation: a diagnosis worksheet

A repeated spike beyond the documented cable end may be an optical echo, not another connector or a broken fiber. This worksheet helps field teams recognize ghosts, detector saturation and dead-zone effects before authorizing excavation, resplicing or cable replacement.

Visual reference photographs

Illustrative OTDR equipment used to investigate repeated reflective events and trace saturation
Illustrative visual reference only, not completed Cyber FTTH Mart project evidence. Preserve the native trace and acquisition settings before changing the test setup.
Illustrative fiber connector inspection used to remove contamination as a source of high reflection
Illustrative visual reference only, not completed Cyber FTTH Mart project evidence. Inspect, clean and reinspect every test interface before interpreting echoes.
Illustrative organized fiber termination work used to correlate OTDR events with physical route records
Illustrative visual reference only, not completed Cyber FTTH Mart project evidence. Compare trace distances with the route, slack, patching and closure schedule.
Core rule: Do not create a repair ticket from an automatic event table alone. A suspected event must agree with trace shape, loss behavior, distance, route records and a controlled retest.

1. What an OTDR ghost is

An OTDR launches a pulse and locates events from the return time of backscatter and reflected light. A strong Fresnel reflection can travel back toward the instrument, reflect again at another interface, and re-enter the fiber. The delayed light can appear at a later distance as a false reflective event. The extra peak is real light, but it does not represent a physical connector at the displayed location.

VIAVI describes two common causes: strong reflective events and an incorrect acquisition range. Its guidance says a ghost often appears at a multiple of the strong event's distance and produces no corresponding loss through the false event. FOA similarly warns that ghosts are common on short cables with highly reflective connectors and can make an echo beyond the actual cable end look like a second cable section.

2. Recognize the signature before changing anything

Trace observationGhost or saturation clueVerification
Reflective peaks repeat at equal spacingRound-trip echoes between two reflective interfacesCalculate the distance differences and compare them
Suspected event has reflection but no step lossVIAVI identifies zero-loss passage as a ghost clueUse trace cursors before and after the peak
Peak has a flat topEXFO identifies this as detector saturationReduce pulse width and improve the reflective interface
Displayed event lies beyond the documented endEcho or range artifact is more likely than hidden fiberReconcile with route length and receive cable
Long recovery tail hides nearby eventsReflection dead zone is masking the traceUse a shorter pulse and clean connectors
Event moves when launch-cable length changesThe test setup is contributing to the artifactRepeat with a known alternate launch cable

3. Calculate the expected echo positions

Record the distances of the dominant reflective interfaces. Do not round them to the nearest route landmark. Use the same group-index setting for every comparison because an incorrect index shifts all displayed distances.

Spacing test
Observed spacing = later reflective peak distance - earlier reflective peak distance

Multiple test
Distance ratio = suspected ghost distance ÷ dominant reflection distance

If the ratio is close to 2, 3 or another whole number, and the event has no loss step, treat it as a ghost candidate. Measurement tolerance must account for cursor placement, pulse width, group index and trace resolution.

EXFO gives an additional pattern: distances between successive pairs of events can be approximately equal. That pattern can expose an echo bouncing between two strong reflectors even when the first event is not at the OTDR port.

4. Inspect the trace, not only the event table

Automatic analysis is useful for screening, but it can assign a connector symbol, end-of-fiber label or loss value to an artifact. Open the native bidirectional trace where available and inspect the backscatter line on both sides of each candidate.

  1. Confirm whether a real backscatter continuation exists after the event.
  2. Look for a vertical step that indicates genuine insertion loss.
  3. Zoom the peak and check whether its top is clipped or flat.
  4. Measure the recovery tail and determine what nearby fiber is hidden.
  5. Compare event spacing with launch-cable, link and receive-cable lengths.
  6. Check whether the candidate exists at both test wavelengths.
  7. Compare the opposite-direction trace without forcing event numbers to match.

A ghost can be prominent in one direction and absent in the other because the reflective interfaces and launch conditions change. That asymmetry is evidence to interpret, not a reason to average a false event into the splice table.

5. Remove avoidable reflections first

A dirty, damaged, mismated or open connector can create the strong reflection that drives saturation and echoes. Inspect the OTDR port, launch lead, bulkhead, patch cord and link connector with the correct microscope and safety procedure. Clean only with approved materials, then reinspect before reconnection.

Confirm connector polish compatibility. Never mate APC to UPC. Fit a receive cable when the far-end connector must be measured, and terminate open ends as recommended by the test-equipment manufacturer. Use index-matching methods only when appropriate for the connector or bare-fiber test arrangement and when the material can be safely removed.

Reflection improvement
Change in reflectance magnitude = corrected event reading - original event reading

Because reflectance values are negative dB, a corrected value such as -55 dB is less reflective than -30 dB. Record both readings and the instrument's saturation indication rather than inventing a precise value above its measurement limit.

6. Select pulse width, range and averaging deliberately

VIAVI warns that a pulse that is too long can oversaturate a link and create ghosting, while a pulse that is too short may not reach the end with usable signal-to-noise ratio. Start with the shortest pulse that provides sufficient dynamic range for the link, then lengthen only when the far end cannot be resolved.

Set the acquisition range beyond the link and receive cable, but avoid an unnecessarily large range. Increase averaging time to improve signal-to-noise ratio instead of immediately increasing pulse width. Document wavelength, pulse width, range, acquisition time, index of refraction, launch cable and receive cable for every accepted trace.

The launch cable must exceed the launch dead zone for the chosen pulse. VIAVI's published examples range from tens of metres for short nanosecond pulses to much longer cables for wide pulses. Select from the instrument guidance and actual dead-zone result, not a single universal cable length.

7. Separate a ghost from a real reflective fault

A real mechanical splice, damaged connector or cracked fiber can also be reflective. Do not dismiss an event merely because it is reflective. A real event should normally correlate with a physical route position and may show loss, a changed backscatter level, repeatability from both directions or persistence after the dominant reflection is corrected.

TestGhost expectationReal-event expectation
Correct first high reflectionLater echo reduces or disappearsPhysical event remains
Change launch-cable lengthArtifact position or spacing relationship changesRoute-correlated distance remains after compensation
Shorter pulseSaturation and echo may reduceEvent resolves more accurately
Opposite directionEcho pattern changes materiallyEvent correlates with the same physical location
Insertion-loss testNo unexplained end-to-end loss from the ghostFault may contribute measurable loss

8. Avoid hazardous and service-affecting tests

Confirm whether the fiber is dark before connecting a standard OTDR port. Live PON and active transport links require the correct filtered test port, wavelength plan and operating procedure. EXFO warns that incoming optical power can add noise, prevent valid acquisition or damage an instrument when port limits are exceeded. Measure with a suitable power meter and follow the equipment rating.

Never disconnect a live service merely to eliminate a reflection without an approved maintenance window. Record subscriber or circuit impact, notify the owner, protect open connectors and restore every patch exactly to the controlled port map.

9. Field diagnosis sequence

  1. Save the native trace, screenshot and event table before adjustment.
  2. Verify route length, launch lead, receive lead and group index.
  3. Check for equally spaced peaks and whole-number distance multiples.
  4. Check for a flat-topped saturated peak and extended dead zone.
  5. Measure whether the suspected event produces a true loss step.
  6. Inspect, clean and reinspect all accessible test interfaces.
  7. Correct APC, UPC, adapter or open-end problems.
  8. Repeat with a shorter pulse and suitable acquisition range.
  9. Increase averaging time without hiding the original evidence.
  10. Repeat at the second specified wavelength.
  11. Test from the opposite direction where the route permits.
  12. Change the launch setup in a controlled comparison if ambiguity remains.
  13. Reconcile every real event with the closure, rack or route record.
  14. Use insertion-loss testing when end-to-end loss acceptance is required.
  15. Escalate unexplained persistent events before physical intervention.
  16. Record corrective work and final settings.
  17. Retain original and corrected native traces.
  18. Obtain owner acceptance for deviations and inaccessible sections.

10. Handover worksheet

FieldRequired record
Link identityEndpoints, fiber ID, route, nominal length and service state
InstrumentModel, serial, calibration status, port and software version
AcquisitionWavelength, pulse, range, averaging, group index and resolution
Test leadsLaunch and receive cable IDs, lengths, connector polish and inspection status
Artifact evidencePeak distances, spacings, loss steps, saturation and dead-zone observations
Controlled changesCleaning, pulse, range, lead or termination changes and their effects
DecisionGhost, saturated real event, confirmed physical event or unresolved exception
Final evidenceOriginal and corrected native traces, photos, route correlation and approval

Primary technical references

Investigating an ambiguous OTDR trace?

Share the native trace files, route record, test wavelengths, launch setup and service state. Cyber FTTH Mart can help structure controlled retesting, route correlation and restoration evidence.

Discuss fiber trace diagnosis ↗