AIRWAY.txt

[David Walsh 811659]

Could somebody please define each column in the AIRWAY.txt for me?

 

In NZ we have a Standard Route Clearances (SRC) which have a designator e.g. AAHN1 (Auckland-Hamilton 1) and an [Mod - Happy Thoughts]ociated route e.g. H211. The pilot just files the designator in the FPL and you clear them on a SRC.

 

The issue is that ES doesn't see a AAHN1 as a route of airways and waypoints, hence does not draw routes or identify the next controller to hand off to etc so I was wondering if I could manipulate the AIRWAY.txt file and insert SRC designators into it.

 

Any help appreciated.

 

Cheers,

 

David,

VATNZ

[Gergely Csernak]

David,

 

I can not describe the exact file format, but I can write down what ES expects from it:

It is a TAB delimited file. I cut the content of each line by the TAB characters. The compilation of the elements are the followings:

1 - the name of the point

2-3 - latitude and the longitude of the point

4 - ignored

5 - the name of the airway

6 - the type of the airway

7 - the previous point along the airway

8-9 - ignored (but actually the latitude and the longitude of the previous point)

10 - minimum altitude

11 - airway can be used from previous to this point

12-16 is the same as 7-11 but for the next point

[Adam Arkley 1031024]

Gergely,

 

I actually came onto the forum to find out some stuff about this, and then saw this. I'll add to it.

 

Is it possible for the Airways docomeent to have some added functionality built in? In the UK, we have single directional airways, and most airways have max altitudes as well as min altitudes. Can support for this be implemented?

[Stephan Boerner 945550]

I think it would make more sense to check with Navigraph if they are willing to extend the airway.txt, before thinking about implementing anything to ES that is not supported by the DataSource.

[Alen Smriko 1034823]

11 - airway can be used from previous to this point

 

By this you mean that the airway can/cannot be used in that direction?

[Johan Grauers]

Gergely,

 

I actually came onto the forum to find out some stuff about this, and then saw this. I'll add to it.

 

Is it possible for the Airways docomeent to have some added functionality built in? In the UK, we have single directional airways, and most airways have max altitudes as well as min altitudes. Can support for this be implemented?

 

We have single-way airways in Sweden that display a warning on the route page if they're filed in the wrong direction. So that is possible to do, if you want I can try and figure out how it works with the airway.txt file?

[Alen Smriko 1034823]

To clarify why I'm asking.

 

Take this image for reference. It's from the current Croatian upper route chart:

 

Now, an example. In the FSnav airway.txt file (AIRAC 1008) I found this.

ZAG	45.895559	16.306697	14	UL603	H	LURID	45.135000	17.399445	28500	Y	PODET	46.171375	15.626797	29000	N
ZAG	45.895559	16.306697	14	UL604	H	PETOV	46.309675	15.976167	24500	Y	NOVLO	45.229444	16.953056	29000	N
LURID	45.135000	17.399445	14	UL603	H	DOBOT	44.773889	17.902500	29000	Y	ZAG	45.895559	16.306697	29000	N
NOVLO	45.229444	16.953056	14	UL604	H	ZAG	45.895559	16.306697	29000	Y	BOSNA	44.370556	17.759722	30000	N
PODET	46.171375	15.626797	14	UL603	H	ZAG	45.895559	16.306697	29000	Y	KLAGY	46.514300	14.775170	25000	Y
PETOV	46.309675	15.976167	14	UL604	H	MIRSO	46.475986	15.841981	24500	Y	ZAG	45.895559	16.306697	29000	N

 

According to how you described the data:

1. The direction from LURID to ZAG is correct (inconsistent). The direction from ZAG to PODET is wrong (inconsistent).
   
2. The direction from PETOV to ZAG is correct(inconsistent). The direction from ZAG to NOVLO is wrong (ok).
   
3. The direction from LURID to ZAG is wrong (ok).
   
4. The direction from ZAG to NOVLO is correct (inconsistent).
   
5. The direction from ZAG to PODET is correct (ok).
   
6. The direction from PETOV to ZAG is wrong (ok).

 

I'm really having trouble understanding this file. Could someone please help?

[Alen Smriko 1034823]

On the day before tomorrow, I had a flight which had a route "...ZAG UL603 KFT..." (ZAG PODET KLAGY KFT). Everything was fine except ES was showing that the segment from ZAG to PODET was in the wrong direction ("direction error").

 

Either ES reads the data from the "airway.txt" file incorrectly, or Navigraph messed it up...

[Ervins Reinverts]

Looks like exactly the same issue I am describing in the neighbouring topic "flight plan interpretation" (second one in my post).

Wondering if there is any doc around that describes tha airway.txt format, so I could check it out myself?

[Johan Grauers]

If there's just one point that shows direction error I have found that it's usually like this.

 

Pilot files

 

ABC UN7123 NDE

 

ABC gives a route direction error

 

Then UN7123 is usually one way, up to ABC, so the pilot has a correct route but he's just coming on the airway when it becomes two way.

 

So unless I see several points with "direction error" on them, I'll say it's OK.

[Gergely Csernak]

11 - airway can be used from previous to this point

 

By this you mean that the airway can/cannot be used in that direction?

 

Alen,

 

My description was confusing, I guess. The 11th item in the line means: "airway can be used from this point to the previous". That clears the "inconsistent" definitions.

[Alen Smriko 1034823]

So, what you are saying is that Navigraph messed it up on the segment from ZAG to PODET on UL603?

[Gergely Csernak]

It seems so.