The O'Hare Airport Sighting
On November 7, 2006, around a dozen United Airlines employees at Chicago O'Hare — ramp workers, mechanics, pilots — watched a silent dark disc hover below the clouds over Gate C17, then shoot straight up and reportedly punch a hole in the overcast. The FAA logged no radar return and declined to investigate, calling it a weather phenomenon. The independent group NARCAP later published a 128-page study. No photo was ever produced.

Our read
Evidence — 10 claims
7 supported · 2 contested · 1 open
Sources — 4
4 sources · academic + journalism + court / archive
Contested
Competing readings of the record remain live.
- SupportedAround a dozen United Airlines employees — ramp workers, mechanics, and pilots — witnessed a silent dark disc hovering over Gate C17 on November 7, 2006.
- SupportedThe object was described as a dark, metallic-looking disc, hovering silently below a 1,900-foot overcast, with no sound or navigation lights.
- SupportedMultiple witnesses reported the object shot straight up and punched a hole through the cloud layer on departure.
- SupportedThe FAA logged no radar return for the object and declined to open a formal investigation, attributing reports to a weather phenomenon.
- SupportedThe incident became public only after Jon Hilkevitch filed a FOIA request for FAA ATC audio; United Airlines initially denied the incident.
- SupportedNARCAP Technical Report 10 (May 2007) concluded a physical object was likely present and flagged the radar non-detection as an aviation safety concern.
- ContestedAstronomer Mark Hammergren suggested the cloud hole was consistent with a fallstreak hole, a known meteorological phenomenon.
- ContestedNARCAP investigators argued the fallstreak-hole hypothesis does not fully account for a discrete hovering object that then accelerated upward.
- SupportedNo usable photograph or video of the object was ever produced.
- OpenNo official aviation authority has formally addressed or responded to the NARCAP Technical Report 10 findings.
What remains unexplained
No investigation was ever opened, no photo exists, and the FAA's weather-phenomenon attribution remains unspecified. The radar gap at one of the world's busiest airports — for an object observed by a dozen aviation professionals in daylight — is formally unresolved.
- 01What specific weather phenomenon the FAA believed caused the reports has never been named or documented.
- 02The radar non-detection mechanism — whether the object was radar-absorbent, small, or something else — has not been explained.
- 03No aviation authority has formally responded to NARCAP's aviation-safety findings in the 17 years since TR-10 was published.
Gate C17, Chicago O'Hare International Airport. November 7, 2006, mid-afternoon. A dark, silent disc hovered below the cloud deck for several minutes, then shot straight up and — according to multiple witnesses — punched a clean hole through the overcast on its way out.
The witnesses were not random passersby. They were United Airlines ramp workers, mechanics, and pilots. Around a dozen of them, standing on the tarmac, watching the same object over the same gate. None of them had a camera that produced a usable image. All of them, by later accounts, were shaken enough to file reports with their employer.
What happened
The sighting lasted roughly five minutes, somewhere between 4:15 and 4:30 PM local time. The object was described as a dark, metallic-looking disc, perhaps 6 to 24 feet in diameter depending on the witness, hovering silently below a 1,900-foot overcast. No sound. No navigation lights. No movement until it moved — and when it did, it went straight up at speed.
The cloud hole it allegedly left behind was real enough that multiple witnesses independently described it. Whether the hole was caused by the object's departure or was a pre-existing atmospheric feature is one of the things nobody resolved.
United Airlines initially denied the incident. The story broke publicly only after journalist Jon Hilkevitch filed a Freedom of Information Act request for FAA air traffic control audio — a request that cost him $14.95 — and the Chicago Tribune published his report on January 1, 2007. The story became one of the most-read pieces the Tribune ran that year.
The evidence
The FAA logged no radar return for the object. Air traffic controllers in the tower reported no visual observation. The agency declined to open a formal investigation, attributing the reports to a weather phenomenon — specifically without elaborating on what weather phenomenon would hover silently over a specific gate for five minutes and then accelerate upward.
The FAA FOIA documents archived by The Black Vault include the ATC audio that Hilkevitch's request surfaced. The audio confirms that the event was discussed by airport personnel in real time. The FAA's position — no radar, no investigation — remained unchanged after the documents became public.
In May 2007, NARCAP (the National Aviation Reporting Center on Anomalous Phenomena) published Technical Report 10, a 128-page analysis by Richard Haines and colleagues. NARCAP's conclusion: a physical object was likely present, the radar non-detection was itself anomalous and worth investigating as an aviation safety issue, and the case warranted formal inquiry. NARCAP is careful not to claim the object's ultimate nature — their lane is aviation safety, not identification — but the report is detailed, methodical, and not dismissive.
Mark Hammergren, an astronomer at the Adler Planetarium, offered a prosaic read: the cloud hole was consistent with a fallstreak hole, a known meteorological phenomenon sometimes called a hole-punch cloud. That's a reasonable atmospheric explanation for the hole. It doesn't account for the hovering disc that witnesses watched for several minutes before the hole appeared.
What the explanations don't explain
The FAA's weather-phenomenon attribution explains nothing specific. No one named the phenomenon. No one explained how a weather event hovers stationary over a single airport gate.
The fallstreak-hole hypothesis addresses one detail — the cloud hole — and leaves the rest of the witness accounts untouched. A fallstreak hole is caused by ice crystals falling from a cloud layer, not by a discrete object ascending through one.
The radar gap is the detail NARCAP found most significant. O'Hare is one of the busiest airports in the world. Its radar coverage is not casual. An object large enough for a dozen trained aviation workers to observe for several minutes, at close range, in daylight, returning no radar signature is either a very unusual object or a very unusual failure of detection. The NARCAP report flags this as an open question with direct implications for airspace safety.
What's still open
No photograph was ever produced. No official investigation was ever opened. The FAA's position has not changed. NARCAP's report sits in the public record, formally unaddressed by any aviation authority. The witnesses — trained aviation professionals, at one of the world's busiest airports, in the middle of the afternoon — described something none of the available explanations fully accounts for. That's where the record ends.
Who witnessed the O'Hare UFO sighting in 2006?
Around a dozen United Airlines employees witnessed the event, including ramp workers, mechanics, and pilots stationed near Gate C17. They were trained aviation professionals observing the object in daylight at close range, which is part of why the case drew serious attention from aviation safety researchers.
Did the FAA investigate the O'Hare UFO sighting?
No. The FAA logged no radar return for the object and declined to open a formal investigation, attributing the reports to a weather phenomenon without specifying one. The incident only became public after journalist Jon Hilkevitch obtained FAA air traffic control audio through a FOIA request.
What did the NARCAP report conclude about the O'Hare sighting?
NARCAP's 128-page Technical Report 10, published in May 2007, concluded that a physical object was likely present and that the radar non-detection was anomalous enough to warrant formal investigation as an aviation safety concern. The report stopped short of identifying the object's nature — NARCAP's focus is aviation safety, not UAP identification.
Was the cloud hole at O'Hare explained?
Astronomer Mark Hammergren suggested the hole in the overcast was consistent with a fallstreak hole, a known meteorological phenomenon caused by ice crystals falling from a cloud layer. NARCAP's investigators noted that this explanation addresses the cloud hole but does not account for witnesses observing a discrete hovering object before the hole appeared.
Was there any photo or video evidence from the O'Hare sighting?
No usable photograph or video was ever produced from the incident, despite the presence of multiple witnesses on an active airport tarmac. The absence of visual documentation is one of the case's significant limitations, alongside the FAA's lack of a radar return.
How did the O'Hare UFO story become public?
Chicago Tribune reporter Jon Hilkevitch filed a Freedom of Information Act request for FAA air traffic control audio related to the incident — a request that cost him $14.95. His report, published January 1, 2007, became one of the Tribune's most-read pieces that year and forced United Airlines to acknowledge the event after initially denying it.
UAP
USS Nimitz Encounter
Over two weeks in November 2004, U.S. Navy radar tracked an unidentified object off the California coast that maneuvered in ways no known aircraft could match. The pilot who saw it up close has been on the record ever since.
2004-11
UAP
Phoenix Lights
On the evening of March 13, 1997, thousands of witnesses across Arizona — including Senator John McCain and Governor Fife Symington — reported a massive silent V-shaped craft passing slowly over Phoenix, followed several hours later by a row of stationary lights over the same metro area. The Air Force attributed the row of lights to A-10 flares; the triangular craft was never officially explained.
1997-03-13
UAP
The Stephenville Sightings
In January 2008, dozens of residents around Stephenville, Texas — including a pilot and a constable — reported a huge, silent, fast-moving object with brilliant lights, some claiming jets gave chase. The Air Force first denied any aircraft were present, then confirmed ten F-16s were training nearby. A MUFON analysis of FAA radar reported an unidentified non-transponder track, while skeptics attribute the whole episode to jets and high-intensity flares.
2008-01-08
Federal Aviation Administration (FAA)
2006-2007
Not investigated — attributed to a weather phenomenon
No radar return, no air traffic controller observations; the agency declined a formal inquiry. The story surfaced only after a FOIA request for ATC audio.
NARCAP (National Aviation Reporting Center on Anomalous Phenomena)
2007-05-14
Unidentified aerial phenomenon; a physical object was likely present; flagged as an aviation-safety concern
128-page Technical Report 10. The authors focus on aviation safety and a radar-detection gap, not on claiming the object's ultimate nature.
Mark Hammergren, astronomer (Adler Planetarium)
2007
Prosaic explanation offered — consistent with a 'hole-punch cloud' (fallstreak hole)
A meteorological reading addressing the cloud-hole detail; NARCAP's investigators argued it does not fully account for a discrete hovering object that then accelerated upward.
- NARCAP Technical Report 10 — Report of an Unidentified Aerial Phenomenon at O'Hare International Airport, Nov 7 2006 (Haines et al., May 2007)Quoted or summarized under fair use — follow the link for the originalaccessed 2026-05-21
- Jon Hilkevitch — In the sky! A bird? A plane? A … UFO? (Chicago Tribune, January 1, 2007)Quoted or summarized under fair use — follow the link for the originalaccessed 2026-05-21
- The Black Vault — Case Files: 2006 O'Hare International Airport UFO Sighting (FAA FOIA document archive)Quoted or summarized under fair use — follow the link for the originalaccessed 2026-05-21
- 2006 O'Hare International Airport UFO sighting — WikipediaCreative Commons — reuse allowed with attribution, share-alikeaccessed 2026-05-21
This account draws on publicly available sources and historical records. Report a factual error → How we source and correct →