Garmin G5 Static - Altitude

[Desert Rat]

Originally Posted by g3xpert

Terry,

While there is a static cal procedure provided in the installation manual, you should not have to perform it right out of the box. Reach out to us via email at G3Xpert@Garmin.com and we can get an exchange set up for you if you would like.

Thanks,

Justin

Thanks, but I'm not the original poster, just an interested bystander

[BASE1127]

I'm having the same issue with my G5. It's off by about 90'. Is there really no way to calibrate the Kolsman window without doing a full static recalibration? Can you not just program an offset?

[Mark Burns]

Originally Posted by BASE1127

I'm having the same issue with my G5. It's off by about 90'. Is there really no way to calibrate the Kolsman window without doing a full static recalibration? Can you not just program an offset?

+1
Help us Garmin

[Mile High Relic]

I recently installed a pair of G5's and there is about a 60' difference between the altimeter and the G5.

I'm planning to fly tomorrow to a different airport so I'll have another datapoint.

OP, thanks for posting this.

Edit: Didn't realize this was a 2 year old thread until after I posted.

[Walt]

Originally Posted by BASE1127

I'm having the same issue with my G5. It's off by about 90'. Is there really no way to calibrate the Kolsman window without doing a full static recalibration? Can you not just program an offset?

Originally Posted by Mark Burns

+1
Help us Garmin

Originally Posted by Mile High Relic

I recently installed a pair of G5's and there is about a 60' difference between the altimeter and the G5.

I'm planning to fly tomorrow to a different airport so I'll have another datapoint.

OP, thanks for posting this.

Edit: Didn't realize this was a 2 year old thread until after I posted.

Having done tons of alt checks and calibrations, I don’t think an offset is a great idea as it offsets the entire range. Some other vendors offer that but I often end up with a full cal if I dial in an offset on the ground.

I’ve done lots of G5’s and don’t recall ever seeing a large error (maybe 40’ max) so I’d be a little suspect about the reference you’re comparing it to.

[jeffw@sc47]

I have a G5X and a GDU465. Current flight hours 45.5.

Current display check.
Baro setting: Displayed Alt:
G5X 30.10 890
465 30.10 930 -- 40' difference

Baro setting: Displayed Alt:
G5X 29.92 730
465 29.92 765 -- 35' difference

If I only had the 465 it would be perfect, I rely on the 465 which is consistent with the airfield elevation. I consider the G5 as a backup and would add 40' if I was relying on it.

[Mile High Relic]

Originally Posted by Walt

I’ve done lots of G5’s and don’t recall ever seeing a large error (maybe 40’ max) so I’d be a little suspect about the reference you’re comparing it to.

The reference might be the issue for me. I flew to an unfamiliar airport and the G5 was dead on the published airport altitude at 5150 using the local AWOS barometric reading. My altimeter and RMI uEncoder both read something different.

My home airport (KBJC) elevations range from 5566' all the way to 5673', depending on location, so I'm not even sure what the exact elevation is at my hangar.