How I can add an airport that does not appear in the programming of the FMS?

how small is the airport?

SETM

Hiya

Just did a search on Wikipedia and cannot find an ICAO code for that airport, or even country, what is the airport name and which country is it in?

Kind regards

John Calleja

You need to add its runways to wpnavapt.txt in the FSX\PMDG/NAVDATA folder. Any ILSes, VORs etc on the airport's grounds need to be added to wpnavaid.txt. Then you'd need to code a terminal procedure file for the SIDs, STARs, and approaches which are in FSX\PMDG\SIDSTARS

Thanks Ryan, thanks for the help, Greetings from Cuenca, Ecuador in south america

Ryan, or someone can explain to me that means all these numerical values​​, for example:

 

CUENCA-MARISCAL LAMAR SECU05 06234054 -2.894731 -78.991139000.0005408306

CUENCA-MARISCAL LAMAR SECU23 06234234 -2.884200 -78.977653110.9023408256

 

 

which means all these values: 06234054 -2.894731 -78.991139000.0005408306

06234234 -2.884200 -78.977653110.9023408256

 

Thanks for the help

Please sign your name to your posts by the way - that's a rule here.

 

Is the airport already in the navdata? If so it's probably below the runway length limit for the NG - 4000 feet I believe.

Hiya

Just did a search on Wikipedia and cannot find an ICAO code for that airport, or even country, what is the airport name and which country is it in?

Kind regards

John Calleja

 

3rd result in a Google search.

 

http://worldaerodata.com/wad.cgi?id=EC63627

If the airport is Camilo Ponce EnrIquez then it's listed in the NavData as SECA

Hello All

 

So, demistification:

 

CUENCA-MARISCAL LAMAR SECU05 06234054 -2.894731 -78.991139000.0005408306

CUENCA-MARISCAL LAMAR SECU23 06234234 -2.884200 -78.977653110.9023408256

 

Each of the above entries are runway descriptions.

 

CUENCA-MARISCAL LAMAR = Name/Name City

SECU05 = ICAO identifier of the airport + tenths of runway mag heading rounded to neareast ten (changes every 10 years)

06234 = runway usable length in feet

054 = precise magnetic heading

-2.894731 = lattitude (negative means Southern)

-78.991139 = longitude (negative is EAST)

000.00 = ILS Frequency (none installed on this end of the RWY, see ILS for the pair end of the RWY - 110.90 MHz)

054 = ILS Mag course (should and is the same as the precise RWY orientation - no approx here)

08306 = beginning of the RWY (touchdown) altitude

 

Same applies to all definitions.

 

By the way, we are talking about Mariscal Lamar International Airport in La Castellana, Cuenca, Ecuador

 

 

Hope this helps,

 

Ionut G. Micu

Romania

Thanks friend, thanks for the tip, did not know, for Ryan and all of you my name is Freddy Narvaez, Greetings from Cuenca, Ecuador in South America.

 

Thanks Ionut G. Micu, for the complete explanation, thank you very much

 

Yes, I know that the information is of Cuenca SECU, I put as an example, the information sought was SETM, now it is SECA, thanks to all for your support

Then you'd need to code a terminal procedure file for the SIDs, STARs, and approaches which are in FSX\PMDG\SIDSTARS

 

This is not necessary Ryan. An airport will be recognized just from the 'wpnavapt.txt' file.

....it's probably below the runway length limit for the NG - 4000 feet I believe

 

Hmm, I found some airports in the list telling me that the criteria might be even worse... :Whew:...down to 3000ft (which surely is good for emergency cases).

 

I had developed a little tool to filter out the airports from FSX fulfilling certain criteria, like runway length (I usually selected 3000 ft for the NGX) and surface (water and ice, sand, dirt etc. are not the ones we are looking for) and to write the results in the proper format into a text file. Due to the wandering magnetic pole I wasn't able to use this file directly because of the changing runway identifiers (36R becomes 01R) and developed airports (e.g. EDDF getting a new runway and renaming some existing ones). If there is a mismatch to an existing terminal procedure file you are running into an error message (this is welcome!). One day, having a lot of time in my hands I'll think about the inclusion of terminal procedure files as well - in two ways, first to map what's in the sim and second to get delta information in order to work on changed airports in FSX. It's a mess to use the latest navdata finding sometimes no representation in the sim where airports are even misplaced for miles in some cases.

 

Ryan, I hope that any new format of your nav-files will allow to search for proper keys and keywords...

 

Before I forget: I'm using the free tool makerunways from Pete Dowson which produces a quite comprehensive XML file that can be read by MS Excel (I'm not sure whether Open Office can do it now). It contains all required data.