Skip to content
Aletheca
FAAFederalTransportation

Federal Aviation Administration

Component of Department of Transportation

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

    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

  1. 1portalhttps://www.foia.gov/agency-search.html
  2. 2mailFederal Aviation Administration 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

FiledALT-2026-1055FAA

FAA radar data, controller voice recordings, facility logs and inquiry files for Phoenix-area airspace, 13–14 March 1997

Records of the Air Traffic Organization and its 1997 predecessor (Air Traffic Services / Western-Pacific Region, AWP) concerning the evening of 13 March 1997 and the early hours of 14 March 1997, specifically: (a) any continuous data recording, NTAP or equivalent radar target history for Phoenix TRACON (P50), Phoenix Sky Harbor tower and Albuquerque ARTCC (ZAB) sectors covering the Phoenix metropolitan area and the corridor south toward the Barry M. Goldwater Range, 0200Z–0600Z on 14 March 1997; (b) any controller voice recordings, transcripts or reduced-tape transcriptions for those positions in the same window; (c) daily records of facility operation and position/watch logs (FAA Form 7230-4 or successor) for P50, PHX tower and ZAB for 13–14 March 1997; (d) any pilot report, UFO or unidentified-traffic report, or flight-assist record generated at those facilities on those dates, and any transmittal of such a report to another agency; (e) records showing whether any radar or voice media for that period were impounded, retained, copied or transferred, and if not, the records-retention schedule and destruction authority applied to them; (f) correspondence, congressional and public inquiry files, and public-affairs talking points held by the Western-Pacific Regional Office or the Administrator's office concerning the 13 March 1997 Arizona sightings, 13 March 1997 through 31 December 1998. If any category no longer exists, we request the retention schedule, the destruction certification if one exists, and a description of the record systems searched.

Filed Sep 9, 2026