This NEO came within 0.00027 AU (0.105 LD) at 17:40 UT today. At that time, it was moving through Scutum at 23.8"/sec. The peak brightness predicted by ST4v was 13.2 magnitude. The estimated size is 3-8 meters.

This NEO was first detected at Mt Lemmon on May 26 when it was 22.3 magnitude. It was just added to the MPC's NEAs at Today's Epoch datafile today, so not chance to give a heads up. Since it would have been above the southern hemisphere clouds anyway,  .

Phil S.

Hi MP Hunters,

It seems like the MP cards are stacked for the southern hemisphere, but the weather gods really have your number. Here's another one.

Peak brightness is estimated to only reach 16.6 magnitude which is too faint for a 13" scope but possibly imageable. It's moving very fast (338.3"/min at close approach of 321.1k km) when it will be in Centaurus.

Here's an ST4v IA finder chart for the night of May 30-31 in Brisbane, AU: [attachment=2390]

The track is close to Omega Centauri ~2100 on May 30.

Good hunting & clear skies,

Phil S.

I noticed that the iTelescope data has been updated. Thanks, Greg. 

I looked at the T68(NM) scope & it has an Astrodon OIII 3nm filter, only. This scope used to have a one-shot color camera. This was the designation it was given to distinguish it when it was located in the Bathhurst site in AU several years ago.

The other T68 is listed as being at New Mexico Skies.

I was wondering which is the proper one to use going forward? Didn't they make this scope free to use for short observing runs?

Phil S.

This NEO is predicted to make a close approach on June 3 04:14 UT. Using ST4v, I predict that the peak brightness of 16.0 magnitude will occur around midnight EDT on June 2 when it will be in Scorpius passing between Antares & M4. This should make for an interesting image, if Antares doesn't blow everything out.

Here's the ST4v IA chart for this close approach: [attachment=2387]

At least the MP's field will be easy to spot.

Phil S.

This NEO is predicted to reach 16 magnitude on May 26 to 29 with peak brightness of 15.8 magnitude from the morning of May 27 through the morning of May 29 EDT. Minimum Re is 0.03 AU. The motion is predicted to be up to 34.8"/min.

It will move through Ara, Telescopium, Pavo, Indus & Tucana.

I know that you folks down under have been experiencing crap weather, but maybe you can catch a break for this one.

Phil S.

I am just starting to use this product today so bear with me as I continue to learn this product.

I have my Target List specified as 'Messier' yet I see objects for the winter listed.  How can I tell SkyHound to only list certain objects this type of year using some kind of filter?

Thanks.

These objects are too faint to detect visually, but 4 newly discovered NEOs will make close approaches today & tomorrow. The minimum distances range from 0.00364 AU for 2022 KK to 0.00644 for 2022 KX. The NEOs 2022 KY (0.00541 AU) and 2022 KZ (0.00620 AU) are the other two.

The times for close approach range from May 24 18:21 UT to May 25 19:59 UT.

It's unfortunate none of these are bright enough to be visible.

We missed the close approach of 2022 KG1 which was discovered after its pass on May 22. ST4v predicted a peak brightness of 14.6 magnitude with the best views in Australia & New Zealand. This was a screamer - >20"/sec at 73.7k km.

At least it didn't hit us.

Phil S.

SINCE THIS MAY BE OF INTREST TO OTHERS ON THE FORUM - BELOW IS MY ORIGINAL EMAIL TO SUPPORT:

I am new to Astrophotography and am beginning to use iTelescope. My belief is that the use of Sky Tool 4 Imaging is the best way to plan to make the best use of the subscription fee. I have been able to determine how to set up most items in an plan to be submitted to iTelescope; but am uncertain how to determine the need to select Autoguide for a specific telescope. Is this already selected in the configuration for a telescope and will automatically be set for a plan; or do I need to determine that this needs to be set and manually check to enable? If I need to manually select, any guidance on how to determine if a telescope requires Autoguide would be appreciated.
 
My thanks for an excellent product and I look forward to many fine imaging projects.

AND HERE IS THE EXCELLENT RESPONSE:

Most options are built into the imaging system settings, but Autoguide is one of the exceptions (to enable more flexibility). The best way to determine if a given iTelescope requires the Autoguide selection is to look at the description of the iTelescope on their web site.

Unfortunately this information has been getting harder to find over time (it used to be an obvious top level menu selection), and worse yet, its starting to be placed in multiple places on their system, so finding it can be inconsistent.
 
The most reliable way to find the information for an iTelescope is to log into the iTelescope itself, like you were going to make a reservation or control it. On the top left there is a menu item that reads "Telescope Info."
 
That same info appears to be linked here:
https://support.itelescope.net/support/solutions/161305
 
Once you find the information page you may need to read the operation notes for clues. Also look for a line like this:
 
"*Guiding*: MOAG with Loadstar SX2"
 
This means it has an autoguider and the Autoguide option must be enabled.
 
You can usually get away with assuming that the Autoguide option should be turned on. In almost all cases, if there is no autoguider available, it will simply ignore the command.  But it is safest to o only enable it when necessary. Once you make this selection for a given imaging system on the Scheduler it will remember it for the next time.
 
The ones that don't use autoguiding are generally the Planewave scopes, such as T30, T17, T24, T21, T11, etc. Their mounts are so good that they can track for up to 10 minutes with need to guiding.

How do I import the itelescope Imaging systems into the software.  I cant seem to find this information.  Thanks,  Mike

The CNEOS website reports the close approach (0.00982 AU) at 15:54 UT on 2022 May 22. I wasn't able to download elements for this object from MPC this evening. The H=25.4 & the 'Rarity'=0 so it's probably too faint for visual observation anyway.

Just wanted to alert folks in case someone wanted to give it a try.

Phil S.