FlightGear wiki - User contributions [en]

Innsbruck Airport

2014-09-29T17:14:01Z

Ot-666: /* Download */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below.

[http://eaip.austrocontrol.at/lo/131212/ad_2_lowi.htm Austro Control 2013 LOWI Maps (Luftfahrthandbuch Österreich / AIP Austria)]

These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East 2007]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West 2007]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West 2007]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery Overlay ==
Since terrasync terrain is mostly catching up, the download is currently only containing the files needed to use as a overlay for the official terrasync scenery

(Better height data / resolution and some shape file updates are still on the developer wishlist...)

The repo currently contains LOWI, some stuff in Austria and EDNY (Germany). [http://gitorious.org/fgfs-custom-scenery/custom-scenery-overlay/ GIT Repo - Custom Scenery Overlay]

{|
| Autors: || Oliver Thurau, Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.11.24
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=BFsRThNldh0 Flightgear - Simply Innsbruck]
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Up to date download is via the download button at the repo available: [http://gitorious.org/fgfs-custom-scenery/custom-scenery-overlay/ GIT Repo - Custom Scenery Overlay]
* For using the scenery current Flightgear or GIT is recommended, but it should work with fgfs v2.8 and up.

=== Development ===
* See this [http://forum.flightgear.org/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually.
* The previous custom scenery based on the terrain by the Austria Scenery Project is no longer available!

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

FlightGear Newsletter July 2014

2014-08-02T19:54:50Z

Ot-666:

{{Newsletter-header|July 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-item|5 years of newsletters}} 
{{Newsletter-cover-header|Development news}} 
{{Newsletter-cover-item|A Canvas based GNS 530 GPS}} 
{{Newsletter-cover-item|Nasal: Making safer base-class calls}} 
{{Newsletter-cover-item|FGCamera}} 
{{Newsletter-cover-item|Osm2city}}
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}} 
{{Newsletter-cover-item|Paro Int. Airport - VQPR}} 
{{Newsletter-cover-header|Other}} 
{{Newsletter-cover-item|Support for Nasal in Notepad++}} 
{{Newsletter-cover-item|Primary Flight Displays for Android Devices}} 
{{Newsletter-cover-item|Parachute for YASim (Thrusters & Nasal)}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}} 
{{Newsletter-cover-item|Mainair Flash 2 Alpha}} 
{{Newsletter-cover-item|Aero L-159 ALCA}} 
{{Newsletter-cover-header|Multiplayer events}} 
{{Newsletter-cover-item|FGUK Mach Loop Challenge}}
|}
</div>
== 5 years of newsletters ==
[[File:Fgmagfiveyears.png]]

The [[FlightGear Newsletter July 2009|first edition]] of the FlightGear newsletter in its current form was published in July 2009. At the time, there was no place where news from the various "sections" of FlightGear was collected. After several discussions and earlier fruitless attempts, the first edition was hosted on the wiki. This allowed (and still allows) anyone to contribute by writing articles, collecting news, checking grammar and providing images. Over the years we have together written 60 editions (take a look at [[FlightGear Newsletter|the archive]]).

<big>We would like to thank all readers and contributors for their support!</big>

PS: Please take a look at [[FlightGear Newsletter#You are invited to contribute!|FlightGear Newsletter]] if you're interested in helping!

== Development news ==


=== A Canvas based GNS 530 GPS ===
After a long hiatus (3 years!) forum user cbendele felt like doing some FlightGear aircraft modeling again. Three years ago, when he started the panel for his Bo, he could not find a nice, modern, panel mount IFR GPS. The King GPS we have is ancient, and the Garmin 196, while nicely modelled, Is a VFR handheld. So he decided to start with this:

[[File:Gns530-prototype-07-2014.png|300px]]

The GNS530 is already kind of outdated as well, but together with its smaller sibling the GNS430, it is still much more widespread than its successor (GTN650/750). Also the GTN650/750 use touch screen interfaces.

Right now this is very much work in progress. It is also the first time cbendele wrote more than five lines of nasal, so he was basically learning the language while he wrote this. Still, it's far enough to present it here and let people try it and send critique and suggestions. Learn more at [[Garmin GNS530]] or the [http://forum.flightgear.org/viewtopic.php?p=215254#p215254 forum topic]

=== Nasal: Making safer base-class calls ===
There is a lot of Nasal code floating around doing the equivalent of this when using multiple inheritance to make base class calls:

<syntaxhighlight lang="nasal">
object.parents[x].method();
</syntaxhighlight>
Internally, this works such that Nasal's inheritance mechanism relies on a so called '''parents''' vector that contains a list of classes that are used for field/method look-ups. This vector can be accessed using numeric indexes - thus, the correct value for '''x''' is directly affected by the way the parents vector is set up, i.e. its internal class ordering:

<syntaxhighlight lang="nasal">
var myClass = {parents:[FirstBaseClass, SecondBaseClass, ThirdBaseClass] };
</syntaxhighlight>

However, this practice of using indexed parents access to look up a base class should be considered a "hack" and discouraged, because it's not a particularly robust or even safe way to call a superclass, simply because it doesn't tell Nasal anything about the name of the class you're trying to call, but merely its index in the inheritance/lookup vector, which may be subject to change (e.g. due to refactoring). Thus, we encourage people to actually use Nasal's built-in '''call()''' API to accomplish the same thing in a more robust fashion:

<syntaxhighlight lang="nasal">
call(Class.method, [], me);
</syntaxhighlight>

This will tell Nasal that you want it to call a certain method in a particular class - and if that fails, you'll get better diagnostics (error messages), too. The main problem here is that the other approach is pretty vulnerable when restructuring your code, as it is heavily reliant on inheritance '''ordering''' - which is something that isn't exactly straightforward: code shouldn't "break" just because the inheritance ordering is modified. Thus, please try to use the latter idiom. If in doubt, just get in touch via the Nasal sub forum.

To pass argument to the method, just add them to the 2nd argument, i.e. the empty vector:

<syntaxhighlight lang="nasal">
call(Class.method, [nil,nil,nil], me);
</syntaxhighlight>

To pass a custom namespace environment, you can use this:

<syntaxhighlight lang="nasal">
var namespace = {};
call(Class.method, [nil,nil,nil], me, namespace);
</syntaxhighlight>

Which would be equivalent to this example using an anonymous namespace:
<syntaxhighlight lang="nasal">
call(Class.method, [nil,nil,nil], me, {} );
</syntaxhighlight>

(If you want to preserve/modify the namespace, it makes sense not use an anonymous namespace though).

To do exception handling, you can pass an empty vector and check its size (>=1):
<syntaxhighlight lang="nasal">
var err = [];
call(Class.method, [nil,nil,nil], me, {}, err );
if(size(errors))
print("There was some problem calling a base class method: Class.method()");
</syntaxhighlight>

You can also declare the variable expression inline:

<syntaxhighlight lang="nasal">
call(Class.method, [nil,nil,nil], me, var ns={}, var err=[] );
if(size(errors))
print("There was some problem calling a base class method: Class.method()");
else {
print("Success, namespace is:");
debug.dump(ns);
}
</syntaxhighlight>

== FGCamera ==
Development of FGCamera continues. The script is being redesigned to be compatible with default view system. The upcoming version (FGCamera v1) will have new camera mode: "world-view".

{{#ev:youtube|hebx8WdXHa0}}

== Osm2city ==
Development of Osm2city continues. The video shows Innsbruck, Austria (LOWI) with Flightgear at 1440p (Rendered for youtube at 1080p).
For more information see: [[Osm2city.py]]

{{#ev:youtube|V_Bkpx8tANE}}

== Scenery corner ==
=== Paro Int. Airport - VQPR ===
[[File:VQPR PARO AIRPORT.jpg|320px|right]]
Works have been added to [[Paro Airport|Paro International Airport]] (VQPR) with terminal, tower, hangars and other buildings. Now users you can enjoy the apron lights, the reference points like Mr. Smiths House or other POIs like the Sangchen Choekhor Monastery. [[TerraSync]] has it all! It is not necessary to download any custom scenery. More information can be found on the wiki page: [[Paro Airport]]. This is the first airport of the Bhutanese Series. Three new domestic airports like Gelephu Airport (VQGP) are currently being developed. Work also continues on navaids for the Kingdom of Bhutan - of course only in the FlightGear-World. Everybody is invited to follow the stage of development at the designers wiki user page ([[User:Fgjosh|Fgjosh]]).

{{#ev:youtube|itNY9YUmY3M}}

== Support for Nasal in Notepad++ ==
[[File:Highlight parse.png|400px|thumb|Screenshot of [http://gitorious.org/nasal-support/nasal-npp Nasal support for Notepad++]]]
Programming in Nasal on Windows can now be a lot friendlier with [http://gitorious.org/nasal-support/nasal-npp Nasal support for Notepad++]. It provides comprehensive syntax highlighting and class/function listing in a hierarchical fashion.

Syntax highlighting is available for other editors as well, for more information see [[Howto:Syntax highlighting for Nasal]]

== Primary Flight Displays for Android Devices ==
Android devices are light, thin, and offer a very decent computing power and graphics processing. They are battery operated and can connect to other devices through WiFi (there is no need of cables). They are, in fact, perfect for integration in home-made cockpits. This new project offers the opportunity of extending their usage in the form of Primary Flight Displays and Navigation displays for airliners in FlightGear. There are currently four Primary Flight Display (PFD) Apps in "early production" state: Basic, Boeing 777, Boeing 787-8, and Airbus 330. The Basic App is at this moment available in the Android Play Store. The other Apps will be uploaded during the next days provided that no serious problems are found in the Basic App. You are more than welcome to test it and give feedback! Visit the project website for more information: https://sites.google.com/site/flightgearandroid/

{{#ev:youtube|jd61x-_QNpM}}
{{#ev:youtube|Y6M9SyMZSCk}}
{{#ev:youtube|N1D--DZjvtE}}

== Parachute for YASim (Thrusters & Nasal) ==
[[File:V-1 Parachute.png|350px|thumb|V-1falling slowly with a parachute]]
Tomaskom developed a realistically behaving parachute for YASim aircraft. It is capable of a slow and stable fall and can recover the aircraft even from very severe rotations. It all began as a question about a parachute which ended by brainstorming of the best approach. See [http://fguk.eu/index.php/forum/development-hangar/4546-external-reactions-forces-in-yasim this forum topic] for the discussion.

Re-implementing the code elsewhere is very easy. Most of it can be blindly copied with just some adjustments (trigger binding, chute area, ...). See [http://forum.flightgear.org/viewtopic.php?f=49&p=215650 this forum topic] for instructions.

Currently there is a reference implementation in a special version of the V-1 flying bomb, available at [http://fguk.eu/index.php/hangar/viewdownload/11-other-objects-and-vehicles/400-v-1-flying-bomb FGUK]. You can also get an idea of it's stabilization properties from [https://www.dropbox.com/s/81ns5ib5tf3y74t/V-1_Parachute.avi this video]

The drone (Firebee) for which the parachute was requested is not yet publicly available.

== In the hangar ==
=== Mainair Flash 2 Alpha ===
[[File:Flash2a_in_Air2.png|350px|thumb]]
The microlight [[Mainair Flash 2 Alpha]] is now weightshift controlled and has a new wing model.
* redesigned FDM with weightshift-control
* new wing model
* customizable controls
* weight and balance gui
* animated cockpit view
* animated pilot and an optional passenger
* emergency parachute
* multiplayer ready
* aerotow hitch

=== Aero L-159 ALCA ===
{{#ev:youtube|uLojBI7ezdM|350|right|L-159 Disintegration}}
A first public version of the L-159 ALCA (Advanced Light Combat Aircraft) has been released. The aircraft is still in alpha stage and fairly incomplete (there are some changes to the model planned, so no texturing yet, no cockpit instruments), but it already has many advanced and sometimes unique features, most notably the disintegration animations. 
Some of the most important features include:
* Unique model disintegration animation (video on the right, see details here: http://forum.flightgear.org/viewtopic.php?f=4&t=23681)
* Cannons with realistic fire rate and tracers once every few rounds, visible/audible over MP (hit transmission is a work in progress)
* Fully automated fuel system with automatic source switching and fuel level balancing
* Carefully tuned lights including Rembrandt support, light intensity and flares fading in daylight. You may need to increase the Lights shader setting in order to see all effects with Rembrandt on.
* Most payload options modeled, including optional experimental fixed fuel probe
* I consider the FDM (YASim) almost complete and generally well tuned, handling changes a lot with heavy payload
Download available from the FGUK hangar: 
http://fguk.eu/index.php/hangar/viewdownload/8-military-jets/409-l-159-alca
[[File:L-159.png|300px|thumbnail|left|L-159 ALCA]]
{{-}}

== Multiplayer Events ==
=== FGUK Mach Loop Challenge ===
'' Saturday 9th August 2014 - Llanbedr Airfield (EGOD) - 1900 G/U/Z''
{{-}}
{{#ev:youtube|XK0Y1sfijLY||right|A trip around the loop with the Vulcan B2}}
[http://www.fguk.eu FGUK] will be taking the Mach Loop Challenge on Saturday 9th August, as flown by BAE in their Eurofighter simulator at Warton. The world-famous low flying route in North Wales, on the doorstep of FGUK's Llanbedr headquarters, is a 26 mile course threading the valleys and hills around Machynlleth. Can you consistently lower your time and beat the other pilots around the course without breaking the sound barrier and startling the sheep?

A custom AI scenario displays the route with fly-through pointers, checks for adherence to the rules, and announces and records your time - just hand in your score file, and you will be included in the results when published in the following week. More information and updates in the weeks either side of the 9th on FGUK's [https://www.facebook.com/FlightGearUK Facebook page] and [https://twitter.com/FlightGearUK Twitter account]. As always at the Mach Loop, there will be photography and video and the event will be streamed live on our [https://www.youtube.com/channel/UCBb-2WXJuAOVh8QvsdVNrrQ YouTube channel].

Recommended choices to fly the loop competitively are Supersonic single and twin seaters, but you can bring anything within reason that doesn't make you a danger to others. Assemble at FGUK Llanbedr (EGOD) at 1900 G/U/Z (8pm BST). If you're planning to bring something unusual, we ask you to notify us in the forum to make sure all the models are visible to the camera.

A full briefing for pilots will be published on Sunday, along with the definitive AI scenario for the competition. Check the [http://fguk.eu/index.php/12-flight-articles/saturday-flight-articles/21-saturday-9th-august-mach-loop-challenge ongoing event article] and the [http://fguk.eu/index.php/forum/saturday-night-flying/4659-flightnight-9-8-14-mach-loop-challenge?start=40#16865 forum thread] to keep up to date.

Innsbruck Airport

2013-12-18T17:29:46Z

Ot-666: /* Download */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below.

[http://eaip.austrocontrol.at/lo/131212/ad_2_lowi.htm Austro Control 2013 LOWI Maps (Luftfahrthandbuch Österreich / AIP Austria)]

These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East 2007]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West 2007]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West 2007]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery Overlay ==
Since terrasync terrain is mostly catching up, the download is currently only containing the files needed to use as a overlay for the official terrasync scenery

(Better height data / resolution and some shape file updates are still on the developer wishlist...)

The repo currently contains LOWI, some stuff in Austria and EDNY (Germany). [http://gitorious.org/fgfs-custom-scenery/custom-scenery-overlay/ GIT Repo - Custom Scenery Overlay]

{|
| Autors: || Oliver Thurau, Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.11.24
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=BFsRThNldh0 Flightgear - Simply Innsbruck]
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Up to date download is via the download button at the repo available: [http://gitorious.org/fgfs-custom-scenery/custom-scenery-overlay/ GIT Repo - Custom Scenery Overlay]
* Download as zip is available: [http://www.multiformat.de/ftp/scenery-addon/custom-scenery-overlay.zip Custom Scenery Overlay - 2013.11.24]
* For using the scenery current Flightgear or GIT is recommended, but it should work with fgfs v2.8 and up.

=== Development ===
* See this [http://forum.flightgear.org/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually.
* The previous custom scenery based on the terrain by the Austria Scenery Project is no longer available!

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2013-11-24T23:26:50Z

Ot-666: /* FlightGear Custom Scenery */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below.

[http://eaip.austrocontrol.at/lo/131212/ad_2_lowi.htm Austro Control 2013 LOWI Maps (Luftfahrthandbuch Österreich / AIP Austria)]

These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East 2007]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West 2007]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West 2007]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery Overlay ==
Since terrasync terrain is mostly catching up, the download is currently only containing the files needed to use as a overlay for the official terrasync scenery

(Better height data / resolution and some shape file updates are still on the developer wishlist...)

The repo currently contains LOWI, some stuff in Austria and EDNY (Germany). [http://gitorious.org/fgfs-custom-scenery/custom-scenery-overlay/ GIT Repo - Custom Scenery Overlay]

{|
| Autors: || Oliver Thurau, Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.11.24
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=BFsRThNldh0 Flightgear - Simply Innsbruck]
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Up to date download is via the download button at the repo available: [http://gitorious.org/fgfs-custom-scenery/custom-scenery-overlay/ GIT Repo - Custom Scenery Overlay]
* Download as zip is available: [http://www.multiformat.de/ftp/scenery-addon/custom-scenery-overlay.zip Custom Scenery Overlay - 2013.11.24]
* For using the scenery current Flightgear or GIT is recommended, but it should work with fgfs v2.6 and up.

=== Development ===
* See this [http://forum.flightgear.org/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually.
* The previous custom scenery based on the terrain by the Austria Scenery Project is no longer available!

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2013-11-24T22:47:17Z

Ot-666: /* Development */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below.

[http://eaip.austrocontrol.at/lo/131212/ad_2_lowi.htm Austro Control 2013 LOWI Maps (Luftfahrthandbuch Österreich / AIP Austria)]

These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East 2007]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West 2007]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West 2007]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://forum.flightgear.org/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.01.05
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=BFsRThNldh0 Flightgear - Simply Innsbruck]
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2013.01.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://forum.flightgear.org/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually.

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2013-11-16T14:57:42Z

Ot-666: /* Approach */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below.

[http://eaip.austrocontrol.at/lo/131212/ad_2_lowi.htm Austro Control 2013 LOWI Maps (Luftfahrthandbuch Österreich / AIP Austria)]

These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East 2007]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West 2007]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West 2007]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://forum.flightgear.org/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.01.05
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=BFsRThNldh0 Flightgear - Simply Innsbruck]
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2013.01.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://forum.flightgear.org/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo, but the above download link is recommend: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2013-02-16T14:10:03Z

Ot-666: /* Youtube videos */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.01.05
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=BFsRThNldh0 Flightgear - Simply Innsbruck]
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2013.01.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo, but the above download link is recommend: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2013-01-05T18:38:29Z

Ot-666: /* Development */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.01.05
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2013.01.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo, but the above download link is recommend: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2013-01-05T18:33:30Z

Ot-666: /* FlightGear Custom Scenery */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.01.05
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembarndt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2013.01.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2013-01-05T18:24:38Z

Ot-666: /* FlightGear Custom Scenery */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2013.01.05
|}
[[File:LOWI area overview.jpg|700px]]

Innsbruck - LOWI area overview.

[[File:LOWI with Rembrandt lights.jpg|700px]]

Innsbruck - LOWI with Rembrandt lights.

[[File:LOJO with Rembrandt lights.jpg|700px]]

LOJO helicopter base at Innsbruck airport with Rembrandt lights.

=== Youtube videos ===
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2013.01.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

File:LOJO with Rembrandt lights.jpg

2013-01-05T18:15:59Z

Ot-666:

=={{int:filedesc}}==
{{Information
|description={{en|1=LOJO helicopter base at LOWI / Innsbruck airport with Rembrandt lights.}}
|date=2013-01-05
|source={{own}}
|author=[[User:Ot-666|Ot-666]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

File:LOWI with Rembarndt lights.jpg

2013-01-05T18:15:57Z

Ot-666:

=={{int:filedesc}}==
{{Information
|description={{en|1=LOWI / Innsbruck with Rembrandt lights.}}
|date=2013-01-05
|source={{own}}
|author=[[User:Ot-666|Ot-666]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

Innsbruck Airport

2013-01-05T18:05:13Z

Ot-666: /* Download */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2012.11.01
|}
[[File:LOWI area overview.jpg|700px]]

=== Youtube videos ===
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2013.01.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2012-11-19T09:41:32Z

Ot-666: /* FlightGear Custom Scenery */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2012.11.01
|}
[[File:LOWI area overview.jpg|700px]]

=== Youtube videos ===
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2012.11.01]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2012-11-19T09:40:56Z

Ot-666: /* FlightGear Custom Scenery */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2012.08.05
|}
[[File:LOWI area overview.jpg|700px]]

=== Youtube videos ===
* [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI]
* [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]
* [http://www.youtube.com/watch?v=qPksRhZJqwI&feature=plcp EC135 P2 D-HBBY at Innsbruck airport]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2012.11.01]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2012-11-01T18:43:58Z

Ot-666: /* Download */

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2012.08.05
|}
[[File:LOWI area overview.jpg|700px]]

youtube videos: [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI], [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2012.11.01]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Innsbruck Airport

2012-08-05T13:51:55Z

Ot-666:

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2012.08.05
|}
[[File:LOWI area overview.jpg|700px]]

youtube videos: [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI], [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]

=== Download ===
* Download as zip is available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2012.08.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

Suggested custom scenery

2012-08-05T02:02:48Z

Ot-666:

== Airports ==

The list of airports with improved scenery features is now available from a separate [[Suggested Airports|Suggested Airports page]].

== Landscape ==

* '''France''': Custom scenery for France with improved landcover information and more detailed elevation information (no improvements on the objects) is under development. See the [[Custom France Scenery|Custom France Scenery page]].

* '''Innsbruck (Austria) area''': The scenery currently covers a 1x1 degree area containing parts of Austria and Germany, and makes use of accurate data from the Corine Land Cover, and Open Street Map projects. See [http://flightgear.org/forums/viewtopic.php?f=5&t=5350 this forum post] and [[FlightGear Newsletter August 2009#Innsbruck Gets A Face Lift|the August 2009 newsletter]] for details.

* '''LOWI & Austria Scenery Preview''': This scenery includes the Innsbruck scenario and is much more complete than the previous. It is still experimental, but should try it as having been really good. Info and download can be found [http://wiki.flightgear.org/Innsbruck_Airport here]

Innsbruck Airport

2012-08-05T01:58:55Z

Ot-666:

{{infobox Airport
|name = Innsbruck Airport
|image = Innsbruck_Airport_img1.jpg
|alt =
|iata = INN
|icao = LOWI
|type =
|owner = Tiroler Flughafenbetriebs GmbH 
|city = Innsbruck, Austria
|runway= 08/26
|length= 2000m
|material= Asphalt
|website = [http://www.innsbruck-airport.com/index.html/_lang/en Innsbtruck Airport]
}}
Nestled high in the Austrian stretch of the Alps is '''Innsbruck Airport'''. Innsbruck is a seasonally busy [[:Category:Airports|airport]] that serves the ski/alpine industry. It takes local, national and international aviation [[Interactive Traffic|traffic]].

Use of the Innsbruck Airport is restricted to "High Performance" aircraft by Austrian authorities (see the Austro Control link below). The airport lies within a steep East-West valley, requiring non-ICAO standard procedures to approach and depart.

== Procedures ==
=== Approach ===
''Approach maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

[[Media:InnsbruckAppEast.jpg| Chart: Approach From East]] 
[[Media:InnsbruckAppWest.jpg| Chart: Approach From West]] 
[[Media:InnsbruckDepAll.jpg| Chart: Depart East or West]] 

'''Approach From The East:''' ILS Approach RWY 26. Navigate to the Rattenberg NDB (RTT 303) at FL100. Salzburg Maxglan (LOWS) provides a close and suitable departure runway. From overhead RTT, turn to heading 211°, descend to 9600ft and intercept the ILS (111.1). Dial in Absam NDB 313. At Minimum Descent Altitude (overhead the Absam NDB), pilot must be visual or perform the prescribed missed approach. Turn to runway heading when required and land.

'''Approach from the West:''' LLZ/DME Approach into the circuit for a RWY 26 landing. Depart airport Memmingen Allgau (EDJA), navigate to Kempten VOR (KPT 109.6). Overhead KPT, join the 138 radial and navigate to the Kuhtai NDB (KTI 413), at FL130. When LLZ (111.10) is identified (not established), depart the NDB heading 104° not below FL115. At DME 20.4 miles, commence descent, and join the LLZ. Do not proceed below FL105 if not established on LLZ. Observe minimum altitudes on descent, stop descent at 3700ft. If visual, turn final and land, otherwise follow prescribed missed approach.

=== Departure ===
''Departure maps have been provided in the links below. These are sourced from Austro Control - but may not necessarily be current.''

'''Departure to the East:''' Using Absam NDB (AB 313) and LLZ (OEJ 109.7), depart RWY 08 at max climb. Fly overhead the NDB, establish on the LLZ, to 9500ft.

'''Departure to the West:''' Starting on Absam NDB (AB 313) and Kempten VOR (KPT 109.6), depart RWY 08 at max climb. Cross the AB NDB not below 5600ft and make right turn to 245, for Innsbruck NDB (INN 420). Cross INN not below 9400ft, turn to KPT. Altitude must be 11500 by 39 miles out of KPT.

== Complexity ==
Steep non-standard climb and descent angles, LLZ offset to runway heading. Try throwing some weather in for good measure.

== FlightGear Scenery ==
The required scenery for LOWI is [ftp://ftp.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-1.0.1/e010n40.tgz e010n40.tgz]. It includes all airports listed in this article.

== FlightGear Custom Scenery ==
The download contains Austria with terrain created by Tuxklok from the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14132#p141931 Austria Scenery Project] and the current state of the LOWI and Austria scenery model development.

{|
| Autors: || Christian Schmitt, Tuxklok, Oliver Thurau, Paolo Rota, HHS, David G. and others
|-
|-
| Latest update: || 2012.08.05
|}
[[File:LOWI area overview.jpg|700px]]

youtube videos: [http://www.youtube.com/watch?v=saJEakwvEuE&hd=1 Flightgear - planespotting at LOWI], [http://www.youtube.com/watch?v=gtYMvNQHuEA&list=UUT6mwzOJlbm3PNiYz2X9Vvw&index=3&feature=plcp IAR 80 Romanian WW2 Fighter over Innsbruck]

=== Download ===
* Download as zip os available: [http://www.multiformat.de/ftp/LOWI/LOWI-austria-PREVIEW.zip LOWI & Austria preview 2012.08.05]
* For using the scenery Flightgear GIT is recommended, but it will work with fgfs v2.6 and up.

=== Development ===
* See this [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438 forum post] for more info about the state of LOWI area development.
* Generally, changes will go into the scenery DB eventually. Some yet unpublished updates are to be found in this repo: http://gitorious.org/papillon81/flightgear-custom-scenery

== External links ==
* Austro Control Website: [http://www.austrocontrol.co.at/en/content/lfa/Flugbewilligungen/Special_Performance_Procedures/LOWI/LOWI.shtml| LOWI Page]
* Airport Building Images: [http://www.travel2austria.com/?Tirol:Airport_Innsbruck_Kranebitten| travel2austria.com]

[[Category:Airports in Austria]]
[[Category:Challenging airports]]

File:LOWI area overview.jpg

2012-08-05T01:35:18Z

Ot-666:

=={{int:filedesc}}==
{{Information
|description={{en|1=Above Innsbruck with LOWI airport in the valley.}}
|date=2012-08-05
|source={{own}}
|author=[[User:Ot-666|Ot-666]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

FlightGear Newsletter December 2011

2012-01-02T13:05:26Z

Ot-666: /* Airport of the month */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

{{newsletter}}
[[Image:Fgfs-screen-372-gooneybird-xmas-2011.jpg|thumb|240px|Gooneybird's Christmas wishes]]
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== 2011 annual ==
2011 was the year in which:
* FlightGear 2.4.0 was released
* a [[release plan]] had been set up; leading to more frequent releases
* the FlightGear website was changed into a CMS, allowing more frequent updates
* the wiki saw its 10.000.000th pageview

== Development news ==

=== 2.6.0 release preparations ===
{{Main article|Release plan}}
On January 17, release branches will be created from our [[Git]] repository. That's basically the birth of a new release. From then on, no new features (and aircraft) can be pushed. Only bug fixes are accepted.

Thanks to the branching, development for the next-next release (2.8.0?) can start right away; even before 2.6.0 is released.

==== Aircraft developers ====
Until the release branches are created, changes to aircraft may still be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Aircraft defined as part of the base package (e.g. the c172p) are already in the frozen state and shall not undergo major changes in this period.

Keep in mind that the people that are able to commit your stuff are just as busy finishing their own work as you are! Therefore it is important that you create merge requests for everything that you'd like to see included in the upcoming release, as soon as possible. This includes new aircraft and large updates to existing aircraft.

Don't let it wait for tomorrow, do it today!

=== FlightGear development over time ===
Graphics created by stuart:

[[File:6month.png|800px]]

"As you can see, FG development has been quite variable over time (generally a lot of development in the northern hemisphere winter), but core development, as shown by the red and blue lines (FG is made up of the separate simgear and flightgear codebases) has been fairly constant since the start of the project.It also highlights the massive increase in aircraft over the last couple of years, as shown by the amount of change to fgdata (yellow line)."

For more info, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=12881#p131567].

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

[[File:B-29_wet_runway.jpg|400px]]
[[File:Sopwith_Camel.jpg|400px]]

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

[[File:IAR-80-dirt-1.jpg|400px]]
[[File:IAR-80-dirt-2.jpg|400px]]

[[File:IAR-80-dirt-3.jpg|400px]]
[[File:IAR-80-dirt-4.jpg|400px]]

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

=== New terrain textures ===
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository.
More info and screenshots in this forum [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread]. This is still work in progress, of course.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* '''How long have you been involved in FlightGear?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created. These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== CASA C-101 Aviojet ====
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===
====Learjet 35-A====
The [[Learjet 35-A]] has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it (download soon on forum) and take your favorite plane. There are some really nice areas just perfect for long VFR routes! 
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html the mailinglist].

=== EBAW (Antwerpen - Deurne) ===

Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)

This scenery, is sadly enough, not yet available with terrasync. You can download it from the [https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery Belgian scenery git repo].

[[File:Ebaw_textured_01.jpg|200px]][[File:Ebaw_textured_02.jpg|200px]][[File:Ebaw_textured_03.jpg|200px]]

Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit and the request is done!

The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.

[[File:Fgfs 2011-12-22 20-56-19-72.jpg|800px]]

[[File:Fgfs 2011-12-22 20-57-38-47.jpg|800px]]

Read more about the current state of the development: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438#p83288]

== Screenshot of the month ==
P.A.F. (LFLG home base) wish you a Merry X-mas!

[[File:LFLG Lancair Chrismas.png|800px]]

Merry X-mas!

PAF link : http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania, what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===Updated articles===
*[[Learjet 35-A]] is updated matching the true Aircraft flight manual (with FlightGear limitations). On the Wiki it is one of the best described aircraft.
*[[Unique Features]] now contains a massive list of what makes [[FlightGear]] unique.
*The German [[:de:Flughöhe|Flughöhe]] article is close to complete matching the English version.

== Community news ==
=== FlightGear on Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|2eGOdBsd8Os|400|F-4E formation training at TFFG}} (Also see [[Toward real close formation flight]])
{{#ev:youtube|9_4zOOZTWqI|400|Santa Claus doing a practice run for his big night in December.}}

=== New tutorials and screencasts ===
=== Forum news ===
[[File:Santa2011.png]]

The headers on [http://flightgear.org/forums the forum] have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?

=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
* You can turn on [[anti-aliasing]]? I know I didn't.

[[Category:FlightGear Newsletter|2011 12]]

File:Fgfs 2011-12-22 20-56-19-72.jpg

2012-01-02T13:00:21Z

Ot-666: LOWI rwy08 on a bad weather day

LOWI rwy08 on a bad weather day

FlightGear Newsletter December 2011

2012-01-02T12:58:43Z

Ot-666: /* Airport of the month */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

{{newsletter}}
[[Image:Fgfs-screen-372-gooneybird-xmas-2011.jpg|thumb|240px|Gooneybird's Christmas wishes]]
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== 2011 annual ==
2011 was the year in which:
* FlightGear 2.4.0 was released
* a [[release plan]] had been set up; leading to more frequent releases
* the FlightGear website was changed into a CMS, allowing more frequent updates
* the wiki saw its 10.000.000th pageview

== Development news ==

=== 2.6.0 release preparations ===
{{Main article|Release plan}}
On January 17, release branches will be created from our [[Git]] repository. That's basically the birth of a new release. From then on, no new features (and aircraft) can be pushed. Only bug fixes are accepted.

Thanks to the branching, development for the next-next release (2.8.0?) can start right away; even before 2.6.0 is released.

==== Aircraft developers ====
Until the release branches are created, changes to aircraft may still be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Aircraft defined as part of the base package (e.g. the c172p) are already in the frozen state and shall not undergo major changes in this period.

Keep in mind that the people that are able to commit your stuff are just as busy finishing their own work as you are! Therefore it is important that you create merge requests for everything that you'd like to see included in the upcoming release, as soon as possible. This includes new aircraft and large updates to existing aircraft.

Don't let it wait for tomorrow, do it today!

=== FlightGear development over time ===
Graphics created by stuart:

[[File:6month.png|800px]]

"As you can see, FG development has been quite variable over time (generally a lot of development in the northern hemisphere winter), but core development, as shown by the red and blue lines (FG is made up of the separate simgear and flightgear codebases) has been fairly constant since the start of the project.It also highlights the massive increase in aircraft over the last couple of years, as shown by the amount of change to fgdata (yellow line)."

For more info, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=12881#p131567].

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

[[File:B-29_wet_runway.jpg|400px]]
[[File:Sopwith_Camel.jpg|400px]]

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

[[File:IAR-80-dirt-1.jpg|400px]]
[[File:IAR-80-dirt-2.jpg|400px]]

[[File:IAR-80-dirt-3.jpg|400px]]
[[File:IAR-80-dirt-4.jpg|400px]]

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

=== New terrain textures ===
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository.
More info and screenshots in this forum [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread]. This is still work in progress, of course.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* '''How long have you been involved in FlightGear?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created. These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== CASA C-101 Aviojet ====
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===
====Learjet 35-A====
The [[Learjet 35-A]] has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it (download soon on forum) and take your favorite plane. There are some really nice areas just perfect for long VFR routes! 
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html the mailinglist].

=== EBAW (Antwerpen - Deurne) ===

Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)

This scenery, is sadly enough, not yet available with terrasync. You can download it from the [https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery Belgian scenery git repo].

[[File:Ebaw_textured_01.jpg|200px]][[File:Ebaw_textured_02.jpg|200px]][[File:Ebaw_textured_03.jpg|200px]]

Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit and the request is done!

The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.

[[File:LOWI december.jpg|800px]]

[[File:Fgfs 2011-12-22 20-57-38-47.jpg|800px]]

Read more about the current state of the development: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8438#p83288]

== Screenshot of the month ==
P.A.F. (LFLG home base) wish you a Merry X-mas!

[[File:LFLG Lancair Chrismas.png|800px]]

Merry X-mas!

PAF link : http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania, what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===Updated articles===
*[[Learjet 35-A]] is updated matching the true Aircraft flight manual (with FlightGear limitations). On the Wiki it is one of the best described aircraft.
*[[Unique Features]] now contains a massive list of what makes [[FlightGear]] unique.
*The German [[:de:Flughöhe|Flughöhe]] article is close to complete matching the English version.

== Community news ==
=== FlightGear on Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|2eGOdBsd8Os|400|F-4E formation training at TFFG}} (Also see [[Toward real close formation flight]])
{{#ev:youtube|9_4zOOZTWqI|400|Santa Claus doing a practice run for his big night in December.}}

=== New tutorials and screencasts ===
=== Forum news ===
[[File:Santa2011.png]]

The headers on [http://flightgear.org/forums the forum] have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?

=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
* You can turn on [[anti-aliasing]]? I know I didn't.

[[Category:FlightGear Newsletter|2011 12]]

File:Fgfs 2011-12-22 20-57-38-47.jpg

2012-01-02T12:48:48Z

Ot-666: LOWI airport on a bad weather day

LOWI airport on a bad weather day

FlightGear Newsletter October 2011

2011-10-30T13:58:19Z

Ot-666: /* Scenery corner */

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== FGdata split ===
A team of developers started preparing the FlightGear [[git]] repositories for a significant change. Aircraft will be split of from fgdata, in order to ease development of aircraft and data as a whole. At the moment (of publication of this newsletter) we're in the testing phase; inviting anyone to test out the new system and report any bugs, comments and questions.

We would like to emphasize that those testing repositories are not meant to replace the "old" fgdata yet!

Details can be found on the special wiki page: [[FlightGear Git: splitting fgdata]].

=== Move to CMake ===



=== New Replay System ===
The [[Instant Replay]] system has received a major overhaul. The existing system worked well with specific types of aircraft only, since it relied on a hard-coded set of properties to be recorded/replayed, mainly covering propeller aircraft. Jet engines (thrust-reversers, N1/N2 rpm), or non-standard gears (i.e. a Concorde with 4 landing gears) were not working well though. The new system can be adapted to any kind of aircraft and any kind of custom property or animation.

[[File:FG-instant-replay-new.png|thumb|500px|The new instant replay dialog.]]

Most obvious change is probably an improved replay dialog: the video player-like GUI provides play/pause/skip buttons and also controls replay speed. During replay use the 4 arrow keys as controls (left/right to skip, up/down to speed-up/slow-down). Also new: ''slow-motion playback'' is now supported!

Another new feature is the option of taking controls at any point during replay. Use the ''Instant Replay'' to go back in time, then hit the "My controls!" button to regain controls and continue the flight from the current position. You may find this to be useful to train particular flight phases, such as flying the same approach again and again, maybe using different weather/wind conditions. Even if you messed up an approach: go back, try again, until you're getting better! :) Currently this particular feature is only available for YASim aircraft - except helicopters. JSBSim support is likely to be available soon.

The first step to adapt an aircraft to the improved recording system is to pick one of the ready-to-use configuration files, depending on aircraft/engine/.. type. The configuration file only needs to be included in the aircraft's ...-set.xml file. As an optional second step, you can add more custom properties to cover aircraft-specific effects. For more details, see the [https://www.gitorious.org/fg/fgdata/blobs/master/Docs/README.flightrecorder README.flightrecorder] in the fgdata/Docs folder.

A few adapted aircraft examples showing different levels of customization are already present in current git/fgdata:
* ASK13 (glider)
* c172p (propeller/piston)
* b1900d (turboprop)
* UH-1 (helicopter)
* 777-200ER (jet).

Furthermore, the replay system's buffers are now fully configurable (see /sim/replay/buffer properties). If you have enough memory, you could increase the buffer recording durations and rates.

Work on the replay system isn't finished yet. However, have a test flight with the current state in current git ;-).

=== The bombable addon has been updated ===
[[File:bombable4_4_800.png]]

Flug's [[Bombable]] addon received a number of major updates, among them:

* '''AI aircraft move vertically -- and do loops''': AI aircraft now move much more realistically in the vertical direction. They do loops, dive, and all the rest. Their behavior (climb rates, dive rates, and so on) matches those of the corresponding FG aircraft. This makes for a much more realistic 3-D dogfighting experience in FlightGear.
* '''Realistic roll rates for AI aircraft''': Roll rates are one the most important factors determining the effectiveness of fighter aircraft-- aircraft that can roll faster can turn faster. Now the roll rate for AI aircraft in scenarios can be customized, and bugs in the roll & turn routines for AI aircraft have been fixed.
* '''Significant performance improvements''': Bombable now makes much less of an impact on your framerate, and much less stuttering & slowdown at key points, like when numerous machine gun rounds are impacting.
* '''Damage impact detection is the most advanced element in Bombable'''. It is greatly improved over FG's native impact detection system, and the framework is in place for further refinements or as a model for FG to implement more refined impact detection internally. Damage tracking and communication over Multiplayer works well in a very lightweight with a very low data rate. However, only a general damage percentage is tracked and communicated. Damage to different locations or systems is not simulated. Proof of concept for explosions, fires, weapons damage animations, and crash animations is in place. All these elements could be refined for greater realism.
* '''Relocate any scenario to your location''': Have an AI scenario based in San Francisco, but want to fly in London? No problem, just hit a button in the Bombable menu and your scenario comes to you, wherever you are. Damage levels for AI aircraft and objects are re-set. It's like loading a new scenario without having to re-start FlightGear.
* '''Re-spawn AI aircraft and objects''': After you have shot down (or been shot down by!) AI aircraft or objects in scenarios, you can instantly re-spawn them and try again. (Available in the Bombable menu.)

The last two are kind of game changers--it's like being able to re-start/re-load a scenario instantly without having to re-start FG.

In addition, there have been some feature requests to make the bombable addon more challenging by improving its AI. This spawned an interesting discussion about possible ways to make the AI even smarter than it is already [http://flightgear.org/forums/viewtopic.php?f=6&t=5742&start=300#p140013]. Also see [[Howto: Neural networks in Nasal]].

For a nice video demo created by Vodoun da Vinci, please see [[FlightGear Newsletter October 2011#Community news|community news]].

== Interview with a contributor: Gijs de Rooy ==
''From this month onwards, we'd like to see a monthly interview with a contributor. Questions are available on [[interview questions]] and anyone is free to write an interview (with him-/herself) for next month's newsletter!''

* '''How long have you been involved in FlightGear? What was it that made you join?'''
According to the forum software I joined all the way back in July 2007. One year earlier I was one of the first users of Google SketchUp, free 3D modelling software. After modelling several buildings in my home town, Amsterdam (and placing them in Google Earth) I started working on Amsterdam Airport Schiphol. By then, Google Earth had a (simple) built-in flight simulator. Amsterdam would be the first airport to be modelled especially for that, that was my plan at least...

While modelling Schiphol, I stumbled across this free flight sim, called FlightGear, that wasn't a game, unlike Google's. In [http://flightgear.org/forums/viewtopic.php?f=5&t=473 one of my first posts] on the FlightGear forum I asked for someone to place my models into FlightGear's scenery. Georg (Heliflyer) placed my first buildings. I took some effort, but I finally managed to place buildings myself. Sadly the guy that introduced me to FlightGear and gave me a hobby that would last up till today, passed away in 2009.

* '''Do you have real world connections with aviation or IT?'''
Since two months I'm studying Aerospace Engineering at the University of Delft. So far I really like this mix of hobby and study.

* '''What are your major interests in FlightGear?'''
One of the things I like about FlightGear is the wide range of things one can get involved with: modelling, texturing, writing manuals, collecting data etc. and of course flying itself. Therefore I have a very long list of interests. However, there are three key parts that I particularly enjoy; being the development of scenery and aircraft and helping others by writing wiki articles and replying to questions at the forum.

* '''What project(s) are you working on right now?'''
My main development projects right now are the Boeing [[747-400]] and Dutch scenery. Both can be considered as never finished; there are always things to add/improve.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
Until this year I spent roughly 4 to 5 hours a day on FlightGear related things. Now that I'm studying I have less free time, but still several hours a day on average. Most of that time is taken up by non-development stuff, like the forum, wiki and livery database. Over the years I've been spending way too litle time on the actual flying.

* '''What do you plan on doing in the future?'''
I would really like to bring the 744 to a state where a real pilot cannot spot a thing that is missing in the simulation.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Starting something new is easy, completing it is much harder. I could have never guessed I would still be working on the 744, three years after I started!

I've always been telling newcomers to start improving existing features. It's a great way to familiarize yourself with the project. By looking into existing aircraft's files for example, you will quickly find out how those files are linked together and what their purpose is.

== Snapshot releases ==

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
=== New aircraft ===

=== Updated aircraft ===
The [[Learjet 35-A]] has been updated. Several minor errors have been fixed and improvements have been put in-place. The [[Learjet 35-A]] is the only business jet with a functional autopilot. It is a gem to fly and perfect for beginners and experts to try [[radio navigation]], autopilot control and [[ILS]] procedures. Thanks Xsaint and PH-JBO for the work done.

=== Livery database reaches 600 ===
On October 8, the [[FlightGear livery database]] welcomed its 600th livery! Thanks to 70 authors, the virtual skies are more colourful than ever.

At the moment the contribution system is being rewritten. For the time being, new liveries are only accepted via direct email to [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs].

== Scenery corner ==

=== Support for 8.50 airport data ===
[[File:EHAM_overview_night.png|thumb|270px|[[Amsterdam Airport Schiphol]] by night, with the new 8.50 lighting.]]
[[File:EHAM_gate_D.png|thumb|270px|Schiphol's D gates, in combination with AI traffic.]]
As mentioned in the previous newsletter; efforts are made to bring [[TerraGear]] up to a level where it supports the 8.50 apt.dat format, nowadays used by X-Plane. This new format has all kind of exciting features like curved taxiways and accurate lining/lighting (not just "ordinary" taxiway lines, but also markings like hold lines). Furthermore, seperate runway end definitions so it is now possible to create runways with different markings on both ends (including "empty ends" for runways being only used into one direction).

We'd like to thank Christian (papillon81), Pete (Psadro GM) and Emmilian (i4dnf) for their hard work. It's probably legitimate to say that this is the biggest improvements in FlightGear scenery over the past years!

=== Airports ===

Work progressed on a line of higher detailed service vehicle scenery models.

[[File:Fgfs 2011-10-29 13-41-16-88.jpg|400px|Service vehicles lineup]][[File:Fgfs 2011-10-23 18-02-20-12.jpg|400px|Baggege trailer lineup]]

[[File:Fgfs 2011-10-26 20-46-13-55.jpg|400px|ULD Container trailer linup]][[File:Fgfs 2011-10-16 04-35-08-94.jpg|400px|Short version of the Volvo-FM airport fuel truck]]

Currently the line includes a small tow truck, Baggage trailer, ULD container trailers, Catering Trucks and a Fuel Truck.

You can follow the development on the forum: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=13472]

== Aircraft of the month ==

Diamond DA42 Twin Star

[[File:Fgfs-screen-032.png|600px]]

http://en.wikipedia.org/wiki/Diamond_DA42

== Glider of the month ==

Jean Astir Grob G102

[[File:Astir.png|600px]]
[[File:Fgfs-screen-026.png|600px]]

== Airport of the month ==
[[File:FJDG.jpg|600px]]

The nearest airport is about 700 NM away. Around us are about 30 small islands, none with [[radio beacons]], none with an airport but some with a small beach. This Airport has four odd looking pillboxes. If you click they will open, very slowly. Now if you would have a [[Northrop B-2 Spirit |B2 bomber]] you could park your aircraft in it. If you don't have a [[Northrop B-2 Spirit|B2]] you are allowed to land, but only in an emergency. Fake an emergency and get here, bring piña colada and have a party on the beach!

*It is sooo beautiful here. Oh, where? FJDG, [http://en.wikipedia.org/wiki/Chagos_Archipelago Diego Garcia at Point Marianne]. Perfect for [[VFR]] tours, and a piña colada on the beach.

== Screenshot of the month ==
[[File:Mount Everest VNTR.jpg]]
*[[Learjet 35-A]] and [http://en.wikipedia.org/wiki/Mount_Everest Mount Everest] viewed from West towards East. Atlas image of the route to [http://en.wikipedia.org/wiki/Tumlingtar_Airport VNTR]. I could see the direction of NDB and knew the altitude of the RW. The RW was not visible till the absolute last moment racing down with airbrakes at max. The landing was a success but I had to change underwear and clean the seat.

== Suggested flights ==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
=== 10,000,000 pageviews ===
On October 29, the FlightGear wiki welcomed it's 10,000,000th (10 millionth) pageview! Coming from five million in October 2010, we doubled in just 12 months time. That is a proof that FlightGear has more users than ever and more users are able to find their way to the wiki. Both things are very nice of course!

We'd like to thank everyone that donated some free time to create/improve/correct articles and upload images to the wiki. As the wiki is (just like FlightGear) completely dependant on the community we'd like to emphasize that anyone is welcome to help! You can find a short introduction to the wiki at [[Help:Your first article]].

To 20 million and beyond! We're already well on our way, with {{NUMBEROFVIEWS}} views at this very moment. More statistics are available at [[Special:Statistics]].

=== Nasal documentation ===
Flug and Hooray revamped the [[Nasal]] documentation, to make it hopefully more comprehensive and more accessible to new programmers. If you think, anything is unclear or missing, please leave a remark at the article's talk page or [http://flightgear.org/forums/viewtopic.php?f=30&t=13811 the forum topic].

===New articles===
*The article about [[altitude]] has received an update and a fresh lick of paint. Please help to correct the German version.
*[[Aircraft speed]] is a bit more up-to speed now.
*Places to fly, Suggested Flights, Suggested Flights from newsletters and the flights from the main website have all been merged into one gathering place of amazing places you really have to visit one day, soon. Check out [[Suggested Flights]] and feel free to add your secret pearls!

===New aircraft articles===
===Most popular newsletters===

== Community news ==
===Reminder: FSweekend===
A team of FlightGear developers will promote FlightGear to the public at the [[FSweekend]] (5 and 6 November 2011), the largest flight simulator event in the world. They highly appreciate it if you are able to stop by. If you are unable to visit [[Lelystad Airport]] (EHLE) in real life, make sure you pay a virtual visit!

A visit is definitely worth it. The more knowing that Durk Talsma, one of our longtime core developers, will do a one hour presentation on FlightGear.

[[File:Fgfs-screen-028.png|x125px]][[File:FSweekend_banner_2011.jpg|x125px|link=http://www.fsweekend.com]]

More information can be found at the event's wiki page: [[FSweekend 2011]].

=== FlightGear on YouTube ===
Vodoun da Vinci has [http://flightgear.org/forums/viewtopic.php?f=19&t=13823 uploaded a new movie] complete with music soundtrack to demonstrate the latest [[Bombable]] addon. This one primarily features head on attacks by custom [[P-51D Mustang]]s over Sochi, Russia.

The code in the Mustangs has been hacked to make them aggressive in attacking head on. My favorite style with my FW-190 D9 Dora supplied by Detlef Faber. The clips have been recorded with time set to evening and morning (dusk and dawn) as this provides the kind of dark and contrasting sky that best suits me for hunting.

=== FlightGear on Facebook ===
Started in December 2010, [http://www.facebook.com/FlightGear the FlightGear Facebook page] welcomed its 6000th "liker" on October 7! The original plan was to outnumber the likers of [[Pro Flight Simulator]] and the like, but now that we've outnumbered them by far, the Facebook page can be seen as a way to provide a periodic dose of what's new, cool or fun in FlightGear. Over the past months, we've been frequently posting nice screenshots from forummembers.

Speaking of which, [http://flightgear.org/forums the forum] is still the place to be when you're looking for support.

=== New tutorials and screencasts ===
[http://icestar-fghangar.web44.net/web/ Icecode's and Star's hangar] which was created on February 2011, is now bringing a new [http://icestar-fghangar.web44.net/web/?q=node/51 Tutorials section] where a new tutorial will be uploaded each week (sometimes more often). Starting with this week's tutorial "[http://icestar-fghangar.web44.net/web/?q=node/54 VOR navigation]". The tutorials are not going to be only limited on how to fly aircrafts but also we'll be showing you tips on how to develop aircrafts, scenery, liveries and many other things. Have fun reading and enjoy your flights!

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== FlightGear in the news==
FlightGear was featured in the October edition of [http://microsim.over-blog.com/ MicroSim], a French flight simulation magazine. The two paged article (click images below to open larger versions) discussed our latest release 2.4.0. Altough MSFS and X-Plane have better graphics and more complete aircraft, the writer considers FlightGear a worthwhile alternative.

The next edition of MicroSim will include a tutorial, to guide new users through the program.

[[File:MicroSim_oct2011_1.png|300px]]
[[File:MicroSim_oct2011_2.png|286px]]

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
*[[Translation requests| To '''translate''' (wiki) we must '''translate translate'''!]] so, Help and translate [[Translation requests| translate]] Wenn Sie Aus Deutschland sind or Jeśli jesteś z Polski, and from anywhere!
**Special thanks to Alexmdv and Michat for their translation work! (And Hamster and so many others)

* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can comment on the newsletter in the [http://www.flightgear.org/forums/viewforum.php?f=50 forums]? Help us improve *your* newsletter! Give comments, suggestions and feedback!

[[Category:FlightGear Newsletter]]

File:Fgfs 2011-10-16 04-35-08-94.jpg

2011-10-30T13:56:11Z

Ot-666: Short version of the Volvo-FM airport fuel truck.

Short version of the Volvo-FM airport fuel truck.

File:Fgfs 2011-10-26 20-46-13-55.jpg

2011-10-30T13:54:37Z

Ot-666: ULD Container trailer linup (some loaded with AKH ULD)

ULD Container trailer linup (some loaded with AKH ULD)

FlightGear Newsletter October 2011

2011-10-30T13:51:54Z

Ot-666: /* Scenery corner */

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== FGdata split ===
A team of developers started preparing the FlightGear [[git]] repositories for a significant change. Aircraft will be split of from fgdata, in order to ease development of aircraft and data as a whole. At the moment (of publication of this newsletter) we're in the testing phase; inviting anyone to test out the new system and report any bugs, comments and questions.

We would like to emphasize that those testing repositories are not meant to replace the "old" fgdata yet!

Details can be found on the special wiki page: [[FlightGear Git: splitting fgdata]].

=== Move to CMake ===



=== New Replay System ===
The [[Instant Replay]] system has received a major overhaul. The existing system worked well with specific types of aircraft only, since it relied on a hard-coded set of properties to be recorded/replayed, mainly covering propeller aircraft. Jet engines (thrust-reversers, N1/N2 rpm), or non-standard gears (i.e. a Concorde with 4 landing gears) were not working well though. The new system can be adapted to any kind of aircraft and any kind of custom property or animation.

[[File:FG-instant-replay-new.png|thumb|500px|The new instant replay dialog.]]

Most obvious change is probably an improved replay dialog: the video player-like GUI provides play/pause/skip buttons and also controls replay speed. During replay use the 4 arrow keys as controls (left/right to skip, up/down to speed-up/slow-down). Also new: ''slow-motion playback'' is now supported!

Another new feature is the option of taking controls at any point during replay. Use the ''Instant Replay'' to go back in time, then hit the "My controls!" button to regain controls and continue the flight from the current position. You may find this to be useful to train particular flight phases, such as flying the same approach again and again, maybe using different weather/wind conditions. Even if you messed up an approach: go back, try again, until you're getting better! :) Currently this particular feature is only available for YASim aircraft - except helicopters. JSBSim support is likely to be available soon.

The first step to adapt an aircraft to the improved recording system is to pick one of the ready-to-use configuration files, depending on aircraft/engine/.. type. The configuration file only needs to be included in the aircraft's ...-set.xml file. As an optional second step, you can add more custom properties to cover aircraft-specific effects. For more details, see the [https://www.gitorious.org/fg/fgdata/blobs/master/Docs/README.flightrecorder README.flightrecorder] in the fgdata/Docs folder.

A few adapted aircraft examples showing different levels of customization are already present in current git/fgdata:
* ASK13 (glider)
* c172p (propeller/piston)
* b1900d (turboprop)
* UH-1 (helicopter)
* 777-200ER (jet).

Furthermore, the replay system's buffers are now fully configurable (see /sim/replay/buffer properties). If you have enough memory, you could increase the buffer recording durations and rates.

Work on the replay system isn't finished yet. However, have a test flight with the current state in current git ;-).

=== The bombable addon has been updated ===
[[File:bombable4_4_800.png]]

Flug's [[Bombable]] addon received a number of major updates, among them:

* '''AI aircraft move vertically -- and do loops''': AI aircraft now move much more realistically in the vertical direction. They do loops, dive, and all the rest. Their behavior (climb rates, dive rates, and so on) matches those of the corresponding FG aircraft. This makes for a much more realistic 3-D dogfighting experience in FlightGear.
* '''Realistic roll rates for AI aircraft''': Roll rates are one the most important factors determining the effectiveness of fighter aircraft-- aircraft that can roll faster can turn faster. Now the roll rate for AI aircraft in scenarios can be customized, and bugs in the roll & turn routines for AI aircraft have been fixed.
* '''Significant performance improvements''': Bombable now makes much less of an impact on your framerate, and much less stuttering & slowdown at key points, like when numerous machine gun rounds are impacting.
* '''Damage impact detection is the most advanced element in Bombable'''. It is greatly improved over FG's native impact detection system, and the framework is in place for further refinements or as a model for FG to implement more refined impact detection internally. Damage tracking and communication over Multiplayer works well in a very lightweight with a very low data rate. However, only a general damage percentage is tracked and communicated. Damage to different locations or systems is not simulated. Proof of concept for explosions, fires, weapons damage animations, and crash animations is in place. All these elements could be refined for greater realism.
* '''Relocate any scenario to your location''': Have an AI scenario based in San Francisco, but want to fly in London? No problem, just hit a button in the Bombable menu and your scenario comes to you, wherever you are. Damage levels for AI aircraft and objects are re-set. It's like loading a new scenario without having to re-start FlightGear.
* '''Re-spawn AI aircraft and objects''': After you have shot down (or been shot down by!) AI aircraft or objects in scenarios, you can instantly re-spawn them and try again. (Available in the Bombable menu.)

The last two are kind of game changers--it's like being able to re-start/re-load a scenario instantly without having to re-start FG.

In addition, there have been some feature requests to make the bombable addon more challenging by improving its AI. This spawned an interesting discussion about possible ways to make the AI even smarter than it is already [http://flightgear.org/forums/viewtopic.php?f=6&t=5742&start=300#p140013]. Also see [[Howto: Neural networks in Nasal]].

For a nice video demo created by Vodoun da Vinci, please see [[FlightGear Newsletter October 2011#Community news|community news]].

== Interview with a contributor: Gijs de Rooy ==
''From this month onwards, we'd like to see a monthly interview with a contributor. Questions are available on [[interview questions]] and anyone is free to write an interview (with him-/herself) for next month's newsletter!''

* '''How long have you been involved in FlightGear? What was it that made you join?'''
According to the forum software I joined all the way back in July 2007. One year earlier I was one of the first users of Google SketchUp, free 3D modelling software. After modelling several buildings in my home town, Amsterdam (and placing them in Google Earth) I started working on Amsterdam Airport Schiphol. By then, Google Earth had a (simple) built-in flight simulator. Amsterdam would be the first airport to be modelled especially for that, that was my plan at least...

While modelling Schiphol, I stumbled across this free flight sim, called FlightGear, that wasn't a game, unlike Google's. In [http://flightgear.org/forums/viewtopic.php?f=5&t=473 one of my first posts] on the FlightGear forum I asked for someone to place my models into FlightGear's scenery. Georg (Heliflyer) placed my first buildings. I took some effort, but I finally managed to place buildings myself. Sadly the guy that introduced me to FlightGear and gave me a hobby that would last up till today, passed away in 2009.

* '''Do you have real world connections with aviation or IT?'''
Since two months I'm studying Aerospace Engineering at the University of Delft. So far I really like this mix of hobby and study.

* '''What are your major interests in FlightGear?'''
One of the things I like about FlightGear is the wide range of things one can get involved with: modelling, texturing, writing manuals, collecting data etc. and of course flying itself. Therefore I have a very long list of interests. However, there are three key parts that I particularly enjoy; being the development of scenery and aircraft and helping others by writing wiki articles and replying to questions at the forum.

* '''What project(s) are you working on right now?'''
My main development projects right now are the Boeing [[747-400]] and Dutch scenery. Both can be considered as never finished; there are always things to add/improve.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
Until this year I spent roughly 4 to 5 hours a day on FlightGear related things. Now that I'm studying I have less free time, but still several hours a day on average. Most of that time is taken up by non-development stuff, like the forum, wiki and livery database. Over the years I've been spending way too litle time on the actual flying.

* '''What do you plan on doing in the future?'''
I would really like to bring the 744 to a state where a real pilot cannot spot a thing that is missing in the simulation.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Starting something new is easy, completing it is much harder. I could have never guessed I would still be working on the 744, three years after I started!

I've always been telling newcomers to start improving existing features. It's a great way to familiarize yourself with the project. By looking into existing aircraft's files for example, you will quickly find out how those files are linked together and what their purpose is.

== Snapshot releases ==

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
=== New aircraft ===

=== Updated aircraft ===
The [[Learjet 35-A]] has been updated. Several minor errors have been fixed and improvements have been put in-place. The [[Learjet 35-A]] is the only business jet with a functional autopilot. It is a gem to fly and perfect for beginners and experts to try [[radio navigation]], autopilot control and [[ILS]] procedures. Thanks Xsaint and PH-JBO for the work done.

=== Livery database reaches 600 ===
On October 8, the [[FlightGear livery database]] welcomed its 600th livery! Thanks to 70 authors, the virtual skies are more colourful than ever.

At the moment the contribution system is being rewritten. For the time being, new liveries are only accepted via direct email to [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs].

== Scenery corner ==

=== Support for 8.50 airport data ===
[[File:EHAM_overview_night.png|thumb|270px|[[Amsterdam Airport Schiphol]] by night, with the new 8.50 lighting.]]
[[File:EHAM_gate_D.png|thumb|270px|Schiphol's D gates, in combination with AI traffic.]]
As mentioned in the previous newsletter; efforts are made to bring [[TerraGear]] up to a level where it supports the 8.50 apt.dat format, nowadays used by X-Plane. This new format has all kind of exciting features like curved taxiways and accurate lining/lighting (not just "ordinary" taxiway lines, but also markings like hold lines). Furthermore, seperate runway end definitions so it is now possible to create runways with different markings on both ends (including "empty ends" for runways being only used into one direction).

We'd like to thank Christian (papillon81), Pete (Psadro GM) and Emmilian (i4dnf) for their hard work. It's probably legitimate to say that this is the biggest improvements in FlightGear scenery over the past years!

=== Airports ===

Work progressed on a line of higher detailed service vehicle scenery models.
[[File:Fgfs 2011-10-29 13-41-16-88.jpg|400px|Service vehicles lineup]][[File:Fgfs 2011-10-23 18-02-20-12.jpg|400px|Baggege trailer lineup]]]

Currently the line includes a small tow truck, Baggage trailer, ULD container trailers, Catering Trucks and a Fuel Truck.

You can follow the development on the forum: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=13472]

== Aircraft of the month ==

Diamond DA42 Twin Star

[[File:Fgfs-screen-032.png|600px]]

http://en.wikipedia.org/wiki/Diamond_DA42

== Glider of the month ==

Jean Astir Grob G102

[[File:Astir.png|600px]]
[[File:Fgfs-screen-026.png|600px]]

== Airport of the month ==
[[File:FJDG.jpg|600px]]

The nearest airport is about 700 NM away. Around us are about 30 small islands, none with [[radio beacons]], none with an airport but some with a small beach. This Airport has four odd looking pillboxes. If you click they will open, very slowly. Now if you would have a [[Northrop B-2 Spirit |B2 bomber]] you could park your aircraft in it. If you don't have a [[Northrop B-2 Spirit|B2]] you are allowed to land, but only in an emergency. Fake an emergency and get here, bring piña colada and have a party on the beach!

*It is sooo beautiful here. Oh, where? FJDG, [http://en.wikipedia.org/wiki/Chagos_Archipelago Diego Garcia at Point Marianne]. Perfect for [[VFR]] tours, and a piña colada on the beach.

== Screenshot of the month ==
[[File:Mount Everest VNTR.jpg]]
*[[Learjet 35-A]] and [http://en.wikipedia.org/wiki/Mount_Everest Mount Everest] viewed from West towards East. Atlas image of the route to [http://en.wikipedia.org/wiki/Tumlingtar_Airport VNTR]. I could see the direction of NDB and knew the altitude of the RW. The RW was not visible till the absolute last moment racing down with airbrakes at max. The landing was a success but I had to change underwear and clean the seat.

== Suggested flights ==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
=== 10,000,000 pageviews ===
On October 29, the FlightGear wiki welcomed it's 10,000,000th (10 millionth) pageview! Coming from five million in October 2010, we doubled in just 12 months time. That is a proof that FlightGear has more users than ever and more users are able to find their way to the wiki. Both things are very nice of course!

We'd like to thank everyone that donated some free time to create/improve/correct articles and upload images to the wiki. As the wiki is (just like FlightGear) completely dependant on the community we'd like to emphasize that anyone is welcome to help! You can find a short introduction to the wiki at [[Help:Your first article]].

To 20 million and beyond! We're already well on our way, with {{NUMBEROFVIEWS}} views at this very moment. More statistics are available at [[Special:Statistics]].

=== Nasal documentation ===
Flug and Hooray revamped the [[Nasal]] documentation, to make it hopefully more comprehensive and more accessible to new programmers. If you think, anything is unclear or missing, please leave a remark at the article's talk page or [http://flightgear.org/forums/viewtopic.php?f=30&t=13811 the forum topic].

===New articles===
*The article about [[altitude]] has received an update and a fresh lick of paint. Please help to correct the German version.
*[[Aircraft speed]] is a bit more up-to speed now.
*Places to fly, Suggested Flights, Suggested Flights from newsletters and the flights from the main website have all been merged into one gathering place of amazing places you really have to visit one day, soon. Check out [[Suggested Flights]] and feel free to add your secret pearls!

===New aircraft articles===
===Most popular newsletters===

== Community news ==
===Reminder: FSweekend===
A team of FlightGear developers will promote FlightGear to the public at the [[FSweekend]] (5 and 6 November 2011), the largest flight simulator event in the world. They highly appreciate it if you are able to stop by. If you are unable to visit [[Lelystad Airport]] (EHLE) in real life, make sure you pay a virtual visit!

A visit is definitely worth it. The more knowing that Durk Talsma, one of our longtime core developers, will do a one hour presentation on FlightGear.

[[File:Fgfs-screen-028.png|x125px]][[File:FSweekend_banner_2011.jpg|x125px|link=http://www.fsweekend.com]]

More information can be found at the event's wiki page: [[FSweekend 2011]].

=== FlightGear on YouTube ===
Vodoun da Vinci has [http://flightgear.org/forums/viewtopic.php?f=19&t=13823 uploaded a new movie] complete with music soundtrack to demonstrate the latest [[Bombable]] addon. This one primarily features head on attacks by custom [[P-51D Mustang]]s over Sochi, Russia.

The code in the Mustangs has been hacked to make them aggressive in attacking head on. My favorite style with my FW-190 D9 Dora supplied by Detlef Faber. The clips have been recorded with time set to evening and morning (dusk and dawn) as this provides the kind of dark and contrasting sky that best suits me for hunting.

=== FlightGear on Facebook ===
Started in December 2010, [http://www.facebook.com/FlightGear the FlightGear Facebook page] welcomed its 6000th "liker" on October 7! The original plan was to outnumber the likers of [[Pro Flight Simulator]] and the like, but now that we've outnumbered them by far, the Facebook page can be seen as a way to provide a periodic dose of what's new, cool or fun in FlightGear. Over the past months, we've been frequently posting nice screenshots from forummembers.

Speaking of which, [http://flightgear.org/forums the forum] is still the place to be when you're looking for support.

=== New tutorials and screencasts ===
[http://icestar-fghangar.web44.net/web/ Icecode's and Star's hangar] which was created on February 2011, is now bringing a new [http://icestar-fghangar.web44.net/web/?q=node/51 Tutorials section] where a new tutorial will be uploaded each week (sometimes more often). Starting with this week's tutorial "[http://icestar-fghangar.web44.net/web/?q=node/54 VOR navigation]". The tutorials are not going to be only limited on how to fly aircrafts but also we'll be showing you tips on how to develop aircrafts, scenery, liveries and many other things. Have fun reading and enjoy your flights!

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== FlightGear in the news==
FlightGear was featured in the October edition of [http://microsim.over-blog.com/ MicroSim], a French flight simulation magazine. The two paged article (click images below to open larger versions) discussed our latest release 2.4.0. Altough MSFS and X-Plane have better graphics and more complete aircraft, the writer considers FlightGear a worthwhile alternative.

The next edition of MicroSim will include a tutorial, to guide new users through the program.

[[File:MicroSim_oct2011_1.png|300px]]
[[File:MicroSim_oct2011_2.png|286px]]

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
*[[Translation requests| To '''translate''' (wiki) we must '''translate translate'''!]] so, Help and translate [[Translation requests| translate]] Wenn Sie Aus Deutschland sind or Jeśli jesteś z Polski, and from anywhere!
**Special thanks to Alexmdv and Michat for their translation work! (And Hamster and so many others)

* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can comment on the newsletter in the [http://www.flightgear.org/forums/viewforum.php?f=50 forums]? Help us improve *your* newsletter! Give comments, suggestions and feedback!

[[Category:FlightGear Newsletter]]

FlightGear Newsletter October 2011

2011-10-30T13:50:18Z

Ot-666: /* Scenery corner */

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== FGdata split ===
A team of developers started preparing the FlightGear [[git]] repositories for a significant change. Aircraft will be split of from fgdata, in order to ease development of aircraft and data as a whole. At the moment (of publication of this newsletter) we're in the testing phase; inviting anyone to test out the new system and report any bugs, comments and questions.

We would like to emphasize that those testing repositories are not meant to replace the "old" fgdata yet!

Details can be found on the special wiki page: [[FlightGear Git: splitting fgdata]].

=== Move to CMake ===



=== New Replay System ===
The [[Instant Replay]] system has received a major overhaul. The existing system worked well with specific types of aircraft only, since it relied on a hard-coded set of properties to be recorded/replayed, mainly covering propeller aircraft. Jet engines (thrust-reversers, N1/N2 rpm), or non-standard gears (i.e. a Concorde with 4 landing gears) were not working well though. The new system can be adapted to any kind of aircraft and any kind of custom property or animation.

[[File:FG-instant-replay-new.png|thumb|500px|The new instant replay dialog.]]

Most obvious change is probably an improved replay dialog: the video player-like GUI provides play/pause/skip buttons and also controls replay speed. During replay use the 4 arrow keys as controls (left/right to skip, up/down to speed-up/slow-down). Also new: ''slow-motion playback'' is now supported!

Another new feature is the option of taking controls at any point during replay. Use the ''Instant Replay'' to go back in time, then hit the "My controls!" button to regain controls and continue the flight from the current position. You may find this to be useful to train particular flight phases, such as flying the same approach again and again, maybe using different weather/wind conditions. Even if you messed up an approach: go back, try again, until you're getting better! :) Currently this particular feature is only available for YASim aircraft - except helicopters. JSBSim support is likely to be available soon.

The first step to adapt an aircraft to the improved recording system is to pick one of the ready-to-use configuration files, depending on aircraft/engine/.. type. The configuration file only needs to be included in the aircraft's ...-set.xml file. As an optional second step, you can add more custom properties to cover aircraft-specific effects. For more details, see the [https://www.gitorious.org/fg/fgdata/blobs/master/Docs/README.flightrecorder README.flightrecorder] in the fgdata/Docs folder.

A few adapted aircraft examples showing different levels of customization are already present in current git/fgdata:
* ASK13 (glider)
* c172p (propeller/piston)
* b1900d (turboprop)
* UH-1 (helicopter)
* 777-200ER (jet).

Furthermore, the replay system's buffers are now fully configurable (see /sim/replay/buffer properties). If you have enough memory, you could increase the buffer recording durations and rates.

Work on the replay system isn't finished yet. However, have a test flight with the current state in current git ;-).

=== The bombable addon has been updated ===
[[File:bombable4_4_800.png]]

Flug's [[Bombable]] addon received a number of major updates, among them:

* '''AI aircraft move vertically -- and do loops''': AI aircraft now move much more realistically in the vertical direction. They do loops, dive, and all the rest. Their behavior (climb rates, dive rates, and so on) matches those of the corresponding FG aircraft. This makes for a much more realistic 3-D dogfighting experience in FlightGear.
* '''Realistic roll rates for AI aircraft''': Roll rates are one the most important factors determining the effectiveness of fighter aircraft-- aircraft that can roll faster can turn faster. Now the roll rate for AI aircraft in scenarios can be customized, and bugs in the roll & turn routines for AI aircraft have been fixed.
* '''Significant performance improvements''': Bombable now makes much less of an impact on your framerate, and much less stuttering & slowdown at key points, like when numerous machine gun rounds are impacting.
* '''Damage impact detection is the most advanced element in Bombable'''. It is greatly improved over FG's native impact detection system, and the framework is in place for further refinements or as a model for FG to implement more refined impact detection internally. Damage tracking and communication over Multiplayer works well in a very lightweight with a very low data rate. However, only a general damage percentage is tracked and communicated. Damage to different locations or systems is not simulated. Proof of concept for explosions, fires, weapons damage animations, and crash animations is in place. All these elements could be refined for greater realism.
* '''Relocate any scenario to your location''': Have an AI scenario based in San Francisco, but want to fly in London? No problem, just hit a button in the Bombable menu and your scenario comes to you, wherever you are. Damage levels for AI aircraft and objects are re-set. It's like loading a new scenario without having to re-start FlightGear.
* '''Re-spawn AI aircraft and objects''': After you have shot down (or been shot down by!) AI aircraft or objects in scenarios, you can instantly re-spawn them and try again. (Available in the Bombable menu.)

The last two are kind of game changers--it's like being able to re-start/re-load a scenario instantly without having to re-start FG.

In addition, there have been some feature requests to make the bombable addon more challenging by improving its AI. This spawned an interesting discussion about possible ways to make the AI even smarter than it is already [http://flightgear.org/forums/viewtopic.php?f=6&t=5742&start=300#p140013]. Also see [[Howto: Neural networks in Nasal]].

For a nice video demo created by Vodoun da Vinci, please see [[FlightGear Newsletter October 2011#Community news|community news]].

== Interview with a contributor: Gijs de Rooy ==
''From this month onwards, we'd like to see a monthly interview with a contributor. Questions are available on [[interview questions]] and anyone is free to write an interview (with him-/herself) for next month's newsletter!''

* '''How long have you been involved in FlightGear? What was it that made you join?'''
According to the forum software I joined all the way back in July 2007. One year earlier I was one of the first users of Google SketchUp, free 3D modelling software. After modelling several buildings in my home town, Amsterdam (and placing them in Google Earth) I started working on Amsterdam Airport Schiphol. By then, Google Earth had a (simple) built-in flight simulator. Amsterdam would be the first airport to be modelled especially for that, that was my plan at least...

While modelling Schiphol, I stumbled across this free flight sim, called FlightGear, that wasn't a game, unlike Google's. In [http://flightgear.org/forums/viewtopic.php?f=5&t=473 one of my first posts] on the FlightGear forum I asked for someone to place my models into FlightGear's scenery. Georg (Heliflyer) placed my first buildings. I took some effort, but I finally managed to place buildings myself. Sadly the guy that introduced me to FlightGear and gave me a hobby that would last up till today, passed away in 2009.

* '''Do you have real world connections with aviation or IT?'''
Since two months I'm studying Aerospace Engineering at the University of Delft. So far I really like this mix of hobby and study.

* '''What are your major interests in FlightGear?'''
One of the things I like about FlightGear is the wide range of things one can get involved with: modelling, texturing, writing manuals, collecting data etc. and of course flying itself. Therefore I have a very long list of interests. However, there are three key parts that I particularly enjoy; being the development of scenery and aircraft and helping others by writing wiki articles and replying to questions at the forum.

* '''What project(s) are you working on right now?'''
My main development projects right now are the Boeing [[747-400]] and Dutch scenery. Both can be considered as never finished; there are always things to add/improve.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
Until this year I spent roughly 4 to 5 hours a day on FlightGear related things. Now that I'm studying I have less free time, but still several hours a day on average. Most of that time is taken up by non-development stuff, like the forum, wiki and livery database. Over the years I've been spending way too litle time on the actual flying.

* '''What do you plan on doing in the future?'''
I would really like to bring the 744 to a state where a real pilot cannot spot a thing that is missing in the simulation.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Starting something new is easy, completing it is much harder. I could have never guessed I would still be working on the 744, three years after I started!

I've always been telling newcomers to start improving existing features. It's a great way to familiarize yourself with the project. By looking into existing aircraft's files for example, you will quickly find out how those files are linked together and what their purpose is.

== Snapshot releases ==

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
=== New aircraft ===

=== Updated aircraft ===
The [[Learjet 35-A]] has been updated. Several minor errors have been fixed and improvements have been put in-place. The [[Learjet 35-A]] is the only business jet with a functional autopilot. It is a gem to fly and perfect for beginners and experts to try [[radio navigation]], autopilot control and [[ILS]] procedures. Thanks Xsaint and PH-JBO for the work done.

=== Livery database reaches 600 ===
On October 8, the [[FlightGear livery database]] welcomed its 600th livery! Thanks to 70 authors, the virtual skies are more colourful than ever.

At the moment the contribution system is being rewritten. For the time being, new liveries are only accepted via direct email to [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs].

== Scenery corner ==

=== Support for 8.50 airport data ===
[[File:EHAM_overview_night.png|thumb|270px|[[Amsterdam Airport Schiphol]] by night, with the new 8.50 lighting.]]
[[File:EHAM_gate_D.png|thumb|270px|Schiphol's D gates, in combination with AI traffic.]]
As mentioned in the previous newsletter; efforts are made to bring [[TerraGear]] up to a level where it supports the 8.50 apt.dat format, nowadays used by X-Plane. This new format has all kind of exciting features like curved taxiways and accurate lining/lighting (not just "ordinary" taxiway lines, but also markings like hold lines). Furthermore, seperate runway end definitions so it is now possible to create runways with different markings on both ends (including "empty ends" for runways being only used into one direction).

We'd like to thank Christian (papillon81), Pete (Psadro GM) and Emmilian (i4dnf) for their hard work. It's probably legitimate to say that this is the biggest improvements in FlightGear scenery over the past years!

=== Airports ===

Work progressed on a line of higher detailed service vehicle scenery models.
[[File:Fgfs 2011-10-29 13-41-16-88.jpg|600px|Service vehicles lineup]][[File:Fgfs 2011-10-23 18-02-20-12.jpg|600px]]

Currently the line includes a small tow truck, Baggage trailer, ULD container trailers, Catering Trucks and a Fuel Truck.

You can follow the development on the forum: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=13472]

== Aircraft of the month ==

Diamond DA42 Twin Star

[[File:Fgfs-screen-032.png|600px]]

http://en.wikipedia.org/wiki/Diamond_DA42

== Glider of the month ==

Jean Astir Grob G102

[[File:Astir.png|600px]]
[[File:Fgfs-screen-026.png|600px]]

== Airport of the month ==
[[File:FJDG.jpg|600px]]

The nearest airport is about 700 NM away. Around us are about 30 small islands, none with [[radio beacons]], none with an airport but some with a small beach. This Airport has four odd looking pillboxes. If you click they will open, very slowly. Now if you would have a [[Northrop B-2 Spirit |B2 bomber]] you could park your aircraft in it. If you don't have a [[Northrop B-2 Spirit|B2]] you are allowed to land, but only in an emergency. Fake an emergency and get here, bring piña colada and have a party on the beach!

*It is sooo beautiful here. Oh, where? FJDG, [http://en.wikipedia.org/wiki/Chagos_Archipelago Diego Garcia at Point Marianne]. Perfect for [[VFR]] tours, and a piña colada on the beach.

== Screenshot of the month ==
[[File:Mount Everest VNTR.jpg]]
*[[Learjet 35-A]] and [http://en.wikipedia.org/wiki/Mount_Everest Mount Everest] viewed from West towards East. Atlas image of the route to [http://en.wikipedia.org/wiki/Tumlingtar_Airport VNTR]. I could see the direction of NDB and knew the altitude of the RW. The RW was not visible till the absolute last moment racing down with airbrakes at max. The landing was a success but I had to change underwear and clean the seat.

== Suggested flights ==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
=== 10,000,000 pageviews ===
On October 29, the FlightGear wiki welcomed it's 10,000,000th (10 millionth) pageview! Coming from five million in October 2010, we doubled in just 12 months time. That is a proof that FlightGear has more users than ever and more users are able to find their way to the wiki. Both things are very nice of course!

We'd like to thank everyone that donated some free time to create/improve/correct articles and upload images to the wiki. As the wiki is (just like FlightGear) completely dependant on the community we'd like to emphasize that anyone is welcome to help! You can find a short introduction to the wiki at [[Help:Your first article]].

To 20 million and beyond! We're already well on our way, with {{NUMBEROFVIEWS}} views at this very moment. More statistics are available at [[Special:Statistics]].

=== Nasal documentation ===
Flug and Hooray revamped the [[Nasal]] documentation, to make it hopefully more comprehensive and more accessible to new programmers. If you think, anything is unclear or missing, please leave a remark at the article's talk page or [http://flightgear.org/forums/viewtopic.php?f=30&t=13811 the forum topic].

===New articles===
*The article about [[altitude]] has received an update and a fresh lick of paint. Please help to correct the German version.
*[[Aircraft speed]] is a bit more up-to speed now.
*Places to fly, Suggested Flights, Suggested Flights from newsletters and the flights from the main website have all been merged into one gathering place of amazing places you really have to visit one day, soon. Check out [[Suggested Flights]] and feel free to add your secret pearls!

===New aircraft articles===
===Most popular newsletters===

== Community news ==
===Reminder: FSweekend===
A team of FlightGear developers will promote FlightGear to the public at the [[FSweekend]] (5 and 6 November 2011), the largest flight simulator event in the world. They highly appreciate it if you are able to stop by. If you are unable to visit [[Lelystad Airport]] (EHLE) in real life, make sure you pay a virtual visit!

A visit is definitely worth it. The more knowing that Durk Talsma, one of our longtime core developers, will do a one hour presentation on FlightGear.

[[File:Fgfs-screen-028.png|x125px]][[File:FSweekend_banner_2011.jpg|x125px|link=http://www.fsweekend.com]]

More information can be found at the event's wiki page: [[FSweekend 2011]].

=== FlightGear on YouTube ===
Vodoun da Vinci has [http://flightgear.org/forums/viewtopic.php?f=19&t=13823 uploaded a new movie] complete with music soundtrack to demonstrate the latest [[Bombable]] addon. This one primarily features head on attacks by custom [[P-51D Mustang]]s over Sochi, Russia.

The code in the Mustangs has been hacked to make them aggressive in attacking head on. My favorite style with my FW-190 D9 Dora supplied by Detlef Faber. The clips have been recorded with time set to evening and morning (dusk and dawn) as this provides the kind of dark and contrasting sky that best suits me for hunting.

=== FlightGear on Facebook ===
Started in December 2010, [http://www.facebook.com/FlightGear the FlightGear Facebook page] welcomed its 6000th "liker" on October 7! The original plan was to outnumber the likers of [[Pro Flight Simulator]] and the like, but now that we've outnumbered them by far, the Facebook page can be seen as a way to provide a periodic dose of what's new, cool or fun in FlightGear. Over the past months, we've been frequently posting nice screenshots from forummembers.

Speaking of which, [http://flightgear.org/forums the forum] is still the place to be when you're looking for support.

=== New tutorials and screencasts ===
[http://icestar-fghangar.web44.net/web/ Icecode's and Star's hangar] which was created on February 2011, is now bringing a new [http://icestar-fghangar.web44.net/web/?q=node/51 Tutorials section] where a new tutorial will be uploaded each week (sometimes more often). Starting with this week's tutorial "[http://icestar-fghangar.web44.net/web/?q=node/54 VOR navigation]". The tutorials are not going to be only limited on how to fly aircrafts but also we'll be showing you tips on how to develop aircrafts, scenery, liveries and many other things. Have fun reading and enjoy your flights!

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== FlightGear in the news==
FlightGear was featured in the October edition of [http://microsim.over-blog.com/ MicroSim], a French flight simulation magazine. The two paged article (click images below to open larger versions) discussed our latest release 2.4.0. Altough MSFS and X-Plane have better graphics and more complete aircraft, the writer considers FlightGear a worthwhile alternative.

The next edition of MicroSim will include a tutorial, to guide new users through the program.

[[File:MicroSim_oct2011_1.png|300px]]
[[File:MicroSim_oct2011_2.png|286px]]

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
*[[Translation requests| To '''translate''' (wiki) we must '''translate translate'''!]] so, Help and translate [[Translation requests| translate]] Wenn Sie Aus Deutschland sind or Jeśli jesteś z Polski, and from anywhere!
**Special thanks to Alexmdv and Michat for their translation work! (And Hamster and so many others)

* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can comment on the newsletter in the [http://www.flightgear.org/forums/viewforum.php?f=50 forums]? Help us improve *your* newsletter! Give comments, suggestions and feedback!

[[Category:FlightGear Newsletter]]

FlightGear Newsletter October 2011

2011-10-30T13:43:19Z

Ot-666: /* Scenery corner */

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== FGdata split ===
A team of developers started preparing the FlightGear [[git]] repositories for a significant change. Aircraft will be split of from fgdata, in order to ease development of aircraft and data as a whole. At the moment (of publication of this newsletter) we're in the testing phase; inviting anyone to test out the new system and report any bugs, comments and questions.

We would like to emphasize that those testing repositories are not meant to replace the "old" fgdata yet!

Details can be found on the special wiki page: [[FlightGear Git: splitting fgdata]].

=== Move to CMake ===



=== New Replay System ===
The [[Instant Replay]] system has received a major overhaul. The existing system worked well with specific types of aircraft only, since it relied on a hard-coded set of properties to be recorded/replayed, mainly covering propeller aircraft. Jet engines (thrust-reversers, N1/N2 rpm), or non-standard gears (i.e. a Concorde with 4 landing gears) were not working well though. The new system can be adapted to any kind of aircraft and any kind of custom property or animation.

[[File:FG-instant-replay-new.png|thumb|500px|The new instant replay dialog.]]

Most obvious change is probably an improved replay dialog: the video player-like GUI provides play/pause/skip buttons and also controls replay speed. During replay use the 4 arrow keys as controls (left/right to skip, up/down to speed-up/slow-down). Also new: ''slow-motion playback'' is now supported!

Another new feature is the option of taking controls at any point during replay. Use the ''Instant Replay'' to go back in time, then hit the "My controls!" button to regain controls and continue the flight from the current position. You may find this to be useful to train particular flight phases, such as flying the same approach again and again, maybe using different weather/wind conditions. Even if you messed up an approach: go back, try again, until you're getting better! :) Currently this particular feature is only available for YASim aircraft - except helicopters. JSBSim support is likely to be available soon.

The first step to adapt an aircraft to the improved recording system is to pick one of the ready-to-use configuration files, depending on aircraft/engine/.. type. The configuration file only needs to be included in the aircraft's ...-set.xml file. As an optional second step, you can add more custom properties to cover aircraft-specific effects. For more details, see the [https://www.gitorious.org/fg/fgdata/blobs/master/Docs/README.flightrecorder README.flightrecorder] in the fgdata/Docs folder.

A few adapted aircraft examples showing different levels of customization are already present in current git/fgdata:
* ASK13 (glider)
* c172p (propeller/piston)
* b1900d (turboprop)
* UH-1 (helicopter)
* 777-200ER (jet).

Furthermore, the replay system's buffers are now fully configurable (see /sim/replay/buffer properties). If you have enough memory, you could increase the buffer recording durations and rates.

Work on the replay system isn't finished yet. However, have a test flight with the current state in current git ;-).

=== The bombable addon has been updated ===
[[File:bombable4_4_800.png]]

Flug's [[Bombable]] addon received a number of major updates, among them:

* '''AI aircraft move vertically -- and do loops''': AI aircraft now move much more realistically in the vertical direction. They do loops, dive, and all the rest. Their behavior (climb rates, dive rates, and so on) matches those of the corresponding FG aircraft. This makes for a much more realistic 3-D dogfighting experience in FlightGear.
* '''Realistic roll rates for AI aircraft''': Roll rates are one the most important factors determining the effectiveness of fighter aircraft-- aircraft that can roll faster can turn faster. Now the roll rate for AI aircraft in scenarios can be customized, and bugs in the roll & turn routines for AI aircraft have been fixed.
* '''Significant performance improvements''': Bombable now makes much less of an impact on your framerate, and much less stuttering & slowdown at key points, like when numerous machine gun rounds are impacting.
* '''Damage impact detection is the most advanced element in Bombable'''. It is greatly improved over FG's native impact detection system, and the framework is in place for further refinements or as a model for FG to implement more refined impact detection internally. Damage tracking and communication over Multiplayer works well in a very lightweight with a very low data rate. However, only a general damage percentage is tracked and communicated. Damage to different locations or systems is not simulated. Proof of concept for explosions, fires, weapons damage animations, and crash animations is in place. All these elements could be refined for greater realism.
* '''Relocate any scenario to your location''': Have an AI scenario based in San Francisco, but want to fly in London? No problem, just hit a button in the Bombable menu and your scenario comes to you, wherever you are. Damage levels for AI aircraft and objects are re-set. It's like loading a new scenario without having to re-start FlightGear.
* '''Re-spawn AI aircraft and objects''': After you have shot down (or been shot down by!) AI aircraft or objects in scenarios, you can instantly re-spawn them and try again. (Available in the Bombable menu.)

The last two are kind of game changers--it's like being able to re-start/re-load a scenario instantly without having to re-start FG.

In addition, there have been some feature requests to make the bombable addon more challenging by improving its AI. This spawned an interesting discussion about possible ways to make the AI even smarter than it is already [http://flightgear.org/forums/viewtopic.php?f=6&t=5742&start=300#p140013]. Also see [[Howto: Neural networks in Nasal]].

For a nice video demo created by Vodoun da Vinci, please see [[FlightGear Newsletter October 2011#Community news|community news]].

== Interview with a contributor: Gijs de Rooy ==
''From this month onwards, we'd like to see a monthly interview with a contributor. Questions are available on [[interview questions]] and anyone is free to write an interview (with him-/herself) for next month's newsletter!''

* '''How long have you been involved in FlightGear? What was it that made you join?'''
According to the forum software I joined all the way back in July 2007. One year earlier I was one of the first users of Google SketchUp, free 3D modelling software. After modelling several buildings in my home town, Amsterdam (and placing them in Google Earth) I started working on Amsterdam Airport Schiphol. By then, Google Earth had a (simple) built-in flight simulator. Amsterdam would be the first airport to be modelled especially for that, that was my plan at least...

While modelling Schiphol, I stumbled across this free flight sim, called FlightGear, that wasn't a game, unlike Google's. In [http://flightgear.org/forums/viewtopic.php?f=5&t=473 one of my first posts] on the FlightGear forum I asked for someone to place my models into FlightGear's scenery. Georg (Heliflyer) placed my first buildings. I took some effort, but I finally managed to place buildings myself. Sadly the guy that introduced me to FlightGear and gave me a hobby that would last up till today, passed away in 2009.

* '''Do you have real world connections with aviation or IT?'''
Since two months I'm studying Aerospace Engineering at the University of Delft. So far I really like this mix of hobby and study.

* '''What are your major interests in FlightGear?'''
One of the things I like about FlightGear is the wide range of things one can get involved with: modelling, texturing, writing manuals, collecting data etc. and of course flying itself. Therefore I have a very long list of interests. However, there are three key parts that I particularly enjoy; being the development of scenery and aircraft and helping others by writing wiki articles and replying to questions at the forum.

* '''What project(s) are you working on right now?'''
My main development projects right now are the Boeing [[747-400]] and Dutch scenery. Both can be considered as never finished; there are always things to add/improve.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
Until this year I spent roughly 4 to 5 hours a day on FlightGear related things. Now that I'm studying I have less free time, but still several hours a day on average. Most of that time is taken up by non-development stuff, like the forum, wiki and livery database. Over the years I've been spending way too litle time on the actual flying.

* '''What do you plan on doing in the future?'''
I would really like to bring the 744 to a state where a real pilot cannot spot a thing that is missing in the simulation.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Starting something new is easy, completing it is much harder. I could have never guessed I would still be working on the 744, three years after I started!

I've always been telling newcomers to start improving existing features. It's a great way to familiarize yourself with the project. By looking into existing aircraft's files for example, you will quickly find out how those files are linked together and what their purpose is.

== Snapshot releases ==

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
=== New aircraft ===

=== Updated aircraft ===
The [[Learjet 35-A]] has been updated. Several minor errors have been fixed and improvements have been put in-place. The [[Learjet 35-A]] is the only business jet with a functional autopilot. It is a gem to fly and perfect for beginners and experts to try [[radio navigation]], autopilot control and [[ILS]] procedures. Thanks Xsaint and PH-JBO for the work done.

=== Livery database reaches 600 ===
On October 8, the [[FlightGear livery database]] welcomed its 600th livery! Thanks to 70 authors, the virtual skies are more colourful than ever.

At the moment the contribution system is being rewritten. For the time being, new liveries are only accepted via direct email to [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs].

== Scenery corner ==

=== Support for 8.50 airport data ===
[[File:EHAM_overview_night.png|thumb|270px|[[Amsterdam Airport Schiphol]] by night, with the new 8.50 lighting.]]
[[File:EHAM_gate_D.png|thumb|270px|Schiphol's D gates, in combination with AI traffic.]]
As mentioned in the previous newsletter; efforts are made to bring [[TerraGear]] up to a level where it supports the 8.50 apt.dat format, nowadays used by X-Plane. This new format has all kind of exciting features like curved taxiways and accurate lining/lighting (not just "ordinary" taxiway lines, but also markings like hold lines). Furthermore, seperate runway end definitions so it is now possible to create runways with different markings on both ends (including "empty ends" for runways being only used into one direction).

We'd like to thank Christian (papillon81), Pete (Psadro GM) and Emmilian (i4dnf) for their hard work. It's probably legitimate to say that this is the biggest improvements in FlightGear scenery over the past years!

=== Airports ===

Work progressed on a line of higher detailed service vehicle scenery models.
[[File:Fgfs 2011-10-29 13-41-16-88.jpg|thumb|270px|Service vehicles lineup]]

Currently the line includes a small tow truck, Baggage trailer, ULD container trailers, Catering Trucks and a Fuel Truck.

You can follow the development on the forum: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=13472]

== Aircraft of the month ==

Diamond DA42 Twin Star

[[File:Fgfs-screen-032.png|600px]]

http://en.wikipedia.org/wiki/Diamond_DA42

== Glider of the month ==

Jean Astir Grob G102

[[File:Astir.png|600px]]
[[File:Fgfs-screen-026.png|600px]]

== Airport of the month ==
[[File:FJDG.jpg|600px]]

The nearest airport is about 700 NM away. Around us are about 30 small islands, none with [[radio beacons]], none with an airport but some with a small beach. This Airport has four odd looking pillboxes. If you click they will open, very slowly. Now if you would have a [[Northrop B-2 Spirit |B2 bomber]] you could park your aircraft in it. If you don't have a [[Northrop B-2 Spirit|B2]] you are allowed to land, but only in an emergency. Fake an emergency and get here, bring piña colada and have a party on the beach!

*It is sooo beautiful here. Oh, where? FJDG, [http://en.wikipedia.org/wiki/Chagos_Archipelago Diego Garcia at Point Marianne]. Perfect for [[VFR]] tours, and a piña colada on the beach.

== Screenshot of the month ==
[[File:Mount Everest VNTR.jpg]]
*[[Learjet 35-A]] and [http://en.wikipedia.org/wiki/Mount_Everest Mount Everest] viewed from West towards East. Atlas image of the route to [http://en.wikipedia.org/wiki/Tumlingtar_Airport VNTR]. I could see the direction of NDB and knew the altitude of the RW. The RW was not visible till the absolute last moment racing down with airbrakes at max. The landing was a success but I had to change underwear and clean the seat.

== Suggested flights ==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
=== 10,000,000 pageviews ===
On October 29, the FlightGear wiki welcomed it's 10,000,000th (10 millionth) pageview! Coming from five million in October 2010, we doubled in just 12 months time. That is a proof that FlightGear has more users than ever and more users are able to find their way to the wiki. Both things are very nice of course!

We'd like to thank everyone that donated some free time to create/improve/correct articles and upload images to the wiki. As the wiki is (just like FlightGear) completely dependant on the community we'd like to emphasize that anyone is welcome to help! You can find a short introduction to the wiki at [[Help:Your first article]].

To 20 million and beyond! We're already well on our way, with {{NUMBEROFVIEWS}} views at this very moment. More statistics are available at [[Special:Statistics]].

=== Nasal documentation ===
Flug and Hooray revamped the [[Nasal]] documentation, to make it hopefully more comprehensive and more accessible to new programmers. If you think, anything is unclear or missing, please leave a remark at the article's talk page or [http://flightgear.org/forums/viewtopic.php?f=30&t=13811 the forum topic].

===New articles===
*The article about [[altitude]] has received an update and a fresh lick of paint. Please help to correct the German version.
*[[Aircraft speed]] is a bit more up-to speed now.
*Places to fly, Suggested Flights, Suggested Flights from newsletters and the flights from the main website have all been merged into one gathering place of amazing places you really have to visit one day, soon. Check out [[Suggested Flights]] and feel free to add your secret pearls!

===New aircraft articles===
===Most popular newsletters===

== Community news ==
===Reminder: FSweekend===
A team of FlightGear developers will promote FlightGear to the public at the [[FSweekend]] (5 and 6 November 2011), the largest flight simulator event in the world. They highly appreciate it if you are able to stop by. If you are unable to visit [[Lelystad Airport]] (EHLE) in real life, make sure you pay a virtual visit!

A visit is definitely worth it. The more knowing that Durk Talsma, one of our longtime core developers, will do a one hour presentation on FlightGear.

[[File:Fgfs-screen-028.png|x125px]][[File:FSweekend_banner_2011.jpg|x125px|link=http://www.fsweekend.com]]

More information can be found at the event's wiki page: [[FSweekend 2011]].

=== FlightGear on YouTube ===
Vodoun da Vinci has [http://flightgear.org/forums/viewtopic.php?f=19&t=13823 uploaded a new movie] complete with music soundtrack to demonstrate the latest [[Bombable]] addon. This one primarily features head on attacks by custom [[P-51D Mustang]]s over Sochi, Russia.

The code in the Mustangs has been hacked to make them aggressive in attacking head on. My favorite style with my FW-190 D9 Dora supplied by Detlef Faber. The clips have been recorded with time set to evening and morning (dusk and dawn) as this provides the kind of dark and contrasting sky that best suits me for hunting.

=== FlightGear on Facebook ===
Started in December 2010, [http://www.facebook.com/FlightGear the FlightGear Facebook page] welcomed its 6000th "liker" on October 7! The original plan was to outnumber the likers of [[Pro Flight Simulator]] and the like, but now that we've outnumbered them by far, the Facebook page can be seen as a way to provide a periodic dose of what's new, cool or fun in FlightGear. Over the past months, we've been frequently posting nice screenshots from forummembers.

Speaking of which, [http://flightgear.org/forums the forum] is still the place to be when you're looking for support.

=== New tutorials and screencasts ===
[http://icestar-fghangar.web44.net/web/ Icecode's and Star's hangar] which was created on February 2011, is now bringing a new [http://icestar-fghangar.web44.net/web/?q=node/51 Tutorials section] where a new tutorial will be uploaded each week (sometimes more often). Starting with this week's tutorial "[http://icestar-fghangar.web44.net/web/?q=node/54 VOR navigation]". The tutorials are not going to be only limited on how to fly aircrafts but also we'll be showing you tips on how to develop aircrafts, scenery, liveries and many other things. Have fun reading and enjoy your flights!

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== FlightGear in the news==
FlightGear was featured in the October edition of [http://microsim.over-blog.com/ MicroSim], a French flight simulation magazine. The two paged article (click images below to open larger versions) discussed our latest release 2.4.0. Altough MSFS and X-Plane have better graphics and more complete aircraft, the writer considers FlightGear a worthwhile alternative.

The next edition of MicroSim will include a tutorial, to guide new users through the program.

[[File:MicroSim_oct2011_1.png|300px]]
[[File:MicroSim_oct2011_2.png|286px]]

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
*[[Translation requests| To '''translate''' (wiki) we must '''translate translate'''!]] so, Help and translate [[Translation requests| translate]] Wenn Sie Aus Deutschland sind or Jeśli jesteś z Polski, and from anywhere!
**Special thanks to Alexmdv and Michat for their translation work! (And Hamster and so many others)

* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can comment on the newsletter in the [http://www.flightgear.org/forums/viewforum.php?f=50 forums]? Help us improve *your* newsletter! Give comments, suggestions and feedback!

[[Category:FlightGear Newsletter]]

File:Fgfs 2011-10-23 18-02-20-12.jpg

2011-10-30T13:40:40Z

Ot-666: Volk DFZ30NT tow truck & baggage trailers

Volk DFZ30NT tow truck & baggage trailers

File:Fgfs 2011-10-29 13-41-16-88.jpg

2011-10-30T13:33:19Z

Ot-666: Lineup of higher detialed aiport service vehicles.

Lineup of higher detialed aiport service vehicles.

FlightGear Newsletter October 2011

2011-10-30T13:28:53Z

Ot-666: /* Scenery corner */

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== FGdata split ===
A team of developers started preparing the FlightGear [[git]] repositories for a significant change. Aircraft will be split of from fgdata, in order to ease development of aircraft and data as a whole. At the moment (of publication of this newsletter) we're in the testing phase; inviting anyone to test out the new system and report any bugs, comments and questions.

We would like to emphasize that those testing repositories are not meant to replace the "old" fgdata yet!

Details can be found on the special wiki page: [[FlightGear Git: splitting fgdata]].

=== Move to CMake ===



=== New Replay System ===
The [[Instant Replay]] system has received a major overhaul. The existing system worked well with specific types of aircraft only, since it relied on a hard-coded set of properties to be recorded/replayed, mainly covering propeller aircraft. Jet engines (thrust-reversers, N1/N2 rpm), or non-standard gears (i.e. a Concorde with 4 landing gears) were not working well though. The new system can be adapted to any kind of aircraft and any kind of custom property or animation.

[[File:FG-instant-replay-new.png|thumb|500px|The new instant replay dialog.]]

Most obvious change is probably an improved replay dialog: the video player-like GUI provides play/pause/skip buttons and also controls replay speed. During replay use the 4 arrow keys as controls (left/right to skip, up/down to speed-up/slow-down). Also new: ''slow-motion playback'' is now supported!

Another new feature is the option of taking controls at any point during replay. Use the ''Instant Replay'' to go back in time, then hit the "My controls!" button to regain controls and continue the flight from the current position. You may find this to be useful to train particular flight phases, such as flying the same approach again and again, maybe using different weather/wind conditions. Even if you messed up an approach: go back, try again, until you're getting better! :) Currently this particular feature is only available for YASim aircraft - except helicopters. JSBSim support is likely to be available soon.

The first step to adapt an aircraft to the improved recording system is to pick one of the ready-to-use configuration files, depending on aircraft/engine/.. type. The configuration file only needs to be included in the aircraft's ...-set.xml file. As an optional second step, you can add more custom properties to cover aircraft-specific effects. For more details, see the [https://www.gitorious.org/fg/fgdata/blobs/master/Docs/README.flightrecorder README.flightrecorder] in the fgdata/Docs folder.

A few adapted aircraft examples showing different levels of customization are already present in current git/fgdata:
* ASK13 (glider)
* c172p (propeller/piston)
* b1900d (turboprop)
* UH-1 (helicopter)
* 777-200ER (jet).

Furthermore, the replay system's buffers are now fully configurable (see /sim/replay/buffer properties). If you have enough memory, you could increase the buffer recording durations and rates.

Work on the replay system isn't finished yet. However, have a test flight with the current state in current git ;-).

=== The bombable addon has been updated ===
[[File:bombable4_4_800.png]]

Flug's [[Bombable]] addon received a number of major updates, among them:

* '''AI aircraft move vertically -- and do loops''': AI aircraft now move much more realistically in the vertical direction. They do loops, dive, and all the rest. Their behavior (climb rates, dive rates, and so on) matches those of the corresponding FG aircraft. This makes for a much more realistic 3-D dogfighting experience in FlightGear.
* '''Realistic roll rates for AI aircraft''': Roll rates are one the most important factors determining the effectiveness of fighter aircraft-- aircraft that can roll faster can turn faster. Now the roll rate for AI aircraft in scenarios can be customized, and bugs in the roll & turn routines for AI aircraft have been fixed.
* '''Significant performance improvements''': Bombable now makes much less of an impact on your framerate, and much less stuttering & slowdown at key points, like when numerous machine gun rounds are impacting.
* '''Damage impact detection is the most advanced element in Bombable'''. It is greatly improved over FG's native impact detection system, and the framework is in place for further refinements or as a model for FG to implement more refined impact detection internally. Damage tracking and communication over Multiplayer works well in a very lightweight with a very low data rate. However, only a general damage percentage is tracked and communicated. Damage to different locations or systems is not simulated. Proof of concept for explosions, fires, weapons damage animations, and crash animations is in place. All these elements could be refined for greater realism.
* '''Relocate any scenario to your location''': Have an AI scenario based in San Francisco, but want to fly in London? No problem, just hit a button in the Bombable menu and your scenario comes to you, wherever you are. Damage levels for AI aircraft and objects are re-set. It's like loading a new scenario without having to re-start FlightGear.
* '''Re-spawn AI aircraft and objects''': After you have shot down (or been shot down by!) AI aircraft or objects in scenarios, you can instantly re-spawn them and try again. (Available in the Bombable menu.)

The last two are kind of game changers--it's like being able to re-start/re-load a scenario instantly without having to re-start FG.

In addition, there have been some feature requests to make the bombable addon more challenging by improving its AI. This spawned an interesting discussion about possible ways to make the AI even smarter than it is already [http://flightgear.org/forums/viewtopic.php?f=6&t=5742&start=300#p140013]. Also see [[Howto: Neural networks in Nasal]].

For a nice video demo created by Vodoun da Vinci, please see [[FlightGear Newsletter October 2011#Community news|community news]].

== Interview with a contributor: Gijs de Rooy ==
''From this month onwards, we'd like to see a monthly interview with a contributor. Questions are available on [[interview questions]] and anyone is free to write an interview (with him-/herself) for next month's newsletter!''

* '''How long have you been involved in FlightGear? What was it that made you join?'''
According to the forum software I joined all the way back in July 2007. One year earlier I was one of the first users of Google SketchUp, free 3D modelling software. After modelling several buildings in my home town, Amsterdam (and placing them in Google Earth) I started working on Amsterdam Airport Schiphol. By then, Google Earth had a (simple) built-in flight simulator. Amsterdam would be the first airport to be modelled especially for that, that was my plan at least...

While modelling Schiphol, I stumbled across this free flight sim, called FlightGear, that wasn't a game, unlike Google's. In [http://flightgear.org/forums/viewtopic.php?f=5&t=473 one of my first posts] on the FlightGear forum I asked for someone to place my models into FlightGear's scenery. Georg (Heliflyer) placed my first buildings. I took some effort, but I finally managed to place buildings myself. Sadly the guy that introduced me to FlightGear and gave me a hobby that would last up till today, passed away in 2009.

* '''Do you have real world connections with aviation or IT?'''
Since two months I'm studying Aerospace Engineering at the University of Delft. So far I really like this mix of hobby and study.

* '''What are your major interests in FlightGear?'''
One of the things I like about FlightGear is the wide range of things one can get involved with: modelling, texturing, writing manuals, collecting data etc. and of course flying itself. Therefore I have a very long list of interests. However, there are three key parts that I particularly enjoy; being the development of scenery and aircraft and helping others by writing wiki articles and replying to questions at the forum.

* '''What project(s) are you working on right now?'''
My main development projects right now are the Boeing [[747-400]] and Dutch scenery. Both can be considered as never finished; there are always things to add/improve.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
Until this year I spent roughly 4 to 5 hours a day on FlightGear related things. Now that I'm studying I have less free time, but still several hours a day on average. Most of that time is taken up by non-development stuff, like the forum, wiki and livery database. Over the years I've been spending way too litle time on the actual flying.

* '''What do you plan on doing in the future?'''
I would really like to bring the 744 to a state where a real pilot cannot spot a thing that is missing in the simulation.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Starting something new is easy, completing it is much harder. I could have never guessed I would still be working on the 744, three years after I started!

I've always been telling newcomers to start improving existing features. It's a great way to familiarize yourself with the project. By looking into existing aircraft's files for example, you will quickly find out how those files are linked together and what their purpose is.

== Snapshot releases ==

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
=== New aircraft ===

=== Updated aircraft ===
The [[Learjet 35-A]] has been updated. Several minor errors have been fixed and improvements have been put in-place. The [[Learjet 35-A]] is the only business jet with a functional autopilot. It is a gem to fly and perfect for beginners and experts to try [[radio navigation]], autopilot control and [[ILS]] procedures. Thanks Xsaint and PH-JBO for the work done.

=== Livery database reaches 600 ===
On October 8, the [[FlightGear livery database]] welcomed its 600th livery! Thanks to 70 authors, the virtual skies are more colourful than ever.

At the moment the contribution system is being rewritten. For the time being, new liveries are only accepted via direct email to [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs].

== Scenery corner ==

=== Support for 8.50 airport data ===
[[File:EHAM_overview_night.png|thumb|270px|[[Amsterdam Airport Schiphol]] by night, with the new 8.50 lighting.]]
[[File:EHAM_gate_D.png|thumb|270px|Schiphol's D gates, in combination with AI traffic.]]
As mentioned in the previous newsletter; efforts are made to bring [[TerraGear]] up to a level where it supports the 8.50 apt.dat format, nowadays used by X-Plane. This new format has all kind of exciting features like curved taxiways and accurate lining/lighting (not just "ordinary" taxiway lines, but also markings like hold lines). Furthermore, seperate runway end definitions so it is now possible to create runways with different markings on both ends (including "empty ends" for runways being only used into one direction).

We'd like to thank Christian (papillon81), Pete (Psadro GM) and Emmilian (i4dnf) for their hard work. It's probably legitimate to say that this is the biggest improvements in FlightGear scenery over the past years!

=== Airports ===

Work progressed on a line of higher detailed service vehicle scenery models.

Currently the line includes a small tow truck, Baggage trailer, ULD container trailers, Catering Trucks and a Fuel Truck.

You can follow the development on the forum: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=13472]

== Aircraft of the month ==

Diamond DA42 Twin Star

[[File:Fgfs-screen-032.png|600px]]

http://en.wikipedia.org/wiki/Diamond_DA42

== Glider of the month ==

Jean Astir Grob G102

[[File:Astir.png|600px]]
[[File:Fgfs-screen-026.png|600px]]

== Airport of the month ==
[[File:FJDG.jpg|600px]]

The nearest airport is about 700 NM away. Around us are about 30 small islands, none with [[radio beacons]], none with an airport but some with a small beach. This Airport has four odd looking pillboxes. If you click they will open, very slowly. Now if you would have a [[Northrop B-2 Spirit |B2 bomber]] you could park your aircraft in it. If you don't have a [[Northrop B-2 Spirit|B2]] you are allowed to land, but only in an emergency. Fake an emergency and get here, bring piña colada and have a party on the beach!

*It is sooo beautiful here. Oh, where? FJDG, [http://en.wikipedia.org/wiki/Chagos_Archipelago Diego Garcia at Point Marianne]. Perfect for [[VFR]] tours, and a piña colada on the beach.

== Screenshot of the month ==
[[File:Mount Everest VNTR.jpg]]
*[[Learjet 35-A]] and [http://en.wikipedia.org/wiki/Mount_Everest Mount Everest] viewed from West towards East. Atlas image of the route to [http://en.wikipedia.org/wiki/Tumlingtar_Airport VNTR]. I could see the direction of NDB and knew the altitude of the RW. The RW was not visible till the absolute last moment racing down with airbrakes at max. The landing was a success but I had to change underwear and clean the seat.

== Suggested flights ==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
=== 10,000,000 pageviews ===
On October 29, the FlightGear wiki welcomed it's 10,000,000th (10 millionth) pageview! Coming from five million in October 2010, we doubled in just 12 months time. That is a proof that FlightGear has more users than ever and more users are able to find their way to the wiki. Both things are very nice of course!

We'd like to thank everyone that donated some free time to create/improve/correct articles and upload images to the wiki. As the wiki is (just like FlightGear) completely dependant on the community we'd like to emphasize that anyone is welcome to help! You can find a short introduction to the wiki at [[Help:Your first article]].

To 20 million and beyond! We're already well on our way, with {{NUMBEROFVIEWS}} views at this very moment. More statistics are available at [[Special:Statistics]].

=== Nasal documentation ===
Flug and Hooray revamped the [[Nasal]] documentation, to make it hopefully more comprehensive and more accessible to new programmers. If you think, anything is unclear or missing, please leave a remark at the article's talk page or [http://flightgear.org/forums/viewtopic.php?f=30&t=13811 the forum topic].

===New articles===
*The article about [[altitude]] has received an update and a fresh lick of paint. Please help to correct the German version.
*[[Aircraft speed]] is a bit more up-to speed now.
*Places to fly, Suggested Flights, Suggested Flights from newsletters and the flights from the main website have all been merged into one gathering place of amazing places you really have to visit one day, soon. Check out [[Suggested Flights]] and feel free to add your secret pearls!

===New aircraft articles===
===Most popular newsletters===

== Community news ==
===Reminder: FSweekend===
A team of FlightGear developers will promote FlightGear to the public at the [[FSweekend]] (5 and 6 November 2011), the largest flight simulator event in the world. They highly appreciate it if you are able to stop by. If you are unable to visit [[Lelystad Airport]] (EHLE) in real life, make sure you pay a virtual visit!

A visit is definitely worth it. The more knowing that Durk Talsma, one of our longtime core developers, will do a one hour presentation on FlightGear.

[[File:Fgfs-screen-028.png|x125px]][[File:FSweekend_banner_2011.jpg|x125px|link=http://www.fsweekend.com]]

More information can be found at the event's wiki page: [[FSweekend 2011]].

=== FlightGear on YouTube ===
Vodoun da Vinci has [http://flightgear.org/forums/viewtopic.php?f=19&t=13823 uploaded a new movie] complete with music soundtrack to demonstrate the latest [[Bombable]] addon. This one primarily features head on attacks by custom [[P-51D Mustang]]s over Sochi, Russia.

The code in the Mustangs has been hacked to make them aggressive in attacking head on. My favorite style with my FW-190 D9 Dora supplied by Detlef Faber. The clips have been recorded with time set to evening and morning (dusk and dawn) as this provides the kind of dark and contrasting sky that best suits me for hunting.

=== FlightGear on Facebook ===
Started in December 2010, [http://www.facebook.com/FlightGear the FlightGear Facebook page] welcomed its 6000th "liker" on October 7! The original plan was to outnumber the likers of [[Pro Flight Simulator]] and the like, but now that we've outnumbered them by far, the Facebook page can be seen as a way to provide a periodic dose of what's new, cool or fun in FlightGear. Over the past months, we've been frequently posting nice screenshots from forummembers.

Speaking of which, [http://flightgear.org/forums the forum] is still the place to be when you're looking for support.

=== New tutorials and screencasts ===
[http://icestar-fghangar.web44.net/web/ Icecode's and Star's hangar] which was created on February 2011, is now bringing a new [http://icestar-fghangar.web44.net/web/?q=node/51 Tutorials section] where a new tutorial will be uploaded each week (sometimes more often). Starting with this week's tutorial "[http://icestar-fghangar.web44.net/web/?q=node/54 VOR navigation]". The tutorials are not going to be only limited on how to fly aircrafts but also we'll be showing you tips on how to develop aircrafts, scenery, liveries and many other things. Have fun reading and enjoy your flights!

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== FlightGear in the news==
FlightGear was featured in the October edition of [http://microsim.over-blog.com/ MicroSim], a French flight simulation magazine. The two paged article (click images below to open larger versions) discussed our latest release 2.4.0. Altough MSFS and X-Plane have better graphics and more complete aircraft, the writer considers FlightGear a worthwhile alternative.

The next edition of MicroSim will include a tutorial, to guide new users through the program.

[[File:MicroSim_oct2011_1.png|300px]]
[[File:MicroSim_oct2011_2.png|286px]]

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
*[[Translation requests| To '''translate''' (wiki) we must '''translate translate'''!]] so, Help and translate [[Translation requests| translate]] Wenn Sie Aus Deutschland sind or Jeśli jesteś z Polski, and from anywhere!
**Special thanks to Alexmdv and Michat for their translation work! (And Hamster and so many others)

* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can comment on the newsletter in the [http://www.flightgear.org/forums/viewforum.php?f=50 forums]? Help us improve *your* newsletter! Give comments, suggestions and feedback!

[[Category:FlightGear Newsletter]]

FlightGear Newsletter February 2011

2011-02-28T12:01:05Z

Ot-666: /* Airports */

FlightGear Newsletter February 2011

2011-02-27T01:47:44Z

Ot-666: /* LOIU Innsbruck Hospital Heliport (Austria) */

FlightGear Newsletter February 2011

2011-02-27T01:46:42Z

Ot-666: /* LOWI Innsbruck Airport Hangar n1 - n3, n5 and Engine-test Building (Austria) */

FlightGear Newsletter February 2011

2011-02-27T01:45:42Z

Ot-666: /* Airports */

FlightGear Newsletter February 2011

2011-02-27T01:29:34Z

Ot-666: /* Airports */

FlightGear Newsletter February 2011

2011-02-27T01:25:42Z

Ot-666: /* Airports */

File:LOWI hangar 01-03.jpg

2011-02-27T01:11:47Z

Ot-666: LOWI airport hangar n1 - n3 and the engine test building.

LOWI airport hangar n1 - n3 and the engine test building.

File:LOWI hangar n1-n5 at night.jpg

2011-02-27T01:09:34Z

Ot-666: LOWI airport hangar n1 - n5 and the engine test building at night.

LOWI airport hangar n1 - n5 and the engine test building at night.

FlightGear Newsletter February 2011

2011-02-21T23:07:00Z

Ot-666: /* LOIU Innsbruck Hospital Heliport (Austria) */

FlightGear Newsletter February 2011

2011-02-21T23:05:03Z

Ot-666: /* LOIU Innsbruck Hospital Heliport (Austria) */

FlightGear Newsletter February 2011

2011-02-21T23:04:15Z

Ot-666: /* LOIU Innsbruck Hospital Heliport (Austria) */

FlightGear Newsletter February 2011

2011-02-21T23:00:11Z

Ot-666: /* Scenery corner */

File:LOIU Innsbruck Hospital Heliport.jpg

2011-02-21T22:54:14Z

Ot-666: This heliport is located on top of the main hospital building in Innsbruck, just a stone throw away from LOWI airport Austria and the LOJO oamtc helicopter base.

This heliport is located on top of the main hospital building in Innsbruck, just a stone throw away from LOWI airport Austria and the LOJO oamtc helicopter base.

FlightGear Newsletter November 2010

2010-11-30T22:59:55Z

Ot-666: /* Scenery corner */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== FlightGear events ==
== Call for volunteers ==
The [[OpenRadar]] project is looking for a new maintainer.

The [[TerraGear GUI]] project is looking for programmers to help create a GUI frontend for [[TerraGear]] [http://flightgear.org/forums/viewtopic.php?f=5&t=7485#p102005].

== Development news ==
Anders Gidenstam has continued to develop Walkview which opens up all sorts of exciting possibilites. Here is a short video of Walkview being used to give a different perspective on starting the Sopwith Camel [http://www.youtube.com/watch?v=KAQT2s7pFJs]. In addition to the rectangular plane that we have had for some time, we can now define the area in which we can "walk" as a line, polyline, or circle.

We use the new definitions in Multi Player Carrier Carl Vinson to move around the Goofer's deck while we are goofing, or to seek a more advantageous view from PriFly, or to inspect the Flight deck as the Flight Deck Officer, as seen in [http://www.youtube.com/watch?v=h9MUT7GfzBs this video].

Meanwhile, in other news, Tim Moore has fixed the condition tag in the Material Animation. We can combine these two facilites to generate some more interesting views - [http://www.youtube.com/watch?v=1YmJN9o6TBc]. Alexis Bory has said that he will see if he can produce some more models with which to populate the hangar. Let's hope he finds something!

== Shader requests ==
We have added a new page to the wiki titled [[shader requests]]. This is intended to provide a place for people to post ideas related to new shaders for use in FlightGear. But this is also meant to be place for aspiring shader developers to find interesting ideas for new shaders. In the past, these ideas were often spread over many different places, such as forum or mailing list discussions, and often ended up getting hidden rather quickly. So if you have ideas related to improving existing shaders or creating completely new ones, please add your ideas to the [[Shader requests]] page. And if you are aware of any ongoing shader development efforts, please also add those there. Consequently, if you want to get started creating shaders for FlightGear, please make sure to check out this page.

== Known problems ==
Though working perfectly for years, the "live weather" feature in FlightGear 1.9.x and 2.0 is now broken. Unfortunately, the FlightGear code of past releases contains minor problem which so far remained undetected and without effect. Since early November, probably caused by a server upgrade at the weather services, the FlightGear weather requests are now being rejected due to this problem. To revive live weather you have the following options:
* As a workaround, configure a proxy-server on the fgfs command-line. Relaying the request through a proxy solves the issue (see [http://www.flightgear.org/forums/viewtopic.php?t=10002 forum topic]).
** A description on "How To Fix (temporarily)" you can find under http://www.emmerich-j.de/FGFS/METAR-fix.html
* Experts being able to patch and recompile FlightGear may try to apply a patch (also see forum).
* Developers can use FlightGear's latest developer version from GIT, which already contains the required bugfix.
* Otherwise please stick with manual weather configuration and wait for the next FlightGear release (won't be too long).

== Nasal for newbies ==
== New software tools and projects ==

== FlightGear addons and mods ==
== In the hangar ==
=== New aircraft ===

====DC-8-63====
Isix and Armchair Ace have recently unveiled a DC-8-63. You can follow the progress on the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=10228 development thread].
[[File:Fgfs-screen-178.png|thumb|left|The DC-8-63 in KLM colours.]]
=== Updated aircraft ===

[[File:ZF_Navy_free_balloon-2.jpg|thumb|The ZF Navy free balloon with the envelope shader enabled.]]
====ZF Navy free balloon====
The [[ZF Navy free balloon]] has been updated with a custom shader effect that changes the shape of the balloon envelope according to its gas content.

====IAR 80====
The [[IAR_80|IAR 80]] beta has seen some updates, with new features added in the eyecandy department, as well as some refining of the [[Nasal_scripting_language|Nasal]] code and a revamped [[FDM]].

====Boeing 757 and 717====
[[User:Skyop|Skyop]] has picked up development of the [[Boeing 757-200]] and the [[Boeing 717]]. New features included generic autostart systems, improved models, new instruments and new [[YASim]] [[FDM]]s. New and improved cockpits and aircraft systems are planned. Skyop is requesting livery makers to start painting their favorite airlines and submitting their textures to the [http://liveries.flightgear.org official FlightGear livery database].

Follow further progress at the [http://flightgear.org/forums/viewtopic.php?t=9944 757-200 development thread] and the [http://flightgear.org/forums/viewtopic.php?t=6145 717 development thread].

====Boeing 777-200====
The [[Boeing_777-200|777-200ER]] received a cockpit and systems upgrade.
Extensions by Syd Adams and ThorstenB include better [[GPWS]] integration, improvements for cockpit instruments, sounds, textures, key/mouse bindings and many bug fixes.
The upgraded 777-200ER also features brake temperature monitoring.
Pilots are advised to also use spoilers and thrust-reversers for deceleration to avoid overheated brakes - especially when landing a heavily loaded plane.
The new auto spoilers, automatically deploying on touch-down when armed, provide some assistance here.

[[File:B777-200_RTO.jpg|thumb|Smoking brakes after a 777-200ER had to execute a rejected takeoff.
The airline declined to comment on the reason for the takeoff problem, but assured no one on board was injured.]]

====Douglas DC-8-73F====
[[File:DC8pit.png|thumb|left|The cockpit as it was on the 29th of November.]]
[[User:Armchair Ace|Armchair Ace]] has been developing the DC-8-73's cockpit, which has also been used in the new DC-8-63.

=== Liveries ===

==Scenery corner==
===New Bangkok International Airport===
[[File:VTBD_wip01.jpg|thumb|Bangkok Int'l Airport - work in progress.]]
Mike (aka D-Sky1) is busy again. This time he is working on Suvarnabhumi Airport (VTBD, also known as New Bangkok International Airport) in Thailand) as the architecture of the airport buildings is very beautiful. It will sure take some time but a first glance at the work in progress is already possible. Discuss the progress with us in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10075 the forum].
After the airport is finished, placed and available, AI traffic will follow (mainly Thai Airways).

AI traffic arrives at [[RPLL]] (Manila, Philippines): Mike created a comprehensive list of AI traffic of Cebu Pacific Airlines. Soon available via GIT, Cebu Pacific Airlines will provide domestic and international flights to the most important destinations. AI for the second big carrier of the Philippines (Philippine Airways) will follow later.

===Land cover updates===
Detailed land cover data for Vermont has been added to the map server. This state in the northeast United States will be a part of the next world scenery release.

Work continues on hand-created, detailed land cover data for northern Switzerland. Photos of landmark buildings or airport buildings in Switzerland would be welcome as we try to model this beautiful country.

===NASA Interactive Launch Complexes===
[[File:mercuryredstone3.png|thumb|Mercury Redstone 3 Rocket ready for launch.]]
Jack Mermod has released the first of many NASA Interactive Launch Complexes. This first release is based on Launch Complex 5 and the [http://en.wikipedia.org/wiki/Mercury-Redstone_3 Mercury-Redstone 3] launch. The model should be in the official database soon, for now you can download the scenery [http://alphashangar.co.nr/ here].

=== Jet d'Eau in Geneva ===
[[File:Geneva fountain.jpg|thumb|Jet d'Eau in Geneva.]]
The Jet d'Eau in Geneva is with 140m height a recognisable landmark. Ot-666 created the fountain and the pier it is located on in the Lake Geneva.
The model features night illumination for the fountain.

=== Airports ===
Looking for new airports to visit? Try a Dublin (EIDW) to Aalesund (ENSD) flight! These two airports, along with Sandane airport in Anda, Norway (ENVA), have recently had models added to the database to make them a more interesting place to fly.

===I.C.E.J.A.W===
[[File:ICEJAW_snowcover.jpg|thumb|Demonstration of ICEJAW depicting buildings with and without snow cover.]]
In an effort to improve the cities in FlightGear, Daniel Strawn (aka "Intel-Qube") has modeled a simple "one size fits all" city. Affectionately codenamed "ICEJAW", the city, still in development, features tangible helipads to land on, billboards and snow cover for heavy snow-fall.
Follow development in the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10016 forum topic].

=== TerraGear-CS ===
After attempts to provide a new World Scenery build in sync with the 2.0 software release failed miserably (due to software deficiencies), some effort has been expended into investigations, experiments (some of which ended up in filing bug-reports for related software) and large-scale tests for replacing the entire polygon processing in TerraGear by the use of [http://grass.osgeo.org/ GRASS GIS]. Just to give an idea about the term "large scale": The procedure to turn the Europe-wide CORINE CLC2000 vector data set into a topologically consistent coverage is taking several weeks on a 3 GHz Xeon machine.

The "*-decode" commands and old-style work directories are affected by this change as well as all polygon-mangling routines in "construct". The GRASS toolbox provides all the features we need for ''reliable'', topologically correct polygon handling (cleaning, clipping and the like). Those (early) steps of the new toolchain which have proven to be rather stable are available [http://mapserver.flightgear.org/git/?p=terragear-cs;a=tree;f=gisscripts here] (GRASS7 required for certain features).

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
A beautiful flight is from Prince George, ICAO: CYXS, to Calgary Springbank, ICAO: CYBW, under the route created by reed, which can be seen at [http://flightgear.org/forums/viewtopic.php?f=10&t=9772 the forums]

== Aircraft review ==
[[Image:Beechcraft_B1900D.JPG|thumb|Cockpit of the B1900D]]
The [[Beechcraft B1900D]] is a twin-engine turboprop aircraft, designed to be an all-weather regional airliner. It's been used by U.S. military and many other governments. In total, 695 very produced until 2002, and it's one of the default aircrafts in FlightGear and has been available since version 0.9.8.

With a well-implemented cockpit and fully functional GPS, it is one of the better developed aircraft within FlightGear.

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==

=== FSweekend ===
As in previous year's FlightGear organized a booth at the annual [[FSweekend]] event in Lelystad, the Netherlands. [[FSweekend 2010|This year's edition of FSweekend]] came and went by before we realized it. Although there was initially skepticism as to whether we would be able to top last year's presentation, we did so, by quite a large margin. Main attractions this year were our Thomas-Krenn sponsored server, driving 10 monitors, and our near continuous use of [[Anaglyph (3D)|anaglyphic 3D]]. Although we had considered it to be a neat gadget, running flightgear in 3D analglyphic mode turned out to be a brilliant move. Not only did it draw a lot of people to our booth who wanted to check it out, handing out 3D glasses also worked as an extremely good vehicle to start a conversation with them.

Some assorted highlights include:
*Our Thomas-Krenn AG machine has been running for 8 hours straight, on both days, without a single glitch. At one point Torsten ran out of fuel, because he hadn't realized that FlightGear had been running for so long continuously. The machine ran in three 3D mode most of the time, and the way the screens were set up gave the impression that the were just holes in a wall though which you could see a (virtual) reality known as FlightGear. Very nicely done.
*Very positive comments on the Lockheed Constellation's artwork, particularly because that model is really shining when presented in 3D (probably the best cockpit we have for a 3D demo).
*Also very postive comments on the advance copy of the 737NG (800) that Innis Cunningham sent me. Also in particular due to the fact that the switches on the overhead panel look very real in 3D.
*Booth members Gijs and Jorg trying to outperform each other in terms of their helicopter flying skills (trying to land it on a chimney, once they found the helipad to easy).
*A number of people claiming that our booth was the best one at FSWeekend this year.
*Our aerotowing demo involving all of our major demonstration machines (my machine as the glider, Jorg's computer as the tow plane, and our sponsor's machine as a joint (3D) model viewer.
*Some people just not believing that a single machine could drive 10 monitors and actively checking where all the monitor cables actually went to.
*Another opportunity to meet FlightGear developers (one expected encounter: Geoff McLane, and one totally unexpected meeting with Thorsten Brehm). Thanks guys for showing up!

And last, but not least, everybody involved in getting this year's booth organized. It's been a lot of fun. Some pictures of the event can be found [http://www.dropbox.com/gallery/7455889/1/FSWeekend2010?h=0e9825 here]

=== FlightGear on youtube ===
[http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=8726 Sealbhach] has made an [http://www.youtube.com/watch?v=zveiKtooXs0 excellent video] showcasing the great scenery at LOWI.

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===

== Useful links ==
== And finally ... ==
===A christmas present for you===
[[File:Gerbrandytoren_christmas.jpg|thumb|World's largest Christmas tree.]]
Do not forget to pay a visit to the [http://en.wikipedia.org/wiki/Gerbrandy_Tower Gerbrandytoren] in the Netherlands. With a height of 366.8m and 120 lights, it is the world's largest Christmas tree between December 11 and January 6. The tower is located 21 nm South East (HDG 120h) of [[Amsterdam Airport Schiphol]] ([http://mpmap02.flightgear.org/?ll=52.009982,5.053582&z=15 location on MPMap]).

=== Contributing ===
One of the regular thoughts expressed on the FlightGear forum is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

=== Amateur Built Collimated Display ===
''Contributed by Gene Buckle''

A couple of months ago, my friend Wayne and I embarked on the development of a fully functional collimated display system for our DIY flight simulators. A collimated display has been the holy grail of DIY cockpit builders because of the image it generates. Collimated displays are also known as "infinity" displays. It's described that way because the focus point to your eye becomes "infinity" when you're located at the right spot when viewing the mirror. The exact details of how they work are beyond this article, but you can learn more at [http://en.wikipedia.org/wiki/Full_flight_simulator Wikipedia]; see the section marked "Collimated Cross-Cockpit Displays".

Building the display successfully is a pretty big deal. Up until we completed the proof-of-concept project, collimated displays were the sole domain of multi-million dollar flight simulators from the likes of CAE, FlightSafety and others. It was declared too complex and too costly by just about everyone that ever approached the problem. Fortunately for us, all the "experts" were wrong. Not only did we build a fully functional collimating display, but we did it with off the shelf materials and very, very little expenditure. Total material costs for the mirror and projection screen is under $100.

The test mirror was built using an 8 foot diameter spherical shape. The framework itself describes a 60 degree wide by 40 degree high "slice" of that shape. The mirror itself is made of a 48" wide, 2mm thickness of Mylar sheet. In order to properly stretch the mirror, a set of "ears" had to be added to the framework.

This shows the frame prior to the mirror being glued into place:

[[File:mirror_frame.jpg|200px|Collimating Mirror Framework]]

The framework itself is made from 12mm Baltic Birch and is under 36" tall. The arcs defined by the "inside" ribs show where the spherical section mirror will form. In order to form the mirror, vacuum must be applied. This will stretch the mirror into a spherical section shape.

Attaching the Mylar:

[[File:attaching_mylar.jpg|200px|Attaching the Mylar to the framework]]

The Mylar is attached to the oval ring by a high-tack spray on adhesive made by 3M.

In order to test the visual properties of the system, we set it up on a platform I'd built some time ago to use with racing games:

[[File:mirror_test.jpg|200px|Test setup]]

The mirror just reflects what is on the screen above it - the test screen in this case is just a bit less than half the radius of the mirror and is 17" tall. In order to start testing as soon as possible, Wayne skinned the screen with kraft paper. It's very wrinkly, but it did an adequate job of being a screen. It's also what we had handy at the time. :)

Here's the complete test configuration:

[[file:test_config.jpg|200px|Test configuration]]

We used a Fein Turbo III dust collector as our vac source and it pulls the mirror down very well! It's pulling about 5 PSI in order to force the Mylar into the correct shape. Below is a picture of the mirror after being pulled down.

[[file:formed_mirror.jpg|200px|Formed mirror]]

Photographs and video cannot do this justice! It's just incredible to look at!

Here's a pic of Wayne performing the first test flight:

[[file:test_flight.jpg|200px|Test Flight]]

...and thus was born the world's very first amateur built fully collimated display for DIY flight simulators. I can't stress enough how thankful I am for Wayne and his skills. Were it not for his deep understanding of the math involved, this would have never been built.

Here are a few YouTube videos of the system in operation:
* [http://www.youtube.com/watch?v=y67TAo9Lv5g First draw down of the mirror]
* [http://www.youtube.com/watch?v=8yaDnXYlf8k My badly narrated test flight]
* [http://www.youtube.com/watch?v=zogFny49zrI A walk-around of the setup taken the next day]

The [http://www.diy-cockpits.org/coll/collimated_display.html project site] has more pictures and details on the current state of the project. Work has already begun on a 180 degree version!

=== Did you know ===
* You can act as an [[ATC|air traffic controller]] on the multiplayer servers by downloading the [[ATC-aircraft|ATC aircraft]]?
* That Luiz Jazbinsek, known as Cael in the FlightGear forums, is doing a [http://flightgear.org/forums/viewtopic.php?f=10&t=10126 world circumnavigation] with the [[Beechcraft B1900D]]?

[[Category:FlightGear Newsletter|2010 11]]

File:Geneva fountain.jpg

2010-11-29T22:21:49Z

Ot-666: The Jet d'Eau at the Lake Geneva.

The Jet d'Eau at the Lake Geneva.

FlightGear Newsletter November 2010

2010-11-29T21:07:51Z

Ot-666: /* Scenery corner */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== FlightGear events ==
== Call for volunteers ==
The [[OpenRadar]] project is looking for a new maintainer.

The [[TerraGear GUI]] project is looking for programmers to help create a GUI frontend for [[TerraGear]] [http://flightgear.org/forums/viewtopic.php?f=5&t=7485#p102005].

== Development news ==
Anders Gidenstam has continued to develop Walkview which opens up all sorts of exciting possibilites. Here is a short video of Walkview being used to give a different perspective on starting the Sopwith Camel [http://www.youtube.com/watch?v=KAQT2s7pFJs]. In addition to the rectangular plane that we have had for some time, we can now define the area in which we can "walk" as a line, polyline, or circle.

We use the new definitions in Multi Player Carrier Carl Vinson to move around the Goofer's deck while we are goofing, or to seek a more advantageous view from PriFly, or to inspect the Flight deck as the Flight Deck Officer, as seen in [http://www.youtube.com/watch?v=h9MUT7GfzBs this video].

Meanwhile, in other news, Tim Moore has fixed the condition tag in the Material Animation. We can combine these two facilites to generate some more interesting views - [http://www.youtube.com/watch?v=1YmJN9o6TBc]. Alexis Bory has said that he will see if he can produce some more models with which to populate the hangar. Let's hope he finds something!

== Shader requests ==
We have added a new page to the wiki titled [[shader requests]]. This is intended to provide a place for people to post ideas related to new shaders for use in FlightGear. But this is also meant to be place for aspiring shader developers to find interesting ideas for new shaders. In the past, these ideas were often spread over many different places, such as forum or mailing list discussions, and often ended up getting hidden rather quickly. So if you have ideas related to improving existing shaders or creating completely new ones, please add your ideas to the [[Shader requests]] page. And if you are aware of any ongoing shader development efforts, please also add those there. Consequently, if you want to get started creating shaders for FlightGear, please make sure to check out this page.

== Known problems ==
Though working perfectly for years, the "live weather" feature in FlightGear 1.9.x and 2.0 is now broken. Unfortunately, the FlightGear code of past releases contains minor problem which so far remained undetected and without effect. Since early November, probably caused by a server upgrade at the weather services, the FlightGear weather requests are now being rejected due to this problem. To revive live weather you have the following options:
* As a workaround, configure a proxy-server on the fgfs command-line. Relaying the request through a proxy solves the issue (see [http://www.flightgear.org/forums/viewtopic.php?t=10002 forum topic]).
** A description on "How To Fix (temporarily)" you can find under http://www.emmerich-j.de/FGFS/METAR-fix.html
* Experts being able to patch and recompile FlightGear may try to apply a patch (also see forum).
* Developers can use FlightGear's latest developer version from GIT, which already contains the required bugfix.
* Otherwise please stick with manual weather configuration and wait for the next FlightGear release (won't be too long).

== Nasal for newbies ==
== New software tools and projects ==

== FlightGear addons and mods ==
== In the hangar ==
=== New aircraft ===
=== Updated aircraft ===

[[File:ZF_Navy_free_balloon-2.jpg|thumb|The ZF Navy free balloon with the envelope shader enabled.]]
====ZF Navy free balloon====
The [[ZF Navy free balloon]] has been updated with a custom shader effect that changes the shape of the balloon envelope according to its gas content.

====IAR 80====
The [[IAR_80|IAR 80]] beta has seen some updates, with new features added in the eyecandy department, as well as some refining of the [[Nasal_scripting_language|Nasal]] code and a revamped [[FDM]].

====Boeing 757 and 717====
[[User:Skyop|Skyop]] has picked up development of the [[Boeing 757-200]] and the [[Boeing 717]]. New features included generic autostart systems, improved models, new instruments and new [[YASim]] [[FDM]]s. New and improved cockpits and aircraft systems are planned. Skyop is requesting livery makers to start painting their favorite airlines and submitting their textures to the [http://liveries.flightgear.org official FlightGear livery database].

Follow further progress at the [http://flightgear.org/forums/viewtopic.php?t=9944 757-200 development thread] and the [http://flightgear.org/forums/viewtopic.php?t=6145 717 development thread].

====Boeing 777-200====
The [[Boeing_777-200|777-200ER]] received a cockpit and systems upgrade.
Extensions by Syd Adams and ThorstenB include better [[GPWS]] integration, improvements for cockpit instruments, sounds, textures, key/mouse bindings and many bug fixes.
The upgraded 777-200ER also features brake temperature monitoring.
Pilots are advised to also use spoilers and thrust-reversers for deceleration to avoid overheated brakes - especially when landing a heavily loaded plane.
The new auto spoilers, automatically deploying on touch-down when armed, provide some assistance here.

[[File:B777-200_RTO.jpg|thumb|Smoking brakes after a 777-200ER had to execute a rejected takeoff.
The airline declined to comment on the reason for the takeoff problem, but assured no one on board was injured.]]

=== Liveries ===

==Scenery corner==
===New Bangkok International Airport===
[[File:VTBD_wip01.jpg|thumb|Bangkok Int'l Airport - work in progress.]]
Mike (aka D-Sky1) is busy again. This time he is working on Suvarnabhumi Airport (VTBD, also known as New Bangkok International Airport) in Thailand) as the architecture of the airport buildings is very beautiful. It will sure take some time but a first glance at the work in progress is already possible. Discuss the progress with us in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10075 the forum].
After the airport is finished, placed and available, AI traffic will follow (mainly Thai Airways).

AI traffic arrives at [[RPLL]] (Manila, Philippines): Mike created a comprehensive list of AI traffic of Cebu Pacific Airlines. Soon available via GIT, Cebu Pacific Airlines will provide domestic and international flights to the most important destinations. AI for the second big carrier of the Philippines (Philippine Airways) will follow later.

===Land cover updates===
Detailed land cover data for Vermont has been added to the map server. This state in the northeast United States will be a part of the next world scenery release.

Work continues on hand-created, detailed land cover data for northern Switzerland. Photos of landmark buildings or airport buildings in Switzerland would be welcome as we try to model this beautiful country.

===NASA Interactive Launch Complexes===
[[File:mercuryredstone3.png|thumb|Mercury Redstone 3 Rocket ready for launch.]]
Jack Mermod has released the first of many NASA Interactive Launch Complexes. This first release is based on Launch Complex 5 and the [http://en.wikipedia.org/wiki/Mercury-Redstone_3 Mercury-Redstone 3] launch. The model should be in the official database soon, for now you can download the scenery [http://alphashangar.co.nr/ here].

=== Jet d'Eau in Geneva ===
The Jet d'Eau in Geneva is with 140m height a recognisable landmark. Ot-666 created the fountain and the pier it is located on in the Lake Geneva.
The model features night illumination for the fountain.

=== Airports ===
Looking for new airports to visit? Try a Dublin (EIDW) to Aalesund (ENSD) flight! These two airports, along with Sandane airport in Anda, Norway (ENVA), have recently had models added to the database to make them a more interesting place to fly.

===I.C.E.J.A.W===
[[File:ICEJAW_snowcover.jpg|thumb|Demonstration of ICEJAW depicting buildings with and without snow cover.]]
In an effort to improve the cities in FlightGear, Daniel Strawn (aka "Intel-Qube") has modeled a simple "one size fits all" city. Affectionately codenamed "ICEJAW", the city, still in development, features tangible helipads to land on, billboards and snow cover for heavy snow-fall.
Follow development in the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10016 forum topic].

=== TerraGear-CS ===
After attempts to provide a new World Scenery build in sync with the 2.0 software release failed miserably (due to software deficiencies), some effort has been expended into investigations, experiments (some of which ended up in filing bug-reports for related software) and large-scale tests for replacing the entire polygon processing in TerraGear by the use of [http://grass.osgeo.org/ GRASS GIS]. Just to give an idea about the term "large scale": The procedure to turn the Europe-wide CORINE CLC2000 vector data set into a topologically consistent coverage is taking several weeks on a 3 GHz Xeon machine.

The "*-decode" commands and old-style work directories are affected by this change as well as all polygon-mangling routines in "construct". The GRASS toolbox provides all the features we need for ''reliable'', topologically correct polygon handling (cleaning, clipping and the like). Those (early) steps of the new toolchain which have proven to be rather stable are available [http://mapserver.flightgear.org/git/?p=terragear-cs;a=tree;f=gisscripts here] (GRASS7 required for certain features).

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
A beautiful flight is from Prince George, ICAO: CYXS, to Calgary Springbank, ICAO: CYBW, under the route created by reed, which can be seen at [http://flightgear.org/forums/viewtopic.php?f=10&t=9772 the forums]

== Aircraft review ==
[[Image:Beechcraft_B1900D.JPG|thumb|Cockpit of the B1900D]]
The [[Beechcraft B1900D]] is a twin-engine turboprop aircraft, designed to be an all-weather regional airliner. It's been used by U.S. military and many other governments. In total, 695 very produced until 2002, and it's one of the default aircrafts in FlightGear and has been available since version 0.9.8.

With a well-implemented cockpit and fully functional GPS, it is one of the better developed aircraft within FlightGear.

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==

=== FSweekend ===
As in previous year's FlightGear organized a booth at the annual [[FSweekend]] event in Lelystad, the Netherlands. [[FSweekend 2010|This year's edition of FSweekend]] came and went by before we realized it. Although there was initially skepticism as to whether we would be able to top last year's presentation, we did so, by quite a large margin. Main attractions this year were our Thomas-Krenn sponsored server, driving 10 monitors, and our near continuous use of [[Anaglyph (3D)|anaglyphic 3D]]. Although we had considered it to be a neat gadget, running flightgear in 3D analglyphic mode turned out to be a brilliant move. Not only did it draw a lot of people to our booth who wanted to check it out, handing out 3D glasses also worked as an extremely good vehicle to start a conversation with them.

Some assorted highlights include:
*Our Thomas-Krenn AG machine has been running for 8 hours straight, on both days, without a single glitch. At one point Torsten ran out of fuel, because he hadn't realized that FlightGear had been running for so long continuously. The machine ran in three 3D mode most of the time, and the way the screens were set up gave the impression that the were just holes in a wall though which you could see a (virtual) reality known as FlightGear. Very nicely done.
*Very positive comments on the Lockheed Constellation's artwork, particularly because that model is really shining when presented in 3D (probably the best cockpit we have for a 3D demo).
*Also very postive comments on the advance copy of the 737NG (800) that Innis Cunningham sent me. Also in particular due to the fact that the switches on the overhead panel look very real in 3D.
*Booth members Gijs and Jorg trying to outperform each other in terms of their helicopter flying skills (trying to land it on a chimney, once they found the helipad to easy).
*A number of people claiming that our booth was the best one at FSWeekend this year.
*Our aerotowing demo involving all of our major demonstration machines (my machine as the glider, Jorg's computer as the tow plane, and our sponsor's machine as a joint (3D) model viewer.
*Some people just not believing that a single machine could drive 10 monitors and actively checking where all the monitor cables actually went to.
*Another opportunity to meet FlightGear developers (one expected encounter: Geoff McLane, and one totally unexpected meeting with Thorsten Brehm). Thanks guys for showing up!

And last, but not least, everybody involved in getting this year's booth organized. It's been a lot of fun. Some pictures of the event can be found [http://www.dropbox.com/gallery/7455889/1/FSWeekend2010?h=0e9825 here]

=== FlightGear on youtube ===
[http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=8726 Sealbhach] has made an [http://www.youtube.com/watch?v=zveiKtooXs0 excellent video] showcasing the great scenery at LOWI.

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===

== Useful links ==
== And finally ... ==
===A christmas present for you===
[[File:Gerbrandytoren_christmas.jpg|thumb|World's largest Christmas tree.]]
Do not forget to pay a visit to the [http://en.wikipedia.org/wiki/Gerbrandy_Tower Gerbrandytoren] in the Netherlands. With a height of 366.8m and 120 lights, it is the world's largest Christmas tree between December 11 and January 6. The tower is located 21 nm South East (HDG 120h) of [[Amsterdam Airport Schiphol]] ([http://mpmap02.flightgear.org/?ll=52.009982,5.053582&z=15 location on MPMap]).

=== Contributing ===
One of the regular thoughts expressed on the FlightGear forum is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

=== Did you know ===
* You can act as an [[ATC|air traffic controller]] on the multiplayer servers by downloading the [[ATC-aircraft|ATC aircraft]]?
* That Luiz Jazbinsek, known as Cael in the FlightGear forums, is doing a [http://flightgear.org/forums/viewtopic.php?f=10&t=10126 world circumnavigation] with the [[Beechcraft B1900D]]?

[[Category:FlightGear Newsletter|2010 11]]

File:LOWI oamtc helicopter base.jpg

2010-09-20T00:32:49Z

Ot-666: uploaded a new version of "File:LOWI oamtc helicopter base.jpg": update to current project status

Helicopter base at LOWI Innsbruck airport.