Built 2026-09-23 (Wednesday, September 23, 2026)

Archive Methodology & Data Pipeline

Technical explanation of how TFR Archive captures, normalizes, classifies, and permanently preserves temporary flight restrictions across United States national airspace.

Key facts
Advertisement space: methodology-top (Reserved to prevent cumulative layout shift)

1. Why 15-Minute Polling

Standard daily web scraping is insufficient for temporary flight restrictions. Many stadium TFRs exist for only five hours during a game. Hazard firefighting TFRs can be issued, expanded, and cancelled within a single afternoon. By polling official FAA endpoints every 15 minutes, the capture pipeline records short-lived restrictions and amendments before they disappear.

2. Versioning and Change Detection

Every poll computes a cryptographic SHA-256 hash of the incoming TFR detail document. If a hash changes, the pipeline creates a new immutable version record (v2, v3, etc.) and computes a diff highlighting radial expansions, altitude modifications, time extensions, or cancellation notices.

3. Deterministic Classification

To guarantee reproducible and audit-safe classifications, TFR Archive uses code-based classification rules living in pipeline/classify.py. Legal basis is derived strictly from Title 14 CFR citations (91.137, 91.141, 91.143, 91.145, 99.7). Every classification records an evidence phrase and confidence score.

4. Geospatial Resolution

Center coordinates and radii are converted into closed 64-point polygons. Point-in-polygon and haversine algorithms resolve each restriction to its containing state, county, nearest city, and all affected public and private airports inside the boundary or within 10 nautical miles.

Source: FAA tfr.faa.gov and System Operations NOTAM publication. Captured: 2026-09-23 23:00 UTC. Permanent record preserved by TFR Archive under public domain principles.