French Strikes - impact on GA IFR

Peter wrote:

Which satnav apps will show the airspace as G during the relevant times?

SkyDemon?

That means France must notam each unit’s strike times, and would imply the change to G is either notamed or somebody checked that the airspace really becomes G and is willing to risk it on behalf of their customers

Peter wrote:

That means France must notam each unit’s strike times, and would imply the change to G is either notamed or somebody checked that the airspace really becomes G and is willing to risk it on behalf of their customer

I think @Ibra would know how it actually happens. :)

arj1 wrote:

would know how it actually happens

Sadly, I don’t I have flown few times with no clue which airspace, I mean in Normandie not Southampton

However, I tend to carefully watch for ZIT, ZRT and P-areas, like this one (load of them from 20th April)

SUP-AIP-050/23

If you bust ZRT you will get your skin pulled, French or foreigner does not matter

Just had some fun with AR doing EGKA-LFBH. The French strike causes this, so I filed VFR through the striking sector

N0152F040 BOGNA/N0152F080 DCT OSPOL/N0150F080 M189 NEVIL DCT IBUMO DCT BULOX/N0150F060 VFR DCT TABIL/N0144F060 DCT IBSUS DCT LUSON IFR LUSON6C

With some luck ATC may not insist on IFR cancellation at BULOX.

Sadly the above hack fails to work because AR chucks out LUSON IFR LUSON6C and files it as a VFR arrival, so if LFBH ATC refuse an IAP, one is screwed.

It works fine for me, IFR all the way, tomorrow at 1200Z

Can you parse ‘…LGL A5 NTS A25 LUSON LUSON6D LFBH’ for IFR arrival at FL70?

This works" EGKA N0145F070 DRAKE DCT SITET A34 LGL A5 NTS A25 LUSON LUSON6D LFB"

It does not look great today at 8pm with possible delays from strikes but it validates

This works, as one would expect

EGKA N0149F070 DRAKE DCT SITET A34 LGL H20 BENAR A34 AMB B19 POI DCT NITUB DCT XERGI DCT LUSON LUSON6C LFBH

Yes, but be ready for the slot., I‘d say.
Consider filing 45 minutes early and then freezing the slot that comes.