What this tests

parsing

Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.

Anatomy

A contractor synchronizing databases damaged a file, the NOTAM system — the thing that tells pilots about closed runways and hazards, so, load-bearing — refused to come up, and the FAA grounded every departing flight in the United States for the first time since a certain date in 2001. One file. All departures. The backup failed too, because backups are load-bearing in theory and decorative in practice. The specimen serves a database-ish download that truncates mid-record — the shape of "the file looks plausible until something tries to read it, at which point the aviation industry pauses". CrowdStrike proved the genre for kernels; the FAA proved it for airspace. If your pipeline ingests files without validating structure before trusting contents, this specimen is your rehearsal. The pilots will thank you. Eventually. Once they're airborne again.

Source: FAA statement on NOTAM system outage (January 11, 2023) · 2023-01-11

Replay it

curl -i https://faultydata.com/r/FD-2026-064

// response appears here

Signature

{Status:200 Headers:map[Content-Disposition:attachment; filename="notam.db" Content-Type:application/octet-stream] Body:NOTAMDB\x00\x01\x02\x03HEADER-CORRUPT-RECORD-PARTIAL Corrupt:truncate Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-028 — Malformed channel file update (CrowdStrike, Jul 2024) FD-2026-035 — Stack trace in the error body FD-2026-046 — Dependency self-sabotage (colors.js, Jan 2022) FD-2026-061 — Memory leak served in responses (Cloudbleed, Feb 2017) FD-2026-062 — Migration returns other customers' data (TSB, Apr 2018) FD-2026-077 — Digitally signed malicious update (SolarWinds SUNBURST, 2020)