Hi, when creating route in the Flight Plan Route Description window, I sometimes would do it without SID/STAR for example:

XXXX ABC A123 DEF YYYY

However in some airport, DEF is both the name for the waypoint/navaid and the STAR from that waypoiny/navaid, in such case, LMN would say a error: couldn't find waypoint after A123, as it consider the "DEF" as a star, rather than waypoint.

I know I can select Write no SID/STAR option, but it's kinda annoying I'll have to switch it every time, so would it be possible for LMN to prioritize DEF as a waypoint here? I believe it would be a simple logic to detect if there is no other entry after A123, DEF is more likely to be a waypoint, rather than a STAR.

Usually SID/STAR names are created to avoid confusion with fix point names.
Could you give the exactly airport, fix points and procedure names where you get such a confusion?

Regards,
Piotr
 

1 hour ago, ppgas said:

Usually SID/STAR names are created to avoid confusion with fix point names.
Could you give the exactly airport, fix points and procedure names where you get such a confusion?

Regards,
Piotr
 

Here is a example: RJAA NINOX Y28 ONDOC Y452 OOITA Y40 KAZMA RJFT (on navigraph2313)

LNM told me :

No waypoint after airway Y40. Ignoring flight plan segment.

Flight plan from Narita Intl (RJAA) to Kumamoto (RJFT).
Distance without procedures is 520 NM.
Arrive using STAR KAZMA and runway 07.

27 minutes ago, C2615 said:

Here is a example: RJAA NINOX Y28 ONDOC Y452 OOITA Y40 KAZMA RJFT (on navigraph2313)

LNM told me :

No waypoint after airway Y40. Ignoring flight plan segment.

Flight plan from Narita Intl (RJAA) to Kumamoto (RJFT).
Distance without procedures is 520 NM.
Arrive using STAR KAZMA and runway 07.

I suppose this not problem lack of STAR here, but rather too short distance between KAZMA and RJFT airport. Probably LNM calculates that over fix point KAZMA you are not already on Y40 airway but below its lower boundary. From KAZMA to RJFT airport there is only 18NM distance and probably vertical profile is below Y40 lower boundary here.
Try create fake aircraft profile with incredible descent rate (for example 9900 fpm) and low speed (99 kts for example), and switch to this profile before creating the fpl, it should be enough to stay with vertical profile over KAZMA within Y40 boundary  and LNM should accept RJAA NINOX Y28 ONDOC Y452 OOITA Y40 KAZMA RJFT as a proper flight plan. I use this trick and it works 🙂

Regards,
Piotr

ps. previously when you added proper STAR LNM accepted fpl because remained distance to RJFT was enough to stay on Y40 at KAZMA fix.

8 hours ago, C2615 said:

so would it be possible for LMN to prioritize DEF as a waypoint here?

Maybe. I have to guess what the user wants.

Elevation profile and aircraft performance is not considered when scanning route descriptions. Distance between waypoints can play a role for ambiguities but not here.

I can try to detect the situation where waypoint and STAR have the same name after an airway, and insert the waypoint *and* the STAR. If you don't like the STAR, delete it. Or add a waypoint instead of STAR *if* an airway is given before. I'm unsure if this would break the SimBrief import and
I'm not sure how to solve this yet. Have to see. Noted.

For now use "RJAA NINOX Y28 ONDOC Y452 OOITA Y40 KAZMA KAZMA RJFT" instead. I'll try to change the scanning for one of the 3.0.X beta.

Alex