Ghost Reflections in Optical Time Domain Reflectometers' (OTDR) traces are often misunderstood and misdiagnosed. These reflections are false "non-physical" events that may appear on an OTDR trace under certain conditions, even though no actual connector, splice, or reflective interface exists at the indicated distance. These fake events are created by the test pulse bouncing back and forth between two highly reflective events.
In certain cases, the instruments' advanced (smart) trace analysis may not flag them as wrong, so it requires awareness, knowledge and experience to identify and remove these anomalies, when they occur. Understanding and correctly identifying Ghost Events is crucial because:
-
They can be mistaken for real connectors or breaks.
-
They can lead to incorrect alarming, diagnosis, unnecessary truck rolls and increased operational cost.
-
They may confuse automated event analysis in PON and long-haul links.
Ghost reflections that appear beyond the physical end of the fiber are generally easier to recognize and are often correctly detected and handled by the link map analysis and events table. However, they may still be visible on the trace when you zoom out to a longer span. While the test set is functioning properly in these situations, less experienced users may still be confused by what they see on the trace. The example below illustrates such a case.
Although the link map summary generated by the OTDR’s smart analysis correctly identifies all link elements and the fiber end, the presence of a ghost reflection in the trace still indicates a problem—either with the link itself (strong internal reflection) or with the measurement setup (test configuration or connections). In the example above, the result is flagged as a FAIL, and the red mark indicates that you must inspect the connection at 68 ft (20.7 m).
How to Identify Ghost Reflections
These ghost reflections are generated by multiple reflections of a significant Fresnel event, such as a dirty or damaged connector, connector mismatch, air gaps, poorly aligned mechanical splices, bad fusion splices and an open fiber end. These reflections re-enter the fiber under test, bounce back, and are detected again by the OTDR.
A common source of ghost reflections is poor OTDR connections, such as dirty, damaged or mismatched connections. In those cases, since the test cables (including launch reels) tend to be much shorter (d1) than the fiber under test (d2), the ghost event(s) will show up after the End of Fiber event, at distances that are around a multiple of the total fiber length (2·d2, 3·d2).
Ghost reflections on an OTDR trace may be identifiable by some of their specific characteristics:
-
They follow a strong reflective event. Ghost reflections occur when a connection has very high reflectance, generally worse than -40 dB and more typically when reflectance exceeds about -30 dB.
-
They occur at distances mathematically related to earlier reflections (often multiples of the fiber length between strong reflections).
-
They show a reflection but no corresponding loss.
-
They may not change after the fiber under test is physically inspected.
- They tend to occur more often when testing short fibers.
Challenges
When present, accurate identification of ghost reflections is critical for reliable fiber certification and maintenance, yet it can be difficult and not always straightforward. Even the smart link map analysis in modern test sets can be misled by these events, and correctly interpreting the results still requires technician experience.
- If there is only one highly reflective event caused by test-related connections, the corresponding ghost reflection would appear after the end of fiber, at approximately twice the distance from the OTDR port, which makes them easier to spot. However, when multiple highly reflective events are present within the fiber link, the situation becomes more complex, and a ghost reflection may appear at approximately twice the distance from the preceding highly reflective event.
- Ghost reflections that occur within the fiber span exhibit no associated loss. However, ghost reflections that appear beyond the physical end of the fiber may display measurable loss, particularly when they are located on the trailing edge of the end reflection.
- In certain cases, ghost events may be less apparent when using a larger pulse width because the higher overall signal level increases backscatter, which can obscure or mask the ghost reflection.
Can Ghost Reflections Be Removed?
Yes. However, we shall focus on identifying and eliminating the highly reflective events that caused the ghost in the first place. Ghost events are often created by (bad) temporary connections made for testing purposes. A properly executed OTDR test report should not contain ghost reflections, except when they are being specifically documented as the fault under investigation. Once identified, ghost reflections shall be eliminated by addressing the root cause.
-
Thoroughly clean and inspect all connectors. (Eliminate highly reflective connections, such as damaged or dirty connectors, APC to UPC connector mismatch, etc.).
-
Use APC connectors where possible.
-
Use of proper launch and receive fibers (launch cables), for further troubleshooting.
-
Use the OTDR trace and analysis to identify high reflectance connections or splices within the fiber span and get them fixed.
-
Have a good idea of the expected link characteristics, so you can detect anything that seems out of place.
-
If the separation between ghost events is a multiple of your launch cable length, then inspect all the connections, because one of them may be highly reflective.
-
Reduce pulse width if dynamic range allows. This will only reduce the total energy put into the link, so the ghosts are no longer visible. However, the high reflectance issue(s) that caused the ghost will still need to be addressed.)
-
Use proper fiber termination during testing. That is, avoid testing into open fiber ends. (Note: Terminating the far end of the fiber during testing can hide ghost events because it eliminates the large reflection from an open fiber end, leaving little or no optical power to bounce back and forth and generate those ghosts. However, the high reflection fault that caused ghosts in the first place will still be there.)
Why is it Important to Eliminate (the Cause of) Ghost Reflections?
Because ghost events are caused by high reflectance points in the fiber link—typically seen as large, sharp peaks on an OTDR trace—they introduce high return loss into data links. This leads to signal degradation, reduced performance, increased error rates, and potential system failures, especially in high-speed, high‑power transmission systems. High‑power single‑mode lasers are particularly vulnerable and can be damaged by excessive back‑reflection.
Note from the author: Some online articles claim or imply that ghost events are not a significant issue and suggest they can be minimized or disregarded. In reality, since ghost events are caused by highly reflective connections, they represent a serious problem that must be corrected. In practical terms, the presence of ghost reflections should always be treated as an indication of an underlying fault.