Within Virginia UFOs
Did Pilots and Radar Track the Same Objects?
Pilot testimony and Washington-area radar reports made July 1952 the most important early chapter in Virginia's UFO history.
On this page
- The Nash Fortenberry flight near Norfolk
- Washington National Airport's radar reports
- What the surviving evidence can and cannot prove
Page outline Jump by section
Introduction
In July 1952, Virginia became part of one of the defining episodes of early American UFO history. On 14 July, Pan American Airways pilots William Nash and William Fortenberry reported eight glowing objects manoeuvring below their DC-4 near Norfolk and the Chesapeake Bay. Five days later, air-traffic controllers at Washington National Airport in Arlington began tracking unexplained targets around the capital, with further radar and visual reports appearing the following weekend.
The incidents are often joined into a single dramatic story, but the surviving evidence does not show that the pilots and radar operators tracked the same objects. They occurred on different nights, roughly 130 miles apart, and no radar return is known to have accompanied the Nash–Fortenberry observation. Their importance lies instead in the pattern: experienced aviation personnel, busy Virginia-linked airspace and official investigators all became involved during an exceptional national wave of reports. The testimony is substantial enough to resist easy dismissal, but the absence of photographs, preserved radar data and reliable distance measurements prevents a firm conclusion.
The Nash–Fortenberry flight near Norfolk
At about 9.10 pm on 14 July 1952, Nash and Fortenberry were flying a Pan American DC-4 southwards at approximately 8,000 feet. Their route took them over the Chesapeake region towards Norfolk, with Newport News and Hampton Roads visible below. Both men later said that they noticed a reddish glow ahead and to their right, initially resembling the reflection of a distant town. The glow separated into six apparently circular objects arranged in formation, followed shortly afterwards by two brighter objects that joined them.[NICAP]nicap.orgUFO ReportJuly 14, 1952; 20-25 miles N. of Norfolk, Va (BBU 1444) [CCL Item #24]… Objects approached head on at high speed estimated at about 12…
The pilots described the objects passing beneath their aircraft, apparently silhouetted against the darker water or ground. According to their reconstruction, the formation then made a sharp reversal and departed towards the Newport News area. Nash and Fortenberry emphasised that the lights appeared to have definite edges rather than the diffuse appearance of searchlights or reflections. The entire close observation lasted only seconds, although they continued watching the lights as they receded.[NICAP]nicap.orgUFO ReportJuly 14, 1952; 20-25 miles N. of Norfolk, Va (BBU 1444) [CCL Item #24]… Objects approached head on at high speed estimated at about 12…
They reported the encounter by radio soon afterwards, asking that a message be forwarded to the military. Their initial wording was comparatively restrained: two pilots had observed eight unidentified objects near Langley Field, apparently travelling above 1,000 mph at an estimated altitude of 2,000 feet. The crew then attempted to reconstruct the sighting while details were still fresh. Air Force investigators interviewed Nash and Fortenberry separately after they landed in Miami, comparing their accounts and map markings before questioning them together.[NICAP]nicap.orgnash-tulien…
That prompt reporting is one reason the case has remained prominent. The witnesses were not casual observers trying to identify a distant point of light. They were commercial aviators accustomed to judging aircraft, navigation lights and relative motion. Both also had naval aviation backgrounds. Their separate accounts were reportedly consistent on the central features: the number of objects, reddish-orange illumination, formation movement and abrupt change of direction.[NICAP]nicap.orgnash-tulien…
Credible witnesses, however, cannot automatically supply accurate measurements. The pilots had no instrument reading for the objects’ altitude, range, dimensions or speed. Their more spectacular later estimates—including enormous size and velocities of many thousands of miles per hour—were calculations built upon assumed distance and scale. A small nearby light and a large distant object can occupy the same apparent angle, so an error in the original range estimate would greatly alter every derived figure.
Were there supporting witnesses?
Later accounts frequently state that several people on the ground reported similar red objects around Hampton Roads that evening. The best-known example is a naval officer who wrote to the Virginian-Pilot, describing eight red lights near Point Comfort about 15 minutes before the airliner encounter. Other reports were said to have been discussed by investigators, but much of this material survives through newspaper correspondence and private UFO archives rather than complete, traceable Air Force case files.[NICAP]nicap.orgnash-tulien…
These reports modestly strengthen the possibility that unusual lights were visible in the wider region. They do not provide decisive corroboration of the pilots’ formation. The reported times, positions and movements are not precise enough to establish that separate witnesses observed one common set of objects. Nor is it always clear whether accounts were recorded independently before publicity about the Pan American sighting could influence descriptions.
The distinction matters. Several people reporting reddish lights on the same evening is more interesting than a wholly isolated cockpit observation. It is still not the equivalent of triangulation, in which observers at known locations record simultaneous bearings that establish an object’s position and altitude.
Washington National Airport’s radar reports
The Washington radar events began during the night of 19–20 July, five days after the Norfolk encounter. Washington National Airport—now Ronald Reagan Washington National Airport—stands in Arlington, Virginia, directly across the Potomac from Washington. That location gives the nationally famous “Washington UFO flap” an important Virginia connection: some of its central observations occurred inside National Airport’s air-traffic-control facilities.
Shortly before midnight, controller Edward Nugent noticed several unidentified returns on a radar display. His supervisor, Harry Barnes, and other controllers examined the targets and reportedly checked that the equipment was operating normally. A separate radar in the airport control tower was also said to show unusual returns. The targets appeared intermittently at different points around the capital rather than following ordinary airway patterns.[Wikipedia]Wikipedia1952 Washington, D.C., UFO incidentMarch 14, 2007 — At 11:40 p.m. on Saturday, July 19, 1952, Edward Nugent, an air traffic controller at Washington National Airport, spott…
Controllers contacted nearby military and aviation facilities, including Andrews Air Force Base in Maryland. Some unusual returns were reported there as well, although the observations across the different radar sets were not always simultaneous or identical. Commercial pilots were asked to look for lights, and several people reported seeing isolated bright objects. One Capital Airlines pilot described lights that appeared to move rapidly, while other crews saw nothing where radar operators suggested a target should have been.[Wikipedia]Wikipedia1952 Washington, D.C. UFO incident1952 Washington, D.C. UFO incident
A similar episode developed on 26–27 July. Interceptor aircraft were sent towards reported targets, but the results were inconclusive. Radar returns sometimes disappeared as fighters approached and reappeared after they moved away, a sequence that encouraged speculation that intelligently controlled objects were reacting to the aircraft. Yet the pilots obtained no sustained close visual encounter comparable to the Nash–Fortenberry report, and no interceptor returned with photographs, gun-camera film or a confirmed airborne radar lock on a physical craft.
Contemporary accounts are commonly described as “radar-visual” evidence, but that phrase can imply more than the records demonstrate. Radar operators saw unexplained returns, and witnesses saw unexplained lights during the same general periods. In some instances, reported directions appeared broadly compatible. The surviving documentation does not provide a continuous, time-synchronised record proving that a particular light and a particular radar return were one object.
What did the investigations conclude?
The Washington events created an immediate political and public-relations problem. Reports had apparently entered sensitive airspace around the national capital during a period of intense Cold War anxiety. President Harry Truman sought an explanation, and on 29 July Major General John Samford, the Air Force’s director of intelligence, led a large Pentagon press conference. He acknowledged that credible people sometimes reported remarkable things but said there was no evidence of a threat to the United States.[Wikipedia]Wikipedia1952 Washington, D.C. UFO incident1952 Washington, D.C. UFO incident
The principal official explanation was anomalous radar propagation associated with atmospheric inversions. Normally, radar energy travels in broadly predictable paths. Sharp changes in temperature or humidity can bend the beam towards the ground, allowing it to reflect from buildings, terrain or other surface features and return as misleading targets. Such returns may appear, vanish or move as atmospheric conditions change. Astronomer Donald Menzel later argued that this mechanism could account for much of the Washington radar activity, while stars, meteors and distorted lights could explain at least some visual reports.[Project Gutenberg]gutenberg.orgThe World of Flying Saucers, by Donald H. Menzel and Lyle G. Boyd—A Project Gutenberg eBook…
The inversion explanation is technically plausible and was supported by weather conditions favourable to unusual propagation. It also fits some awkward features of the reports: intermittent targets, inconsistent detections between installations and failures by aircraft to locate solid objects at the indicated positions. Radar in 1952 was indispensable but far less capable of automatically filtering weather, ground clutter and anomalous propagation than modern systems.
It was not universally convincing. Edward Ruppelt, who headed Project Blue Book during the period, later argued that inversions were common around Washington during that summer whereas the striking targets appeared on only a few nights. He also believed that experienced controllers could often distinguish familiar weather-related returns from aircraft-like targets. His memoir nevertheless records other cases in which trained pilots and radar crews were sincerely misled by balloons, astronomical objects or unusual propagation, demonstrating that expertise reduced error without eliminating it.[Wikisource]en.wikisource.orgOpen source on wikisource.org.
The events also increased Central Intelligence Agency interest in UFO reporting. An official CIA history states that the exceptional volume of reports in 1952, particularly the Washington incidents, raised concerns not simply about mysterious objects but about national defence systems being overwhelmed by reports, public alarm or deliberate deception. The resulting Robertson Panel met in January 1953 and concluded that UFO reports showed no direct evidence of a national-security threat. It recommended reducing public fascination with the subject because mass reporting could burden communications and obscure genuine hostile activity.[CIA]cia.govDOC 0005517742CLA's Role in the Study of UFOs, 1947-90The first report of a "flying saucer" over the United States came on 24 June 1947, when Kennet…
That policy legacy is part of why the Washington cases remain controversial. Supporters see the panel’s emphasis on “debunking” as evidence that officials became more concerned with managing belief than resolving difficult cases. A less conspiratorial reading is that defence agencies, facing thousands of low-quality reports during the Cold War, prioritised false-alarm control over open-ended scientific investigation. Both interpretations recognise the same underlying weakness: the evidence gathered in 1952 was too fragmented to settle the physical cause.
Did pilots and radar track the same objects?
There is no documented chain connecting the Nash–Fortenberry objects to the Washington radar targets. The cases were separated by five days, substantial distance and different types of evidence. Norfolk supplied a close-looking visual report without known radar confirmation. Washington supplied multiple radar returns and scattered visual observations, but no comparably detailed view of structured objects.
Their association is therefore historical rather than evidential. Both occurred during the extraordinary summer 1952 reporting wave; both involved professional aviation witnesses; and both lay within the linked Chesapeake–Washington air corridor. The Norfolk report also emerged near Langley Air Force Base and the major military concentration of Hampton Roads, while the Washington returns appeared around some of the country’s most sensitive airspace. That combination ensured intense attention even though the individual incidents did not directly corroborate each other.
Treating them as one continuous flight by unknown craft goes beyond the evidence. Nothing establishes a route from Chesapeake Bay to Washington, a shared appearance, common performance characteristics or repeated detection of the same formation. The Washington reports usually concerned radar points and isolated lights, whereas Nash and Fortenberry described eight flattened, luminous objects moving together.
What the surviving evidence can and cannot prove
The strongest part of the Chesapeake case is the pilots’ prompt, detailed and broadly consistent testimony. The strongest part of the Washington case is that experienced controllers reported unusual returns on more than one radar installation over two weekends. Together, they show that July 1952 produced genuine identification problems for skilled aviation personnel in Virginia-linked airspace. The Air Force’s own records preserved a category of unexplained reports rather than claiming that every observation had been conclusively solved. Project Blue Book material now held through National Archives collections also illustrates how investigations varied in completeness and changed with official priorities.[archives.gov]prologue.blogs.archives.govsaucers over washington the history of project blue booksaucers over washington the history of project blue book
The evidence cannot establish extraordinary speed or manoeuvrability with confidence. Nash and Fortenberry lacked measured range, so their speed and size estimates were necessarily speculative. Washington’s radar returns were not preserved as a modern digital data set that independent analysts could replay against weather, equipment performance and known traffic. Surviving narratives do not consistently provide exact timestamps, bearings, altitude information, radar characteristics or synchronised visual observations.
Proposed explanations for the Norfolk sighting include reflections in the cockpit glazing, distorted ground lights, astronomical mirage effects and nearby luminous insects. Menzel considered reflections or optical effects more plausible than objects executing an almost instantaneous reversal. These proposals identify real vulnerabilities in night observation through aircraft windows, but no single explanation has reproduced every feature described by both pilots.[Wikipedia]WikipediaNash-Fortenberry UFO sightingNash-Fortenberry UFO sighting
For Washington, atmospheric propagation remains the leading conventional explanation for much of the radar activity, supplemented by misidentified stars, meteors and aircraft lights. It is stronger than the more speculative Norfolk explanations because it addresses a known radar mechanism and the recorded weather environment. Even so, it does not neatly resolve every operator recollection or reported visual coincidence.
The most defensible assessment is therefore mixed. The Nash–Fortenberry report remains an unusually detailed but uninstrumented pilot observation. The Washington events remain a complicated set of radar anomalies and visual reports for which weather-related propagation offers a credible, though disputed, explanation. Neither incident has been debunked in every detail, but neither provides proof of an exotic vehicle.
Within Virginia’s UFO history, their lasting importance is methodological. They demonstrate why trained witnesses and multiple sensors deserve careful attention, while also showing that those features alone are insufficient. Without calibrated recordings, established range and precise correlation between observers, an impressive encounter can remain unresolved for decades without becoming stronger evidence than it was on the night it occurred.
Amazon book picks
Further Reading
Books and field guides related to Did Pilots and Radar Track the Same Objects?. Use these as the next step if you want deeper reading beyond the article.
The UFO Experience: A Scientific Inquiry
Discusses major aviation sightings and investigations.
UFOs: Generals, Pilots, and Government Officials Go on the Re...
Explores credible pilot and radar reports.
eBay marketplace picks
Marketplace Samples
Live-tested eBay searches with available results related to this page.
Selected fromUFO poster oneBay.co.uk.
Endnotes
1.
Source: nicap.org
Title: UFO Report
Link:https://www.nicap.org/520714norfolk_dir.htm
Source snippet
July 14, 1952; 20-25 miles N. of Norfolk, Va (BBU 1444) [CCL Item #24]... Objects approached head on at high speed estimated at about 12...
Published: July 14, 1952
2.
Source: nicap.org
Link:https://www.nicap.org/reports/nash-tulien.htm
Source snippet
nash-tulien...
3.
Source: Wikipedia
Title: 1952 Washington, D.C., UFO incident
Link:https://en.wikipedia.org/wiki/1952_Washington%2C_D.C.%2C_UFO_incident
Source snippet
March 14, 2007 — At 11:40 p.m. on Saturday, July 19, 1952, Edward Nugent, an air traffic controller at Washington National Airport, spott...
Published: March 14, 2007
4.
Source: Wikipedia
Title: 1952 Washington, D.C. UFO incident
Link:https://en.wikipedia.org/wiki/1952_Washington%2C_D.C._UFO_incident
5.
Source: gutenberg.org
Link:https://www.gutenberg.org/cache/epub/17346/pg17346.html
Source snippet
RuppeltAuthor: Edward J.Ruppelt... 1 Project Blue Book and the UFO Story... July 1955, E.... On the night of December 10, 1952, near a...
Published: December 10, 1952
6.
Source: cia.gov
Title: DOC 0005517742
Link:https://www.cia.gov/readingroom/docs/DOC_0005517742.pdf
Source snippet
CLA's Role in the Study of UFOs, 1947-90The first report of a "flying saucer" over the United States came on 24 June 1947, when Kennet...
Published: June 1947
7.
Source: gutenberg.org
Title: Project Gutenberg
Link:https://www.gutenberg.org/files/66639/66639-h/66639-h.htm
Source snippet
The World of Flying Saucers, by Donald H. Menzel and Lyle G. Boyd—A Project Gutenberg eBook...
8.
Source: en.wikisource.org
Link:https://en.wikisource.org/wiki/Page%3ARuppelt_-_The_Report_on_Unidentified_Flying_Objects.djvu/232
9.
Source: cia.gov
Link:https://www.cia.gov/readingroom/docs/CIA-RDP79B00752A000300100010-4.pdf
10.
Source: prologue.blogs.archives.gov
Title: saucers over washington the history of project blue book
Link:https://prologue.blogs.archives.gov/2019/12/19/saucers-over-washington-the-history-of-project-blue-book/
11.
Source: upload.wikimedia.org
Link:https://upload.wikimedia.org/wikipedia/commons/2/21/Project_Blue_Book%2C_BBA-PBSR11-300.pdf
12.
Source: Wikipedia
Title: Nash-Fortenberry UFO sighting
Link:https://en.wikipedia.org/wiki/Nash-Fortenberry_UFO_sighting
13.
Source: nicap.org
Link:https://www.nicap.org/chop.htm
14.
Source: nicap.org
Title: UF O Report
Link:https://www.nicap.org/520719wns_dir.htm
15.
Source: nicap.org
Title: IU R 33:1 Intelligent Motions
Link:https://www.nicap.org/articles/iur33-1_intelligent_motions_swords_article.htm
16.
Source: gutenberg.org
Link:https://www.gutenberg.org/cache/epub/17346/pg17346-images.html
17.
Source: gutenberg.org
Link:https://gutenberg.org/ebooks/17346
18.
Source: nicap.org
Link:https://www.nicap.org/chronos/1952NEW.htm
19.
Source: commons.wikimedia.org
Title: File:1952 UFO Flap Air Force frequency graph of UFO reports.png
Link:https://commons.wikimedia.org/wiki/File%3A1952UFO_Flap-_Air_Force_frequency_graph_of_UFO_reports.png
20.
Source: cia.gov
Title: FLYIN G SAUCERS UFO REPORTS | CIA FOIA (foia.cia.gov)Fuller Gulf of Mexico,
Link:https://www.cia.gov/readingroom/document/cia-rdp81r00560r000100010002-9
21.
Source: cia.gov
Title: DOC 0000838057
Link:https://www.cia.gov/readingroom/docs/DOC_0000838057.pdf
22.
Source: cia.gov
Link:https://www.cia.gov/readingroom/docs/DOC_0000192682.pdf
23.
Source: cia.gov
Title: DOC 0000190094
Link:https://www.cia.gov/readingroom/docs/DOC_0000190094.pdf
24.
Source: cia.gov
Link:https://www.cia.gov/readingroom/docs/1992-04-01A.pdf
25.
Source: cia.gov
Link:https://www.cia.gov/readingroom/document/07083374
26.
Source: cia.gov
Title: CIA RDP66B00403R000200160048 9
Link:https://www.cia.gov/readingroom/docs/CIA-RDP66B00403R000200160048-9.pdf
27.
Source: cia.gov
Link:https://www.cia.gov/readingroom/document/06935701
28.
Source: cia.gov
Title: FOIA CASE LOG CALENDER YE[16111550]
Link:https://www.cia.gov/readingroom/docs/FOIA%20CASE%20LOG%20CALENDER%20YE%5B16111550%5D.pdf
29.
Source: cia.gov
Link:https://www.cia.gov/readingroom/docs/CY%202008%20CASE%20LOG%5B15829355%5D.pdf
30.
Source: war.gov
Link:https://www.war.gov/medialink/ufo/061226/release_03/documents/CIA-UAP-002_Scientific-Advisory-Panel-on-Unidentified-Flying-Objects_Report_1952-1953.pdf
31.
Source: nicap.org
Link:https://www.nicap.org/bluebook/unknowns.htm
32.
Source: nicap.org
Link:https://www.nicap.org/ufoe/ufoe33_38.htm
33.
Source: nicap.org
Title: Flying Saucers From Outer Space
Link:https://www.nicap.org/books/fsos/appendixes.htm
34.
Source: nicap.org
Link:https://www.nicap.org/bluebook/bluelist.htm
35.
Source: Wikipedia
Title: Project Blue Book
Link:https://en.wikipedia.org/wiki/Project_Blue_Book
36.
Source: Wikipedia
Title: Robertson Panel
Link:https://en.wikipedia.org/wiki/Robertson_Panel
37.
Source: history.com
Title: ufos washington dc news reports
Link:https://www.history.com/articles/ufos-washington-dc-news-reports
38.
Source: history.com
Title: u s air force closes the book on ufos 45 years ago
Link:https://www.history.com/articles/u-s-air-force-closes-the-book-on-ufos-45-years-ago
39.
Source: history.com
Title: ufos washington white house air force coverup
Link:https://www.history.com/articles/ufos-washington-white-house-air-force-coverup
40.
Source: archives.gov
Title: Project BLUE BOOK
Link:https://www.archives.gov/research/military/air-force/ufos
41.
Source: archives.gov
Link:https://www.archives.gov/research/guide-fed-records/groups/237.html
42.
Source: nicap.org
Title: section 5
Link:https://www.nicap.org/ufoe/section_5.htm
43.
Source: nicap.org
Title: Challenge of UFOs
Link:https://www.nicap.org/books/coufo/coufo_complete.htm
44.
Source: cia.gov
Title: RADA R INSTALLATIONS | CIA FOIA (foia.cia.gov)
Link:https://www.cia.gov/readingroom/document/cia-rdp82-00457r012700370006-2
45.
Source: project1947.com
Link:https://www.project1947.com/fig/1953a.htm
Additional References
46.
Source: docsteach.org
Title: Docs Teach Saucers Over Washington, DCOn
Link:https://docsteach.org/document/saucers-over-washington/
Source snippet
Saucers Over Washington, DCOn July 19, 1952, air traffic controllers at Washington National Airport spotted several radar “blips...
Published: July 19, 1952
47.
Source: youtube.com
Link:http://www.youtube.com/watch?v=Xmrk5AaaO2U
Source snippet
The Night UFOs Swarmed Over Washington D.C. | The 1952 Invasion They Tried to Hide...
48.
Source: youtube.com
Link:http://www.youtube.com/watch?v=NK-PqEEGBh4
Source snippet
The 1952 Washington D.C. UFO Incident | Radar, Jets & An Unsolved Mystery...
49.
Source: youtube.com
Link:http://www.youtube.com/watch?v=0JGDKGtykO4
Source snippet
The Washington D.C. UFO Flyover 1952: When the Skies Above the Capital Turned Against Us...
50.
Source: youtube.com
Link:http://www.youtube.com/watch?v=0OIcv6ekTTw
Source snippet
1952 Washington DC UFO radar incident pilot The 1952 Washington D.C. UFO Incident | Radar, Jets & An Unsolved Mystery STM Daily News...
51.
Source: archivesfoundation.org
Link:https://archivesfoundation.org/documents/50-years-ago-government-stops-investigating-ufos/
52.
Source: theufodatabase.com
Link:https://theufodatabase.com/incidents/nash-fortenberry-ufo-sighting
53.
Source: ufouap.net
Link:https://www.ufouap.net/en/cases/nash-fortenberry-ufo-sighting
54.
Source: instagram.com
Link:https://www.instagram.com/p/DQ7kP1HEYTa/
55.
Source: academia.edu
Link:https://www.academia.edu/49680297/Project_Blue_Book_Special_Report_14