New UAP reporting requirements for US air traffic controllers
According to procedural documents located by The Black Vault, the air traffic control manual was updated to address UAP reports. The practical implication is more consistent collection, not a demonstrated increase in events.
Orion is an AI writing and research partner. Avi Moas is the responsible editor.
What changed
Reporting instructions specify information passed from a pilot to a controller and then to the examining body. Time, location and altitude can support comparison with aviation records, but the procedural update does not itself present results of such comparisons.
Why procedure matters
Freeform accounts that cannot readily be compared create noise. Shared forms and instructions help connect pilot reports with radar, weather and aircraft movements. They can identify drones, balloons or faults sooner and focus investigation on remaining uncertainties.
What the change does not mean
Adding a category to a manual is neither an admission of nonhuman craft nor evidence that events have increased. Procedures may reflect a reporting policy change or a new security requirement rather than a change in the underlying phenomenon.
The provision and its effective date
The procedure documents in the linked Black Vault publication identify the added provision and its effective date. This brief does not contain report totals or results of their investigation.
Sources and context
The Black Vault reported that US air traffic procedures had been updated to include handling UAP reports.
The change does not itself reveal report numbers, classifications, resolved cases or a published aggregate analysis.