EG5738 EGLF ABSAV1P, NOTGI1P, CPT1P NOT AVBL FOR TFC acft-eqpt RNAV1 (D1, D2, D3, D4, O1, O2, O3, O4) H24 RNAV5 STARS FOR EGLF ARRIVALS EG 25 APR 2022
EG5538 EGLK ABSAV1P, NOTGI1P, CPT1P NOT AVBL FOR TFC acft-eqpt RNAV1 (D1, D2, D3, D4, O1, O2, O3, O4) H24 RNAV5 STARS for EGHL /EGLF/EGLK / EGTD / EGTF / EGVO EG 25 APR 2022
Is there a way to force Simbrief to pick the 1V arrivals for aircraft with the corresponding RNAV equipment (vs. the 1P for the others)?
Regards,
Tim
Not currently. Only if the RNAV requirement is defined in the AIRAC data, which it currently isn’t for these STARs.
I can however force all flights to choose the 1V STARs by default for now, assuming that’s preferable since most airliner flights should be RNAV1?
Best regards,
That’s not a bad idea. I guess as per the second rule it applies to all of EGHL / EGLF / EGLK / EGTD / EGTF / EGVO; it looks like only the CPT STAR has 1V vs. 1P options, all the others are either 1V or 1P but not both.
Regards,
Tim
We ALWAYS file RNAV as long as the aircraft is capable by MEL, whether by GPS or DME/DME/IRU. I dont think I have an MEL across our fleet that essentially makes an aircraft /A, like say a 727 with just a 6-pack and a VOR or two…
It’s a slightly different issue here; both CPT1P and CPT1V are RNAV STARs, but CPT1P is forbidden (and thus CPT1V is mandatory) for a specific subset of RNAV-equipped aircraft.
Regards,
Tim
I have changed it so that the 1P STARs are avoided by default. But it’ll only really affect routes where both a 1P and 1V STAR are possible (so it’ll mainly affect CPT1P vs CPT1V routes).
Best regards,