Original diagram by Dark Fires. Schematic, not an observation; not to scale.
A bright light reported in the same part of the sky over several minutes deserves a check against known astronomical objects. A planet identification becomes useful when it predicts the observation’s direction and timing, rather than merely naming a bright object that happened to be visible that night.
Build the prediction from the observer’s position
NASA JPL’s Horizons tutorial describes observer tables for the apparent observing quantities of solar-system bodies. For a terrestrial sighting, choose the candidate body, the observer’s geographical location and a time interval covering the report. A prediction from Earth’s centre is not the same setup as a prediction for a specific observer.
Preserve the entered coordinates, height, date, time scale and output settings. Convert the witness’s local civil time carefully, including daylight-saving rules where applicable. If “about nine” could mean a range of times, calculate the range. A precisely printed table cannot repair an uncertain input.
Compare direction before appearance
Azimuth describes direction around the horizon and elevation describes angle above it. The Horizons manual documents observer quantities and atmospheric-refraction options. Confirm the conventions in the output instead of guessing which direction corresponds to zero degrees or whether refraction has already been included.
Use a landmark, a surveyed camera position or recognizable stars to constrain the recorded direction. Treat an uncalibrated phone compass as an estimate. Buildings and terrain can obscure a predicted object even when its calculated elevation is above a mathematical horizon. A sky application screenshot is helpful only when its location, time and orientation are also preserved.
Compare the full sequence. Does the candidate occupy the reported sector at the beginning and end? Is its slow change of direction consistent with the footage? Does it disappear behind the same obstruction? Agreement across several independent constraints is more informative than a resemblance in colour or brightness.
Avoid forcing a match
Consider a hypothetical report placing a light between 220 and 230 degrees azimuth. A candidate predicted at 225 degrees fits that rough direction; one at 290 degrees does not become a good match merely because it is bright. This example illustrates a test, not an identification of any actual case.
Horizons concerns solar-system targets. It is not a general catalogue for identifying every star, aircraft or artificial Earth satellite in a video. If a planetary candidate fails, document that failure and choose the appropriate tool for another class of source rather than stretching the result.
State what the comparison establishes
Publish the saved query settings and relevant output beside the measured direction and its uncertainty. Use language such as “consistent with Venus within the available timing and bearing uncertainty” when that is what the evidence supports. A strong astronomical match can explain a sighting, but the mere presence of a planet somewhere above the horizon cannot.









