Every entry on DA Form 3265 exists because a record system needs it in writing. The form's official title is EXPLOSIVE ORDNANCE INCIDENT REPORT, and it is raised whenever an office must explosive ordnance incident report in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 04/01/2014, status ACTIVE, is what stands here, spread across 1 page(s) and about 104 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give.
Behind any Army form sit two separate decisions. What the document asks is settled by TJAG, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 75-15. That division is the reason a form can outlive several changes in the process it serves.
Retrieval governs the order of entry. The head of the form takes name, identification number, unit and date, and those values become the handles by which the record is found later — the substantive blocks are never searched on. This is why the spelling must match official records exactly rather than approximately.
The rules of entry all trace back to the page being fixed in advance. Tabbing follows the order built into the form, which usually matches how the page reads and misses less than clicking. An exclusive group discards the earlier selection because contradictory entries would make the record unusable. One-line fields have no wrap because print positions are predetermined, so an overlong entry displays fully and prints truncated. Longer text goes to the remarks area or a continuation, both provided for exactly that. Where nothing applies, the nil mark is entered — a blank leaves the reader unable to tell a considered answer from a skipped one.
Signing is the act that makes the document evidence, and until it happens the entries are only a proposal. Additional signatures — reviewer, approver, witness — each stand for a separate judgement, dated when applied so the record shows who accepted what and in what order. The common faults all damage that record in the same way: a blank mandatory field breaks the chain of required answers, swapped digits in an identification number detach the document from its subject, an inverted day and month misplaces it in time, and stale data from a reused copy states things nobody meant to state.
Behind the Privacy Act statement is a requirement that anyone asked for personal data be told, in advance, under what authority it is sought, for what purpose, who else routinely sees it, and whether refusal is possible. Reading it after completing the fields defeats its function. And the completed form is itself a personal record from that point on, subject to the handling rules such records carry.
Download the form
The published formats — PDF, XFDL — reflect the range of places a form gets filled in. Where there is a computer, the fillable pdf supplies live fields that keep entries positioned and readable. Where there is not, the printable pdf gives the identical page as flat artwork for pen entry. The distinction is one of setting rather than of authority; the page is the same document in both.
The choice of application decides whether your work survives. Browsers render pdfs as documents to be read; where a viewer shows fields without a mechanism to store them, typed text disappears when the tab closes, and nothing announces the loss. A full reader treats the file as a form and preserves entries on save. The xfdl format comes from IBM Lotus Forms, used across Army systems because of the routing and signature functions built into it, and it opens in the Lotus Forms Viewer alone.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- ADDRESS
- AIR
- ARR
- COMPL
- CONFIRMED
- CONTROL
- ContentArea1
- DATE
- DATE_A
- DISPO
- DPRT
- INCIDENT
- INCIDENT_B
- ITEMS
- NAME
- NARRATIVE
- PERSONNEL
- PHONE
- POINT
- Page1
- R70
- R71
- R72
- R73
Disposition is prescribed, not chosen. AR 75-15 names the destination, whether that is a specific office, the unit administrative channel or the personal record, and the applicable records schedule governs how long it survives there. Both rules exist to keep the file consistent across offices with different habits. Take your copy before the document leaves, since it will not come back.
Forms cluster by series and number for the same reason files do: shared proponency and a shared prescribing directive usually mean a shared process. So a document in the DA series referenced on the face of another is generally part of the same transaction, and continuation sheets, cover sheets and transmittals belong to the package from the outset rather than arriving after a query.
Revision follows the process, which is why editions appear without a fixed interval, and the printed date rather than any version number identifies them. Nothing on a stored copy signals that it has aged; the check is manual. Work already completed under a superseded edition stands as filed, because the record was made under those terms and is properly interpreted under them.
A word on where this page sits. These are reproductions of published Department of the Army documents, made available by an independent site with no official role and no authority to issue forms. The structure described above — proponent, prescribing directive, records schedule — exists apart from this site entirely, which is why nothing written here is legal advice and why acceptance by any office is not something that can be promised. Put questions of entry, requirement or eligibility to TJAG or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 3265?
- EXPLOSIVE ORDNANCE INCIDENT REPORT
- Which edition is current?
- 04/01/2014
- Who is responsible for this form?
- TJAG
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 42-ITEM ONLY PRODUCED IN ELECTRONIC MEDIA