Simbrief planning with purist Starship
-
I'm hitting a wall which seems to possibly be a Simbrief limitation rather than a Starship one when it comes to non-GNSS planning:
I'm trying to make a 1980's correct Simbrief profile, which I think SB still isn't "respecting". Here is the data I've got:
Per a Foreflight article I've found, all Rockwell Collins FMS systems have at least the following:
R (PBN approved) and PBN B2 (RNAV 5, GNSS), C2 (RNAV 2, GNSS), D2 (RNAV1, GNSS)Now we're simulating no GNS430 and disabling the GNSS update to replicate the original 1980s layout, so I've got mine set up as the following:
Navigation/Communication Equipment:
S- Standard Equipment (VHF, VOR, ILS)
D- DME
H- HF Radio
R- PBN approved
W- RVSM ApprovedPBN Capability:
B3- RNAV 5, DME/DME
C3- RNAV 2, DME/DME
D3- RNAV 1, DME/DMEIf I try and plan out a flight on Simbrief with these 1980s limitations, it still spits out an RNAV STAR. If I remove EVERYTHING except VOR only navigation, Simbrief STILL gives me RNAV arrivals. To further make it confusing, if I load the 727, which has PBN like above, Simbrief will give me VOR-to-VOR.
Anyone try to make sense of this? I've also cross-posted in Navigraph's forums. This is my profile if anyone wants to try:
https://dispatch.simbrief.com/airframes/share/575521_1750455157752
-
Also quite interested in this.
You are missing F- ADF
And if you want to fly with original nav equipment but able to communicate with today’s ATC frequencies, you will need Y- for 8.33 MHz spacing.
RVSM as a standard was only introduced after the Spaceship introduction.
"In October 2008 NC-29 was the first of the five remaining privately owned airworthy Starships to complete RVSM certification, returning the aircraft’s service ceiling to the original FL410 limit." So depends on what you prefer to do there.Transponder type is another area, where I haven't examined the correct code yet.
Edit: Oh and does it technically also do B4- RNAV 5, VOR/DME on top of B3?
-
Simbrief is primarily built for airliners and doesn't really understand anything else. It will happily assign a piston or turboprop aircraft a "turbojet only" procedure.
For things like this, I enjoy planning by hand in Navigraph directly and then plugging that route into Simbrief for fuel purposes.
Alternately, you can maybe take what it gives you and manually enter the SID/STAR waypoints by hand and call that out in your remarks.
Just double check what it assigns you.
-
Simbrief is primarily built for airliners and doesn't really understand anything else. It will happily assign a piston or turboprop aircraft a "turbojet only" procedure.
For things like this, I enjoy planning by hand in Navigraph directly and then plugging that route into Simbrief for fuel purposes.
Alternately, you can maybe take what it gives you and manually enter the SID/STAR waypoints by hand and call that out in your remarks.
Just double check what it assigns you.
@jmarkows
If you enjoy planning the flight as I do, take a look at LittleNavMap.There is a slight learning curve but I prefer it to Navigraph.
Plus, LNM will also calculate your block fuel.
It even tracks your flight and fine tunes your fuel usage based on how you fly (I am a max cruise type of guy, no fuel to purchase)
My fuel calculations from LNM are usually within a few gallons because of this tracking.It also exports to Simbrief so importing flightplans into MSFS is easier.
-
I found this note:
RNP D1-D4:
"Required for RNAV SID and STAR procedures. If an RNAV 1 code is not specified, ATC will reject flight plans that include RNAV SID/STAR procedures"I've removed the D3 and Simbrief is still issuing GNSS STARS so I've forwarded it to their dev team
-
The problem is that certain RNAV SID/STAR's have GNSS requirement, whilst others are happy with DME/DME as well. Both can do the RNP1 requirement. So, unless SB goes and checks the notes off all RNAV SID's and STAR's, all it can do is generalize. It's up to you to check your calculated route for particular legalities.