Radar and ATC audio requests are routinely met on time and in full — the material is a business record rather than an intelligence one, and it shows in every column of the scorecard.
What happened when Aletheca filed
Requests filed
38
Median to determination
44 days
Past the deadline
41%
Released something
79%
Pages with redactions
22%
Glomar
0%
Fee waivers granted
61%
Appeals that changed it
50%
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
01portalAgency FOIA Portalverified
https://pal.foia.gov
02emailEmailunconfirmed
faa@foia.faa.gov
03mailPostal mailunconfirmed
Federal Aviation Administration 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
1portalFAA FOIA portal
2email7-awa-arc-foia@faa.gov
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
All radar data (NTAP or equivalent), controller audio recordings, and position reports for Salt Lake City ARTCC sectors 14 and 16 between 0200Z and 0500Z on 11 March 2026.
Filed Mar 16, 2026Agency ref 2026-00611421 backers