Skip to content
Aletheca
USAFFederalDefense & Military

Department of the Air Force

Component of Department of Defense

Computed from Aletheca filings. An unobserved outcome is shown as unknown.

What happened when Aletheca filed

Requests filed
1
Median to determination
Unknown
Past the deadline
Unknown
Released something
Unknown
Pages with redactions
Unknown
Glomar
Unknown
Fee waivers granted
Unknown
Appeals that changed it
Unknown

Computed from Aletheca’s own filings, whose full text is public. Not the agency’s self-reported Annual FOIA Report — where both exist they are shown side by side and never merged.

How it takes requests

  1. 01portalNational FOIA Portalverified

    https://www.foia.gov/agency-search.html

  2. 02mailPostal Mailunconfirmed

    Department of the Air Force FOIA Office, FOIA Requester Service Center, Washington DC 20208

Routes marked unconfirmed are inferred from the agency’s domain pattern in the source dataset and have not been proven by a delivered letter. Aletheca confirms an endpoint before the first request goes to it and records the confirmation as a public event — a request sent to a plausible-looking address that bounces silently is worse than no request at all.

Routes Aletheca actually uses

  1. 1portalhttps://www.foia.gov/agency-search.html
  2. 2mailDepartment of the Air Force FOIA Office, FOIA Requester Service Center, Washington DC 20208

Tried in this order; the router falls through when one fails and records the fallback as an event.

What it holds

  • correspondence
  • contracts
  • reports
  • emails
  • memoranda
  • data
  • policies

Record classes this kind of body normally keeps. Useful for drafting a request a records officer can act on without guessing — a request describing records the agency does not hold is refused as no-records, which costs a filing fee and teaches nobody anything.

Filing tips

  • Be specific on date range and custodians
  • Cite public-interest fee waiver and news-media status if applicable
  • Request Vaughn index for withholdings
  • Ask for rolling release

Requests in the archive

Showing 1–1 of 1 requests

ProcessingALT-2026-1056USAF

Luke AFB and Maryland ANG A-10 sortie, flare-drop and unit-history records for the Barry M. Goldwater Range, March 1997

Records of the Department of the Air Force and, through it, the Air National Guard units involved, for 1 March through 30 June 1997: (a) flying schedules, sortie/mission records, aircrew flight logs and range-use or range-scheduling records for training missions flown on the Barry M. Goldwater Range on the evening of 13 March 1997, including any night flare-delivery training; (b) munitions or expendables expenditure records showing the type, number and time of illumination flares (e.g. LUU-2 or equivalent) released that evening, and the altitude and coordinates of release; (c) records of the Maryland Air National Guard 104th Fighter Squadron / 175th Wing A-10 detachment deployed to Arizona in March 1997, including deployment orders and the detachment's operations records; (d) the 56th Fighter Wing (Luke AFB) annual or periodic unit history covering the first half of calendar year 1997, and the wing and Air National Guard public-affairs files, press releases, media queries and internal talking points concerning the 13 March 1997 Arizona light sightings; (e) any base or wing incident report, command post log entry, or inquiry into the sightings, and any correspondence with the FAA, the National Guard Bureau or members of Congress about them.

Filed Sep 9, 2026