AF Form 4377 is the Air Force Command Post daily events log, the official chronological record of everything that affects the unit or Command Post operations during a 24-hour Zulu period. It is prescribed by AFMAN 10-207, opens at 0001Z, and closes at 2359Z.1Department of the Air Force. AFMAN 10-207 – Command Posts It is not the Security Forces desk blotter; that is AF Form 53, governed by a different manual and career field.
Where To Get the Current Form
The current version of AF Form 4377 is dated 04 Apr 2008 and is available through the Department of the Air Force E-Publishing website. Type the product number into the search box without spaces, as “AF4377,” and click Find it.2Department of the Air Force E-Publishing. Department of the Air Force E-Publishing FAQ Searching “AF Form 4377” with spaces will not return the form. If you only know the name, search “Events Log” instead and browse the results.
Computer-generated versions are authorized on two conditions: every field on the original must appear on the digital version, and the text “CG AF FORM 4377” must appear clearly at the bottom left of the printout.1Department of the Air Force. AFMAN 10-207 – Command Posts Some Major Commands prescribe alternative media for the events log, so check your MAJCOM supplement before assuming the standard form is what your installation uses.
How To Fill Out the Events Log
The purpose of the log is to let someone who was not present reconstruct what happened during a 24-hour window. That principle should drive every entry. A reader jumping to a single line should be able to tell what happened, when, who was involved, and what action followed, without reading the surrounding entries for context.
Each log covers one Zulu day. Open a fresh AF Form 4377 at 0001Z and close it at 2359Z.1Department of the Air Force. AFMAN 10-207 – Command Posts All timestamps use Zulu (UTC) time, not local time. If your installation is in the Central time zone, an event at 2:30 p.m. local during Central Daylight Time would be logged as 1930Z.
Write entries in chronological order and keep them factual. Record what happened, when, who was involved, and what follow-up actions were taken or directed. Skip opinions, speculation, and editorializing. If a report came in secondhand, note the source.
The events you record will depend on your unit’s mission and MAJCOM guidance, but they generally cover operational events (mission launches, aircraft emergencies, changes to readiness posture, exercise inputs, higher headquarters directives), personnel notifications (recall initiations, key personnel status changes, command authority transfers), facility and communication issues (system outages, backup activations, alarms relayed from other agencies), and administrative actions (shift changeovers, controller sign-on and sign-off times, routine system checks).
Accuracy and Legal Exposure
Every entry is an official record. Deliberately entering false information, or signing off on entries you know to be inaccurate, exposes you to prosecution under Article 107 of the UCMJ, which covers false official statements by anyone subject to the UCMJ who signs a false record or makes a false official statement with intent to deceive.3Office of the Law Revision Counsel. 10 U.S.C. 907 – Art. 107 False Official Statements, False Swearing The punishment is whatever a court-martial directs, ranging from forfeiture of pay to confinement depending on the circumstances.
Because the log contains names, ranks, and identifying information, federal agencies that maintain such records are required by the Privacy Act of 1974 to keep them accurate, relevant, timely, and complete.4Department of Justice. Privacy Act of 1974 Verify spellings, ranks, and unit designations before finalizing entries. To correct an error after the fact, follow your local amendment procedure, typically a line-through with initials and the correct information, or a corrective entry on electronic logs. Do not delete or overwrite the original.
Shift Changeover and Closeout
The log does not close at shift change. It runs the full 0001Z-to-2359Z period. At the end of a shift, the outgoing controller briefs the incoming controller on all open items and significant events, and the changeover itself gets its own entry noting who is coming on duty and who is departing. This preserves an unbroken chain of accountability across the Zulu day.
Once the log closes at 2359Z, it routes through the chain of command for review. The Flight Commander or senior controller on duty typically reviews the completed log for accuracy and completeness, often as part of the next day’s turnover. If your Command Post uses a computer-generated format, save the final version to a location accessible to leadership, not a local workstation.
Retention and Storage
Completed AF Forms 4377 are official Air Force records and must be managed under the Air Force Records Management and Information Governance Program.5Department of the Air Force. AFI 33-322 – Records Management and Information Governance Program The retention period depends on the records disposition schedule that applies to your unit. Your MAJCOM or local records manager can confirm the exact schedule for Command Post logs at your installation.
Store logs so they cannot be altered or accessed by unauthorized personnel. Electronic logs belong on a network drive with access controls, not a thumb drive or a personal folder. Paper logs go in a secured area. If a log is ever placed under a litigation hold, meaning it could be relevant to legal proceedings, do not destroy it regardless of what the normal disposition schedule says.
Requesting a Completed Log Through FOIA
Members of the public or former service members who need a copy of a completed AF Form 4377 can submit a Freedom of Information Act request. The fastest route is the Air Force’s online Public Access Link at efoia.cce.af.mil.6Air Force Compliance Division. FOIA No special form is required. Describe the records as specifically as possible, including the date range, installation, and any other detail that would help the office locate the log.
To submit by mail, or if you don’t know which installation holds the records, send the request to Headquarters Air Force/AAII (FOIA), 1000 Air Force Pentagon, Washington, DC 20330-1000, and mark both the letter and envelope “FOIA.”6Air Force Compliance Division. FOIA You can also submit directly to the FOIA Requester Service Center at the specific base holding the records, which is usually faster than going through headquarters. Fees depend on requester category, with reduced or waived charges for news media, educational institutions, and non-commercial requesters.7U.S. Army Corps of Engineers. FOIA Schedule of Fees – 32 CFR 286.12 Include a statement in your request naming the maximum amount you are willing to pay so the office can contact you before charges exceed it.
AF Form 4377 Compared With AF Form 53
The two forms are commonly confused because both are chronological logs of daily activity, but they belong to different career fields. AF Form 53, the Security Forces Desk Blotter, is prepared by the security forces controller at each control center, covers the tour of each flight, and is governed by AFMAN 31-201.8United States Air Force. AFMAN 31-201 Volume 7 – Security Forces Administration and Reports AF Form 4377 is the Command Post events log, governed by AFMAN 10-207, and runs on Zulu time rather than local shift schedules. Security Forces personnel use AF Form 53; Command Post controllers use AF Form 4377.