The O'Hare UFO Sighting: A Disc Above Gate C-17, and a Hole in the Clouds.

What happened, in a paragraph.

On the afternoon of November 7, 2006, between approximately 4:15 and 4:20 PM Central Standard Time, multiple United Airlines ground-staff personnel at Chicago O'Hare International Airport reported observing a dark gray, metallic, disc-shaped object hovering approximately 1,500 feet above Concourse C in the vicinity of Gate C-17. The object was reportedly visible for several minutes — estimates of duration vary from witness to witness in the range of two to five minutes — before accelerating vertically through the cloud cover (a low overcast deck reported as approximately 1,900 feet above ground level at the time) and leaving a clean, circular hole in the cloud layer that remained visible for some minutes afterward. The principal eyewitnesses were approximately twelve ground-services employees, including a ramp worker who first noticed the object while pushing back another aircraft, a tug driver, several mechanics, and at least one ramp supervisor. The cockpit crew of United Airlines Flight 446, a Boeing 737 at Gate C-17 at the time, reported observing the object from the flight deck. A United supervisor radioed the United operations center, which radioed the O'Hare air traffic control tower with the report. No tower controller is known to have observed the object visually, and no radar return on the FAA's primary or secondary surveillance radars was subsequently confirmed for the event. The incident drew no immediate public attention; the airline's initial position when contacted by journalists was that no incident had occurred. The story broke publicly with Jon Hilkevitch's Chicago Tribune front-page article of January 1, 2007, which had been preceded by Hilkevitch's FOIA-supported reporting on the FAA's internal logs. The FAA, in response to Hilkevitch's inquiries, confirmed that the United radio call had been made and logged, and that the call had referenced a UFO observed above Gate C-17; the FAA's substantive position on the event, articulated by Administrator Marion Blakey, was that the observation was best explained as a weather phenomenon, specifically a "hole-punch cloud" or fallstreak hole. The witnesses, in subsequent interviews including those collected by the civilian National Aviation Reporting Center on Anomalous Phenomena (NARCAP) and the Mutual UFO Network (MUFON, Case File 35083), have not accepted that explanation. The incident remains one of the most-publicized commercial-aviation UFO reports of the modern era.

The documented record.

The radio call and the FAA log

At approximately 4:30 PM CST on November 7, 2006, a United Airlines operations supervisor at O'Hare contacted the O'Hare air traffic control tower by ground line to report that ramp employees and a 737 cockpit crew had observed an unidentified disc-shaped object over Concourse C. Verified The radio/telephone call was logged in the FAA's internal operational records [1]. The FAA's initial response to public inquiries, in the immediate aftermath and through December 2006, was that no record of any such call existed. This position was reversed in early January 2007 after Hilkevitch's FOIA requests forced disclosure of the internal log [2]. The reversal — from "no record" to "yes, the call was logged" — is documented in the FAA's own communications and is one of the elements of the case that has remained durable in subsequent retellings.

The witnesses

Approximately twelve United Airlines ramp-side personnel reported direct visual observation of the object. Verified Most chose to speak to investigators (Hilkevitch, NARCAP, MUFON) on condition that their identities not be published, citing concerns about their continued employment with the airline; the airline's initial denial of the incident and its discouragement of further employee discussion are part of the documented record [3]. The witnesses who did speak on the record, primarily to NARCAP investigator Richard Haines (a former NASA Ames Research Center senior scientist and aviation human-factors specialist) and to MUFON's Sam Maranto, described the object consistently in its broad outlines: dark gray, disc-shaped, with sharp edges, no visible lights, no exhaust plume, no audible sound, hovering steadily at an estimated 1,500 feet for several minutes, then accelerating vertically into and through the overcast.

The cockpit crew of UAL 446 — a Boeing 737 at Gate C-17 at the time of the incident — reportedly observed the object from the flight deck. The pilot's identity and the cockpit crew's individual statements have not been released publicly; the airline did not authorize them to speak with investigators, and they did not come forward independently [3][4].

The cloud-hole observation

Multiple ground-staff witnesses reported that as the object accelerated upward through the overcast, it left a roughly circular hole in the cloud layer through which clear sky was briefly visible. Verified The cloud-hole observation is one of the most-cited specific elements of the case and is the element that most directly motivated the FAA's "hole-punch cloud" framing. The hole reportedly persisted for several minutes before closing. Photographs of the hole were not produced; the witnesses had been at work at the time and did not have cameras at hand, and the airport's surveillance camera coverage at the time did not include skyward-facing imagery of the relevant area at the relevant resolution [3].

The Hilkevitch Chicago Tribune article

On Verified January 1, 2007, Chicago Tribune transportation reporter Jon Hilkevitch published a front-page article, "In the Sky! A Bird? A Plane? A … UFO?", reporting the incident based on FOIA-produced FAA logs and interviews with United employees [2]. The story was carried on the wires nationally and internationally over the following days and prompted the FAA's substantive public response. Hilkevitch's reporting was the first time the event reached general public attention; for almost two months between the incident and the article, the case was known only to the immediate witnesses, a small number of internal United and FAA personnel, and the early MUFON/NARCAP investigators.

The FAA's "weather phenomenon" classification

Following the Hilkevitch story, the FAA's public position, articulated by Administrator Marion Blakey and by FAA spokesperson Elizabeth Isham Cory, was that the event was best explained as a weather phenomenon, specifically a "hole-punch cloud" (also called a fallstreak hole or a cavum cloud). Verified A hole-punch cloud is a circular gap that forms in a thin layer of supercooled water-droplet altocumulus or cirrocumulus cloud when ice-nucleation triggered by passing aircraft (or other disturbance) causes the local supercooled droplets to convert to ice crystals, which fall out as a streak below; the visual appearance is a clean circular hole, often with a streamer of ice crystals trailing downward [5]. Hole-punch clouds are a recognized meteorological phenomenon and are common in conditions matching some of those at O'Hare that afternoon. The FAA's position has been that the hole in the cloud cover, which the witnesses reported, was the actual phenomenon, and that the disc-shaped object beneath it was a misperception or misidentification.

The witnesses' continuing dissent has rested on two specific points: first, that several of them reported observing the object for minutes prior to any cloud disturbance, which is not consistent with a hole-punch cloud as the primary phenomenon; and second, that the object's reported appearance (sharp-edged, dark, disc-shaped) is not consistent with the appearance of the meteorological phenomenon the FAA invoked. The dispute has not been adjudicated by any independent investigation [3][6].

The NARCAP and MUFON investigations

The most thorough civilian investigations of the incident were conducted by NARCAP, principally by its chief scientist Richard Haines and project director Ted Roe, and by MUFON, principally by Illinois state director Sam Maranto. Verified NARCAP's report, "Report of an Unidentified Aerial Phenomenon and Its Safety Implications at O'Hare International Airport on November 7, 2006," was published in March 2007 and ran to 154 pages, including witness interviews, weather and air-traffic-control records analysis, and an evaluation of the FAA's hole-punch cloud explanation [4]. The report concluded that the weather-phenomenon explanation was inconsistent with the witness reports and that the event represented an unexplained aerial phenomenon of potential aviation-safety significance. MUFON's parallel investigation, opened as Case 35083, reached substantially similar conclusions [6]. Neither civilian investigation has been treated by the FAA as the basis for reopening the official disposition of the case.

The absence of radar return

One of the structurally significant features of the case is the absence of any confirmed radar return on either the FAA's primary surveillance radar (ASR-9, then in service at O'Hare) or its secondary surveillance radar. Verified An object the size reported by the witnesses (roughly the size of a small commercial aircraft) hovering at 1,500 feet above a major commercial airport for several minutes would, on ordinary expectation, produce some primary radar return. The absence of such a return has been used by skeptical analysts as evidence that the object did not exist as described; it has been used by NARCAP and MUFON as evidence that the object had unusual radar-cross-section properties [4][6]. The radar data from the relevant period have been requested through FOIA; the FAA's response has been that detailed radar tapes from the relevant scope were not retained beyond the agency's standard retention period.

The competing positions.

Position 1: A controlled object of unknown origin.

The position held by the principal witnesses, by NARCAP, and by MUFON. Claimed The argument: the witness reports are mutually consistent in describing a discrete, edged, disc-shaped object behaving in a controlled manner over the airport; the duration of the observation (minutes, not seconds) and the multiplicity of witnesses make misperception of a meteorological phenomenon unlikely; the cloud-hole was a consequence of the object's departure, not the primary phenomenon being misperceived as an object; and the FAA's weather-phenomenon classification was reached quickly, in the absence of formal investigation, and substantively in tension with the witness testimony.

Position 2: A hole-punch cloud and associated misperception.

The position taken by the FAA and by some meteorological commentators. Claimed The argument: hole-punch clouds are real and not uncommon in supercooled-droplet altocumulus, which was present in the layered overcast at O'Hare that afternoon; the witnesses observed the hole-punch phenomenon and reconstructed a disc-shaped object below it through pareidolia and confirmation among themselves; the absence of radar return and of any photographic record is consistent with the absence of an actual object; the airline-internal pressure not to make formal incident reports, combined with the social dynamics of a small group of co-workers, produced an account more coherent than the underlying observations would individually support.

Position 3: A non-disclosed civilian or military aircraft.

A less-prominent third position, occasionally raised in aviation forums. Unverified The argument: a developmental aircraft (a high-altitude balloon, a tethered surveillance platform, a low-observable testbed) was conducting an undisclosed operation in the vicinity, and neither the operating agency nor the FAA has subsequently acknowledged it. The position is consistent with the witness testimony but is unsupported by any specific evidence of a known program operating at low altitude over downtown Chicago on the date in question, and runs against the operational improbability of conducting such a test over the world's busiest airport without formal coordination.

The unresolved questions.

The UAL 446 cockpit testimony

The cockpit crew of United 446 are reported to have observed the object from the flight deck but have not given on-the-record statements. Unverified Their testimony, if collected, would substantially strengthen or weaken the case: cockpit crew are trained observers, their statements would have the credibility of certificated airline professionals, and the cockpit voice recorder from the relevant period would, if retained, provide a contemporaneous record of any in-cockpit discussion. The CVR retention window is two hours of continuous recording; even at the time of the Hilkevitch reporting in January 2007, the relevant tape would have been overwritten. The cockpit crew has not come forward in the years since.

The internal United Airlines record

United Airlines, then in bankruptcy reorganization and managed under conditions that limited internal investigation of non-safety events, did not produce an internal report of the incident. Unverified Whether internal communications between ramp supervisors, dispatch, and operations exist as written records (email, ACARS messages, dispatch logs) has not been disclosed. United was acquired by Continental in 2010 to form United Continental Holdings (since renamed United Airlines Holdings); any preserved internal record would now sit with the successor entity.

The radar data, definitively

The FAA's position is that ASR-9 primary radar data from the relevant time and area were not retained beyond the standard retention period. Disputed Whether such tapes existed and were destroyed in the ordinary course, or were never recorded at the necessary level of detail, has not been independently resolved. The retention practice at FAA radar facilities in 2006 generally was for a limited period (typically 15–45 days) absent a specific incident designation; the November 7 event was not designated as an incident under the FAA's accident-and-incident reporting system, and would therefore not have triggered the longer retention.

The FAA's "no record" initial response

The agency's first public response to journalist inquiries in November and December 2006 was that no record of the radio call existed. Disputed That position was reversed in early January 2007 after FOIA pressure. Whether the initial "no record" answer reflected an honest internal failure to locate the log, a deliberate decision not to confirm the call, or a procedural distinction the agency drew between the call and a formal "incident record" has not been clarified by any subsequent statement. The reversal stands as the most concrete documented instance of the agency's awkward institutional posture toward the event.

Primary material.

The accessible primary record on the O'Hare event includes:

• The FAA internal operational log entry for the November 7, 2006 United radio call to the O'Hare tower, released to Hilkevitch under FOIA in December 2006.
• Jon Hilkevitch's Chicago Tribune reporting, principally the front-page article of January 1, 2007 and subsequent follow-up reporting through 2007.
• The NARCAP technical report, "Report of an Unidentified Aerial Phenomenon and Its Safety Implications at O'Hare International Airport on November 7, 2006," Haines & Roe, March 2007 (hosted at narcap.org).
• The MUFON case file for Case 35083, including witness statements and the Maranto investigation correspondence (held by the Mutual UFO Network).
• The National Weather Service surface and upper-air observations for Chicago O'Hare for November 7, 2006, available through NOAA's National Centers for Environmental Information; relevant for evaluating the meteorological context.
• FAA Administrator Marion Blakey's public statements in January 2007 articulating the hole-punch cloud classification.

The sequence.

1. November 7, 2006, ~4:15 PM CST United ramp personnel at Concourse C first observe a disc-shaped object above Gate C-17.
2. November 7, 2006, ~4:18 PM CST Object reportedly accelerates vertically through the overcast, leaving a circular hole in the cloud layer.
3. November 7, 2006, ~4:30 PM CST United operations supervisor radios the O'Hare tower; FAA logs the call.
4. Mid-November 2006 Initial inquiries by independent investigators; United Airlines and the FAA initially state no incident occurred.
5. Late November — December 2006 Jon Hilkevitch files FOIA requests with the FAA; first internal log entry confirmed.
6. January 1, 2007 Hilkevitch's Chicago Tribune front-page article publishes the incident publicly.
7. Early January 2007 FAA Administrator Marion Blakey and spokesperson Elizabeth Isham Cory publicly characterize the event as a hole-punch cloud / weather phenomenon.
8. January — March 2007 NARCAP (Haines, Roe) and MUFON (Maranto) civilian investigations conducted.
9. March 2007 NARCAP publishes its 154-page technical report concluding that the weather explanation is inconsistent with witness testimony.
10. 2007 onward Witnesses continue to give limited media interviews, generally on condition of anonymity, maintaining the original account.
11. 2010 United Airlines merges with Continental Airlines; institutional successor inherits any preserved records.
12. 2021–2024 The case is referenced in renewed congressional UAP discussion as an example of the commercial-aviation reporting problem; no formal AARO review is publicly disclosed.

Cases on this archive that connect.

The Nimitz Tic-Tac Incident (File 010) — the closest methodological comparison case. Both are multi-witness UAP encounters; the Nimitz case has multi-sensor radar and FLIR confirmation, the O'Hare case does not.

The Phoenix Lights (File 048) — the 1997 mass-witness Arizona event. Both cases share the pattern of large numbers of civilian observers, official conventional-explanation framings, and witness dissent from that framing.

The Gimbal and GoFast Videos (File 056) — the Navy-released FLIR encounters that, like O'Hare, have produced extended disputes over conventional versus non-conventional interpretations.

The Belgian UFO Wave (File 052) — another extended observation event with multiple civilian witnesses and a partial official response, where the institutional posture has shifted over decades.

Full bibliography.

1. Federal Aviation Administration. Internal operational log entry for November 7, 2006, O'Hare International Airport, ATCT/United Airlines radio communication. Released under FOIA, December 2006.
2. Hilkevitch, Jon. "In the Sky! A Bird? A Plane? A … UFO?" Chicago Tribune, January 1, 2007, page 1.
3. Hilkevitch, Jon. Follow-up reporting on the O'Hare incident, Chicago Tribune, January–March 2007 (multiple articles including witness interviews and FAA response coverage).
4. Haines, Richard F. and Roe, Ted. "Report of an Unidentified Aerial Phenomenon and Its Safety Implications at O'Hare International Airport on November 7, 2006." National Aviation Reporting Center on Anomalous Phenomena (NARCAP) Technical Report 10, March 9, 2007.
5. Schaefer, V. J. and Day, J. A. A Field Guide to the Atmosphere. Houghton Mifflin, 1981 (and subsequent meteorological literature on fallstreak holes / hole-punch clouds, including Heymsfield et al., "Aircraft-Induced Hole Punch and Canal Clouds: Inadvertent Cloud Seeding," Bulletin of the American Meteorological Society, 2010).
6. Mutual UFO Network (MUFON). Case File 35083, O'Hare Airport Incident, November 7, 2006. Sam Maranto, Illinois State Director, case investigator.
7. Federal Aviation Administration. Public statements by Administrator Marion C. Blakey and spokesperson Elizabeth Isham Cory, January 2007, characterizing the event as a "weather phenomenon."
8. National Weather Service, Chicago/Romeoville Forecast Office. Surface observations and METAR records for KORD, November 7, 2006, 21:00–22:30 UTC.
9. Greenewald, John Jr. The Black Vault. Compiled FOIA correspondence with the FAA on the O'Hare incident, 2007–present.
10. Maranto, Sam. Mutual UFO Network Journal reporting on the O'Hare investigation, 2007 issues.
11. Larry King Live (CNN), February 9, 2007. Segment on the O'Hare incident with George Knapp, Hilkevitch, and aviation analysts; transcript archive.
12. Powell, Robert. Mutual UFO Network and Scientific Coalition for UAP Studies (SCU) reanalyses of the O'Hare event in the context of post-2017 UAP reporting practice.
13. National Aviation Reporting Center on Anomalous Phenomena. Case archives, narcap.org, including subsequent commentary and updates on the O'Hare report.
14. U.S. Government Accountability Office. Reports on FAA radar data retention practices in the 2006–2010 period, providing context for the unavailability of relevant radar tapes.