# Bug in Export of VFR Plan fo FS2020

**URL:** https://forum.navigraph.com/t/bug-in-export-of-vfr-plan-fo-fs2020/11003
**Category:** General
**Created:** [February 6, 2023, 7:18am UTC](https://forum.navigraph.com/t/bug-in-export-of-vfr-plan-fo-fs2020/11003 "2023-02-06T07:18:16Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Netdreamer](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/netdreamer/32/11828_2.png) [@Netdreamer](https://forum.navigraph.com/u/Netdreamer)
#### Post date: [February 6, 2023, 7:18am UTC](https://forum.navigraph.com/t/bug-in-export-of-vfr-plan-fo-fs2020/11003/1 "2023-02-06T07:18:16Z")

</div>

Hello, I found a bug (and a possible fix) in the export of VFR plans to FS2020.  
When FP is exported, XML contains:

> \<FPType\>VFR\</FPType\>  
> \<RouteType\>LowAlt\</RouteType\>

When imported in FS2020, it’s then converted to an IFR Low Altitude plan… and every waypoint is lost and recalculated.  
I tried to REMOVE the RouteType, leaving only the FPType, and plan is (almost) correctly imported as VFR Direct-GPS plan.

Tested on this VFR plan in Navigraph Charts:  
LSZA/01 CANE2U.CANNE 461000N0085252E DCT VP498 DCT VP497 DCT VP502 DCT LILO/09  
[LSZALILO.pln](https://forum.navigraph.com/uploads/short-url/mdPK4JfwCarsqH39fFfgrASQY1K.pln) (4.8 KB)  
[LSZALILO-FIXED.pln](https://forum.navigraph.com/uploads/short-url/mFlrml6GLfpxkMLrjCuMd2me6nv.pln) (4.8 KB)

I’m using Navigraph Charts 8.19.0 build 4016136394

---

<div class="post-metadata">

### Author: ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)
#### Post date: [February 13, 2023, 7:18am UTC](https://forum.navigraph.com/t/bug-in-export-of-vfr-plan-fo-fs2020/11003/2 "2023-02-13T07:18:39Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.