Every entry on DA Form 5957 exists because a record system needs it in writing. The form's official title is RADAR DEPLOYMENT ORDER (LRA), and it is raised whenever an office must radar deployment order (lra) in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 10/01/2020, status ACTIVE, is what stands here, spread across 1 page(s) and about 95 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give. A later edition has since been published, which is why this one remains: records executed against it must still be readable in the terms they were written.
The form has an author and an occasion, held by different authorities. T2COM owns the content and reshapes it when what is being recorded changes. ATP 3-09.12 governs the event that calls for the form and the route the finished document takes afterwards. Keeping those two apart is what allows a procedure to be amended without the page being rebuilt each time.
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.
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
Why several files for one page? Because the form has to be completed in a headquarters and in places without a workstation, and PDF 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.
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.
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
- Acknowleg1
- Acknowleg2
- Acknowleg3
- Acknowleg4
- Acknowleg5
- AffectingFrie1
- AffectingFrie2
- Alternate1
- Altitude1
- Altitude2
- Altitude3
- Altitude4
- Altitude5
- CallSign1
- CallSign2
- ContentArea1
- Easting1
- Easting2
- Easting3
- Easting4
- Easting5
- LeftEdge1
- LeftEdge2
- LeftEdge3
Where the signed form goes is settled by ATP 3-09.12 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.
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.
An edition marks the form at a point in a process that keeps moving, and the date printed on the page is what distinguishes one from another. Since a saved file never announces its own obsolescence, compare its date against the current edition before using it again. Prior executions remain valid: the change applies forward, and a record is read against the edition it was written under.
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 T2COM or your servicing administrative office.
Questions and answers
- What is DA Form 5957?
- RADAR DEPLOYMENT ORDER (LRA)
- Which edition is current?
- 10/01/2020
- Who is responsible for this form?
- T2COM
- In which formats can it be downloaded?
- PDF, PDF
Publisher notes
- 42-ITEM ONLY PRODUCED IN ELECTRONIC MEDIA