It looks like you're using an Ad Blocker.

Please white-list or disable AboveTopSecret.com in your ad-blocking tool.

Thank you.

 

Some features of ATS will be disabled while you continue to use an ad-blocker.

 

FOIA: Clovis NM Sighting of Orange Lights 24APR52 (Unidentified)

page: 1
0

log in

join
share:

posted on Feb, 2 2008 @ 09:00 AM
link   
NM_APR_24_1952.pdf
Clovis NM Sighting 24APR52 (Unknown)
A sighting in Clovis NM by an AF Flight Surgeon who witnessed orange lights. sometimes fused and sometimes split that would move at tremendous speed at times.

Document date: 1952-04-24
Department: Unknown
Author: Unknown
Document type: Report
pages: 4

 

Archivist's Notes: This 24APR52 sighting was classified as unknown on the record card. The file is difficult to read but you can discern most of the desription of this sighting over the skies of Clovis, NM.
 



posted on Feb, 2 2008 @ 01:01 PM
link   
The sighting involves a bright object seen over the skies at Clovis, New Mexico. The specifics of this object was the amber/orange color and the flight pattern which was erratic. This kind of movement made it hard to determined if it was only one object or more then one. The object also appeared to be motionless for few seconds then flying with a high rate of speed. No more details or comments about. The whole sightings lasted 5 minutes, enough time for the observer to notice all the above. The witness, the AF flight surgeon is a trained observers so his testimony is regarded as coming from e credible source. As the op said, the document is in poor condition and nothing else can be retracted from it.



posted on Feb, 3 2008 @ 02:37 PM
link   
All the information in this document has already been covered. It is an interesting description though of an object separating and coming back together. It is hard to imagine if it were a craft flown by some intelligence, why would they do that? There are many cases that have similar descriptions of objects separating and recombining like the Rendlesham Forest / Bentwaters Incident for example.



 
0

log in

join