The question of how to handle legacy airport identifiers when digitizing paper logbooks surfaces a surprisingly nuanced record-keeping issue that affects a broad population of pilots who began training at smaller domestic airports, particularly in the western United States, where three-character non-ICAO identifiers were historically common. The specific case cited — U42 transitioning to KSVR (Sevier Valley Airport in Richfield, Utah) — is representative of dozens of airport identifier conversions the FAA has executed over the years as it aligned domestic identifiers with ICAO four-character formatting standards. The underlying logbook entry itself remains legally valid regardless of which identifier a pilot uses during digitization, as 14 CFR 61.51 governs the content of pilot records but does not prescribe a specific standard for resolving historical identifier discrepancies during format conversions.
From a record integrity standpoint, the strongest professional practice is to preserve the original identifier — U42 in this instance — because it accurately reflects the aerodrome designation that was legally in effect at the time the flight was conducted and the instructor's endorsement was made. An examiner, employer, or insurance underwriter reviewing that record would be evaluating flights as they were logged, and the historical identifier provides a defensible, verifiable chain of custody. Annotating the digital record with a note field referencing the current identifier (KSVR) is a straightforward and widely accepted supplemental approach that preserves accuracy while aiding future searchability and cross-referencing in platforms such as ForeFlight, LogTen Pro, or Garmin Pilot.
The broader digitization challenge this post reflects is increasingly common as a generation of pilots trained in the 2000s and earlier moves into professional aviation and undertakes logbook conversion for career advancement purposes. Many legacy identifiers — particularly Utah's "U"-prefix designators, Oregon's "S"-prefix airports, and Washington's "W"-prefix fields — have no direct lookup equivalents in ICAO databases, which can cause validation errors or blank entries in modern electronic logbook platforms. Pilots and operators using these systems for Part 135 certificate applications, ATP certificate applications, or airline hiring processes should audit their digitized records specifically for identifier gaps that automated import tools may silently drop or flag as invalid.
For operators and chief pilots managing pilot records under Part 135 or reviewing logbooks for Part 121 hiring pools, this identifier ambiguity extends to international operations as well, where ICAO, IATA, and FAA LID designators for the same aerodrome can differ substantially. Establishing a clear internal logbook policy — whether preserving historical identifiers with a notation convention or standardizing to current ICAO format — removes ambiguity during audits and streamlines records review. The FAA's lack of specific regulatory guidance on this narrow point places the interpretive burden on the individual pilot, making a consistent, documented methodology the most professionally defensible position.