Do you know if any of these fixes have resolved the issue I’ve run into where the MCDU pulls waypoints from a previous session’s flight plan? That may be trickier as I haven’t found a reliable way to recreate it.
Hi! Maybe you know about this one as well. I have this flight plan from Rovaniemi (EFRO) to Gibraltar (LXGB): EFRO/03 OLNOP4B OLNOP DCT SOPLI DCT SUN DCT AGWIM/N0263F220 DCT OGIRO DCT VADIN M852 ALS N872 PAM/N0263F230 N872 LESDO DCT OLZOM DCT DISAK DCT TUDRA DCT OSMOB DCT ARVID T424 PPN N857 NOLSA N10 BAN N857 MONTO N864 CRISA DCT BRIKE DCT LXGB/27 which I created in Simbrief and imported into the EFB Route Planner via the Simbrief EFB app.
Almost everything is OK, but the waypoint VADIN is a bit special. It exists in the enrouteLegs array, but with the type FsEnrouteLegType_LatLon and only a latitude and a longitude. No “VADIN” to be found in there at all.
Do you have an idea what might happen here? I looked up the waypoint in the EFB’s search field and it’s found there as well.
EDIT: Sorry my bad. The VADIN after OGIRO is indeed shown as LAT/LON
The import strangely starts the M852 part at NEGIL which is not even part of the Simbrief flight plan. The other VADIN is in the middle of this part where the route gets back on track. Why? I have no idea. Sorry.
What I would expect it to look like is this:
OGIRO
VADIN
via M852
GODOG
ADSEN
ALS
But I get this instead:
Hans
That was because of not clearing the ini file where I store the temporary flightplan. This is fixed.
Hans
Unfortunately, without the SimBrief code in hand, I can’t really venture a guess. The EFB is really just a 1:1 reflection of what they set with the API (which in JS is the same structs as you would in WASM), it doesn’t do any interpretation or transformation of the route, so my instinct is to say that they may be doing something incorrectly.
Thank you. I will talk to them and see what they can find.
Hans
Did you think WASM crash on clicking GPWS maint page is this import-related?
@SeiteZentaur026 can you reproduce this WASM crash?
I would recommend opening a unique bug report for this issue as it has nothing to do with the flight plan import process in the 2024 ATRs.
I already filled a bug report on the forum.
Then probably best to discuss it there, not this irrelevant thread 
What are the airports in your flight plan?
https://jonbeckett.substack.com/p/programming-flight-plans-in-the-atr
- You can programme flight plans manually directly into the MCDU
- You can programme flight plans via SimBrief, import them into the aircraft tablet, and transfer them to the MCDU.
- You can programme flight plans via the simulator EFB, transfer them to the aircraft tablet, and transfer them to the MCDU.
- You can programme flight plans via the web, transfer them to the EFB, then to the aircraft tablet, and transfer them to the MCDU.
The updated procedure covers all routes.
One thing worth noting - there is a short-coming in the direct SimBrief route at the moment; the aircraft MCDU doesn’t always populate with the full route - only the departure and destination - this can be worked around by generating an OFP in Simbrief, copying the route, and pasting it into the simulator flight planner in a browser - then loading into the EFB, transferring it to the aircraft tablet, and on to the MCDU.
It’s all documented in the guide.
I have just done one MANUALLY. Have you picked airports with arrivals, SID’s, transitions? You have to put in the Departure and Arrival airports first before you put in the waypoints.
Start by
FLPN INIT
route
enter departure and arr icao code
EXEC
Start with SID
click soft key next to destination Airport
departure runway
then click Return
STAR and appr
soft key next to dest airport
approach
desired sid
desired transition
Soft key next to return
Then you key in waypoints into scratchpad
then remove discontinuities by pressing CLR and the soft key next to waypoint you want rid of.
Captures ILS and descends
SIDs and STARs are not intended to come over with import into the ATR to match the kinds of flight route importing that happens IRL where pilots still manually select those procedures.
The ATR72 will accept Simbrief flight plans for the ATR42, and the ATR42 will accept flight plans for the ATR72.
This is a separate issue than what is reported here - I would recommend opening a separate bug report.
Mine freezes up the entire navigational system. I can import manually, but using simbrief and the EFB it locks up. It has not been fixed as of yet.