Consider what a Department-level form is for. DD Form 651 — Carrier's Report of Vehicle Damage or Breakdown — was established to Carrier's Report of Vehicle Damage or Breakdown, and it was placed in the DD sequence because the underlying transaction occurs throughout the Defense establishment in substantially the same shape. Standardizing the record was cheaper and more reliable than letting six services each design their own.
That decision has consequences you will notice. Because not stated prescribes the form for the Department as a whole, and not stated maintains it on the Department's behalf, the same blank passes between the Army, the Navy, the Air Force, the Marine Corps, the Space Force, the Coast Guard when operating under Defense jurisdiction, the defense agencies and the combatant commands without translation. A clerk in one component reads a record created in another and finds the fields where they expect them.
Current edition: not stated, status not stated. Understand why that date is worth attention here. When the Department reissues a form, the replacement takes effect across every component simultaneously, so an older copy is not merely locally out of date — it is out of date in every office that might receive it.
The sequence printed on the form is the sequence in which a reviewer will read it, and the two should agree. Header data frames every entry below it; the substantive fields depend on that frame; the certification stands at the end because its whole function is to vouch for what came before. Entries made out of sequence commonly contradict entries made earlier.
Check the edition date before you type anything, against not stated. Old blanks accumulate in shared drives for years, and the cost of one is not obvious until a reviewer cannot find a field. Because DD forms are revised centrally and replaced across the Department in a single action, there is no component still tolerating the old layout as a local practice.
Every field takes an entry, N/A included. The reason is evidentiary rather than clerical: a completed record is supposed to show what was asked and what was answered, and blank space records neither. On dates, follow the format printed beside the field. Conventions vary between components, and a joint document is read by people who do not share your habits.
Where the form collects personal identifiers, a Privacy Act Statement accompanies it, and its placement is meaningful. The statute requires disclosure at the point of collection — authority, purpose, routine uses, and the consequence of declining — so that the person supplying the information does so knowing what becomes of it. Reading it after you have filled the fields inverts the arrangement entirely.
The signature converts entries into an attestation, and that is why its form is prescribed. Ink, or a digital signature carrying a credential that identifies the signer — commonly issued on a Common Access Card. Typed characters in the box satisfy neither standard, because the whole value of a signature lies in being difficult to produce on someone else's behalf. Date it as you sign; an undated attestation cannot be placed in the sequence of events.
Recurring defects have a pattern to them, and it is mostly the pattern of a record that cannot be relied on: an edition that does not match, gaps that cannot be interpreted, entries that cannot be read after scanning, dates that could mean two things, and a certification nobody executed. For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
Formats available: PDF, across unknown pages and about unknown fields. That several formats coexist is a consequence of scale — the Department cannot standardize the software on every desk that needs this form, so it standardizes the document instead.
Two states of the same page circulate, and the reason is worth knowing. In the fillable pdf, the boxes are real fields holding real data; in the printable pdf, the boxes are drawings. Where a record will cross components — as Department records regularly do — the typed version is the safer artifact. Each scan, each forwarding, each reproduction costs handwriting a little legibility, and the office that finally files the record is rarely the office that received it first.
If you find an xfdl file here, its presence is historical. The format belongs to IBM Lotus Forms, which the Department adopted Department-wide for electronic forms and fielded on a scale that makes wholesale removal slow. You need the matching viewer to open it; ordinary pdf software cannot read the format and will say so unhelpfully.
Every format is free, as published government documents are. A note on tools, though — the interactive field layer that makes a fillable pdf useful is precisely the part browser viewers handle least reliably. Save the file, open it in a full pdf reader, and the fields behave as the form's designer intended.
Submission follows not stated and whatever local instruction supplements it. Make a copy before the original leaves. Department forms travel across organizational lines by design, and the administrative distance that makes them useful is the same distance that makes tracing a lost one difficult.
When DD Form 651 cites another form, the citation is self-sufficient. The DD series is a single sequence administered at Department level, so the number resolves to exactly one document without any need to establish which component issued it — a convenience that exists only because the sequence was never allowed to fork.
Where a service form is cited in the same instruction, the two numbering systems should not be read across. DA numbering belongs to the Army and is administered by an Army proponent; DD numbering belongs to the Department and is administered by not stated or an equivalent Department office. The systems developed separately and were never harmonized, so identical digits in each identify two documents with nothing in common. The prefix, not the number, tells you which system you are in.
Editions change for reasons that originate above the form itself. The prescribing directive is reissued and the form follows; the information the Department needs to collect changes and the fields change with it; the statutory notice language is amended and every form carrying that notice is republished. None of these events announces itself to the person who downloaded a copy last year, which is why confirming not stated at the moment of download is the only reliable check available to you.
The role of this page is narrow and worth stating plainly. It makes a published Defense form available and explains its structure. It does not advise, does not interpret policy for your circumstances, and cannot indicate how any office will treat a completed copy — those judgments rest with the authorities that own the process. Direct such questions to not stated, to the administrative office that services you, or to the authority named in not stated.
Questions and answers
- What is DD Form 651?
- Carrier's Report of Vehicle Damage or Breakdown
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?