# The Lakenheath Radar Night [View on uap.fun]() CASE FILE 014 · 1956 Cold War radar rooms tracked impossible starts, stops, and turns. Then a Venom night fighter went up—and two versions of its encounter entered history. ![Illustration of a back-facing 1950s radar controller at a circular green scope, looking through windows toward a rural night airfield, a distant fighter silhouette, and unresolved points of light.]() Not a real photo. Maintained by uap.fun · Last updated at September 17, 2026 at 2:21 AM CDT. Sources reviewed September 17, 2026 · Reviewed annually or when significant Blue Book, RAF, radar, or aircrew records emerge. ## AT A GLANCE - **DATE:** August 13–14, 1956 - **LOCATION:** RAF Bentwaters and RAF Lakenheath, Suffolk, England - **REPORT TYPE:** Military radar-visual reports and fighter interception - **RECORD STATUS:** Unresolved; official radar-propagation finding remains disputed ## The story ### A telephone call about four-thousand-mile-an-hour targets On the clear night of August 13, 1956, radar operators at two American-tenanted RAF stations watched a routine shift fracture into a chain of extraordinary reports. Bentwaters Ground Controlled Approach called the Radar Air Traffic Control Center at Lakenheath, roughly forty miles to the northwest, and asked whether its scopes showed targets moving at about 4,000 miles per hour. The surviving records do not contain a radar film or plotter log from every station. What they preserve is a hurried sequence of operator estimates, visual reports, telephone relays, intelligence forms, and an interception order written into the machinery of Cold War air defence. Sources: [Teletype BOI-485]() · [The Lakenheath Radar/Visual UFO Case]() · [History, documents, and witness archive for the Lakenheath case]() ### The first tracks at Bentwaters The Bentwaters report begins between 21:20 and 22:00 Zulu. One return crossed the scope from east-southeast toward west-northwest at a speed estimated above 4,000 miles per hour. A second episode involved twelve to fifteen returns moving northeast, spreading across six or seven miles and apparently merging into one enormous blip before stopping, moving, and stopping again. A third fast return crossed east to west. Operators said the echoes resembled ordinary aircraft targets and that equipment checks disclosed no malfunction. Yet their speed calculations do not always agree with the stated ranges and sweep times, and Lakenheath did not report seeing these earliest tracks on its own scopes. Sources: [Air Intelligence Information Report IR-1-56]() · [Project Blue Book report: Bentwaters–Lakenheath, England]() · [The Lakenheath Radar/Visual UFO Case]() ### A star, a beacon, and an empty search Not every strange thing that night remained strange. Bentwaters tower chief Lawrence Wright watched an amber point low in the southeast for about an hour; its slow rise and changing colour fit Mars seen through thin cloud. First Lieutenants Charles Metz and Andrew Rowe searched from a T-33 for roughly forty-five minutes and found no unknown aircraft. They reported a bright star near the eastern horizon and the Orford coastal beacon flashing through haze. These identifications belong to the case rather than outside it: while radar operators were reporting dramatic tracks, a deliberate aerial search returned empty and at least one prolonged visual observation had an astronomical answer. Sources: [Air Intelligence Information Report IR-1-56]() · [Astronomical comments on the Lakenheath case]() · [History, documents, and witness archive for the Lakenheath case]() ### The white light over the field At 22:55 Zulu, the Lakenheath teletype records a new Bentwaters contact approaching from thirty miles east at an estimated 2,000–4,000 miles per hour. The return vanished two miles east of the station, reappeared three miles west, and continued off the scope. That gap might reflect the blind region above a ground radar or an anomalous return. The episode became harder to dismiss because the report paired it with two visual accounts: tower personnel said a bright light crossed east to west at tremendous speed near 4,000 feet, and the pilot of an aircraft at that altitude said a bright light streaked beneath him. The record asserts simultaneity, but supplies no names, signed aircrew statement, radar photograph, or precise visual geometry for independent reconstruction. Sources: [Teletype BOI-485]() · [Case 2: Lakenheath, England]() · [The Lakenheath Radar/Visual UFO Case]() ### The target that stopped southwest of Lakenheath After the warning call, Lakenheath controllers searched with moving-target indication engaged. They reported an echo twenty to twenty-five miles southwest that appeared stationary even though the filter should have suppressed very slow ground returns. A second radar set reportedly confirmed it at the same location. The target then moved north-northeast at a calculated 400–600 miles per hour, halted for several minutes, and set off again without a visible build-up of speed. Other returns appeared nearby, while ground observers described small white lights that stopped, turned, and diminished to points. The teletype treated radar and visual observations as mutually reinforcing; later reviews found their timing and identity much less secure. Sources: [Teletype BOI-485]() · [The Lakenheath Radar/Visual UFO Case]() · [History, documents, and witness archive for the Lakenheath case]() ### A Venom enters the story An RAF de Havilland Venom night fighter was scrambled from Waterbeach. In the contemporary American teletype, controllers first vector it toward a target six miles east of Lakenheath. The pilot reportedly sees a bright white light, loses it, and is directed toward another return. He then reports radar contact and a lock. As the fighter passes, the ground scope appears to show the unknown slipping behind it. The pilot allegedly acknowledges the pursuit, circles without shaking the target, asks for assistance, and calls it the clearest radar target he has ever seen. A second Venom launches; the first returns low on fuel, the second makes no contact, and all remaining targets disappear by about 03:30 Zulu. Sources: [Teletype BOI-485]() · [Case 2: Lakenheath, England]() · [The Lakenheath Radar/Visual UFO Case]() ### The aircrew remembered a different interception Decades later, researchers located members of the 23 Squadron crews. Navigator John Brady’s log and recollection place his scramble near 02:00. He remembered three or four passes at roughly 7,000 feet and a faint radar paint that seemed stationary. Pilot David Chambers saw nothing. Brady denied a gun lock, a visual sighting, violent evasion, or a ten-minute tail chase, and thought the return resembled a meteorological balloon with a radar reflector. A second crew also recalled an unimpressive stationary contact. Their testimony confirms that RAF fighters searched for something and obtained at least weak airborne-radar returns, but directly challenges the case’s most cinematic scene. Sources: [Interview with RAF navigator John Brady]() · [History, documents, and witness archive for the Lakenheath case]() · [Lakenheath–Bentwaters incident]() ### How one night became two incompatible classics The contradiction cannot be solved by quietly choosing the more dramatic version. The teletype was transmitted three days after the event and names the USAF controllers who supplied it, but its Venom dialogue was relayed from the ground rather than signed by the RAF aircrew. Brady and Chambers spoke forty-four years later, when memory had aged but personal logs helped identify the sortie. The Americans may have combined radio calls, scope interpretation, and separate targets into a pursuit narrative; the aircrew may have forgotten details; or more than one episode may have become entangled. The most defensible history keeps both records visible and refuses to promote reported gun lock into uncontested fact. Sources: [Teletype BOI-485]() · [Interview with RAF navigator John Brady]() · [History, documents, and witness archive for the Lakenheath case]() ### Blue Book closes the card; Colorado opens it again The Project 10073 record card grouped the Bentwaters and Lakenheath reports under anomalous propagation and warned that the radar, ground, and airborne observations could not be considered concurrent after the fuller Bentwaters report was reviewed. Twelve years later, the Air Force-sponsored University of Colorado study reached an unusually different tone. Radar specialist Gordon Thayer called Lakenheath the most puzzling case in the radar-visual files and considered a mechanical device of unknown origin the most probable reading, while explicitly allowing for witness fallibility and conventional explanations. His analysis relied heavily on the contemporary messages and retired watch supervisor Forrest Perkins’s later letter—before the interceptor crews themselves were interviewed. Sources: [Project Blue Book report: Bentwaters–Lakenheath, England]() · [Case 2: Lakenheath, England]() · [The Lakenheath Radar/Visual UFO Case]() ![Scanned Project 10073 record card for the August 13–14, 1956, Bentwaters–Lakenheath reports, listing anomalous propagation and noting that the observations could not be treated as concurrent.]() The Project 10073 record card summarized roughly five hours of varied radar and visual reports, entered “anomalous propagation,” and cautioned that the observations were not demonstrably concurrent. U.S. Air Force, August 1956; public domain in the United States. Contrast was adjusted on the complete page for legibility without changing its content. [Image source]() [Public domain — U.S. federal government work]() ### Four ordinary explanations, none for the whole night The serious conventional case is a mosaic rather than one neat answer. Mars plausibly explains Wright’s long-lived southeastern light. Perseid meteors can explain brief streaks and were conspicuous that night, though Ian Ridpath noted that ordinary radar would not normally track their high ion trails. Balloons fit the slow cluster, prevailing winds, and the weak stationary returns recalled by the Venom navigators. Anomalous propagation or moving-target-indicator faults can create false, vanishing, or displaced echoes, especially the apparent gap over Bentwaters. These mechanisms substantially reduce the mystery, but no preserved meteorological profile, equipment fault report, balloon release record, and synchronized plot reconstructs every reported track. Sources: [Air Intelligence Information Report IR-1-56]() · [Interview with RAF navigator John Brady]() · [Astronomical comments on the Lakenheath case]() ### What remains on the green scope Lakenheath–Bentwaters endures because it is both stronger and messier than its legend. Military personnel filed prompt reports; separate radar rooms were involved; aircraft actually launched; and the Air Force preserved a substantial file. But the speeds were scope estimates, the visual-radar matches were asserted rather than instrumentally synchronized, and the famous chase is contradicted by the crew most likely to have flown it. The case is not a clean demonstration of an impossible machine. It is a night when genuine air-defence work, atmospheric and astronomical clutter, weak radar contacts, institutional relay, and unresolved observations became inseparable—and when the archive itself began telling two stories. Sources: [Project Blue Book report: Bentwaters–Lakenheath, England]() · [Case 2: Lakenheath, England]() · [History, documents, and witness archive for the Lakenheath case]() ## The evidence ### The contemporary documentary spine The strongest evidence is documentary: IR-1-56 from Bentwaters, BOI-485 from Lakenheath, later Air Force analyses, and the Project 10073 record card. They establish that military controllers reported unusual returns, that visual reports entered official channels, that aircraft searched, and that the incident received technical review. They do not include preserved raw radar film, photographs of an object, cockpit recordings, physical material, or a complete set of signed RAF statements. Sources: [Project Blue Book report: Bentwaters–Lakenheath, England]() · [Air Intelligence Information Report IR-1-56]() · [Teletype BOI-485]() ### Radar redundancy with imperfect synchronization The case’s evidential appeal rests on apparently corresponding returns from Bentwaters GCA, Lakenheath traffic-control and approach radars, and a Venom’s airborne set. Redundancy matters only when contacts can be matched in time, position, and motion. The surviving narrative says several observations corresponded, but the official card cautions that they were not all concurrent, the earliest Bentwaters tracks were not seen at Lakenheath, and no common data recording survives. Multiple radars therefore strengthen the reality of reported anomalies without proving that every scope displayed one physical object. Sources: [Project Blue Book report: Bentwaters–Lakenheath, England]() · [The Lakenheath Radar/Visual UFO Case]() · [History, documents, and witness archive for the Lakenheath case]() ### The pursuit is disputed at its source The tail-chase account is contemporary but secondhand: USAF controllers described what their scope seemed to show and what they believed the RAF pilot said. Brady’s later first-person account accepts a weak radar contact but rejects the visual sighting, gun lock, evasive pursuit, and quoted dialogue. This conflict cannot be resolved from the available record. The archive supports an interception and radar search; it does not support presenting an intelligent chase as an uncontested event. Sources: [Teletype BOI-485]() · [Interview with RAF navigator John Brady]() · [History, documents, and witness archive for the Lakenheath case]() ### The conventional case is cumulative Mars, the Perseids, balloons, radar blind zones, anomalous propagation, and possible moving-target-indicator behavior each fit portions of the reports. The strongest specific match is Mars for the hour-long southeastern light; the aircrew’s balloon comparison is important for the later weak airborne returns. The weakest version of skepticism is that one meteor shower explains every visual and radar event. A cumulative ordinary explanation remains plausible, but it is a retrospective fit assembled without the synchronized instrument data needed to test it decisively. Sources: [Air Intelligence Information Report IR-1-56]() · [Interview with RAF navigator John Brady]() · [Astronomical comments on the Lakenheath case]() ### Classification This file is classified here as an unresolved military radar-visual episode with a disputed official anomalous-propagation finding. “Unresolved” reflects the inability to reconstruct all reported returns and visual observations from surviving data. It does not mean that the reported speeds, stops, or pursuit are verified performance characteristics of a craft. The best-documented conclusion is narrower: trained personnel encountered a confusing series of radar and visual events, and later investigators and participants disagreed sharply about what happened during the interception. Sources: [Project Blue Book report: Bentwaters–Lakenheath, England]() · [Case 2: Lakenheath, England]() · [Interview with RAF navigator John Brady]() ## Timeline - **13 AUG 1956 · ABOUT 9:20–10:00 PM Z:** Bentwaters GCA reports several episodes: fast individual returns and a slower cluster of twelve to fifteen echoes apparently merging, stopping, and moving away. - **SAME PERIOD:** Tower chief Lawrence Wright watches an amber star-like light in the southeast; a T-33 crew searches for about forty-five minutes, finds no unknown aircraft, and notes a bright star and the Orford beacon. - **10:55 PM Z:** A later Bentwaters return crosses east to west; the Lakenheath teletype pairs it with reports of a bright light from the tower and an aircraft overhead. - **SHORTLY AFTER 11:00 PM Z:** Bentwaters alerts Lakenheath. Controllers there report a stationary echo southwest of the station, confirmation on a second set, and subsequent start-stop motion. - **14 AUG · AFTER MIDNIGHT:** Ground personnel report white lights while Lakenheath continues tracking intermittent returns; the exact correspondence between visual and radar events remains uncertain. - **ABOUT 2:00 AM Z:** The first 23 Squadron Venom launches from Waterbeach. The U.S. teletype later describes a white light, radar lock, and tail chase; the aircrew later recalls only faint stationary radar paint and no visual pursuit. - **ABOUT 2:40 AM Z:** A second Venom takes over the search, obtains another weak contact according to later crew testimony, and returns without identifying an object. - **ABOUT 3:30 AM Z:** The final reported targets disappear from the Lakenheath scopes; no object, image, radar film, or physical trace is recovered. - **16–31 AUG 1956:** Lakenheath transmits BOI-485 three days after the incident; Bentwaters completes IR-1-56 after interviewing radar operators, tower personnel, weather staff, and the T-33 crew. - **1968–1971:** The University of Colorado study and Gordon Thayer’s later AIAA article turn the once-classified incident into a landmark radar-visual case while acknowledging conventional possibilities. - **1978–2001:** Additional controllers and, eventually, the Venom aircrews are identified. Their accounts confirm an interception but fracture the famous pursuit narrative and reopen the balloon and radar-anomaly questions. ## Sources & interviews - [Project Blue Book report: Bentwaters–Lakenheath, England]() — U.S. Air Force · August 1956 · 44-page case file via Wikimedia Commons - [Air Intelligence Information Report IR-1-56]() — 81st Fighter Bomber Wing, U.S. Air Force · August 31, 1956 · Verbatim archival transcript - [Teletype BOI-485]() — 3910th Air Base Group, U.S. Air Force · August 16, 1956 · Verbatim archival transcript - [Case 2: Lakenheath, England]() — University of Colorado Scientific Study of Unidentified Flying Objects · Gordon D. Thayer · 1968 · NCAS edition - [The Lakenheath Radar/Visual UFO Case]() — Gordon D. Thayer · Journal of Astronautics and Aeronautics · September 1971 · Preserved transcription - [History, documents, and witness archive for the Lakenheath case]() — David Clarke, Andy Roberts, Martin Shough, and Jenny Randles · Documentary research archive - [Interview with RAF navigator John Brady]() — David Clarke and Andy Roberts · February 11, 2001 · Transcript - [Astronomical comments on the Lakenheath case]() — Ian Ridpath, with British Astronomical Association meteor data · January 2001 - [Project BLUE BOOK — Unidentified Flying Objects]() — U.S. National Archives · Program records and Air Force fact sheet - [65 years of USAFE and RAF Lakenheath: Heritage to horizons]() — U.S. Air Force · RAF Lakenheath official history - [Lakenheath–Bentwaters incident]() — Wikipedia · Orientation and reference trail · Consulted September 17, 2026 - [RAF Bentwaters]() — Wikipedia · Airfield orientation and reference trail · Consulted September 17, 2026 - [RAF Lakenheath]() — Wikipedia · Airfield orientation and reference trail · Consulted September 17, 2026 - [RAF Bentwaters media category]() — Wikimedia Commons · Historical-media and licensing search · Consulted September 17, 2026 - [RAF Lakenheath media category]() — Wikimedia Commons · Historical-media and licensing search · Consulted September 17, 2026 ## A NOTE ON EVIDENCE Unidentified describes a limit of the available information. It doesn’t identify an origin. [NEXT CASE FILE: The Nimitz Encounter]()