Archived

This topic is now archived and is closed to further replies.

Jarkko

CFMU validation errors and using PFPX auto routing to fix them

32 posts in this topic

MODS

can you 'sticky this'

Thanks

+1.

Very good information, thanks, Jarkko.

0

Share this post


Link to post
Share on other sites

MODS

can you 'sticky this'

Thanks

Great post +1 for sticky

0

Share this post


Link to post
Share on other sites

Jarkko,

thank you so much for your support. Now I'm able to fix the routes on my own, without searching for valid routes on the internet. Thank you.

Maybe you can add another important thing to your original post:

"Errors referring to invalid flightlevels can be ignored until you computed your flight. Only if they exist after flight computation, you need to pay attention to them."

Best regards,

Chris

1

Share this post


Link to post
Share on other sites

Cool its possible with PFPX :P

Question: what to do with FL errors?

0

Share this post


Link to post
Share on other sites

Thanks for the Help. I'm trying to find a route from LTAI to EDDS but the Validator is still finding incorrect parts in the corrected routes. Could anyone check it?

0

Share this post


Link to post
Share on other sites

Thanks for the Help. I'm trying to find a route from LTAI to EDDS but the Validator is still finding incorrect parts in the corrected routes. Could anyone check it?

Well I tried to find a route that would validate, but struggled.

Only been able to understand CFMU validating for less than a day.

Someone more able should be able to help out and also could show us how it's done!

0

Share this post


Link to post
Share on other sites

Thanks for the Help. I'm trying to find a route from LTAI to EDDS but the Validator is still finding incorrect parts in the corrected routes. Could anyone check it?

This route I created passed the validation check: EKSEN UA16 KFK UL610 VADEN L610 UTEKA UL610 TONDO UP870 RASTA UL173 MUN L173 DODIL T127 TEKSI

Let me know if it works for you, too.

0

Share this post


Link to post
Share on other sites

EDITED BY MIKKELGH TO CLEAR UP A BIT OF CONFUSION

EDITED TEXT MARKED WITH RED

I'll add my bit. Hopefully some of you can use the information.

The errors are typically followed by a country code eg. ED for Germany and a number. You can look these up in the route availability page at Eurocontrol: http://www.cfmu.eurocontrol.int/RAD/

The current airac is here: http://www.cfmu.eurocontrol.int/RAD/1309/index.html.

Let's say you get the error EHYY1028a. This points to the Netherlands (EH country code) and the specific ID number (1028).

So from the above page you click on the link to the Netherlands RAD: http://www.cfmu.eurocontrol.int/RAD/1309/docs/E1_RAD_3_RADAN_EH_en.pdf

In this document you search for 1028 (or the route segment) and you will get the following description:

Traffic ARR EDDF/FE/FH, ETAR, ETOU above FL245 shall file via UT149. Below FL245 this traffic shall file via Z/UZ738

Jarrko's example is filed with a cruise level above FL245. In that case follow Jarrko's example.

Imagine you fly in a turbo prop below FL245: In this case you must file via Z/UZ738. Find the proper connection points for Z/UZ738 and give it another try with the validator.

Anyway, you will find many usefull informations at the above RAD pages, e.g. country specific rules for using DCTs. This could become handy if you get strange routings or have problems finding a valid route.

The city pair capping is useful for figuring out the appropriate flight level between cities.

Best regards,

Mikkel

3

Share this post


Link to post
Share on other sites

Was just wondering about the 'country codes!

They are the first 2 of the ICAO code. So the UK would be EG, hope that's correct

0

Share this post


Link to post
Share on other sites

Was just wondering about the 'country codes!

They are the first 2 of the ICAO code. So the UK would be EG, hope that's correct

Correct!

LF is France

ED is Germany

LS is Switzerland

and so on.

0

Share this post


Link to post
Share on other sites

My original post may lead you to believe that you should use Z/UZ738. This would be misleading if you follow Jarrko's example. I didn't think of this when I wrote the example, since my purpose was only to explain how to interpret the error codes.

Now that my post has been added to Jarrko's I should probably clarify what the error message EHYY1028a actually states:

1. If you fly ABOVE FL245 and are flying to EDDF/FE/FH, ETAR, ETOU you must file via UT149 (as in the example posted by Jarrko).

2. If you fly BELOW FL245 you must file via Z/UZ738.

In Jarrko's example the route is flown above FL245. Therefore solution 1 would be the correct choice when flying to EDDF.

Suppose you fly in some turbo prop aircraft below FL245 you would have to follow solution 2.

I apologize if my first post may have caused some confusion. To rectify this I have edited my post to hopefully clear up the confusion.

Best regards,

Mikkel

0

Share this post


Link to post
Share on other sites

On problem I've found is when flying to an airport with no published star. EGSS-EKBI returns eg.

CLN1E CLN UL620 ARTOV UP44 SOMVA UP155 OKOKO UZ303 NIRDU UN873 TUSKA N873 MIKRO, but validation fails:

Route 134:The Star limit is exceededfor aerodrome EKBI [EKBI50882B] connecting to MIKRO

Suggestions?

Torben

0

Share this post


Link to post
Share on other sites

@Torben: For Danish airports without SID entry points you plan to the appropriate holding point. For EKBI that would be either LO (or LOKSA) or GE (or GELBA) depending on which runway you intend to land on.

For airport-specific information on arrivals (and departures for that matter) you can look in the Danish Aeroservice Information Package (AIP) part 3, AD2.

Look for the text documents, direct link is HERE for EKBI. In chapter/section 22 (page 7), you find Flight Procedures, which describes procedures for arrival and depature from EKBI.

The structure in the text documents follows a standard (as far as I'm aware), which is followed by all European countries. So once you get the hang of it, it becomes quite easy to read for other airports in both Denmark and other European countries.

If you have any other questions feel free to ask :-).

Best regards,

Mikkel

0

Share this post


Link to post
Share on other sites

Thanks, Mikkel

What I found was that you need to choose a runway and appropriate fix and not "just" plan the enroute section - a bit different from what I'm used to. Even after choosing an intersectio very close to the airport (<5nm) the program didn't accept a dct to the airport (EKBI). I can live with that - but I think I'll plan for worst case scenario (longest SID/STAR) in order to be sure that I have sufficient fuel for my trip.

Torben

0

Share this post


Link to post
Share on other sites

The reason you cannot choose an intersection close to the airport is that it is mandatory to file direct to one of the aerodrome holding points (LO/LOKSA, GE/GELBA). In EKYT it would be AAL-vor and so on. Good luck on your planning :).

Thanks, Mikkel

What I found was that you need to choose a runway and appropriate fix and not "just" plan the enroute section - a bit different from what I'm used to. Even after choosing an intersectio very close to the airport (<5nm) the program didn't accept a dct to the airport (EKBI). I can live with that - but I think I'll plan for worst case scenario (longest SID/STAR) in order to be sure that I have sufficient fuel for my trip.

Torben

0

Share this post


Link to post
Share on other sites

Stuff like this should have been in the manual, I've been searching around for this sort of thing for days, thanks Jarkko (and others).

0

Share this post


Link to post
Share on other sites

I must say that despite the good explanations, i have difficulties to corrigate the errors. Often, after trying to corrigate an error- message i get even more of them...

An error-message that i really don't understand is:

"NOSTO UL612 KUMBI DOES NOT EXIST IN FL RANGE F000...F245"

Iif i make a mousover the UL612-track it says "min alt 250 / max 600". And since my cruise altitude is FL 350, this error really doesn't make sense. Is this perhaps a bug?

Cheers

François

0

Share this post


Link to post
Share on other sites

Hi François

Could you post your complete route (including departure and arrival airport)? Then we can try an replicate it and find an answer.
Best regards,
Mikkel
0

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.