USS Roosevelt 2014-2015 Encounters
EventUSS Roosevelt 2014-2015 Encounters
EventNavy aviators from USS Theodore Roosevelt reported recurring UAP encounters in 2014-2015 training airspace off Virginia and Florida.
Navy aviators from USS Theodore Roosevelt reported recurring UAP encounters in 2014-2015 training airspace off Virginia and Florida.
The USS Roosevelt 2014-2015 encounters describe a series of reports by U.S. Navy aviators associated with the USS Theodore Roosevelt Carrier Strike Group during training workups off the U.S. East Coast. Pilots including Ryan Graves later said that unidentified objects appeared repeatedly in restricted training airspace after radar upgrades on F/A-18 Super Hornets, with some contacts also producing visual or infrared observations.
The events became a central modern UAP case because they involved professional military aviators, controlled training ranges, multiple sorties, and videos later released by the Department of Defense. The Roosevelt series is closely connected to the USS Roosevelt Gimbal and GoFast Encounters. The Gimbal and GoFast clips were recorded in January 2015 and were among the three Navy videos the Department of Defense officially released in 2020, along with FLIR1 from the 2004 Nimitz case. DOD said it released the videos to clear up misconceptions about whether they were real and that the aerial phenomena observed remained characterized as unidentified at the time of release.
That statement verified the videos as Navy material, not the more extraordinary interpretations attached to them.
The case's strongest feature is persistence in a military operating area. One odd radar hit can be a glitch; a recurring pattern reported by trained pilots forces a broader look at range safety, sensor calibration, airspace management, and reporting channels. The New York Times and later television reporting emphasized that pilots were concerned about near misses and that the Navy updated or formalized reporting procedures for unexplained aerial encounters. Those procedural changes are important because they show the issue was treated as a flight-safety and intelligence problem even before any claim about origin.
The case also has weaknesses. Public videos are short, sensor-specific, and heavily interpreted by viewers who do not have the full tactical context. Speed, distance, wind, camera mode, parallax, and aircraft motion can dramatically affect how objects look in infrared or targeting-pod footage. AARO and other analysts have since argued that some famous clips, including GoFast, can be explained by conventional motion geometry or wind-driven objects.
That does not erase the broader Roosevelt reporting stream, but it means the videos should not carry the entire case. The better question is whether the full set of reports, radar data, pilot statements, and range information still leaves a residual anomaly after careful analysis. The Roosevelt events also changed the social environment for pilot reporting. Historically, aviators often avoided UFO language because it could harm careers.
After the 2017-2020 public cycle, the Navy, Congress, and the Advanced Aerospace Threat Identification Program story helped make UAP reports a legitimate safety and intelligence topic. The Roosevelt case helped move that shift from abstract policy to operational reality.
What is documented is the existence of Navy videos, public pilot testimony, media reporting, and official release of the videos.
What is claimed is a recurring presence of unknown objects in restricted airspace during 2014-2015.
What is disputed is whether specific objects were exotic craft, drones, balloons, sensor artifacts, or conventional objects misread under complex conditions.
Probed read: Roosevelt is a high-value modern case because it combines witnesses, military context, and official video provenance. Its public video clips should be treated as fragments, not full proof of anomalous performance.
What would move the assessment: Full radar tracks, raw sensor data, range-control logs, pilot debriefs, weather/wind data, and AARO case files tied to each event would determine whether the series is a sensor-and-identification problem or something harder to explain.


