When attempting to add a route to the database that is simply “DCT”, I am getting an Error 400. The specific example that I encountered this issue with is LFPO-LFPG which requires item 15 to be “DCT” (as described in chart 10-3N7, e.g., and can be seen in flight plans on edi-gla as well).
I understand that item 15 validly being literally just “DCT” is an exceptionally rare case, but it would be nice to be able to add these routes to the database anyway so pilots can get the correct ones suggested
One of the unfortunate limitations is that a DCT-only route disables the detailed navlog altogether (thus no winds and limited/less accurate fuel and altitude planing), so unfortunately it’s not likely to be an easy fix. It’s also possible the current database design doesn’t allow storing of a DCT-only route, although that last part is just a guess?
That is true, but I can go and generate a briefing/flight plan with only DCT as the route just fine, so regardless of the associated problems in getting proper wind data for such a flight, it seems a bit odd that I can’t put that same route into the database as an IFPS-validated one.
I’m hoping that there is just some logic behind the scenes that didn’t account for situations like this and can be easily resolved (I had the same error some time ago with a valid 804 NM or so DCT through the Nordic FRA and back then the maximum direct limit for manually added routes was apparently 800 NM and the SimBrief people were able to adjust that number a bit to accommodate my route - hopefully it’s a similar case here).
