Every entry on DA Form 2397-6 exists because a record system needs it in writing. The form's official title is TECHNICAL REPORT OF US ARMY AIRCRAFT ACCIDENT, PART VII - IN-FLIGHT OR TERRAIN IMPACT AND CRASH DAMAGE DATA, and it is raised whenever an office must technical report of u.s. army aircraft accident part vii - in-flight or terrain impact and crash damage data in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated February 2009, status not stated, is what stands here, spread across 2 page(s) and about 200 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 OCSA, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by PAM 385-40. 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.
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.
Personal information may not be gathered silently, and the Privacy Act statement is how that obligation is met on paper: it names the collection authority, the purpose, the routine uses and whether disclosure is mandatory. Because it exists to inform a decision, it belongs before the fields it covers rather than after them. A filled copy then holds personal data and is stored and transmitted under the corresponding safeguards.
Download the form
Formats exist because completion happens under different conditions, not because anyone wanted variety. The published set is PDF, XFDL. A fillable pdf carries live entry objects, so typed text lands in fixed positions and stays legible whoever reads it later. A printable pdf drops those objects and leaves the page as an image, which is what an office needs where a screen is unavailable and a pen is not. The document itself is unchanged between them; what differs is the circumstance each anticipates.
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.
No charge and no account apply: these are published documents, and access to them is not something a distributor is entitled to price.
What the form asks for
- AIRCRAFT
- AIRSPEED
- ANGL_DEG
- ANGL_DOWN
- ANGL_UP
- ANG_DEGREE
- BIRDS
- CABPENE_A
- CABPENE_A_1
- CABPENE_A_2
- CABPENE_A_3
- CABPENE_B
- CABPENE_C
- COCKPIT_A
- COCKPIT_B
- COCKPIT_C
- COCKPIT_C_1
- COCKPIT_C_2
- COCKPIT_C_3
- COCKPIT_C_4
- COCKPIT_D
- COCKPIT_D_1
- COCKPIT_E
- COCKPIT_E_1
Where the signed form goes is settled by PAM 385-40 rather than by the office holding it — a named recipient, the unit administrative channel, or the individual's own file, depending on why it was raised. Retention likewise belongs to the records schedule for the series, which exists so documents are kept for as long as anyone might need them and no longer. Keep a copy before release; the original serves the file from then on, not you.
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.
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.
One boundary should be stated clearly. What is distributed here are copies of published Department of the Army forms; the site is independent, issues nothing of its own, and holds no position in the system it describes. Proponency, prescribing directives and retention schedules operate without reference to it. Consequently nothing here is legal advice and no assurance about acceptance is possible. Questions about a particular entry, a requirement or eligibility belong with OCSA or your servicing administrative office.
Questions and answers
- What is DA Form 2397-6?
- TECHNICAL REPORT OF US ARMY AIRCRAFT ACCIDENT, PART VII - IN-FLIGHT OR TERRAIN IMPACT AND CRASH DAMAGE DATA
- Which edition is current?
- February 2009
- Who is responsible for this form?
- OCSA
- In which formats can it be downloaded?
- PDF, XFDL