Unable to import Simbrief PLN file with LAT/LONG points
-
Very much enjoying the Starship (and that's an understatement!) but I have encountered one issue when loading a simbrief-generated PLN file.
This flight plan includes a mix of LAT/LONG points, five-letter waypoints and four letter ICAO airport codes as enroute waypoints. Also this is an A-to-A flight, so the dep and arr airports are the same. Any of these factors I am wondering might be an issue affecting import.
I follow the instructions from the manual and I can get the PLN file loaded up in the MSFS EFB, but when I get to "send to avionics and ATC" all that happens is the DEP/ARR fields load in to the Starship flight plan but none of the intervening points do. I don't see any "Importing flight plan' message on the CDU either.
Am I trying to do something that the product isn't intended to do in terms of the abnormal flight plan, or is there some step I am perhaps overlooking?
-
Very much enjoying the Starship (and that's an understatement!) but I have encountered one issue when loading a simbrief-generated PLN file.
This flight plan includes a mix of LAT/LONG points, five-letter waypoints and four letter ICAO airport codes as enroute waypoints. Also this is an A-to-A flight, so the dep and arr airports are the same. Any of these factors I am wondering might be an issue affecting import.
I follow the instructions from the manual and I can get the PLN file loaded up in the MSFS EFB, but when I get to "send to avionics and ATC" all that happens is the DEP/ARR fields load in to the Starship flight plan but none of the intervening points do. I don't see any "Importing flight plan' message on the CDU either.
Am I trying to do something that the product isn't intended to do in terms of the abnormal flight plan, or is there some step I am perhaps overlooking?
While the flight plan loading in Starship is kind of a can of worms due to unexpected behavior in the native flight planner (and that this was not a feature I was originally planning to implement until so many people requested it), let me start with a really quick question:
@markadeane said in Unable to import Simbrief PLN file with LAT/LONG points:
"send to avionics and ATC"
Did you try just "Send to Avionics" with no "ATC"? In my experience, the former works very well, but the latter opens the above mentioned can of worms.
-
Thanks for thew quick response. I tried both methods, yes. No luck either way.
I plan on trying a few things tonight to see if I can narrow it down to any one aspect of the flight plan. But the plan itself was as follows: (and before anyone asks, yes I was going to rip around the Grand Canyon at 280 kts using this as a rough reference!)
KSEZ/21 N0273F080 DCT 360530N1112259W DCT KLIFF DCT 364809N1113625W DCT KPGA DCT 365159N1113524W 364902N1113752W 363745N1114550W 363029N1115113W 362703N1115018W 362537N1115219W 362343N1115255W 362328N1115058W 362218N1115329W 361140N1114758W 360608N1114949W 360245N1115423W 360607N1120522W 360339N1120629W 355749N1120757W 353031N1121024W 351832N1121035W 351601N1120946W 350435N1115659W 350004N1115815W 345807N1120128W 345541N1115943W KSEZ/03
If I were going to pin this issue on anything, it would most likely be the Lat/Long fixes but I'd be interested in your thoughts.
-
(I just attempted a post here that appears to have failed so I apologise if it subsequently appears as a duplicate)
I tried both methods you asked about with no success I'm afraid.
If it helps at all, this is the flightplan text string out of Simbrief.
KSEZ/21 N0273F080 DCT 360530N1112259W DCT KLIFF DCT 364809N1113625W DCT KPGA DCT 365159N1113524W 364902N1113752W 363745N1114550W 363029N1115113W 362703N1115018W 362537N1115219W 362343N1115255W 362328N1115058W 362218N1115329W 361140N1114758W 360608N1114949W 360245N1115423W 360607N1120522W 360339N1120629W 355749N1120757W 353031N1121024W 351832N1121035W 351601N1120946W 350435N1115659W 350004N1115815W 345807N1120128W 345541N1115943W KSEZ/03.
I also have the PLN file I could send along for analysis if that's helpful.
(In case anyone is wondering about the craziness of this plan, it was intended to give me a rough guide to a closed circuit for a high speed low level run through the marble canyon and grand canyon areas.)
