Why a form may call a known name “unknown”
A traveler with one legal name can run into a mismatch between their documents and a booking form built around two fields: first name and last name. If the form will not accept an empty field, a system or staff member may put FNU—“First Name Unknown”—in the unused slot. The label describes what the form can accommodate, not what the traveler’s name actually means.
The placeholder has to travel with the record
Airlines, visa offices, and border agencies use names to connect bookings and applications to identity documents. A placeholder may help a rigid form accept a record, but it can also create confusion if it appears differently across a ticket, passport, or application. Name fields and conventions vary by system, so FNU is not a universal rule or a substitute for following the relevant agency’s instructions.
That is why the practical detail matters: a mononymous traveler should check how the airline or issuing authority wants the name entered before booking or applying. A placeholder that solves one form’s problem can become a mismatch when another system expects the document’s name to appear exactly as issued.
