The December 2024 Eugene, Oregon Pilot Sightings
On the night of December 7, 2024, in the FAA's Seattle Air Route Traffic Control Center airspace around Eugene, Oregon, the crew of United Airlines Flight 1596 (Denver–Eugene) radioed that they were seeing "three or four targets" at "all altitudes, up and down." Life Flight Network air-ambulance pilot Joe Buley, flying a Pilatus PC-12 from Aurora, Oregon toward North Bend, heard that call and soon reported his own lights, including a red one "zipping towards us and then back out towards the ocean." A Seattle Center controller, recorded in a 44-minute LiveATC archive that spread online within days, cleared him "to maneuver as necessary left and right to avoid the UFO out there." A Horizon Air crew on the same frequency said, "No, it's not Starlink, I promise." The FAA confirmed that a pilot had reported unidentified lights. Within a week, analysts on the Metabunk forum had used the Sitrec tool with flight-track data to match both a photo from the United flight and a video taken aboard Buley's aircraft to the predicted positions of Starlink satellite flares. Scientist Douglas Buettner, who had studied a similar 2022 case, called Starlink "most likely." Buley and the Horizon crew remain unconvinced, chiefly because the light seemed to change direction.
Bottom line
- Best explanation
- Starlink satellite flares. Analysts on the Metabunk forum matched both a photo from United 1596 and the medevac crew’s own video of the “red orb” to predicted Starlink flares in time and position, and a scientist who studied a similar 2022 case called Starlink “most likely.”
- Why “Disputed”
- No official body has investigated, and the witnesses reject the satellite answer. The flare matches come from a volunteer forum, not a formal inquiry, and the pilots’ account of a light changing direction for 20 minutes has been explained as an illusion, not shown to be one.
- What would change it
- A formal investigation or published analysis of the flare reconstructions, or the clearer video and further data the scientist wanted. The FAA confirmed only that a report was filed and has published no investigation.
Pictured: downtown Eugene, Oregon and Spencer Butte, seen from Skinner Butte — not a photograph of the reported lights themselves. No rights-clear photograph or video frame of the actual December 7, 2024 sighting is known to exist; the crews' photos and phone video circulated on social media, and this site does not reproduce them.
Theoretical Alignment
Low-to-moderate alignment with the Extraterrestrial Hypothesis: the reported motion (rapid direction changes, a "corkscrew pattern," a light that seemed to close in and retreat) would be striking if instrumentally confirmed, but ATC radar saw nothing, and the crews' own photos and video have been matched to Starlink satellite flares. A meaningful Psycho-Social component is plausible given that the sighting broke nationally at the exact moment the concurrent New Jersey drone wave had saturated U.S. media with nighttime-sky anxiety, though the underlying pilot reports themselves were filed with ATC in real time, before any of that national coverage existed — a genuine timing coincidence discussed in detail below, not evidence the pilots were primed by the drone panic.
Background
Eugene, Oregon, sits in the southern Willamette Valley, roughly 110 miles south of Portland and within a wider Pacific Northwest corridor that has an outsized place in American UFO history: Kenneth Arnold's foundational June 24, 1947 sighting near Mount Rainier, Washington — the case that coined the term "flying saucer" — occurred roughly 200 miles to the north-northeast, and the celebrated McMinnville photographs were taken on a farm near McMinnville, about 100 miles north of Eugene, in May 1950. According to Willamette Week, Portland and Seattle have had more reported sightings since 2000 than any other U.S. metro area, and both McMinnville and Chehalis, Washington host annual UFO festivals.
December 2024 was an unusually charged month for U.S. aerial-anomaly reporting generally. Beginning November 13, 2024, thousands of nighttime drone and light reports had already swept New Jersey and spread into New York, Pennsylvania, and other Northeastern states — the subject of this site's separate New Jersey / Northeast Drone Wave case file — and by the first week of December that story had become one of the most heavily covered domestic news items in the country, with nightly cable-news segments, a Congressional briefing, and public statements from the outgoing Biden administration. It was against that specific national backdrop, on the far side of the continent and involving an entirely separate set of witnesses, aircraft, and airspace, that the Eugene sightings occurred and were then reported.
Commercial and air-ambulance pilots are not casual observers. Both categories of witness in this case — an airline flight crew and a dedicated medical-transport pilot — hold FAA certifications requiring flight-hour minimums and recurrent training, and they work in a professional culture that discourages sensational reporting over an open, recorded radio frequency. That training does not, however, include identifying Starlink satellite flares, which have only been common since 2019.
Complete Timeline
| Date | Event |
|---|---|
| Nov 13, 2024 | The New Jersey / Northeast drone wave begins, an unrelated but concurrent national news story that would dominate U.S. aerial-anomaly coverage through December 2024 and into January 2025. |
| Dec 7, 2024, ~8:39 PM PST | The crew of United Airlines Flight 1596, inbound to Eugene from Denver, asks Seattle Air Route Traffic Control Center (ZSE), "Is there any military activity out straight ahead of us?" The controller says no, but mentions another report of something at 30,000 feet. The pilot adds: "just straight west of Eugene. I mean it's — we're seeing three or four targets. They're all altitudes up and down; it's pretty crazy," and says the lights are "shooting way up," reportedly to about 50,000 feet. |
| Dec 7, 2024, ~8:40–8:53 PM PST | Life Flight Network pilot Joe Buley, flying Pilatus PC-12 N661LF from the carrier's Aurora, Oregon base toward North Bend with two medics aboard, has just checked in with Seattle Center while climbing through about 7,000 feet. He hears the United report, and near Corvallis his crew begins seeing lights. He reports traffic "at about 2–3 o'clock, 20–30 miles," then "another one show up about my 1 o'clock about 1,000 feet high, zipping towards us and then back out towards the ocean... It's red in color, um, moving at extreme speeds. I don't even know how to describe on how it's moving." At one point he describes a light moving in "a corkscrew pattern." |
| Dec 7, 2024, ~8:53 PM PST | The Seattle Center controller tells the medevac flight: "Medevac 1LF roger. You are cleared to maneuver as necessary, left and right, to avoid the UFO out there." |
| Dec 7, 2024 (local) | A Horizon Air crew (Flight 2207) on the same frequency also reports lights. According to a transcription of the recording, they said, "There's something flying, it's not satellites, they're changing direction," and that the lights "stayed with us the whole way in." Willamette Week quotes a pilot rejecting the satellite idea ("No, it's not Starlink, I promise") and reports that a Horizon pilot said he had seen the same thing "a few times over the last month in the same area." KGW, citing a controller, dated the Horizon reports December 8; the recording ran past midnight UTC, which is December 8 in UTC. |
| Dec 7–8, 2024 | The full exchange is captured on a publicly archived 44-minute LiveATC.net recording of Seattle Center's frequency, which becomes the primary evidentiary record of the incident. |
| Dec 8–9, 2024 | The recording circulates on Reddit. On December 9 a Metabunk member posts a Sitrec comparison matching a photo taken from United 1596 to a predicted Starlink satellite flare. The National UFO Reporting Center also receives a report from a different pilot who overheard the radio chatter while landing. |
| Dec 11–13, 2024 | OregonLive, KGW, KEZI, KPIC/KVAL and KATU report the story, followed by Newsweek, NewsNation and the New York Post. The FAA confirms: "A pilot reported seeing unidentified lights while flying in Seattle Air Route Traffic Control Center airspace on Saturday, Dec. 7," but will not confirm that the circulating audio is authentic. Life Flight Network confirms its pilot is on the recording and says the light "at no time... pose[d] any safety risk to our aircraft or crew." |
| Dec 12–13, 2024 | Douglas Buettner, deputy chief scientist of the Acquisition Innovation Research Center at Stevens Institute of Technology, who led a study of a 2022 Pacific airline sighting, tells KTVB and KGW that the lights appear "to be Starlink satellites, most likely." He explains, "literally all it is" is sunlight reflecting off a satellite, notes that two other people who reviewed the case agreed it was "consistent with Starlink," and says clearer video and more data would be needed to rule out other explanations. |
| Dec 14, 2024 | Buley sends a video with metadata to a Metabunk analyst. Synced in Sitrec with the PC-12's ADS-B track, the "red orb" appears at the same place and time as a predicted Starlink flare. The analyst concludes that its brightening and fading gave the illusion of approach and retreat. |
| Dec 13, 2024 | Joe Buley tells KEZI and KGW he is not convinced: "Satellites don't typically change directions. But then again, I could be wrong, but I honestly don't think it was. I've never seen a satellite move like that." |
| Jan 14, 2025 | Willamette Week publishes a feature situating the Eugene sightings within the broader history of Pacific Northwest UFO reports, from Kenneth Arnold through McMinnville to the present. |
| Sep–Oct 2025 | FAA Notice N 7110.800 (dated September 12, 2025; effective October 26, 2025) replaces the term "UFO" with "UAP" in the controller manual, JO 7110.65 §9-8-1, and tells controllers to inform their supervisor of any reported UAP activity. A companion notice, N 7210.970 (September 25, 2025), requires facilities to notify the FAA's security coordinators. At the time of the Eugene exchange, the manual itself still used the word "UFO." |
The Sightings
The exchange began, as far as the public record shows, with the crew of United Airlines Flight 1596, a scheduled passenger flight approaching Eugene from Denver. The recording starts at 0430 UTC on December 8 (8:30 PM Pacific on December 7). At about 8:39 PM, the crew asked Seattle Center, "Is there any military activity out straight ahead of us?" The controller said no, and added that he had another report of something at 30,000 feet. The pilot went on: "just straight west of Eugene. I mean it's — we're seeing three or four targets. They're all altitudes up and down; it's pretty crazy." He also said the lights were "shooting way up," which OregonLive reported as about 50,000 feet. That is far above the airliner, but a point of light has no visible size, so its altitude cannot be judged by eye. The crew's tone is measured; it is a professional traffic call, not an emergency.
A second aircraft was already on the frequency: a Life Flight Network medical flight flown by Joe Buley in a Pilatus PC-12 (registration N661LF), heading from Aurora, Oregon toward North Bend–Coos Bay with two medics aboard. Buley told KEZI that he had just checked in with Seattle Center while climbing through 7,000 feet when he heard another aircraft report "strange things," and that he and his crew talked about it before they began seeing lights near Corvallis. So his sighting was not fully independent of United's: he knew lights had been reported before he looked. He described three separate events. First came an "orangish red orb... probably at least 20 miles away" that "spun down a little bit, and then moved on to the north," seen for "10 to 15 seconds at most," along with a white strobe at his 3 o'clock that he first took for an aircraft. Second was a light "at a much higher altitude" that moved around a small part of his field of view for 10 to 15 seconds. Third, and strangest, was a light at his own altitude that would "come up to us and sit for about three to five seconds, and then it would go back out over the ocean, over the horizon... almost like a boomerang." On the radio he called it "red in color... moving at extreme speeds," and said one light was moving in "a corkscrew pattern." He told KGW, "Usually, things don't change directions unless it's an aircraft." In a later Reddit post he said his crew watched this light for more than 20 minutes, all the way south and back north toward Florence. He also said it seemed to "park itself 22 miles off my right wing."
Buley's accounts of his TCAS (Traffic Collision Avoidance System) display are not consistent. To KEZI he tied the TCAS target to the white strobe: "I looked down at my TCAS and I showed traffic there. That's when I asked ATC if they had traffic at our 2 o'clock and 22 and a half miles, and they replied with no." In a Reddit post quoted on Metabunk, he said the red light sat on the "22 1/2 mile ring on my TCAS" and followed his descent from 16,000 to 14,000 feet. But asked directly by a Metabunk analyst whether he saw the red light move on TCAS, he wrote: "i don't think I ever saw it moving on TCAS as I was trying to fly talk to ATC watch the object and communicate with my med crew. Things were a little busy." TCAS displays only transponder-equipped aircraft, so a satellite could not produce a target. A real but unidentified transponder return, or a coincidental one, at the strobe's position remains possible, but the evidence for a TCAS "track" of the red light is weak. No resolution advisory was issued, and Life Flight said the light "at no time... pose[d] any safety risk to our aircraft or crew."
A third crew, Horizon Air Flight 2207, is also heard on the recording. According to a transcription posted to Reddit and reproduced on Metabunk, the crew said, "They're not satellites... at least 4," "There's something flying, it's not satellites, they're changing direction, it's strange looking," and "They stayed with us the whole way in." Willamette Week quotes a pilot saying "No, it's not Starlink, I promise," and reports that a Horizon pilot said he had seen the same phenomenon "a few times over the last month in the same area." No independent report of those earlier sightings has surfaced. KGW, citing a controller, said two Horizon pilots reported lights; it dated their reports December 8, which matches the UTC date of the recording.
The Air Traffic Control Recording
The episode is preserved on a 44-minute recording of the Seattle Center frequency, archived by the volunteer service LiveATC.net and reposted to Reddit and YouTube. Newsweek reported that the recording's metadata and contents matched flight records, although the FAA declined to confirm it was authentic. This is one of the case's real strengths: it is a real-time record of professional aviators describing what they saw as it happened, not a reconstruction from memory. It also shows that the crews were listening to each other's reports, which matters when judging how independent their accounts were.
The most widely quoted line came at about 8:53 PM, when the controller told Buley's flight: "Medevac 1LF roger. You are cleared to maneuver as necessary, left and right, to avoid the UFO out there." Controllers routinely give pilots discretion to maneuver around traffic. The word "UFO" was not improvised slang, either: the controller manual then in force, FAA Order JO 7110.65 §9-8-1, still used the term "UFO." FAA Notice N 7110.800 (September 12, 2025; effective October 26, 2025) later replaced it with "UAP" and required controllers to tell their supervisor about such reports, and Notice N 7210.970 (September 25, 2025) added notification of the FAA's security coordinators. The controller's wording does not mean the government had classified the light as anything.
The same controller told the United crew there was no military activity ahead when they asked, adding that he had "another one reported at 30,000" feet and was "not sure what it is." Because that assurance is sometimes cited, including in some of this case's own press coverage, as evidence ruling out a military explanation for the lights, it is worth being explicit about what weight to give it: an on-the-fly, real-time assurance from a single air traffic controller reflects that controller's own immediate situational awareness of scheduled, coordinated military flight activity in their sector at that moment — not a comprehensive, after-the-fact confirmation from the Department of Defense that no classified, unscheduled, or otherwise non-coordinated military asset (flare drop, training exercise, high-altitude balloon, or experimental platform) was operating in the area. Official government and military statements of this kind, offered informally and without a documented investigation behind them, are a genuinely useful data point but not a dispositive one; agencies with an institutional and career interest in the least-alarming available explanation have a documented history — from the Air Force's own Project Blue Book-era "swamp gas" rulings to the CIA's later-acknowledged 1950s-60s practice of quietly letting U-2 and OXCART reconnaissance flights be misreported as UFOs rather than correcting the record — of incomplete or convenient real-time reassurances that were only fully clarified, if ever, much later. That history does not mean the controller's statement here was wrong; it means it should be weighed as one input among several, not treated as proof.
Media Coverage and the Starlink Explanation
Within days of the recording's public circulation, Oregon television stations KGW, KATU, and KEZI ran interviews with Buley, and national outlets including Newsweek, NewsNation and the New York Post picked up the story, which OregonLive had broken with the ATC audio. The FAA, asked directly for comment, confirmed only the bare fact that a report had been filed: "A pilot reported seeing unidentified lights while flying in Seattle Air Route Traffic Control Center airspace on Saturday, Dec. 7." The agency declined to say more, and would not confirm the authenticity of the circulating audio.
The most prominent expert comment came from Douglas Buettner, deputy chief scientist of the Acquisition Innovation Research Center at Stevens Institute of Technology. Buettner was lead author of a 2024 study (arXiv 2403.08155, presented to an International Academy of Astronautics conference on space situational awareness). It reconstructed an August 10, 2022 sighting by five pilots on two airliners over the Pacific and identified the object as the Starlink "train" launched that same day, using satellite orbital elements and ADS-B flight data. He told KTVB and KGW that the Oregon lights appear "to be Starlink satellites, most likely": "literally all it is" is sunlight reflecting off a satellite. He said two other people who looked at the case agreed it was "consistent with Starlink," but that clearer video and more data would be needed to rule out other possibilities. (An earlier version of this page said he put his confidence at "60 to 80 percent"; this site could not find that figure in any source.)
Analysts on the Metabunk forum went further. On December 9, 2024, a member posted a comparison of a photo taken from United 1596 with a reconstruction in Sitrec, a tool that combines satellite orbital data with aircraft ADS-B tracks to show what a crew would have seen. The bright light in the photo matched a predicted Starlink flare. Other members identified lights in additional crew footage as the bright stars Altair and Vega plus a Starlink flare. On December 14, the same analyst reported that Buley had sent him a video with its file metadata. Synced in Sitrec with the PC-12's track, the "red orb" appeared "at exactly the same spot and at the same time as we'd expect it to if it was a Starlink satellite flare." He attributed the red color to atmospheric attenuation and scattering, and the apparent approach and retreat to the flare brightening and fading. National UFO Reporting Center chief technology officer Christian Stepien made a similar general point to KPIC: satellites maneuvering into their final orbits "can look really bizarre, and a lot of pilots aren't familiar with that."
The Starlink explanation is a specific, checkable analysis, not a wave of the hand. It rests on reconstructions that match the timing and position of the crews' own photo and video, and anyone with the same data can reproduce them. Two things keep it short of complete proof. First, Metabunk is a volunteer forum, and its reconstructions have not been formally published or reviewed by an independent body. Second, Buley, his crew and the Horizon crew all describe directional changes and a light that kept its distance for 20 minutes or more. A satellite flare cannot do that. But a series of flares appearing and fading at the same point in the sky, seen from a moving aircraft by observers who assumed the light was about 20 miles away, could produce that impression. That is the analysts' argument, and the video supports it. The pilots' testimony is sincere and consistent. Against it, the one direct recording of the red light matches a satellite flare.
The New Jersey Drone Wave Backdrop — A Genuine Coincidence, Not the Same Story
Because the Eugene sightings broke into national media on almost exactly the same days — December 12–13, 2024 — that the New Jersey / Northeast drone wave was reaching its own media peak, a number of outlets covering the Oregon story explicitly framed it as part of the same national moment, and some readers have since conflated the two. It is worth being precise about what is and is not actually connected.
The two incidents are geographically, procedurally, and evidentially distinct. The New Jersey wave involved thousands of ground-based civilian reports of nighttime drone and light activity beginning November 13, 2024, concentrated initially around Picatinny Arsenal in New Jersey and later spreading across multiple Northeastern states, investigated by the FBI, DHS, and FAA, and eventually attributed by federal officials to a mix of lawfully operated commercial and hobbyist drones, misidentified manned aircraft, and stars. The Eugene sightings, by contrast, involved a small number of airborne reports — from professional flight crews, not ground observers — over a single evening in a single, specific stretch of Oregon airspace, investigated (to the limited extent it was investigated at all) by the FAA alone, with no drone, DHS, or FBI involvement reported anywhere in the public record. Nothing in the Eugene case's ATC recording, FAA statement, or witness interviews mentions drones, New Jersey, or any suspected connection between the two events; the pilots' real-time radio reports came before the Eugene story's own national coverage. The New Jersey drone story, however, was already national news by December 7, so this site cannot rule out that it shaped how the crews framed what they saw. The crews certainly heard each other's reports on the frequency.
What genuinely is shared between the two stories is timing and atmosphere, not substance: December 2024 was a month in which American aviation and national-security media coverage was unusually primed to treat any unexplained nighttime light as a potential story, and outlets covering Eugene frequently opened their articles by referencing the concurrent New Jersey coverage as a hook, which likely inflated the Eugene story's own national reach beyond what a standalone regional pilot report would typically receive. Readers and researchers revisiting this case should treat the New Jersey drone wave as useful contextual backdrop for why the Eugene sightings received the national attention they did — and, separately, as a genuinely relevant precedent for how a federal investigation of an aerial-anomaly wave can conclude with real evidence (identified drones, misidentified aircraft, stars) but still leave officials publicly unable to agree on a single, complete explanation — without treating the two incidents as a single event or evidence for one another.
Key Witnesses
Joe Buley
The case's central named witness, and the only one to give repeated, named interviews. Buley, 37, told KEZI he has been flying since 2013 and has more than 6,000 hours. On December 7, 2024 he was flying Life Flight Network's Pilatus PC-12 N661LF from Aurora toward North Bend with two medics. After hearing United 1596's report, he and his crew saw an orange-red light and a white strobe near Corvallis, then a red light that seemed to approach and retreat over the ocean for more than 20 minutes. His accounts of whether the red light appeared on his TCAS are not consistent (see above). He shared his crew's video with Metabunk analysts, who matched it to Starlink flares. He remains skeptical: "Satellites don't typically change directions... I've never seen a satellite move like that." He and Life Flight both stressed that the light posed no danger to the flight.
United Airlines Flight 1596 Crew (anonymous)
The first crew to report the lights to Seattle Center, at about 8:39 PM. Neither pilot has been publicly named, and United has not commented. The crew asked about military activity and reported "three or four targets" at "all altitudes up and down." A photo from the flight deck, forwarded by the controller to a member of the public and posted online, was matched on Metabunk to a Starlink flare. Airline pilots generally need an FAA Airline Transport Pilot certificate, which normally requires 1,500 flight hours (fewer under restricted-ATP rules), plus recurrent training.
Horizon Air Flight 2207 Crew (anonymous)
Horizon Air Flight 2207 also reported lights on the same frequency. According to a transcription of the recording, the crew said, "There's something flying, it's not satellites, they're changing direction." Willamette Week quotes "No, it's not Starlink, I promise" and reports that a Horizon pilot said he had seen the same phenomenon "a few times over the last month in the same area." No other report corroborates those earlier sightings.
The Five Observables Assessment
Assessment: Low Observability is scored Present only in the narrow sense that ATC radar showed nothing where the pilots saw lights. That is expected for satellites, and the pilot's own accounts of a TCAS target are inconsistent. Anti-Gravity Lift and Instant Acceleration are scored Speculative rather than Present because the "corkscrew" and "boomerang" directional changes described by the witnesses are vivid and shared by crews who could hear each other, but were never captured by any instrument capable of measuring true velocity — only human perception, an ambiguous TCAS report, and video that analysts matched to satellite flares, neither of which can rule out an optical-brightness illusion of the kind the Starlink hypothesis proposes. Hypersonic and Trans-Medium are not applicable; nothing in the record describes a speed estimate exceeding conventional aircraft performance, and there is no claim of the object entering water, ground, or any medium beyond air.
Evidence Assessment
Supporting Anomalous Origin
- Three professional flight crews reported lights on the same frequency the same evening (though each could hear the others' reports)
- The primary witness (Joe Buley) is named and on the record, and shared his crew's video
- Buley reported a TCAS traffic target about 22 miles away that ATC radar did not show (though his accounts link it variously to a white strobe and the red light, and he later said he did not see the red light move on TCAS)
- Buettner called Starlink "most likely" but wanted clearer video and more data, and the Metabunk reconstructions have not been formally published
- The medevac and Horizon crews rejected the satellite explanation based on the motion they saw
- A Horizon pilot reportedly said he had seen the same thing "a few times over the last month in the same area"
- The entire exchange exists as an unedited, contemporaneous, third-party-archived audio record, not reconstructed after the fact from memory
Supporting Conventional Explanation
- Sitrec reconstructions matched both a photo from United 1596 and the medevac crew's own video of the "red orb" to predicted Starlink flares in time and position
- Starlink flares seen from aircraft over the Pacific are a documented source of pilot reports (Buettner et al. 2024)
- Other lights in the crew footage were identified as the stars Altair and Vega
- No radar corroboration exists from ATC's own ground-based systems for the primary object
- No physical trace or debris exists, and the released video shows a fading and brightening point, not a moving craft
- The FAA's own confirmation was limited strictly to the fact that a report was filed; the agency offered no assessment of the object's nature and has published no investigation
- Nighttime visual misjudgment of distance, speed, and direction change is well-documented in aviation human-factors literature, particularly for a static or slow-moving light against a featureless dark sky with no reference points
Why "Disputed"
This case is classified DISPUTED because no official body has investigated it, and the people who saw the lights reject the explanation that the best available evidence supports. Three crews reported lights on a recorded frequency, which is a better foundation than a single account. But the crews heard each other, and the one direct recording of the "red orb" (the medevac crew's own video) and a photo from United 1596 have both been matched to predicted Starlink flares by reproducible Sitrec reconstructions. Buettner, who studied a similar Pacific case, calls Starlink "most likely." What keeps the file open is that these reconstructions come from a volunteer forum rather than a formal investigation, and that the pilots' descriptions of a light that kept its distance and changed direction for 20 minutes have been explained as an illusion rather than shown to be one in every detail. This site regards satellite flares as the probable explanation.
Sensor & Instrumentation Detection Profile
The case's instrumentation record is thin. Buley reported a TCAS traffic target about 22 miles off at his 2–3 o'clock that ATC did not see, but his descriptions link it to different lights, and he later said he did not think he saw the red light move on TCAS. TCAS shows only transponder-equipped traffic, so it could not have shown a satellite. Seattle Center reported seeing nothing in the positions the pilots gave. The medevac crew filmed the red light on a phone; the video shows an orange speck fading in and out. Buley later sent a copy with metadata to a Metabunk analyst, who synced it to a Starlink flare. Crew photos and short clips from the United flight were forwarded by the controller to members of the public and posted online. No military sensor data has been reported.
Environmental & Geospatial Context
The sightings occurred over the southern Willamette Valley and toward the Coast Range and the Pacific, within Seattle Center (ZSE) airspace. Weather around Eugene had cleared after rain earlier in the day: Open-Meteo's ERA5 reanalysis shows 11–28% cloud cover and about 2–3°C between 8 and 9 PM, with no precipitation. Buley said fog at Coos Bay was too thick for him to land. According to JPL Horizons, the Moon was about 44% illuminated and roughly 20–24° up in the southwest at the time. The lights were reported looking west, toward the ocean, the direction in which Starlink flares were predicted to appear. The reported altitudes, from the medevac aircraft's cruise altitude (about 14,000–16,000 feet) up to an estimated 50,000 feet, are visual guesses at points of light, and the crews may have been describing several different light sources.
Observer Credibility & Occupational Profile
All three flight crews involved in this case are professionally credentialed aviators operating under FAA Part 121 (scheduled airline) or Part 135 (air-ambulance/charter) certification, the two most rigorously regulated categories of civil aviation in the United States. Airline Transport Pilot certification, required of airline crews, normally demands 1,500 flight hours (fewer under restricted-ATP rules) plus recurrent simulator training. Joe Buley's Part 135 air-ambulance certification carries its own demanding recurrency and check-ride regime, and his more than 6,000 flight hours since 2013 represent a substantial, verifiable track record with no reported disciplinary or credibility issues raised by any source reviewed for this case file. All three crews delivered their reports in the same register: calm, specific, professionally phrased traffic calls to air traffic control, not excited or embellished accounts to a media outlet after the fact — exactly the discipline pilots are trained to maintain under workload, and a real, positive credibility signal. Weighed against that occupational credibility is the same limitation present in nearly every fast-moving nighttime aerial sighting: even the most experienced pilot's naked-eye assessment of a distant point of light's true distance, size, and motion is inherently imprecise without an independent instrument cross-check, and human perception is well documented to misjudge a brightening and dimming light as an approaching and retreating one. As one Metabunk member noted, pilots trained before 2019 were never taught what Starlink flares look like.
Physical & Material Assays
No physical evidence of any kind — debris, trace material, or recovered object — exists in this case. No landing, close-range encounter, or ground-level effect was reported by any witness. The only tangible artifacts are the archived audio recording, the crews' photos and phone video (shared online and with Metabunk analysts), the FAA's brief confirming statement, and a NUFORC report from a pilot who overheard the radio traffic.
Historical Precedents & Archive Matches
The Eugene sightings sit within a dense regional history of Pacific Northwest aerial-anomaly reports. Kenneth Arnold's June 24, 1947 sighting of nine crescent-shaped objects near Mount Rainier, Washington, which coined the term "flying saucer," occurred less than 200 miles to the north; the celebrated McMinnville photographs, taken by Paul and Evelyn Trent on their farm and later published in Life magazine, were captured about 100 miles north of Eugene in May 1950. Willamette Week reports that Portland and Seattle have had more reported sightings since 2000 than any other U.S. metro area. The closest technical precedent, though, is Buettner's own case: on August 10, 2022, five pilots on two airliners over the Pacific reported a UAP that he and his co-authors identified as the Starlink train launched that day.
Within this site's own case files, the Eugene sightings share the most direct structural similarity with the February 2021 New Mexico American Airlines encounter, another case built entirely around a real-time, professionally delivered ATC radio report from a commercial airline crew, subsequently authenticated by the airline and confirmed (in each case only partially) by the FAA, with no radar corroboration and no resolved conventional explanation. Both cases illustrate the same evidentiary pattern: a credentialed pilot's real-time report is much harder to dismiss as fabrication or memory drift than an after-the-fact witness account, but that same immediacy means neither case benefits from the kind of extended, multi-instrument investigation that stronger-evidence cases like the Coyne helicopter incident received. The New Jersey / Northeast drone wave, discussed at length above, is a genuinely relevant precedent for a different reason: it demonstrates that even a federal investigation drawing on FBI, DHS, and FAA resources and reviewing more than 5,000 individual reports can conclude with a real evidentiary basis (identified drones, misidentified aircraft, stars) while still leaving senior officials publicly unable to agree on one single, complete account — a caution against assuming that "a plausible conventional explanation exists" and "the case is fully resolved" are the same thing.
Material Analysis
Because no physical trace, debris, or recovered object exists in this case, "material analysis" here refers instead to the case's instrumented and photographic record — the closest analogue this incident has to physical evidence.
The TCAS Registration
The TCAS report has drawn the most attention. TCAS works by interrogating nearby aircraft transponders, and many installations also receive ADS-B broadcasts. A satellite has neither, so a TCAS target could not have been a Starlink flare. But the target Buley described to KEZI was the one he associated with a white strobe at his 2 o'clock, about 22.5 miles away. He later told a Metabunk analyst he did not think he ever saw the red light move on TCAS. A transponder-equipped aircraft that ATC was not tracking, or a spurious target, would explain a single TCAS return. Neither would make the red light anomalous. Without a data export, the TCAS episode cannot be checked.
The Photographic Evidence
A still photograph from the United flight deck, and short clips, were forwarded by the Seattle Center controller to members of the public who contacted him, and were posted to Reddit and Imgur. The medevac crew's phone video was shared by Buley (some of it on his wife's YouTube channel) and sent with metadata to a Metabunk analyst. Both were reconstructed in Sitrec against public orbital data and ADS-B tracks, and both matched predicted Starlink flares. This site has not independently verified the metadata, but the method is reproducible by anyone with the same files.
Supporting Non-Terrestrial Origin
- Buley reported a TCAS traffic target that ATC did not see, though his accounts of it are inconsistent
- The medevac and Horizon crews described directional change rather than a steady or gradually fading light
- The crews described several different lights at different apparent altitudes, not all of which have been individually matched
Supporting Terrestrial/Conventional Origin
- Sitrec reconstructions matched the United photo and the medevac crew's video of the "red orb" to predicted Starlink flares
- The released video shows a speck brightening and fading in place, not a craft in motion
- No physical trace, debris, or recovered material exists
- Perceived approach/retreat motion from a brightening/dimming light source is a well-documented visual illusion under nighttime conditions
The Conventional Explanation Candidate (CEC)
Four distinct conventional explanations have been proposed or are reasonably considered for the Eugene sightings, evaluated individually below.
SpaceX Starlink Satellite Flares
The leading explanation. Starlink satellites can produce sharp flares of reflected sunlight when the Sun lies below the observer's horizon but still lights the satellite. Seen from an aircraft looking west after dark, a flare grows bright and fades over seconds to minutes, often at the same place in the sky as the next one. Douglas Buettner, who identified a 2022 Pacific airline UAP as a fresh Starlink train, called Starlink "most likely" here. Metabunk analysts using Sitrec matched both a United 1596 photo and the medevac crew's own video of the "red orb" to predicted Starlink flares in time and position. That makes this the only candidate backed by a checkable reconstruction of the actual imagery. Its weak points are that the reconstructions have not been formally published, and that the pilots' descriptions of direction changes and of a light that held its distance have to be explained as perception rather than motion.
Misidentified Conventional Aircraft
A distant conventional aircraft's anti-collision strobe or navigation lighting, viewed at night against a featureless dark sky with no reference points, can produce a visual impression of erratic movement, particularly if the observing pilot is simultaneously flying their own aircraft and only glancing at the light intermittently. This explanation is weakened significantly, though not eliminated outright, by the fact that both the United and Horizon Air crews are themselves trained, current pilots highly familiar with what standard aircraft lighting looks like from the air, and by ATC's statement that it saw nothing in that position — though, per the caveat discussed in the Sensor & Instrumentation section above regarding real-time controller assurances generally, an unscheduled, non-transponding, or otherwise uncoordinated aircraft would not necessarily have appeared on that same radar picture either.
Military Flares or an Unannounced Training Exercise
Military flare drops or training exercises are a documented, recurring source of unusual nighttime aerial-light reports near U.S. airspace corridors, and would plausibly account for a light near the coast given the region's proximity to several Pacific Northwest military training areas. This candidate is weakened by the Seattle Center controller's answer to the United crew that there was no military activity ahead, and by the fact that no flare-like behavior (slow descent, burnout) was described. As with any real-time institutional assurance of this kind, it is worth weighing that statement carefully rather than treating it as automatically conclusive: government and military bodies, including air traffic control facilities coordinating with the Department of Defense, have a documented history of incomplete or delayed real-time situational awareness regarding classified, unscheduled, or otherwise non-standard military activity, and a single controller's immediate assurance is not equivalent to a formal after-the-fact confirmation from the relevant service branch that no asset of any kind was operating in the sector. This is not a claim that the controller was wrong, or that the military was concealing anything in this specific instance — no evidence in the public record suggests that — only that the statement should be treated as one input among several rather than a definitive ruling-out of the candidate.
Genuine Unexplained Anomaly
A residual possibility remains that some of what the crews saw was not explained by any of the candidates above. The case for it rests on the pilots' testimony about direction changes and on the TCAS report. The TCAS report is inconsistent, and the testimony conflicts with the crew's own video, which matches a satellite flare. This candidate has no positive evidence of its own.
Plausibility Ratings
SpaceX Starlink Satellite Flares
Plausible (as source of the photographed light) Inconclusive (as complete explanation)Matched to the actual imagery: a photo from United 1596 and the medevac crew's video of the "red orb" both line up with predicted Starlink flares. Called "most likely" by Buettner. It is not formally confirmed, and the pilots' perception of direction changes must be explained as an illusion.
Misidentified Conventional Aircraft
ImplausibleWeakened by trained crews not recognizing the lights as aircraft lighting and by ATC seeing nothing in that position, though an aircraft may explain the white strobe and the TCAS target Buley associated with it.
Military Flares / Training Exercise
InconclusiveWeakened by the controller's statement that there was no military activity ahead and by the lack of flare-like behavior; not formally ruled out by any service branch.
Genuine Unexplained Anomaly
InconclusiveSupported only by the pilots' perception of motion and a disputed TCAS report; the direct imagery matches satellite flares.
Related Cases
Official Records & Reporting Channels
Changed the controller manual (JO 7110.65 §9-8-1) from "UFO" to "UAP" and required controllers to inform their supervisor of reported UAP activity; effective October 26, 2025. The companion Notice N 7210.970 (September 25, 2025) covers notification of the FAA's NTSO Air Traffic Security Coordinator. At the time of the Eugene sightings the manual still used "UFO."
UNCLASSIFIEDCivilian sighting database. KPIC reported that NUFORC received a report from a pilot who overheard the radio traffic while landing. (Earlier versions of this page gave this as report #184932 with a "Starlink (Racetrack) — Possible" note; NUFORC's site blocked automated access during this review, so that entry was not re-checked.)
UNCLASSIFIED (public database)The Pentagon's official UAP investigation office. No AARO report or public statement specifically addressing the Eugene sightings has been located in the public record as of this case file's publication.
UNCLASSIFIEDSearch Government Archives Directly
Further Reading — Recommended Literature
UFOs: Generals, Pilots, and Government Officials Go on Record
The definitive case for taking credentialed pilot and official testimony seriously, directly relevant to a case built entirely around professional aviators' real-time reports.
Imminent
The former AATIP director's account of the modern UAP disclosure push, including the framework behind the Five Observables applied throughout this case file.
UFO: The Inside Story of the US Government's Search for Alien Life Here—and Out There
A comprehensive modern history of official U.S. government UAP investigation, useful context for how a case like this one moves (or doesn't) through federal channels.
The Coming of the Saucers
Kenneth Arnold's own account of the 1947 sighting that founded the Pacific Northwest's place in UFO history, the direct regional precedent for this case.
Escaping the Rabbit Hole (Revised & Updated)
By the founder of Metabunk, the forum whose Sitrec reconstructions matched the crews' photo and video to Starlink flares.
DISCLOSURE: Some links above are affiliate links. If you purchase through them, OverClassified receives a small commission at no additional cost to you. This helps support independent research.
Essential Viewing
Life Flight Pilot Reports Seeing "UFO" Near Eugene, Oregon
KATU News segment covering pilot Joe Buley's account of the December 7, 2024 sighting.
Oregon Pilot Speaks Out After Seeing UFO
KEZI 9 News follow-up interview with Joe Buley detailing his skepticism of the Starlink explanation.
"Buzzed an Aircraft" / "It's on TCAS" — UFOs Spotted Over Oregon (ZSE ARTCC)
Full annotated playback of the archived Seattle Center air traffic control recording covering the incident.
Sources
- Federal Aviation Administration. Public statement confirming a pilot report was filed in Seattle ARTCC airspace, Dec. 7, 2024, as quoted in multiple outlets below.
- KATU News. "Life Flight pilot reports seeing 'UFO' near Eugene." katu.com
- KEZI 9 News. "Pilot speaks on UFO sighting over Western Oregon skies." kezi.com
- KGW. "Pilots report mysterious lights 'moving at extreme speeds' across Oregon skies." kgw.com
- KGW. "Oregon pilot remains 'as curious as everybody else' about mysterious lights in sky." kgw.com
- KPIC/KVAL. "At least one report of UFO sighting over Eugene by commercial pilot, FAA confirms." kpic.com
- Newsweek. "Pilots told to 'maneuver' around Oregon 'UFO' in leaked cabin audio." newsweek.com
- Newsweek. "Pilot encountered mystery objects 'moving at extreme speed': FAA." newsweek.com
- Willamette Week. "A Recent Report of Strange Lights Illuminates a Longer History of UFO Sightings in the Pacific Northwest." Jan. 14, 2025. wweek.com
- Grants Pass Tribune. "Pilots Report UFO Sightings Near Eugene, Oregon: Unidentified Lights and Strange Maneuvers." grantspasstribune.com
- Metabunk. "Oregon UFO Lights seen by pilots [Starlink]," thread 13825, Dec. 2024 (posts by flarkey, Dec. 9 and 14, 2024; pilot statements quoted from Reddit and direct messages; ATC transcription). Sitrec and ADS-B analysis. metabunk.org
- Acker, Lizzy. "‘You are cleared … to avoid the UFO’: Pilots report unidentified lights over Oregon." OregonLive, Dec. 13, 2024 (republished by the Anchorage Daily News). adn.com
- Reilly, Patrick. "Pilots report mysterious lights ‘moving at extreme speeds’ across Oregon skies as drone sightings baffle New Jersey." New York Post, Dec. 13, 2024 (citing KGW). aol.com
- Buettner, Douglas J., Richard E. Griffiths, Nick Snell & John Stilley. "Enhancing Space Situational Awareness to Mitigate Risk: A Case Study in the Misidentification of a Starlink Satellite ‘Train’ as Unidentified Aerial Phenomena." arXiv 2403.08155 (2024). arxiv.org
- NASA JPL Horizons, observer ephemeris (Moon), Dec. 8, 2024 04:30–05:00 UTC, near Corvallis, Oregon. ssd.jpl.nasa.gov
- FAA. Notice N 7210.970, "Unidentified Anomalous Phenomena (UAP) Activity," Sept. 25, 2025. faa.gov
- National UFO Reporting Center. Sighting database (report #184932 as previously cited; not re-checked). nuforc.org
- National UFO Reporting Center. "About Us" — organizational background on NUFORC and CTO Christian Stepien. nuforc.org
- Federal Aviation Administration. Notice N 7110.800 (listed as JO 7110.800), "Unidentified Anomalous Phenomena (UAP) Reports," Sept. 12, 2025; effective Oct. 26, 2025; since cancelled and incorporated into JO 7110.65. faa.gov
- All-domain Anomaly Resolution Office (AARO), U.S. Department of Defense. Official UAP investigation office. aaro.mil
- FlightAware. Aircraft registration record for N661LF, 2014 Pilatus PC-12/47E, Life Flight Network LLC. flightaware.com
- Life Flight Network. Organizational background, Oregon service area, and fixed-wing fleet. lifeflight.org
- Eugene Airport / Mahlon Sweet Field (KEUG). Airport identifier and location reference. en.wikipedia.org
- NewsNation. "UFO lights over Oregon allegedly encountered by pilots." newsnationnow.com
- Wikipedia. "2024 United States drone sightings" — background on the concurrent New Jersey/Northeast drone wave. en.wikipedia.org
- Military.com. "Drones, Planes or UFOs? Americans Abuzz Over Mysterious New Jersey Sightings." Dec. 14, 2024. military.com
- Wikimedia Commons. "Eugene skyline.jpg," photographed by Jsayre64, Dec. 23, 2005 (CC BY-SA 3.0). commons.wikimedia.org
Corrections (October 2026)
A review of the original news reports, the Metabunk thread and the FAA notices found that earlier versions of this page overstated the case. Key changes: Buley was not an independent witness to United 1596; he heard its report on the frequency before seeing lights. The medevac crew's phone video was released, and Metabunk analysts matched it (as well as a United flight-deck photo) to predicted Starlink flares. The page had said only one photo was matched. Buley's accounts of a TCAS target are inconsistent, and he told an analyst he did not think he saw the red light move on TCAS. The page had presented the TCAS return of the red light as established. The "60 to 80 percent" confidence attributed to Douglas Buettner was not found in any source; he said "most likely." The page had also said the FAA had no UFO procedure before 2025. In fact the controller manual then used the term "UFO," and N 7110.800 renamed it UAP.
Following this review, the rating was changed from Open 33 to Disputed 30 (October 28, 2026), because the higher rating had rested partly on claims corrected or removed above.
Other corrections: the United quote is "just straight west of Eugene... three or four targets... all altitudes up and down" ("up to the 50s" was not found). Buley described the lights as at least 20 miles away, not "one to five miles," and was cruising at 14,000–16,000 feet, not 7,000 feet, near Corvallis. "I know what that looks like" was not found; the Horizon quote is "No, it's not Starlink, I promise." The weather was mostly clear near Eugene at the time, not overcast with rain (ERA5 hourly). The Moon was about 44% lit and up in the southwest (JPL Horizons), not 39%. McMinnville is about 100 miles from Eugene, not "an hour's drive," and the per-capita NUFORC ranking claims were unsourced. Buley has flown since 2013, not necessarily with Life Flight since then. The Daily Mail citation was replaced with OregonLive, the New York Post/KGW and Buettner et al. (2024).
See something inaccurate? Have additional information or sources?
Suggest an Edit →Last Updated: October 28, 2026
