minimoto71
I'm beginning to think the errors are inherent in their coordinate system, not so much the object database. For example, take a target which is not in any of ZWO's catalogs, note it's RA and dec and make a finder chart for it (screenshot off Astrobin or any of several online sources).
In ASIAir, enter the coordinates (either J2000 or JNOW) and press the green GO button. The first attempt is usually well off the real position, possibly half a degree. With repeated attempts it may get close on the 3rd or 4th try.
I first struck this a year ago attempting to find Huchra's object (Einstein Cross) and more recently with Hoag's Object; in both cases the third attempt put it close enough that the star field was identifiable from the finder charts.
I also know the coordinate system in my mount (CQ350) is fairly accurate; entering the coordinates on its handset it nailed the correct position within 5 arcmin first try.
What's unclear to me at the moment is how much of the coordinate conversions ASIAir is doing internally, vs relying on the mount to execute GOTO's using its coordinates. Given the mount is PARK'd I suspect ASIAir is doing the maths.