Registry entry

United States Statement Regarding a Valid Lost or Stolen Passport Book and/or Card (Form DS-64)

Report a valid U.S. passport book and/or card as lost or stolen, using the data model of Form DS-64 (Statement Regarding a Valid Lost or Stolen U.S. Passport Book and/or Card). Filing this form electronically cancels the reported passport in the Consular Lost and Stolen Passport System (CLASP), so it can no longer be used for travel; a bearer who later travels on a reported-lost passport may be detained on U.S. entry. If the applicant is also applying for a new passport (the common case), Form DS-64 is submitted together with Form DS-11 (see us/dos/passport-application-ds11); if not, it is mailed to CLASP with a photocopy of a valid government-issued photo ID, or reported online/by phone at travel.state.gov. If the lost/stolen passport is already expired, it is no longer valid and this form is not needed. It does not submit the report; the live U.S. Department of State source is always authoritative (see VERIFICATION.md).

Registry entry

us/dos/lost-or-stolen-passport-ds64

Jurisdiction
United States · national
Version
1.1.1
Verification
verified
Authority
U.S. Department of State, Bureau of Consular Affairs

GovSchema spec v0.3

Authoritative source Form DS-64 (OMB Control No. 1405-0014)

Machine access

Schema document
registry/us/dos/lost-or-stolen-passport-ds64/1.1.1/schema.jsonapplication/schema+json
Verification record
registry/us/dos/lost-or-stolen-passport-ds64/1.1.1/VERIFICATION.mdtext/markdown
Registry catalog
registry/index.jsonone record per schema id

Field reference

35 fields across 5 steps, read from the published schema.json — names, types, requiredness, and validation as the document states them. The live government form remains the authoritative source.

Which document(s) are being reported

  • passportBookStatus enum required

    not_applicable if the applicant is not reporting a passport book. At least one of passportBookStatus or passportCardStatus must be lost or stolen.

    enum: not_applicable | lost | stolen
  • passportCardStatus enum required

    not_applicable if the applicant is not reporting a passport card. The passport book and card have different numbers; at least one of passportBookStatus or passportCardStatus must be lost or stolen.

    enum: not_applicable | lost | stolen
  • isConnectedToNewApplication boolean required

    If true, submit this form together with Form DS-11 (Application for a U.S. Passport). If false, mail this form alone with a front-and-back photocopy of a valid government-issued photo ID to the Consular Lost and Stolen Passport Unit (CLASP), or report online or by phone instead.

Identifying information of passport holder

  • lastName string required

    Personal identifier; handle as sensitive data.

    length: 1–80
  • firstName string required

    Personal identifier; handle as sensitive data.

    length: 1–80
  • middleName string optional

    Personal identifier; handle as sensitive data.

    length: 0–80
  • nameChangedSincePassportIssued boolean required

    If true, also give nameAtPassportIssuance.

  • nameAtPassportIssuance string optional

    Personal identifier; handle as sensitive data. Required when nameChangedSincePassportIssued is true.

    length: 0–160
  • dateOfBirth date required

    Personal identifier; handle as sensitive data. YYYY-MM-DD.

    classification: sensitive-pii
  • placeOfBirth string required

    City & state if in the U.S., or city & country if born abroad.

    length: 1–120
  • socialSecurityNumber string optional

    Personal identifier; handle as sensitive data. 9 digits, no separators. Providing the SSN is voluntary per the form's Disclosure notice, but is used to verify the identity of the person reporting the lost/stolen passport and to identify the passport being reported; failure to provide it may result in processing delays.

    patternclassification: sensitive-pii

Contact information

  • currentAddressLine1 string required

    Street address.

    length: 1–120
  • currentAddressCity string required

    City of the applicant's current address.

    length: 1–80
  • currentAddressState string optional

    Two-letter USPS state abbreviation. Not applicable to a foreign address; see currentAddressCountry instead.

    pattern
  • currentAddressPostalCode string required

    5-digit or ZIP+4 U.S. format if in the U.S.; the form also permits a foreign postal code here for an address outside the U.S. (see currentAddressCountry).

    length: 0–15
  • currentAddressCountry string optional

    Required only when the current address is outside the United States.

    length: 0–100
  • telephoneNumber string required

    Personal identifier; handle as sensitive data. In international E.164 format, e.g. +12025551234.

    pattern
  • alternateTelephoneNumber string optional

    Personal identifier; handle as sensitive data. In international E.164 format.

    pattern
  • emailAddress string optional

    Personal identifier; handle as sensitive data.

    length: 0–160

Details of the loss or theft

  • lossOrTheftExplanation string required

    Answer completely; if the exact circumstances are unknown, be as exact as possible.

    length: 1–2000
  • lossOrTheftLocation string required

    Provide the address if known: city and state if in the U.S., or city and country if known to have occurred abroad.

    length: 1–500
  • lossOrTheftDate date required

    YYYY-MM-DD. If the exact date is unknown, give the last date the applicant remembers having it in their possession.

  • policeReportFiled boolean required

    If true and the report is available, submit a copy with the form.

  • lostPassportBookNumber string optional

    Personal identifier; handle as sensitive data. Applicable when passportBookStatus is lost or stolen. A reused number cannot be reissued.

    length: 0–20classification: sensitive-pii
  • lostPassportBookIssueDate date optional

    YYYY-MM-DD. Applicable when passportBookStatus is lost or stolen.

  • lostPassportCardNumber string optional

    Personal identifier; handle as sensitive data. Applicable when passportCardStatus is lost or stolen. The book and card have different numbers.

    length: 0–20classification: sensitive-pii
  • lostPassportCardIssueDate date optional

    YYYY-MM-DD. Applicable when passportCardStatus is lost or stolen.

  • hasOtherLostOrStolenPassports boolean required

    Refers to prior incidents, separate from the one being reported now. If true, also give otherLostPassportCount and otherLostPassportApproximateDates. If more than one valid U.S. passport previously issued to the applicant was lost or stolen, the replacement passport may be limited in validity.

  • otherLostPassportCount integer optional

    Required when hasOtherLostOrStolenPassports is true.

    range: 1–∞
  • otherLostPassportApproximateDates string optional

    Required when hasOtherLostOrStolenPassports is true. Free text; the form allows more than one approximate date.

    length: 0–200
  • otherLostPassportPoliceReportFiled boolean optional

    Required when hasOtherLostOrStolenPassports is true. If true and the report is available, submit a copy with the form. A distinct field from policeReportFiled: the form has two separate 'Did you file a police report?' questions — this one under the other-lost-passports history question, the other under the current loss/theft-date question.

Signature

  • isMinorUnder16 boolean required

    If true, both parents/legal guardians must sign (see guardianSignatureDate and secondGuardianSignatureDate) instead of the applicant, and a front-and-back photocopy of each signing guardian's ID must accompany the form. If only one parent/guardian has sole legal authority to obtain a passport for the child (22 C.F.R. 51.28), a supporting document (e.g. a court order proving sole legal custody, or Form DS-5525) must be included instead of the second guardian's signature. If false, the applicant signs (see applicantSignatureDate).

  • applicantSignatureDate date optional

    Required when isMinorUnder16 is false. YYYY-MM-DD. By signing, the applicant declares under penalty of perjury that they have read the warning on page one, the information provided is correct and complete, they have not given the passport to another person or disposed of it in an unauthorized manner, they understand the reported passport(s) will be invalidated, and they will return it to Passport Services if it is subsequently found.

  • guardianSignatureDate date optional

    Required when isMinorUnder16 is true, unless the sole-legal-authority exception applies (see isMinorUnder16). YYYY-MM-DD.

  • secondGuardianSignatureDate date optional

    Required when isMinorUnder16 is true and no parent/guardian has sole legal authority under 22 C.F.R. 51.28 (see isMinorUnder16). YYYY-MM-DD.

Verification record

This file is the source-review record for this document version, per the manual-source-review-v1 practice. It documents the provenance of the published fields and flow and states the current verification claim honestly.

Current claim

  • status: verified
  • verification.method: manual-source-review-v1
  • verification.lastVerifiedAt: 2026-07-02

A full field-by-field comparison (manual-source-review-v1 → Procedure step 2) and flow comparison (step 3) are now complete. No field, type, requiredness, validation, or flow discrepancy was found against the sources examined; no data change was needed. This is a PATCH per VERSIONING.md ("a re-verification that finds the source unchanged ... refreshes verification.lastVerifiedAt [and] status to verified").

Sources examined (re-fetched directly this pass)

  • https://travel.state.gov/content/travel/en/passports/have-passport/lost-stolen.html — re-fetched directly (HTTP 200, no access block). Confirmed unchanged: the three reporting channels (Online Form Filler at pptform.state.gov, cancels within 1 business day; by mail with Form DS-64 plus a front-and-back photo-ID photocopy; or in person while applying for a new passport with Form DS-11), the "reporting does not replace the passport — apply in person for a replacement" statement, and the do-not-report-an-already-expired-passport exception. Page footer now reads "Last Updated: May 12, 2026" — after this schema's original 2026-07-01 authoring date, but the "Report Your Passport Lost or Stolen" content itself (reporting options, key points) is unchanged from what v1.0.0/v1.1.0 recorded; the update timestamp reflects an unrelated page-template refresh elsewhere on travel.state.gov, not a content change to this page's substance.
  • Form DS-64 PDF, re-fetched directly from eforms.state.gov/Forms/ds64.pdf (HTTP 200) and re-extracted with a second, independent tool — pdfjs-dist (getTextContent()), distinct from the original authoring's pdf-parse — closing v1.0.0's open "re-fetch and re-extract... or try an alternative extraction tool" item. Page 2 (the data-collection fields) extracted cleanly and matches this schema's fields/steps 1:1: the book/card status-and-selection checkboxes, the connected-new-application question, identity (name, name-change, DOB, place of birth, SSN with its voluntary-disclosure note), contact (address, phone, alternate phone, email), the loss/theft explanation/location/date questions, both distinct "Did you file a police report?" questions (one under the loss/theft-date question, mapped to policeReportFiled; one under the other-lost-passports history question, mapped to otherLostPassportPoliceReportFiled — the GOV-321 correction from v1.0.0 still holds), the lost book/card number-and-issue-date fields, the other-lost-passports history group, and the signature block including the minor-under-16 dual-guardian path and its 22 C.F.R. 51.28 sole-authority exception (Form DS-5525).
  • Page 1's known custom-glyph font-encoding artifact reproduced identically in this pass's independent extraction (e.g. "book and/or card" again rendering as "ERRNDQGRUFDUG"), confirming it is a stable rendering artifact of the PDF's generation tooling — not new drift, and not something a different extraction tool resolves — and that it continues to affect only page 1 boilerplate/legal prose, not any page 2 field label or the page 1 filing-options text (which extracted legibly and matches this schema's description fields).
  • OMB Control No. 1405-0014 confirmed unchanged (matches source.documentRef); the PDF's expiration-date line is one of the strings affected by the glyph artifact and could not be read with full confidence this pass either, consistent with v1.0.0's original note — not treated as a discrepancy since documentRef does not encode an expiration date.

What was re-confirmed against the source (no changes)

  • Cross-field "at least one of book/card" constraint. Still expressible only as a description-level note on passportBookStatus/ passportCardStatus, not a machine-enforced crossFieldValidation rule: spec v0.3's crossFieldValidation (§8.3, [GSP-0013]) shapes are when + requireAbsent/requirePresent (gating a different field's presence) or a compare between two fields' values, neither of which expresses "at least one of these two enum fields must not both be not_applicable" without a synthetic boolean helper field. Left as a documented, spec-grammar limitation rather than forcing an awkward encoding — unchanged from v1.0.0/v1.1.0.
  • Constraint patterns (SSN 9-digit, ZIP/postal code length, E.164 phone) remain reasonable GovSchema-convention encodings, not citations of a published DOS validation rule — unchanged.
  • Online and phone-reporting channels' exact data model were still not directly observed (the Online Form Filler at pptform.state.gov requires an interactive session; the phone channel per the PDF's own page 1 is "not available for customers abroad" and has no published field list). This document remains sourced from the paper/PDF Form DS-64, which travel.state.gov states is the same underlying report; source.url/ documentRef target that paper form specifically, so this is a documented scope decision, not a gap blocking verified status — the same pattern applied to other login-gated online channels in this registry (e.g. nz/dia/realme-verified-identity).
  • Pairing with Form DS-11. isConnectedToNewApplication's description and the document description's reference to us/dos/passport-application-ds11 both re-confirmed against the live page's "While applying for a new one" section, which states the applicant "must include information about your most recent passport while filling out Form DS-11" and that DOS "may pause your application and ask you to submit Form DS-64" if that information is incomplete — consistent with this schema's existing framing of DS-64 as submitted together with DS-11 in the common case.

Noted aside, not fixed this pass (out of scope for this review)

Several fields whose description already says "Personal identifier; handle as sensitive data" (lastName, firstName, middleName, nameAtPassportIssuance, telephoneNumber, alternateTelephoneNumber, emailAddress) do not carry the optional classification: sensitive-pii member that this document's own v1.0.0→v1.1.0 spec-migration bump already applied to dateOfBirth, socialSecurityNumber, lostPassportBookNumber, and lostPassportCardNumber. This is a partial GSP-0006 classification backfill, not something this verification pass's practice (field/type/ requiredness/validation/flow accuracy against the live source) covers; flagged for whoever next runs a classification-backfill pass over this document, same pattern as the de/bmi/residence-registration v1.1.1 aside.

Re-verification

Per the practice's Cadence, nextReviewBy is set to 2027-01-01 (6 months). Re-check the source on or before that date, on any source.url change, or when the U.S. Department of State publishes a new Form DS-64 revision.

View the raw record (VERIFICATION.md)

Version history

Independent and non-affiliated

GovSchema is an independent, open-source project. This reference is not produced, reviewed, or endorsed by U.S. Department of State, Bureau of Consular Affairs or any government. The authoritative source is always the live government form and its official instructions.