January 18Jan 18 I am new to Little Navmap but I am slowly learning it and loving it. I am also slowly learning how to fly. I started out learning how to do IOLS approaches and was able to producr proper flight plans and fly them successfully. Now I have moved on to learning how to do RNAV approaches. Pretty simple process that I think I understand fairly well. However, when producing a flight plan in little navmap for an RNAV landing at the destination, I don't see runways identified as RNAV. I see RNP, and after some reading on the internet, I thought RNP is how Little Navmap specifies RNAV runways. But when I try to use one in my flight plan and then fly the plan, I don't seem to ever be able to hit the VNV button on the G1000 and get VPATH to come on in the PMD display. That makes me think I have not actually specified am RNAV runway. Obviously, you can tell I am confused and would love someone to explain to me how to properly identify RNAV runways in Little Navmap and if the RNP designator is actually for RNAV, then am I never able to hit the VNV button and get it to activate? On another note, I have had the hardest time getting the .pln files from Little Navmap to load properly. Runways and other stuff never seen to load correctly. However, I read in an internet thread that if you export the plan into Simbrief and then load it from there in the sim, it will load correctly. I have found that in mosat cases this actually works. Not sure why just loading the .pln file directly has so many issues. Your help understand the RNAV part of building Little Navmap flight plans would be greatly appreciated. Thanks all .... Rob Case: (Lian Li PC-011 Dynamic XL), PSU: (MEG Ai300p pcie 5 & ATX 3.0), Motherboard: (ASUS TUF Gaming x670E-PLUS WIFI 6E), CPU: (AMD Ryzen 7 7800-X3D) Memory: (G.Skill Trident Z5 NEO RGB Series 64GB DDR5 6000), GPU: (Zotac Gaming GeForce RTX 4090 AMP Extreme Airo). CPU Cooler: (ASUS ROG Strix LC RGB 360) Fans: (7 Corsair LL Series 120mm RGB)
January 18Jan 18 RNAV approaches are listed in the procedure tree and are attached to the respective runway. See for 07C at EDDF below: RNP is required navigation performance and an attribute of an RNAV approach. Not all RNAV approaches provide a vertical guidance (VNAV). Currently LNM does not show which one. 1 hour ago, Rob G said: On another note, I have had the hardest time getting the .pln files from Little Navmap to load properly. Runways and other stuff never seen to load correctly. This depends on the simulator and stock or add-on aircraft. MSFS has its own issues loading plans. Often you have to change the runways manually in the sim. Procedures and their runways should load fine (mostly). Parking positions as start are normally ok. Alex Alex' Projects: Little Navmap
January 18Jan 18 Author Thank you very much for your response. Much appreciated. Case: (Lian Li PC-011 Dynamic XL), PSU: (MEG Ai300p pcie 5 & ATX 3.0), Motherboard: (ASUS TUF Gaming x670E-PLUS WIFI 6E), CPU: (AMD Ryzen 7 7800-X3D) Memory: (G.Skill Trident Z5 NEO RGB Series 64GB DDR5 6000), GPU: (Zotac Gaming GeForce RTX 4090 AMP Extreme Airo). CPU Cooler: (ASUS ROG Strix LC RGB 360) Fans: (7 Corsair LL Series 120mm RGB)
January 19Jan 19 Procedures are a complex topic. Here is more information from the user manual: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/APPROACHES.html There is also a IFR tutorial that shows how to build and change a plan: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/TUTORIALS.html Hope this helps. Alex Alex' Projects: Little Navmap
Create an account or sign in to comment