Convert raw OTDR cable distance to actual physical ground distance. Accounts for splice enclosure slack coils and route deviation to improve fault location accuracy.
Break the route into segments where the cable type changes (e.g. buried conduit into a hub, then aerial lashed the rest of the way) instead of one averaged deviation factor for the whole run — each segment's own typical deviation is applied only to its own length.
An OTDR measures the total length of optical fiber from the instrument to the fault. That cable length is not the same as the physical ground distance from the truck to the fault for two key reasons:
Industry-standard values used when no site records are available:
Where route records (GIS data) are available, always use actual as-built distances rather than estimates.
This correction is especially important for long cable runs with many splice closures. A 10-enclosure section with 15m per enclosure adds 150m of cable — enough to send a crew to the wrong address.
Why does slack subtract before the deviation percentage is applied, not after?
Slack coils are extra cable length that never contributed to ground distance in the first place — they need to come out of the OTDR reading before you convert the remaining cable length into a ground-distance estimate. Applying the percentage first and subtracting slack after would incorrectly shrink the slack correction along with the route length.
How many splice enclosures are actually between the OTDR and my fault?
This is the one input this tool can't calculate for you — it comes from your route records (as-built documentation, GIS data, or a field audit). If you don't know the enclosure count, a conservative approach is to estimate based on typical splice spacing for your build standard (often every 1,000–2,000 ft in distribution plant) rather than assuming zero, which understates the correction.
Does this replace walking the route with a locator?
No — it narrows the search radius so a locate crew spends less time walking the wrong section of route. The corrected distance is still an estimate built on typical slack/deviation values unless you have exact as-built records; always confirm the final location in the field rather than digging based on the estimate alone.