Jay Honeck
Touchdown! Greaser!
You would think after over 20 years of flying, and over 5 years of flying on the Texas coast, I wouldn't run into anything new anymore, but yesterday's flight was full of new experiences.
1. First time an entire sector's radar was down. Corpus Christi Approach could give us the barometric pressure -- and nothing else. Their radar was completely INOP.
2. First time hearing Spanish chatter on Unicom. 123.0 was non-stop Espanol. Dunno if it was someone local, or if we were picking up Mexico.
3. First time ADS-B reported another airplane's altitude incorrectly.
Here's what happened with #3: We were coming in to land at our home 'drome, KTFP, T.P. McCampbell Airport. Mary was PIC, and I was watching traffic on our tablet in the back seat, while she was watching it on our EFIS up front. On Unicom we heard a Navy T-34 Turbine Mentor coming in for a low approach to Rwy 31, and it was showing up on both of our screens as "+32" -- meaning it was 3200' above us.
I looked out the window, and there he was, at our altitude, or a bit below. WTH?
Here are the particulars. I was viewing ADS-B traffic on our Nexus 7, using Garmin Pilot and the GDL-39. This is a passive "ADS-B In" only system. Mary was viewing ADS-B traffic a completely independent system: Our GRT Avionics Horizon HXr EFIS, using Skyradar and two aircraft-mounted external antennas. This is an active "ADS-B In/Out" system.
Both systems showed exactly the same thing: The plane was moving on the map, exactly as the plane outside was moving, but it was showing up at 3200' above us.
(Yes, I looked through the bubble canopy to see if there was a trailer 3200' above the other guy. Nope.)
Anyone know how this could happen? Could it be a glitch with the Navy trainer's transponder? Or could it somehow be related to Corpus Approach being FUBAR?
1. First time an entire sector's radar was down. Corpus Christi Approach could give us the barometric pressure -- and nothing else. Their radar was completely INOP.
2. First time hearing Spanish chatter on Unicom. 123.0 was non-stop Espanol. Dunno if it was someone local, or if we were picking up Mexico.
3. First time ADS-B reported another airplane's altitude incorrectly.
Here's what happened with #3: We were coming in to land at our home 'drome, KTFP, T.P. McCampbell Airport. Mary was PIC, and I was watching traffic on our tablet in the back seat, while she was watching it on our EFIS up front. On Unicom we heard a Navy T-34 Turbine Mentor coming in for a low approach to Rwy 31, and it was showing up on both of our screens as "+32" -- meaning it was 3200' above us.
I looked out the window, and there he was, at our altitude, or a bit below. WTH?
Here are the particulars. I was viewing ADS-B traffic on our Nexus 7, using Garmin Pilot and the GDL-39. This is a passive "ADS-B In" only system. Mary was viewing ADS-B traffic a completely independent system: Our GRT Avionics Horizon HXr EFIS, using Skyradar and two aircraft-mounted external antennas. This is an active "ADS-B In/Out" system.
Both systems showed exactly the same thing: The plane was moving on the map, exactly as the plane outside was moving, but it was showing up at 3200' above us.
(Yes, I looked through the bubble canopy to see if there was a trailer 3200' above the other guy. Nope.)
Anyone know how this could happen? Could it be a glitch with the Navy trainer's transponder? Or could it somehow be related to Corpus Approach being FUBAR?