DD Form 1748-7 occupies a particular place in Defense recordkeeping. Its title is JOINT AIRDROP INSPECTION RECORD (JPADS - PRECISION AIRDROP), and it exists to Joint Airdrop Inspection record (JPAS-Precision Airdrop). What the DD prefix records is an administrative judgment made long before your copy was printed: this transaction was determined to be common to the whole Department rather than peculiar to one service, and so the documentation of it was standardized at Department level.
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.
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.
Verify the printed edition against not stated first. Field structure shifts between editions, and the office that receives your record is reading the current one. That office may sit outside your service, which removes even the informal accommodation you might expect from a colleague who used the old version last month.
Leave nothing empty. Where an item genuinely does not apply, N/A is the correct entry, because the record must distinguish between a question that was answered in the negative and a question that was never reached. An empty box carries no information about which happened. Date fields deserve particular care on a Department form, since the reviewer may write dates by a convention different from yours; use the format the form itself specifies.
The Privacy Act Statement is not boilerplate appended for legal cover; it is the mechanism by which a statutory obligation is discharged at the moment of collection. When the government asks an individual for personal information, it must state the authority under which it asks, the principal purpose, the routine uses to which the data may be put, and whether answering is voluntary or mandatory. Those four disclosures are placed ahead of the data fields deliberately, because the point of telling you is to inform a choice you have not yet made.
What the signature block asks for is an act, not a text. Ink on a printed copy performs that act; a digital signature bound to your credential performs it electronically, CAC-based in most Defense systems. Typing your name performs nothing, since anyone with the file could type the same characters. Enter the date at the same moment: the certification is a statement about a point in time and needs one recorded.
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 1 pages and about 185 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.
All of it downloads without charge. Where care is needed is in the reader you choose. A fillable pdf depends on field properties that desktop applications honour and browser previews frequently ignore, so work locally rather than inside a browser window.
What the form asks for
- A.1
- A.2
- A.3
- A.4
- A.5
- A.6
- A.7
- AFTER_L
- A_Parachutes
- A_Transported
- B.1
- B.2
- B.3
- B.4
- B.5
- B.6
- B.7
- B.Containers
- BEFORE_L
- B_Airlift
- Blackbox10
- Blackbox17
- Blackbox18
- Blackbox3
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.
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.
A form is downstream of the policy that requires it, and revision usually starts there: a directive is reissued, a collection requirement is altered, notice language is updated by statute. The form is republished as a consequence. Since none of that reaches individual users, an archived copy quietly becomes wrong, and verifying not stated each time you download is the whole remedy.
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 1748-7?
- JOINT AIRDROP INSPECTION RECORD (JPADS - PRECISION AIRDROP)
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?