Hey there,
I’ve noticed this little issue when planning a flight that departs an airport within a FIR that is somewhat oceanic, e.g. the LPPO Santa Maria FIR, KZWY New York Oceanic, etc.
The ‘Oceanic clearance’ or ‘Oceanic request’ section preceding the Navlog should contain all relevant waypoints for the oceanic crossing, the section lists all enroute waypoints and the mach number as well as planned initial and maximum altitude for the crossing. However, Simbrief includes SID & STAR waypoints if they are in that FIR and takes the Flight Level & Mach number from there (or the second waypoint in my current case). While it is technically the first waypoint laying in an Oceanic FIR, ATC won’t wanna know what Flight Level and Mach we’re doing in the climbout, but rather what our plan for the enroute/oceanic cruise segment is.
This is the LIDO layout:
OCEANIC CLEARANCE:
SM528 SM522 RODAS SM532 MIPRU 40N030W 43N040W 44N050W BOBTU JAROM
LOMPI BRADD FL036 .40
MAX OCEANIC ENTRY FL360
--------------------------------------------------------------------
AWY FL IMT MN WIND OAT EFOB PBRN
POSITION LAT EET ETO MORA ITT TAS COMP TDV
IDENT LONG TTLT ATO DIS RDIS GS SHR TRP AFOB ABRN
FREQ
--------------------------------------------------------------------
299 14.8 0.1
JOAO PAULO N3744.5 ... 26 292 M010
LPPD W02541.9 0000 ... 2112 249 .... ....
MIPRU2X 018 284 .39 282/010 17 14.5 0.4
SM528 N3744.8 0002 ... 51 276 M010 P06
SM528 W02542.6 0002 ... 1 2111 249 453 .... ....
MIPRU2X 036 284 .40 290/011 14 14.4 0.5
SM522 N3745.6 0001 ... 25 276 M011 P06
SM522 W02551.0 0003 ... 7 2104 256 453 .... ....
I’ve come across this or a similar issue when building my own LIDO-style layout, too. I’m using the waypoint after oceanic entry for the Mach number as a workaround and the first oceanic fix that’s not SID/STAR and also not TOC/TOD for the Flight Level, and I’m getting this right now:
OCEANIC REQUEST:
MIPRU N40W030 N43W040 N44W050 BOBTU JAROM LOMPI FL174 .78
MAX OCEANIC ENTRY FL360 RVSM ALT CHK [ ]
--------------------------------------------------------------------
AWY ETO FL IMT MN WIND OAT EFOB
POSITION LAT EET RTO MTCA ITT TAS COMP TDV
IDENT LONG TTLT ATO DIS RDIS GS SHR TRP AFOB
--------------------------------------------------------------------
... 14.4
JOAO PAULO I N3744.5 ...
LPPD W02541.9 0000 ... 2112 ....
MIPR2X ... 174 336 .63 273/035 M03 13.3
MIPRU N3816.4 0002 ... 20 329 406 M021 P17
MIPRU W02621.9 0012 ... 15 2097 385 00 453 ....
DCT ... 360 310 .78 283/059 M49 12.1
T O C N3933.3 0024 ... 53 302 455 M056 P08
W02901.3 0032 ... 146 1951 399 01 438 ....
DCT ... 360 311 .78 293/058 M51 11.7
40N030W N4000.0 0007 ... 20 300 455 M058 P06
W03000.0 0040 ... 52 1899 397 02 428 ....
DCT ... 360 304 .78 310/049 M51 8.8
43N040W N4300.0 0111 ... 20 295 453 M048 P06
W04000.0 0152 ... 484 1415 405 01 435 ....
NEW_YORK_OCE N4299.6
-KZWY W04000.0
Now, what I’m doing is filtering all entries for oceanic FIRs (LPPO, EGGX, CZQX, …), remove them if they’re <is_sid_star>: <1> or : <TOP OF CLIMB/DESCEND> and taking the mach number from the waypoint after the entry.
Of course, a human looking at this would instantly see “oh yeah, they want to cross in FL360 at Mach .78, sure” but how do we tell Simbrief this?
Ideally, it might make sense to define the oceanic cruise initial altitude and Mach within Simbrief for this. I’ve thought about using <cruise_mach> but that is not necessarily the Mach number at entry, so to get it really right, we’d have to define them as keys on their own.
EDIT:
I’ve built a little check into my code that determines if TOC is within the oceanic segment, and uses the TOC FL for the oceanic request. That might be a feasable workaround in general:
OCEANIC REQUEST:
MIPRU N40W030 N43W040 N44W050 BOBTU JAROM LOMPI FL360 .78
MAX OCEANIC ENTRY FL360 RVSM ALT CHK [ ]
--------------------------------------------------------------------
AWY ETO FL IMT MN WIND OAT EFOB
POSITION LAT EET RTO MTCA ITT TAS COMP TDV
IDENT LONG TTLT ATO DIS RDIS GS SHR TRP AFOB
--------------------------------------------------------------------
... 14.4
JOAO PAULO I N3744.5 ...
LPPD W02541.9 0000 ... 2112 ....
MIPR2X ... 174 336 .63 273/035 M03 13.3
MIPRU N3816.4 0002 ... 20 329 406 M021 P17
MIPRU W02621.9 0012 ... 15 2097 385 00 453 ....
DCT ... 360 310 .78 283/059 M49 12.1
T O C N3933.3 0024 ... 53 302 455 M056 P08
W02901.3 0032 ... 146 1951 399 01 438 ....
DCT ... 360 311 .78 293/058 M51 11.7
40N030W N4000.0 0007 ... 20 300 455 M058 P06
W03000.0 0040 ... 52 1899 397 02 428 ....
