What's new
Van's Air Force

Don't miss anything! Register now for full access to the definitive RV support community.

ADS-B altitude reporting

NYTOM

Well Known Member
Have a FreeFlight (new) ADS-B working with a GTX 327 (used) and a Trans-Cal encoder(new). Noticed today when I checked todays flight on FlightAware that my altitude was a LOT lower than what I was flying. Like a thousand feet! :eek:
I installed all this equipment myself and it has been fine for three years and gone thru two VFR checks at the local avionics shop. :) Just did a performance check on the FAA site now and came back fine. :) Any advice or tips on what I can check before I make a appointment at the shop, have to wait over a month and then possibly have to give up my first born to get this corrected? :eek:
 
Might help someone else.

Since no one had any suggestions I did some searching and on the Mooney site found that a common problem with erroneous readings is poor pin connections due to corrosion/ dirt & vibration. Takes 10 separate connections just to transfer altitude reading. Suggest contact cleaner, especially on slide in transponder connections and encoder plugs. Other common problem is connection to static is incomplete or has leaks. Thought this info might at least help someone and give them something to try before a $$$ trip to the avionics shop. :)
 
Flightaware

I would not put so much faith in what they report. Before spending a dime, go fly, ask approach, center to verify what they see. Not sure about your adsb device, but if it is UAT, then accurate reporting isnt always available via Flightaware. 1090s systems are generally accurate as seen by Flightaware.

Flight aware reports altitude at 29.92 barometer. Recent flight @ 5500’ reported by Flightaware 5125’
 
Asking ATC is the easiest way, it's the only way to know their local altimetry from QNE FL.

Grounds are every bit as important, hopefully all involved are common to a forest of tabs.

You can check your own datastream with free Fltplan Go by long touching your aircraft symbol if you have an ADSB-In device.

You can buy a 978 MHZ SDR dongle and antenna if you have a device that supports it. Android has good freeware, not all Androids support USB dongle/On the Go/OTG.

$40, used to be $20. Easier to ask ATC

NESDR Nano 3 OTG - Premium Tiny RTL-SDR Bundle for Android and Other USB OTG (microUSB) Host Devices. RTL2832U
 
NEVER use FlightAware, SkyRadar and other INTERNET sites to verify your ADS-B reported altitude. FlightAware, and ALL ADS-B based receive sites, show GPS altitude not Barometric Pressure altitude and they can be quite different. As BH1166 posted:
Flight aware reports altitude at 29.92 barometer. Recent flight @ 5500’ reported by Flightaware 5125’

Ask ATC what they are displaying. THAT is Barometric Pressure altitude and what must be accurate. Also, you ran the FAA ADS-B compliance check and it came back fine which tells me you are chasing a problem that does not exist.

FWIW, GPS altitude is best for not colliding with things on the ground. Barometric altitude is best for not colliding with other aircraft.

:cool:
 
Last edited:
I believe ADSB data includes both GPS altitude and baro altitude. I know foreflight reports GPS altitude for me and for traffic and think that each app can choose which altitude to show on the screen.

It is not uncommon for GPS altitude to be 1000' from baro altitude. If a source is being used for traffic, it is critical to know which altitude is being used. Most integrated systems will be using the same source for ownship and other traffic targets.

Also important to note that baro altitude is sent from your plane at 29.92 and ATC does the correction before displaying it or re-transmitting it to others.

As you can see, there is all different kinds of altitude floating around in the ether, so need to fully understand it before using it.

Larry
 
Last edited:
First of all. I completely agree with not relying on FlightAware or it's competitors for valuable information. The FAA PAPR report is truly the only thing that matters. And understand the PAPR completely relies on the encoded pressure altitude and cannot correlate this with what you altimeter reads.

I have two FreeFlight ADS-B systems installed and they have been rock solid. And, if you have the control head (recommended) it has a digital encoder built in if you want to use it. It's use is optional.

You don't mention what Trans-Cal model you have. I would assume since it is new is has digital RS-232 altitude data to use (one wire connection). Which is the preferred source as it is more precise than the old grey code bundle of wires. Most Trans-Cals have both type of outputs but I think the latest compact model provides digital signal only.

If an aircraft has a G5 I like to use that as an encoder since it can send altitude directly to your transponder/ADS-B system via digital data (one wire). No correspondence trouble when the altimeter itself is the encoder.

The best way to truly check out your altitude is to fly under flight following or IFR flight plan or talk and squawk with an approach/departure controller. If you truly are off 1000' you don't have to ask. They will immediately bring it up to you. ATC does not mind reading back to you your reported altitude.
 
You can have clean PAPRs and useless ATC ADSB!

Until I ran a dedicated ground from firewall FOT to the Skybeacon wingtip- that was my case.

PAPRS read what you put out, but not if it is accurate PA/encoder/Mode 3C!

The PAPR helps with a lot, but not accurate baro alt. Check the max level on top of the PAPR and see if it matches your flight max height in coverage- that's about all it has for height accuracy.

If the OP has the right transcal issue or connection or static error- an IFR pitot static might help.

My plane passed those and was good to FL180, maybe it would help troubleshoot.
 
Last edited:
globe.adsbexchange.com gives all the ADS-B data reported by an aircraft, including baro altitude and GPS (WGS84) altitude.
 
I believe ADSB data includes both GPS altitude and baro altitude.

Yes, but INTERNET based sites show GPS altitude not Barometric. Those few that report Barometric altitude report UN-ADJUSTED Barometric altitude which is based on 29.92" not on your local altimeter setting. Neither of them will be the same as your flying altitude, unless the Altimeter setting where you are flying happens to be 29.92".

This is a separate issue from any static port problem. We have to "assume" the OP has a good static system since it works correctly at times.

The best way to truly check out your altitude is to fly under flight following or IFR flight plan or talk and squawk with an approach/departure controller. If you truly are off 1000' you don't have to ask. They will immediately bring it up to you. ATC does not mind reading back to you your reported altitude.
^^^^^THIS^^^^^

:cool:
 
Last edited:
Thank you

The responses have been very educational. I’m sure everyone is right about the on-line flight reporting services and their lack of accuracy compared to actual flight. In my ignorance I assumed all readings would be close if not the same.:p What brought this all to light was my concern for what altitude others were seeing me at in their cockpits. On nice days it can get pretty crowded on the East Coast and although I don’t totally rely on it , it’s nice to have a second set of electronic eyes watching for traffic. I WILL check it out with ATC on the next flight . :)
 
I think most adsb-in systems don’t display target altitudes. Since adsb data contains both gps altitude and pressure altitude, the system displays an apples to apples difference: either the difference between target gps altitude and on-board gps altitude, or the difference between pressure altitudes. It then displays targets as 100’ higher, 200 ft lower, etc. Either data difference should be accurate, easily understood, and you don’t have to worry about actual indicated altitude.
 
Back
Top