unable to enter airway in flight plan

[bootsie 0]

I've just been trying to enter the following IFR route directly into the flightplan window.

KJFK RBV J230 BYRDD J48 FLASK KATL

After clicking the RBV VOR and selecting Load Airway, then selecting J230/BYRDD, it never appears in either the flightplan window or the map display. No errors anywhere and nothing in the logs.

I used FP Import to import the route string directly and that seemed to work fine.  Am I doing something wrong? I'm using AIRAC 1712 on v2.3.1.1

 

Thanks

[Alvega 2,124]

Just tried here, same thing happened.

[Dave-Pilot2ATC 870]

Appears to be a bug that also is in the latest version 2.3.1.2.  I'll work on a fix.

Thanks for the report.

Dave

[bootsie 0]

No problem, I'll just use FP Import for now.  Actually, I don't know why I'm not doing that anyway!

[bootsie 0]

Just to add to this - even when I import the route string, the waypoints for the SID don't appear in my flight plan.  I thought it was working ok that way but apparently not.

[Dave-Pilot2ATC 870]

SIDs, STARs and Approaches (the procedures) are not part of the route and are therefore not imported.  This is because the procedures need to be based on active runways etc which will change from one flight to another while the route can be saved and reused.

[bootsie 0]

Sorry, I wasn't explaining properly.

When I filed the imported flight plan and the SID and STAR were selected automatically, the SID waypoints didn't appear on the map or in the flightplan.  The STAR points were fine though.

[Dave-Pilot2ATC 870]

Ahh, OK.  What was the imported route and what SID was selected automatically.  I'll try and duplicate the issue.

Thanks,

Dave

[bootsie 0]

Dave,

Route was

KJFK RBV J230 BYRDD J48 FLASK KATL

Just tried this and GREKI4 SID was chosen automatically but doesn't appear anywhere in the flightplan.  STAR was WINNG1 and shows up fine in both the flightplan and the map.

[Dave-Pilot2ATC 870]

Thanks for the additional detail.

I've found the bug that was causing the SID not to display and also the bug that prevented the manual entry of the route...so next update should fix both.

Thanks again,

Dave