Search the Community
Showing results for tags 'innsbruck'.
Found 11 results
-
/images/notams/notams22/inns0406.jpgInnsbruck Airport (IATA: INN, ICAO: LOWI), also known asKranebitten Airport, is the largest international airport in Tyrol inwestern Austria. It is located approximately 2.5 miles from the centreof Innsbruck. The airport, which was opened in 1925, handlesregional flights around the Alps, as well as seasonal internationaltraffic to further European destinations. During the winter, activityincreases significantly, due to the high number of skiers travellingto the region. Innsbruck Airport is well known for having a difficult approach dueto surrounding terrain, prohibiting certain aircraft types fromoperating at the airport. The approach and descent is a verycomplicated process-the Alps create vicious winds and currents, whichthe pilot has to deal with throughout the process. Because there aremountains all around, the plane usually circles the airport, enters apattern, to decrease both speed and altitude. Source
-
/images/notams/notams22/inns0404/inns0404.jpgMSFS Snowy Runways is a mod to allow airports located in snowy regions tobe visible when snow is activated in MSFS 2020. It works with Live Weather orwith Custom weather settings in the MSFS weather panel. No extra app orprogram download required. The mod is intended to be used in snowy winterconditions only. It is a snowy mod for those who like to fly to snowy winterairports and actually see the runways after snow clearance to allowflights. The mod is customised for each airport included in the package. /images/notams/notams22/inns0404/snowy-runways-1.jpg /images/notams/notams22/inns0404/snowy-runways-2.jpg /images/notams/notams22/inns0404/snowy-runways-3.jpgPurchase Taburet - Snowy Runways Innsbruck/Courchevel For MSFS See other Taburet scenery for MSFS 2020
-
-
Flying with MB-339 in Innsbruck. Aircraft by IndiaFoxtEcho. https://www.youtube.com/watch?v=FjlNpb09LV8
-
So had to cut this one down and play some music as it was a really bad takeoff and a hard, bouncy landing at Innsbruck (LOWI). -
/images/notams/notams19/orbx0807.jpgA destination that needs no introduction, Innsbruck is one of theiconic airports of the world, with a jaw-dropping backdrop,heart-stopping approaches and location smack dab in the heart ofEurope. Our award-winning depiction of this famous location has nowbeen brought to life for X-Plane 11. Within the scenery's extraordinary coverage area (a mini-region inTrueEarth style), explore the peaks and glaciers of the Austrian Alps,the picturesque Inn, Wipp and Stubai Valleys, the historic BrennerPass and a sizable chunk of the German state of Bavaria. Dozens oftowns and villages dot the Tyrolian and Bavarian landscape, and ofcourse the city of Innsbruck has been created in immaculate detailwith over 160 landmarks. As well as all these features are threehigh-detail heliports; Hat Tux/Alpin 5 (LOJT), located deep in thehidden valleys of the Tirol, the Unversity Hospital (Uni Klinik)rooftop pad in the heart of the city, and the A-AMTC Flight RescueCentre, adjacent to the airport. Innsbruck Airport itself is the country's third largest and is atrue multi-purpose field; where else will you see busy airlineschedules competing for space alongside corporate hi-flyers, rescueand leisure helicopter crew, general aviation flyers, recreationalglider pilots and even frequent Red Bull visitors? Brought to life inimmaculate detail, comb over beautiful modelling and texture work,ultra-HD ground textures, and dozens of aircraft and GSE types createdexclusively for this location. FeaturesHD Airport, CityScene and Mini-Region all in oneUltra-detailed rendition of LOWIComplete CityScene for InnsbruckEnormous 8200km2 mini-regionThree major heliportsBeautiful hand-corrected and coloured PR at 30cm/60cm/1mOver 160 custom POIStunning custom vegetation and building autogenMajor bridges, freeway overpasses created as unique modelsCompletely customized GSE and static aircraft fleet unique to LOWIBeautiful night lightingAnimated GSEUltra-HD mesh sampled from 10m DEM sourceComplete TrueEarth style coverage for entire tileExpertly optimized for best possible performanceOriginal version by Jarrad Marshall, brought to XP11 with the help of Vittorio Greco and Tony WroblewskiPurchase LOWI - Innsbruck for X-Plane
-
/images/notams/notams19/inns0725.jpgOne of our most iconic airports is making the leap to X-Plane byLaminar Research. An airport that needs no introduction, Innsbruck isone of the world's greatest destinations. Dramatic alpine scenery,beautiful architecture, and one of the most hair-raising approaches inthe aviation world, this airport is absolutely enchanting. We have also included an entire cityscape (including 160 points ofinterest), three heliports and an 8000 km2 TrueEarth stylemini-region. This is a project we have been excited about for a longtime; check out all the features and screen shots over at ourforums! Source
-
Vienna - Innsbruck (And Return) Flight Review By Cedric De Keyser Ready to taxi I've recently made this short flight over Austria and decided to share this virtual experience with other civil aviation and flight simulation enthusiasts - this is the first time I'm doing so. I live in Belgium and so usually "fly" from/to Belgian airports (mainly Brussels-National) or neighbouring hubs (Amsterdam, Frankfurt, London, Paris) on short, medium or intercontinental commercial flights simulations. A domestic flight in a foreign country is relatively rare, that's what makes the first exception for this one. Another fact is that I always try to fly as realistically as possible, which means respecting the route, airline, aircraft type and schedule if possible. The flight we are talking about here was, according to Austrian Airlines' timetable, OS5901 VIE-INN (there are several flights a day), which is actually operated by Tyrolean Airways (VO), using the turboprop aircraft Dash 8-300/400 or the jet aircraft Fokker 70. Taxiing out (First Officer's view) - "Cabin crew, take your seats!" I made this flight with a Douglas MD-87 of Austrian Airlines (here comes the second exception), a relatively old and noisy aircraft whose days in scheduled operations are unfortunately numbered. This is the type of aircraft that the company has used on its Vienna-Brussels service until recently and which is now being operated by CRJ, Fokker 70 of Airbus A320 depending the time of the day. Innsbruck's 6562 feet (2000 m) runway is long enough to accomodate the aircraft and I thought that bigger types and wide bodies were never to been seen there but I was wrong: I've found a real picture showing a Boeing 767 of Lauda (Austria's leisure airline) visiting the airport. Situated in a valley in Tyrol, in the heart of the Austrian Alps, this 1900 foot (570 m) high airport is well known for its particular and dangerous approach, one of the most challenging approaches in Europe. Ready for take off - note the flight plan path in the Nav Display CRT gauge The navigation tool used for the flight was NavDash 2.5. The flight plan was encoded in the flight management computer following the information found on E(LO) 9 Jeppesen Low Altitude enroute chart and routed via VALIK intersection, Linz VOR (LNZ), Salzburg VOR (SBG) and then directly towards Rattenberg NDB (RTT), entry point for an eastern approach of Innsbruck. The progress screen of the FMC showed that a distance of 227 nautical miles (420 km) was to be covered. A cruise altitude of 15000 feet (4500 m) was chosen as well as a cruise speed (ground speed) of 320 knots (590 km/h). The fuel tanks were not fully filled up (40%) for this short flight, allowing a shorter take off run. I turned the seatbelts and no smoking signs on before an imaginary welcome message to the passengers. At 17:10 local time (16:10 UTC) the engines were started. Take off The aircraft was parked at a remote stand at Vienna - Schwechat International (LOWW) and no pushback was required. I gently gave a thrust of 60% N1, followed by the typical rating rise sound of the Pratt & Whitney JT8D turbojets and the 53000 kg (this is the take off weight considerating the amount of fuel loaded and that 90% of the seats were occupied) heavy aircraft began to roll. Once reached the taxiing speed of 15 kts (28 km/h) the throttle lever was brought back to a lower position. Flaps were set to 11 degrees and after a short taxi to runway 29 the aircraft (which was number one as no traffic was generated on this airport) lined up for an immediate take off. Cruise The throttle was brought to 80% N1, and as the engines were correctly responding, full power was given to make this baby fly. At 150 kts (278 km/h) the aircraft rotated and at 160 kts (296 km/h) flight OS5901 was airborne. With a positive rate of climb, the gear was set to 'up' and once reached the altitude of 2000 feet I pushed the LNAV button of the FMC ; the autopilot, which had previously been engaged, made the aircraft directly head to the first waypoint of the flight plan with a slight left turn (I didn't fly the SID - standard instrument departure - as I don't own these charts for LOWW). Starting descent As the speed was increasing, flaps were retracted and power reduced (by the way, I've heard that if full power - take off rate - is set to an aircraft engine lasting 5 minutes, the high technology jewel will be irreversibly damaged as the turbine components will melt due to too long high temperature exposure, even if they are engineered to work at temperatures exceeding their melting point in modern turbofan engines; but that's another story). After some little turbulence undergone in the stratus clouds above Vienna the cruise altitude of 15000 feet (FL150) was quickly reached (passing 10000 feet the seatbelts sign was as usual turned off). Auto thrust was engaged to maintain a cruise speed of 320 kts - as the plane was then entirely controlled by the autopilot, I could contemplate the immaculate sea of clouds I was flying over with, on the left and later forward, the peaks of the Alps emerging. Kai Tak International The sun was slowly going down but I didn't have much time to gaze at the sunset as I had to attend to the descent and approach of our destination. As you've understood, in a way to make things a little more exciting, I set some relatively bad weather at Innsbruck, an overcast sky with cloud base of 4550 feet and summits at 5300 feet, but with good visibility and winds calm. At about 20 nm before Rattenberg the descent started. The approach procedure for this flight was a LOC DME EAST, to be followed by a landing on runway 26 at Innsbruck (LOWI). Descent (approaching RTT) - the passenger should hope that the pilot knows what he is doing Innsbruck's approach is very particular. It consists of an instrument approach followed by a visual approach. The instrument approach is similar to a common ILS approach, except that the localizer will lead you on an invisible path whose axis is not the runway axis (there is an offset between the localizer course and the runway centerline heading) and whose "target" is not the runway treshold, but a spot from which the approach turns to a visual procedure (for LOWI, the localizer - OEV loc. - is situated just south of the airport and up to 6 nm can be flown visually). There are a few airports in the world that allow such particular and curved approaches, I can cite Innsbruck of course (LOC DME EAST/WEST rwy 26, Honolulu Int'l PHNL (LDA/DME rwy 26L), Reggio Calabria LICR (VOR/DME SDF rwy 33), and the best known of all, but nowadays closed Hong Kong Kai Tak Int'l VHHH with its IGS rwy 13 procedure. This was the most difficult approach in aviation history, because of the offset making aircraft (mainly 747 types) negotiate a 47° right turn on short final over a very dense urban area, demanding a special qualification for the crew. As I've also tried it like many nostalgic FS pilots here is an illustration: Approach on track 211° - note the localizer signal in the nav display For Innsbruck the offset is only 5° (localizer 256° and rwy 261°) but the danger comes from very high terrain in the immediate vicinity of the airport, more precisely to the north and south, as well as in the approach path. The approach begins at Rattenberg NDB, with a maintained altitude of 9500 feet, turning left to 211° before intercepting OEV localizer (256° 111.1 MHz). At that time, the seatbelts signs had been turned on again and the speed reduced to 220 kts (410 km/h). Intercepting the localizer At about 26 nm (48 km) from the destination I received the localizer signal, showing that the current altitude of 9500 feet was OK. I turned the ADF frequence to 313 kHz to get the signal from Absam NDB (AB) located on the approach path at about 6 nm from runway 26 treshold. At 22 nm from OEV the localizer was intercepted, making a right turn over 7300 feet (2200 m) high terrain (meaning only 2200 feet or 660 m below the aircraft), with the new heading of 256°. Had it been a usual ILS approach, I would already had been on final, slowly descending to the airport following this invisible way. I didn't turn the autopilot to APCH mode for the instrument approach as I usually make manual approaches and landings when the cloud base is not too low and the visibility not too bad. Final (instrument approach) - the airport is somewhere under these clouds, at 12.5 nm (23 km) from current position. Final (visual approach) - at about 1.5 nm (2800 m) from runway treshold, full flaps, spoilers armed I began to lower the flaps with the speed reduced to 170 kts (315 km/h). Passing 5300 feet the aircraft penetrated the cloud layer, by then nothing could be seen during long seconds. At 4550 feet we got out of the haze, with the airport's reassuring runway and approach lights in sight, but not yet lined up with the runway. The gear was set down. As flight OS5901 came to its end, we left (and thanked) the localizer's precious help to concentrate on the visual approach. The speed had then been reduced to 150 kts (277 km/h). The landing was smooth and I used full reverse on this relatively short runway so could exit via taxiway A (had the landing been longer, I should have to make an u-turn at the end of runway 26 and backtrack the runway). Short final - airspeed: 138 kts (255 km/h) Flaps and spoilers were retracted and after a very short taxi to the terminal the engines were switched off, parking brakes set at 18:05 local time, 55 minutes after the engines were started at Vienna. Arrival Return Flight I didn't made the return flight the same day but two weeks later, on the 25th of March evening. The review of this flight will be far more brief than the one of the outward journey, I will only say a few words about the special departure procedure that was observed. Ready for take off The flight routed via the same waypoints (RTT, SBG, LNZ, VALIK) as the going flight, but with a different cruise altitude. I set clear skies all along the way, which gave the opportunity to see the landscape; rather interesting in the first 30 minutes of the flight. Departing from Innsbruck is as special as arriving. Aircraft, once airborne from rwy 08 or 26, have to intercept OEJ localizer (068° 109.7 MHz) located east-north-east of the airport, the initial departure being a visual procedure. Upon reaching the localizer, aircraft must change to 66° using the localizer back course and then head towards RTT NDB. Departing aircraft must also observe maximum rate of climb due to the surrounding high terrain. I departed from runway 26, then climbed on track 270° before negotiating a 200° tight left turn under visual before reaching the 68° heading of the localizer. I guess this departure sequence must be quite sickening to sensitive passengers but I've never experienced it in real life. As the aircraft was climbing, we could progressively discover the mountains stretching as far as the eye can see. Departure (heading 66°) - maximum climb gradient Tools Used Aeronautical documents: Cruise - between Rattenberg and Salzburg JEPPESEN enroute chart E(LO) 9, approach plates and airport diagrams for Vienna - Schwechat (LOWW) and Innsbruck (LOWI), ARRIVAL and SID charts for LOWI. Commercial Software: Microsoft Flight Simulator 2000 Professional Edition Freeware Add-On Software: NavDash 2.5 by Masakazu Iizuka (NAVDAS25.ZIP) NavDash 2.5.4 update for FS2K by Masakazu Iizuka (ND254UP.ZIP) FS2000 Replacement Clouds by Chris Willis (RPRL3CLD.ZIP) Vienna Schwechat International Airport Scenery v0.99 by Stefen Siegl and Philip Zajicek (LOWW_099.ZIP) Innsbruck Scenery v1.1 by Ricky Blanco and Neus (IBF.ZIP) MD-87 EFIS Panel by Paul Golding/Project Freeware (PGMD87V1.ZIP) Austrian Airlines McDonnell Douglas MD-87 by the Project Freeware Group (included in the PGMD87V1.ZIP package) Boeing 707-320 Sound Package, an original sound set by Daniel R. Careri, modified by Charles Fox (CF707SND.ZIP) On short final rwy 29 at Vienna Hong Kong Screen Shot: Kai Tak 2000 Scenery v3 by Thomas Kwong (KT2000V3.ZIP) Cathay Pacific Airways Boeing 747-400 - Project Open Sky, designed by Mitsushi Yutaka and Hiroshi Igami, flight dynamics by Johan Dees, painted by C. Vincent Cho (OS744CX.ZIP) Many thanks to all these people for their quality add-ons. Hope you've enjoyed reading this review. Cedric De Keyser cdk@ngi.be -
Vienna - Innsbruck (And Return) Flight Review
Nels_Anderson posted a topic in Nels Corner - Articles
View full article -
How To Fly Dangerous Approaches: Innsbruck, Austria By Andrew Herd Click LOWIunl.pdf to get large size PDF image Navigational equipment required: Standard basic avionics fit plus VOR indicator, DME, and ADF. Aircraft: This tutorial can be flown with the Microsoft Lear and I have included situations for that aircraft. If you are unfamiliar with the flight parameters for the aircraft I have included a crib sheet for the Lear here. The Microsoft .air file for this plane is not one of their better efforts and I would recommend using Steve Small's .air file if you want the aircraft to fly anything like the real thing. The other thing that I must warn you about on the Lear is that whoever did the panel forgot to put the autothrottle on it. Yeah, I know, hilarious, good job Microsoft don't make real planes, is it not? This means that you will have to ensure that the autothrottle arm is checked by going to the menu and visiting \aircraft\autopilot. Note that in the situations, the fuel load has been cut to about 25% for the sake of realism, which will allow you to land without using up the entire runway. Scenery: I used the Innsbruck airport from Aerosoft's excellent German Airports 1 payware package and Eddie Denney's RealSceneFS mesh. There are various freeware versions of Innsbruck around on this web site which are worth a go if you don't have German Airports 1, and Eddie's mesh isn't the only one available for this area, so shop around and use something else if you prefer - but I would recommend using a mesh add-on as the approach will make more sense if all the mountains are actually there! The one thing you must do is to download Andreas Widmann's Innsbruck navaids correction (lowioej.zip) which is available here on FlightSim.Com. Without it, you will be missing most of the rather complex localiser setup that Innsbruck possesses - it isn't there in the default scenery. Andreas has implemented the localiser as a VOR, but it is correct that it lacks a glideslope. If you don't install it, then parts of this tutorial will not make much sense. Downloads: INNSBRUCK_APPROACH.ZIP - extract these files into your \FS2000\pilots folder Comments: The tutorial assumes that you understand the basics of VOR and NDB navigation and that you know the basics of how to fly an ILS. I am assuming that you have flown the earlier approaches in this series and have learned the techniques explained there. Innsbruck must be one of the most beautiful airports in the world, but it isn't in the most convenient place. The runway is at an elevation of 1900 feet and the final approach has to be made in a narrow valley with enormous mountains on either side. The descents are steep, at over 400 feet per minute, the tolerances are tight, the localiser is offset five degrees, the final approach is visual and the missed approach procedure involves a steep climb followed by a terrifyingly tight turn. If this isn't enough to put you off completely, there is the added challenge of Foehn wind conditions. The Foehn is special to the Alps, but similar sorts of winds occur in mountainous regions all over the world, (the Chinook in the Rockies, the Sirocco in Italy and the Khamsin in Egypt, for example.) In each case the principle is the same. When humid air reaches mountains it has to rise and it cools down in the process. Eventually the air saturates and it starts raining, which dries the air; usually when the air masses reach their highest point. Then the air begins to fall and as it does it warms up again. It doesn't sound too bad when it is put like that, but the result is a surface wind which at Innsbruck has a direction of 100-180 degrees, average windspeed of 15-22 knots, and gusts to 30-50 knots, which can make the approach fairly challenging. The notes on the approach make the admirable understatement that severe turbulence, associated with horizontal windshear, and severe downdrafts can be expected below 5000 feet, especially over the town of Innsbruck itself, which can make approaches from the west particularly tricky. Take some time to study the approach plate series. Please click the top thumbnail to download the PDF file containing all the approach plates you need. Jeppesen have also allowed us to reproduce an approach plate and you can view this by clicking the lower thumbnail. Instructions: Please make sure you have Indicated Airspeed (IAS) set. If you have True Airspeed set, the instructions which follow will make no sense at all. Ensure that the EHSI and the RMI of the aircraft are aligned, which is the default situation. Also, ensure that you do not have gyro drift checked under the realism settings, unless you are proficient at making corrections for this. Do not use the GPS on pain of death. The tutorials are written for the FSS plates, but I have indicated where the Jeppesen plates differ. Last of all, before we get going, if any real-world ATPL holders would like to correct me on any of this, I would be glad to hear from them. Talk through Situation 1: East procedure Rwy 26 precision approach - select situation InnsbruckLearVillach1a The situation places you inbound to the Rattenberg NDB at 16000 feet, with an IAS of 280. You are about 64 nm from the Villach VOR and the aircraft is in Nav hold mode. Looks good out of the window, doesn't it? Nice day and all. Heh, heh. Anyway, you are are planning to set your passengers down in Innsbruck very shortly, so tune in to the ATIS (126.025, welcome to European fractional frequencies - visit options, setting, instrument and click 25 khz so the radio will receive it) and get the weather report. Those of you who didn't reset the altimeter on the Aspen approach will remember to do it now - for the rest of you this is a friendly reminder. Now take a look at the glass. In these winds, the aircraft is tending to stray off the airway, so it might be worth unchecking the nav hold and switching in heading hold to get back on track. Your ADF should be tuned to 303, which is RTT NDB, and the white needle should be pointing straight up if we are heading toward it, so make any alterations of course you need. One of the reasons for choosing this approach is that it is a good demonstration of how far commercial pilots has to anticipate - and do remember that we aren't doing any radio communications here, which adds to the workload. If you look at the STAR plate with VILLACH 1A on it, it seems as if all we have to do to align with the approach is to alter course onto approach once we reach RTT and fly straight in - but there are two reasons why we can't, which will be apparent if you study the East Procedure plate as well. The first reason why we can't turn straight inbound is that to begin the approach we would need to alter course by nearly ninety degrees, which would spill everyone's drinks, not to mention being an illegal turn. The other problem is that we are at 16000 feet and the profile begins at 9500. Given that the airway we are on has a minimum enroute altitude of 15000 feet, somewhere along the line we are going to have to lose at least 5500 feet, even if we are down to the MEA at RTT. The solution is to fly around the holding pattern in order to lose height and align course, and with one minute legs, if we lose 1800 feet on each inbound and outbound leg, one turn should be enough. The one thing in our favor is that our approach angle to RTT means we can make an uncomplicated direct entry to the holding pattern. By the way, if you don't know how to fly a hold, then I recommend reading Jaques Zahar's superb tutorial on the subject, which explains everything you need to know. Reduce your speed to 250 knots and watch the white NDB needle - the moment it begins to swing, begin your holding pattern entry. Screen shot one shows the Lear making the first turn after crossing the NDB. Don't be in too much of a hurry to turn onto 048 - if you judge your turn so that the CDI needle is deflected about a dot and a half as you become established on the outbound course, you should be well positioned to make the distant turn of the pattern without having to tighten up too much in order to prevent an overshoot. Once you are established outbound, get the instruments set up to intercept the inbound leg. The holding pattern is centered on RTT, but is aligned on the 228 radial from the Salzburg VOR, so you need to tune Nav1 to 113.80 and twist the course to 228. If you watch the EHSI on the outbound leg (one minute legs, so use a timer), you should be able to correct for wind drift by making sure your course parallels the CDI, a neat trick which cannot be done without a glass cockpit. You can descend in the turns as long as you restrict your bank angle to fifteen degrees, but beware the Lear's horrible tendency to lose height very rapidly as it is going around - you can easily end up a thousand feet too low here, which could be a fatal mistake. The solution is to set your target height to 10500 and to add quite a lot more power in the turns, being careful not to let the airspeed balloon. Dropping 8 degrees of flap won't hurt either. Screen shot 2 shows an almost perfect intercept of the inbound leg, with the aircraft coming nicely down to altitude. The inbound leg requires a certain amount of concentration. You must identify the OEV localiser no later than overhead the RTT NDB, so tune Nav1 to 111.1 well before you reach it. Reduce speed to 180 knots, drop 8 degrees of flap if you haven't already, and the moment the white needle swings again, indicating that you are crossing back over the NDB, which is the initial approach fix, alter course to 211 and maintain height - assuming you have the localiser - if not, you will have to go around the pattern again. Now set a course of 255 on the OBS. The object of the exercise is to allow us to identify D22 from the localiser. In these weather conditions, this is a really tricky one to get right, and I failed to do it first time too. You should be able to see the localiser on the EHSI, so if you don't intercept it exactly at D22 just fly on until you do. This is only a simulation after all - if real life you would want to do it perfectly - that is why they pay the professionals the money they do. Screen shot 3 shows the D22 intercept. When you reach this point alter course onto 255 and maintain altitude. Now the kind people who did the plate obviously appreciated that the cockpit workload is rather high up till now, because they allow you a short breather before making the descent, which begins at D17.2 from the localiser. At this point the reason for the D22.0 intercept becomes clear - the main problem if you overshoot RTT by a significant margin is that you can end up intercepting the localiser as close as D20, which gives you very little time to prepare for the descent; and descending from above the localiser could easily result in a controlled flight into terrain. At this point you can tune the Absam NDB on your ADF (313) as you may need it for a missed approach. Once you are established inbound on the localiser course, drop 20 degrees of flap, and start reducing speed. Now the big question is what IAS we actually need here. The SAS FSS plate is optimised for a Boeing 737 and suggests a fairly high approach speed of Vref 30 + 15 until visual, which builds in a good safety margin for adverse weather conditions. Later, if you want, you can fly the approach in a 737, but I would recommend a bit of practice in a smaller aircraft first. In the Lear, I would recommend is an approach speed of 130-140 kias, which allows a similar safety margin, and so we need to need to reduce speed to 140 knots and drop 40 degrees of flap as we begin our descent at D17.5. Once you have the localiser, drop the gear and get on down. You will find that a rate of up to 1200 fpm is needed initially, depending on wind and turbulence, and pay very, very close attention to the altitude restrictions, because the clearance over obstacles isn't that great. The missed approach is at at D4.0 from OEV, the localiser, at 3700 feet. Screen shot 4 shows the situation at about D14 from the localiser. Depending on your luck, you should be visual fairly early on in the descent, and you can fly her in the moment you feel happy to do so. When you cross the threshold, cut the thrust to idle (I would suggest that you knock out the autothrottle at about 5 nm from the localiser, or you may have trouble getting your airspeed right given the wind conditions) and get ready to deploy the spoilers on touchdown. You can let her roll to a halt with a touch of brakes, reverse thrust would be overkill. Situation 2: ILSDME Rwy 26 precision approach in bad weather - select situation InnsbruckLearVillachBad OK, that first approach shouldn't have been too difficult if you have flown the other tutorials in this series, now let's do it in worse weather. The problem in this situation is the gusting wind, which plays havoc with the autopilot and means that you have to pay extremely close attention to the airspeed and sink rate on the turns in the holding pattern. Depending on which way you are travelling, you will probably find that you need 30 more knots set on the autothrottle than you need in order to maintain a given IAS. I found I had to fly the descent with 180 knots set in the autopilot and a descent rate of 1200 feet per minute to begin with, easing to 800 feet per minute later. As you descend, be prepared to alter your descent rate if you look to be going down too fast. Once you pass RTT inbound ensure that you tune the Absam NDB on your ADF (313) as you may need it for a missed approach. The missed approach point is at D4.0 from OEV, the localiser, at an altitude of 3700 feet, which is the best height to set on the autopilot. There is a hell of a lot to watch out for on this approach - the wind is blowing you all over the place, so try not to stray off the localiser, and watch your height like a hawk, because going below one of the restrictions could pile you into a mountain. Too high is better than too low, believe me. The critical restrictions are at D8.0 to D6.0 as at that point you are flying over a mountain with only a thousand feet to spare (screen shot 6). This is not the place to discover that you haven't reset the altimeter, and in these weather conditions it is all too easy to forget your altitude while you are fighting to keep the plane on track. This is, as you have probably already guessed, a missed approach. You might be visual at the MAP, but I doubt it. When you take the decision, lift the gear, knock out the autopilot, push the throttles forward and pick up your flaps to 20 degrees once the airspeed exceeds 140 knots. I can't emphasis too much that you need to climb as high as you can by the time you reach D1.0 from the localiser, and then make the sharpest turn the aircraft is capable of, because there is no room at all for executing this manoeuvre. I suggest at least a thirty degree bank, forty five if you have the airspeed, and flying the aircraft by hand on full throttle - and at the risk of repeating myself, make sure you gain all the altitude you can before doing the turn, because if you try to simultaneously climb and bank steeply a stall is almost inevitable. At the NDB, lift the flaps, set 9500 altitude and a 1500 fpm climb rate, set the heading to 075 for the outbound course (if you leave the OBS set to 255, the localiser will sense normally, even though you are flying it the wrong way), reset the autothrottle, and switch the autopilot back in, if you are cool enough. This is probably the moment to say something to the passengers like, "Er, we just had a slight problem and had to go around, did any of you see the expression on the face of that bird perched on top of that cliff back there?" Once you are past Absom, tune the RTT NDB on 303 and at D14.0 on the localiser, alter course to it and enter the holding pattern using a teardrop entry. Not much fun to do that in real life, I think. The Jeppesen plate has an important difference from the FSS one, in that the missed approach outbound track uses the back course of the OEJ localiser, yup, there are two of the little varmints (unless you are using the default MS scenery, in which case OEJ is missing). The trouble with the Jepp plate is that it isn't very clear, and it is all too easy to fail to appreciate what is going on, especially given the single letter difference between the localiser IDs and the sheer amount of clutter on the chart. Flying the Jeppesen missed approach is much the same as flying the FSS one to begin with, except that Jeppesen put a minimum altitude constraint of 3700 feet on the climb before the turn at D1.0 OEV. You then intercept the OEJ (109.7) localiser front course on 068, and once you have passed over the beacon, fly out on the back course (hit the back course button on the dash) on 066 with maximum climb gradient until you reach 9500 feet, after which you turn left and fly direct to the RTT NDB where you hold again. One of the disadvantages of this procedure is that at the very moment you need all the help you can get you are very close to the localiser, with the needle is so sensitive it isn't much good, though to be fair, this is partly down to the way the localiser has been implemented as a VOR in the fix. Situation 3: West procedure Rwy 26 precision approach - select situation InnsbruckLearWest If you have got this far, I consider you to be an experienced pilot, so no more Mr. Nice Guy. We are now going to fly the west procedure, which is one of the most difficult ones in existence. I suggest that anyone who needs to empty their bladder does so now, to save embarrassment later. By the way, the screen shots show much better visibility than you are going to get. I thought you might like to see the mountains just once. The situation places you about 18 nm outbound from the KPT VOR at 13000 feet, the MEA for this transition. Nav1 is tuned to KPT on 109.6 and the ADF to 413, which is the KTI NDB, which is the IAF. You will reach KTI when the DME reads 42 nm from KPT, so sit back and enjoy the view for the time being. At about 35 nm DME, reduce your IAS to 250 knots and prepare for the turn. At about 41 DME, alter your heading onto 104 degrees, retune Nav1 to the OEJ localiser on 109.7 and twist the OBS to 068, your inbound heading. Reset your altitude to 11500, with a sink rate of 1500 fpm and once you have made the turn, reduce your IAS to 180 knots and drop eight degrees of flap. Unless you have eight pairs of hand, use of the pause key might be appropriate here. According to the procedure, the OEJ LLZ/DME must be identified not later than overhead the KTI NDB and with Andreas' fix applied this is exactly what happens, as shown in screen shot 8 - see the white ADF needle falling. Looking at the plate, you should intercept the localiser at D20.0 at 11500 feet. As the CDI begins to center, alter your heading to 068, reset your altitude to 5000 feet with a descent rate of 1000 fpm, and once you have the localiser, drop your gear and reduce speed to 140 IAS with 40 degrees of flap. This should allow you to make the altitude restrictions without any problems - just make sure that you don't get so obsessed with playing around with the descent rate that you wander off the localiser! The MAP is at D6.0 at 5000 feet, at which point you have actually crossed Innsbruck and must conduct a visual approach after making a tight right hand turn assuming you are VFR. I would recommend flying this one by hand, because once again, there isn't a lot of room to get around, and the autopilot is unlikely to manage it. This turn is very problematic: if you make it too wide, then you will have trouble establishing yourself on finals; too tight and you may not have the airspeed to get around. I chose a bank angle of between 30 and 45 degrees and had just enough room to get in. In real life, this one would be very sweaty first time. Not to mention twentieth time - it is bad enough in Flight Simulator. By the way, you did remember to contact ATIS and reset the altimeter, didn't you? Andrew Herd andrew@flightsim.com -
View full article
