Airline keeps mistaking 101-year-old woman for 1-year-old baby

Y2K, Year 2038, and age/date bugs

• Many relate this case to lingering Y2K-style assumptions: two‑digit years, limited ranges, and “rolling epochs” that break for extreme ages.
• Some note that Y2K was only quiet because of extensive mitigation, and worry that the Year 2038 problem may be worse and less prepared for.
• Others treat it more humorously, inventing “iPhones as units of time” and joking that unfixed 2038 bugs might either cause or prevent an AI apocalypse.

Airline booking quirks and edge cases

• Commenters speculate airline systems use rolling epochs or simplified age rules, making 101 indistinguishable from 1 in some contexts.
• Several point out airlines often mishandle even basic data like names, so rare age edge cases are unlikely to be prioritized.
• Some see the bug as non‑critical (<0.001% of bookings) and thus realistically never fixed.

Passports, IDs, and date encoding schemes

• Passports’ machine‑readable zones and some chips still rely on two‑digit years; this has already caused issues for centenarians in other bureaucracies.
• Various national ID schemes (Polish PESEL, Swedish and South African systems) show creative hacks for fitting birthdates, centuries, and sometimes gender into limited numeric spaces.
• There is debate whether IDs should encode personal attributes at all; some argue for opaque identifiers plus checksums only.
• Gender/sex markers and changing identities clash with “immutable” encodings and legacy databases, causing real administrative and medical record problems.

Names, “null”, and system robustness

• Similar failures occur with special names or fields: “Null” or “NONE” as names or license plates, honorifics baked into name fields, or short given names being misinterpreted.
• These examples are cited as warnings about mixing human‑readable meaning with control values in databases and protocols.

Age, mobility, and assistance policies

• Several focus on the practical impact: wheelchair assistance tied to age logic led to an elderly passenger being treated like a baby.
• Others note assistance should be based on explicit requests and detailed needs, not crude age inference.

Legacy airline IT and reliability

• Comments describe deeply entrenched COBOL/Unisys/TTY‑era airline systems with Java front‑ends over ancient cores.
• Some worry about lack of IT support (e.g., no weekend coverage) as a broader reliability and safety concern, though others see these as inconveniences rather than safety threats.