I created a low level IFR flight-plan using LNM and I load the flightplan in MSFS via the more>load flight plan and although MSFS world map shows the flight plan correctly the flightplan on the MFD seems to display a return flight.

Please view the following screen images and advise if I am doing something incorrectly or just don't understand something.

Thanks

 

 

Can you post the flight plan (https://www.avsim.com/forums/topic/605519-how-to-post-a-screenshot-or-files/)?
With Navigraph update?

MSFS is a bit touchy when setting a departure or approach runway in LNM. It seems that the waypoints are too close.

Alex

Hello Alex

Firstly this same problem I have experienced with more than one flight plan and both are from airports with no SIDS and both flight plans are to the same arrival airport which does have STARS.

 

However I think that it could be caused by the fact that both flight plans are short (abt 100miles) as I just created another flight (which is much longer) also from an airport with no SIDS but to the same airport with STARs and there was no problem. Looking at the cruising altitude, which I failed to notice and correct before, it is 30000. 

 

Here is the flight plan (with the problem)

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>YMRY to YSCB</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>30000</CruisingAlt>
        <DepartureID>YMRY</DepartureID>
        <DepartureLLA>S35* 54' 7.20",E150* 8' 41.63",+000016.00</DepartureLLA>
        <DestinationID>YSCB</DestinationID>
        <DestinationLLA>S35* 18' 25.00",E149* 11' 42.03",+001869.00</DestinationLLA>
        <Descr>YMRY, YSCB created by Little Navmap 3.0.5</Descr>
        <DeparturePosition>36</DeparturePosition>
        <DepartureName>Moruya</DepartureName>
        <DestinationName>Canberra</DestinationName>
        <AppVersion>
            <AppVersionMajor>11</AppVersionMajor>
            <AppVersionBuild>282174</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="YMRY">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>S35* 53' 51.99",E150* 8' 39.98",+000016.00</WorldPosition>
            <ICAO>
                <ICAOIdent>YMRY</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="RW363">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>S35* 51' 11.90",E150* 9' 26.67",+030000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>RW363</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="YSCB">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>S35* 18' 25.00",E149* 11' 42.03",+001869.00</WorldPosition>
            <SuffixFP>Z</SuffixFP>
            <ApproachTypeFP>ILS</ApproachTypeFP>
            <RunwayNumberFP>35</RunwayNumberFP>
            <ICAO>
                <ICAOIdent>YSCB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>
 

John

 

 

Edited June 28, 20241 yr by Jarnie
types

Thanks for the plan, John. I did not check on MSFS yet (not at my flying computer now) but did you try without setting a departure runway in LNM? This means that you should *not* use "Set runway for departure airport ..." since this function adds a user defined waypoint RW363 which might be too close to the airport.

Alex

 

I played around in MSFS with this plan. The loading screen shows all plans ok but the G1000 breaks it. Removing the departure runway does not help. only removing the approach show the plan ok.

If I add the approach from within MSFS it shows the strange return path again. Sorry, I cannot do much about this.
Another case where MSFS cannot even digest its own plans.🤷‍♂️ 

Alex