A newly released set of Federal Aviation Administration (FAA) records, obtained through the Freedom of Information Act (FOIA), documents an unusual aerial encounter involving a business jet over Northern Nevada in May 2025. The records include air traffic control (ATC) audio and internal FAA logs, though key data, specifically radar information, was withheld.
The FOIA request, originally submitted May 30, 2025, sought comprehensive records related to an Unidentified Anomalous Phenomenon (UAP) observed by flight PWA192 during its return trip from San Francisco International Airport (SFO) to Chicago Executive Airport (PWK). The FAA issued a partial denial response under case number FAA-2025-03957, releasing limited material while withholding others under federal exemptions.
The case first came to light through an anonymous tip submitted to The Black Vault. While anonymous sources are typically treated with caution, the details provided were corroborated through FAA documentation and audio recordings released under FOIA.
The most direct official acknowledgment appears in the FAA’s Daily Record of Facility Operation (Form 7230-4), which documents the event as it was recorded in real time by Oakland Air Route Traffic Control Center (ZOA).
At approximately 0210 UTC, the log states:
This entry establishes several key facts: the object was visually observed, it appeared aircraft-like, it maintained a parallel course, and it was not detected on radar systems available to controllers.
Audio transcripts from Oakland Center sectors provide a more detailed and dynamic description of the object as observed by the flight crew and discussed with controllers.
Initial descriptions suggested a “black circle” or object with possible wing-like features. As the encounter progressed, the characterization shifted. At one point, the object was described as resembling “some sort of fighter,” aligning with the wording later used in the FAA’s official log.
The object reportedly maintained position alongside the aircraft for an extended period of approximately 100 miles while pacing the jet at cruise altitude. This sustained proximity is notable, as it implies controlled flight behavior rather than a transient or incidental sighting.
The encounter concluded with the object rapidly ascending and disappearing from view. This abrupt vertical departure was emphasized in the communications, distinguishing the object’s behavior from conventional aircraft operating profiles.
While the FAA log provides a concise summary, the ATC audio reveals a broader range of uncertainty and evolving interpretation among those involved.
The official entry frames the object as “similar to a fighter,” whereas real-time communications included more ambiguous descriptors, including references to unusual shape and unclear configuration. The progression from an undefined “black” object to something potentially resembling a military aircraft highlights how interpretation shifted during the event.
Flight PWA192 is operated by Priester Aviation and utilizes a Gulfstream G150, a twin-engine business jet designed for mid-range operations.
The G150 typically cruises at altitudes up to 45,000 feet and speeds approaching Mach 0.85. Equipped with modern avionics and collision avoidance systems, it is representative of advanced civilian aviation platforms, making its inability to identify the nearby object—visually or electronically—noteworthy.
The FAA withheld radar data under FOIA Exemption 3, citing Sensitive Security Information (SSI).
According to the response letter, “We are withholding in full 12 En Route Automation Modernization radar files because the SSI cannot be segregated.”
The FAA further noted that certain material was withheld under 10 U.S.C. § 130e, which allows for the protection of “sensitive, but unclassified information” where disclosure could reveal vulnerabilities in Department of Defense infrastructure or operations.
However, the only visible redaction within the released Daily Record of Facility Operation appears minimal and tied to an earlier log entry unrelated to the PWA192 incident, referencing navigational aid outages and coded facility status notes. The section documenting the unidentified aircraft encounter at approximately 0210 UTC remains largely intact and unredacted, suggesting the withheld DoD-related information does not directly pertain to the unidentified object.
The log itself provides additional operational context surrounding the event. Routine oversight checks, system certifications (including ADS-B and CPDLC), and periodic pilot report (PIREP) reviews were conducted throughout the shift, with only minor weather-related entries such as turbulence and thunderstorm tops recorded. Just prior to the encounter, a PIREP check logged no significant anomalies beyond light to moderate turbulence, reinforcing that the airspace environment was otherwise stable at the time of the sighting.
The absence of radar data leaves a significant gap, particularly given the FAA log’s explicit statement that no radar targets were observed in the area.
The encounter occurred northeast of Reno, Nevada, which is an area surrounded by multiple military testing and training facilities.
Nearby installations include:
-
Naval Air Weapons Station China Lake (California)
-
Naval Air Station Fallon (Nevada)
-
Tonopah Test Range (Nevada)
-
Nellis Air Force Base and the Nevada Test and Training Range
These locations are associated with advanced aviation testing, including classified and stealth aircraft programs. Given this proximity, it remains plausible that the observed object could have been, and maybe is even most likely, a military asset operating under restricted or non-cooperative conditions.
The FAA’s records ultimately categorize the object as unidentified. While the log leans toward an aircraft-like explanation, the lack of radar correlation, the extended pacing behavior, and the rapid vertical departure leave key questions unresolved.
The event also highlights broader aviation safety considerations. Objects operating undetected in controlled airspace, regardless of their origin, present potential risks to civilian aircraft. The inability to identify or track such objects in real time underscores ongoing challenges in airspace awareness and coordination.
The released records provide a rare, document-supported glimpse into such an encounter, capturing both the uncertainty and the operational response as it unfolded.
###
Document Archive
FAA-2025-03957 Release Letter and Incident Report [7 Pages, 1MB]
Audio Archive (Unedited – Right Click, Save As)
PWA192_R43_052025_0130-0245.wav – 140MB
PWR192_R29-32_052025_0130-0245.wav – 140MB
Follow The Black Vault on Social Media:
Facts Only
A business jet, flight PWA192, operated by Priester Aviation encountered an unidentified object over Northern Nevada in May 2025.
The flight was en route from San Francisco International Airport (SFO) to Chicago Executive Airport (PWK).
The object was visually observed by the flight crew and described as a "black circle" or resembling a fighter jet.
The object maintained a parallel course alongside the aircraft for approximately 100 miles at cruise altitude.
The encounter concluded with the object rapidly ascending and disappearing from view.
The FAA documented the incident in its Daily Record of Facility Operation (Form 7230-4) at approximately 0210 UTC.
The FAA withheld radar data under FOIA Exemption 3, citing Sensitive Security Information (SSI).
The incident occurred northeast of Reno, Nevada, near multiple military testing and training facilities.
The FAA's official log categorized the object as unidentified and noted no radar targets were observed.
The released records include partial FAA logs, audio transcripts, and a response letter under case number FAA-2025-03957.
The aircraft involved was a Gulfstream G150, a twin-engine business jet with modern avionics.
The FAA's response cited 10 U.S.C. § 130e to protect sensitive but unclassified Department of Defense information.
Executive Summary
A business jet operated by Priester Aviation encountered an unidentified aerial object over Northern Nevada in May 2025. The incident, involving flight PWA192 en route from San Francisco to Chicago, was documented in FAA records and air traffic control audio obtained via FOIA. The object was visually observed by the crew, described initially as a "black circle" and later as resembling a fighter jet, and maintained a parallel course alongside the aircraft for approximately 100 miles before rapidly ascending and disappearing. No radar correlation was detected, and the FAA withheld radar data under exemptions citing sensitive security information. The encounter occurred near military testing facilities, including Naval Air Station Fallon and the Nevada Test and Training Range, raising questions about whether the object could have been a classified military asset. The FAA's official log categorized the object as unidentified, highlighting ongoing challenges in airspace awareness and safety.
The released records include partial FAA logs and audio transcripts, with key radar data redacted. The FAA's response cited federal exemptions to protect sensitive information, though the incident log itself remained largely unredacted. The event underscores the complexity of identifying and tracking unidentified objects in controlled airspace, particularly in regions adjacent to military operations. While the object's behavior—sustained pacing and rapid vertical departure—suggests controlled flight, its lack of radar signature and ambiguous visual descriptions leave its origin unresolved. The incident serves as a documented case of an aerial encounter that defies straightforward explanation, balancing between plausible military activity and unexplained phenomena.
Full Take
The strongest version of this narrative presents a well-documented aerial encounter that defies easy explanation, supported by FAA logs and audio transcripts. The source deserves credit for transparency in releasing partial records and acknowledging the limitations of the available data, including the withholding of radar information under legitimate exemptions. The incident is framed as a genuine mystery, with the object's behavior—sustained pacing and rapid vertical departure—suggesting controlled flight, yet its lack of radar signature and ambiguous visual descriptions leave its origin unresolved.
Pattern scan: The narrative avoids emotional exploitation or distortion, presenting the facts neutrally. However, the withholding of radar data under broad exemptions could be seen as a form of evasion, limiting the public's ability to fully assess the incident. The proximity to military facilities introduces a plausible explanation (classified testing) while also leaving room for speculation about unexplained phenomena. This dual framing could inadvertently create a false binary—either military or "other"—without exploring intermediate possibilities.
Root cause: The paradigm driving this narrative is the tension between transparency and national security. The unstated assumption is that the public has a right to know about aerial encounters, yet the government has a duty to protect sensitive information. This echoes historical patterns of UFO/UAP reporting, where military secrecy and public curiosity often clash.
Implications: For human agency, the incident highlights the limits of civilian oversight in airspace where military operations may occur. The costs are borne by the public, who are left with incomplete information, and by aviation safety, where unidentified objects pose potential risks. Second-order consequences include eroding trust in institutions if such encounters are frequently withheld or poorly explained.
Bridge questions: What additional data would be necessary to conclusively identify the object? How should the balance between transparency and security be managed in cases like this? What role should independent oversight play in investigating such incidents?
Counterstrike scan: If this were part of a coordinated influence campaign, the playbook might involve selectively releasing ambiguous data to fuel speculation while withholding key evidence to prevent resolution. The actual content does not match this pattern, as the FAA's response is consistent with standard procedures for protecting sensitive information. The narrative remains structurally aligned with factual reporting rather than manipulation.
Patterns detected: none