The Noble, Oklahoma Jet Chase
In 27 May 2005, near Noble, Oklahoma, USA, late on the night of Friday 27 May 2005, at about 23:30, a single witness in Noble, Oklahoma, a town roughly twenty miles south of Oklahoma City, was taking what he described as his nightly walk when he saw two objects crossing a very clear sky with several miles of visibility. This case file covers what witnesses reported, the official narrative, and a two-pass assessment with its evidence tier.
What did witnesses see at Noble?
Late on the night of Friday 27 May 2005, at about 23:30, a single witness in Noble, Oklahoma, a town roughly twenty miles south of Oklahoma City, was taking what he described as his nightly walk when he saw two objects crossing a very clear sky with several miles of visibility. The first was a triangular craft moving from north to south at what he estimated as about 20,000 feet and roughly 500 knots. He stressed that it was perfectly silent.
Several miles behind it came a second object he took to be a fighter jet, moving faster, in the 600 to 700 knot range, and clearly chasing the first. As the two came toward his position he began to hear the jet's engines, the only sound in the encounter. He described the leading triangle as seeming to toy with its pursuer: as the jet closed the gap, the triangle would accelerate and pull ahead again.
When the pair passed nearly overhead, the triangular object made a sharp right-hand turn to the west. The jet could not match the angle. Its turn was much wider and more pronounced, a long loop that cost it ground. The two then ran roughly west-northwest in a straight line, the triangle again easing ahead each time the jet crept closer. After a few seconds, the witness said, the triangle accelerated dramatically and left the jet behind for good. He watched the jet make one tight loop a few miles off, then turn away to the north-northeast and pass out of sight. The whole sequence lasted about four minutes.
The detail he kept returning to was the light pattern. The triangle was marked by three lights that were not evenly spaced. Using the jet's wingspan as a yardstick, he put two of them about 50 to 75 feet apart and the third roughly 100 to 150 feet from that pair. The two closer lights were at the front and the lone trailing light faced the pursuing jet, which gave the odd impression that the craft was moving in reverse. The lights were an unusual milky white, nothing like the bright red, green and white lights he could clearly see on the jet. He closed by noting that Tinker Air Force Base, which he said has fighters, sits about 25 miles east of his house, and he insisted the account was true.
What is the official explanation?
There is no government investigation of this event. The only institutional handling it received came from the National UFO Reporting Center, the civilian hotline then run by Peter Davenport, who appended an investigator's note to the filing. NUFORC is not an official body, so this is a civilian intake record, not an Air Force or FAA finding.
Davenport wrote that NUFORC spoke with the witness by telephone on two occasions and "found him to be quite objective in his description of the alleged sighting, and very well organized in his description of what it was he apparently witnessed." He recorded that the witness would contact the FAA Air Route Traffic Control Center in Oklahoma City to ask whether the controllers on duty that Friday night might know the cause, and that he had been encouraged to ask media and law enforcement whether anyone else had seen the same thing. No such corroboration was ever published, and no FAA radar release, no control-center statement, and no Air Force comment is attached to the case.
Davenport's note also offered the one candidate explanation on record. He wrote: "We have to allow for the possibility that the object apparently being pursued by what may have been a military fighter jet may have been an F-22 'Raptor' fighter on a test flight, but even that aircraft would have to have displayed conventional red and green marker lights on its wing tips." That qualification matters, because the witness was emphatic that the lead object showed only milky white lights and no red or green markers. The source line on the filing reads "From: Skywatch International, National UFO Reporting Center, Sighting Report," which simply traces how the report was relayed into NUFORC. The promised witness illustration of the light pattern does not survive in any reachable archive.
What did the witnesses think it was?
The witness opened his report by stating, "I am a competent, educated scientist of sound mind and character. I have never reported anything like this before," and he closed it with, "I assure you that this is a true account of what I observed on the stated date and time." He did not claim the object was extraterrestrial. What he claimed was narrower and more checkable: that he watched a silent triangular craft outmaneuver and outrun a conventional jet, and that the difference in flight performance and in lighting was obvious from the ground.
His belief, in other words, was that he had seen something a fighter could not keep up with. The strength of the account is its internal consistency and the specifics a fabricator rarely bothers with: the staged turns, the jet losing ground in the wider loop, the trailing light facing the pursuer, the milky-white versus red-green color contrast, and speed and altitude figures given in knots and feet rather than vague impressions. Those are the observations of someone used to estimating aircraft performance.
The weakness is equally plain. This is a single-witness, single-source case. Despite NUFORC's request that anyone else who saw the event come forward, and despite the witness's stated intent to query the FAA center in Oklahoma City, no second observer, no controller, and no radar trace was ever produced. The corroboration the case needed to rise above one careful man's testimony simply never arrived.
Is the Noble, Oklahoma Jet Chase real? The two-pass assessment
Pass one, the ordinary reading. The most economical explanation is a real military intercept or training engagement that the witness read correctly as a chase but misjudged in its particulars. Distance and darkness wreck angular size and speed estimates, so the "50 to 75 feet" light spacing and "500 knots" are eyeball guesses, not measurements. A single aircraft seen at night can present a small cluster of lights that the brain resolves into a triangle, and a banking pursuer naturally appears to "lose ground" in a wider turn for geometric reasons alone. The witness himself named Tinker Air Force Base, and Davenport floated an F-22 on a test flight. Both have problems. Tinker's resident unit in 2005 was the 552nd Air Control Wing flying the E-3 Sentry AWACS, a four-engine command-and-control aircraft, not a fighter squadron, so a local "Tinker fighter" is not a clean fit. The F-22 idea is chronologically plausible but geographically awkward: the Raptor had finished initial operational test and evaluation in February 2005 and was approved for full-rate production in March 2005, but it would not reach initial operational capability until 15 December 2005, and its test and training were run out of Edwards, Nellis, Tyndall and Langley, not central Oklahoma. The harder snag is the witness's insistence that the lead object carried only steady milky-white lights and no red or green navigation markers, which any conventional or test aircraft in that airspace would be required to show, the exact point Davenport flagged. So the ordinary reading lands on a misperceived but real aircraft event, most likely a conventional aircraft or a pair of them whose lighting and maneuvering were misjudged, with the specific F-22 and Tinker explanations weakened by unit basing and the missing navigation lights.
Pass two, taken at face value. If the report is accurate, a silent triangular craft showing a non-standard light configuration outperformed a pursuing jet in both straight-line acceleration and turn rate, repeatedly opening distance at will. That would describe a craft operating outside the published flight envelope of the aircraft chasing it, which is the recurring signature of the black-triangle reports of that era and a genuinely anomalous performance claim.
This is a single-witness, text-only account from a credible-sounding observer, vetted only by a civilian hotline, with no radar, no second witness, no official record, and a candidate explanation that does not cleanly close. There is no method-shown debunk to weigh, and no authenticated footage or instrument data to elevate it. With no official narrative attached and the case standing entirely on one person's testimony, it sits at Unknown.
Sources
- web.archive.org/web/20250130123039/https://www.ufocasebook.com/oklahoma052705.html
- nuforc.org/subndx/?id=lOK
- news.lockheedmartin.com/2005-12-15-US-Air-Force-Declares-Initial-Operating-Capability-for-Lockheed-Martin-F-22A-Raptor-Fighter
- www.af.mil/News/Article-Display/Article/132244/langley-celebrates-raptors-initial-operational-capability/
- news.lockheedmartin.com/2004-04-30-Lockheed-Martin-F-A-22-Raptor-Begins-Initial-Operational-Test-Evaluation-Phase
- www.tinker.af.mil/About-Tinker/Fact-Sheets/Display/Article/2461278/552nd-air-control-wing/
More cases from this region: UFO sightings in United States
