I created a plan from KCNM to KDVT with KPHX as alternate. The plan generates fine in Simbrief but when loaded into LNM, the flight plan destination is changed to the alternate, KPHX. If I eliminate the alternate in Simbrief, the plan loads correctly into LNM. Any idea what's happening here?

Alternates from SimBrief are normally detected.

Can you copy and paste the whole output from LNM here in a post?

Alex

Not sure I was clear. The problem is in the transfer from Simbrief to LNM the alternate becomes the destination. I'll do it again tonight and send the results.

10 minutes ago, loop_n_roll said:

The problem is in the transfer from Simbrief to LNM the alternate becomes the destination.

Understood exactly this. LNM menu "File" -> "Open Flight Plan from SimBrief", right?

I tried to reproduce it here, but to no avail.
Might be a certain flight plan triggering this.

Alex

 

This is the plan in simbrief:------------------------------------------------------------------- N058SB 19MAR2024 KCNM-KDVT BE58 N058SB RELEASE 1142 19MAR24 OFP 3 CAVERN CITY-PHOENIX DEER VALLEY WX PROG 1912 1915 1918 OBS 1906 1906 1906 ATC C/S N058SB KCNM/CNM KDVT/DVT CRZ SYS 2300/24.0 19MAR2024 N058SB 1210/1230 1445/1453 GND DIST 444 BARON 58 / IO-520-C STA 1455 AIR DIST 432 CTOT:.... G/C DIST 402 AVG WIND 143/009 MAXIMUM TOW 5400 LAW 5400 ZFW 5400 AVG W/C P005 ESTIMATED TOW 4885 LAW 4504 ZFW 4335 AVG ISA P003 AVG FF LBS/HR 168 FUEL BIAS P00.0 ALTN KPHX TKOF ALTN ....... FL STEPS KCNM/0065/ ---------------------

 

And this is what is imported to LNM:

Flight successfully downloaded. Reading of route description successful.

Nothing found for SUNSS8. Ignoring.

Flight plan from Cavern City Air Trml (KCNM) to Phoenix Sky Harbor Intl (KPHX).
Distance without procedures is 414 NM.
Using cruise altitude 6,500 ft for flight plan.
Takeoff from runway 14L.
Arrive using STAR SUNSS8.

Route description:
KCNM/14L N0196F065 DCT WHOLE DCT EWM J4 SSO SUNSS8 KDVT/07R KPHX.
Found 5 waypoints:
KCNM WHOLE EWM SSO KPHX.

 

I see that LNM does not find the STAR SUNSS8 which appears in skyvector. BTW I can create the plan fine using LNM only.

 

 

Using the flight plan route description in LNM shows the same issues.
KDVT has SUNSS8, but LNM complains anyway and messes up the rest. 😕

Definitely a bug which crept in with the changes in 3.0. Will fix for 3.0.6.

Thanks for reporting!

Alex

This release candidate for 3.0.6 should fix the issue: https://k00.fr/3liopl2z

Plus a bunch of more bugs when importing SimBrief and reading/writing route descriptions.

Alex