SUNlite - Vol 14 No 01

Magazine Overview

SUNlite, Volume 14, Number 1, published in January-February 2022, is a magazine dedicated to UFOlogy and UFOs. The cover features a striking image of a starry night sky over a snow-covered landscape with a bright celestial object, accompanied by the headline "Shedding some light on UFOlogy and UFOs." The issue includes an excerpt referencing Dr. J. Allen Hynek and his work on "The UFO Experience," noting the persuasive nature of Venus as a potential misidentified UFO.

Table of Contents

The issue features several articles and case reviews:

• "Weeding out the Weinstein catalog: January 27, 1994 Kazakhstan Republic" (Pages 2-3)
• "UFO evidence under review: January 9, 1953, Northern Japan" (Pages 4-5)
• "The 701 club: Case 11419 Grand Haven/Holland, Michigan February 27, 1967" (Pages 6-8)
• "A method for modeling linear UAP motion from airborne surveillance system videos" by Chris Clarke (November 2021) (Pages 9-12)
• "Project Blue Book case review: July-December 1963" (Pages 13-25)

Article Summaries

Going back to the past

This section discusses the Department of Defense's (DOD) announcement of the "Airborne Object Identification and Management Synchronization Group" (AOIMSG), the successor to the Navy's UAP task force (UAPTF). The AOIMSG's purpose is to identify objects in "special use airspace" and assess threats to national security. The author suggests this is an attempt by the DOD to dilute an amendment that required the formation of the Anomaly Surveillance, Tracking, and Resolution Office (ASTRO) and the Aerial and Trans medium Phenomena and Advisory Committee (ATPAC), which would have included UFOlogists. The author expresses concern that the AOIMSG might become another "Project Blue Book," discovering identifiable objects and facing public pressure from leaked videos and rumors. The article also mentions Chris Clarke's analysis of the Aguadilla video, which the author believes could be a balloon.

Weeding out the Weinstein Catalog: January 27, 1994 - Kazakhstan Republic

This article examines a UFO sighting reported by the crew of a Tajik Airlines Boeing 747SP over Kazakhstan. The crew encountered a bright, luminous object that approached at high speed and altitude, maneuvering in circles and corkscrews for about 45 minutes. The object left contrail-like effects at an estimated altitude of 100,000 feet. The pilot, Captain Ed Rhodes, believed the object was extraterrestrial and under intelligent control. The article notes that photographs taken by the pilot have never surfaced, raising questions about the source and the outcome of the photos. The analysis suggests the sighting might have been a Progress M-21 rocket launch from Baikonur, which occurred around the same time and location, consistent with the observed phenomena.

UFO evidence under review: January 9, 1953 - Northern Japan

This section reviews a UFO sighting involving an F-94 jet interceptor pilot, Lt. Melvin E. Conine, and radar observer, Sec. Lt. Walter D. Lawley, Jr., over Northern Japan. The object was described as a rotating cluster of lights that changed color from red to white to green. The visual sighting lasted one minute, and radar contact was weak and fuzzy for two minutes. The article notes confusion regarding the date, with some references pointing to December 29, 1952, which was previously attributed to Venus. The Blue Book file for this case is missing information about Colonel Blakeslee's incident but includes the F-94 intercept. The analysis suggests the sighting was likely a balloon launched from Misawa AFB, as concluded by Blue Book, or potentially Venus or an aircraft landing light. The article argues that this case should be removed from the "best evidence" category.

The 701 Club: Case 11419: Grand Haven/Holland, Michigan February 27, 1967

This article details a UFO sighting involving multiple witnesses, including Sheriff Grysen and others, in Grand Haven/Holland, Michigan. The object was described as a large white light with smaller red and green lights, which made an instantaneous 90-degree turn and moved too fast to follow, lasting for over an hour. The Blue Book file partially explained it as Venus. The analysis, based on a report by William T. Powers, suggests that Venus was the likely source for many of the observations, as it set around 20:43. The rapid motions described are attributed to an involuntary impression of motion or the light simply going out. Other possibilities considered include aircraft landing lights or a Naval exercise. The article concludes that the case should be classified as "probably Venus/possible aircraft/insufficient information" and removed from the list of unidentifieds.

A Method for Modeling Linear UAP Motion from Airborne Surveillance System Videos

Written by Chris Clarke, this article presents a method for analyzing unidentified aerial phenomena (UAP) captured on video, particularly from airborne surveillance systems with metadata overlays. The presentation aims to determine if an object's movement can be explained by prosaic factors, such as being blown by the wind, before considering extraordinary explanations. The "Simple Model" involves creating a model that includes the aircraft's position, the camera's bore-sight intersection with the ground, and wind speed and direction to deduce the object's path and speed. The article notes that surveillance aircraft typically fly at speeds that would not allow them to follow a wind-blown object in the manner described in some UAP cases.

Recurring Themes and Editorial Stance

The recurring themes in this issue revolve around the critical analysis of UFO sightings, often seeking prosaic explanations such as misidentification of celestial bodies (like Venus) or conventional aircraft. There is a clear editorial stance favoring rigorous investigation and a skeptical approach to claims of extraordinary phenomena. The magazine highlights the challenges in UFO investigation, including the lack of follow-up, missing evidence (like photographs), and the potential for government programs to be less transparent or thorough than desired. The articles emphasize the importance of examining available data, cross-referencing information, and applying logical reasoning to UFO reports, often concluding that many cases can be explained by known phenomena or lack sufficient evidence to be considered truly anomalous.

This document is a review of Project Blue Book cases from July through December 1964, along with a detailed methodology for analyzing airborne object flight paths, exemplified by the 2013 Aguadilla UAP case.

Methodology for Analyzing Airborne Objects

The document outlines a method to deduce the flight path of airborne objects recorded by surveillance systems. This method relies on the availability of on-screen metadata (aircraft and ground track) and historical weather data. It is primarily applicable to slow-moving, linear paths that could be windborne.

The process involves using the overall view of the recorded event and lines of sight to deduce a potential linear path. This path is then measured for length and direction to calculate the object's velocity and heading. This calculated data is then compared with recorded wind speed and direction to assess whether the motion is consistent with weather conditions, thereby indicating if the object is extraordinary.

The Complex Model

This model illustrates an object moving linearly while an aircraft orbits it. The challenge is that the aircraft's motion is not parallel to the object. This is overcome by using a fourth line of sight to determine the intersection point, which indicates the object's path direction. Distance measurements between points in the video, correlated with metadata, allow for the calculation of the object's speed.

Validation of the Path

To validate the deduced path, the object's direction and speed are compared with local weather observations. If the object is windblown, its movement should closely match local wind conditions, though high-altitude winds may differ from ground-level winds.

Modeling Real World Examples: The Aguadilla UAP

This section details the analysis of a 2013 video showing an unknown object maneuvering over Aguadilla Airport, Puerto Rico. The video was recorded by a US Department of Homeland Security DHC-8 aircraft equipped with an L-3 Wescam MX-15 surveillance turret.

Modeling in Google Earth

The metadata from the video, including aircraft flight path and ground target points, was modeled using Google Earth. This visualization showed the Aguadilla area, the aircraft's flightpath, and 35 lines of sight from the camera to the ground over a 209-second period. By rotating the observer's position, the potential line of motion of the object was determined.

A vector was drawn from the intersection of the camera's line-of-sight with the object's motion line-of-sight. This red line approximated the object's linear path, indicating a southwest direction of travel, starting at an altitude of 305m (1000 ft) and ending at 210m (689 ft). The track length was measured at 1.173 km on a bearing of 237° (WSW), and the speed was calculated at 12.5 mph.

Validation of Calculated Velocity and Direction

Historical weather data for the time of the sighting (April 26, 2013) showed wind speeds between 050° and 060° at 11-12 knots (approximately 21.3 kph), with an ENE direction (67° bearing). The calculated movement of the object (067° at 20 kph) closely comported with the recorded wind speed and direction (055° at 21 kph). This suggests the object was likely a lighter-than-air object propelled by the wind.

Summary of Aguadilla UAP Analysis

The method applied to the Aguadilla UAP case supported the hypothesis that the object's movement was slow and linear, as expected for a wind-driven object. This finding is compatible with other assessments, such as Ruben Lianza's 2017 report suggesting a Chinese Lantern.

Project Blue Book Case Review: July-December 1964

This section provides a detailed review of numerous cases from the Project Blue Book files for the latter half of 1964. Each entry includes the date, location, the original Project Blue Book (BB) explanation, and the reviewer's evaluation.

July 1964 Cases

Cases reviewed include sightings in Fosterdale, NY (misinterpretation of conventional objects, meteor, aircraft), Mason, OH (meteor), Denver, CO (meteor), Bridgeport, CA (aircraft), Frankfort, IN (insufficient data, possible aircraft), Pacific (satellite, SA-5 rocket body), Dayton, OH (aircraft), Clearwater, FL (flare drop), Winchester, VA (insufficient data, possibly Vega), Roeland Park, KS (aircraft), Hazelton, ID (aircraft), Kelleen, TX (aircraft), Rapid City, SD (meteor), Ten Sleep, WY (meteor), Cape Girardeau/Jackson/Belleville (insufficient data, inversion, temperature inversion), Washington DC (balloon), Mankato, MN (insufficient data), New Iberia, LA (star/planet), Buckley, IL (aircraft), San Antonio, TX (moon), Chicago, IL (satellite), Vandenberg, CA (balloon), Texarkanna, TX (unreliable report, possible aircraft/satellites), Pasadena, CA (meteor), Pacific (satellite), Odessa, TX (unreliable report, possible aircraft), Sacramento, CA (satellite), and Cleveland, OH (satellite).

August 1964 Cases

Cases reviewed include sightings in Kansas City, MO (satellite), Folsom, CA (satellite), Pacific (satellite), Dayton, OH (satellite), Berea, OH (balloon, Echo 2 sighting), Dayton, OH (meteor), Lincoln Park, MI (meteor), Vermillion, OH (satellite), Pacific (balloon, possible meteor), Gainesville, GA (grass, oil ring), Dayton, OH (satellite), Lynn, MA (balloon), Dayton, OH (satellite), New Carlisle, OH (satellite), Oregon area (meteor), Washington DC (aircraft), Dayton, OH (satellite), Buckley ANG base, CO (parachute flare, possible meteor), Clinton, IA - Littleton, IL (unidentified), Brigham, UT (birds), Fayetteville, NC (satellite), Yahatz, OR (satellite, Transit 2A rocket body), Waldorf, MD (Venus/Mars), Pacific (satellite, Transit 2 rocket body), Holt, MI (aircraft), Pacific (satellite), Kissimee, FL (insufficient data), Coudersport, PA (insufficient data), Sayre, OK (satellite), Cleveland, OH (satellite), Langley AFB, VA (missile activity, possibly aircraft), Lakewood, AR (balloon), Dayton, OH (satellite), Pacific (flare), and Ft. Huachuca, AZ (aircraft, balloon, satellite).

September 1964 Cases

Cases reviewed include sightings in Pickstown, SD (satellite), Franklin, OH (satellite), Dayton - Franklin, OH (satellite), Marietta, OH (insufficient data, possible aircraft), Kansas City, MO (satellite), Baltimore, MD (satellite), Cresco, IA (birds), Whitesboro, NY (satellite), Bronx, NY (satellite), Norwich, NY (unidentified), Rooxbury, NY (meteor), Laredo AFB, TX (satellite), Dayton, OH (satellite), Denver, CO (unidentified), Kansas City, MO (satellite, Jupiter), Lake Chelan, WA (aircraft, ground lights), Pacific (satellite), Miami, FL (satellite), Pacific (satellite), Cleveland, OH (aircraft), Cleveland, OH (insufficient data), Franklin, MA (insufficient data), Dayton, OH (satellite), Kansas City, MO (spica), Celina, OH (satellite), Washington, MO (aircraft), Wilbur, WA or Los Angeles, CA (satellite), Binghampton, NY (aircraft, satellite, meteor, stars/planet), Dayton, OH (satellite), Ft. Huachuca, AZ (balloon, satellite), Kansas City, MO (satellite), and Dayton, OH (satellite).

October 1964 Cases

Cases reviewed include sightings in Cedar Grove, NJ (unidentified), Ulysses, KS (debris in wind), Kent, England (insufficient data, possible aircraft), Kansas City, MO (meteor), Centerville, OH (Venus), Houma, New Orleans, Baton Rouge, LA (stars), Coldwater, OH (aircraft), Berea, OH (aircraft), Rapid City, SD (meteor), CA, NV, OR (missile), Red Bluff, CA (insufficient data, wind borne object), Reno, NV/Stead AFB, NV (meteor, Jupiter, insufficient data), San Jose, CA (unreliable report, object observed to 'land'), Florence, OR (insufficient data, possible meteor), Springfield, OH (insufficient data, possible meteor), and Soudan, MN (aircraft).

Recurring Themes and Editorial Stance

The recurring themes in the Project Blue Book case reviews are the frequent identification of known objects such as satellites (especially Echo 1 and 2), aircraft, meteors, balloons, and celestial bodies (planets, stars). Many cases are dismissed as misinterpretations, insufficient data, or hoaxes. The reviewer's stance appears to be one of critical evaluation, seeking plausible explanations and often agreeing with or clarifying the original Project Blue Book conclusions. The methodology section suggests a scientific approach to analyzing unexplained phenomena, emphasizing data correlation and comparison with known physical processes like wind.

This document, identified as issue 20 of 'UFO Report' from November 1964, presents a detailed analysis of unidentified flying object (UFO) sightings and their classifications. The content primarily consists of tables listing dates, locations, explanations for the sightings (BB explanation), and the author's evaluation of each case. The magazine also includes a summary section that discusses the challenges of analyzing the data and highlights specific types of reports.

Analysis of Sightings (November & December 1964)

The document meticulously lists numerous sightings from November and December 1964. Many entries are classified under 'BB explanation' as 'Satellite', 'Meteor', 'Balloon', 'Aircraft', 'Reflection', 'Moon Dog', 'Betelgeuse', 'UNIDENTIFIED', 'Conflicting data', 'Unreliable report', 'Insufficient data', 'Missile', 'Meteor shower', 'Fomalhaut', 'Jupiter', 'Capella', 'Spica', 'Arcturus/Mars', 'Radar Anomalies', 'Psychological category', and 'Visual: Stars/planets' or 'Radar: False targets'.

The author's 'My evaluation' column often confirms these explanations, frequently citing 'Agreed', 'Agreed. Echo 2', 'Agreed. Echo 1', 'Possible meteor', 'Possible aircraft', 'Possible balloon', 'Possible birds', 'Possible Sirius', 'Possible contrail', 'UNIDENTIFIED', and 'No Case file'.

Notable entries include:

• November 1964:
• Summitt, NJ (Nov 26): Missile classified as 'Insufficient data', evaluated as 'Possible meteor'.
• Ft. Jones/Mt. Shasta, CA (Nov 30): Moon Dog classified as 'Insufficient data', evaluated as 'Possibly Sirius'.
• Fosterdale, NY (Nov 31): Classified as 'Insufficient data', evaluated with a note that images looked like star trails or time exposures of satellites/planes.
• Hancock, NY (Nov): Satellites classified as 'Insufficient data', with the evaluation noting that witnesses had no specific dates and guessed at times, with multiple sightings sounding like satellites.
• Junction City, KS (Nov 5): Classified as 'Insufficient data', evaluated as 'Agreed. 12-14 year olds reporting object landing in ravine but nothing seen in ravine. No positional data/duration.'
• St. Petersburg, FL (Nov 5-20): A complex series of evaluations for 'Satellites' and 'Aircraft', with specific dates and evaluations like 'Possible aircraft or Abelstar rocket' and 'Echo 2'.
• Braintree, MA (Nov 7): Classified as 'Insufficient data', evaluated as 'Agreed. Witnesses sent letter but did not provide pertinent details and did not return form'.
• Waldwick, NJ (Nov 15): Classified as 'Insufficient data', evaluated as 'Possible aircraft'.
• 75 mi. W of Midway Is. (Nov 16): Meteor shower classified as 'Agreed. This appears to be a display of several Leonid fireballs.'
• Blue Hill, ME (Nov 16-20/1): Aircraft classified as 'Agreed. Observations by 10-year old student looking out window.'
• Bridgewater, MA (Nov 17): Aircraft classified as 'Agreed. Report by 13-year old involving lights moving around the sky.'
• Lakeland, FL (Nov 20): Conflicting data classified as 'Possible aircraft'.
• Honolulu, HI (Nov 26): Balloon classified as 'Agreed'.
• Glen Falls, NY (Nov 29): Balloon classified as 'Contrail illuminated by setting sun'.

• December 1964:
• Seward, PA (Dec): Meteor classified as 'Agreed'.
• Pacific (Dec 2): Satellite classified as 'Agreed. Possibly Cosmos 44.'
• Near Iceland (Dec 4): Satellite classified as 'Agreed. Echo 2.'
• Baker, OR (Dec 4): Visual: Stars/planets classified as 'Agreed. Possibly Arcturus', and Radar: False targets classified as 'Agreed'.
• Vero Beach, FL (Dec 5): Classified as 'Insufficient data', evaluated as 'Possible meteor'.
• Falls Church, VA (Dec 14): Moon classified as 'Agreed'.
• Needham, MA (Dec 14): Classified as 'Insufficient data', evaluated as 'Agreed. Second hand report. No positional data.'
• Cudahy, WI (Dec 18): Unreliable report classified as 'Possible meteor'.
• Patuxent River, MD (Dec 19-29): Radar Anomalies classified as 'Agreed. Saturn rocket booster.'
• Harrisonburg, VA (Dec 21): Psychological category classified as 'Agreed'.
• Cleveland, OH (Dec 29): Arcturus/Mars classified as 'Agreed. Witness not specific about azimuth to determine which. Both objects were about same magnitude.'

Reclassification Section

This section analyzes 293 cases from July through December 1964, with the author's opinion that 73 (about 25%) were improperly classified. Of these, 39 (about 13% of total cases, 53% of reclassifications) were listed as 'insufficient information'. A table details these cases, their original classification, and the author's proposed reclassification with reasons.

Key reclassifications include:

• July 1964:
• Frankfort, IN (July 1): Reclassified from 'Insufficient data' to 'Possible aircraft'.
• Pacific (July 2): Reclassified from 'Insufficient data' to 'Satellite. SA-5 rocket body.'
• Winchester, VA (July 5): Reclassified from 'Insufficient data' to 'Possibly Vega. 16-year old witness stated it was a star in motion towards north but was mostly visible overhead for 30 minutes.'
• Hazelton, ID (July 7-9): Reclassified from 'Aircraft' to 'Possible Echo 2 sightings. Echo 2 made passes approximately at the time in question. Witness gave time for only one date and not all three.'
• Mankato, MN (July 10): Reclassified from 'Insufficient data' to 'Possibly Echo2. Echo 2 made a pass very similar to the one described but 15 minutes after the time listed.'
• Texarkanna, TX (July 13): Reclassified from 'Unreliable report' to 'Insufficient data. No duration/positional data for sightings. It is possible these were sightings of aircraft and satellites (Two rocket bodies were visible during the sighting).'
• Berea, OH (July 17): Reclassified from 'Balloon' to 'Echo 2 sighting. BB gave incorrect Zulu time (witness specified EDT and not EST).'
• Lynn, MA (July 18): Reclassified from 'Balloon' to 'Possibly Echo 2 and aircraft. BB Zulu time did not incorporate DST. Witness reported object going SW and then NNE. First part was possible aircraft going SW. Echo 2 then came out of SW and was confused to be the original object.'
• Buckley ANG base, CO (July 20): Reclassified from 'Parachute Flare' to 'Possible meteor. Duration listed as 2 minutes but description matches meteor.'
• Langley AFB, VA (July 24): Reclassified from 'Missile activity' to 'Not missile activity. Possible aircraft from Navy base in Norfolk/VA beach (Oceana NAS). Course was in that direction. Report states GCA tracked objects for five minutes but no data available about speed or altitude.'
• Marietta, OH (July 26): Reclassified from 'Insufficient data' to 'Insufficient data. BB identified as flare because that was how it was reported. Duration not listed and description is brief.'
• Kansas City, MO (July 28): Reclassified from 'Jupiter' to 'Jupiter did not rise until 0600Z (sighting 0430Z) and in the East (sighting in SW). Antares'.
• Lake Chelan, WA (July 28): Reclassified from '1. Aircraft, 2. Ground lights' to 'Possibly Arcturus'.
• Kansas City, MO (July 29 - Aug 8): Spica classified as 'Probably Arcturus (description is object in west. Both stars visible Arcturus is brighter of two.)'.

• August 1964:
• Calumet, MI (Aug): Satellite classified as 'Insufficient data. No date.'
• Mansfield Center, CT (Aug): Satellite classified as 'Insufficient data. No date. Report made four months later.'
• Fort Bragg, NC (Aug): Classified as 'Insufficient data', evaluated as 'Possible meteors'.
• Kansas City, MO (Aug 2): Fomalhaut classified as 'Possibly Saturn'.
• Little Silver, NJ (Aug 4): Balloon classified as 'Possibly Altair'.
• Wilkes Barre, PA (Aug 5): Classified as 'Insufficient data', evaluated as 'Brief (15 seconds) daylight sighting of stationary object that disappeared. Possible balloon.'
• Fort Worth, TX (Aug 5): Classified as '1-2. Misinterpretation of conventional objects. 3-4. Star', evaluated as 'Report is confusing. First two sightings appear to be meteors. Third sighting may have been Saturn. Fourth sighting could have been Echo satellite. Witness gave same time for four sightings. Echo was 30 minutes after time given.'
• Fort Worth, TX (Aug 5): Satellite classified as 'Insufficient data. Witness did not give positional information. Could have been Echo 1 or 2. Both made passes over region within 30 minutes of sighting.'
• Wilkes Barre, PA (Aug 6): Classified as 'Insufficient data', evaluated as 'Possible meteor.'
• Colorado Springs/Denver, CO (Aug 9): Classified as 'Insufficient data', evaluated as 'Possible birds. Film did not show anything in focus.'
• Lone Pine, CA (Aug 29): Classified as '1. Jupiter, 2. Capella, 3. Fomalhaut', evaluated as '1. Saturn, 2. Insufficient data (no positional information), 3. Insufficient data (no positional information)'.
• Roswell, NM (Sep 4): Classified as 'Satellites', evaluated as 'Insufficient data. Witness wrote letter on 4 September describing UFO with no time or specific date.'

Summary Section

The summary highlights the significant problem of poorly copied and incomplete files from the August 1964 period, making analysis difficult. It states that Echo 1 and 2 satellites, along with other bright satellites and space debris, accounted for approximately 31% of the UFO reports during the analyzed time period.

The summary also notes a continued significant number of sightings by witnesses aged 16 and younger, suggesting that some of these might be due to active imaginations rather than careful observations. It mentions submissions from 'collectors' of UFO reports, which led to many reports being lumped together, often as Echo 1 and 2 satellite observations.

The 'UFO landing/alien reports' are described as particularly troublesome. The summary suggests that most can be attributed to hoaxes or overactive imaginations, with the exception of a significant case from Harrisonburg, Virginia, in December. The investigation of this case is criticized for its potential lack of thoroughness, influenced by local UFO groups and newspaper stories. The report questions the evidence, noting that while high radiation levels were reportedly found, there were no significant marks on the ground. The author expresses dissatisfaction with the survey methods, comparing them unfavorably to their experience in the Navy Nuclear Power Program.

Finally, the summary acknowledges that many reports suffer from missing information, making them difficult to analyze, which explains why Blue Book classified so many as 'Insufficient information/data'. The author plans to continue analyzing reports from 1965-1967, aiming for about 300-400 sightings per issue, with the project anticipated to be completed by 2025.

Recurring Themes and Editorial Stance

The recurring themes in this issue are the misidentification of celestial objects and man-made satellites as UFOs, the prevalence of 'insufficient information' in case files, and the challenges in conducting thorough investigations. The author's stance appears to be critical and analytical, aiming to reclassify cases based on available evidence and logical explanations, often attributing sightings to known phenomena like satellites, meteors, or aircraft. There is a clear skepticism towards landing/alien reports without substantial physical evidence, and a critique of investigative procedures when they appear to be lacking rigor. The editorial process involves a systematic review and reclassification of historical UFO data, with a focus on scientific and logical explanations.