That’s why i was asking. If msfs messed up imported flight plan, then why import flight plan in the first place?
I install navigraph navdata. And all I need to do is pick a departure gate, pick an arrival gate. Select IFR, then pick departure pattern and arrival pattern and approach from the drop down list based on the weather and wind direction all from the world map and press FLY.
All the waypoints and flight plans are loaded without USR or weird turnaround. And I always fly without issues. And default ATC never caused me any grief.
The data is not corrupted until MSFS looks at it. I’ve verified that the text route doesn’t contain any weird waypoints in Navigraph, and then when I save the plan and import it to MSFS, the extra waypoints are added. I’ve done this with both Navigraph and MFS (creating the flight plan). From what I can tell, it’s not Navigraph that is messing it up.
I’m glad that your method works for you, but there are other issues that need to be addressed by Microsoft / Asobo.
I mean I’ve done that method myself in the past too. Install navigraph navdata update, then use Simbrief, create flight plan, generate OFP, download .FPLN file, load .FPLN file on the world map in MSFS. They’re generally fine unless you make any slight changes to it, then the whole flight plan will reset. Sure…
But when I compare between the two, loading flight plan from SimBrief, versus creating them from the world map. I just don’t see what value it added coming from SimBrief. Sure the waypoints can be different. But you still fly at the right direction and end up at the destination all the same. And with an assigned SIDs, and STARs, and approaches, those patterns will always follow the Navigraph patterns anyway.
And as long as I have all those patterns set up from the beginning without making any changes in the flight, the aircraft will fly that whole flight plan without problems. ATC will always follow your flight plan anyway, so it’s not like they will give you instructions that will make you change your arrival pattern or approach.
And with a Gate-to-Gate flight plan that is only possible to be done by creating a flight plan using the default world map flight planner, you can actually plan your flight and “choose” which gate you want to park in. The Ground ATC will direct you to that chosen gate, and even in the (pretty frequent) bugs with ATC where you can’t request taxi to the gate, the flight plan to the gate is already loaded as well, and the marshals and ground services would be ready for you at the gate that you chose from the flight plan.
I try to do an IFR flight plan from San Diego area to Burbank (KBUR).
I try to set the flight plan to follow the basic TEC route, something like SNAP 13 or 14, for those who know this.
When entering the route on the startup page, selecting low-level IFR:
The first ‘game’ waypoint is USR1 can not get rid of this. I get this on almost any flight regardless.
Then from the Seal Beach VOR (SLI), I get a spike added to the route from SLI towards KBUR then returns back to SLI area.
Oh man I hate that “manseq” waypoint. I’m not sure if it’s MSFS or the WT G1000NXi doing it, but the aircraft doesn’t ever seem to pick up that first point. Just flies fight in on by, then I have to do a “Direct To” the next waypoint in the flight plan to get it back on track. The workaround works, but why is it missing the waypoint?
Wish there was a way to not auto-generate the route in the MSFS flight plan. I would prefer to have a way that we can “build” the flight plan, or put in the text of the waypoints.
I’m happy MSFS is here, and I’ll keep playing, but flight planning is just one of the areas to be tightened up. I’m glad they do the Dev chats and post the roadmap and such. We’ll keep ‘em busy for a while! (The “voting” system though… I mean if something is wrong and needs to be fixed, who cares if 1 person or 400 vote on it?)
With Navigraph up-to-date ican export flightplan from LittleNavMap, import it in MSFS , change runway to a parking spot and just press fly. 99% of the time works perfectly, it has no problem importing SID and STARS. You could also select just the departure airport and manually input flight plan in the GPS if that’s what you want.
SANP 13: OCN V23 POPPR SMO125 SMO SMO0311 SILEX Altitude is 6000 ft.
(we can not use the victor airways as an input so you have to input waypoints such as SLI)
Climbing out of any of the San Diego airports gives a first waypoint as this USR1 (for me) it is usually a few miles off the end of the departure end of the runway assigned.
I have a number of ORBX airports and free ware installed throughout SoCal (my home turf). But removal of the community folder completely, I still get this waypoint.
I tried just now to replicate the issue… it is not there. First time in months.
Tried inputting flight plan in different way… nothing.
So, now figure out what my quick and dirty varies from the normal and see if I can trigger the problem again.
edit: The first flight plan was Neo4316’s plan with departures, arrivals, and approaches all predefined. I wonder if that cleared some stuck bit somewhere. Whereas I usually do the enter manually. Like I have to do in my own plane.
