At 00:08 GMT on 4 January 1958, a US military transport crew reported a bright orange light while flying over Libya. An intense blue flash illuminated the cockpit, and the observers described a rapid apparent acceleration. The released Air Force file preserves both that striking account and a much less dramatic conclusion: the investigation classified the observation as a meteor.
The report also mentions interference on the navigator’s radar. It places that interference approximately ten minutes before the visual event. This distinction matters because the case appears in a radar-case catalogue, where a reader could easily assume that radar tracked the same luminous object. The surviving document does not establish such a track.
The record and its chronology
The principal source is a four-page scan of the Air Force case file preserved by NICAP. Its first page is an ATIC Project 10073 record card. Two further pages reproduce parts of an unclassified military message, while another contains a handwritten evaluation. These are different layers of the investigation rather than four independent sightings.
The record card identifies the event as 4 January 1958 and gives the GMT date-time group as 04/0008Z. The message bears later transmission and receipt markings. Those administrative dates belong to the reporting process; they do not move the encounter to the day when the message was received. The incident year used for this archive entry is therefore 1958.
What the aircrew described
The message describes one orange object, with an orange tail and an elliptical appearance. It explicitly says that no estimate of length or width could be made. The initial appearance was of approximately level flight, followed by a very bright blue flash reflected into the aircraft’s cockpit. The observers then reported very high apparent acceleration and disappearance.
The summary card records an observation lasting five seconds and gives a north-easterly course. The message likewise uses a five-second interval for the initial observation, with another brief interval associated with disappearance. The poor-quality continuation contains additional duration and direction entries. These should not be combined into a precise, independently timed flight reconstruction.
A short visual interval is enough to leave a memorable impression, especially when a flash illuminates an aircraft. It supplies much less information about distance. Neither the released summary nor the message provides a measured range to the light. An angular movement across the sky therefore cannot be converted from this file into a reliable physical speed, size or acceleration.
The radar entry does not establish a pursuit
The card has both air-visual and air-intercept-radar boxes marked. Its narrative, however, describes a navigator noticing a jamming pattern roughly ten minutes before the sighting. The message makes the same chronological separation. There is no reproduced radar photograph, successive range-and-bearing plot or continuous sequence linking the interference to the orange light.
The report is therefore evidence that a radar interference observation was included in the case, not evidence that a controlled craft jammed the aircraft. Temporal proximity alone does not identify a common cause. Nor does the presence of radar aboard a military aircraft turn an unmeasured visual description into a radar-confirmed trajectory. The file should be read at that narrower level.
The feature seen about an hour later
The crew also reported a faint outline interpreted as either a vapour trail or high cirrus after approximately another hour on course. They associated it with what they thought had been the relative position of the original object. That is an attributed comparison made after a substantial interval, not a continuously observed trail connecting two measured positions.
The original wording offers alternatives for what the feature was. It would be misleading to turn that uncertainty into a confirmed exhaust plume, or to use it to reconstruct a route for the original light. The surviving material does not identify the feature through a photograph, meteorological analysis or a second aircraft’s observations.
How the investigation reached a meteor assessment
On the record card, the checked conclusion is the astronomical-meteor category. The accompanying comments consider a competing possibility: a fragment associated with Sputnik 1, which the evaluator understood to have decayed around that date. That passage records an investigative hypothesis. It does not provide an orbital calculation identifying the light as a particular satellite fragment.
The evaluator favoured a meteor because the observation was brief and the reported appearance lacked the flaking or breakup expected in the satellite-decay alternative being considered. The comments describe a meteor as more probable. Thus the form’s categorical box and its more cautious explanatory prose should be read together. Neither supports presenting the file as an officially unexplained alien encounter.
Earlier uncertainty and later classification
The military message records an earlier intelligence assessment that no definite plausible explanation had been established. It also speculates about a remote connection with claims concerning Egyptian weapons capability. Nothing in the message demonstrates that connection. A speculative sentence in a preliminary report is not a verified weapons identification.
The later record card supplies the meteor classification. Preserving both stages explains how an initially uncertain report could enter an investigation and subsequently receive an ordinary astronomical explanation. Selecting only the preliminary uncertainty would suppress the outcome. Selecting only the conclusion would conceal the unusual details that prompted the inquiry.
Where the aircraft was reported
The continuation gives the observer’s position as 23°54′ north, 22°13′ east. The record card labels the location as over south-western Libya. Those two geographical descriptions do not agree neatly: the supplied coordinates are in Libya’s southern interior, well towards the country’s eastern side. This entry follows the explicit coordinates for its approximate map reference and preserves the broader archival label as a source discrepancy.
Map location
The pin at approximately 23.90°N, 22.22°E is rounded from the aircraft position stated in the original message, PDF page 3. It marks the reported observer area, not the light’s position, an impact site, a radar return or a recovered object. The source supplies no verified ground destination. This is a historical airborne report, not a visitor attraction or an invitation to enter remote land.
Assessment and sources
The case documents a military aircrew’s short observation, a separately timed radar interference report and an investigation that favoured a meteor. Its importance is documentary: the original file lets readers distinguish the observers’ impressions, an early speculative intelligence response and the final classification. No photograph, recovered material or independently measured flight path is supplied.
Sources checked: the released four-page military file, including visual inspection of the record card and both message pages; NICAP’s catalogue entry as a finding aid; and the US government’s explanation of federal-work copyright for the record-card illustration. The handwritten evaluation is difficult to read and has not been used to supply additional factual details. No original radar log, complete aircraft log or satellite trajectory was inspected. Checked 10 November 2026.