OK, attached to this post you'll find the job done until today.

This file contains all data from the following ENAV documents:
    ENR 2.1.3 - Approach Control Zones
    ENR 2.1.5 - Military Aerodrome Traffic Zones of airports/heliports not open to civil traffic
    ENR 5.1.1 - Prohibited Areas
    ENR 5.1.2 - Restricted Areas
    ENR 5.1.3 - Danger Areas
    ENR 5.1.4 - Temporary Segregated Areas
    ENR 5.2.1 - Military Firing Areas

I'm currently working on ENR 5.6.3 - Interdiction to overfly and/or to land on Protected Areas (natural parks and areas subject to natural fauna protection). There are a lot of this, especially on Alps!
I planned to dedicate more time to this work during Christmas holidays, and to release the version 1.0 (or "2008.0") of this file on January 2008.

Until then, please enjoy my file, and feel free to contact me for any issue and/or suggestion.

Ciao, and Happy Landings!
Mauro

Hello Mauro,

I have wrote a file in OpenAir of the North-East part last spring for our soaring purposes. The file is attached below.

A lot of the nationalparks are not a problem for gliders and similar planes, because they are only effective for motorplanes (aeroplanes!). This was the way I unterstood the Italian AIP, but maybe the original version written in Italian will give a clearer view.

There are a lot of Airways in Italy, which make the Airspace a lot more unclear than it is anyway. I only took the Airways below FL 195, because above FL 195 there is Class C in Italy.

You should normally can delete Vipiteno (Restricted Area) because the reason for it is heave glider activity.

When I wrote the file it was also not very clear to me what's up with TMA Milano and the VFR Sectors. I unterstood it this way that in the VFR Sectors of TMA Milano Transponder (Mode A and C) is mandatory. So the entire area of TMA Milano wouldn't be allowed to use without Transponder.

The Class E in Italy also seems to be a bit different to other countries, You also need a Transponder to be allowed to fly there.


kind regards,

Georg

Hello,

1. how can I insert this NO-FLY-ZONE to the database on airspaces?
http://www.aecaosta.it/dbext/parco2002.htm
(look at the bottom of the page)
Can I use SeeYou (desktop), and how can I insert lines?

2. how can I export in the .cub file the airspaces?

3. how can I import the .txt file in mt SeeYou mobile so that I can see it?

THX!

Here You find a brief describtion how to enter a new airspace in the OpenAir-file (just open it with the editor)

I think there is no possibility to convert from OpenAir to .cub-file for Naviter purposes. The only way is to open the OpenAir-file You created in SeeYou-Desktop and export it with the connection manager to the mobile device.

I hope this helps You.

kind regards,

Georg

Well, not sure what the "connection manager" (can you explain, please?) is, but I understand the OpenAir format.
I'm trying to; thanks!
 

Sorry, I meant the mobile manager in the seeyou-desktop-program.


kind regards,

Georg

Hi,

First of all: Thanks a lot for providing the file of italian airspaces, which helps a lot especially with the military firing areas!
Unfortunately it´s quite confusing, for example when flying in the area of bolzano, as there are too much airways that disturb while not really concerning in thermal flying.

The chance to simply hide the waste airspaces by deselecting "airways" does not work, as all of the italian airways are also labeled as "class d" airspace!

Is it possible to change that for further airspace packages and label the italian airways only as "airways"?

Thanks a lot,
Alex.

The problem with the airways is that a lot of programs cannot read them, therefore they were definded as Class C or D. To remove them You only need to open the file with the text-editor and remove them.

For OpenAir-format there even exist no definition of airways. In TimNewportPeace it exists, but only a few programs run on TimNewportPeace and have problems to display it (but SeeYou can display these airways).


kind regards,

Georg

Hi Georg,

The problem is that the airspace delivered by SeeYou is not human-readable, at least for me!

As you said, SeeYou is able to display airways!
So I would think, that the airspace that is suggested to be used only with SeeYou, should be in the appropriate format.

So this is maybe the duty of the Naviter guys!

Thanks a lot,
Alex

Maybe I don't understand. Human readable format is attached to the first post, you may edit it any way you like. You may convert it back to unreadable CUB format with SeeYou > File > Mobile Wizard. Let me know if you need more help.