Administrative documents are written for readers who were not present, and DA Form 7306 is no exception. Titled WORKSHEET FOR TELEPHONIC NOTIFICATION OF GROUND ACCIDENT, it is used to worksheet for telephonic notification of ground accident — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date 10/01/2013 and the status ACTIVE. Its 1 page(s) and roughly 200 fields are sized to what the record must prove years later, which is always more than the moment appears to need. A newer edition exists. This one is retained because the documents completed on it were completed under its terms and are read under them.
Two offices stand behind the form, and the distinction between them explains most of what follows. DAS is the proponent: it decides what the form asks and revises it when the underlying process changes. AR 385-10 is the prescribing authority: it decides when the form is raised at all and where the completed document travels. Content and occasion are separated deliberately, so that a change in procedure does not require redesigning the page.
Identification precedes substance for a structural reason. Name, identification number, organisation and date of preparation are how the finished document is located in a file or a database; the body of the form is what someone reads after the search has succeeded. Spell the name as official records spell it, since the search runs against those records and not against habit.
Much of the form's behaviour follows from its being a fixed page. Tab order was set at build time along the reading sequence, which is why tabbing catches boxes a pointer passes over. Exclusive groups release one choice when another is made because a record cannot carry two answers to a single question. Single-line fields refuse to wrap because every entry must print where the layout expects it — text beyond the width is lost at the margin, visible on screen to the end. That is what remarks areas and continuation sheets are for. Marking a field that does not apply matters for a related reason: emptiness is ambiguous, and a reviewer reading the file later cannot distinguish an omission from a decision.
A signature is what converts entries into a record, which is why it comes last and why an unsigned form remains a draft however complete it looks. Where a reviewing official, an approving authority or a witness also signs, each adds a distinct attestation, and each dates the day of signing rather than the day of preparation — the dates trace the sequence of responsibility. The recurring defects are worth knowing precisely because they defeat that purpose: an empty mandatory field leaves an obligation unmet, transposed identification digits attach the record to nobody, a date with day and month reversed puts events in the wrong order, and entries left in a reused working copy assert facts nobody intended.
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
Why several files for one page? Because the form has to be completed in a headquarters and in places without a workstation, and PDF, XFDL covers both. The fillable pdf holds interactive fields that fix each entry in place and remove handwriting from the equation. The printable pdf is the same layout without those fields, meant for a printer and a pen. Neither is a lesser copy of the other; each answers a condition the other cannot.
Where a file opens matters more than it appears to. A browser will display a pdf, but browser viewers were built to read documents, and some accept keystrokes into fields they never intended to store — the entries are gone at tab close, without warning, because saving was never part of what that viewer does. A dedicated reader is built around the file's own structure and keeps what you enter. The xfdl file belongs to a different lineage entirely: IBM Lotus Forms, adopted across Army systems for the routing and signature handling built into it. That is why only the Lotus Forms Viewer reads it.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- ACCDNT_A
- ACCDNT_B
- ARMYCVLN
- BOX2
- BOX4
- CASENUM
- COMMANDR
- COMMRCAL
- CVLIAN
- CheckboxStyle1
- ContentArea1
- DAY
- DAY_A
- DAY_B
- DSN
- ENLSTED
- EXACLOC
- FATAL
- HGHRNK
- MACOM
- MONTH_A
- MONTH_B
- NAME
- NEARSITE
Disposition is prescribed, not chosen. AR 385-10 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.
Series and number are how the DA series signals which documents belong together, and the grouping follows real process boundaries: a shared proponent or directive usually means a shared purpose. A form cited on the face of another is part of that same transaction, and continuation sheets, covers and transmittals complete it.
Editions change because the process changes, and the printed edition date is the only marker of which version a page belongs to. A copy saved locally cannot know it has been superseded, so the date on it is compared against the edition in force before reuse. Records already executed under an earlier edition are left alone — a document is read under the terms it was made, and reopening completed files to match a later form would falsify the account.
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 DAS or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 7306?
- WORKSHEET FOR TELEPHONIC NOTIFICATION OF GROUND ACCIDENT
- Which edition is current?
- 10/01/2013
- Who is responsible for this form?
- DAS
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 42-ITEM ONLY PRODUCED IN ELECTRONIC MEDIA