falconno

Glad it worked for you, Keith.Again this demonstrate the importance of having user uploaded procedure files "in sync" with the current airac data. If they are not updated according to changes in airac, these errors will occur. As you might know PMDG Prcedures made by Terry Yingling are always up to date and in sync with the current airac. They do not cover every airport and may not be complete, but at least they are always up to date. See also the thread pinned at the top of this forum " SID/STAR/IAPs updates explained"As a sidenote, over at the Navdata forum there is a poll and some interesting discussions on how often we need or want to have the airac datas updated according to real world.

Keith,It means as stated, REDNO is no longer a part of this procedure and has been removed from the airac cycle, as in real life. The author of this procedure has not updated it according to earlier AIP changes.If you take a look at the latest star charts for EGJJ you will also see that REDNO is replaced by DIKRO in the star procedures JERSEY2B and JERSEY2H.You can easily change this by opening up the SID/STAR file for EGJJ and replace REDNO with DIKRO in star's JERSEY2B and JERSEY2H. Then you will be up and running again.(I haven't checked the other procedures though but at least you will not get any error messages with these changes.)

Yes it's normal. But this is for future use if ACARS. It has no function by now as ACARS is not implemented yet.

I don't think the PXR/240/13 fix will be correct here. The charts states hdg 240 after passing 1550. So the 240 is not in reference to PXR, but where you are after passing 1550. This may be tricky to enter in the FMC.There may be several ways to do this, but in this case I would have done this the old fashioned way and use HDG SEL.1. Before takeoff, on the FIX page enter a 13NM from PXR to get a green arc radius from PXR. Then you have a visual reference to 13NM (I prefer to do this) - Also enter BXK in VOR1 and PXR in VOR2: Enter 257 in the COURSE window, enter 258 in HDG window.2. After takeoff at 400 RA select HDG SEL as your roll mode. Fly rwy hdg to 1550, then dial in 240 in the MCP (also remember the 7000 restriction until further clearance)3. Follow 240 until 13NM PXR on DME readout4. When reaching 13NM PXR dial in hdg 280 in the MCP5. When established on hdg 280 arm VOR LOC. 6. The plane will then fly hdg 280 and intercept radial 257 to BXK vor.Then follow the rest of your sid transition.Another way to make use of LNAV and VNAV is to write this into a SID procedure. Then you will have something like this:SID BXK.2 RNW 25L RNW 25R RNW 26 TRK 258 UNTIL 1550 TRK 240 UNTIL 13 FROM NAVAID PXR TRK 280 INTERCEPT RADIAL 257 TO NAVAID BXK NAVAID BXK

Just press the LSK6R (EXIT HOLD) and then execute the command with EXEC button. You will see that the text changes to EXIT ARMED(in grey text) at LSK6R. When you reach the initial holding point again the aircraft will leave the holding.

HiTo code this into the procedure I think you will have to define a fix on the intersection of the two courses, runway heading and the SMO 160 radial, for each runway with the alt restriction(3000B) included. At some airports these crossing intsc may be predefined. On the other hand the easiest way may be to set the at or below 3000 restriction on the SMO R-160 fix manually before takeoff as Ryan described.If you set up the departure manually in the FMC, you could also enter this alt restriction on the SMO 160 radial as a PB/PB waypoint, or course intersection waypoint. As an example for runway 24R you can enter R0954250/SMO160 in the scratchpad and upselect this to LSK1L, and enter /3000B at LSK1R.For the other rwy's enter this at LSK1L25L:R0947250/SMO16025R:R0946250/SMO16024L:R0953250/SMO160The R09xx are intsc in the database for each runway, 250 is the heading.Or you can use HDG SEL and LVL CHG or handfly as described earlier, several options here....

As for for these Norwegian repaints, you can get a lot of them here:http://www.virtualnorwegian.com/index.php?...lerpmdgrepaints

Or, if you have a TV-out on your video card, and a digital camcorder with firewire, and a firewire card on your pc, you can get very smooth and good results. When you have recorded what you want, you can edit the recordings with software on your PC. Not any frame rate hits either.Fraps may be good, but it eats fps, unless you have a testosterone machine, which I don't have:-)

Hi NicolasIf you download afcad_vhhx.zip you will at least get the runway lights with this afcad file. With the Afcad2 program you can easily add the ILS if you have the correct coordinates for LOC, DME and GP.In the scenery package from Roger Mole there are two bgl files named CHINAILS and CHINAMKB. Slip these two into your ...(Fs9)Addon sceneryScenery folder, then you have the ILS. I am not shure, but it looks like the ILS at VHHX in these files are slightly out of position. So if someone have the correct coordinates for LOC, DME and GP this is an easy task to do in Afcad.

Hi there.All runways are listed in the Airac files. But it seems that these runways for some reason are missing in the SID/STAR file for CYYZ in the PMDG_Procedures download. It is possible to edit the file yourself, just add the following lines under the RNWS section in the sid/star file:RNW 06RRNW 15RRNW 15LRNW 24LRNW 24RRNW 33Lyou will get the runways, but no procedures.However in the procedure file you can download at Navdata(CYYZ_v4), all runways with procedures are listed. So I suggest that you download from here to get the complete procedures.Also take som time to read the thread pinned at the top in this forum about "SID/STAR/IAPs updates explained. New 737NG owners should read this." Very useful information about these issues.

Hi Joe"Where did you understand that the crossing for BEUTY was At or below 8000 ft?"Just to clarify, he did not wrote that, he wrote "AT OR ABOVE 8000" if you look at it again.In addition to what Michael wrote, the "AT OR ABOVE 8000" command must be correct here if you look at the plate, it clearly states 8000. But it also says "Expect to cross (BEUTY)at 10000". And this is as Michael says given by ATC.As I read this the 8000A is the "base" altitude restriction along this segment. Then you have further guidance by ATC to EXPECT 10000 when crossing BEUTY(by ATC). My charts also states that.This editing must(if given)eventually be entered by the pilot directly in th FMC if necessary, not as a restriction in the SID/STAR file, that would be wrong. So I think the procedure you have is correct.You can also delete the 8000A at LSKxR and let the FMC calculate for itself, and if the result then is within any restrictions, this is a good alternative. Or you can as you say insert 10000 as a hard constraint at LSKxR.

Of course you are right Mats, I wasn't precise enough here. Some day I'll stop reading these Classic documents and stuff about the air data inertial reference unit, confuses an old NG desktop pilot:-smile12

Hi Frank.As Enrico indicated, the FMC reads it's data from the airac files(and thus updated), and the NAV radios read the old datas in FS9, unless you have any updated add-on scenery or Afcad with the new vor stations. Any FMC flight plans will be fine(LNAV), but the VOR/DME approaches and dme readouts will be tricky with the old vor. However there is an easy and quick solution. Open up AFCAD and insert the new VOR stations at the correct positions and save, done in seconds. Then you will have correct NAV radios, correct DME readout, and correct VOR needle and course deviation indicator on the PFD and ND. These new navaids will then be usable for all FS aircraft, not only the NG.Here are the info for these two stations you can use in AFCAD(I don't know the range though):EL PRAT PRA DVOR/DME 114.30N 41 16.59E 02 04.54BARCELONA BCN DVOR/DME 116.70N 41 18.26E 02 06.29As for the autotune, this is not implemented, the real ones has it though.

AS Thomas said there is a new runway at KMIA, and as a result renumbered runways. This has also been included in the Airac and SID/STAR files for a long time now. So the latest Airac cycle, new procedure file and new Afcad/scenery will do the trick. You may also try a search on KMIA here, the issue has been discussed many times.

Glad it worked for you!I'm not quite sure what you mean with "What is the purpose of LSK5R if it doesn't change to the selected active runway ?"LSK1-5R will always list first the approaches (if defined in the procedure file), and then available runways(as defined in the procedure file). If you want to select a rwy without approach procedure, just select the rwy number, 06 or 24.In the APPROACHES section the runways are included with the published approach procedure. If you are cleared for an ILS approach, select (in this case)ILS24. No need to select the rwy on top of that again (not possible either). Maybe this is what you mean?

Glen, have you tried page 2 ? I'll bet you'll find 24 there:-) As a general rule to get the 'RWY EXT' prompt, select the rwy under RUNWAYS, not the ones under approaches with ILS06, DME24 and so on..

Jack, FYI if you have the -800/900 upgrade you can map the DOOR OPEN/CLOSE function to a single key, under the PMDG,GENERAL,KEYBOARD ASSIGNMENT. One key for forward pax, and another for rear pax and cargo doors.Refer ro the manual, "TITLE AND MENUS"

>it worked. thanks. i don't know why the manual said to enter>a decimal point..huh?FYI, it does not say so either!:-)

Hi there.MSFS original navigation data are hardcoded into bgl files(scenery files) within fs, and based on data from Jeppesen valid in 2002(?). They are not directly editable as the text files you mention in Squawkbox. For Squawkbox and a lot of other add-ons the case is somewhat different as you mentioned. For those you can also get updated real world navigation data (Airac cycles) every month from Navdata. You can also add customm waypoints to the database if you like and if you know the format.You can however make some modifications to the Fs9 data and make new scenery files(bgl's) and edit/add navaids with a scenery program like Afcad, Airport for Windows, SceneGX etc.But the easiest option to add your own fixes/points within Fs9 is to use a flightplanner tool like FsNavigator. Make your flightplan/route here, add your own custom fixes/waypoints, and export the plan as a Fs9 plan. Then import it into the FS9 planner. Both FsNavigator and FsBuild can export your plan to Fs9, SquawkBox and a lot of other formats and add-ons.

You may try this link and navigate around there: http://www.sia.aviation-civile.gouv.fr/htm...eset_aip_fr.htm.You can find the same charts here too: http://www.ead.eurocontrol.int/

"I couldn

Cliff -I bet it's the same as this one: http://forums.avsim.net/dcboard.php?az=sho...id=71539&page=2

Mr/Mrs nameless?(obriets) -All the basics about what's have been discussed in this thread are described in the FMC manual:Place Bearing Distance waypoints (PBDs)Bearing / Bearing waypoints (BBs)Along Track waypoints (ATWs)Latitude Longitude Waypoints (LLWs)Helmut -The format for using this for a lat/long at lets say: N 63 10.2 E 008 10.1 will be N63102E008101. So you insert into the scratchpad a 13-digits continious row without slashs.

Thanks Vangelis for the good "in-depth" explanation of the along track waypoints. A small addition to what's mentioned; these ATW's are also very useful (among other options) to meet any ATC restrictions, speed, altitude commands, along the route where there are no matching waypoints. Enter them exactly as instructed by ATC, and let the FMC do the hard work:-) Ex: "PMDG 123, continue approach above 6000 until 15 from XYZ vor". Make the along track waypoint as Vangelis explained as XYZ/-15 (here 15nm before XYZ vor) at LSKxL, and enter the the altitude restr. at LSKxR as 6000A.

HiSeveral possibilities:1: On the arrival page, click on the appropriate rwy, then you can define a point", RWY EXT" along the runway extended centerline. Enter the desired distance and exec. Remember to close the "route discontinuity's". See below:http://forums.avsim.net/user_files/99926.jpghttp://forums.avsim.net/user_files/99927.jpg2 You can also insert a PBD waypoint in reference to the airport, navaid intsc etc.. The point below is entered as ENKB260/10. ENKB is the airport, 260 heading, and 10 is the distance:http://forums.avsim.net/user_files/99928.jpg