Hello,

I keep having problems with my flight plans. I ditched RR for that and with SD it is the same.
Every time I fly through Belgium, they don't have my flight plan. Neither Ostend approach nor Brussels radar.
This is very annoying as it happened that I had to fly holds at KOK for 38min once. 
Coventry has my flight plan and they activate it. 

Anyone else with this problem?

Markus

I found the issue myself. Sky demon addressing is wrong.
In AIP Belguim:
http://www.belgocontrol.be/website/eaip/eAIP_Main/html/eAIP/EB-ENR-1.11-en-GB.html

Sky demon hasn't implemented their flight plan rules:
My plan go addressed to: EGBEZTZX EGZYVFRT EGBBZTZX EBBUZFZX EDGGZFZX EDMMZFZX EDDZZPZX EDDXYIYR

I entered Belginan airspace inbound, so EBBRZPZX is needed.
The flight was planned through Ostend TMA (or CTR) so EBOSZTZX has to be added.
And most of the flight was spent in Brussels TMA (airspace C)  EBBRZTZX should be on that list.

Please SD team. Verify ENR 1.1 and get the correct addressing in your system.

I know I can add addresses to my flighplan before I send it, but it seems that SD should do the job, that is what a customer would expect.

I will ask our colleagues at EuroFPL to comment on the issue you have raised (it's their addressing engine we use).

EuroFPL is an IFR tool. I think they haven't got the full implementation of VFR flight plans.
There are plenty deviations from addressing in Europe.
VFR addressing is more complex than IFR as you just have the IFPS and that is it.

Greetings everyone!

This is Derek over at EuroFPL.  I just wanted to pipe up in response to some of the addressing issues to let you know what we're currently working to improve in terms of our addressing backend.  First of all, our apologies for any delays or other inconveniences due to incomplete or inaccurate addressing.  As mentioned, VFR addressing can be quite complex, and quite often a cruel mistress.

In terms of the Belgium overflight above, you can see that we address the FIR unit EBBUZFZX as prescribed, (EBBRZPZX is only applicable to departure/arrivals), and are curiously omitting Oostende TMA (EBOSZTZX) and Brussels TMA (EBBRZTZX).  The reason for the latter?  Sadly our current system, on the EuroFPL side, lacks the spacial awareness/resolution to detect TMA or CTR penetration based on a fly-through, and certainly doesn't yet have the sophistication of airspace plotting and modeling that you guys enjoy with SkyDemon everyday.

So this is our key goal going forward!  While in most cases a terminal ATSU would simply get the flight data from the FIR unit up the chain without delay, hearing some of these accounts of 40 minutes holds is indeed alarming!  We'll try to come up with some fixes that we can implement right away, while we work on a more elegant/intelligent spacial solution.  In most instances, a lot more authorities are utilizing technology to consolidate addressing and we're starting to see more and more single-point addressing for departures and overflights and the like to make it friendlier for all.  Hopefully Belgium will follow suit!

And to do our part, in the name of efficiency, safety, compliance, and of course our commitment to you guys, we'll see about enhancing our system as soon as possible.  Apologies again, and safe flying!

Best regards,

- Derek
EuroFPL Admin

Derek,

Is there any news on this matter?

Thanks,

Markus

Since this topic we have indeed addressed the issue behind the omission of airspace-specific flightplan addresses, as long as you have the latest version of SkyDemon.

So, just to be clear - when I head off over Belgium to Germany in a fortnight, I should be fine to just file with the addressing that SD provides?

Yes, you should be. Feel free to play around with some test routes, and you'll now see extra addresses being added when your route penetrates certain TMA etc for which additional addresses have been prescribed.