Download the form
Use DA Form 2397-4 when you need to technical report of u.s. army aircraft accident part v - summary of witness interview. Full title: TECHNICAL REPORT OF US ARMY AIRCRAFT ACCIDENT PART V - SUMMARY OF WITNESS INTERVIEW. Everything you need is on this page — the file, the entry rules, the routing. Edition February 2009, status not stated, 2 page(s), roughly 95 fields.
Authority sits in two places. OCSA owns the form, PAM 385-40 says when it is raised and where it goes. Routine cases need neither read in full — the page itself carries the sequence. The entries are completed by their subject or by unit administrative staff working from what that person supplies.
PDF, XFDL are available and the decision takes one second. Type your entries: fillable pdf. Write them: printable pdf. The published layout is common to both, so the format governs your method and nothing more.
Use a full pdf reader, not the browser viewer. Browser viewers display fields they cannot always save, and the loss shows up only when you reopen the file — type one entry, save, reopen, verify, then fill the rest. The xfdl file is IBM Lotus Forms, used inside Army systems, and opens in the Lotus Forms Viewer alone — no pdf reader, no word processor.
Free, unregistered, unmodified. What arrives is what the publisher released.
What the form asks for
- ADDRESS
- AGE
- Aircraft_SN
- Case_Date
- Case_Time
- ContentArea1
- Decline
- EXPERNC
- GRADE
- INTERVWR
- INTRVIEW
- Interviewer_Date
- LOCATE
- Line1
- Line2
- Line3
- NO_A
- Name_Witness
- OCCUP
- Page1
- Page2
- R26
- R39
- R41
The heading entries carry more weight than the body. Name spelled as in official records, identification number, organisation, date prepared. Retrieval runs on those values, so a transposed digit or a casual spelling costs someone a file search. Fill them before anything else.
Tabbing beats clicking for coverage. The order was set at build time and tracks the page layout, so following it leaves no gaps. Boxes and buttons are clicked; where options are exclusive, one selection cancels another by design. Watch field width on long entries: one-line fields have no wrap, and what runs past the edge disappears in print though the screen still shows it. Move that text to remarks or a continuation. Never leave an inapplicable field empty — enter the nil mark, because a reviewer cannot distinguish a skipped question from a considered answer.
Signature comes after every other entry — ink or an approved electronic means, and without it the document is a draft. Where reviewing, approving or witnessing signatures are called for, take them in printed block order, each dated on the day applied. Before release, one pass from the top. The defects worth hunting are always the same four: mandatory fields left empty, identification digits transposed, dates with day and month reversed, and stale data surviving in a copy reused in place of a blank form.
Privacy Act statement first, personal entries second. The notice covers who is authorised to collect, why, who else routinely sees it, and whether you must answer. After completion the file carries personal data and is stored and sent under the corresponding safeguards.
The prescribing directive names the destination; office custom does not. Depending on the case that means a specific office, the unit administrative channel, or the personal record. Keep a copy first, because the original does not come back. Retention runs on the applicable records schedule.
Companion documents come from the same series and number scheme. Within the DA series, a shared proponent or a shared directive usually means shared use, and a form cited on the face of another accompanies it. Gather the whole package first — continuation sheets, cover sheets, transmittals.
A stored file goes stale silently. The proponent revises, a new edition date is published, and your copy says nothing about it — so compare the printed date against the edition in force before typing into it again. Completed submissions on an earlier edition are not reopened.
What is distributed here are reproductions of published Department of the Army documents. Independent site, no official standing, no forms of its own. Nothing on the page constitutes legal advice, and acceptance by any office is outside what can be stated. Put questions about entries, requirements or eligibility to OCSA or your servicing administrative office.
Questions and answers
- What is DA Form 2397-4?
- TECHNICAL REPORT OF US ARMY AIRCRAFT ACCIDENT PART V - SUMMARY OF WITNESS INTERVIEW
- Which edition is current?
- February 2009
- Who is responsible for this form?
- OCSA
- In which formats can it be downloaded?
- PDF, XFDL