Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

How to correctly export for Pilot2ATC import?

Featured Replies

Hi Alex,

I would like to import a flightplan into Pilot2ATC that has been created in LittleNavMap that includes a SID, STAR and ILS APPROACH.

In Pilot2ATC, I can only import the following formats:

1. .PLN file
2. From the clipboard in formats shown in the screenshot below
3. From SimBrief directly

Whatever format I try, the SID, STAR or APPROACH are always missing.

I have also posted on the Pilot2ATC forums to see if it is an import issue on their side.

It would be amazing if LNM was an import option in Pilot2ATC for more complicated routes.

Thank you as always for the best flight planner out there!

Toby

format.jpg

Edited by toby23

Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11
Link to my: Dynamic Flight Dispatch Tool

Sorry, don't know Pilot2ATC.

You push you plan to SimBrief (only LNM 2.8 betas) and the download it into Pilot2ATC.

Plain old FSX PLN format cannot transport SID and STAR but this is true for many add-ons. All add-on aircraft I have cannot import only the route. SID, STAR and approach have to be selected manually.

Alex

  • Author

I am just trying to simplify the pre-flight workload which currently involves too much importing and exporting as LNM is the only way to export in the correct format to the Garmin units or the PMS50 GTN unit and it would save time if I could export straight from LNM to Pilot2ATC, including the approach. The option to export to SimBrief works fine but the approach will still need adding. I understand why that is so and guess I will have to just add it manually. Thank you as always for your help and commitment to flight planning in our sims 🙂

 

Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11
Link to my: Dynamic Flight Dispatch Tool

3 minutes ago, toby23 said:

Thank you as always for your help and commitment to flight planning in our sims

You're welcome.🙂

Let me know if Pilot2ATC has it's own flight plan format. Probably mentioned in the user manual.
Maybe I can add something to LNM.

Alex

  • Author

Hi Alex @albar965

The developer of Pilot2ATC said this..

Quote

The P2A "export" format would be what results when you Save the flight plan.  It creates an XML file with the route and all procedures, cruise altitude, etc. so it can be loaded using the Load button with all the details.

I suspect if you email a copy of your Saved sample flight plan to the LNM dev, he could create his export from that and then a "Load" in P2A would bring it in.

Dave

Below in the spoiler tag is the xml code generated upon exporting a sample flight in the Pilot2ATC format .vbf, using the route below taken from SimBrief. I have added the RNAV 06L Approach via MJV transition which is missing from the SimBrief routing:

LEIB/06 LAMPA2F LAMPA LAMPA2M LEPA/06L

Spoiler

<?xml version="1.0" encoding="utf-8"?>
<SerializableFltPlan xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <SerializedSIDPlan>
    <AirportIdentifier>LEIB</AirportIdentifier>
    <Name>LAMP2F</Name>
    <RunwayName>RW06</RunwayName>
    <RunwayTransitionSIDId>0</RunwayTransitionSIDId>
    <CommonRouteSIDId>20254</CommonRouteSIDId>
    <EnrouteTransitionSIDId>0</EnrouteTransitionSIDId>
    <ActiveWaypoints />
  </SerializedSIDPlan>
  <SerializedSTARPlan>
    <AirportIdentifier>LEPA</AirportIdentifier>
    <Name>LAMP2M</Name>
    <RunwayName>RW06L</RunwayName>
    <EnrouteTransitionName>LAMPA</EnrouteTransitionName>
    <RunwayTransitionSTARId>0</RunwayTransitionSTARId>
    <CommonRouteSTARId>16054</CommonRouteSTARId>
    <EnrouteTransitionSTARId>0</EnrouteTransitionSTARId>
    <ActiveWaypoints />
  </SerializedSTARPlan>
  <SerializedAPPRPlan>
    <VectorSetupComplete>false</VectorSetupComplete>
    <AirportIdentifier>LEPA</AirportIdentifier>
    <Name>R06L</Name>
    <Type>RNAV</Type>
    <RunwayName>RW06L</RunwayName>
    <ActiveWaypoints />
    <ApproachTransitionName>MJV</ApproachTransitionName>
  </SerializedAPPRPlan>
  <DepartureAirportICAOCode>LEIB</DepartureAirportICAOCode>
  <DestinationAirportICAOCode>LEPA</DestinationAirportICAOCode>
  <CruiseAltitude>10000</CruiseAltitude>
  <DescentRate>1000</DescentRate>
  <TODDistance>30.5784149</TODDistance>
  <ActiveRouteWpts>
    <FPWpt>
      <TrackCalculated>false</TrackCalculated>
      <TrackDistanceCalculated>false</TrackDistanceCalculated>
      <TagType>NavFix</TagType>
      <TagId>37059</TagId>
      <Type>Named</Type>
      <OwnerType>Route</OwnerType>
      <Identifier>LAMPA</Identifier>
      <Name>LAMPA</Name>
      <Via>DIRECT</Via>
      <Position>
        <Latitude>38.8018074</Latitude>
        <Longitude>1.92405283</Longitude>
      </Position>
      <Passed>false</Passed>
      <Freq>0</Freq>
      <AltitudeConstraint>NoRestriction</AltitudeConstraint>
      <NavFix_Id>37059</NavFix_Id>
      <TargetAltitudeCalculated>true</TargetAltitudeCalculated>
      <FirstAltitude xsi:nil="true" />
      <SecondAltitude xsi:nil="true" />
      <ManualTermination>false</ManualTermination>
      <TargetAltitude>10000</TargetAltitude>
      <SpeedConstraint>NoRestriction</SpeedConstraint>
      <FirstSpeed xsi:nil="true" />
      <SecondSpeed xsi:nil="true" />
      <TargetSpeed>162</TargetSpeed>
      <TargetSpeedCalculated>true</TargetSpeedCalculated>
      <Track>0</Track>
      <TrackDistance>0</TrackDistance>
      <TrackETE />
      <CountryCode>LE</CountryCode>
      <MagVar>1.5</MagVar>
    </FPWpt>
  </ActiveRouteWpts>
  <PlanETESeconds>2013.6</PlanETESeconds>
  <PlanGrndSpeed>162</PlanGrndSpeed>
  <PlanDistance>106.569435</PlanDistance>
  <Name>LEIB-LEPA</Name>
  <Type>IFR</Type>
</SerializableFltPlan>

 

Edited by toby23

Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11
Link to my: Dynamic Flight Dispatch Tool

18 hours ago, toby23 said:

Below in the spoiler tag is the xml code generated upon exporting a sample flight in the Pilot2ATC format .vbf, using the route below taken from SimBrief. I have added the RNAV 06L Approach via MJV transition which is missing from the SimBrief routing:

Thanks for the example. Looks like the file contains some internal information like the IDs which are not know to other programs. No idea if the program can import this if these are omitted.

What about flight plan route description strings which can be exported by LNM to the clipboard?

Alex

  • Author

Pilot2ATC reliably imports SimBrief formatted flightplans with the SID and STAR data and planned cruise altitude intact. It would be great if it could include the LNM added Approach too.

Edited by toby23

Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11
Link to my: Dynamic Flight Dispatch Tool

5 hours ago, toby23 said:

Pilot2ATC reliably imports SimBrief formatted flightplans with the SID and STAR data and planned cruise altitude intact. It would be great if it could include the LNM added Approach too.

What approach? LNM does not include the approach into the route description. Only SID and STAR.

See below from LNM where you can read and generate these route strings:

image.png

Alex

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.