Department of the Air Force

What happened when Aletheca filed

Requests filed

26

Median to determination

176 days

Past the deadline

72%

Released something

48%

Pages with redactions

66%

Glomar

4%

Fee waivers granted

46%

Appeals that changed it

20%

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. 01portalAgency FOIA Portalverified

   https://pal.foia.gov

2. 02emailEmailunconfirmed

   usaf@foia.usaf.gov

3. 03mailPostal 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. 1portalSAF/AAZ FOIA portal
2. 2mailSAF/AAZ, 1000 Air Force Pentagon

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 filed here