How AARO resolves UAP cases: balloons, birds, sensors, and the unresolved bucket

The better question is what data survived the first pass. A UAP report can look strange in a clipped infrared video and still resolve once analysts know the sensor, platform, viewing angle, wind, altitude, location, timestamp, and likely objects in the area.

That is the pattern in AARO's public case-resolution trail. The case is not judged only by the image on screen. It is judged by the source package around the image.

This matters because a public UFO clip usually arrives stripped of the boring facts that make identification possible. AARO's public examples show that the boring facts are often the case.

Step one is intake: what was reported, who reported it, what sensor captured it, and why it entered the UAP pipeline. Flight safety, restricted airspace, unusual motion, or missing attribution can all trigger a report without proving exotic technology.

Step two is reconstruction. Analysts test the apparent motion against platform movement, line of sight, geography, wind speed, known aircraft, balloons, birds, satellites, drones, atmospheric effects, and sensor behavior.

Step three is confidence language. A case can resolve with high confidence, moderate confidence, or stay unresolved. The confidence level matters as much as the conclusion because it tells the reader how much data the conclusion is carrying.

Step four is the bucket: resolved to a prosaic object, closed as not anomalous, still undergoing analysis, unresolved pending more information, or archived because the data is too thin to support a stronger call.

The Al Taqaddum case is a clean example. AARO says an infrared sensor on an aerostat over Iraq recorded 17 minutes and 30 seconds of footage, and AARO assessed with high confidence that the object did not exhibit anomalous behavior or capabilities. The object was consistent with a cluster of fully and partially inflated balloons.

The Puerto Rico case shows why reconstruction matters. The public story often focused on speed, splitting, and entering the water. AARO says an Intelligence Community partner reconstructed the flight path and look angle, found the video showed two objects traveling near each other rather than one object splitting, and found they traveled in a straight line at wind speed without entering the water.

The Eglin case shows the limit of certainty. AARO assessed the reported object very likely was a lighter-than-air object, such as a balloon, and said the object was not exhibiting anomalous or exceptional characteristics. AARO described that assessment as moderate confidence because the available data was limited.

These examples are useful because they do not require ridicule. They show the method: rebuild the scene, compare against ordinary objects, and use confidence language that matches the evidence.

AARO's public reporting-trends page lists balloons as 510 closed-case resolution outcomes, or 52.1 percent of the closed cases shown. Satellites are second at 314 outcomes, or 32.1 percent. UAS appears as 76 outcomes, or 7.8 percent.

That does not mean every UAP is a balloon. It means the closed-case record is heavily shaped by ordinary airborne and spaceborne objects that can look strange under limited viewing conditions.

The public should read that as a baseline, not a dismissal. Before a case earns stronger language, it has to survive the ordinary buckets that already explain many closed cases.

AARO's official imagery page includes unresolved cases where AARO says the footage depicts a physical object, but the morphology, performance characteristics, and behavior are unremarkable and do not warrant further analysis unless new information becomes available.

It also includes cases where the footage is insufficient for AARO to determine the subject matter. Those are very different unresolved labels. One can mean physical object with no remarkable behavior. Another can mean not enough information to say what the video shows.

The FY2024 ODNI and DoD report adds scale to that problem. AARO received 757 reports during the covered period, determined 21 cases merited further analysis by Intelligence Community and science and technology partners, and placed 444 cases in the Active Archive because they lacked sufficient data to facilitate analysis.

That is the core rule for readers: unresolved is an evidence status. It should not be treated as proof of alien technology, and it should not be thrown away if the source trail may improve later.

First, find the original source: agency page, case report, hearing record, dataset, or raw imagery page. If the claim starts with a repost, keep it low on the ladder until the source trail is found.

Second, look for the data package: sensor type, platform, time, location, altitude, duration, weather, wind, heading, field of view, calibration, and whether original files exist.

Third, separate apparent behavior from reconstructed behavior. Fast movement across a screen is not the same as fast movement through space. Splitting on video is not the same as one object physically splitting. A reflection, sensor artifact, or line-of-sight issue can change the story.

Fourth, match the conclusion to the confidence level. A high-confidence balloon case, a moderate-confidence lighter-than-air assessment, an unresolved physical object, and an insufficient-data clip should not be described with the same words.