Military Forms Guide

DA Form 7335-R — TOW GUNNERY TABLES 5 AND 6 - BASELINE TFTT GUNNERY

tow gunnery tables 5 and 6: baseline tftt gunnery

Administrative documents are written for readers who were not present, and DA Form 7335-R is no exception. Titled TOW GUNNERY TABLES 5 AND 6 - BASELINE TFTT GUNNERY, it is used to tow gunnery tables 5 and 6: baseline tftt gunnery — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date August 2003 and the status not stated. 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.

The form has an author and an occasion, held by different authorities. TRADOC owns the content and reshapes it when what is being recorded changes. FM 3-22.34 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, 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.

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

  • BUTTON1
  • BUTTON10
  • BUTTON10A
  • BUTTON10B
  • BUTTON10C
  • BUTTON11
  • BUTTON11A
  • BUTTON11B
  • BUTTON11C
  • BUTTON12
  • BUTTON12A
  • BUTTON12B
  • BUTTON12C
  • BUTTON13
  • BUTTON13A
  • BUTTON13B
  • BUTTON13C
  • BUTTON14
  • BUTTON14A
  • BUTTON14B
  • BUTTON14C
  • BUTTON15
  • BUTTON15A
  • BUTTON15B

Where the signed form goes is settled by FM 3-22.34 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.

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.

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. TRADOC 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 7335-R?
TOW GUNNERY TABLES 5 AND 6 - BASELINE TFTT GUNNERY
Which edition is current?
August 2003
Who is responsible for this form?
TRADOC
In which formats can it be downloaded?
PDF, XFDL

Other forms in the series