The Vault Files: 2006 O’Hare International Airport UFO Sighting

Table of Contents

• Executive Summary
• The Sighting: November 7, 2006
• Eyewitness Accounts and Reactions
• Initial Response by United Airlines and FAA
• NARCAP Investigation and Findings
• Media Coverage and Public Reaction
• Proposed Explanations
• Unexplained Aspects and Significance
• Conclusion
• Sources / References

Note: The re-creation imagery used in this article to represent the 2006 O’Hare International Airport UFO incident is based on documented witness testimony, FAA audio recordings, NUFORC reports, and the NARCAP TR-10 investigation. While care was taken to remain faithful to the accounts, elements such as the object’s exact shape, altitude, and visual scale are subject to variation among observers. These visuals are intended to illustrate the events and support the narrative, not to depict exact photographic evidence. 

Executive Summary

On November 7, 2006, around 4:15 p.m. local time, a group of United Airlines employees at Chicago’s O’Hare International Airport reported seeing a mysterious unidentified flying object (UFO) hovering over Gate C17 in the United terminal[1]. The object was described as a metallic, disc-shaped craft, dark gray in color, about 6 to 24 feet in diameter, and it was completely silent[2]. After several minutes of hovering below a low cloud ceiling, the disc abruptly shot upward at high velocity, punching a crisp circular hole through the clouds before disappearing―an occurrence witnesses described as “like somebody punched a hole in the sky”[3][4]. Despite multiple credible eyewitness accounts, including airport pilots, mechanics, and managers, the Federal Aviation Administration (FAA) initially denied any knowledge of the incident and declined to investigate, later suggesting that the sighting was caused by a weather phenomenon[5][6]. To this day, the O’Hare airport UFO encounter remains unexplained, and it is often cited as one of the most notable UFO sightings of the 21st century, raising questions about aviation safety and how such incidents are handled by authorities[7][8].

The Sighting: November 7, 2006

The incident unfolded on a cloudy afternoon at one of the world’s busiest airports. At approximately 4:15 p.m. CST on November 7, 2006, a ramp employee on the tarmac at O’Hare Airport spotted an unusual object hovering above Gate C17 in Terminal 1 (the United Airlines concourse)[9][10].

This worker was in the process of directing United Flight 446, a Boeing 737 bound for Charlotte, when he looked up and saw a disc-shaped “craft” directly above the gate area[9]. He notified the departing flight’s cockpit crew about the object, and word of the sighting quickly spread through United’s ground personnel via radio. Soon, dozens of other airport employees — including pilots in nearby aircraft, airline supervisors, mechanics, and ramp workers — rushed to get a look at the phenomenon[11][12].

Witnesses observed the object hovering at an altitude they estimated to be anywhere from roughly 500 to 1,500 feet above the ground, just under the cloud layer that day[13][14]. Everyone agreed it had a distinctly defined saucer-like shape and a dull metallic gray color. No lights were visible on it, and it made no sound whatsoever[13]. Some witnesses described it as rotating like a Frisbee, while others thought it appeared stationary despite its spinning-disc appearance[13][15]. All eyewitness accounts concurred that the object was definitely not an airplane or any familiar aircraft; it lacked wings, engine noise, or standard navigation lights[16][14].

After hovering in place for several minutes above Gate C17, the UFO abruptly accelerated straight up. It shot vertically through the overcast sky at a tremendous speed, causing a peculiar visual effect: as it pierced the cloud deck (estimated at ~1,900 feet altitude that day), it left behind a clean, circular hole in the cloud cover[3][4]. Multiple witnesses saw this hole appear in the otherwise unbroken cloud ceiling. They reported that the hole lingered for a few minutes as a window of clear air before the clouds gradually drifted in to close it[4]. One United employee later vividly remarked, “It was like somebody punched a hole in the sky”, referring to the sudden opening the object created[4]. This strange hole-punch effect, coupled with the object’s sudden departure, left witnesses both astonished and uneasy.

Eyewitnesses estimate the UFO hovered for roughly 5 to 10 minutes in total before it departed[18][19]. During that period, it remained motionless just below the cloud ceiling, offering observers on the ground a clear view of its shape and color against the overcast sky[13]. The object was small relative to a commercial airliner — various accounts guessed its diameter was anywhere from around 6 feet up to 24 feet across[13][15]. (A later analysis by the National Aviation Reporting Center on Anomalous Phenomena, NARCAP, concluded the object might have been larger, on the order of 22 to 88 feet in diameter, if it was closer to the cloud altitude when seen[20].) Its abrupt vertical departure was so rapid that several witnesses admitted they had trouble visually tracking it as it streaked into the clouds[21][15].

Notably, no air traffic controllers in the O’Hare control tower saw the object during the event, and it did not register on the airport’s radar systems at the time[22][23]. The control tower was located on a different part of the airport and the controllers’ view of Gate C17’s airspace was partially obstructed by the terminal buildings, which may explain why they did not visually observe the hovering disc[24][25]. Additionally, the object was small and stationary, which could make radar detection difficult if it lacked a transponder; indeed, an FAA review of radar data found “nothing out of the ordinary” on radar returns during that period[26][23]. From the tower’s perspective, nothing unusual was officially noted during those minutes – the UFO essentially went unnoticed by on-duty controllers, even as it was being watched intently by airline personnel on the ground below.

Eyewitness Accounts and Reactions

Multiple eyewitnesses provided detailed, strikingly consistent accounts of what they saw, though most spoke only on condition of anonymity (due to fear of ridicule or admonishment from their employers)[27][28]. The first known witness was the United ramp employee (“Witness A” in NARCAP’s report) who was guiding Flight 446 at Gate C17 when he looked up and observed the disc directly above his position[29]. He described the object as a “round rotating disc” hovering at an altitude he initially estimated to be 500–1,000 feet overhead[30]. According to his report, after a couple of minutes the object “shot off” straight upward, punching through the clouds and out of sight[31]. The witness recalled seeing blue sky through the hole for a brief moment as the object departed[32]. He was adamant that what he witnessed was a solid object and not an illusion: “I know that what I saw … definitely was not an [Earth] aircraft,” the employee later told the Chicago Tribune[33][13].

Two other key witnesses were United Airlines pilots (identified as Witnesses B and C) who were in the cockpit of an empty Boeing 777 nearby. They were taxiing the aircraft from the gate area to a maintenance hangar when they heard radio chatter about the sighting and spotted the object themselves[33][14]. Both pilots opened their cockpit side windows to get an unobstructed look upward. They saw a saucer-like craft hovering above Concourse C and observed it for several minutes[34][35]. One of these pilots, a United mechanic who was taxiing the 777, later told reporters he is “scientific by nature” and was initially skeptical that a UFO would hover over a busy airport – yet he conceded that “what I saw … stood out very clearly, and it definitely was not an aircraft” of any conventional type[33][36]. This pilot’s immediate reaction was a mix of astonishment and concern; like others, he noted the object had no recognizable features of airplanes or helicopters (no wings, tail, or sound) and moved in a manner unlike anything he’d seen in his aviation career[14][4].

Several other United employees witnessed the event from various vantage points. A United supervisor in Concourse B (the adjacent terminal concourse) ran outside onto the ramp area after hearing excited radio chatter on the airline’s internal frequencies[37]. He arrived just in time to catch a glimpse of the disc before it vanished. This manager later recounted, “I stood outside in the gate area not knowing what to think, just trying to figure out what it was. I knew no one would make a false call like that.” He and others emphasized that the reports were treated seriously among the staff – if some unknown object was hovering over O’Hare, it presented a potential hazard that needed attention: “If somebody was bouncing a weather balloon or something else over O’Hare, we had to stop it because it was in very close proximity to our flight operations,” the supervisor explained of his concern[38][3]. Another employee, a United airline mechanic, was reportedly so shaken by the sighting that he “experienced some religious issues” afterward – suggesting the event challenged or deeply disturbed his personal beliefs[33][39]. Co-workers described this individual as emotionally distressed by what he had seen.

In total, by most counts, at least 10–12 United Airlines personnel witnessed the object during the brief time it was visible[1][40]. Their ranks included pilots, ground crew, baggage handlers, a cockpit crew taxiing a plane, mechanics, and managers. While there were minor discrepancies in their reports (for example, some weren’t certain if the disc was spinning or not, and estimates of its exact altitude varied), their descriptions of the object’s appearance and behavior were remarkably congruent on the critical points[41][15]. All of them asserted that something very real and very unusual had been hovering over the airport that day, and all were confident it was not a known aircraft or weather balloon[42][14]. Importantly, some independent witnesses outside the airport may have also seen the object. In the weeks after the incident, several individuals in the Chicago area (including at least one person driving near O’Hare and a passenger on an incoming flight) came forward with reports of seeing a strange disc or “oval object” in the sky near the airport on November 7 at around 4:30 p.m.[41][43]. These external sightings, logged in databases like the National UFO Reporting Center (NUFORC), corroborate the timing and general description of the object, though they are fewer in number compared to the United employee accounts[43][44].

The reactions among the United staff witnesses ranged from awe to anxiety. Several witnesses admit to being “upset” or frustrated that what they saw was not taken seriously by authorities[43][45]. One United employee could not shake an uneasy feeling after the object disappeared, worrying about the implications: “Whatever the thing was, it could have interfered with O’Hare’s radar or other equipment, or even caused a collision,” this witness later told the Tribune, emphasizing the potential safety risk that an unknown object posed in busy airspace[46][47]. In interviews, none of the airport worker witnesses jumped to the conclusion that it was an “alien spaceship” or made claims about extraterrestrial origin[48]. In fact, a number of them expressed skepticism about extraterrestrials yet remained adamant that an unidentified craft of some kind had been present. As one pilot said, “I don’t understand why aliens would hover over a busy airport, but I know what I saw … was not an Earth aircraft”[33][49]. This down-to-earth attitude lent additional credibility to their accounts in the eyes of investigators; they were experienced aviation professionals who reported the incident out of genuine concern for safety rather than sensationalism[48][42].

Initial Response by United Airlines and FAA

In the immediate aftermath of the sighting, the response from official channels was notably guarded and dismissive. When employees first began reporting the UFO over Gate C17 on the radio, the matter was relayed up the chain within United Airlines. A United operations supervisor at O’Hare (reportedly a woman named Sue, based on transcripts) phoned the FAA air traffic control tower to alert them to what was being seen.

However, the initial call to the FAA tower was met with disbelief and humor rather than action[50][51]. According to FAA recordings later obtained via the Freedom of Information Act, at about 4:30 p.m. the United supervisor asked the tower, “Hey, did you see a flying disc out by C17?”[50]. The controller on duty jokingly replied, “You guys been celebrating the holidays or what? … I haven’t seen anything, and if I did I wouldn’t admit it.”[52]. He then added, “No, I have not seen any flying disc at gate C17… unless you’ve got a new aircraft you’re bringing out that I don’t know about,” which drew laughter from both sides of the call[53][54]. In essence, the tower personnel did not take the report seriously at that moment – they treated it as a likely prank or misunderstanding.

Over the next 15–20 minutes, as the UFO sighting continued, United employees grew more insistent. The United ramp supervisor made a second call to the tower around 4:50 p.m., after the object had departed, trying to ensure the incident was at least noted. In this follow-up call (also captured on tape), she said plainly: “This is [Sue] from United… There was a disc out there flying around.”[55][56]. The controller (now a different individual) reacted with surprise: “There was a what?” – “A disc,” she repeated, “like a UFO or something”[57][58]. She emphasized to the FAA manager that “I’m not high and I’m not drinking” and that multiple personnel saw it, even mentioning “someone got a picture of it”[59][60]. The tower replied that they hadn’t seen anything on their side but would “keep an eye out,” effectively ending the conversation without further action[61]. (It is worth noting that the claim of a photograph is tantalizing – one United employee apparently snapped a picture of the object with a personal camera or phone[62]. However, no such photo has ever been publicly released or verified, and United Airlines did not provide it to investigators. The existence of a photo remains unconfirmed.)

When journalists later inquired about the incident, United Airlines officially denied having any record of its employees reporting a UFO. United spokesperson Megan McCarthy told the Chicago Tribune that there was “no record of anything” unusual that day: “There’s nothing in the duty manager log,” she said, referring to the internal log for significant events[63][64]. United management claimed they were not aware of the incident and that no formal report had been made within the company. Behind the scenes, though, it became known that United managers had, in fact, interviewed some of the witnesses soon after the event. Several employees later told NARCAP investigators that they were asked by United officials to write reports or draw sketches of what they saw, but also were instructed not to discuss the incident with others[27][65]. This suggests that United did conduct an internal inquiry of sorts – at least gathering statements – even if they chose not to publicly acknowledge it. (A NARCAP report mentions that United Airlines “allegedly began its own internal safety review” of the incident, but the findings of any such review were never made public[66].)

On the government side, the FAA initially flat-out denied any knowledge of the UFO sighting. When Chicago Tribune reporter Jon Hilkevitch first contacted the FAA in late 2006 while investigating the story, FAA spokespeople insisted they had no information or reports about any unusual object over O’Hare on November 7[67]. The FAA’s Midwest Public Affairs manager, Elizabeth Isham Cory, stated that controllers saw nothing on radar or visually, and thus “we’re not conducting any investigation”[26]. Only after the Tribune filed a Freedom of Information Act (FOIA) request did the FAA reconsider its stance. In response to the FOIA inquiry, the FAA quietly reviewed its air traffic control tapes and archives from that day[68][69]. This internal review led to a reversal: the FAA discovered the recorded phone calls from the United supervisor to the tower, confirming that the incident had indeed been reported at the time[68]. Confronted with this evidence, the FAA acknowledged that a call had occurred but continued to downplay the event.

In early January 2007, an FAA representative finally explained the agency’s official position: they concluded that no security breach or unidentified craft had been detected, and the likely explanation was a “weather phenomenon.” Specifically, the FAA and some skeptics pointed to an odd meteorological occurrence called a “hole-punch cloud” (or fallstreak hole) to explain the reports of a circular hole in the overcast that day[70][71]. The idea was that a perfectly timed passage of a small aircraft (such as a corporate jet) through the low cloud deck could have caused ice crystals to form and precipitate, opening a round hole in the clouds that witnesses mistook for a craft punching through. “That night was a perfect atmospheric condition in terms of low cloud ceiling and a lot of airport lights,” the FAA’s Cory told the Tribune, suggesting that perhaps the employees saw an optical illusion of lights on the clouds[72]. According to her, “When the lights shine up into the clouds, sometimes you can see funny things. That’s our take on it.”[72] In short, the FAA decided not to investigate further, considering the case closed with a meteorological explanation and noting that nothing showed up on radar to warrant concern[26][5]. This quick dismissal angered many of the witnesses. Some of the United employees were reportedly “upset” that federal officials declined to further investigate the matter, feeling that their sighting was being written off without a proper inquiry[43].

In summary, neither United Airlines nor the FAA pursued a formal investigation in the immediate wake of the sighting. United’s public stance was effectively “we have no information”, and the FAA’s stance was “it was likely weather and we’re not worried about it.” However, this lack of official curiosity was later criticized by aviation and UFO investigators, especially given the location of the incident. As Chicago’s O’Hare is a high-security, high-traffic airport, the notion that an unauthorized object hovered over a gate area and then vanished—without triggering any security response—was troubling to many. One commentator, Mark Rodeghier (scientific director of the Center for UFO Studies in Chicago), pointed out the post-9/11 security implications: “It’s an unknown object over O’Hare, seen by official personnel, and does United or the FAA take it seriously? Of course not… But how can you not worry about something hovering over an airport after 9/11? It doesn’t make sense.”[73][74]. Critics argue that regardless of one’s beliefs about UFOs, an incursion into controlled airspace above an airport should be treated as a potential safety or security issue, not laughed off.

NARCAP Investigation and Findings

While official agencies chose not to investigate further, the case was actively examined by a civilian aviation-safety organization: the National Aviation Reporting Center on Anomalous Phenomena (NARCAP). NARCAP is a private research group composed of scientists and former aviation professionals that studies aviation-related UAP (Unidentified Aerial Phenomena) sightings. Dr. Richard Haines, a former NASA research scientist and NARCAP’s chief scientist, led a detailed investigation into the O’Hare incident soon after it became public. In March 2007, NARCAP published a 155-page technical report on the case (Technical Report #10) titled “Report of an Unidentified Aerial Phenomenon and its Safety Implications at O’Hare International Airport on November 7, 2006.”[75].

Loading...

Taking too long?

Reload document

| Open in new tab

This report compiled witness testimonies, analyzed radar data, and considered possible explanations, all with an eye toward aviation safety.

Key findings from the NARCAP investigation include:

• No Radar Confirmation: NARCAP obtained FAA radar data via FOIA to double-check for any unexplained targets. As the FAA had stated, no obvious radar returns coinciding with the time and location of the sighting were found[23]. This suggests the object either was too small or low to be picked up by airport surveillance radar, or it had some radar-evasive properties. (NARCAP analysts noted that a small, stationary or slow-moving object could potentially be filtered out by radar settings, and O’Hare’s radar might have blind-spots in the immediate vicinity overhead due to radar angle and “ground clutter” filtering[7][76].)
• Duration and Flight Path: Based on witness timelines, the object was present for an estimated ≈5 to 7 minutes of hovering (from roughly 4:30 to 4:35 p.m.) before its sudden departure[18][77]. When it left, it traveled straight up through the cloud layer at high speed. No horizontal movement was reported – it essentially vanished into the sky. The report highlighted that “anytime an airborne object can hover for several minutes over a busy airport but not be registered on radar or seen from the control tower, it constitutes a potential threat to flight safety.”[78][79] NARCAP stressed that this incident revealed a gap in detection: an object was essentially invisible to both radar and tower observers, yet clearly present to those on the ground.
• Cloud Hole Analysis: NARCAP gave particular attention to the “hole-in-cloud” (HIC) phenomenon reported. Investigators analyzed weather data and the dimensions of the hole. Witnesses said the hole was sharply defined, roughly the same diameter as the object, and lasted for as long as 10–15 minutes before closing[20][80]. This is unusually long-lived for a hypothesized “fallstreak hole” caused by an airplane; such holes typically remain for only a few minutes[4][80]. The report posits that if the object itself created the hole (by physically passing through the cloud or by emitting heat), it would likely have had to be extremely hot or release significant energy. Calculations suggested that on the order of 9.4 kilojoules per cubic meter of energy would be needed to evaporate the cloud moisture and leave a hole of that size[80][81]. This could indicate a “super-heated object” or perhaps one emitting a strong thermal or microwave energy field causing localized heating[80]. Such an energetic output is inconsistent with any small drone or conventional aircraft, lending weight to the idea that the cause was truly anomalous. NARCAP also noted that the hole was approximately circular and of similar diameter to the reported craft, implying the object either physically punched through or induced the aperture equal to its own size[20].
• Witness Credibility and Consistency: The NARCAP team interviewed several of the United employee witnesses confidentially. They found the witnesses to be credible and their accounts consistent on major points[82][83]. The report took steps to protect the anonymity of the employees (referring to them as Witness A, B, C, etc.) since some feared reprisals or ridicule. Notably, NARCAP addressed an Internet rumor that had circulated: an alleged witness using the alias “rampagentX” had posted a sensational story about the O’Hare UFO on a forum, but NARCAP determined this account was a likely hoax and “spurious”, not matching any known legitimate witness[84]. By comparing details, they concluded that “it is very unlikely that witness A is ‘rampagentX’” from the forum, debunking that piece of misinformation[85]. All real witnesses interviewed maintained that the event indeed happened as described and that they had nothing to gain from reporting it except improving safety[83][48].
• Historical Context: In its analysis, NARCAP pointed out that while multiple-witness daytime UFO sightings at major airports are unusual, they are not entirely unprecedented[86][87]. The report briefly cites other cases where pilots or airport personnel reported similar disc-like objects and even holes in clouds. (For example, there have been past pilot reports of disc-shaped UAP leaving cloud openings or affecting clouds, though such reports are rare.) This context was provided to show that the O’Hare incident, while extraordinary, fits a pattern of aviation-related UAP events that have been historically underreported or brushed aside. NARCAP’s broader research indicates a systemic “under-reporting bias” in aviation, where pilots and crews often choose not to report unusual aerial phenomena due to fear for their careers or ridicule[88][89]. The O’Hare case was offered as a prime example of this: numerous credible professionals saw something, yet official channels initially suppressed or ignored the reports, and only through media coverage did it come to light.
• Safety and Recommendations: The crux of NARCAP’s concern was safety. Dr. Haines stated, “We must be proactive before an aircraft goes down.”[90][91] He and his co-authors argued that UAP pose a potential aviation hazard if they can appear in busy airspace unannounced. In the O’Hare report, NARCAP concluded that an official government inquiry should be carried out to assess whether current radar and sensor systems are adequate to detect these kinds of objects, and to ensure procedures are in place to handle such an incident in the future[92][79]. They noted the apparent inability of O’Hare’s radar and tower personnel to detect the hovering object, labeling it a “potentially significant air safety problem”[78]. Among the recommendations were improving the collection of UAP reports within the aviation community and reducing stigma so that pilots or air traffic controllers can report unusual sightings without fear of ridicule or career harm[93][89]. (Earlier, in 2004, NARCAP had produced a separate report on the “under-reporting bias” of UAP in aviation and urged the FAA to establish better reporting mechanisms[75][94]. The O’Hare case gave new urgency to those recommendations.)

Overall, NARCAP’s investigation treated the O’Hare UFO sighting as a serious aviation safety incident involving an unidentified aerial object. The report stopped short of speculating on the object’s origin – it did not claim this was an “alien spacecraft” – but it emphatically documented the reality of the sighting and the fact that it “remains unidentified.” The NARCAP team was critical of the FAA’s quick dismissal. In a later statement, a NARCAP researcher remarked that the FAA’s refusal to investigate seemed at odds with its mandate: “If an object hovered over a major airport, witnessed by numerous employees and officially reported, how can it not warrant investigation? The safety implications alone should compel it.”[95]. By compiling data on this case, NARCAP hoped to encourage a change in attitude within the aviation industry about UAP reports.

It’s worth noting that NARCAP’s Technical Report 10 on the O’Hare incident was archived and made available publicly (via the NARCAP website and later the Internet Archive) so that other researchers and the public could review the evidence[75]. The thoroughness of this report has been praised by UFO researchers; even some skeptics acknowledge that the witnesses clearly saw something unusual. Critics of the NARCAP report, however, argue that it perhaps too readily dismissed the hole-punch cloud explanation. They suggest that an aircraft-induced fallstreak hole could linger longer under certain conditions and that witnesses might have perceived a structure (the supposed disc) where there was none, due to pareidolia or miscommunication. NARCAP’s team addressed this by pointing out the multiple independent and overlapping descriptions of a structured object, and the low likelihood that so many seasoned aviation observers would all identically hallucinate a metallic disc for several minutes View original source →