This is an attempt to unscramble the maze of accounts the page author has encountered concerning the August 13-14, 1956
RADAR-Visual UFO case at Bentwaters and Lakenheath air bases, in England. The following chart attempts to correlate the
various accounts. Note that each sighting could have a different cause, and may be unrelated to any of the other sightings.
The separate sightings are identified by [number]
The accounts are identified and color-coded as follows:
- (C) Scientific Study of Unidentified Flying Objects - Edward U Condon et al
- (K) UFOs Identified - Philip J Klass
- (M) Science in default - James McDonald (UFOs - A scientific Debate - Sagan + Page)
- (H) The Hynek UFO Report - J Allen Hynek
- (S) Encyclopedia of UFOs - Ron Story
- (B) UFO: The Government Files - Peter Brookesmith
- (R) Something in the Air - Jenny Randles
- (P) Phenomenon: Forty Years of Flying Saucers - Spencer & Evans
- (T) Summary Time Chronology - Larry Robinson (author of this page)
- (L) Comments - Larry Robinson
The Details of the Location, Date, and Time
(L) The Locations
As marked by the green markers on the map (G):
- A. RAF Bentwaters (RADAR site - also the location of Rendlesham Forest)
- B. RAF Woodbridge
- C. RAF Waterbeach (Venom fighters stationed here)
- D. RAF Lakenheath (RADAR site)
- E. RAF Sculthorpe
- F. RAF Neatishead
- London Airport - Another map length southwest of the southwest corner of the map
(L) Distances
The distances are straight line, center to center (Ignore the blue road direction lines).
- D. RAF Lakenheath to A. RAF Bentwaters: 43 miles, bearing 117°
- C. RAF Waterbeach to D. RAF Lakenheath: 17 miles. bearing 53°
(L) Dates and Times of Sightings
- Sightings began August 13, 1956, at 2130 Z (9:30 pm standard time, 10:30 pm British Summer Time)
- Sightings ended August 14, 1956, at 0330 Z (3:30 am standard time, 4:30 am British Summer Time)
[1] 2130 First Bentwaters RADAR sighting:
- (C) (Not included)
- (K) From 25-30 mi SE of Bentwaters, target took 295 heading, disappeared 15-20 mi NW of Bentwaters. Plots out
at > 5000 mi/hr. No visual. Second event in this account.
- (M) From 25-30 mi ESE of Bentwaters, target took 295 heading, faded 20 mi NW of Bentwaters. 4000 mi/hr cited.
End to end at 30 sec transit time gives 6000 mi/hr. Estimated 5-6 mi/sweep gives 9000 mi/hr. No visual.
- (H) (not included)
- (S) From 25-30 mi ESE of Bentwaters, target took 295 heading, faded 20 mi NW of Bentwaters. 4000 mi/hr
cited. No visual.
- (B) (not included)
- (R) Fast target from North Sea. Feared to be a Soviet invasion.
- (P) Vacasse Account: Target took 295 heading, faded 15-20 mi WNW of Bentwaters. 4500-5000 mi/hr.
5-6 mi/sweep. No visual.
- (T) Fast object from North Sea moved inland. Only RADAR.
- (L) Only RADAR!
- How did it disappear? No account is clear.
- Which speed (if any) is correct?
- The 9000 mi/hr figure implies 2 to 2.4 seconds per sweep. Notice that McDonald took the upper limit of the possible
distance covered to get 6000 mi/hr, not the lower limit of 40 miles, which gives 4800 mi/hr (closer to the estimate
cited).
- If the sweep rate is 10.66 seconds as given in [4] below, the speed is 1689 to 2026 mi/hr.
- If the alternate of 6.4 seconds is the sweep rate, the speed works out to 2812 to 3375 mi/hr.
- Radar sets had various sweep rates.
- A multiple-trip echo would divide the speed of the original object by the number of extra pulses.
- Since none of the other RADARs covering the area detected it, it was not a solid object, unless it was a
multiple-trip echo of a meteor.
[2] 2130-2155 Second Bentwaters RADAR sighting:
- (C) (not included)
- (K) From 8 mi SW of Bentwaters, 12-15 blips spread out over 50-60 mi. The cluster moved NE. When 14 mi NE
of Bentwaters, targets grew faint, then merged into one strong one, which alternately hovered and moved NE until it went
off screen at 60 mi. No visual. First event in this account.
- (M) From 8 mi SW of Bentwaters, 12-15 blips spread out. The cluster moved NE, preceded by 3 objects in a
triangle. When 40 mi NE of Bentwaters, targets grew faint, then merged into one strong one, which alternately hovered and
moved N until it went off edge of screen. No visual.
- (H) (not included)
- (S) From 8 mi SW of Bentwaters, 12-15 blips spread out. The cluster moved NE, preceded by 3 objects in a
triangle. When 40 mi NE of Bentwaters, targets grew faint, then merged into one strong one, which hovered 10 min, moved N
at 100 mph, hovered again, went N until it went off edge of screen. No visual.
- (B) (not included)
- (R) (not included)
- (P) Whenry account: From 8 mi SW of Bentwaters, 12-15 blips spread out. The cluster moved NE, preceded by
3 objects in a triangle, at 80-125 mph. When 45 mi NE of Bentwaters, targets merged into one strong one, which hovered
10-15 min, moved NE 5 mi, hovered again 3-5 min, went N until it went off edge of screen. No visual.
- (T) Cluster converged, moved NE.
- (L) Only RADAR!
- Interesting that the target spread was greater than the distance the cluster moved. This supports a multiple
reflection theory.
- Discrepancies among accounts in location of merge, and direction of disappearance.
- Only RADAR! Since none of the other RADAR sets covering the area detected these, they were not solid objects at the
locations reported.
- A possibility is a spurious effect in the MTI (moving target indicator) mercury delay line. The MTI was newly
installed.
- The new AGC circuit (Automatic Gain Control, installed with the MTI) could have amplified weak targets to
planelike blips if misadjusted.
- Another possibility is multiple echoes from moving corner-reflecting vehicles, such as railroad gondolas or
dump trucks.
2130-2230 T-33 (pilot trainer jet) planes hunt for objects:
- (C) American T-33 tried to intercept, found nothing.
- (K) Two T-33 planes searched for an hour, found nothing. Pilots saw bright star and Orford Ness
flashing beacon.
- (M) One T-33 searched and found nothing. No RADAR aboard. Saw star and lighthouse.
- (H) (not included)
- (S) One or two T-33 jet trainers made fruitless search.
- (B) (not included)
- (R) (not included)
- (P) One T-33 on training flight vectored to find these, found nothing.
- (T) One T-33 already in the air searched, saw only a star and the Orford Ness lighthouse.
- (L) No sightings!
- How many planes were there?
- Did any ground personnel see the planes?
- Note that the Lockheed T-33 was a training aircraft, intended to train pilots to fly jets. It carried no weapons.
[3] 2200 Third Bentwaters RADAR sighting:
- (C) (not included)
- (K) Object tracked from 30 mi E of Bentwaters to 25 mi W of Bentwaters. Sudden disappearance. Cited at
over 4000 mi/hr. Using 16 s transit time gives 12000 mi/hr.
- (M) Just like [1], except different heading.
- (H) (not included)
- (S) (not included)
- (B) (not included)
- (R) (not included)
- (P) Whenry account: Object tracked from 30 mi E of Bentwaters to 25 mi W of Bentwaters in 16 seconds. Over
4000 mi/hr. No visual.
- (T) High velocity. No visual.
- (L) Only-RADAR!
- T-33s did not see any objects.
- Neither did any other RADAR.
- This is either a multiple-trip echo of a meteor, or not a solid object.
First Bentwaters visual sighting:
- (C) (not included)
- (K) Staff supervisor saw light ESE 10 deg up (identified as Mars).
- (M) (not included)
- (H) (not included)
- (S) (not included)
- (B) (not included)
- (R) (not included)
- (P) Observer in the tower sighted object later identified as Mars.
- (T) Mars sighted.
- (L) This was part of the general confusion, and the page author does not count it as a UFO sighting.
[4] 2255 Fourth Bentwaters sighting:
- (C) Object tracked from 40 mi E of Bentwaters to 40 mi W of Bentwaters. Blurry yellowish light seen
heading SW by tower crew. Plane over Bentwaters at 5000 ft saw light go below plane heading W. Cited 2000-4000 mi/hr.
Reported as "size of a golf ball." Bentwaters or Sculthorpe alerted Lakenheath by direct telephone line.
- (K) (given as 2200, the time of third sighting) Object tracked from 30 mi E of Bentwaters to 25 mi W of
Bentwaters. Became weak and disappeared. 16 seconds total. Seen for only 3 sweeps. Bright light heading W seen by tower
crew. C-47 plane over Bentwaters at 4000 ft saw light go below plane heading W. Cited 4000 mi/hr. Lakenheath alerted.
- (M) Object tracked from 30 mi E of Bentwaters to 25 mi W of Bentwaters. Disappeared from RADAR while
within 3 mi of the station, then reappeared on other side, 3 mi away. Sudden disappearance. Blurry light heading W seen
by ground crew. C-47 over Bentwaters at 4000 ft saw light go below plane heading W. Cited 4000 mi/hr. No sonic boom.
Bentwaters alerts Lakenheath.
- (H) Object tracked from 30 mi E of Sculthorpe to 25 mi W of Sculthorpe. Blurry light seen by tower
crew. C-47 over Bentwaters at 4000 ft saw light go below plane. Sculthorpe says 4000 mi/hr.
- (S) Object tracked from 30 mi E of Bentwaters to 25-30 mi W of Bentwaters. Light seen by ground crew at
4000 ft. C-47 over Bentwaters at 4000 ft saw light go below plane. 2000-120000 mi/hr. Bentwaters alerts Lakenheath.
- (B) Object tracked from 30 mi E of Bentwaters to 25-30 mi W of Bentwaters. Weak return. Light seen by
ground crew. C-47 over Bentwaters at 4000 ft saw light go below plane. 2000-4000 mi/hr.
- (R) Object tracked over Rendlesham Forest and Bentwaters. Rapid fuzzy glow seen by tower staff. USAF
transport at 6000 ft saw light below. 2000-4000 mi/hr. Bentwaters called Lakenheath.
- (P) High velocity E to W. Light seen by ground observer at 4000 ft. C-47 over Bentwaters saw light below.
2000-4000 mi/hr. Bentwaters alerts Lakenheath. Lakenheath alerts Sculthorpe and Air Traffic Control.
- (T) High velocity light heading 270, Ground observer saw blurry yellow light. Light passed under C47.
No sonic boom. Bentwaters alerted Lakenheath. Lakenheath had no targets.
- (L) RADAR-Visual!
- This is the only sighting combining ground RADAR, ground visual, and air visual in the entire episode.
- More details are needed as to how long the light was in sight by each crew, and the manner of disappearance.
- Klass seems to have combined events [3] and [4] into one, at the time of event [3].
- If the object was seen for the duration of 2 sweeps (three blips), taking 16 seconds, it gives 8 seconds per sweep,
except that it crossed the center of the scope. Thus, the real time is 1.5 sweeps, giving 10.66 seconds per sweep.
- If a fencepost error occurred due to the language used, and the object was visible as 4 blips, and traveled in 2.5
sweeps, then it is 6.4 seconds per sweep.
- Will the real sweep rate of the Bentwaters RADAR please stand up? 2 seconds (from sighting [1]), 6.4 seconds, or
10.66 seconds? Only the 6.4-second sweep time makes sense in both sightings [1] and [4].
- How far away is this "golf ball" the size is compared to? At arm's length, or hit in the air? The form
says at arm's length, but too many people think of the object as being distant and in the sky when they fill this
out.
- Again, only one RADAR picked it up, making the RADAR sighting either a multiple-trip echo of a meteor or not a
solid object.
- Some confusion may result from the fact that "below" to a pilot does not mean "directly under",
but "lower than my wings".
- It is impossible to determine if the RADAR sighting and the two visual sightings were even of the same object.
- It is also impossible to determine if the two visual sightings were of the same object.
- Both the ground crew and the airplane crew were told where to look for a light. Thus, the "told where to
look" effect comes into play. They were told to look for lights, and they saw lights.
- It is not known how far these lights were from the observers, so the actual speeds of the objects seen in the visual
sightings can not be determined. The observers could only guess.
- Lakenheath switched to MTI at this time. This becomes important later.
[5] 2255 First Lakenheath visual sighting:
- (C) (not included)
- (K) (given at 2200, the time of third sighting) Lakenheath alerted by Bentwaters about sighting [4].
Ground crew sees light on SW heading (probably not the same light).
- (M) Bentwaters alerts Lakenheath about sighting [4]. Lakenheath ground observers see 2000 ft high light
from NE on SW heading (no RADAR sighting of this).
- (H) (not included)
- (S) (not included)
- (B) (not included)
- (R) Lakenheath ground personnel saw a light.
- (P) Ground observer at Lakenheath saw a light in the NE.
- (T) Ground observer saw white light on SW heading.
- (L) Visual Nocturnal Light!
- Obviously, the object sighted at Lakenheath was not the same object as was sighted at Bentwaters, unless everybody
had their compass directions wrong, or it was a high altitude meteor. [4] did not head toward Lakenheath, nor did [5]
come from Bentwaters. Also, the original Bentwaters object [4] would have been long gone by the time Lakenheath
received the message.
- Details are needed as to exactly when, and how long, the light was in sight by each crew.
- Not enough information to evaluate, but possible meteor.
[6] "Later" Visual observation at Lakenheath:
- (C) (not included)
- (K) (not included)
- (M) Low altitude object approaches from NE, stops, then leaves on E heading. No RADAR sighting.
- (H) (not included)
- (S) White light seen by Lakenheath ground observer stopped and changed course.
- (B) (not included)
- (R) (not included)
- (P) (not included)
- (T) Ground observer saw light change course.
- (L) Possibly an airplane.
[7] "Later" Visual observation at Lakenheath:
- (C) Ground observer saw one moving white light join up with another, they fly in formation. No RADAR
sighting.
- (K) (not included)
- (M) Two moving white lights merge into one. No RADAR sighting.
- (H) (not included)
- (S) Two white lights joined up.
- (B) (not included)
- (R) (not included)
- (P) (not included)
- (T) Ground observer at Lakenheath saw two lights rendezvous.
- (L) No bearings given.
- Could these have been T-33s or Venoms?
- Note that the British term "join up" means "rendezvous," not "merge."
[8] 0010 First Lakenheath RADAR sighting:
- (C) Stationary target 20-25 mi SW of Lakenheath on ATC RADAR. Target moved NNW to about 20 mi NNW of
Lakenheath and stopped. MTI was on when object stopped. GCA (ground control) alerted, had target in same place. It
then made several changes in location, with 3-6 min in between. All motion at 600 mi/hr. No visual.
- (K) Stationary target 6 mi SE of Lakenheath, then moved NE until it was 2 mi NW of Lakenheath. No visual.
MTI was on when object stopped.
- (M) Air Traffic Controls RADAR tracked object moving very slowly from 6 mi W of Lakenheath to 20 mi SW,
stopped 5 min. MTI was on when object stopped. GCA alerted, had target in same place. Moved NW until it was 2 mi NW of
Lakenheath. Made instantaneous starts and stops. Seen by ground personnel and both RADARs. GCA then observes 3-4 more
objects doing the same thing.
- (H) Air traffic control target 20-25 mi SW, stopped 20 mi NW. GCA RADAR had target in same place. Target
moved at 400-600 mi/hr. Instantaneous stops and starts. No visual.
- (S) Air traffic control and Ground Control independently have target 6 mi SW, went to 20 mi stopped
5 min. Went to 2 or 20 mi NW, and stopped on MTI. GCA RADAR had target in same place. Instantaneous stops and starts.
No visual. Sgt P says this was earlier.
- (B) (not included)
- (R) (not included)
- (P) Sgt Perkins account: All scopes switched to MTI before sighting. Received call from Sculthorpe.
GCA and ATC have target 20 mi SW. No visual. On MTI while stopped. ATC alerts GCA, target found in same place. Went
to 2 or 20 mi NE of Lakenheath, stopped. Continued to move and stop. Moved at 600 mi/hr. Instantaneous starts and
stops.
- (T) Target on two RADARs simultaneously. Target starts and stops.
- (L) Only-RADAR, or RADAR-Visual?
- No two of these accounts agree where it was or went. There must be typos in some of these, because endpoints and
direction of motion do not match. Only one account gives visual corroboration.
- This is the ONLY object seen by visually and by more than one ground RADAR location, (assuming that McDonald is
correct - no other account has the visual.)
- The call for the Venom was made at this time.
- Since MTI was used, this could be a spurious weather target amplified by the MTI and AGC. The additional GCA
observations tend to confirm this.
[9] Second Lakenheath RADAR sighting:
- (C) (not included)
- (K) Lakenheath ATC has a target making square turns 17 mi E of Lakenheath.
- (M) Lakenheath has a target making square turns 17 mi E of Lakenheath. Target on MTI when stopped.
600-800 mi/hr when moving.
- (H) (not included)
- (S) Lakenheath ATC has a target making square turns 17 mi E of Lakenheath. Target on MTI when stopped.
600-800 mi/hr when moving.
- (B) (not included)
- (R) (not included)
- (P) Lakenheath ATC has a target making square turns 17 mi E of Lakenheath. Target on MTI when stopped.
600-800 mi/hr when moving.
- (T) Target 17 mi E of Lakenheath, square turns.
- (L) Only-RADAR!
- How could they deduce it was making "square turns" from a RADAR updated every 15 seconds?
- This is probably a spurious weather or ground target amplified by the MTI and AGC.
[10] First (and only) Bentwaters-Lakenheath RADAR sighting:
- (C) (not included)
- (K) (not included)
- (M) Bentwaters has stationary MTI target 20-25 mi SW of Bentwaters. Lakenheath has it same place on
both scopes. Target moves at 600 mi/hr to 20 mi NNW of Bentwaters.
- (H) (not included)
- (S) (not included)
- (B) (not included)
- (R) (not included)
- (P) (not included)
- (T) Lakenheath and Bentwaters have target in same place?
- (L) Only-RADAR!
- This seems like a Bentwaters version of [8], but with the positions shifted to be relative to Bentwaters.
- Again, only one account gives this.
- This could be another spurious weather or ground target amplified by the MTI and AGC.
0040 First Venom fighter, approach #1:
- (C) After 35-45 min, Venom scrambled. Venom first detected 35 mi SW of Lakenheath.
- (K) Authorities decide to scramble. The Venom is a 2-seat airplane. The seats are for pilot and RADAR
operator. The pilot may have been operating the RADAR himself, without a RADAR operator. Venoms stationed at
Waterbeach.
- (M) Venoms stationed 20 mi SW of Lakenheath at Waterbeach. The Venom is a 1-seat airplane with a nose
RADAR. First plane detected by Air Traffic Control.
- (H) London 7th Air Division Command called, 3rd RAF command notified. After 30-35 min, 3rd AF decides
to scramble Venoms.
- (S) Chief Controller at Neatishead called. He scrambles Venoms. Venoms were 2-seat planes, fully manned,
stationed at Waterbeach, 20 mi away. Both Lakenheath and Neatishead controllers claimed they were controlling the
intercept.
- (B) The Venoms were 1-seat airplanes stationed at Waterbeach. Menzel erroneously said they were
2-seat.
- (R) The squadron leader Freddy Wimbledon's Account: Each Venom had both pilot and navigator, as confirmed
by the pilots and navigators.
- (P) Sgt. Perkins (ATC) called 7th Air Div London, 3rd Air Base Commander, and Air Command Commander.
They decide to scramble. Lt Wimbledon has command. Venoms were 1-seat jets with nose RADAR. Venoms were stationed at
Waterbeach, 20 mi SW of Lakenheath. First Venom was already in the air, detected 30 mi SW. Venom contacted ARC, then
switched frequency. Perkins not advised of frequency change.
- (T) Other bases alerted, Cmdr Wimbledon alerted. Scramble ordered. The Venom was a 2-seat plane,
fully manned.
- (L) CONFUSION!
- Is the base 20 mi, or 35 mi away? Or maybe the plane had to take off into the wind in a direction away from
Lakenheath? Or was the plane already in the air?
- How many seats are on these DeHavilland Venom fighters? There were one-seat versions and two-seat versions, as
indicated by various sources about this airplane.
- Was a RADAR operator present, or was the pilot operating the RADAR?
- Why did it take half an hour to scramble the Venom? This is a normal occurrence. Ignore it. Anyone expecting a
faster response is expecting a supercompetent military. And the Venom's engine had a complicated startup
procedure.
[11] 0100 First Venom, chase #1:
- (C) (Not clearly distinguished from second chase) Pilot saw light and target. The target did not move
during the intercept, until the target was lost 13 mi W of Lakenheath.
- (K) Venom vectored into target 6 mi E of Lakenheath. Pilot saw a light. Lost it 13 mi W of Lakenheath.
(Apparently, the Venom turned around in this account.)
- (M) Venom vectored to target 13 mi E of Lakenheath. Pilot saw white light. At 13 mi E of Lakenheath,
Venom suddenly lost target and light. (This implies the Venom had it on RADAR here.) Nobody knows what ground RADAR
saw in this account.
- (H) (not included)
- (S) ATC target 6 mi E of Lakenheath, vectored Venom in. Pilot saw light and target, lost it 13 mi W of
Lakenheath.
- (B) (not included) Notes that, according to Donald Menzel, the Venom RADAR had no gunlock capability.
- (R) The account of the airmen has the second Venom in this chase, at 0200 to 0230. Only RADAR contact.
No visual. The pilot radioed "Judy" (RADAR lock). Pilot overshot a stationary target.
- (P) ATC had target 6 mi E of Lakenheath. Neatishead also had target, and vectored Venom to it. Pilot saw
a light, got RADAR contact, radioed, "Judy" (RADAR lock). Pilot switched frequency to ATC, radioed, "I've
got my guns on him!" He suddenly lost target and light; radioed Lakenheath "Where did he go?"
- (T) The pilots said this was the second Venom, not the first, beginning at 0200. Note that the Venom
RADAR contact was along the same line of sight as the Lakenheath RADAR contact. The same anomalous propagation source
could cause both.
- (L) RADAR-Visual!
- What was the Venom doing for 20 minutes in the air before this intercept attempt?
- Are these all supposed to be accounts of the same event??? Which direction is which here? No two accounts agree.
- The Venom RADAR had a nasty habit of picking up ground targets.
- Did the Venom RADAR have gunlock capability?
- There was no height-finder in use on the ground RADAR.
- The RADAR images were not noticed on other RADARs.
- Anomalous propagation appears likely here. The visual light could have been anything: a ground light, a vehicle,
a ship, a star, or a plane. We have no solid record of how it was "lost" by the pilot.
[12] First Venom, chase #2:
- (C) UFO had to be between 15000 ft and 20000 ft to be on CPS-5 RADAR. The Venom had RADAR lock for 10 s,
15 mi SW of Lakenheath. When lock was broken, the CPS-5 RADAR showed the UFO to be following the Venom. The Venom
executed evasive maneuvers, but could not shake the object. Pilot requested to leave because fuel was low. As Venom left,
UFO stopped 10 mi S of Lakenheath. The pilot told the second Venom's pilot "I saw something, but I don't know what
it was." Target then moved N, leaving the area. It was lost on RADAR at 50-60 mi as though it were below
5000 ft.
- (K) Venom vectored into a target 10 mi E of Lakenheath. Pilot got "RADAR lock" for 10 s.
Controllers saw object circle around behind Venom on CPS-5, but pilot did not see this. Venom made evasive maneuvers,
but object stayed with it. Pilot left area due to low fuel. Object followed Venom only a short distance. The Venom
has no fire control.
- (M) Venom vectored into target 10 mi E of Lakenheath. Plane RADAR locked on. The lock was lost, and ground
RADAR told the Venom it passed the target. The target then was always behind the Venom on ground RADAR, no matter what
maneuvers the plane did. No documentation of how the pilot knew the object was behind him (tail RADAR speculated).
Plane low on fuel. Object followed Venom only a short distance after he received permission to return to base. As plane
left, the pilot told the second Venom's pilot "I saw something, but I don't know what it was."
- (H) The pilot, vectored into the object by the tower, radioed back "Got my guns locked on
him!" A few second later, he said, "Hey! Where did he go?" The controller responded, "He got behind
you!" The ATC Sgt didn't see this, but others saw the target circle behind the plane. Pilot used evasive maneuvers to
try to shake the target for 10 min. The target stopped 10 mi S of Lakenheath as the pilot returned to base.
- (S) The pilot, vectored into stopped target 10 mi E of Lakenheath, radioed back, "Judy"
(RADAR lock). A few second later, he said, "Lost target. More help." The controller responded, "He got
behind you!" The target circled behind the plane. Pilot used evasive maneuvers to try to shake the target for 10 min.
Then the pilot elected to return to base. Pilot claimed the target was the clearest target he ever saw.
- (B) The Venom pilot had visual and RADAR contact. The UFO flipped and got behind the Venom. The pilot was
unable to shake it off.
- (R) The pilots said this was the second Venom, not the first. The target never moved at speed. The
Venom kept circling, trying to find the object. The target did not chase the plane. The pilot continued until low on
fuel.
- (P)The chase continues from the previous (P) entry. The pilot changed to the Neatishead frequency, and
radioed, "Lost target. More help!" The Neatishead controller saw the object circle behind the Venom, and radioed
the Venom that this happened. The Venom continued to try to evade the object for 10 minutes. After the first 5 minutes,
the pilot changed to the Neatishead controller. Neatishead cancelled the second scramble, as the first pilot elected to
return to base.
- (T) The pilots said this was the second Venom, not the first. Apparently, the Venom passed the object,
and then kept circling, while the controller kept mixing up the two targets. The pilot kept switching frequencies,
confusing the controllers.
- (L) Only-RADAR, or RADAR-Visual?
- One account gives the minimum height as 15000 ft, another as 1500 ft. Obviously, the 15000 is in error, because a
target is said to normally fade out at 5000 ft at a greater range, giving a minimum height anomaly.
- There was no height-finder in use on the ground RADAR.
- Automatic fire control was never available for or installed on a Venom. The RADAR gunsight could not
"lock on" to a target.
- The Venom had no tail RADAR. Did the pilot rely solely on ground RADAR to tell where the target was? Or was he
running from a light?
- Since the altitude is not known, the Venom could have missed an aerial object vertically by as much as three
miles.
- It is impossible for the CPS-5 to show a "rapid circling."
- It was impossible in MTI mode for the CPS-5 operators to tell which blip was the Venom and which was the UFO.
- The pilot kept switching frequencies, confusing the RADAR men. Each thought he was exclusively controlling the
intercept (explaining the claims of the controllers). And it might have confused the pilot worse, if one controller
was pegging the wrong target as the Venom.
- The fuel load of a Venom should have lasted much longer. Either it was poorly prepared before the flight, or the
pilot wanted an excuse to break off the chase. But if the Venom had already been airborne, it might either have used part
of its fuel, or have been filled for only a short flight.
- The accounts seem to indicate that the pilot was quite frightened. This could have caused the pilot to assume more
was going on.
- Can we ever know exactly what happened here? No information as to flight direction or distance is given for the
evasive maneuvers.
Second Venom:
- (C) Second Venom never arrived due to engine trouble. Was never on Lakenheath RADAR.
- (K) Second Venom broke off due to engine trouble.
- (M) Second Venom found nothing.
- (H) Second Venom was never on Lakenheath RADAR. Returned due to engine trouble.
- (S) The target disappeared by going up or down. Second Venom scramble cancelled due to lack of target.
- (B) A second Venom and two T-33s joined the chase. Nothing was found.
- (R) The pilots said this Venom flew first. The pilot saw nothing at all, circled until he was low on fuel,
and returned to base. There was no malfunction.
- (P) The target went N at 600 mi/hr, disappearing at 60 mi N of Lakenheath. The second Venom was scrambled,
but was recalled to the base by Neatishead.
- (T) For one of the various reasons given, the second Venom found nothing.
- (L) No sighting.
- The account of the pilots with the two flights interchanged could be due to delays in filling out the logs. Or it
could be that one pilot used British Summer Time (the equivalent of daylight-saving time)
in his report, instead of military time.
- The disappearance of the target by rising or falling is a guess. It could have faded due to an MTI-enhanced weather
target dissipating. Or a ground object with a corner reflector (a dump truck?) could have been moved so the corner
reflector was no longer facing in the direction of the RADAR set.
- The accounts even differ on why this plane returned to base.
- The reported behavior of the target matches that of anomalous propagation.
0330 The end of the event:
- (C) All unidentified targets gone by 0330. Other aircraft were properly detected during the event.
- (K) All targets gone by 0330.
- (M) Unidentified targets persisted until 0330.
- (H) The controller in the 1967 Kincheloe AFB case was Perkins. All targets gone by 0330.
- (S) Targets persist until 0330 or 0230, depending on account. (British Summer Time??)
- (B) (not included).
- (R) Ely (Cambridgeshire) civilians reported a plane and one yellow or white light.
- (P) Ely citizens saw a light and an airplane.
- (T) Most accounts agree that the event ended at 0330.
- (L) Time errors.
- The doubts in some of the times might be caused by people using British Summer Time instead of military time.
- No time is given for the Ely visual sightings.
(L) Notes about RADAR:
Here is a look at what really happens in a RADAR set of 1956 vintage. The sequence of events given is for one single
pulse sent out by the transmitter:
- The blanking circuit locks off the electron beam in the display tube, and the receiver input is muted to prevent
damage during transmitter operation.
- The sweep circuits return the electron beam position to the center of the display tube.
- The transmitter sends out the pulse. It moves away from the RADAR antenna at the speed of light (186000 mi/s or
300000 km/s).
- The sweep circuits start moving the electron beam away from the center of the display in the direction the antenna
is pointing.
- The receiver is enabled, and the blanking circuits enable the electron beam.
- As the sweep moves away from the center, the weak electron beam leaves the visible line that is seen to be slowly
rotating around the tube as the antenna rotates.
- The transmitted pulse strikes a target (if present), and part of it is reflected back to the antenna. The time it takes
for the pulse to make the round trip determines the distance from the RADAR set.
- The receiver picks up and amplifies any returning echo (if present).
- If the MTI is on, the echo is amplified further and clipped, then fed to a gating circuit that decides whether or not
an echo is there.
- The resulting signal is fed to the display driver. If the MTI is on, the signal is also fed to the mercury delay line.
The delay line is adjusted to delay any signal fed into it for exactly the time between transmitter pulses.
- The display driver strengthens the electron beam in the display tube whenever it receives an echo signal. If the MTI
is on, a delayed echo from the previous pulse will shut off the electron beam for an instant, canceling out any echoes
received at the same location as the delayed echo.
- The strengthened electron beam makes a much brighter spot on the display tube. The brighter spot persists much longer
on the slow-decay phosphor coating than the weak sweep line does. It will usually persist for several rotations of the
antenna before the phosphor loses all of its energy.
- Any further echoes received by the antenna are handled in the same way as the electron beam continues to move out
toward the edge of the display tube.
- During all of this, the antenna and the sweep coil have rotated a very small fraction of a degree.
- When the beam reaches the edge of the tube, the whole process repeats. Any echoes from the pulse just transmitted that
are received after this point are treated as though they came from the next pulse. These are called second-trip echoes.
Those received after several pulses have been sent are called multiple-trip echoes.
Thus, the RADAR set determines the location of an object by using two values: The direction the antenna was pointing when
the echo was received, and the time since the last pulse was transmitted. Of course, extraneous signals, such as those
abnormally ducted from distant RADARs, second-trip and multiple-trip echoes, multiply reflected echoes, and electronic noise
can also be displayed just as though they were valid echoes. The MTI clipping and gating makes these spurious signals seem
as strong as real echoes from planes. A misadjusted AGC can amplify these effects.