Jump to content


* * * * * 1 votes

Landing Tutorial


  • Please log in to reply
35 replies to this topic

#21 .Ben

.Ben

    formerly Ben.

  • Members/Edit
  • PipPipPipPipPipPip
  • 3,564 posts
  • Location:Leamington Spa

Posted 12 September 2006 - 11:00 AM

No, it should be put in the Knowledge Base - but perhaps edited slightly. (Cropped images, spelling and gramatic errors etc)

--Ben.

#22 Flightsimulatorpilot

Flightsimulatorpilot

    Airline Transport Pilot

  • Members
  • PipPipPipPipPipPip
  • 4,028 posts

Posted 12 September 2006 - 06:11 PM

Thanks for the comments everyone! Yea, I was going a little fast :lol:

The edit button is gone, but I would have fixed the images, errors, etc.
Anyway, I hope it helped some of you! :D

#23 Adam.

Adam.

    Airline Transport Pilot

  • Members
  • PipPipPipPipPipPip
  • 2,870 posts
  • Location:Newcastle england

Posted 13 December 2006 - 11:31 AM

VERY GOOD tutorial, i've been posting on the main forums for a long time asking how to come inline with the runway,   this helps loads!! thx

#24 novice46

novice46

    Passenger

  • New Members
  • Pip
  • 6 posts
  • Location:uk

Posted 21 April 2009 - 12:28 PM

Thanks that is a great help! I didn't know where the localiser or glidescope was or how or where to find them so now it makes a lot more sence and maybe I can finally stop landing short of the runway or on houses, just need to know what the heck the vectors are now lol.

#25 Arm Out The Heli

Arm Out The Heli

    Private Pilot - VFR

  • Members
  • PipPipPip
  • 338 posts
  • Location:North of the South

Posted 21 April 2009 - 12:37 PM

If the localiser needle is on the right, you fly between the needle and mark pin (to the right), not to the left.

Would be good in the KB if it was correct!

#26 JordanFarmer

JordanFarmer

    Commercial Pilot

  • Members
  • PipPipPipPipPip
  • 1,250 posts
  • Location:Near EGTE

Posted 21 April 2009 - 04:32 PM

Good tut, very old though :hrmm: but yeah, Vectors are the directions that air traffic control give you which brings you into the runway. E.G. 'N256VU, turn right heading 160' that is a vector, as long as you are going toward the runway, i think :hrmm: lol

#27 -Dexter

-Dexter

    Supersonic

  • Members
  • PipPipPipPipPipPipPipPip
  • 20,183 posts
  • Location:West Virginia, USA

Posted 23 April 2009 - 05:53 AM

Christ, guys, this is from 2006. :hrmm:

#28 Peter797

Peter797

    Orville Reincarnate

  • Members
  • PipPipPipPipPipPipPip
  • 7,145 posts
  • Location:CYYZ

Posted 27 May 2009 - 09:09 PM

Tutorial still works no?

#29 hendryrusli

hendryrusli

    Student Pilot

  • Members
  • PipPip
  • 72 posts
  • Location:Bandung (WICC)

Posted 07 July 2009 - 01:56 PM

This is a good tutorial. Thanks for posting. Time to brush up my landing skills when I got my Saitek X52 Pro joystick.

#30 Alaska_MD-83

Alaska_MD-83

    Orville Reincarnate

  • Members
  • PipPipPipPipPipPipPip
  • 5,971 posts
  • Location:Los Angeles Ca.

Posted 14 July 2009 - 01:08 AM

View PostFlightsimulatorpilot, on May 29 2006, 09:54 PM, said:

Hi everybody, I made a tutorial on landing. I tought this would help a lot of people that are new to sim and/or are having trouble landing. So, enjoy!  :hrmm:


------------------------------------------------------------------------------------------------
LANDING TUTORIAL:
For this tutorial I am using the default 737 panel, but it's the same for any default panel. I recommed downloading the altitude call-outs from Avsim.com, as it makes the approach easier.


Before we start, I want to explain the different approaches. There are two different approahces: ILS and Visual Approach. ILS is when you enter the frequency into NAV1 and use the markings on the altitude indicator. Visual approach is when you use the PAPI lights to do the approach. Both are basically the same and in this tutorial I will explain both of them.

What about VOR, NDB, Localiser Directional Aid, Localiser, Localiser Back Course, RNAV and GPS approaches?


OK, so let's start! We will be landing on Runway 09R at London Heathrow Airport (EGLL, LHR). First of all, let's find the frequency for Heathrow's 09R. While flying in the sim (on approach to the airport, after getting the landing runway form ATC), press the "alt" key on your keyboard. When you press the tab key, you'll see  a tab at the top of the screen with different sections. Go to world and then click on map. You'll see your plane on the map and your destination airport close by, so zoom in all they way on your destination airport (in this case LHR) and double click on your assigned runway (in this case 09R). Once you do that, you'll see this: The frequency for our runway is 109.50, so click cancel at the bottom of the page to return back to the sim.

Now, open up the radio stack subpanel. You can do this by pressing SHIFT + 2, or by clicking the little "A" symbol on the panel. Go down to the NAV 1 frequency windows (Third two windows from the top). There should be two windows, one on the left and one on the right. The one on the left is the active frequency and the one on the right is the standby frequecny window. Go to the standby frequency selector window (the one on the left) and enter in the frequency (109.50 in my example). Than click the little arrow between the two windows, and the frequency that you just entered should be moved to the left window and the frequecy that was already in the left windown should be moved to the right window. This is only if the ATC instructed you to an ILS approach, if you were given a visual approach, skip this step.

If you were given a visual approach, the ATC will line you up with the runway. But, if you were given an ILS approach, the ATC will give you a heading that's -/+ 30 degrees from your runway heading. For example, our runway heading is 93, so the ATC will give us a heading between 63 and 93 degrees or 93 and 123 degrees. Continue on this heading untill the localizer needle starts to move. If you don't know which needle is the localizer needle, then scroll to to bottom of this post. The ATC should also give you a altitude at which to intercept the glideslope. How do you know what this alltitude is? Well, the ATC will say "maintain x,xxx utill established on the localizer". That is the altitude you should hold untill glideslope intercept.

So, once the localizer needle starts to move, turn toward the runway to line up with it. You should estimate how much to turn, it might be hard at the begining, but it'll be a peace of cake after a couple of approaches. You will know that you're lined up when the localizer needle is in the middle of the altitude indicator (again, scroll to the bottom to see examples). Again, if you're doing a visual approach, skip all of the above.

Alright, so now that you're heading toward the runway at the altitude the ATC told you to hold. Now you'll see the glideslope needle start to move, so you should start the descent. Once the Glideslope needle starts to move, start your descent. Descent at a rate of about 100 foot per minute, and slowly increase your descent. If you follow this, you should be descending at about 500fpm when the GS needle is at center of the altitude indicator. 500fpm is the descent for most runways. You want to keep both the localizer and the glideslope needles in the center of the altitude indicator. Also, use the PAPI lights outside the runway fro reference.  
PAPI (Precision Approach Path Indicator) are 4 lights to the side of the runway. They tell you if you're on GS or not.

It's generally accpeted that when you are one dot below the glideslope you should extend your landing gear. When the aircraft has intercepted the glideslope add your last notch of flaps and set your target power setting for the approach and the plane should start down by iteslf with minimal control inputs.

Descent rates vary for your approach speed. To say 500 FPM decent rate is your target is innacurate.

PAPI lights more often than not don't correspond to the glideslope and should only be used once you abandon the instrument approach and are going visual. Instrument indications may show on glideslope while the PAPI shows you are not on glideslope.


Here's what the lights mean:

All reds = too low
3 reds + 1 white = too low
2 reds + 2 whites = on G/S
1 red +3 whites = too high
all whites = too high

You should keep 2 reds + 2 whites on approach. Follow the G/S and Localizer needles and the PAPI lights throught out your approach. Once near touchdown (200 feet above the ground) follow the PAPI lights more than the needles. At 50 feet above groud, reduce throttle to idle, and at 30 feet, pull the nose up to about 6 degrees. Once you touchdown, apply reverse thurst (if need/allowed) and stay on the centerline by applying rudder if needed.  

Now, if you were given a visual approach, hold the assinged altitude untill the PAPI lights are 2 reds + 2 whites, once that is accomplished, start descending at about 500fpm and follow the PAPI lights untill touchdown (keep 2 reds + 2 whites). ATC will basically line you up with the runway you should do some corrections (as needed) to stay on centerline while on approach. You should estimate if you're on the centerline or not, but here's a good tip: When you're ready to takeoff and line up with the runway, memorize where the centerline is on your panel and you should keep the center line in that place while on approach. The rest is the same as an ILS approach (see above).

This is also not always the case. The PAPI displays 2 glidepaths. Being on the lower glidepath is indicated  by 2 reds over 2 whites and is used by smaller aircraft. Larger aircraft use the upper glideslope which is indicated by 3 white lights and 1 red light when on the upper glidepath.


Here are couple of images to help you out:
Glideslope/Localizer Needles:
Posted Image

To the RIGHT of the localizer, you should turn right to correct:
Posted Image

To the LEFT of the localizer, you should turn left:
Posted Image

Above Glideslope (too high), you should descend to correct:
Posted Image

Below Glideslope (too low), you should climb to correct:
Posted Image

On localizer:
Posted Image

On Glideslope:
Posted Image


Notes:
PAPI lights are not the only type of lights that airports use. There are other type of approach lights such as VASI, etc. I used PAPI because most airports use them,
but you can find tutorials on how to read other type of approach lights on the
internet/aviation sites.

You DO NOT have to enter a frequency in NAV2 windows.

500fpm might not be suitable for a runway you're approaching. You should increase your fpm untill you find one that's suitable. Agian, I used 500 fpm because most Glideslopes use this.

As previously corrected it depends on your approach speed. Jeppesen approach plates will give you the FPM required to maintain the glideslope for your approach speed.

ALWAYS trim your aircraft to keep the descent you want during the approach, it makes the approach much more easier.

Proper speed is also important, so watch your speed.


Words Used:
GS = Glideslope
FPM = Foot per Minute (descent)
PAPI = Precision Approach Path Indicator


Please do not upload this tutorial to any other sites without my permision, contact me first. Thank you.
------------------------------------------------------------------------------------------------

Thanks for reading everybody, hope this helps some poeple. Comments are welcome! :hrmm:
Edit: Sorry about the size of the screenshots, forgot to resize. If you have any questions, feel free to ask me.

Edited by JET PILOT, 14 July 2009 - 01:10 AM.


#31 fred1935

fred1935

    Student Pilot

  • Members
  • PipPip
  • 25 posts
  • Location:Yorkshire UK

Posted 04 January 2010 - 05:40 PM

I am very new to FS2004 and flying of any kind, this tutorial has explained many things to me.  Maybe I can stop landing like a drunken butterfly, in time, or even land at all.   :hrmm:

Thank you.

#32 fredrick_thy_grt

fredrick_thy_grt

    Private Pilot - IFR

  • Members
  • PipPipPipPip
  • 819 posts

Posted 04 January 2010 - 07:46 PM

Seems like you wrote this as a general tut, and your using European procedures, and that is perfectly fine. Great tutorial, but a good habit is to track the localizer on a visual ATC (in America anyway) will not always line you up with the runway so its a good idea to verify your on the right runway. I know Frontier Airlines and SkyWest Airlines require pilots to track the glideslope and localizer even when on a visual approach.  

Great job. :hrmm:

Edited by flynryan692, 04 January 2010 - 07:47 PM.


#33 THBatMan8

THBatMan8

    Cruising at FL110

  • Members
  • PipPipPipPipPipPipPipPip
  • 11,562 posts

Posted 04 January 2010 - 08:32 PM

View Postflynryan692, on Jan 4 2010, 07:46 PM, said:

I know Frontier Airlines and SkyWest Airlines require pilots to track the glideslope and localizer even when on a visual approach.

You're probably thinking of what's called a CDAP (Constant Descent Approach Procedure). CDAP's can only be flown if there is a published FAF (Final Approach Fix) and coupled DME, and you're not really tracking a G/S with a CDAP. You take your GS, divide it by 2 and multiply it by 10 to come up with your descent rate from the FAF (or you could multiply your GS by 5). The LOC/GS reference just serves as a backup to the primary navaid. Certain aircraft, like the 747-400 and most Airbuses, will automatically tune the runways ILS frequency and front course when you select a runway (if equipped) in the FMC, and you can't park the ILS.

Edited by THBatMan8, 04 January 2010 - 08:43 PM.


#34 Fate01_VUSAFS

Fate01_VUSAFS

    Airline Transport Pilot

  • Members
  • PipPipPipPipPipPip
  • 3,316 posts
  • Location:Cleveland, Ohio, USA

Posted 06 January 2010 - 01:16 AM

Just a suggestion to anyone who wants to learn how to fly instrument approaches...

Don't follow this tutorial to the bone, and don't try to learn instrument in an airliner. It's too fast for you to be able to correct your mistakes if you make any. Start off in the 172 or something small that you can handle and practice following in the glide slope without even using your OBS/VOR Indicators. First, learn how to fly in the visual approach just to get you to feel the general landing for that aircraft. Then, track in the glide slope via the indicator lights. After that, then can start practicing using the ILS frequencies to track the exact glide path to the runway. Most FS pilots cannot figure out the FMC and stick with the basic GPS/radio stack features. This is fine, but just make sure you put in the correct ILS frequency for the runway you are approaching, and the proper direction on your OBS. Make sure you set the ILS heading or runway approach heading, not the runway direction. If you're approaching runway 24, check to see whether the ILS heading is 240 or another approach heading such as 237. I could go on and on, but then I might as well create my own tutorial, if there isn't already one in here.

This tutorial is nice and all for someone who generally knows how to fly an ILS and wants to learn in an aircraft with a PFD and Flight Director in the HSI, but if you know nothing about ILS, I think it's a bad idea to step right up and follow this guide, as you're going to find yourself majorly confused and mislead by some areas of the article.

#35 hendryrusli

hendryrusli

    Student Pilot

  • Members
  • PipPip
  • 72 posts
  • Location:Bandung (WICC)

Posted 11 February 2010 - 10:18 PM

This is very helpful tutorial. Thank you!

#36 pyruvate

pyruvate

    Orville Reincarnate

  • Members
  • PipPipPipPipPipPipPip
  • 9,126 posts
  • Location:Here be maple leaves

Posted 12 February 2010 - 09:56 AM

Oh the days, I remember when after I read this tutorial I started landing properly :hrmm:

Now PMDG + FMC = Win :hrmm: