Consider what a Department-level form is for. DD Form 1721-2 — DD Form 1721-2, Space Test Program After Action Report, September 2006 — was established to Space Test Program After Action Report, 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.
The practical effect of Department-level issue is interoperability. not stated establishes the requirement across the Defense enterprise; not stated keeps the document current for all of it. No service maintains its own variant, which means a completed record travels between components — service to agency, agency to joint command — and arrives in a format the receiving office already knows how to read.
The edition in force is not stated, carried by the publisher as not stated, and edition discipline is stricter on a Department form than most people expect, precisely because supersession happens everywhere at once. There is no interval during which one service still works from the previous layout while another has moved on.
Work down the page in the printed order, and understand why the order exists. The identifying block establishes whose record this is and under what circumstances it arises. The body of the form then answers questions that are only meaningful once that context is fixed. The signature block comes last because a certification signed before the entries are complete certifies nothing.
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.
Unclear entries are resolved from the printed instructions first and from not stated where the two texts diverge.
Download the form
What you can download: PDF. The form runs 4 pages and asks for approximately 52 entries. The plurality of formats is deliberate: Defense distribution has never been able to assume one operating environment across the whole force.
Fillable and printable are not two presentations of one file but two different objects. One holds your entries as structured data within the document; the other is a static picture meant to meet a pen. Since a DD form frequently moves outside the organization that created it, the durability of the entry matters more here than on a record that stays in one drawer. Typed text reproduces indefinitely; handwriting degrades at every copy.
What the form asks for
- 5. Objective.
- 6. Flight data. a. Launch Date (4 digit year, 2 digit month, 2 digit day, no dividers).
- b. Mission duration (mission/experiment).
- c. Launch vehicle.
- d. Launch site.
- e. Host vehicle/platform.
- f. Inclination.
- g. Orbit (km). Apogee.
- Plus.
- Minus.
- Perigee.
- Plus.
- Minus.
- h. Special characteristics.
- i. Experiment cost (millions of dollars).
- j. Experiment weight (kg).
- k. Experiment volume (cc).
- l. Nominal/peak power (w).
- m. Picture of experiment (insert file or cut and paste).
- Date (4 digit year, 2 digit month, 2 digit day, no dividers).
- Part 1 - Request for Spaceflight. 1. Experiment title.
- 2. Short title/acronym.
- 3. Experiment number.
- 4. Sponsor organization.
The completed form goes to the office named in not stated or in local implementing procedure, and it is worth keeping a copy before it goes. On a Department form the destination is frequently outside your own chain — another service, a defense agency, a joint staff — and recovering a document that has crossed an organizational boundary is a slower business than retrieving one from a file down the hall.
Forms referenced inside this one are located by number alone, and that simplicity is a direct product of Department-level numbering. Because the DD sequence is maintained centrally and not duplicated by service, a number is a complete address: one number, one document, throughout the Defense establishment.
It helps to see the DA and DD sequences as what they are: separate registries with separate custodians. One serves a single service under a service proponent, the other serves the Department under not stated or an equivalent office, and neither was ever indexed against the other. A number that appears in both systems points to two unrelated documents, which is why reading the prefix comes before reading the digits.
Understanding why editions change explains why checking them is not optional. Revision follows directive reissue, changes in what data is required, and amendments to mandatory notice text — decisions made at Department level and communicated through publication rather than notification. The file you saved does not update itself, so the edition date at download is what you rely on.
What you have here is the document and a description of it, which is a different thing from guidance. This page is not an organ of the Department, gives no legal or procedural advice, and makes no representation about the outcome of any filing; the offices that administer the requirement are the only ones positioned to answer that. Applicability, eligibility and procedural questions belong to not stated, to your servicing personnel office, or to the office designated in not stated.
Questions and answers
- What is DD Form 1721-2?
- DD Form 1721-2, Space Test Program After Action Report, September 2006
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?