falconno

Thank's so very much for the confirmation. Indeed I have experimented and it works great! Makes the life easier to us procedure nuts:-jumpy

Hi AJ,First of all, I assume that you have defined the fixes in the FIXES section. If not, you will certainly get an error message.As a general rule, a procedure file have three sections:-common part (SID FLL9 FIX FLL)-runway transition (RNW 09L KEEP TRK UNTIL 1000)-enroute transition (TRANSITION ZAPPA FIX ZAPPA)Set up the file in this order. You can read more about this in Terry's tutorial on page 5. In your procedure, there are some syntax errors. The HDG(or TRK) command, ex "HDG 90" must be followed by HDG 90 until (FEET), or HDG 90 until 5 FROM NAVAID ABC, HDG 90 INTERCEPT RADIAL 160 FROM NAVAID ABC etc. Your SID may look like this(I have used NAVAID instead of FIX here)SID FLL9 NAVAID FLLRNW 13 HDG 90 UNTIL 1000RNW 09L KEEP TRK UNTIL 1000RNW 09R KEEP TRK UNTIL 5 FROM NAVAID FLLRNW 27R KEEP TRK UNTIL 1000RNW 27L KEEP TRK UNTIL 1300RNW 31 HDG 270 UNTIL 1000 TRANSITION ARKES NAVAID ARKES TRANSITION BEECH NAVAID BEECH TRANSITION MNATE NAVAID DHP NAVAID MNATE TRANSITION PREDA NAVAID PREDA TRANSITION THNDR NAVAID THNDR TRANSITION ZAPPA NAVAID ZAPPAThis is an example ONLY, as I don't have charts or know the ap, and will not reflect the real one. You must probably fill in more commands, but it should help you get started.

Armen and all..I've tested this on severeal "DME" transmitters and it seems that they all show lateral guidance to 180 degrees as a "default". Look at the pics below.The first showing exactly what happened to Armen. The second the actual position and actual heading to the transmitter.http://forums.avsim.net/user_files/86763.jpgThe actual heading to the transmitter is 283:http://forums.avsim.net/user_files/86764.jpgAll the DME's I tried came up with the same result, 180 degrees. I also tried to create some bgl's with DME transitters and this returned the same info, 180 degrees. As Brad says, IRL there are no needles at DME's. So as Markus replied; " I'd say the question is rather why there are ANY needles visible at all." Maybe it's possible to get this sorted out in a future update??Another part of the story is that these stations I tested actually are TACAN's and not only DME's....

The star's are pretty straightforward, most of them goes directly on to KEF VORTAC wherever you approach from. You can use an appropriate airway to KEF, and then select KEF transition in the approach section.Charts for this including holdings and alt restrictions are available at Eurocontrol, or I could send you one....

Hmm, as far as I can see the procedures included in the "PMDG_Procedures" for BIKF are pretty complete.

I would also consider Aeroworx Beechcraft B200 as the twin engine prop, excellent model with good realism and flight dynamics. After the PMDG aircrafts, the B200 is my favorite :-sun1

Hi KavanI can't speak for PMDG, and I must admit that I don't use fs atc very often, but you have som options here;Purchase a flightplanner like FsBuild, it will create your flight plan complete with sid and stars. Then you can export the fp in both rte and pln format. It will even calculate the fuel for you. Great utility, and can be used as standalone, worth the price. You may also consider FsNavigator, it will also export to both rte and pln.Another option is to create the flight plan in Fs Flightplanner, and use a freeware utility called "pln2rte" to export the fp and open it in the FMC.

Hi NickWell, I started a topic regarding this issue, and also asked if someone from PMDG could confirm this, as it wasn't mentioned in the release announcement, but no answer yet... You can see the post here with some pics: http://forums.avsim.net/dcboard.php?az=sho...59404&mode=full.Anyway, something has changed and it seems to be working...Edit: David, you beat me :-)

Hi there.First of all I will say thank you PMDG for the great product updates to the 737 series, works great for me.I have done a series of tests on holding patterns, with entries from many different angles, and now this works great! Look at the pict below, earlier the ac would not pick up the holding pattern from this angle, now it does to it very well. Hdg to entry point 345, inboundcourse holding 106. http://forums.avsim.net/user_files/86095.jpgNow the ac overfly the holding entry point, makes a turn and revert to hld entry, great! Thought I would let you know.One question, I remember Anthony Merton mentioned some time ago that the command syntax for Sid/Star's would be updated in a future update with the command TURN LEFT/RIGHT DIRECT ... I didn't see this issue mentioned in R Randazzo's announcement for the service release. But I tried it, and it seems to work. I have done quite a few test writings and test flight with this command, and it seems to be implemeted and the aircraft follows the path in LNAV very well. Can anyone from PMDG confirm this?http://forums.avsim.net/user_files/86096.jpgThe first example is a turn much greater than 180 deg, while the last two are ca 180 deg. This was hard to do before this service update.

Hi BradThanks for your excellent contribution to this subject. And no, it's not confusing at all. Great "tutorial" in using PBD's and PB/PB. Neat feature really as we can define points anywhere in space for navigation...Actually I've used this feature quite some times. It just takes a bit of trial and error to get a good result as long as we don't have the possibility to create wp's relative to user created wp's(other than in sid/star creation as mentioned).As stated above, it's much easier to do this if you have FsNav running in the background. And the approach:http://forums.avsim.net/user_files/85992.jpgNot a great issue at all though, but is this possible in a future FMC upgrade, a Supplementary Database and the possibilty to create wp's relative to user created wp's? Anthony, someone?

HiYou probably have a SID/STAR file for KORD already as part of the installation process. KORD is part of the PMDG_Procedures package by Terry Yingling. The latest release 0407 can be downloaded from the PMDG site.

Hmm, I had this once long time ago. If memory serves me ok, what I did was to delete the fs9.cfg and let FS build a new one on startup. So you could try this first. If you have customized you fs9.cfg, these changes will be lost. As for the removal tool I haven't tried it on the 800/900, it says 600/700 removal tool...

Steve, in the menu, select PMDG, 737NG, Styles, Colors, CDU. I use Sea green.Edit; Ramon, didn't see your reply before I sent mine

In addition to what have been said, also keep in mind that the APPROACH REF page will not display the dest info until established at crz level (IF you have entered the dest rwy, procedures etc before takeoff).Normally you will not enter the dest rwy and approach procedure before takeoff but when instructed by ATC in crz or desc(according to traffic, wind direction, etc).http://forums.avsim.net/user_files/85775.jpg

As far as I know they are not the same, they have different authors. I haven't compared them in any way, but I am using the ones from Austscene for the moment, and I am well satisfied with the few I have used.

Hi again.As I mentioned earlier in this thread, the LFMK-Salvaza procedures are now ready for download at Navdata. FYI, I will also write the procedures for LFMP-Perpignan, will be ready in next week.

Hi all again.Maybe I was a little bit unclear, but I did not state that the OVERFLY command could be used directly in the FMC. What I meant was of course to insert the OVERFLY command in the procedure file. Sorry for the confusion.

Sebastian,In addition to what have been said, there are not a complete procedure package for every single ap in the world. As you know, you have the user uploads at Navdata and the PMDG_SIDSTARS from PMDG and Terry Yingling.If the wp's, navaids etc referenced in the SID/STAR procedures are missing in the airac you'll get an error message. It's a good practice to have procedure files based on the same airac cycle.As far as I can see, there are no published approach procedure for rwy 28 at LFMK. As pointed out from the others here, it's fairly easy to write your own procedures, though it may be a lot of work. Anthony Merton has created an easy and straightforward language for the FMC, so you can use just text files created with Notepad. Terry Yingling has done an excellent tutorial on this, available in the library. If you give me a couple of days, I'll see if I can nail down some procedures for LFMK.... if there's interest for it....

Mike,To overfly a waypoint there may be several ways, but you could insert a PBD waypoint or even a ATW waypoint close to the waypoint you wish to overfly. Of course you can also change to HDG mode, and revert to LNAV when over the waypoint.If the waypoint is part of a sid/star procedure, you can edit the waypoint with the OVERFLY command, ex NAVAID OVERFLY ABC, or FIX OVERFLY ABC, where ABC is the waypoint or fix.

Marcello,A little bit OT, but as info: As the PMDG_SIDSTARS package don't contain LFPG, the procedure file for LFPG you have is most likely one downloaded from Navdata. This file don't match AIRAC cycle 0407. The BUREX navaid is no longer a part of Airac, and this triggers your error message. The BUREX STAR procedures are most likely removed or renamed.But you can find a more updated one that will function together with the current airac here: http://stefltt.free.fr/FlightSim/Downloads...MDG_SIDSTAR.php

Hi AndreTake a look at this post: http://forums.avsim.net/dcboard.php?az=sho...esg_id=88&page=.Navdata have service maintenance from 01-07 to 05-07-2004 and will be transfered to a new server. Just to the better I'm sure.

Mats,you have much greater knowlegde on this than I have, but based on my experience the DIRECT command will only give a better view of the magenta line on the ND, not in flying though. If I don't remember wrong, there was a post about this a long time ago, but I can't find it. Also in Terry's tutorial v2 it says: "Please take note that the keyword

Hi SimonYou wrote "that is should go DIRECT to NAVAID MG after D250O", and that's exactly what's the FMC is trying to do. It will force the plane back on to the 25 deg radial. But if you look at the charts it tells "turn right to MG Lctr 045 deg bearing". In some way you have to tell the FMC to get on to that 45 radial. There are a couple of options:1) Try this one: SID BERT1D RNW 13 NAVAID MG AT OR ABOVE 2200 NAVAID D250I NAVAID OVERFLY D250O KEEP TRK INTERCEPT RADIAL 45 TO NAVAID MG DIRECT NAVAID MG AT OR ABOVE 9000 NAVAID D330K AT OR ABOVE 10000 NAVAID D343L NAVAID BERTALooks like this and id actually flyable:http://forums.avsim.net/user_files/82079.jpg2) You can insert a fix on the 45 radial like "FIX MG45 COLOCATED MG 226 10". Then you will get this: SID BERT1D RNW 13 NAVAID MG AT OR ABOVE 2200 NAVAID D250I NAVAID OVERFLY D250O FIX MG45 NAVAID MG AT OR ABOVE 9000 NAVAID D330K AT OR ABOVE 10000 NAVAID D343L NAVAID BERTA.And here is the result:http://forums.avsim.net/user_files/82080.jpgBoth of these will force the plane on to radial 45 as per charts.But whatch your speed in these turns, around 220 seems to be ok.

Hi James.I suggest that you take a look in the FMC manual about entering route and waypoints. Timothy Metzinger's tutorial also has an exact explanation of entering a route with isecs, airways etc. in the FMC.To give you a starter, enters like OCK1F and OCK1A are most likely stars, DOGAL, CYMON etc are intersections, fixes, navaids and so on. UL9, J62, UL607 are airways. I will also recommend flight planner like FsBuild2(payware) to build such routes. It will autogenerate the route completely with sid/stars, isec's, airways etc, and it will also calculate fuel for you.

Mr Earhart, read the posts again, Thomas said: "I just used another font (which I found on the net) and changed the text in Paint Shop Pro"