April 28, 2007

JTF Assist

1. Unrar.

2. Burn or mount with Daemon tools.

3. Install the game.

4. ----enter any cd key ----

5. Play the game.



45789-24695-24598-24896-54879



or



87952-26597-45965-45555-45877



or



4jhj4-l7fks-48dhe-58wsl-lertt



alright i found the solution.. too bad i already deleted the game.



Click the start button and click "Run...".

Typ "regedit" (without the quotes)

Go to the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

In the right window doubleclick "ProgramFilesDir".

The value of "ProgramFilesDir" is probably "C:\Program Files". Change this to a drive with at least of 3 GB of free space. For example, I changed it to "D:\Program Files" (Make sure sutch folder exsists).

Install the game.

After you've Installed Joint Task force change the value of "ProgramFilesDir" back to "C:\Program Files\"







ok found the solution. just have to change the FullscreenHeight setting in the settings.ini



Game works fine now





Powered by ScribeFire.

April 26, 2007

Airbus 330-200 Engines

Prior to taking the air again, I think that it’s now justifiable, after 10 successive legs, to wonder how we actually start the engines of our A330-200 aircraft.

Starting the engines of an Airbus airliner is easy. The main reason for this is that engine start, like many other Airbus systems, is a partial automatic procedure.

 

To explain the procedure, I propose to start from the 'cold and dark' cockpit configuration. This is a simple procedure indeed, but we will take some time here to wander from the point and focus on some of the concerned systems.

 

First of all, we have to supply the aircraft with electrical power.

Before engine start, the aircraft can supply its own DC electrical power coming from onboard batteries (BAT 1, BAT 2, APU BAT). The DC electrical system supplies 28 Volt DC and it is mainly used to start the APU, or supply the aircraft when other sources are unavailable. When their voltage goes below a certain level, the batteries will charge from the AC electrical system driven by the engines – just like a car battery ! The AC electrical system provides 3 phase 115/200 Volt, 400 Hz AC provided by engine driven generators installed on each engine. A further generator installed on the APU is used to provide AC power before engine start (and after engine shutdown) or in case of loss of one or the two engine generators. And finally, in case of total loss of electrical power during flight, the aircraft can be supplied by an emergency generator driven by the RAM air turbine, using the high speed air flow to provide power a bit like a wind engine.

APU and engine generators will automatically work once the concerned engine runs, if their corresponding switch on the overhead ELEC panel displays no light. In this configuration, APU generator will also automatically stop once engine generators power become available (or external power is connected). Pilots may still disconnect any generator from the electrical system by switching it off ("OFF" will illuminate). 

On the ground, the aircraft can also be supplied by external power.

We’ll use the aircraft onboard system to start the engines.

 

 

The 3 batteries are switched on.

By the same time, the avionics and the main panel CRT screens come alive.

 

It’s now time to switch on the fuel pumps, but let’s see first how is roughly working the fuel system.

On the A330 type, the fuel is contained in one center and two wing tanks. Because of in flight structural reasons, the center tank is usually filled last and used first. The wing tanks are divided into inner and outer cells which are connected by transfer valves. The engines are fed from the inner cells. There are two main fuel pumps and one standby pump in each inner tank. The main pumps all work in normal operations. If a main pump fails or is switched off, the standby pump takes over. The two center tank pumps work as long as there is fuel in the center tank. Fuel transfer from the center tank to the inner cells is controlled by inlet valves, which top up the inner cells while there’s still fuel in the center tank. After that, once one inner cells goes below a preset level, transfer valves open to allow fuel from the outer cells to flow into the inner cells. In addition to that, a crossfeed valve connects the left and right fuel systems, allowing both engines to be fed by both wing tanks, or one engine to be fed by both wing tanks in case of engine failure and single engine situation. Fuel transfer and valve operations work automatically during flight. The Flight Management System computes the best fuel load balancing in real time for the best aircraft performance. This was once the job of the Flight Engineer. Nowadays Airbus pilots are however always informed by ECAM messages, and can still manually operate on fuel transfer using the Overhead's  FUEL panel.

Now that we’ve demonstrated that fuel pumps may be useful for the engines, let’s switch them to ON ! 

 

 

On the picture, left and center systems have already been set to ON. You'll notice that the center tank pumps show 'FAULT' : this is normal, since there's no fuel in the center tank needed for this new short flight.

 

The next step is to start the APU. The APU (Auxiliary Power Unit) is a small, single spool (N) jet engine located in the aircraft tailcone. APU, which is now common with every modern airliner, allows the aircraft to be independent of external pneumatic and electrical power supplies. The APU can then provide bleed air for engine start and cabin air conditioning and has its own generator to provide AC electrical power (see above). APU can be started on the ground as well as in flight. Starting the APU works almost the same as switching on a lamp. Switching ON the APU MASTER SW button (blue "ON" illuminates) arms the APU system for automatic startup sequence and opens the APU air intake flap. Just below, the START button will initiate automatic startup. When completed, a green 'AVAIL' will illuminate and will also appear on the upper ECAM, meaning that APU is available.

 

 

 

 

The latest image shows both upper and lower ECAM after APU start.

 

Now that the APU is running, we can use its bleed air for engine start. High pressure air (as well as electrical power) is needed to start the main engines. Bleeding air into the engine will initiate the spool rotation until it reaches a preset rate at which ignition will occur.

Some technical background about the jet engine is not superfluous here before going further.

 

The turbofan jet engine which is powering our aircraft, as well as most of nowadays airliners, is an evolution of the twin spool turbojet engine.

A spool is a couple compressor – turbine mounted on the same shaft, and then rotating at the same speed. The compressor and turbine are in most cases a succession of stages. Each stage includes a rotor grid which is integral with the shaft. The rotor grid is a disc fitted with a great number of rotor blades. In modern engines, the rotor blades pitch is variable as a function of the air flow to optimize performance. Each rotor grid is followed by a stator grid, whose purpose is to straighten up the flow to the axial direction of the engine. On most modern engines, the stator vanes pitch is also variable. Each grid will modify the air flow direction and speed.

The intake air will cycle throughout the engine. On the basic single spool engine (like the one that powered the first generation Boeing 707 or DC8), the cycle includes the compression, combustion and expansion. During the cycle, air pressure, volume and temperature change, linked together following thermodynamics laws. The compressor will make the first step. Air pressure and temperature will increase. In the combustion chamber, which is inserted between the compressor and the turbine, compressed air will be mixed with fuel by a complex mixing system. The fuel combustion will considerably increase gasses temperature as well as volume, while pressure will remain almost constant. And finally, gasses will first expand in the turbine driving the compressor, and then complete their expansion in the nozzle, providing the rear thrust that will propel the aircraft in the opposite direction, as result of the well known reaction law. The temperature will decrease during the expansion phase, giving the exhaust gas temperature (EGT) which is an important engine parameter to be controlled by the pilots, with the turbine materials thermic constraints in mind. A dramatic and sudden increase of EGT will result of an engine fire.

The twin spool turbojet (dating back to the sixties) has two concentric shafts rotating at different speeds. A good example is the PW JT8D engine, which powered many aircraft models including B727, B737-200, DC9 and MD80.

The low pressure spool (N1) includes the low pressure (LP) compressor and the low pressure turbine.

The high pressure spool (N2), located between the LP compressor and the LP turbine, includes the high pressure (HP) compressor and the high pressure turbine.

N1 spool rotation rate is often the main driving parameter of the engine, while N2 plays a part during engine start. As an example, take off rate on the CFM56-3B1 (powering the B737-300 and A320 families) will bring N1 to 5175 RPM and N2 to 14460 RPM. Meanwhile, N1 and N2 rotation rates will not be directly displayed as RPM (revolutions per minute) in the flight deck but as a percentage of a maximum rate. Jet engines are characterized by two maximum rates: the maximum take off performance (TO), which is the highest, but limited to a 5 minutes time interval; and the maxi-continuous performance (MCT), which is lower but unlimited in time. Because the gauge range exceeds 100% for the engine rate, this is probably the MCT constant that is used as reference.

The intake air is sucked in by the LP compressor. Unlike on the single spool engine, a part of the intake air will be derivated during the LP compression phase and will NOT be driven to the combustion chamber, therefore bypassing the normal cycle. There are then two air flows on such engine: the cold stream that bypasses the hot gasses generator and the hot stream which goes through the normal cycle. This introduces a new parameter: the bypass ratio, which is defined as the ratio between the derivated air quantity and the normal cycle air quantity, and can then be seen as

 

                        cold stream air quantity

Bypass ratio =  ──────────────

                        hot stream air quantity

 

For a twin spool turbojet, the bypass ratio is roughly equal to 1. Note that for a single spool engine, it will be equal to zero.

We can demonstrate that increasing the bypass ratio will increase engine performance, reduce fuel burn as well as engine noise.

The turbofan engine is a direct application of that concept. In a turbofan, the first stage of the LP compressor, which sucks in the total intake air, is an oversized rotor grid, called the fan. The first turbofans powered the B747, DC10 and L1011 Tristar in the seventies, to be followed by the Airbus A300-B1.

The bypass ratio, as well as the compression rate are greatly improved. The bypass ratio of the first turbofans was close to 5. The big turbofans of the new generation have a bypass ratio equal to 6, with a fan diameter close to 3 m. The General Electric/Pratt & Whitney GP 7200 and Rolls Royce Trent 900, designed for the A380, are currently the biggest and the most efficient engines on the market.

The global thrust provided by such engines is mainly provided by the fan. The fan produces from 70 to 75 % of the engine thrust. It can then also be seen as a streamlined propeller driven by a first generation twin spool turbojet. Besides, only the fan blowed cold stream air will be used by the reverser system.

Rolls Royce engines have a distinctive feature: they have 3 spools: N1 (LP), N2 (IP for Intermediate Pressure) and N3 (HP). In this case, the fan acts as the LP compressor on its own.

The following diagram shows a generic twin spool turbofan engine longitudinal section, where you'll easily locate many of the components that were introduced here.

 

 

Aircraft engine performance evolution always sees greater bypass ratio, greater pressions, greater temperatures, lower noise emissions, lower fuel burn and lower environmental impact. For example, higher temperatures in the turbine inlet (approaching 1500°C) are nowadays possible thanks to better materials as well as a complex cooling system allowing the blades to work above their melting point. The fan size, and therefore the bypass ratio, however, have a upper limit. The engine cannot grow indefinitely since it must still be able to be installed on the aircraft and the bigger is the fan, the greater will be its aerodynamic drag.

 

Now that we're more familiar with the jet engine – and if you are wondering whether we'll once reach Tel Aviv – let's continue with the startup sequence.

We'll perform an automatic start using the APU bleed air for both engines. Engine start usually takes place during the aircraft pushback.

Switching ON the APU BLEED (overhead AIR conditioning panel) will allow blowing high pressure air into the engine, and more precisely, into the High Pressure spool N2 (that would be N3 on a RR engine).

 

 

On the A330, engine #1 (left wing) is usually started first. Not difficult to remember anyway.

Checking APU BLEED is ON, we set the ENG START selector to IGN/START on the pedestal. Next, we set the ENG MASTER switch 1 to ON.

 

 

N2 spool will start rotating (monitor N2 rate increase on the upper ECAM). Once N2 reaches a preset rate, which is commonly 20% for every jet airliner, fuel is injected into the combustion chamber and ignition occurs, the complete engine cycle can start. While opening the fuel cutoff lever for each engine  is necessary on Boeing planes, fuel injection will be done automatically here at 20% N2 and pilots just have nothing more to do.



Once engine 1 is stable (monitor N1, EGT, N2 and fuel flow on the upper ECAM ), setting ON the ENG MASTER switch 2 will start engine 2 in the same way.

The following picture shows the E/WD (upper ECAM) once both engines are started and pushback is completed. ENG START selector is then set back to NORM mode. APU bleed is switched off, but we will leave APU running until we're airborne and above 10,000 feet. APU & APU BLEED should be started again after landing, so that the aircraft can still be powered after engine shutdown.

 

 

So, if we sum up, to start the engines of our A330 we just had to

 

1) set BAT 1, BAT 2, APU BAT to ON

2) switch ON the fuel pumps

3) start the APU

4) check APU GEN, ENG 1 GEN, ENG 2 GEN "no light"

5) set APU BLEED to ON

6) set engine start selector to IGN/START

7) set ENG MASTER switch 1 to ON

8) once engine #1 stable, set the ENG MASTER switch 2 to ON

9) once engine #2 stable, set the engine start selector back to NORM

10) set APU BLEED to OFF



Switch Off:



The following sequence

 

1) set ENG MASTER switch 1 to OFF

2) set ENG MASTER switch 2 to OFF

3) switch off the fuel pumps

4) switch off APU BLEED

5) set APU MASTER SW to OFF

6) switch BAT1, BAT2, APU BAT to OFF





Powered by ScribeFire.

How To...FS Navigation 102: Continuing A Basic Introduction

How To...FS Navigation 102: Continuing A Basic Introduction

By Ron Blehm (6 September 2005)

Review:

In the last article we discussed how to dial in the ADF to get that little arrow pointing toward the Non-Directional Beacon. We also learned to dial in NAV1 to a VOR frequency and set a desired course with the CRS knob (OBS on some aircraft panels) and how to get onto that desired radial. Although we really didn’t discuss this last time, now that you can also dial in a VOR on your NAV2 radio and it’ll work just like an NDB, pointing you, generally, toward the VOR station. Now, we are going to combine these skills in one small step forward.

Putting Them Together: Pendleton To Portland

You should be feeling pretty good now about using NDBs or VORs for navigating around the FS world. Now all you need to do is to use BOTH of them to get somewhere. Like I stated in the last article, I’ll use VORs when I have them but NDBs can be helpful to get you nearer some runways. Set NAV1 to 114.70 and turn your CRS setting to 252 degrees. Depart from Pendleton, OR in any direction (see screenshot A) and as soon as you can, get onto that 252 radial away from town. As you fly along up to 9000 feet retune NAV1 to 112.30. That arrow should light up right away. (Screenshot B) Continue on the 252 radial toward that VOR – you’re flying along the Columbia River, also shown in that last screenshot. Meanwhile, tune your ADF to 332. (Screenshot C)

Screenshot A
Screenshot B
Screenshot C

At the VOR turn left to 240 degrees. You will now follow that to the NDB (so watch for that arrow to swing to life) which will get you set up for landing. When you are clear of some of the gorge terrain, start your descent down to 3000 feet. I’ll give you a little heads up about what we are doing next. Tune NAV 1 for Portland which is 111.80 and set your CRS to 281 (Screenshot D). As you cross the NDB (I hedged myself a little east of the NDB) turn to 280 degrees, drop to 1500 feet and watch for one of the runway 28’s (Screenshot E).

Screenshot D
Screenshot E

So again, the NDB set us up for landing but this time, there was also a VOR to guide us in. If you practiced the skills learned in Class 101, and have made this flight successfully you are well on your way to a very successful flightsim career!

Standard Departures And ILS Arrivals: Portland to Seattle

Now that you are able to get from one place to the next we need to work on getting in and out in a more orderly fashion. First we’ll discuss getting out of the airport area using a “Standard Departure.” Many airports have what they call “Standard Departures” which are paths or corridors planes need to fly through or on in order to leave the airport area. Some SD’s are designed for safety – to avoid nearby mountains, while others (like the River 6 from KPDX) are designed to keep noise out of residential areas. A Standard Departure will use some type of navigational instrumentation so that pilots can fly the route consistently in ANY type of weather. Not only is this safer, it helps air traffic control know where planes are coming from. So, from Portland, the “River 6” ensures that the sound over Gresham is kept to a minimum. It also allows the controllers in Seattle to receive or pick up the planes as they climb out. Like products coming down an assembly line, controllers can focus on one area of their scopes to watch for planes leaving on the River 6 SD. From the end of the River 6 SD, ATC can then direct planes north, south or east towards their respective destinations.

Set your NAV1 to 111.80 (should already be there from the last landing) and spin your CRS/OBS to 090 degrees. You will see that the radial or line we need to fly on is to our left (Screenshot F). What this means is that after we are safely climbing, we need to turn to about 080 or 085 to intercept that 90-degree radial. Then make a right turn back to a heading of 090. (Screenshot G) Climb out on 090 until your DME reads 6 miles, then turn left to 360 degrees and head north, (Screenshot H) climbing on up to what we’ve been using for this tutorial, 9000 feet.

Screenshot F
Screenshot G
Screenshot H

From here you kind of know what to do so set "Otto" to hold you steady and look out the windows at Mt. St. Helens volcano!

Okay, enough sight-seeing…back to work. Tune NAV2 (if you have that) for Seattle at 116.80 and turn toward that arrow’s heading. In the panel shown I didn’t have a NAV2 so I set NAV1 for Seattle and flew north until I intercepted the 330 radial inbound (Screenshot I). I took that down to 30 miles DME. Then, I tuned the ADF to 224. Next, tune NAV1 to 111.70 and set your course (CRS) for 341. Now, one more thing…in your weather menu, set visibility down to only 5 miles! (Screenshot J)

Screenshot I
Screenshot J

ILS: Arriving into Sea-Tac:

Having talked about Standard Departures, we’ll talk about Instrument Approaches. Much like VORs, some runways have a radio beam that travels outward and upward from the end of the runway. Called an “Instrument Landing System”, an ILS directs planes to the end of the runway in any kind of weather. Now, with weather at only 5 miles, it’s time to put that to good use.

Drop down to 3500 feet and continue to follow that arrow toward the NDB. Somewhere about 26 miles out your main instrument (Called an H.S.I. by the way, for Horizontal Situation Indicator) will come to life. Mine looked like Screenshot K.

Screenshot K
Screenshot L

Here’s the deal with an ILS approach. The vertical “broken arrow” line indicates where the runway’s centerline is…right of us in this example. So first job is to get lined up on that sucker! Make a little right turn to get centered up. Next, look for that arrow or diamond or triangle along the right side of your H.S.I. That arrow is above you and tracks a line down to the end of the runway. As that arrow comes down to the middle, you need to slow up a bit and start downward. (Watch the progression in Screenshot L – can you see the runway in the last slide?) If you are coming down too fast you get too low and that arrow creeps back up…too shallow a descent and the arrow gets below you. Keep that thing centered! Small but quick corrections are helpful here! (In fact, now might be a good time to pause the sim and go back and read my ILS tutorial) This is TOUGH STUFF and takes a LOT of practice so hang with it. This is where real pilots make the big bucks! Good luck.

GPS Mode – FMC Programming – Autopilot Use: Seattle to Ketchikan:

Flying the plane by hand, dialing radio frequencies, turning here and there is all pretty tough to do…even harder to do smoothly. (That’s another reason why real pilots get the big bucks isn’t it?) On a good FMC pilots can enter in their waypoints as well as altitude and speed restrictions. They can program things to fly the shortest route, the fastest route, the most economical route, etc. The computers are pretty smart and can calculate fuel burn, time to arrival, what you’ll have for lunch and what order your bags will come off the carousel…well, not really ALL THAT but you get the idea. Since airlines are in the business of efficiency and passengers are interested in a smooth flight, without a lot of weaving to and fro, flying under the control of the FMC is the best way to ensure that everyone is “happy.” (I spoke with a pilot who flies regularly and he estimates that he’ll get 5 minutes of hands-on, in-the-air, time each flight. And the co-pilot gets about 20% of the flights so…) There are many great panels out there that incorporate some forms of FMC but that requires its own tutorial and I’m not the guy to write that. So for us more simple pilots there is the default flight planner! We can use this tool to sort of, in a lame fashion, mimic an FMC. I’ll show you how next:

Screenshot M
For this next part I switched into an Alaska Airlines 737 using the default panel. (Screenshot M) Go into your default flight planner and select Seattle, Washington (KSEA) as departure and Ketchikan, Alaska (PAKT) as your destination. Choose IFR and GPS-direct functions, then, FIND ROUTE. Next, you don’t want to just fly directly there as that’s hardly any fun, so while that route is up on the map view screen, move the view and drag the red route line over the following waypoints:

 The PA NDB (396)

 The YVR VOR (115.90)

 The YZT VOR (112.0)

 The PR NDB (218)

 The ANN VOR (117.1)

 The AKW NDB (229)

This will give you a 717.3-mile, very scenic, route into southern Alaska. Save the flight (“FMC.PLN” or something) and then load the flight.

Now, you should be in a 737 with the default panel, somewhere at Sea-Tac. For my example, I was parked up at the end of the runway, ready for a south departure. Look near the autopilot set-up for a little switch labeled NAV / GPS and click that over to GPS. That tells the instruments to follow the Computer-Programmed route (or FMC for our purposes). Before you start your takeoff roll you can set your altimeter and speed settings too if you’d like but DO NOT turn on any switches or the Flight Director yet (some say you can, some say you can’t…I’ve had mixed results so I leave mine off for now).

Another word of caution or disclaimer here – Flying in this fashion is really not FLYING at all! If this is the extent of your simming than you either do not have a yoke/stick to fly with or you may be a very, very sad person. For me…I have a real life outside of flight simming and if I choose to “fly” in the following manner it’s because I have to help with dinner or the house or the kids or the dog or run some other domestic errands. A real life should not keep you from simming and simming CERTAINLY should not keep you from living a full and eventful life outside of your computer box! (Enough soap-box I think!)

Screenshot N
Screenshot O

Throttle up, steer down the runway, rotate off smoothly, retract the gear and engage Otto. At this point I turn on AP/Master – ALT – SPD – NAV (this one flies the plane along the route you have programmed into the “FMC” – not really an FMC but for us beginners it works, okay?) and YD (that's five buttons lit up). Screenshot N shows the AP all fired up, the plane is flying itself now, and the H.S.I. shows the blue line pointing to my route – I’ve 8 miles to go. At this point you are welcomed to disconnect Otto and hand-fly the plane along the route pointed out by the blue line, that’s fun! (Screenshot O)

Screenshot P
Screenshot Q

If you are not hand-flying, you are free to go wash the dishes or vacuum out the wife’s car because your input is done. Many pilots fly this way because it’s so darn easy. Smooth for the passengers, yes, but not very much fun! The point here is that I want to show you that this default flight planner with NAV-GPS tracking can sort of act like a big old complicated FMC in that it can fly the plane for you, to exactly where you told it to go. Now, if weather changes or if ATC sends you off somewhere else or if you set the route to come in over some big mountain, our little default system will fly you right into that mountain so it’s by no means perfect – sort of a “poor man’s FMC.” However, if you set in the route I have described above, you will be nicely arranged (after turning over the AKW NDB) for the ILS into PAKT runway 11 (Screenshot P). All you have to do is set NAV1 to 109.30, set ADF to 396, switch the NAV / GPS back to NAV, turn HDG to 050 and engage that (HDG) button, and turn CRS to 110 degrees (Screenshot Q).

Screenshot R
So now, we’ve covered NDBs and VORs in Class 101. We’ve covered Standard Departures, ILS approaches and NAV-GPS tracking in this segment (Screenshot R). I hope that this provides enough of a basic introduction to get you all into the air safely. Good luck to you!

How To...FS Navigation 101: A Very Basic Introduction

How To...FS Navigation 101: A Very Basic Introduction

By Ron Blehm (30 August 2005)

Speak normally:

Let me start by saying that I am not a pilot. I don’t fly A320s, I don’t fly Cessnas and some days I’m just lucky to be flying my computer – but I think that sometimes it’s important for someone who is less “professional” to provide information for those who are newer or struggling with a certain concept. It’s always a bummer when the Neurologist is spouting off about the Globus Pallidus and the descending Cerebellar tracks when all you want to know is why Grandpa is falling down. Can’t they just speak normally? So here is my attempt to “speak normally” about some navigation concepts.

Get into the air:

First of all, you need to do some homework because I’m not going to teach you how to fly or how to land. This is not an ILS or autopilot tutorial because I already did that one:

FlightSim.Com has provided you MANY tutorials and “How To’s…” as well as other articles – I’m not going to give you a link to each of those because you can go back, even way back, and find a plethora of information yourself right here. (There is a reason FlightSim.Com is the world’s leading Flight Sim website, you just need to dig around a little bit).

There are also links like these out there on the web for easy picking:

And I’m sure that are MANY others.

Pick the right plane for the job:

Finally, you can use any aircraft that makes you feel comfortable but if you are new to the world of IFR or navigation I might suggest something stable and not too sporty (read as default Caravan?). I took the F.S Flight Club International Dash-8 (www.toomuchfs.com) on this tutorial. I also assigned a panel which maybe isn’t as real as it gets, but I thought it would be good for screenshots. (Although it’s lacking a NAV2 which is a bummer).

Class 1 - NDBs: Hailey to Boise:



Screenshot A
I thought the place to start might be with NDBs, “non-directional beacons.” These radio towers emit a signal on a certain frequency and if a pilot dials in that frequency on his ADF (Automatic Direction Finder) an arrow should point to where that radio tower is. The range on these is not great, maybe 50 miles or less? But you can fly headings to/from NDBs to get from one place to another. NDBs have also been really useful for me, in setting up for landings as there are sometimes NDBs on or near the approach path. NDBs do not give you distance measurements so you have to use a stopwatch to do distance calculations. (For me, anytime the word “calculation” is in a sentence I tend to stop listening).

Another great concept with NDBs is “Push the nose, Pull the tail.” This speaks of the arrow that displays on your panel. If you want to fly a heading of 330 degrees TOWARD the NDB, but your arrow is pointing at 300, you need to fly a heading of about 280 to PUSH the nose of the arrow TOWARD 330. Similarly, if you are flying AWAY from the NDB you need to PULL the tail of the arrow toward the heading you want to be on.

Set up your flight for northwest departure (runway 31) from Hailey, ID/Sun Valley airport (KSUN) and dial the ADF to 220. At this point I noticed that there is no arrow…but I’ll tell you, the NDB is behind you! (Okay, I did this just to be mean…you can depart on runway 13 instead if you’d like!) I went ahead and departed 31 and the arrow showed up at about 300 feet (See Screenshot A) then I turned back TOWARD the NDB. Whatever you do, fly TO THE NDB while climbing to 9,000 feet.

On the screenshot (above), near the top, you will see on the radio that I have dialed 220.0 into the ADF box. I’m flying a heading of 311 (climbing at 700 fpm) but the blue ADF arrow is pointing back. In the gauge on the left side you’ll see the double-sided white arrow pointing backwards to the NDB tower. That’s where I need to head! If you see Screenshot B you’ll see that I’m rolling out of my turn to a heading of about 130 which will push the nose of that NDB needle TOWARD 200 degrees. (You can also catch a glimpse of the airport on the far left.)



Screenshot B
    


Screenshot C

At the Hailey NDB turn to a heading of 201 degrees. Now you get to practice “pull the tail” to keep that arrow aligned on 201 / 021 headings. If you aren’t at 9,000 feet yet, keep climbing. Screenshot C shows that I have passed the NDB, the needle has swung around and I’m flying a heading of 208, trying to pull that tail over to 201. As noted, the DME (distance measuring equipment) is blank because NDBs don’t have that feature.

As you fly away from the Hailey NDB you’ll need to start looking for your next waypoint. Tune your ADF to 211. If you are not in range yet you may be left with nothing (or will have to retune to 220). Once the 211 NDB comes alive, drive towards that arrow. Again, we’ll fly toward the NDB until it swings around and then fly 269 degrees away from the NDB. (Basically you’ll be flying west with the needle pointing east – right?) Screenshot D shows me turning to 280 so I can pull the tail around to 269 (or thereabouts).



Screenshot D
    


Screenshot E

So now you are flying 269 degrees AWAY from the NDB 211. Set your ADF to 333 and follow THAT arrow. As it starts swinging you’ll turn right to 291 degrees. Screenshot E shows me flying AWAY from 333. Next dial up 238 on the ADF and start dropping to 4,000 feet or so. When you are at the 238 NDB, turn right to 075 degrees. Next dial up 359 on your ADF and as you cross over, fly a heading of 098 to KBOI runway 10L. (Screenshot F pretty much sums that up for you-NDB slightly right; turning slightly right; holding 4,000 feet; airport ahead) I happened to do a touch-and-go so that I could keep flying.



Screenshot F
    


Screenshot G

VORs: Boise to Pendleton:

VORs are VHF (very high frequency) radios, which send out 360 beams or “radials” on their signal. These are more accurate than NDBs because rather than pushing noses or pulling tails you can dial in a specific compass heading or radial to fly on. Also, VORs can have a range of more like 150 miles. So now we’ll dial in the Boise VOR, which is on a radio setting of 113.30. Dial this on your NAV1 radio and on the autopilot, set your CRS (course) heading to 343. What this means is that we WANT to fly away from Boise on the 343 degree compass radial. As you depart from runway 10L you’ll be heading basically east but your desired course is going to be northwest, which means you need to turn to the left. Screenshot H shows the start of my left turn, gear and flaps still going up!



Screenshot H
    


Screenshot I

If VORs are set up correctly you should have an arrow pointing to where you WANT to go, with a broken line in the middle showing where that radial is in relation to your position. Basically, if the broken line is left of center, you need to turn left to line that up. So now we set NAV1 to 116.2, keeping the CRS at 343 degrees for now. You can watch the DME (lower left of the main display) count down. Screenshot I shows this as I am flying a heading of 335 trying to center up that line. (Ignore the green arrow as NAV2 is off. We want to be flying 343 as shown next to the CRS readout.) Once it centers I can turn to 343. It may be off because I’m a lousy pilot or it may be off because a wind from the left is blowing me to the right of the radial. From the screenshot you can also see that I am, in effect, still pulling the tail of that old NDB TOWARD 343. When you are about 0.5 to 1 mile out, start turning to 326 degrees and then turn your course setting to match (326).



Screenshot J
    


Screenshot K

Once you are heading 326 degrees away from McCall, ID, repeat the process tuning 108.2 into NAV1 (screenshot J). When you get there, turn to 235 degrees (screenshot K). Then retune to 116.4. As you cross that VOR turn to 211 degrees. Retune again to 114.7 and drop to 3,500 feet. Screenshot L shows me heading into Pendleton, I’m flying a heading of 214 trying to keep that pink line in the middle.



Screenshot L
    


Screenshot M

Fly over the Pendleton VOR and continue on 211 for about another minute…then commence a right-hand turn. While you are turning set your CRS to 074 degrees. So, your goal here is to cross the VOR and



Screenshot N
head towards the AIRPORT on a heading of 074 degrees. Screenshot M shows that I am basically at the VOR – but I’m flying a heading of 094 trying to get over onto the 074 radial. You can see the airport and runway ahead.

Finally, Screenshot N shows that I am 2.5 miles past the VOR but I’m ON the 074 radial – short final to land.

This completes lesson one. You should now be able to use VORs or NDBs to navigate around the world a little more like a real pilot might. For practice, try limiting your visibility to about 5-10 miles…hop from one VOR to another and try to find the nearby airport. You can use this last leg as an example: Take off from Walla Walla, fly 211 degrees to the Pendleton VOR, make a big giant turn onto 074 and follow that to the runway. Next, fly something like 220 from Walla2 and just intercept the 074 inbound to Pendleton. Try these with only 2-3 miles visibility and see how that goes.

Stay tuned for “Navigation 102”.





Powered by ScribeFire.

How To...Runway Alignment

How To...Runway Alignment

By Steve Sokolowski (8 September 2005)

In the 1990s, I lived in a place called Waikoloa, a village located on the island of Hawaii. On those lazy days in paradise, flying a Piper Tomahawk with a buddy of mine was one of those experiences I'll not soon forget. Taking off from Kailua-Kona Airport in the early morning, with its sunlight glistening like the sparkle of diamonds upon the crystal aqua blue water of the Pacific; I reached my cruising altitude of 2000 feet. With ocean water below, majestic mountains, topped with a light sprinkle of newly fallen snow reminiscent of wipped cream covering the top of a childhood ice cream sundae, to my left. If this wasn't heaven, it was a close second. With only 5 hours of flying time under my belt, I left the black sand beaches of the Big Island for the state of Florida.

Leaving my friend and his Tomahawk behind, I longed for the days of strapping myself in the seat; releasing the parking brake and pushing that throttle to the firewall; waiting for that moment of freedom. Freedom from the bonds of earth called gravity.

I had it. I admit it. I had the flying bug, deep within me. And the only "fix" that would satisfy this strange addiction, was the purchase of Microsoft's Flight Simulator 2002. Nothing can compare to flying with the clouds, but Microsoft has come close.

The biggest problem I have with FS2002 is trying to visualize a three dimensional world, while being confined to the realm of a two dimensional computer monitor. While on "final" to Ocala Regional Airport (Florida - KOCF) it's hard to visualize the attitude in reference to the airport. To help with a VFR landing, I made use of the available ILS signal from Ocala. At a frequency of 111.5 MHz, both horizontal location and altitude above the airport is easily made available at a glance. But it stilled lacked "reality".

While surfing the Internet one day, I came across the "How To..." articles found on the FlightSim.Com web site. There was one of the many fine articles that caught my attention. It was titled:

"Stay Aligned With The Runway On Approach" by Bob Allison.



Figure 1
Bob came up with a novel yet simple modification that literally painted a small blue box on the computer monitor in the approximate location of the runway threshold. But when I tried the "trick", I found out pretty fast that the blue box was moving out of the range of the viewing window when descending 500 feet per minute to an airport. So why not convert the small blue box to a 4 inch long blue vertical line?

Take a look at Figure 1. Just by changing the box into a line, you can easily align your "172" for perfect landings without the use of the ILS. With just the use of the VOR (130.70 MHz for Ocala Regional), compass and the magical blue line, you can easily maneuver your aircraft until the runway threshold is located within the boundaries of the blue line (lets call it the "Alignment Bar").

Modifying the Panel.cfg File

To get the Alignment Bar to appear on screen, a small number of lines must be added to the panel configuration for the aircraft you wish to change. To add the Alignment Bar to the Cessna 172 for example, just locate:

C:Program Files/Microsoft Games/FS2002/aircraft/c172/panel/panel.cfg

using Windows Notepad editor. Just remember; it is a good idea to save the PANEL.CFG program to another file or hard drive BEFORE making any changes. Then, if any errors are made, the original .cfg file can be easily re-installed.

With Panel.cfg displayed on your Notepad editor; let's tell the computer that we will be adding another window to the program. Under [Window Titles] - add the following: window05=target (see below). The original configuration is colored in "brown" while the added material is in "blue".



// Panel Configuration file

// Cessna 172sp

// Copyright (c) 2001 Microsoft Corporation. All rights reserved.



[Window Titles]

Window00=Main Panel

Window01=Radio Stack

Window02=GPS

Window03=Annunciator

Window04=Compass

window05=target // <== Add this Line



[Window00]

file=panel_background_640.bmp

file_1024=panel_background_1024.bmp

size_mm=640

position=7

visible=1

no_luminous=1

ident=MAIN_PANEL

Now we must define the color, position and thickness of the Alignment Bar. To do this, just add the following 11 lines to the .cfg file as seen in Blue (below) after [Window04]:

[Window04]

file=172SP_compass.bmp

size_mm=70

position=2

visible=0

ident=COMPASS_PANEL

gauge00=Magnetic_Compass!Magnetic-Compass,0,0













Figure 2



//------------------------------------------------



[Window05]

// VERTICAL BLUE LINE

Background_color=41,200,253

size_mm=512

window_size_ratio=1.00

position=0

visible=0

ident=Target

window_size= 0.003, 0.407

window_pos= 0.505, 0.07 // Position left, Position Up-Down

// Increase this Number '.505' Line goes RIGHT Lower this number '0.07' - Line goes up



// ------------------------------------------------














Figure 3



[VCockpit01]

size_mm=512,512

pixel_size=512,512

texture=$C172s_1

background_color=0,0,0

visible=0



gauge00=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 0, 0, 205, 77

gauge01=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 206, 0, 205, 77

gauge02=Cessna172!Clock, 413, 1, 93, 93

gauge03=Bendix_King_Radio!Bendix-King Radio DME, 0, 86, 198, 51

gauge04=Bendix_King_Radio!Bendix-King Radio . . . . . . . . .



Figure 4
With the added lines complete, save the file to its original hard drive location:

C:Program Files/Microsoft Games/FS2002/aircraft/c172/panel/panel.cfg

It's now time to run Flight Simulator 2002 and take a look at our handiwork.

When loaded, select the Cessna C172SP and hit "Fly Now". With the 172 file running, you will be greeted with the usual Cessna Panel display and scenery window. To activate the Alignment Bar; hit the SHIFT-6 buttons. Magically the Blue Line will appear. To remove the Bar; just hit the SHIFT-6 buttons again.

Using The Alignment Bar



Figure 5
Let's say your flying at 2100 feet and you're at 30 degrees to the left of the centerline at the desired airport (Use the ILS if available). Turn on the Alignment Bar (See Figure 2). Notice the ILS indicates that you're over too far to the left and need to compensate. The idea is now to maneuver your Cessna so that the runway "centerline" is parallel to the Alignment Bar. Figure 3 indicates that you are on the glide path and that the Alignment Bar is parallel to the runway's centerline. Figure 4 is from a previous flight, note the Alignment Bar is centered with the runway. The ILS indicates proper positioning; although a bit low. I've also included the GPS in this photo. See how the GPS shows proper alignment with the runway.

Figure 5 shows your Cessna about .5 miles from the runway; the Alignment Bar is still centered with the runway. Continuing your final descent on this approach will guarantee you a successful landing time and time again.





Powered by ScribeFire.

Follow-Up And Clarification On ILS Tutorial

Follow-Up And Clarification On ILS Tutorial

By Ron Blehm (6 July 2004)

Since writing the original how to article I have received many e-mails, mainly from FS2004 users, about difficulties loading the situations or getting a screen-full of panel with no outside view. I whole-heartedly apologize for that. This was NOT some evil plot to force you to learn how to "Fly the Panel." More likely it is an issue of putting a situation saved in FS2002 into an FS2004 sim! Regardless, I know that it is a hard and frustrating thing to have a bunch of downloads that don't work or don't live up to your expectations. Frankly, I was afraid something like this might happen.

So, here is a very brief update or summary without any downloads. If you follow these step-by-step instructions the new iron sim pilot should be up and flying in no time at all! First, I would refer you to an old article by Geert Rolf; you really need to read this piece, it's important. To answer one e-mail I got, yes, I know it's from a couple of versions ago, it is "quite old" but I doubt the placard flaps and gear speed of the 737 have changed much in 6-7 years and the headings between Brussels and Paris certainly should be the same. As he stated, if you want to get flying, not necessarily "by the book" but quickly, his step-by-step directions will allow you to do that. Also, the point of my article was to build on Mr. Rolf's work and get you "flying" an ILS approach without just hitting the APP button and heading to your local Starbucks.

SET-UP:

1. Choose a plane you like. I picked this Tony Radmilovich-painted 735 from www.toomuchfs.com, "The Flight of the Month Club", seen here to the right.

2. Load the simulator and the plane of your choice. Select GO TO AIRPORT > EUROPE > MOLDOVA > CHISINAU (LUKK) > RUNWAY 8.

3. Once that loads you should be in your 737 (or other iron) idling at the end of Chisinau's runway 8. Be sure it's daylight, clear all weather and set fuel to maybe 50%. (I was in too big a hurry so still had real weather and full fuel). Select flaps 10-15 degrees.

4. Now, set HDG on your autopilot to 082. Set altitude to 3000 feet. Set IAS to 220. DO NOT turn autopilot on!

TAKE-OFF:

1. When you are ready, throttle up and release the brakes. Ground steering until you are ready to rotate, pull back gently on the yoke/stick until you are climbing. Once you have a good rate of climb, ENGAGE flight director, ENGAGE autothrottles, ENGAGE autopilot. Select HDG, ALT, IAS, Y/D. Double check your rate of climb to be sure it's not too high, maybe 1000 fpm or so? (Didn't Geert's article cover all this?)

2. Once your autopilot has settled in and taken control of your aircraft, retract gear and flaps fully, then set HDG to 178. As your plane banks, set ALT to maybe 20,000 feet or so. Once you are through your turn, set IAS to 240 and rate of climb to maybe 2000 fpm if you'd like.

CRUISE:

1. After 10,000 feet you can increase IAS to 320 or so.

2. Set your radios as follows:

  • NAV1 to the ILS 111.10
  • Set CRS to the runway heading of 175
  • NAV2 to the VOR 112.50
  • ADF to the NDB 396

I'm not sure what was going on, like I say, I was in a big hurry so I wasn't getting NAV2 or NDB but oh well. Oh, our destination is just over 350 miles away, Ataturk Airport in Istanbul Turkey. About 151 miles out from Istanbul I picked up the VOR (on NAV1) and saw that the radial was slightly to my right, I turned 5 degrees to 183 so I could intercept the 175 radial inbound.

GOING IN:

1. Somewhere around 50-60 miles DME I slowed IAS to 190 and set ALT to 5000 feet. Did you read the first part of my ILS Tutorial? My goal here is to have you use the autopilot all the way to the runway, just little mouse clicks, small corrections to get and stay lined up. Like we have said, this is to get the new pilot fired up and flying quickly, not necessarily "by the book."

2. Once you get the localizer and glideslope make little clicks of the mouse for HDG to line up with the runway. As the glideslope drops down you should set your ALT to -200 feet. (That's 200 feet BELOW sea level, not a typo) Then, adjust your rate of descent to keep that little arrow locked in. As stated, I accidentally had Real Weather loaded so had to play with my ROD a bit, dropping at 600-900 fpm. See picture, left.

FINAL:

Didn't I cover all this in the original piece? See, my fear was that if you couldn't load my situations or get a good outside view you'd figure you couldn't run the drill. My hope was that you'd at least take the information Mr. Rolf and I suggested to get into the air - and maybe even, safely back down again. I can't fly the thing for you! See picture, right - lined up!

1. Using little mouse clicks on the autopilot's HDG and ROD buttons to keep lined up you'll need to slow down, drop in flaps and gear at the appropriate times (See the "Quick Start Guide" for your speed and distance recommendations) and ride her in.

2. Somewhere under 200 feet AGL you'll need to GRADUALLY DECREASE your ROD to -100 fpm (or less). This eases your drop so you can land smoothly.

3. Somewhere under 100 feet AGL you'll need to DECREASE your IAS to 70-80 knots. To answer, again, an e-mail which stated that the iron jets don't handle well under 100 knots, "They might not even fly at speeds less then that." Since I cannot maintain 240 knots all the way to the gate, logic dictates that somewhere in the process I have to throttle back. Somewhere in the process of landing a plane does need to STOP FLYING. For me, this is that point!

4. Normally I don't like autobraking but since I had full fuel (and was a bit too nose-up) I selected "autobraking one".

5. You'll ease down until the wheels kiss the pavement, you'll need to hit the spoiler key and then DISCONNECT ALL AUTOPILOT FUNCTIONS! Start hitting reverse thrust and be ready to take over ground steering as soon as the nose wheel settles down.

6. Today, I was left of center and long, but got stopped by the mid-field turn-off. Not bad for a fully loaded, fully coupled, non-APP mode landing! (Picture, left.)

I hope that this little additional flight will help you all to get the kinks worked out, in whatever version of FS you use. Now, you can set up other flights in other weather in other planes - but you'll have to take some of that initiative on your own!

Happy landings to all.





Powered by ScribeFire.

How To Intercept, Capture And Fly An ILS Approach - A Progressive Tutorial

For The New "Heavy Iron" Pilot:

How To Intercept, Capture And Fly An ILS Approach - A Progressive Tutorial

By Ron Blehm (21 May 2004)

After successfully flying our Flight Of The Month from Salina Chan, "Queen of the Heavies" (www.toomuchfs.com) I decided that maybe some of you would benefit from a tutorial about capturing and flying an ILS approach - better late than never, right?

FlightSim.Com has featured writings on this topic in the past but you might find this approach a bit easier to get your head around. My goal here is to get you flying successfully, I'm not trying to make commercial pilots out of you and we are NOT necessarily following any documented or "proper" procedures - the hard core simmers can tune out now.

First of all some basics I used to get things going:

  1. You'll need to have a basic understanding of using VORs and NDBs to navigate the world. Try this link for some good help.
  2. You'll need to know how to set your radio stack to change frequencies.
  3. You'll need to know how to set and program your default (or otherwise) autopilot including NAV versus GPS settings, using HDG, CRS, speed and ALT hold, etc.
  4. You'll need to know how to use at least the default flight planner to get from point A to point B. (We are not covering that here).

If you are NOT up to speed on all this stuff you are really not ready to try this so you'll need to go do some study and check back with me later. You can also follow this link for some flight help that is a few years old but very, very good.

Situation 1:

Install the files from ILS1.ZIP into the following FS folder:

	Program Files > Microsoft Games > FS2002 or FS9 > Flights > Myflts

Then, fire up your sim, go to FILE > SELECT FLIGHT and choose ILS1. You will start out in a default 737 approaching London's Stansted airport. Everything should be configured to make a gradual intercept of the ILS. Some things to note while you cruise closer:

  • NAV1 is set to the ILS frequency (110.50).
  • CRS setting on H.S.I. and autopilot are aligned with the runway heading (it will pick up the track anywhere but it helps your situational awareness if you align it to the runway) which is 228 degrees.
  • The ADF radio is set to pick up a local NDB (429) but this, again, just helps your situational awareness and isn't as critical to THIS approach.
  • You should be holding 3500 feet.
  • I have not engaged the APProach hold setting on autopilot and my reasoning is, I think, important! Back in FS2K you could (basically) get close to your ILS, hit APP and the plane would fly itself right down onto the runway. Fun to watch but inconsistent and in FS2002 or FS2004 it is much harder (more realistic) to "capture" that ILS beam. Also, just hitting APP and going out for coffee isn't as challenging, it's less pilot-like, so we ain't going to do that!
  • You will need to confirm your flap settings and I have not lowered your landing gear!

So here's my plan for starting out: You are going to use your HDG, ALT and your IAS settings on the autopilot to control your plane all the way down to the runway. Simple mouse clicks for now, you won't even need your stick/yoke! Then, as you practice and get better you will be encouraged to TURN OFF YOUR AUTOPILOT at earlier and earlier stages of the approach. Soon you should be flying the last 30 miles by hand!

Back to the flight, if you can find the gauge that shows you your DME to the NAV1 you can watch for the needle on the H.S.I to start centering about 14 miles out (picture right). It is not uncommon for a 30 degree intercept angle which means as that needle starts in you need to make a 30 degree turn to match the runway heading. We'll get to that, but this time, more like 10 degrees. Anyway, as that needle centers you'll need to click the autopilot's HDG setting until you are aligned the same as the CRS setting (which you'll recall matched the runway heading of 228 degrees). If the needle is slightly left you'll need to lower the HDG setting one or two degrees. If the needle is slightly right you'll need to increase your HDG setting, just a couple mouse-clicks.

While you are here go ahead and drop your airspeed setting to 160 knots, make sure you have about 15-20 degrees of flaps.

Now, take note of the little arrow or diamond down the side of the H.S.I. (for me was about 11 miles DME) that starts dropping as your flight path crosses (from below) into your glideslope. When that little arrow gets to the middle, set your ALT setting on autopilot to 0000 (picture left). That's right, sea level or at least -200 below airport elevation to be safe. Airport elevation is 348 feet. Then you can adjust your rate of descent, vertical speed to match that little arrow. I usually start at about -700 fpm but that depends on your airspeed. If the arrow gets a notch or two ABOVE you need to decrease your rate of descent, maybe to -400 or 500 fpm. If it drops low (as it will) you'll need to increase rate of descent maybe even to -1000 fpm. Let's see, when I flew this my DME was now 7 miles. Drop IAS (still, you're only working on the autopilot, nothing else at this point) to 150, add more flaps too.

Okay, your mousing finger is warmed up, you should be 5-7 miles out and all lined up. All you need do now is use your right hand to click IAS (slower), HDG (up or down slightly) and VertSpeed (up or down slightly) to follow the arrows of the ILS. Use your left hand to progressively drop in flaps. I look for landing gear about 7 miles out, full flaps by 4-5 miles out, IAS to about 130-140 by 3-4 miles out. Now comes the hardest part, which is little more than faster mouse clicking (picture right). Make sure at this point that your NumLock key is OFF or your stick/yoke is handy for ground steering. As you get down to the last 500 feet or so above the ground you'll want to decrease your rate of descent and IAS (picture left). I cut IAS to 80-90 knots and try to get rate of descent to -100 fpm (if your autopilot lets you do 50 fpm that's great). This is your flare and as soon as the wheels hit you should pop up the spoilers and disconnect AP and start hitting F2 for reverse thrust. Now that autopilot is disconnected you'll need to use your stick or keypad for ground steering as noted above. It may take you a few runs at this to get your timing down but then again, timing is everything isn't it?

Situation 2:

Okay, lets make that a bit tougher. Load up ILS2.ZIP as you did above: This time you are a bit further out on approach to Mumbai, India. While all looks good now I'll tell you that under 4500 feet visibility is limited to 5 miles. Run the approach basically the same way, set IAS to 160, confirm HDG at 085 degrees and lower your ALT to 4000 feet. Add in your flaps and gear at the appropriate times; if you did this link you shouldn't need me to keep telling you this stuff, we're moving on! You will see that I dialed up an NDB (345) which is along your approach path as well as the airport's VOR (NAV2 = 116.60) so try to get your little ADF needle pointing the same way as your CRS or course setting on H.S.I. In other words, fly to the NDB first, then look for your ILS. If you turn to the NDB right away you'll have a sharper angle to intercept the ILS. If you wait until that ADF needle turns a bit and round your corner (picture right) it'll be easier. (See we only added one little component this time). As your ADF and ILS needles center up you'll need to adjust your HDG setting on autopilot to turn you into proper alignment (runway heading is 269 degrees, ILS frequency is 110.30). Again, as your glideslope arrow/diamond thing drops set your ALT to 0000 or lower, and adjust your VertSpeed as needed to keep centered. (I intercepted at 8 miles DME) Airport elevation is 27 feet. Visibility drops...you watch your alignments...(picture left) about 500 feet above ground you decrease rate of descent, about 200 feet you cut IAS to 90 knots, nose rises, speed drops, rate of descent -100 fpm...SQUEEK! You've done it again, congratulations.

One note here on missed approaches: Logically you'd like to have your AP all set to bail you out if you have to go "missed", HDG set, ALT about 5000 feet, IAS to 240 knots, etc. then if you abort landing you hit TOGO on your throttles, engage AP and once you are climbing you clean up. Well, you can't really do that with this technique so you either land the thing or if you MUST go missed you disconnect AP, firewall the throttles and pull back on the stick/yoke/trim. I figure anyone trying to learn to fly "irons" can make a plane climb so fly first and set the AP for go around later!

Situation 3:

Here's the next one, really no tougher than last time; some say easier, just longer (ILS3.ZIP). We'll say that you are piloting a 777 into Taipei, Taiwan. Airport elevation is 107 feet. This time you are well away from the airport but heading down out of your cruise. NAV1 is tracking the radial into a southern Taiwan VOR (115.20) and NAV2 is set to the airport (114.30). Your NAV2 needle should point the way home. Go ahead and turn your HDG early if you like, then fly the 045 degrees radial outbound for 100-110 miles while you descend into the clouds (picture right). At about 100 miles DME from MKR adjust your radio NAV1 frequency to the ILS which is 111.10 and set CRS to runway 5L, which is 052 degrees. See that, only a 7 degree turn to final--easy!

Obviously you can't see a lot out there as I've added some cloud layers and turbulence to your Far East arrival. You'll want to be about 5000 feet by 15-20 miles out, the H.S.I. will tell you if the runway is to your left or right so adjust HDG to turn into it, catch the glideslope arrow and set ALT to -200 adjusting VertSpeed as needed to stay centered. This time, with the wind, rain and turbulence you'll need to constantly play with your HDG and VertSpeed, you may also want to keep IAS a bit higher as you don't want a big gust of wind to stall you out - speaking of faster, a notch or two less flap might help with that but there's also autobraking if you'd like to dial that in (I don't). Don't worry, I'll let you catch a glimpse of the airport before the ground but at this point you shouldn't need that, just fly your panel! (picture left).

Situation 4:

Okay, load up ILS4.ZIP as before. You're getting the hang of this now! One more default plane, the 747, but the same principles! You're approaching Victoria, BC on your way into a rainy Seattle, WA (typical huh?) This time I've added a couple of steps for you to work through: You are tracking NAV1 into the 088 degree radial for the VOR at 113.70, but also notice that the ADF is pointing to an NDB up ahead (240) and NAV2 is set for Paine, which is 110.60.

Cross Victoria at about 21,000 feet and while you fly 088 degrees drop to 14,000 feet before the NDB. From the Skagit NDB turn right to HDG 150 now tracking NAV2 into Paine. On the radio stack set NAV1 for the ILS 110.30 with CRS moved from 088 degrees to 161 degrees (picture right). Drop to 7000 feet and slow down!

Once your ILS beam on the H.S.I. comes alive you can set your NAV2 radio to Seattle's VOR at 116.80. Watch your DME reading, progressively slowing and dropping in your flaps until you can intercept that ILS beam and glideslope. I think I was about 4800 feet when that thing centered up. This time, since we started further out, you may be left or right of the beam so HDG may need to go either way to intercept that sucker. Airport elevation is 429 feet. I look for speed on short final around 150 dropping to 100 knots after 400 feet or so. Again, you may need to run this situation several times to get smooth. You'll also notice that I've added in some wind. This technique works less well with more wind, but you can still deal with a bit of slip/wind correction with this method. (picture left) I flew this situation twice to confirm my settings and had smooth landings, spot on, both times with my HDG about 163-165 degrees.

Situation 5:

Moving on, next up is ILS5.ZIP. This time you are into the Learjet 45 in Valencia, Venezuela. As you can see, the GPS window is open now but this is ONLY to show you that I have set in a flight plan. You will set the NAV / GPS switch on your autopilot to GPS, add one notch of flaps, release brakes and away you go! Once you have a positive rate of climb engage the ALT setting on AP (14,000 feet), engage A/T and IAS to 220 knots, and select CRS. This should fly you along the prescribed route (picture right).

While you are flying I want you to set your radios as follows: ADF to 267, NAV1 to 110.10, NAV2 to 114.90. Now you are set for an ILS into Maracaibo, and here is how that will shake out:

Even though your AP is tracking your GPS route or flight plan, your NAV2 / VOR radio will pick up the VOR at 114.90 (set your DME to follow it in - that's DME2). As you near the VOR (like 10 miles or so) set your HDG on AP to match your ACTUAL, current heading. Click HDG on and CRS off. Then switch that NAV / GPS lever back to NAV. Now set CRS for 026 degrees, that's the runway heading! Drop IAS to 160 knots and decrease ALT to 3700 feet. After you cross the VOR turn HDG to -12 degrees and set NAV2 for the airport, which is 115.70. Elevation is 235 feet, by the way. Now it's the same old drill, watch the needle center up, adjust HDG to turn towards the runway, slowing down and adding flaps at the appropriate times...small clicks left or right, up or down to follow the needles into a smooth and safe landing.

Situation 6:

ILS6.ZIP puts you in a Learjet 45 headed into the offset ILS at Tivat, Bosnia. Now, offsets are a bit of a different story because you can't always time the turn well by using the HDG setting and turning changes your rate of decent too. So you use this technique to the Missed Approach Point, then you disconnect HDG and ALT and fly it yourself. If you'd like to keep A/P in control of speed you are welcomed to do that but once I stop clicking and start flying, I fly the whole thing! So, cross the NDB (345) at 3300 feet. Track the ILS heading 337 degrees dropping slowly to 1800 feet by 3 miles DME. The runway is to your left, 11 o'clock on a heading of about 320 degrees (that's a 17 degree turn on short final!) Airport Elevation is 25 feet. Good luck (picture left)!

Situation 7:

"Man, how many more can this guy come up with?" Well, this is truly the last one (ILS7.ZIP). We're back into the 737, climbing out of Arequipa in southern Peru this time. Set cruise for about 27,000 feet. We're looking at a short flight into Julianca, Peru. Why there? Well because one, the airport is at more than 12,500 feet ASL so you'll have to deal with some density altitude problems here and two, because there's no ILS at the airport. So how does this make it into an ILS tutorial? Well, this is a "new heavy iron" tutorial and not every airport will have an ILS.

So, turn NAV1 and NAV2 to 115.50 and adjust your heading to fly towards that little arrow. When you are about 12-15 miles DME from the airport turn HDG to 115 degrees, slow IAS a bit and reset ALT to 20,000 feet. Add in some flaps as you go but fly this heading maybe 20 or more miles AWAY from the airport before turning left to 320 degrees or so. Set CRS for 290 degrees which will have you flying kind of toward the runway 11/29. (320 minus 290 equals your 30 degree intercept!) (picture right) Hold 20,000 feet until exactly 15 miles DME and then set your ALT to 10,000 feet (or so). If your speed is 180 set rate of descent to 1900 fpm. If your speed is 160 set rate of descent to 1700 fpm. If your speed is 140 set rate of descent to 1500 fpm. I came in a bit too fast and with full flaps, starting at 160 and slowing to 140 should do you just fine, even at 12,500 feet - the runway is just a notch under 14,000 feet long so you don't have to put down on the stripes!

Now here's the tricky part: The VOR may not be in the middle of the threshold so your descent profile or your heading may need to be adjusted as the runway comes into view (unless you wanted to land ON the VOR station?) Like I say, I was coming in a bit too fast and had to really dump my airspeed and altitude the last 5 miles but still, just mouse clicks on the autopilot and I landed safely. (Although a picture will show my spoilers up early to help bleed off the speed!) (picture left)

Now, some will may work through this and be so excited to be flying those big jets that they never graduate beyond using the autopilot and while that's okay (I guess) it really isn't "flying" and this is a "Flight Simulator" not a mouse-clicking game so...learn to turn that sucker off, first at 3 miles out, then 5 then 10, 15, 30 or a hundred miles out, then you'll be FLYING the heavies just like the big boys! (I flew Situation 3 again with no autopilot just to prove my point. While my descent profile wasn't as smooth down to 5000 feet and I landed a bit long, my landing was actually a bit better when flying by hand because I could cross-control the rudder/ailerons a bit.)

So, get to working on this and then, let me know how you do with becoming an "iron sim pilot."





Powered by ScribeFire.