Record Untested Segments in a Rail Examination Run

A rail test vehicle can traverse a route without producing a valid examination for every length of rail. The run record and the coverage record therefore need different meanings. Begin with the planned examination limits and the actual reviewed data status. Preserve locations where the search could not be completed or its validity remains unresolved. Do not label the full traveled distance inspected merely because the vehicle reached the planned endpoint.

The worksheet supports a record of examination exceptions and their disposition. It does not determine track operating conditions, prescribe restrictions or authorize a line to remain in service. Those actions belong to the responsible track-owner process under the applicable requirements. The reporting task is to make the affected location, evidence gap and actual responsible response clear enough that an unresolved length cannot disappear inside an apparently completed route summary.

The current 49 CFR 213.237 text states that a length without a valid search cannot be counted as internally inspected for the specified purposes of that section. Its applicability and required responses need the responsible track owner’s review. This guide does not reproduce operational limits or supply a substitute compliance procedure. Record the actual instruction governing the run and exception handling.

Preserve the test purpose and process designation supplied by the owner. A run can support a particular required inspection or another defined purpose, and its records should not be relabeled after the fact simply to make a coverage total appear complete. Keep any authorized process change with its actual time and location references. The worksheet records what happened and the applicable decision basis without inventing regulatory status from a file name or dashboard label.

Record the division or subdivision, track designation and other actual route identifiers needed to locate the exception. A milepost alone can be ambiguous where parallel tracks or repeated numbering exist. Preserve which rail or examination path is affected using the owner’s defined convention. Do not assume that an exception on one side applies to both sides, or that a satisfactory result on one rail establishes the status of the other.

Where track names changed between the work order and final record, retain a confirmed cross-reference. A local nickname or crew shorthand can help communication but should not replace the formal identity needed for retrieval. The final log should allow another responsible team to locate the affected physical length without relying on the original operator’s memory or interpreting an unverified abbreviation from a handwritten note.

Use the reviewed endpoint references supplied by the examination record. State their direction and measurement convention. A point marker describing where a problem was noticed may not establish the full affected length. Preserve how the responsible reviewer determined the boundaries and any uncertainty. Do not turn an approximate event location into exact endpoints merely because the reporting table requires two numbers.

If the original data uses an onboard distance reference while the owner uses mileposts or another location system, retain the actual crosswalk. A conversion should have a documented basis and appropriate qualification. The worksheet does not calculate track location from GPS or correct instrument distance automatically. Keep the source references visible so later field work can resolve the intended length rather than a convenient but unsupported numerical interval.

Use the actual reason supplied by the qualified examination process. Equipment performance, coupling or surface conditions, obstruction, data loss and incomplete interpretation are not interchangeable categories. Preserve the specific affected interval and the actual assessment. Do not assign a technical cause solely because an expected file is missing. The record should distinguish a confirmed invalid search from a missing deliverable whose underlying examination status has not yet been established.

A concise reason code is useful only if its definition remains available. Add a short factual note where the code does not explain the practical next step. An entry such as no test should tell the reviewer whether further examination is needed, data recovery is being investigated or a location question remains open. The reporting team should not independently declare a search valid or invalid without the actual responsible determination.

Identify the run and file segment before and after an interruption, together with the actual time and location references. A resumed run may overlap earlier coverage or leave a gap. Preserve both possibilities rather than assuming the restart point exactly matches the stop point. The final summary should connect the reviewed usable intervals and retain any unresolved boundary between them.

Do not merge multiple acquisition files into an apparently uninterrupted examination without documenting their relationship. Separate files can be a normal part of the work, but the coverage accounting needs to show how they fit together. Keep the original file identifiers and the actual review conclusion. A continuous-looking table or plotted line should not conceal an interval for which the equipment status or interpretation remains uncertain.

Where a repeat pass covers part of an earlier route, identify the actual overlap and whether it resolves the prior exception. The total distance traveled can exceed the unique physical length examined. Do not add every pass length and label the result unique coverage. Preserve the owner’s actual counting basis and the reviewed coverage map or interval list that supports it.

A repeat pass also does not automatically close every earlier issue within the same broad milepost range. Confirm the affected rail, exact interval and validity of the follow-up evidence. If the repeat addresses only part of the original gap, retain the remaining portion as open. The log should show the actual resolved and unresolved boundaries rather than closing a large exception because a small follow-up report shares its location label.

An interval lacking a valid examination and a suspect location identified in usable data represent different issues. Preserve their separate identities even when they occur near one another. A field verification of a suspect does not necessarily resolve an untested length around it. Conversely, a valid repeat examination of a gap does not automatically close a previously identified suspect unless the actual responsible process addresses that result.

Use separate source references and action records where the tasks differ. The final handover should allow the owner to see both populations without confusing no usable evidence with a known indication. This distinction prevents a misleading all clear conclusion when the only completed action concerned one identified location and a broader examination limitation still remains unresolved.

In a fictional rail test, the reviewed run log identifies an untested interval between owner-defined markers A and D on the designated rail. A later examination covers only B through D. A draft summary closes the entire A-to-D entry because a follow-up report exists. Review records the verified B-to-D result and retains A-to-B as unresolved, preserving the actual boundary evidence and the owner-assigned action for the remaining length.

The example gives no operational restriction, deadline or test technique. Those remain part of the responsible owner’s process. Its lesson is that a follow-up reference is not sufficient unless its physical scope matches the original exception. The record should retain the successfully completed work while keeping the remainder visible, rather than choosing between a misleading fully closed status and an equally misleading claim that no follow-up occurred.

Record when the exception was identified, when it was communicated through the owner’s required process and who received responsibility for the response. Keep these events distinct from the PDF issue date. A later report should not imply that notification occurred earlier merely because the underlying examination happened earlier. Use actual evidence rather than reconstructing a convenient timeline from file timestamps alone.

The log can record an assigned action and due reference supplied by the owner, but it does not calculate statutory deadlines or send operational alerts. The responsible team must use its actual procedures and communication systems. Preserve confirmation where a notification or decision is claimed. A filled recipient field or a saved report does not establish that the relevant person received, understood or acted on the information.

Reference the actual responsible action taken for an untested length without substituting that action for a valid examination result. A management or operational decision can address an immediate situation while the evidence gap remains. The report should show both states accurately. Do not mark a segment examined because a separate action was recorded, or infer that an action is unnecessary because the worksheet has been administratively closed.

When the owner supplies a final disposition, retain its scope, date and supporting reference. The reporting team should not create the technical or operational authority through wording alone. Draft and issued in NDT Connect are document states. They do not establish track suitability, remove restrictions, authorize traffic or replace the owner’s responsible determination under its applicable obligations.

Compare the original planned population with the final reviewed intervals. Identify any sections removed from scope through an actual authorized change, any newly added work and any unresolved gaps. Do not shrink the denominator after the run merely to make the coverage figure reach completion. Preserve the change reference and reason so the final total explains the work performed against the actual agreed scope.

Check boundary conventions before calculating totals. Adjacent interval records can double count a shared section or leave a small gap if their endpoints use different definitions. The responsible data process should establish the convention and reviewed result. The worksheet records that basis rather than performing geographic calculations or claiming precise coverage from rounded milepost labels that do not support that level of detail.

Connect the relevant instrument and operator references to the actual run segments. If equipment or responsible personnel changed, retain the effective interval and associated review evidence. The equipment tracker can organize entered identifiers, while the certificate manager can organize entered qualification records. Neither verifies rail-test qualification or determines whether a particular search was valid.

FRA’s 2026 Track and Structures Compliance Manual catalog provides its current manual chapters, with an effective date of July 1, 2026. Use the actual applicable requirements and owner procedures for technical and regulatory decisions. The catalog reference does not make this editorial worksheet an FRA form, an approved procedure or a certification of the examination personnel or equipment.

The digital reporting workspace can organize interval references, exception reasons and owner-action notes. Import supported DOCX or XLSX tables after previewing their contents. It does not parse native rail-test data, determine valid search coverage or calculate geographic lengths. Keep acquisition files, route maps and technical images in the agreed external package, with clear text references. The image controls in the editor are company and client logos.

The procedure draft tool can structure proposed reporting responsibilities for responsible review. The report buyer-review guide supports document handover checks. These aids do not replace timely operational communication or the owner’s examination and response processes. Use the worksheet to preserve evidence relationships, while keeping the actual technical decisions and required actions in their responsible systems.

An exception should remain identifiable across shift or contractor changes. Preserve its original identity, current boundaries and latest supported status rather than creating a new anonymous entry each day. A receiving team needs to know what has already been examined, what remains and which source records explain the distinction. Do not rely on a cumulative open-length total without the underlying locations and action references.

Where an entry is split or combined during reconciliation, retain the relationship to its earlier form. This prevents the same physical gap from being counted twice or lost when a new reporting package begins. The current list can be concise, but its history should show how the unresolved population changed through actual examinations, scope decisions or confirmed corrections rather than through unexplained deletion of rows.

A left or right label may describe a vehicle-relative view or a fixed owner-defined rail convention. Preserve which convention the source uses, especially when a repeat pass travels in the opposite direction. Do not assume the same short side label identifies the same physical rail on both passes. Use the actual route and orientation evidence to establish the correspondence. A correctly located interval can still be reconciled incorrectly if its follow-up evidence belongs to the opposite rail, so include this check in any direction-changing run handover.

Choose one closed exception and trace the follow-up evidence across its entire original affected length. Confirm the correct track and rail, usable data and responsible conclusion. Then choose an open interval and verify that its actual owner action and remaining boundary are visible. This check targets the risk that a completed run or a nearby follow-up report has been mistaken for complete examination coverage.

Replace the fictional worksheet row with actual reviewed records and confirm the recipient can retrieve the referenced evidence. A reliable untested-segment log states where valid evidence exists and where it does not. It does not promise that an apparently quiet dataset proves the rail is sound or that a report editor can determine track operating conditions. Its value is a clear, persistent record that supports the responsible owner’s next action.