The Joe Rogan ExperienceJoe Rogan Experience #1361 - Cmdr. David Fravor & Jeremy Corbell
CHAPTERS
- 0:02 – 2:33
Cmdr. David Fravor’s background and why this case matters
Joe introduces Cmdr. David Fravor and Jeremy Corbell, emphasizing why trained military eyewitnesses carry weight in UFO/UAP discussions. Fravor outlines his Naval aviation career, Top Gun experience, and command role during the event.
- •Fravor’s 24-year military career and flight qualifications
- •Joe’s shifting stance: believer → skeptic → open-minded → more convinced
- •Why high-level pilot testimony is treated differently than civilian reports
- •Setting expectations for a corroborated, evidence-linked incident
- 2:33 – 4:57
Nimitz workups and the USS Princeton’s unexplained radar tracks (two-week lead-up)
Fravor sets the operational scene: a carrier strike group training off Southern California in November 2004. He explains that the USS Princeton had been tracking multiple unknown objects for about two weeks, descending from extremely high altitude and lingering for hours—without the air wing being briefed.
- •Date/location: Nov 14, 2004, off San Diego/Ensenada corridor
- •Carrier workups: air defense exercise structure (blue vs red forces)
- •Princeton/Aegis SPY-1 and other sensors tracking ~dozen objects
- •Objects reportedly descend from >80,000 ft to ~20,000 ft, loiter, then ascend
- •Frustration: pilots weren’t informed prior to launch
- 4:57 – 8:29
Real-world vector: training canceled and Fravor’s unarmed intercept
The exercise is abruptly canceled as Princeton vectors Fravor’s section to investigate a ‘real-world’ unknown contact. Fravor explains why their jets were not carrying live weapons and describes the intercept geometry as they’re guided toward the target area.
- •Training mission abruptly becomes a real-world intercept
- •Jets are effectively unarmed (training CATM-9) and why that’s standard
- •Controller calls range/bearing/altitude until ‘merge plot’
- •Wingman stays high for overhead view while Fravor descends to investigate
- •Initial assumption: possible drug-runner or conventional contact
- 8:29 – 11:00
Visual contact: the ‘white water’ disturbance and the Tic Tac’s erratic motion
Fravor describes seeing an unusual patch of ‘white water’ in calm ocean conditions and then spotting the white, Tic Tac-shaped object above the surface. The craft moves sharply in multiple directions without visible rotors, wings, or exhaust—behaving unlike any known aircraft.
- •Ocean surface anomaly: disturbance roughly ‘737-sized’ and cross-like
- •First visual identification of the Tic Tac object near the disturbance
- •Estimated size ~40 feet (Hornet fuselage-sized)
- •No rotor wash, rotors, wings, tail surfaces, or obvious propulsion
- •Rapid, at-will lateral movements (forward/back/left/right)
- 11:00 – 12:34
Close-in engagement: mirrored motion, cut-across, and instant disappearance
As Fravor descends and maneuvers to close distance, the Tic Tac appears to ‘mirror’ his movement, suggesting awareness. When he attempts to cut across the circle to intercept, the object accelerates and vanishes abruptly—confirmed by the other jet observing from above.
- •Fravor’s controlled descent over featureless ocean for safety
- •Object rotates orientation and climbs as he descends (mirroring behavior)
- •Fravor ‘cuts across the circle’ to get closer and join on it
- •Object accelerates and disappears in under a second (‘poof’)
- •Both aircrews confirm loss of visual contact from different angles
- 12:34 – 14:04
Return to the disturbance and the ‘cap point’ jump on radar
After losing the object, Fravor returns to the original ocean disturbance only to find it gone and the sea calm. Princeton then reports the object has reappeared at Fravor’s cap point—tens of miles away—implying extreme speed or unconventional movement.
- •The white-water disturbance disappears entirely on return
- •Princeton reports the object ‘back at your cap point’ (~60 miles away)
- •Contact appears on radar without a tracked transit path
- •Fravor’s section makes additional runs but can’t reacquire visually/sensors
- •They return to the ship and land
- 14:04 – 24:06
The FLIR video is captured: radar jamming and the origin of the ‘Tic Tac’ clip
A later sortie equipped with a targeting pod locates the object and records the famous FLIR footage. Fravor explains that the radar indicates jamming and that the crew uses passive tracking via the pod to capture the video that later becomes public.
- •A different crew launches with a targeting pod and hunts for the contact
- •Radar lock attempts show signs of jamming (and why that’s serious)
- •Switch to passive FLIR track to maintain a lock without active radar ranging
- •This is the publicly released ‘Tic Tac’ video (short, not a long clip)
- •How multi-sensor cueing works (radar designation drives other sensors)
- 24:06 – 34:20
On-screen breakdown of the Tic Tac FLIR: IR/TV modes, no plume, and ‘99.9’ ranging issue
With the video up, Fravor walks through the symbology: narrow FOV, IR vs TV modes, altitude/heading holds, and track gates. He highlights the absence of exhaust plume and explains that ‘99.9’ indicates the radar can’t range the target, consistent with active countermeasures or unusual signature behavior.
- •Interpreting FLIR symbology: NAR, IR/TV, hot/white polarity
- •Object appears hotter than background but shows no exhaust plume
- •Autopilot/altitude hold context (stable platform)
- •‘99.9’ indicates inability to get radar ranging/returns
- •Object departs field of view rapidly at the end of the clip
- 34:20 – 54:38
East Coast UAP wave: Go Fast, Gimbal, ‘fleet’ contacts, and near-miss hazards
Fravor connects his 2004 case to later Navy encounters off the East Coast (2015 era), including Go Fast and Gimbal. He discusses reports of numerous radar contacts, near-collisions, and the issuance of NOTAMs warning aviators—framing UAP as an operational safety and security issue.
- •Go Fast vs Gimbal: different videos, same general sensor suite
- •Reports of many objects (‘fleet’) visible on SA page/radar while pod tracks one
- •Near-miss incident and ‘cube in a clear sphere’ descriptions
- •NOTAMs issued to reduce collision risk
- •Debates over speed/interpretation and why aircrews reject simplistic debunks
- 54:38 – 1:05:45
Underwater connections and ‘transmedium’ speculation (plus a helo pilot’s torpedo story)
The conversation expands into whether UAP operate in water as well as air/space, prompted by Fravor’s initial ocean disturbance. Fravor shares a separate account from a helicopter pilot who described large underwater objects and a torpedo recovery that appeared to be ‘pulled’ back down into the depths.
- •Speculation: if propulsion isn’t aerodynamic, water-to-air travel may be feasible
- •Fravor’s ‘something under the water’ intuition tied to the disturbance
- •Helicopter pilot story: dark mass rising from depth during recovery operations
- •Second incident: torpedo allegedly ‘sucked’ underwater; object descends again
- •Why such reports are hard to formally report or validate
- 1:05:45 – 1:17:11
Credibility, hoaxes, and historical narratives: separating signal from noise
They discuss how hoaxes and embellishments muddy the subject, and why Fravor insists on sticking to what was actually observed. They touch on historical accounts (Columbus, religious mass sightings like Fatima) and ‘UFOs in art,’ while emphasizing modern corroboration via sensors and trained witnesses.
- •Fravor rejects embellished claims (e.g., ‘10-minute’ Tic Tac video rumors)
- •Why ridicule and bad-faith stories damage serious investigation
- •Discussion of historical claims (Columbus) and limits of such evidence
- •UFO imagery in paintings and interpretive ambiguity (angels vs tech)
- •Fravor’s own prank story: creating ‘UFO reports’ with afterburner fly-bys
- 1:17:11 – 1:30:46
Government response: briefings, AATIP/FOIA limits, funding, and oversight needs
Fravor explains how the event was debriefed in the Navy and later became part of serious government interest after the 2017 reporting. He describes closed-door conversations with senior officials, argues the funding level is modest relative to defense budgets, and stresses oversight and inter-agency collaboration to avoid siloed efforts.
- •Debrief process: tapes to the Carrier Intel Center; ship-wide rumor mill
- •FOIA confusion and how AATIP-related work can be FOIA-exempt
- •Post-2017: Fravor talks to multiple government groups; high interest
- •Budget framing: millions/year vs overall defense spend; why more study is feasible
- •Need for centralized oversight and cross-agency coordination
- 1:30:46 – 1:49:40
What it could mean: technology leaps, reverse-engineering claims, and material science limits
They explore implications of non-reactionary/field propulsion and whether such capability could be human or non-human. Corbell raises reverse-engineering narratives and ‘meta-materials,’ while Fravor stays cautious—arguing the observed performance would be civilization-changing if it were a hidden domestic program.
- •Fravor’s argument: if a government had it in 2004, it should have surfaced by now
- •Corbell’s claims: understanding gravity propulsion conceptually; materials as bottleneck
- •Discussion of Jacques Vallée’s samples and layered/engineered materials
- •Bob Lazar connections: propulsion ideas, Element 115, and ‘100 years’ estimate
- •Broader point: such tech would transform travel, energy, and geopolitics
- 1:49:40 – 1:54:25
Wrap-up and ‘Storm Area 51’ detour: public curiosity vs productive inquiry
They close by reflecting on how public interest has surged, including the ‘Storm Area 51’ phenomenon, which Corbell reframes as a largely peaceful gathering rather than an actual raid. Joe emphasizes the value of credible witnesses and thanks Fravor and Corbell for the conversation.
- •Corbell’s recap: ‘Storm Area 51’ and media narrative vs on-the-ground reality
- •Fravor dismisses ‘storming’ as reckless; focus should be on serious inquiry
- •Joe reiterates credibility as the central reason the story resonates
- •Final thanks and sign-off
