AOP Home | Calendar | History | Sitemap

Ephemerides, Star Charts, Orbital Elements

Ephemerides

The following ephemerides (for Vesta, but the others are similar) were generated using the JPL HORIZONS system web-interface using the following settings:
Ephemeris Type: OBSERVER
Target Body: Asteroid 4 Vesta
Observer Location: Geocentric [500]
Time Span: Start=2007-03-01, Stop=2007-09-30, Step=1 h
Table Settings: QUANTITIES=1,8,9,19,20,24

Users may wish to generate an ephemeris for their specific location and only for the times when the asteroid is above their local horizon and it is dark. Check out our sample ephemeris to learn how to read and interpret these files.

[These are text files. For printing, you may want to use landscape mode.]

Vesta Ceres Hartley 2 Other targets?
  • Ceres is on the far side of the sun and not visible. Check back in Aug.
  • Although just past opposition, H2 is just past its aphelion which is still outside of Jupiter's orbit, so the comet is extremely faint.

Star Charts

month comments click for larger image
May
About the Charts

Charts were generated using Starry Night Pro Plus 6.0.4 with some edits in Photoshop 7. These charts are just to help give you an approximate idea of where Vesta is in the sky. To get a better fix on the position for your specific location, we suggest you generate an ephemeris for your location or use your own planetarium software setup for your location to pinpoint Vesta.
For printing, use landscape mode.

Table 1: Charts for finding Vesta May-??? 2008.


Orbital Elements

asteroid 4 Vesta

(from Near Earth Object Program)

dwarf planet 1 Ceres

(from Near Earth Object Program)

comet 103P/Hartley 2

(from Near Earth Object Program)
e = 0.08917470816259512 e = 0.07954161506135105 e = 0.69956649628178
i = 7.135204818979962 deg i = 10.58640384320169 deg i = 13.6074278759628 deg
q = 2.150541291648723 AU q = 2.546707459331833 AU q = 1.03718776080353 AU
w = 149.8395377586268 deg w = 72.96456891897816 deg w = 180.8999472824022 deg
a = 2.361090881996088 AU a = 2.7667817480978 AU a = 3.45230391406786 AU
node = 103.9146381259298 deg node = 80.40698745705932 deg node = 219.8645896063065 deg
Q = 2.571640472343454 AU Q = 2.986856036863767 AU Q = 5.867420067332191 AU
M = 90.53975325026667 deg M = 301.6548489618294 deg M = 51.78529176268474 deg
P = 3.63 yr P = 4.60 yr P = 6.41 yr
n = 0.2716658308203709 deg/d n = 0.2141616581891594 deg/d n = 0.1536528226995956 deg/d
TP = 2007-Jun-15.72380926 (2454267.223809259131) JED TP = 2009-Feb-10.43509194 (2454872.935091937124) JED TP = 2004-May-17.97207658 (2453143.472076575974) JED

Table 2: Table containing the orbital elements for Vesta, Ceres and Hartley 2 for input into personal planetarium programs.


Other Targets to Observe

Although Vesta and Ceres are the targets of the Dawn mission and Hartley 2 the target of the EPOXI mission, there are other asteroids and comets related to the missions that you might want to try to observe! Scientists, engineers, and other staff associated with the missions have asteroids named after them for recognition of work done in the field. And what about Tempel 1, the orginal Deep Impact target or comet Boethin the original EPOXI target? Well, here are the links to get you started. Just use what you've learned about observing Vesta and Ceres and apply it to these.

Dawn asteroids Deep Impact/EPOXI asteroids UM asteroids previous mission targets
other asteroids of interest

Orbital Elements for Spacecraft

The Dawn spacecraft is currently too faint to see. The EPOXI spacecraft had a flyby of Earth on 31 Dec 2007 (and will have 2 more in 2008 and 2009).

On occasion we have provided the elements for spacecraft, but they would be for a given date. Why? When looking for the elements, I found (using the telnet option at Horizons) the elements, but it gave them to me for every day that I had specified during a timespan. So I asked...

Q: Okay, if I'm understanding the output right, the elements for the spacecraft are actually changing continuously so there's not exactly one definitive set of elements?

A: Yes, that's correct. Osculating elements can only represent the position and velocity at one instant.

The spacecraft is continuously acted on by gravity perturbations, solar radiation pressure, maneuvers, etc. Six orbital elements at some instant can't capture this time evolution.

Horizons internally uses the navigation team's trajectory model, which includes such factors. So when you obtain orbital elements over a span of time, each set is the result of accessing the underlying trajectory and converting the instantaneous state into equivalent orbital elements for that instant.

Aside from thruster events (maneuvers), the delta should be small. Suitability depends on how accurate you want the result to be.
Jon G.

About orbital elements

Useful Websites