Do not invent an exact point at which the condition crossed the criterion. Record the last supported acceptable observation and the first supported limiting observation, with the unobserved interval between them. You can describe what was known at each date and report the service recorded, but the actual transition time remains uncertain unless other reliable evidence resolves it.
Identify the last known good and first observed limiting conditions
Confirm the blade identity, installation record and applicable condition criterion. Gather the available inspection, service and removal records without altering their original dates. Identify whether the missing entry reflects an inspection that was not performed, a lost record or an unknown situation. Those possibilities have different implications, but none authorizes reconstructing a precise reading from memory and presenting it as a contemporaneous measurement.
The in-house blade-benchmark discussion provides the broader data-quality context. For this comparison, identify the last observation that genuinely supports acceptable condition and the first that documents the limiting condition. If no earlier acceptable observation exists after installation, state that wider uncertainty. Keep the actual removal date separate from the unknown transition date; the blade may have been removed after the condition was first recognized, and the records should preserve that sequence.
Show the unobserved interval instead of choosing an exact failure date
Describe the observation window in dates and, where reliable, recorded exposure. Do not choose the midpoint as the actual endpoint merely because a spreadsheet requires one value. If a planning analysis uses an assumption, label it and retain the full interval alongside it. Check whether the same inspection gaps affect the control. A blade inspected more frequently may appear to have a more precise endpoint without necessarily having a different underlying service life.
Compare only what the evidence supports. You may be able to report service until the last acceptable check, the later observed condition and the actual replacement event. Whether those data establish a ranking depends on the size of the uncertainty and the decision being made. Show when plausible endpoints could change the conclusion. Avoid false precision in an average or cost-per-life figure that hides the uncertainty in the underlying interval.
Use ranges or clearly qualified findings and improve prospective logging
Keep the missing observation visible in the final report and explain how it was handled. Do not delete the blade automatically if its remaining record is useful, and do not silently fill the gap to increase the sample size. The responsible team should decide whether the limited evidence is sufficient for the current purchasing question or whether further prospective observation is needed. Any safety or inspection-process concern should be addressed through normal fleet procedures independently of the analysis.
For a blade evaluation discussion, provide the actual observation timeline and the unresolved endpoint rather than a fabricated lifespan figure. Improve future records with clear ownership, traceable inspection entries and a process for flagging gaps while they can still be investigated. Close the current comparison with qualified findings or ranges where appropriate, not an exact event date that nobody observed. A transparent interval is more useful for future planning than a precise number that cannot be supported.
NIST emphasizes documented measurement evidence and uncertainty. NIST Metrological Traceability: FAQ and Policy ↗
