Airspace update - latest file corrupt for North America?

[John Johnson]

My LX9070 had an airspace update today which seems corrupted.  For examples, the Tucson Class C boundaries are extremely wrong now and the Ryan Class D is missing.  The file date is a few days old (3/4/26 I think).  

Anyone else seeing issues?

Is there a way to revert to the prior file?

thx, JJ

[Paul Remde]

Hi JJ,

I haven't heard any other complaints about that - yet...  Make sure you have those airspace types both enabled and with a large setting for the scale.  Go to Setup, Graphics, Airspace and Notams, and select the desired airspace type.  Then adjust the zoom to a large number, like 500 miles.  Sometimes those number default to a small number, like 35 miiles, and then they don't display on the map when the map is zoomed out. 

Best Regards,

Paul Remde

Cumulus Soaring, Inc.

[John Johnson]

Thanks Paul.  I've already verified the airspaces were enabled in graphics / map settings.  I'll check the zoom settings today.  

A number of odd things showed up in flight yesterday.  For example, my waypoint and airport labels ranged in size from 6 characters (which is the setting I use for all) to very large (like 20 characters).  There was no pattern (airports, outlanding places, waypoints all had a variety of character lengths).

The other odd thing is I didn't get a 'Restart Optimization?' query with an ENL event despite ENL showing up properly in my log.

My Profile and Waypoints files are all older from last summer so no changes in them.

My LX seems to be in a bad place but all was well before yesterday.  I'll try moving back and forth with an older Profile and see if that helps.

thx, JJ

--
You received this message because you are subscribed to the Google Groups "LXNav Soaring Glider Equipment User Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lxnav-user-gro...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/cef4bb8b-0925-45ce-8185-8b16b8239873n%40googlegroups.com.

[Paul Remde]

Hi John,

Regarding the different airport name lengths.  I recommend turning off the display of "Airports" by going to Setup, Files, Airports.  The LXNAV Airport database isn't needed in the USA - as long as your "waypoint" file includes all the airports.  

Best Regards,

Paul Remde

Cumulus Soaring, Inc.

__________________________________________________________

[John Johnson]

Hi Paul,

  I spent 1 1/2hrs checking settings on the unit and found them as expected.  I finally renamed the local profile file on the unit and then downloaded and installed the very same file from LxConnect on my google drive.  That corrected all issues except the missing and corrupt airspace mapping issue.  Apparently, the profile settings were corrupted even though both the unit's local file and cloud version had the same date/time code.  I never let the profile file sync automatically as I want new filenames for any changes I make.  So, something corrupted and downloading and selecting the 'same' profile file from LxConnect fixed things.

  On the airspace corruption, it tries to update airspace everytime I turn the unit on.  The result showing on airspace files page is a selected (check marked) but greyed out file called 'namerica.lxa' with 'file not found' text under it.  There is also an unchecked file named 'North America'.  When I remove the check from the namerica.lxa file and select North America, the greyed out filename disappears.  My guess is the update file never installs or stalls - something like that.

  At this point, I tried forcing database updates and chose 'All' but the result is the same.

  2 questions:  

  1. Is trying the factory reset a practical option?  Can I recover relatively easily once I re-establish wifi and LxConnect is online?

  2. My glider was in the shop and idle for 8wks - is there a battery that might have depleted and caused these corruptions during that time?  My LX9070 is older gen3. 

after the airspace update completes:

thx, JJ

To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/9b5eb62e-b385-47dd-984c-072e9ce88d4an%40googlegroups.com.

[Morgan Hall]

I had my 9070 ask to update the airspace today and I let it.  As I approached Santa Barbara Airspace I noticed that it wasn’t showing at any zoom levels. 

I used ForeFlight on my phone to make sure I stayed clear of the Charlie airspace. When I got higher later, I double checked my files and found the old file listed as “file not found” and the new file unchecked. 

I checked the box and as soon as I returned to the map, it showed me inside the airspace.  

Somehow it had the airspace flipped 180 degrees.  The SBA airspace has a semi-circle shelf that goes out over the ocean but it stops at the mountains which are nearly 4000ft. 

For me, it was flipped with the shelf on the north side of the airport rather than the south side.  

I also noticed later in the flight that the Santa Maria Class Delta was missing.  

Something is funky with the airspace file or the way it loaded.  

I didn’t have a chance to reboot after landing and see if it corrected itself.

Somwthing funky with the update it seems.  I guess I’m glad I wasn’t the only one.  

Morgan

To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/CABr-ZcBCjfRs_aN9sPmJcd08m4mAPpZxP3Ju%3DLm6w_bLYN4M7A%40mail.gmail.com.

[Paul Remde]

Hi,

I'm sorry to hear about the issue.  I have reported it to LXNAV.

Best Regards,

Paul Remde

Cumulus Soaring, Inc.

[Nelson Howe]

Yeah, I had it two days ago.  Half way through my flight I realized airspace wasn't being displayed.  I finally found the unchecked file and the grayed out file.  I was too busy to be sure the displayed airspaces were correct.  I had modified my profile and uploaded the new version before takeoff as well as loading the new airspace files.  I attributed the problem to the profile change.  Apparently I was mistaken. 

[John Johnson]

Well, I'm glad to hear this isn't just an issue with my unit.  With my corrupted profile confusing things, I thought I had a more serious problem. I'll refrain from any further machinations while LxNav sorts this out for us (I filed a report with them as well).  Tucson XC looks good today - backup is Navigator running on my phone.

thx, JJ

--

You received this message because you are subscribed to the Google Groups "LXNav Soaring Glider Equipment User Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lxnav-user-gro...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/f96e6701-faa7-4dd1-8e03-eeba548c6dffn%40googlegroups.com.

[Ramy Yanetz]

I always use the airspace database I download from soaringdata.info

Years ago I tried the LXnav airspace database and found issues which I cant recall exactly. I think It was lacking some of the information like frequencies to call for clearance, not sure. 

In any case, you can download your own airspace file from soaringdata.info. 

Ramy

[Morgan Hall]

Thanks for the reminder.  I've never noticed a problem before using the LX data, but having a backup would have been nice.  Thankfully it's not complicated airspace and easy to avoid with Foreflight, but I'll download a backup file as a precaution.

Morgan

To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/474b2002-3e3f-4a87-a2ac-b2054fd0eec6n%40googlegroups.com.

[John Johnson]

I'm at the field on my phone.  Is Lx using cub or sua file types?

thx, JJ

To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/CAPaUW1Rz14_O4sG2dzEG-obyXuGjP5PzmkDJB9Xnqq86kK2sjw%40mail.gmail.com.

[John Johnson]

Thanks Ramy!  That got my map airspaces back up. ( cub file format )

thx, JJ

On Sun, Mar 8, 2026, 9:46 AM Morgan Hall <mor...@gmail.com> wrote:

To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/CAPaUW1Rz14_O4sG2dzEG-obyXuGjP5PzmkDJB9Xnqq86kK2sjw%40mail.gmail.com.

[Ramy Yanetz]

Sorry for late reply. Yes CUB. Glad that works for you. I will be curious if you see difference from the LXnav airspace (when it is working fine). I recall that when clicking on the lxnav airspace it did not provide all the info but this was more than 5 years ago.

[Paul Remde]

Hi,

I just learned from Uros at LXNAV that a new U.S. Airspace file has been published.  There had been a issue during the conversion process.  

Note: I don't think this issue has ever happed before.  I'm glad that users made the issue known, and that LXNAV fixed it quickly.  

Best Regards,

Paul Remde

Cumulus Soaring, Inc.

[Morgan Hall]

That's great. Nice quick turnaround.  Also good of Ramy to remind about the US airspace option to have as a backup.

Morgan

To view this discussion visit https://groups.google.com/d/msgid/lxnav-user-group/c47f775a-d426-4cad-b787-56a0cf4658b9n%40googlegroups.com.