Gason71

The LNM is very flexible tool, so you can import your airports as userpoints (type "airports") and then display them on the map 😎 For more about CSV format for LNM you can read at point 28.5 of manual: https://www.littlenavmap.org/manuals/littlenavmap/release/3.0/en/USERPOINT.html#csv-data-format I hope this helps you 🙂 Regards, Piotr

Hmm, in my LNM installation there are displayed coords and elevation level when hoover over given point. Have you installed GLOBE Offline Elevation Data database? The description about it is in LNM manual, here: https://www.littlenavmap.org/manuals/littlenavmap/release/3.0/en/GLOBE.html I hope this helps you 🙂 Regards, Piotr

I think you can easily add this VOR as the userpoint by choosing the VOR type in the list. More can be found in the LNM manual under Section 26. Userpoints and subsection 26.2: How to Add Userpoints. I hope this helps you 🙂 Regards, Piotr ps. I forgot about the link 🙂 , here it is: https://www.littlenavmap.org/manuals/littlenavmap/release/2.8/en/USERPOINT.html#

I guess you probably updated the XP11 but didn't update LittleNavmap simulator database. You have to reload library scenery, it's described in point 51.3 of LNM manual, here: https://www.littlenavmap.org/manuals/littlenavmap/release/2.8/en/SCENERY.html I hope it helps you 🙂 Regards, Piotr ps. general info about LNM navigation databases is available here: https://www.littlenavmap.org/manuals/littlenavmap/release/2.8/en/NAVDATA.html

1) NATs explanation: https://occ.ivao.aero/assets/docs/guides/APCGTNAC_EN.pdf 2) NATs daily report: https://www.notams.faa.gov/common/nat.html 3) Skyvector: https://skyvector.com/ IMHO the best option in your situation will be Skyvector map. When you open it, try switch to WorldLo or WorldHi map to see navigation points, then enter to "Layers" and switch "NATs" on (Pacots are also available there). Then you can see enter and exit points from the given tracks. When you'll make right-click on the given point it should display GPS coordinates - what you can use to define your userpoint under LNM. That's all, I hope it helps you 🙂 Regards, Piotr

It's not a LNM problem. You can install any previous LNM version, but it won't work correctly as it's a problem with the FAA charts project. FAA charts were abandoned on the other side (in the last year, if I remember well), and that's why Alex decided to give a warning message. There are more threads about this; look at posts from 2023. Regards, Piotr

You can also use free SKYVECTOR - where are all airways from the current AIRAC database, and then manually add points to the flight plan 🙂 Regards, Piotr

It seems you haven't enabled the "show route" option. Click the button on the right of the yellow star (userpoints) to enable "show route" option 🙂 Regards, Piotr

So, it's not necessary to draw the whole ARC on LNM's map. If you know this technique, you can only choose the entry and exit points in the flight plan and then manually perform whole ARC-DME in simulator 🙂 Regards, Piotr

I'm afraid there is no special tool to draw ARINC procedures. I use circle and measure tool to find circle arc and angles, then manually make route points. It's only an approximation but similar like IRL, when ARC-DME is performed manually with no FMC guidance (GA flight, or old school vintage airliner for example) it's very hard to fly an ideal circle arc :) Regards, Piotr

AFAIK the parking spots aren't indexed in LNM. But when ATC gives you instruction how to taxi, you can follow along taxiways on LNM map and it's easier to find proper parking spot 🙂 It's my method when I fly online. Regards, Piotr

A moment ago I've made some experiments, and I think it's caused by performance parameters in the aircraft profile, so it means the chosen aircraft isn't able to perform this leg. It's because the whole route is only ~6NM long, aircraft has to climb ~1400" up and descent ~1400" down (airport altitude is ~629"), LNM calculates climbing and descending distances based on aircraft performance profile and when isn't able to calculate TOC and TOD, it gives default altitude, in this case 11500" on my side. If you make a fake profile for very slow aircraft with good climbing rate, everything should be OK. Example aircraft performance profile that I've made for these experiments: SUPER ULM - average climb speed: 60kts, avg. vertical climb speed: 600fpm, cruise speed 90kts, avg. desc. speed: 60kts, avg. vert. desc. speed: -600fpm When you set such an aircraft as above** (before importing flight plan from PLN file), your flight plan will be read correctly in LNM with correct altitude 2000ft I hope it helps you 🙂 Regards, Piotr ps. **of course, any other aircraft will be also OK if only will be able to perform this leg 😛

I've got an idea, but never try this kind of trick, so don't know if it'll work. Maybe it's possible to download** from the NOAA weather service manually grib and METAR files to fake XP11 directory and then load them to LNM using XP11 settings in LNM? I notice there is also possibility to load real weather from XP12 directory, but there is more grib files there (LR changed weather engine), so XP11 solution seems better. Does LNM check only winds in .grib and METAR in .txt file from XP11, or it is necessary to download/create another files in fake XP11 directory? Regards, Piotr **downloaded files can be kept in archive, so possible have real weather from any archived day 🙂

I'm sysadmin and using Bitwarden with strong passwords, even don't try to memorize these ... 🙃 Regards, Piotr

After using it for a while, I can say that version 3.0.1 seems more stable than 3.0.0 (the latter did crash a couple of times). Here the same environment as usual - Fedora Linux (F39 now) with the latest kernel. Regards, Piotr PS: I've changed the name of the account because I am unifying the names of my accounts on different sites, but it's still the same person 😁

I think now texting about airspace is okay. The text was prepared for what is defined in ICAO documents as general rules, and IMHO it's a better, universal solution than implementing local regulations, which technically is very tough. It's not so easy with the details 🙂 1) In USA for C and D class airspace, the two-way radio contact is a kind of clearance (FAA rules), and until the ATC responds to the pilot's call, he isn't allowed to enter C or D airspace and has to stay out of it. What's more, in case of first contact, the ATC can also request that a pilot remain clear of the airspace until further instruction to enter, and the pilot has to stay out of the C/D airspace until he's got the command to enter. Only for B-class airspace the VFR traffic has to obtain classical clearance like in other parts of the world. In general, the USA is its own aviation world with FAA-specific regulations and limits. 2) The transponders in Europe (we mainly say about Eurocontrol Space) are mandatory for all flights conducted as IFR/GAT. For VFR/GAT traffic, it's mandatory only for some designated airspaces, e.g., TMZs; it's depicted on the VFR charts (but local regulations can be different). VFR/OAT (military for example) traffic is excluded from these obligations. The colours and borders of airspaces (and some other graphical things on the map) are possible to change by customising the file little_navmap_mapstyle.ini in the user's config directory. Regards, Piotr

I may be wrong, but from the previous posts I’ve understood that Arrex likes this text. He just wants to add something of his own to personalize his LNM. I know that this English text is hidden in the source file maptypes.cpp (I found it today), so this way is difficult to implement for a user, but maybe it’s possible to use the translation mechanism from QT and create a fake language customEnglish with a 1:1 pseudotranslation? In this way, users could prepare their own .ts files for replacement, which is definitely much easier than compiling the C++ source code. However, I have no idea whether this additional “gadget” is worth all this extra work 😛 Regards, Piotr

Aaa, now I remember. On my computer it was also not present after installation. I've manually copied this file to the config directory from GITHUB, exactly from here: https://github.com/albar965/littlenavmap/blob/release/3.0/resources/config/little_navmap_mapstyle.ini Regards, Piotr

1) config files should be in C:/Users/YOURUSERNAME/AppData/Roaming/ABarthel/" on Windows or ~/.config/ABarthel/ on Linux. I don't know how about Mac. 2) Here is my modification for B,C,D,E airspaces that makes LNM map similar to FAA VFR sectional charts: # # little_navmap_mapstyle.ini # ClassBFillColor=#10ce08bf ClassBPen=#185281, 4, Solid ClassCFillColor=#178594ec ClassCPen=#8e2156, 4, Solid ClassDFillColor=#105261ce ClassDPen=#185281, 2, Dash ClassEFillColor=#200aa3c9 ClassEPen=#8e2156, 2, Dash Maybe it helps you 🙂 Regards, Piotr

Ad 1.) if you've looked only at online manual you don't find this, as online manual is available only for _stable_ version - 2.8.12 in this case. 3.0.1 is still beta so you have to look at PDF offline version, it's available under Help menu in LNM. Ad 2.) Only Alex know this, but I suppose it's hard coded. But sources are available on GIT service, so if you only know how to recompile LNM, you can add something to the source files and recompile them 🙂 Regards, Piotr

Ad1) It's still available, only format was slightly changed (pen style was added) -> see LNM manual for version 3.0.1, paragraph 75.3 "Map Display". Ad2) But why? IMHO it's a nice feature which gives the information about airspace restrictions, especially good for newbie pilots 🙂 Regards, Piotr

I use a kind of trick which uses the Navigraph data. When you choose any approach from Navigraph, which ends at the given runway it should display the runway's threshold altitude on the map 🙂 But this trick works only for airports/runways that have stored procedures in Navigraph database. Regards, Piotr ps. BTW when X-Plane data procedures are used, it also displays threshold altitudes, but I don't know how about other simulators, and it seems the Navigraph data are more reliable than from simulator.

I suppose this not problem lack of STAR here, but rather too short distance between KAZMA and RJFT airport. Probably LNM calculates that over fix point KAZMA you are not already on Y40 airway but below its lower boundary. From KAZMA to RJFT airport there is only 18NM distance and probably vertical profile is below Y40 lower boundary here. Try create fake aircraft profile with incredible descent rate (for example 9900 fpm) and low speed (99 kts for example), and switch to this profile before creating the fpl, it should be enough to stay with vertical profile over KAZMA within Y40 boundary and LNM should accept RJAA NINOX Y28 ONDOC Y452 OOITA Y40 KAZMA RJFT as a proper flight plan. I use this trick and it works 🙂 Regards, Piotr ps. previously when you added proper STAR LNM accepted fpl because remained distance to RJFT was enough to stay on Y40 at KAZMA fix.

It's enough switch to option: "Use Navigraph for all Features" and you should get the parking spots that come with the default free Navigraph AIRAC1801 database (or newer if you updated Navigraph database, but this is payed option) 🙂 Regards, Piotr

Usually SID/STAR names are created to avoid confusion with fix point names. Could you give the exactly airport, fix points and procedure names where you get such a confusion? Regards, Piotr