Military Forms Guide

DA Form 2397-11 — TECHNICAL REPORT OF US ARMY AIRCRAFT ACCIDENT, PART XII - WEATHER/ENVIRONMENTAL

technical report of u.s. army aircraft accident part xii - weather/environmental

Every entry on DA Form 2397-11 exists because a record system needs it in writing. The form's official title is TECHNICAL REPORT OF US ARMY AIRCRAFT ACCIDENT, PART XII - WEATHER/ENVIRONMENTAL, and it is raised whenever an office must technical report of u.s. army aircraft accident part xii - weather/environmental 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 1 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.

Two offices stand behind the form, and the distinction between them explains most of what follows. OCSA is the proponent: it decides what the form asks and revises it when the underlying process changes. AR 385-40 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.

The heading blocks come first because the record is retrieved by them, not read into. Name as official records spell it, identification number, unit, date of preparation — those four are the index, and everything below them is content that only surfaces once the index has done its work. A form filed under a name written casually is not lost in principle, only in practice, which amounts to the same thing.

Tab order is not a convenience feature; it was fixed when the form was built and generally traces the page, so following it produces the sequence the designer intended and leaves fewer gaps than a mouse. Exclusive option groups clear the previous selection because the record is not permitted to hold two contradictory answers. Single-line fields do not wrap for the same reason the layout is fixed: the printed page has to fall in known positions, so text past the field width is cut at the margin even though the screen still shows it whole. Overflow belongs in remarks or on a continuation, where there is room designed for it. And an inapplicable field is marked rather than skipped, since a blank tells a later reader nothing about whether the question was considered.

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

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.

Software determines whether an entry lasts. A browser viewer is designed for reading, and several will take typed input into fields without any means of writing it back — the text is simply absent when you reopen. A standalone reader handles the form structure properly. The xfdl file is IBM Lotus Forms, carried in Army systems for the routing and signature support it provides, which is why the Lotus Forms Viewer is its only reader.

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

  • ALT_PRESS
  • ALT_READ
  • ALT_SETT
  • BROKEN
  • CLEAR
  • CONTIN
  • CONTIN_1
  • CONTIN_2
  • CONTIN_3
  • CONTIN_4
  • CORRECT
  • ContentArea1
  • DATE
  • DEGREES
  • DIR
  • ENVIR_D
  • ENVIR_N
  • ENVIR_S
  • ENVIR_U
  • FEET_A
  • FEET_B
  • FEET_C
  • ICING_N
  • ICING_Y

Disposition is prescribed, not chosen. AR 385-40 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.

Related documents are located by series and number, and the relation is rarely accidental — forms under one proponent or one directive tend to serve steps of a single procedure. Anything the DA series form names on its face normally travels with it, as do the continuations, covers and transmittals the process generates. Assembling them together is what makes the submission a complete account.

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.

It is worth being plain about what this page is within all of the above. The files are reproductions of published Department of the Army documents, offered for download by a site with no official standing and no part in issuing anything. That matters because the machinery described here — proponency, prescribing directives, records schedules — runs entirely elsewhere. Nothing written here is legal advice, and no statement can be made about whether an office will accept a given document. OCSA and the administrative office servicing your unit answer questions of entry, requirement and eligibility, and they are the ones positioned to.

Questions and answers

What is DA Form 2397-11?
TECHNICAL REPORT OF US ARMY AIRCRAFT ACCIDENT, PART XII - WEATHER/ENVIRONMENTAL
Which edition is current?
February 2009
Who is responsible for this form?
OCSA
In which formats can it be downloaded?
PDF, XFDL

Other forms in the series