Hi Ben,

General-purpose comments about things that can cause Guide to
appear to have errors of this sort for solar-system objects are at

http://www.projectpluto.com/faq_curr.htm#positions

I've a slight edge on others reading this list: your address is
in my mailing database, and I was therefore able to enter your ZIP
code under "Settings... Location... Enter Location Name." (Guide
will recognize a five-digit number as a US postal code, and a
three-digit number as a Minor Planet Center observatory code.
Persons outside the US are not so fortunate; I don't have lists of
postal code vs. lat/lon for the rest of the world.) The resulting
position was W 89.90, N 35.11.

Using this, and setting the date to 22:53 CDT on Sunday, 2 June
(a.k.a. 3:53 UT on Monday, 3 June), I get Iridium 32 as being at
altitude 11.2 degrees, azimuth 47.8 degrees. Since you mention
"Sunday, 3 June" in your message, I'd recommend checking the
date/time in Guide. Also, it would be good to right-click on a
satellite, then "more info", and look at the "epoch of elements"
to make sure that it is at least reasonably current.

A few nights ago, I set up Guide to show a full-sky overhead
view with satellites to mag 4.5, and went outside with binoculars
and tracked a few as they went by. This is not a wonderful test of
accuracy, since it's at the level of "Satellite X should be going
past Gamma Boo right now... yup, there it is." More precise tests
done by others show a good match to actual satellite behavior.

-- Bill