FlightGear wiki - User contributions [en]

Template:POTW/2013-6

2013-02-10T21:15:20Z

Thebgland:

{{POTW
|image = A330-203.png
|description = http://www.youtube.com/watch?v=efDgpPUaTV4
|article = Airbus A330-200 Series
}}<noinclude>[[Category:Picture of the week 2013]]<noinclude>

File:A330-203.png

2013-02-10T20:37:19Z

Thebgland:

=={{int:filedesc}}==
{{Information
|description={{en|1=A330-203 on runway with services.}}
|date=2013-02-10
|source={{own}}
|author=[[User:Thebgland|Thebgland]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-zero}}

Template:POTW/2012-50

2012-11-25T06:13:36Z

Thebgland: Page Created

{{POTW
|image = Typhoon.jpg
|description = AThe Eurofighter Typhoon is a twin-engine canard-delta wing multirole aircraft. It is being designed and built by a partner consortium, Eurofighter GmbH, founded in 1986, made up of the major aerospace companies of the four Eurofighter partner nations...
|article = Eurofighter Typhoon
}}<noinclude>[[Category:Picture of the week 2012]]<noinclude>

Template:POTW/2012-49

2012-11-23T17:56:19Z

Thebgland: Page Created

{{POTW
|image = Afterburner.jpg
|description = An afterburner is an additional component added to some jet engines, primarily those on supersonic aircraft. Its purpose is to provide a temporary increase in thrust, both for supersonic flight and for takeoff...
|article = Afterburner#Afterburners
}}<noinclude>[[Category:Picture of the week 2012]]<noinclude>

Airbus A320neo/Development

2012-11-22T22:53:47Z

Thebgland: Added Categories

=ToDo List=
==Electrical==
;Files
: /Nasal/electrical.nas - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Nasal/electrical.nas]

;Notes
: Aircraft already uses '''Syd Adam's''' ''Jet Electrical'' system.

;To Do
: Move Nasal file to a dedicated directory in the ''Systems'' folder?

==Hydraulic==
;Asigned Developers
: Narendran

;Branch name
: develop

;Files
: All Hydraulic files in ''/Systems/Hydraulics'' Directory

;Notes
: Will start work on the hydraulic system as soon as the cockpit is ready

==Instruments==

;Assigned Developers
: Jon
: Narendran

;Branch Name
: develop

;Notes
: PFD - Rebuild 3D Instrument, use better textures and markers - COMPLETE
: Upper ECAM (EICAS) - Rebuild 2D Instrument with latest A320 ECAM Layout (3 section)

==Pneumatics==
;Asigned Developers
: Narendran

;Branch name
: develop

;Notes
: Include basic pneumatic air pressure system, also include system cooling functions.

==Fly by Wire==
;Asigned Developers
: Narendran
: Jon Ortuondo (Bicyus)
: Polly

;Branch name
: fbw-devel

;Notes
: Basic airbus flight conrol laws and flight phases/modes work. FBW converts pitch-rate, roll-rate and g-force (over 210 kts) and converts to control surface outputs using pids. Also, when stick is neutralized, fbw shifts to stabilizer pids where trimmers maintain pitch and bank angle.

;Files
: Systems/Airbus-fbw/'''Airbus-fbw.nas''' - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.nas]
: Systems/Airbus-fbw/'''Airbus-fbw.xml''' - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.xml]

;To Do
: Move fbw.nas and a320-fbw.xml to common Systems directory. - ''DONE''
: Update FDM from Airbus-fbw branch
: Further tune PIDs (Polly/Jon?)
: Implement mechanical backup law (requires better systems)
: Study and Implement Flare Mode for NORMAL LAW

==FMGC, FCU and mCDU==
;Asigned Developer(s)
: Narendran

;Branch name
: flight

;Notes
: Using data from smart cockpit and equicom. [http://www.smartcockpit.com/plane/airbus/A320/]
: Making a whole new Autopilot/Route Manager system. < Most of this is complete, but the PIDs need to be played with. (Polly)
: FCU is basically just the old 'Mode Control Panel' but that too requires some extra scripting.

;Resources
: Equicom mCDU Emulator [http://www.equicom.net/mcdu/]
: SmartCockpit FMGS Doc [http://www.smartcockpit.com/pdf/plane/airbus/A320/misc/0011/]
: SmartCockpit Systems Briefing [http://www.smartcockpit.com/pdf/plane/airbus/A320/misc/0002/]
: SmartCockpit Autoflight Systems [http://www.smartcockpit.com/pdf/plane/airbus/A320/systems/0025/]

;Completed Sections
:FMGC (AP1, AP2, NAV, A-THR)
:FCU (aka. MCP)
:FMGC (WP Transition Manager)
:mCDU > DATA
:mCDU > F-PLN
:mCDU > LAT REV A
:mCDU > VER REV (SIMPLE)
:mCDU > INIT A
:mCDU > FLT SRC
:mCDU > INIT B (FUEL PRED)
:mCDU > RAD NAV

;Sections in Progress
:mCDU > LAT REV B (TP)
:mCDU > WINDS - Might have to temporarily simplify this as I'm not exactly sure how to exactly use these for speed and time calculations on the F-PLN yet.
:mCDU > PERF

;Remaining Sections
:mCDU > DIR
:mCDU > PROG
:mCDU > MCDU MENU
:mCDU > WP SRC
:mCDU > NAVAID SRC
:mCDU > RWY SRC
:mCDU > SEC F-PLN
:mCDU > AIRPORT
:mCDU > ATC COMM

==ECAM procedures and Alarms systems==
;Asigned Developers
: Jon

;Branch name
: develop

;Notes
: ''Functionalize'' ALL ECAM Pages :P

==New Cocpit Model & xml==
;Asigned Developers
: Narendran
: Jon A. Ortuondo (bicyus) - xml

;Project > Repository > Branch
: FlightGear Airbus Development > airbus-a320neo-devel ([https://gitorious.org/flightgear-airbus-development/airbus-a320neo-devel]) > ''flightdeck''

;Files
: All Flightdeck models are in root

;Notes
: Basic shell, panel, glaresheild, sidesticks, seats and pedestal models complete. These have also been textured.
: Overhead panel will be derived from the old one but model will be improved
: Cockpit has been ported into FlightGear

;To Do
: Animations and re-positioning of instruments - STARTED
: Re-make PFD and EICAS? (current versions are not too realistic)

==Navigation Display==
;Asigned Developers
: Scott

;Branch name
: develop

;Notes
: The nav display is common to the A320, A330 and A340 series, so ideally would be shared between all three. Using the C++ NavDisplay instrument available in FG 2.6, Scott has created a full-functioning display for the A380, which can be adapted for the A320 with minimal effort, I hope. (It's probably not possible to share the actual XML between the A320/340 and the A380, alas). Contact James or Scott before spending time on this task, please.
: I checked up and found that the nav display is common for all airbus aircraft from A320 to A380, which means we already have a fully functional nav display from the A380. All we'd need to do now is port it (which'd probably include re-sizing) into hte A320neo.

;Status
: Base files applied
: resolving minor adjustments on each of the "mode" displays
: committed ARC/ROSE NAV, VOR, LS modes, supports WPT, ARPT, NDB, VORD EFIS switches

==Low Priority / Unstarted==

===Rembrandt Lighting===

===A319neo and A321neo interior===

;Please edit if anyone wants to take up any unstarted sections.

=Proposals=
==Directory structure==

A320neo
└── Systems
├── electric
│ ├── left_bus.nas
│ └── right_bus.nas
├── fbw
│ ├── Airbus-fbw.nas
│ └── Airbus-fbw.xml
└── hydraulic
├── blue.nas
├── green.nas
├── hydraulics.xml
└── yellow.nas

==Alternate Nasal Only Structure==

A320neo
└── Nasal
├── electrical
│ └── electrical.nas
├── pneumatic
│ └── pneumatic.nas
├── hydraulic
│ └── hydraulic.nas
└── mCDU
├── main_loop.nas
├── functions.nas
└── navdata.nas

[[Category:Airbus]]

File:777jetwaybeaf.jpg

2012-11-22T22:41:42Z

Thebgland: Added Categories

An animated jetway connecting to a 777-200; before and after

[[Category:Boeing]]
[[Category:Airliners]]

File:747KSFO2.jpg

2012-11-22T22:41:23Z

Thebgland: Added Categories

Boeing 747-200 landing at KSFO

[[Category:Boeing]]
[[Category:Airliners]]

Boeing 747

2012-11-22T22:39:47Z

Thebgland: Added a Gallery

[[File:747-400.jpg|thumb|270px|A [[Boeing 747-400]] in KLM livery.]]
[[File:747.jpg|thumb|270px|A [[Boeing 747-100]] in PIA livery.]]
The '''Boeing 747''', sometimes nicknamed the "'''Jumbo Jet'''", is among the world's most recognizable aircraft, and was the first wide-body commercial airliner ever produced. Manufactured by Boeing's Commercial Airplane unit in the United States, the original version of the 747 was two and a half times the size of the [[Boeing 707]], one of the common large commercial aircraft of the 1960s. The aircraft's wingspan is actually longer than the length of the Wright Brothers' first flight. First flown commercially in 1970, it held the passenger capacity record for 37 years, until it was surpassed by the [[Airbus A380]].

The four-engine 747 uses a double deck configuration for part of its length. It is available in passenger, freighter and other versions. The 747's hump created by the upper deck allows for a front cargo door on freighter versions, and serves as additional seating in most versions. The [[Boeing 747-400|747-400]], the latest version in service, is among the fastest airliners in service with a high-subsonic cruise speed of Mach 0.85 (567 mph or 913 km/h). It has an intercontinental range of 7,260 [[nautical mile]]s (8,350 mi or 13,450 km). The 747-400 passenger version can accommodate 416 passengers in a typical three-class layout or 524 passengers in a typical two-class layout.

The 747 was expected to become obsolete after 400 were sold because of the development of supersonic airliners, but it has outlived many of its critics' expectations, and production passed the 1,000 mark in 1993. As of March 2008, 1,400 aircraft had been built, with 122 more in various configurations on order. The latest version of the aircraft, the 747-8, is scheduled to enter service in 2009.

== Variants ==
* [[Boeing 747-100]]
* [[Boeing 747-200]]
* [[Boeing 747-400]]
* [[Boeing 747-8i]]
* [[Boeing 747-8 Dreamlifter]]
* [[Boeing 747-8F]]

== Gallery ==
<gallery>
File:747KSFO1.jpg
File:747KSFO2.jpg
File:747-400_cockpit.jpg
File:747-200.jpg
File:747-400 pushback eham.jpg
File:747-400_wing_flex.jpg
File:Boeing 747-400 KLM night.png
File:Boeing 747-400 lightmap cockpit.png
File:Boeing 747-400 lightmap exterior.png
File:Boeing 747-400 KLM.png
File:747-400 SIA climbing out EGKK.png
</gallery>
== External links ==
* [http://www.boeing.com/commercial/747family/index.html Boeing 747 product page]

{{Boeing}}

[[Category:Airliners]]

File:747KSFO1.jpg

2012-11-22T22:30:50Z

Thebgland:

Boeing 747-200 landing at KSFO

[[Category:Boeing]]
[[Category:Airliners]]

Rockwell B-1B Lancer

2012-11-22T22:18:52Z

Thebgland: Added a See Also Section

{{infobox Aircraft
|image = B-1B.png
|name = Rockwell B-1B Lancer
|type = Military aircraft
|status-fdm = 3
|status-systems = 3
|status-cockpit = 4
|status-model = 4
|authors = Markus Zojer, Paul Jay Schrenker
|fdm = YASim
|status = Development
|fgname = B-1B
}}
== Aircraft Help ==
=== Startup ===
# Switch on Battery switch (overhead/middle)
# Start APU left and/or right (overhead/right) by switching APU MODE L/R to on/start <nowiki>
NOTE: use one of the points below!</nowiki>
#* Couple left and right drive by switching L/R DRIVE to 2/4 ADS COUPLE
#* Switch on L/R BLEED AIR. If only 1 APU active, switch to CRSVR AIR to start engines in the other nacelle
# Switch on Engines (middle console/back) <nowiki>
NOTE: APU left powers engines 1,2 APU right -->3,4</nowiki>
# Switch APU off when engines are on, or after climb

=== Terrain Following Systems TER FLW ===
# Adjust clearance SET CLR (200ft increments)
#* ...A=0, B=200ft, C=400ft, D=600ft to J=2000ft
#* ...flatlands: down to 200ft, hills: 400/600ft
#* ...mountains: 800ft and above
# switch -PRTY- to TER FLW (other setting MAP)
# Toggle master switch TER FLW on

[[File:B-1B_2.jpg|thumb|270px|A takeoff with the [[afterburner]]s on]]
=== Terrain Avoidance Systems TER AVD ===
# Adjust obstancle clearance CLR PLN
#* ...possible settings: 0, 100, 300, 500, 1000ft
# Adjust distance RNG, currently 2.5 or 5nm
# Toggle master switch TER AVD on plane clears obstancle, stays at new alt

=== Fuel Center of Gravity Management System FCGMS ===
(-working but experimental-)
# Set CG SET to %MAC of desire also visible at %MAC scale as orange marker
# Switch SYS to ON CG %MAC visible as white marker works only within a certain margin, then orange and white marker are at same %MAC

=== Weapon System ===
# Select Light or Heavy weapon config from B-1B menu
# Switch to OSO seat/view -> SMS panel ahead
# Arm weapons by selecting bay and then station (on SMS) status visible on SMS display
# press Ctrl j to initiate release sequence
# Close bay doors

== See Also ==
[[Convair B-58]]
== External link ==
* [http://www.flightgear.org/forums/viewtopic.php?t=262 The forum topic]

[[Category:Bomber aircraft]]
[[Category:Variable-sweep wing aircraft]]

Template:POTW/2012-48

2012-11-22T21:47:27Z

Thebgland: Page Created

{{POTW
|image = Atlaslogo_white.png
|description = Atlas Virtual Airlines is a virtual airline that is the product of a merger between several active FlightGear-based virtual airlines. Atlas Virtual Airlines is also one of FlightGear's largest virtual airlines, with over 200 members.
|article = Atlas Virtual Airlines
}}<noinclude>[[Category:Picture of the week 2012]]<noinclude>

Template:POTW/2012-47

2012-11-22T21:43:02Z

Thebgland: Page Created

{{POTW
|image = Lockheed Martin f-22 Raptor.png
|description = The Lockheed Martin/Boeing F-22 Raptor is a single-seat, twin-engine fifth-generation fighter aircraft that uses stealth technology. It was designed primarily as an air superiority fighter, but has additional capabilities that include ground attack, electronic warfare, and signals intelligence roles.
|article = Lockheed Martin F-22 Raptor
}}<noinclude>[[Category:Picture of the week 2012]]<noinclude>

File:Lockheed Martin f-22 Raptor.png

2012-11-21T17:56:28Z

Thebgland:

=={{int:filedesc}}==
{{Information
|description={{en|1=The f-22 raptor on the runway at KHIF.}}
|date=2012-11-21
|source={{own}}
|author=[[User:Thebgland|Brady Griffith]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-zero}}

[[Category:Fighter aircraft]]
[[Category:Lockheed]]

General Dynamics F-16 Fighting Falcon

2012-11-21T17:38:51Z

Thebgland: Added information and a download link

{{infobox Aircraft
|ready = airrefuel
|image = General_Dynamics_F16.jpg
|name = General Dynamics F16
|type = Military aircraft
|fdm = JSBSim
|status = Production
|authors = Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
|fgname = f16
|download = ftp://ftp.de.flightgear.org/pub/fgfs/Aircraft-2.8/f16_20120717.zip
}}

The General Dynamics F-16 Fighting Falcon is a multirole jet fighter aircraft for the United States Airforce developed by General Dynamics.

[[File:F16-cockpit-pano.jpg|480px|thumb|center|[[Howto: Make full spherical panorama|A full spherical panorama]] of the f-16 cockpit]]

== Keyboard Controls ==
'''Flight Controls'''
{| class="prettytable"
|Ctrl-b
|: Toggles speed brake
|-
|Delete
|: Toggles FBW (Fly by Wire) override
|}
'''Miscellaneous'''
{| class="prettytable"
|Ctrl-f
|: Triggers flare release
|-
|Ctrl-h
|: Toggles arrester hook
|-
|C
|: Toggles canopy
|-
|e
|: Fires the cannon
|-
|}
'''Radar'''
{| class="prettytable"
|Ctrl-n
|: Toggles Radar RWS / TWS AUTO Modes
|-
|E
|: Decreases Radar Range
|-
|R
|: Increases Radar Range
|-
|q
|: Toggles Radar Standby Mode
|-
|}

==Development Status==
See [[F16/Development]]

== External link ==
* [http://brenthugh.com/flightgear/Sun_Valley_Tank_Invasion1.zip Several ground bombing scenarios suitable for the F-16, involving moving and static tank formations, explodable M1 Abrams tanks, etc.]

[[Category:Military aircraft]]

{{Lockheed}}

[[Category:Fighter aircraft]]
[[fr:General Dynamics F-16]]

FGSignMaker

2012-11-20T04:30:23Z

Thebgland: Removed a broken link

{{Infobox Software
| title = FGSignMaker
| logo =
| image = FGSignMaker_overview.png
| alt = Version 1.5.0
| developedby = skyop
| initialrelease = 0.5.0
| latestrelease = 1.5.0
| writtenin = (X)HTML/JavaScript
| os =
| platform = Cross-platform
| developmentstatus = Active (2010-)
| type =
| license = [[GNU General Public License]]
}}
'''FGSignMaker''' is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate [[Signs|taxiway sign]] codes for [[FlightGear]] licensed under the [[GNU General Public License]]. It can be used in conjunction with the [[UFO]] and your favorite plain text editor to add taxiway signs for FlightGear. The latest release available is version 1.5.0.

== Web browser compatibility ==
=== Known compatible browsers ===

FGSignMaker 1.5.0 is known to work well with the following web browsers:
* Google Chrome
* Internet Explorer 6 '''not recommended''', due to JavaScript/CSS bugs and for just being a horrible browser in general)
* Internet Explorer 7, 8, 9
* Mozilla Camino
* Mozilla Firefox 3.6
* Opera 9
* Safari

=== Most wanted ===
These browsers are "most wanted". If FGSignMaker works correctly under one of these browsers, please add them to the list above.
* Arora
* Chromium

== Interface ==
=== Sign preview ===
[[File:FGSignMaker_signpreview.png|Sign preview]]

The sign preview, which updates automatically as you modify the sign code, gives you a rough (but fairly accurate) idea of how your sign will look when in FlightGear.

=== Sign code box ===
[[File:FGSignMaker_codebox.png|Sign code box]]

The sign code text box displays the actual code for the taxiway sign. You can insert glyphs here and type custom text. The "Select All" button selects all the text in this box and the "Clear" button deletes all the text ''without warning.''

=== Character counter and syntax checker ===
[[File:FGSignMaker_countersyntax.png|Character counter/syntax checker]]

The character counter (the "Character 15" in this screenshot) displays your cursor's position in the sign code box. It is mostly useful for debugging. The syntax checker is an automatic tool that checks for misplaced braces ({ and }) and space characters (they are invalid, underscores _ must be used instead).

=== Glyph inserter ===
[[File:FGSignMaker_glyphinserter.png|Glyph insertion tools]]

Last but certainly not least, the glyph inserter allows you to place predefined taxiway types and features. Currently it includes the four FAA-standard types implemented in FlightGear (L858-Y, L858-R, L858-L, L858-B), a line (vertical pipe |), and a no-entry sign.

== Placing taxiway signs ==
[[File:FGSignMaker_signfg-signmaker.png|250px|thumb|right|A taxiway sign in FlightGear (background) and in FGSignMaker (inset)]]
This tutorial explains how to add [[Signs|taxiway signs]] to FlightGear along with FGSignMaker. You are highly encouraged to add taxiway signs to your favorite airport, even if they are somewhat inaccurately placed.

=== Step 1: Launch FlightGear ===
[[File:FGSignMaker_tut1.png|400px|Step 1]]

First things first, we'll launch FlightGear in the [[UFO]] at the airport we will be working on (in this case [[KSFO]]). Here I will be using my fancy Linux terminal, but [[FlightGear Launch Control|FGRun]] will also suffice.

=== Step 2: Place taxiway sign(s) ===
[[File:FGSignMaker_tut2.png|830px|Step 2]]

With FlightGear loaded, fly the UFO to the location of the sign you want to place. Press the spacebar (or l-key) to bring up the model select dialog, choose <tt>[[$FG ROOT]]/Aircraft/ufo/Models/sign.ac</tt> and click where you want to place the new sign. Alt+Click the terrain to reposition the sign if need be. Press tab to bring up the adjustment dialog and use the heading slider and arrows to turn the sign. For more information on this process, see [[Howto: Place 3D objects with the UFO]].

=== Step 3: Build your sign in FGSignMaker ===
[[File:FGSignMaker_tut3.png|531px|Step 3]]

Now we create the actual taxiway sign code in FGSignMaker. In this case, a pilot looking at the sign would be on taxiway Delta, taxiway Charlie would be on the left, the end of runway 36L would be right in front, and the end of runway 18R would be on the right. To create this sign in FGSignMaker, we would:
# Click the L858-Y button
# Click the left arrow
# Type "C" into the sign code box
# Click the L858-L button
# Type "D" into the sign code box
# Click the L858-R button
# Type "36L-18R" into the sign code box
# Click the right arrow

=== Step 4: Add the sign into the *.stg file ===
Press the d-key to dump the export data to the command line or fgrun log window. You will see several lines similar to this example:

# w130n30/w123n37/942050.stg
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

------------------------------------------------------------------

As you add more signs and/or scenery objects, this output will grow. The latest object you placed is on the last line.

The most important piece of information we need right now is the *.stg file to edit. This is displayed in the comment (line with the hash # at the front).

# w130n30/w123n37/942050.stg

This tells us that the wanted *.stg file can be found at <tt>[[$FG SCENERY]]/Objects/w130n30/w123n37/942050.stg</tt> - obviously, the path will vary depending on where you placed the sign.

Now open that *.stg file in your favorite plain text editor. Insert the desired OBJECT_SIGN line from the command line output from earlier, like so:

...
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

Now replace the "{@size=10,@material=RedSign}NO_CONTENTS_[random number]" with the taxiway sign code you generated in step 3. Save the file.

=== Step 5: View your new sign(s) in FlightGear ===
[[File:FGSignMaker_signsinfg.png|300px|right|thumb|KBFL taxiway signs made with FGSignMaker]]
You won't immediately see your changes in FlightGear - you will have to restart the simulator. Once you do, you should be able to see the new taxiway signs.

== Submitting your work ==
If you are happy with your work, please submit it into the [[FlightGear Scenery Database]]. See [[FlightGear Scenery Database#Contributing Positions|here]] for more details.

== To-do list ==

* Implement different sizes for signs

== External links ==
* [http://www.flightgear.org/forums/viewtopic.php?t=8596 Forum thread]

[[Category:Scenery enhancement]]
[[Category:Software]]

Howto:Add submodels

2012-10-27T18:27:33Z

Thebgland: Fixed a small grammar error.

[[File:b29s-bombs.jpg|thumb|270px|[[Boeing B-29 Superfortress|B-29s]] dropping their load.]]
Submodels are the means in [[FlightGear]] whereby we can represent anything which is dropped, fired, or launched from an [[aircraft]] or indeed any model... the possibilies are endless. Some examples which can be found in FlightGear: guns, flares, bombs, droptanks, smoke, contrails. These last to date from a time before particles were implemented in FlightGear. While they still exist in older models, they are probably nowadays best done with particles.

In general, AI Models are instantiated at startup. Submodels, which use only AIBallistic objects, are pre-loaded at startup, but only instantiated when required.

This [[:Category:Howto|howto]] will explain '''how to add submodels''' to your model

=== Step 1: creating the submodel ===
First, you need to create a file with the extension .xml containg at least one <submodel> tag. Here is an example taken from the b29:

<submodel>
<name>M-17.001-submodel</name>
<model>/Aircraft/b29/Models/M17.xml</model>
<trigger>/sim/weapons/loadout[1]/bomb[0]/dropped</trigger>
<repeat>false</repeat>
<count>1</count>
<speed>0</speed>
<wind>false</wind>
<aero-stabilised>true</aero-stabilised>
<eda>1.42</eda>
<cd>0.75</cd>
<weight>500</weight>
<x-offset>-49.3968</x-offset>
<y-offset>1.968</y-offset>
<z-offset>-1.8368</z-offset>
<pitch-offset>0</pitch-offset>
<yaw-offset>0</yaw-offset>
<life>900</life>
<delay>0</delay>
<impact>true</impact>
<impact-reports>sim/ai/aircraft/impact/bomb</impact-reports>
</submodel>

'''Notes:'''

# Put the <PropertyList> tag before and </PropertyList> tag after the following document of course, as all our xml's carry this at the start and end! This file can be put anywhere you like in the [[property tree]], but ~/Aircraft/"your model"/Models is usual.
# All measurements are in Imperial Measure: Feet, Inches, Pounds. This is because the original author(s) were American. Please do not ask for this to be changed. There is simply too much work involved in doing so.
# Yet another co-ordinate system is introduced; see below.
# The trigger is a boolean property, which you define, which when "true" causes the submodel to be released/launched.
# A submodel will create an AIBallistic object which will follow a ballistic path. By default one submodel will be released when the corresponding trigger is "true". The initial conditions (IC) define the object's starting point (relative to the user model's current position), and its initial speed and direction (relative to that of the user model aircraft). If you want to release many similar objects with the same IC, then you may use the <repeat>, <delay> and <count> properties to define this.
# There is a long list of allowable tags. The allowed properties are:

<name> The name of the submodel.
<model> The path to the visual model. Any model in any location is allowed. All the normal
animations are available.
<trigger> The property which will act as the trigger.
<speed> Initial speed, in feet/sec, relative to user aircraft.
<repeat> Set "true" if you want multiple releases of this submodel. Defaults
to false
<delay> Time, in seconds, between repeated releases.
<count> Number of submodels available for multiple release.
<x-offset> Submodel's initial fore/aft position relative to user aircraft.
Fore is positive. (ft)
<y-offset> Submodel's initial left/right position relative to user aircraft.
Right is positive. (ft)
<z-offset> Submodel's initial up/down position relative to user aircraft.
Up is positive. (ft)
<yaw-offset> Submodel's initial azimuth, in degrees, relative to user aircraft's
nose. Right is positive.
<pitch-offset> Submodel's initial elevation, in degrees, relative to user aircraft's
pitch. Up is positive.
<buoyancy> Submodel's upward acceleration (fps) due to buoyancy in air. 32 is
neutral (contrails), > 32 exhaust gas, smoke.
<wind> If true, the Submodel is affected by local wind. Defaults to false. This
tag was added to cater for smoke, contrails and the like. The effect of
wind on ballistic objects is not well modelled. For bombs, bulllets etc.
this is best left at the default setting.
<cd> The Coeffient of Drag. Varies with submodel shape - 0.295 for a bullet,
0.045 for an airfoil. Enter an appropriate value. Defaults to 0.295.
<eda> Effective drag area (sq ft). Usually the cross-sectional area of the
submodel normal to the airflow.
<weight> The weight of the submodel (lbs). Defaults to 0.25
<aero-stabilised> If true, the submodel aligns with the local airflow. Defaults to true.
<external-force> If true the submodel is subjected to an external force.
<force-path> A string describing the property where the magnitude, azimuth and elevation
of the external force is to be found. The following child properties are
instantiated:
~/force-lb
~/force-azimuth-deg
~/force-elevation-deg
You need to manipulate these properties with some Nasal to apply an external
force to the submodel.
<force-stabilised> If true, the submodel aligns with the external force. Defaults to false.
If both this and <aero-stabilised> are true this takes priority.
<no-roll> If true, the submodel does not bank in turns. Defaults to false.
<collision> If true, the position of collisions (or hits) with other non-ballistic
AI models are reported. Defaults to false.
<impact> If this is true the position of impact on the terrain is reported. Defaults to
false.
<expiry> If true, the postion of the Submodel when its life expires is reported. Defaults
to false. Collision, Impact, and Expiry are handled in that order.
<impact-reports> A string descibing the location of Collision, Impact, or Expiry position.
Defaults to "/ai/models/model-impact".
<fuse-range> Range (ft) added to Collision and Impact calculations. Defaults to 0.0.
<contents> A string describing the property where the contents (lbs) of a Submodel are located.
Used with droptanks. Set to zero on release. Defaults to "none".
<speed-prop> A string describing the property where the initial speed of the Submodel is located.
Defaults to "none".
<submodel-path> A string describing the path to the .xml file where the next submodel Initial
Conditions are located. This submodel will be instantiated when any of Collision
Impact or Expiry are true. Submodels can be linked to any depth using this tag.
Defaults to "".
<random> If true, initial Azimuth is varied by +- 10 degrees, cd by 10%, and Life by the
value Randomness. Defaults to false.
<randomness> Varies the randomness of Life between 0.0(0%) and 1.0(100%). Defaults to 0.5 (50%).
<slaved> If true the Submodel is slaved to its parent model on release. For a subsequent release
the property "controls/slave-to-ac" must be set to false.

=== Step 2: adding the submodel to your model ===

This is very simple. First, add these lines to your model ~-set.xml file within the <sim></sim> tag:

<submodels>
<serviceable type="bool">true</serviceable>
<path>Aircraft/seahawk/Models/seahawk-submodels3.xml</path>
</submodels>

Where <path> is the path to the file you created at Step 1 above. If you want to add submodels to an AI Object, add the same lines within the <scenario></scenario> tag in the scenario file which instantiates the AI Object.

=== Step 3: controlling the submodel ===

There is no built-in way of setting/toggling the trigger property so you will need to add some mechanism to do this. A suitable key binding might be:

<key n="10">
<name>Ctrl-J</name>
<desc>Jettison Port and Stbd Pylon Stores.</desc>

<binding>
<command>property-assign</command>
<property>controls/armament/station[0]/jettison-all</property>
<value type="bool">1</value>
</binding>

<binding>
<command>property-assign</command>
<property>controls/armament/station[1]/jettison-all</property>
<value type="bool">1</value>
</binding>
</key>

=== Step 4: terminating the submodel ===

There are 3 ways to terminate your submodel:

# Do nothing: the submodel will die when its life expires or its altitude <= -1000, whichever occurs first.
# Instantiate a subsquent submodel: <submodel-path> contains the path to the file containing the submodel to be instantiated. Activated if one or more of <collision>, <impact>, or <expiry> are set to true.
# Instantiate a static model: for this you will need a Nasal fuction:

var droptank_node = props.globals.getNode("sim/ai/aircraft/impact/droptank",1);

var droptanks = func(n) {
var droptank = droptank_node.getValue();
var node = props.globals.getNode(n.getValue(), 1);
geo.put_model("Aircraft/seahawk/Models/droptank-hot.xml",
node.getNode("impact/latitude-deg").getValue(),
node.getNode("impact/longitude-deg").getValue(),
node.getNode("impact/elevation-m").getValue()+ 0.25, #+0.25 to ensure the droptank isn't buried
node.getNode("impact/heading-deg").getValue(),
0,
0
);
}

setlistener("sim/ai/aircraft/impact/droptank", droptanks);

The path <tt>sim/ai/aircraft/impact/droptank</tt> is the one you specified in the tag <submodel-path>. Options 2 and 3 are NOT mutually exclusive. Thus you can both instantiate a static model AND instantiate a subsequent submodel.
As above, this is activated if one or more of <collision>, <impact>, or <expiry> are set to true.

=== Technical stuff ===
# '''Slaved Objects.''' Slaved objects follow exactly the movements of their parent object. They can be released, when they then become normal Ballistic objects. They are designed for use as underwing stores, such as droptanks, as they give a realistic appearance on release. On the other hand, there is a small framerate cost. Where the stores are carried in a bombbay, this technique is not required. Here, an acceptable appearance can be achieved by adding models of the stores in the bombbay which are hidden on instantiation of the submodel.
# '''Formations.''' Wingmen are not AI Aircraft. In the interest of framerate they are in fact a sub-class of slaved objects, with added sinusoidal noise and some simple AI rules. They cannot be released to act independently. The formation can be changed by the use of a Nasal script. There is no collision detection or avoidance, so you must avoid flying the wingmen into each other during a formation change. Thare is a significant framerate cost involved. The wingmen can be as simple or complicated as you wish. The ones currently implemented tend to be fully detailed, and can be "ridden". This is uneccesary, but gives a fun viewpoint of the formation. In due course I will produce a Howto for Wingmen.
# '''Multiplayer.''' Submodels, indeed all AI objects are not visible over MP. This is in part deliberate (to prevent people trying to shoot at airliners), and in part technical (due to lag on the network the submodels would be nowhere near their actual position). On the other hand, it would be nice to include wingmen and perhaps droptanks in the overall scene. At the moment I cannot come up with a design which works at acceptable framerate cost.

[[Category:Aircraft enhancement|Add submodels]]
[[Category:Howto|Add submodels]]

Template:Model Gallery

2012-10-06T18:16:18Z

Thebgland:

<noinclude>This is the right place to add aircrafts to the lists in [[Aircraft]], [[:de:Flugzeuge]], [[:es:Aeronaves]], etc.</noinclude>
{{ #switch: {{{section|}}}
| carrier_borne_aircraft =
{{Gallery
|Buccaneer.jpg|[[Blackburn Buccaneer]]
|Douglas_A4.jpg|[[Douglas A-4 Skyhawk]]
|A-6E.jpg|[[Grumman A-6E|Grumman A-6E Intruder]]
|F-8E.jpg|[[F-8 Crusader]]
|F-14.jpg|[[Grumman F-14 Tomcat]]
|Hawker_Seahawk.jpg|[[Hawker Seahawk|Hawker Seahawk FGA6]]
}}
| experimental =
{{Gallery
|BAC_TSR-2_Prototype.jpg|[[BAC TSR-2 Prototype]]
|V22Osprey.jpg|[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]
|X15.jpg|[[North American X-15]]
|YF-23.jpg|[[Northrop/McDonnell Douglas YF-23]]
}}
| helicopters =
{{Gallery
|Ah-1_vietnam_firebase.png|[[AH-1 Cobra]]
|H21c.jpg|[[Boeing-Vertol H21C]]
|CH-47 Chinook.jpg|[[CH-47 Chinook Helicopter]]
|Bo105.jpg|[[Eurocopter Bo105]]
|Ec135.jpg|[[Eurocopter EC135]]
|EC130.jpg|[[Eurocopter EC130 B4]]
|OH-6.png|[[Hughes OH-6 Cayuse]]
|WG13.jpg|[[Lynx WG13]]
|S51.jpg|[[Sikorsky S51]]
|S58.jpg|[[Sikorsky S58]]
|s76c_landed.jpg|[[Sikorsky S76C]]
|Uh60.jpg|[[Sikorsky UH60]]
|Aluette2.jpg|[[Aérospatiale Alouette II|Alouette II]]
|Hup-3.jpg|[[Piasecki HUP-3]]
|R22.jpg|[[Robinson R22]]
}}
| historical_aircraft =
{{Gallery
|Couzinet70.jpg|[[Couzinet 70]]
|dh91.jpg|[[De Havilland D.H. 91 Albatross]]
|Douglas_DC3.jpg|[[Douglas DC-3]]
|ComperSwift.jpg|[[ComperSwift Comper]]
|Lockheed_1049.jpg|[[Lockheed 1049|Lockheed Constellation]]
|314.jpg|[[Boeing 314]]
|DHC-3.jpg|[[de Havilland Canada DHC-3 Otter]]
|1903_Wright_Flyer.jpg|[[Wright Flyer (UIUC)]]
|Short_Empire.jpg|[[Short Empire]]
|Dc-3-splash.png|[[Douglas DC-3-C47]]
}}
| light_civilian_aircraft =
{{Gallery
|A24-liverie-default.png|[[Aeroprakt A24 Viking]]
|Aerostar_700.jpg|[[Aerostar 700]]
|FK9MK2.jpg|[[B&F FK9 Mark 2]]
|Beech99.jpg|[[Beechcraft Model 99]]
|Cessna_172P.jpg|[[Cessna C172|Cessna 172P]] (1982)
|Edgley_Optica_01.jpg|[[Edgley Optica]]
|Piper Cherokee Warrior II.png|[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]
|Pa-24.jpg|[[Piper PA-24 Comanche|Piper Comanche (PA24-250)]]
|Piper j3cub.jpg|[[Piper J3 Cub]] (1946)
|Piper SenecaII.jpg|[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]
|dr400.jpg|[[Robin DR400]]
|Rallye-MS893.jpg|[[Rallye-MS893E]]
}}
| lighter_than_air =
{{Gallery
|Zeppelin_NT.jpg|[[Zeppelin NT]]
|ZF_Navy_free_balloon.jpg|[[ZF Navy free balloon]]
|Submarine_Scout.jpg|[[Submarine Scout]]
|Zeppelin_LZ_121_Nordstern.jpg|[[Zeppelin LZ 121 Nordstern]]
}}
| modern_airliners_narrowbody_midsize =
{{Gallery
|A320-family.jpg|[[Airbus A320 Family]]
|Beechcraft B1900D.png|[[Beechcraft B1900D]]
|707.jpg|[[Boeing 707]]
|717-200.jpg|[[Boeing 717]]
|727-230.2.jpeg|[[Boeing 727-230]]
|737-100.png|[[Boeing 737-100]]
|737-300.jpg|[[Boeing 737-300]]
|Boeing 737-400 British Airways.jpg|[[Boeing 737-400]]
|757-2002.jpg|[[Boeing 757]]
|Picture 11.png|[[Bombardier CRJ-200LR]]
|CRJ700.jpg|[[Bombardier CRJ700 series]]
|CessnaCitationX.jpg|[[Cessna Citation X]]
|Concorde.png|[[Concorde]]
|Fokker50.jpg|[[Fokker 50]]
|Tu154.jpg|[[Tupolev 154]]
}}
| modern_airliners_widebody_jumbo =
{{Gallery
|Airbus.png|[[Airbus A340-600]]
|A350.png|[[Airbus A350]]
|A380.jpg|[[Airbus A380]]
|747-400.jpg|[[Boeing 747-400]]
|Boeing 767-300.png|[[Boeing 767-300]]
|777-200.jpg|[[Boeing 777-200]]
|787.png|[[Boeing 787]]
|IL-96-400 Jet Airways.bmp|[[IL-96-400 Long Ranger(T)]]
}}
| modern_military_aircraft =
{{Gallery
|A-10.jpg|[[Fairchild A-10]]
|B-52F.jpg|[[Boeing B-52]]
|E-3B.jpg|[[Boeing E-3 Sentry]]
|F-15C.jpg|[[F-15C Eagle]]
|F-80C.jpg|[[F-80C Shooting Star]]
|Harrier.jpg|[[British Aerospace Harrier]]
|General_Dynamics_F16.jpg|[[General Dynamics F-16]]
|Cessna T-37.jpg|[[Cessna T-37]]
|Dassault Mirage F.1 at altitude.png|[[Dassault Mirage F.1]]
|Northrop_T-38.jpg|[[Northrop T-38]]
|OV-10A2.jpg|[[North American OV-10A Bronco]]
|Saab_J35.jpg|[[Saab J 35Ã– Draken|Saab J35Ö Draken]]
|LCA.jpeg|[[HAL Tejas]]
|F-22.png|[[Lockheed Martin F-22 Raptor]]
|MiG-29_splash.png|[[Mikoyan-Gurevich_MiG-29]]
|PC-9M.jpg|[[Pilatus PC-9M]]
|PC-21.jpg|[[Pilatus PC-21]]
}}
| science_fiction =
{{Gallery
|bluebird_hovercraft.jpg|[[Bluebird]]
|UFO.jpg|[[UFO from the 'White Project' of the UNESCO]]
}}
| spacecraft =
{{Gallery
|Shuttle.jpg|[[Space Shuttle]]
|Vostok-1-Exterior.png|[[Vostok-1]]
}}
| ultra_light = 
{{Gallery
|AirwaveXtreme150.jpg|[[Airwave Xtreme 150]]
|Hornet.jpg|[[GDT Hornet (autogyro)]]
|DG-101G_001.jpg|[[Glaser-Dirks DG-101G]]
|DG-300.jpg|[[Glaser-Dirks DG-300]]
|Dragonfly-towing.jpg|[[Dragonfly|Moyes Dragonfly]]
|Paraglider.jpg|[[Paraglider]]
|Asw20.jpg|[[ASW-20 sailplane|Schleicher ASW-20]]
|Sgs233.jpg|[[Schweizer 2-33]]

}}
| vehicles = 
{{Gallery
|AerocarI_1.png|{{int|Taylor Aerocar}}
|Follow_me.jpg|{{int|Follow me}}
|Jeep.jpg|{{int|Jeep}}
|Lamborghini Murcielago LP640 March10.jpg|{{int|Lamborghini Murcielago}}
|M113AS3.jpg|{{int|M113AS3}}
|Mobile_Stairs.jpg|{{int|Mobile Stairs}}
|Pushback.jpg|{{int|Pushback}}
|Snowplow.jpg|{{int|Snowplow}}
}}
| warbirds =
{{Gallery
|Beaufighter.png|[[Bristol Beaufighter]]
|Fokker_DrI.jpg|[[Fokker Dr.I]]
|P51d-mustang.png|[[P-51D Mustang]]
|A6M2_fgfs-screen-166.jpg|[[A6M2 Zero‎]]
|ki-84.jpg|[[Nakajima Ki-84‎]]
|Fw190.jpg|[[Focke-Wulf Fw 190]]
|Sopwith_Camel.png|[[Sopwith Camel]]
|Spitfire.jpg|[[Supermarine Spitfire]]
|MiG-15bis-Exterior.jpg|[[MiG-15]]
|iar80-angry.jpg|[[IAR 80]]
|F4u-park.jpg|[[F4U Corsair]]
|109-1.png|[[Messerschmitt Bf 109]]
}}
}} 
<noinclude>

{{Informative template | 1=
__NOTOC__
==Goal==
This template is used in aircraft/helicopter/vehicle gallery pages and their translations. By using and maintaining this template the translations of the gallery pages can be up to date and synchronised with the least required work possible.

==Usage==
<code><nowiki>{{Model Gallery | section=sectionname}}</nowiki></code>
Replace "sectionname" with the section you want to include.

==Example==
<code><nowiki>{{Model Gallery | section=light_civilian_aircraft}}</nowiki></code>
will be replaced by a gallery structure, that contains the list of "Light civilian aircraft"

===sections===
*carrier_borne_aircraft
*experimental
*helicopters
*historical_aircraft
*light_civilian_aircraft
*lighter_than_air
*modern_airliners_narrowbody_midsize
*modern_airliners_widebody_jumbo
*modern_military_aircraft
*science_fiction
*spacecraft
*ultra_light
*vehicles
*warbirds
}}

[[Category:Templates]]</noinclude>

Runway

2012-10-06T18:11:13Z

Thebgland: /* Approach Lighting */

A runway is a surface on an airport used for takeoffs and landings of aircraft. They are often made out of pavement, though other unpaved surfaces are used, such as dirt, sod, and gravel. They can be many different lengths, from 500m for STOL use to 11900m dirt runways at Edwards AFB.

== Parts of a Runway ==
=== Runway Safety Area ===
Around the runway, there is a runway safety area, which is flat and mostly clear of objects. This is to make sure that there are no loose items on the ground near the runway that could impede aircraft using the runway.

=== EMAS (Engineered Material Arresting Systems) ===
{{Main article|EMAS}}

=== Blast Pads ===
Often constructed at the beginnings and ends of runways are blast pads. These are to protect the runway and ground before it from jet blast produced by aircraft. If these blast pads are not there, terrain before the runway could degrade allowing the runway's surface to crumble towards it. When there are not areas at the ends of runways that are flat and smooth in case of overruns, such as at KMDW, these are often made into EMAS to help stop planes in overruns. They have yellow chevrons painted over them and are not suitable to land, take off, or taxi on unless emergency.
=== Threshold ===
This is the beginning of the runway, from the blast pad to blast pad. There are normally a series of white lines, with the identification after that, to identify the runway, one on each end, in normal circumstances. Extremely rarely, in the case of [[EDDF]], only one end is numbered, and because of this, this is the only used end. This threshold may be displaced from the start of the runway, see below.
=== Displaced Threshold ===
Displaced thresholds displace the normal threshold from the beginning of the runway. These are often constructed due to the fact that aircraft cannot land at the beginning of the runway due to noise restrictions or pavement strength. There are arrows pointing in the direction down the runway on them, leading up to the threshold. Aircraft may use them for takeoffs and to end landings, but in normal circumstances, they are not to be landed on.
=== Runway ===
This is the main operational part of the runway. There are many markings on it, starting at the threshold and continuing down to the other threshold. There is a striped white line continuing down the middle of the runway, as well as landing zone markings. Landing zone markings start with two sets of 3 white stripes, each on one side of the runway. Farther down, there are two sets of solid white boxes, similar in size to the groups of three stripes. In some countries such as Canada and Britain, these are replaced with a different design of stripes. Ahead are two sets of two white stripes, two sets of two white stripes again, two single white stripes, and two more single white stripes. If aircraft do not touch down within this region often a touch-and-go is performed. It should be noted that some or all of these markings do not appear on smaller-sized airports or unpaved runways.

== Runway Lighting ==
Almost all paved runways at major airports have lighting installed on them. This allows pilots to see the outline of the runway without actually seeing the runway, which helps for landing during night and low visibility situations. These lights use full-directional white lights to show the border and center line of the runway. Red lights point towards the middle of the runway and green lights point away from the runway from the threshold.

=== Approach Lighting ===
[[Calgary International Airport|Approach lighting]] assists pilots with a higher-density array right before the threshold to assist in landings while the lights are on. Often on [[ILS]] enabled runways, there are two strips of lights continuing from the approach lights onto the runway through the the landing zone.

== Instrument Landing System ==
{{Main article|Instrument Landing System}}

Often there are many devices built in under the pavement on runways. One of these systems is Instrument Landing System, or ILS. It uses radio signals to guide in a pilot who cannot perform a visual approach or wants a more precise approach, for any reason. This feature is included in FlightGear and is in use at almost all commercial airports, plus many general aviation ones.

Portal:Pilot

2012-10-06T18:02:28Z

Thebgland: Redirected page to Portal:User

#REDIRECT [[Portal:User]]

ATC at EDDF

2012-10-06T17:52:14Z

Thebgland:

Since a while, there are regular ATC sessions at [[EDDF]], hosted by the user Jomo who also acts as TC.

== Considerations for users ==
Please only join the ATC training if you wish to participate and have at least basic knowledge of English and ATC procedures.
Everybody is - of course - welcome to the sessions and the users are all willing to help a new user, but just flying around
uncontrolled while people try to accomplish serious training, is not very polite. 
During EDDF-ATC we communicate basically in English (and hopefully more and more over [[FGCOM]]!).
On request (or when we deem it necessary) we can provide the basic ATC-Commands also in writing for: German, French, Spanish,
Polish, Portuguese, and hopefully soon for more and more languages! (Sorry: But you still have to reply in "something like English"!). 
It is our major goal to train Pilots to use FGCOM (in English) and learn to follow basic Flying-Rules! 
Please do not use Mpserver02, that server is overloaded most of the time and does not react fast enough for ATC-Controlling. 
Never start-up on Runways! Set Startpos e.g. for EDDF in cmd-line or wizard: --parkpos= B42..48, or A10..25, etc. For all parkinglots available see the parking plan. 

== Initial procedure ==
When inbound EDDF: Please contact ATC from about 60 mi outside. 
Maximum Speed below 10000 ft is 250 kts. 
Maximum Taxi-Speed is 30 kts 

== ATC times ==
Currently, ATC at EDDF is available on 
Wednesday,Friday, Saturday and Sunday 
From 17:00 - 21:00 UTC (DST does NOT apply)

== References / more information ==
* [http://www.emmerich-j.de/S0.html General EDDF-ATC information on Jomo's website]
* [http://www.emmerich-j.de/FGFS/EDDF-PARK.zip EDDF parking plan and other documents]

== More Airports regularly providing ATC ==
* [[Konrad Adenauer Airport|Köln Bonn Airport]]
* [[Leipzig/Halle Airport]]
* Luxembourg Airport
* [[Warsaw Chopin Airport]]

[[Category:Air Traffic Control]]

A380 Tutorial

2012-10-06T17:49:04Z

Thebgland:

''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''

= Flying the A380 =

== Objectives ==
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;
* Familiarise you with key cockpit controls
* Provide guidance on weight control
* Introduce features of the Airbus Flight Guidance controls
* Introduce operation of Flight Management Systems
The tutorial will not teach you how to fly or use FlightGear, there are several other introductory tutorials that do a better job of that.

== Before You Start ==
'''FMS Database Files''' 
Before starting FlightGear you will need to download and install copies of FMS database files for the airports you will fly from and to. The A380 FlightGear model uses the Level-D 767 XML Format files for the Flight Management System. There are many web sites that have these files available for download, some require a paid subscription and are updated regularly, others provide them for free.

One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;
* click on "SID/STAR" in the top navigation bar,
* then click on "Download" from the left-hand menu,
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")
* select "YSSY - Sydney" from the stored airports drop-down list, then click on the little folder icon for the most recent version in the table
* save the ZIP file somewhere, we will un-zip it later.
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.

Under the A380 root (which is under <FG-Home>/data/Aircraft/A380) there is a directory called FMS/ this will be initially empty (except for a README file), open the previously downloaded ZIP files, and extract the YSSY.xml and NZAA.xml into the FMS/ directory.

'''YSSY Models''' 
For this tutorial you should also download YSSY terminal models. Visit the wiki page [[Sydney International Airport]] and at the end of the article is a link to download models for YSSY, simply unpack either the tbz (for Linux and Mac users) or zip (for Windows users) file under <FG-Home>/data/

'''Scenery Tiles''' 
If you haven't downloaded the scenery tiles around Sydney Airport, you should start [[Terrasync]] and then start FlightGear at YSSY, this will pre-load the scenery tiles for the airport ready for our tutorial flight, leave it running for a minute or two to download as much scenery around the airport as it can. This will mean the scenery tiles will exist in the directory maintained by terrasync, and the airport models will exist under the FG_DATA directory.

== Overview of Cockpit Components ==

[[File:A380-cockpit-components 01.png|none|500px]]

# Ignition start switch
# APU Master start switch
# External Lighting switches - includes strobe, landing, beacon etc
# Internal Lighting switches - includes no smoking, seat belts and storm
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range
# Engine Display - displays N1, N2, EGT
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")
# Navigation Display (ND)
# Primary Flight Display (PFD)
# System Display (SD/ECAM)
# Multi-Function Display (MFD) screens - display FMGS information
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information
# Engine Master Switches
# Radio Management Panel (RMP)
# ECAM selection switches
# Flaps lever
# Speedbrake/Ground Spoilers lever

The MFD and KCCD combination would be one unit in previous Airbus aircraft (ie: A320, A330, A340) and called a Multifunction Control Display Unit (MCDU)

The Airbus philosophy for the overhead panel is so called "lights out", that is during normal flight nothing should be illuminated on the overhead panel. However the opposite is true for the Flight Control Unit (FCU) on the glareshield; the Flight Director, one of the Auto Pilots and Auto Thrust should be illuminated.

== Introduction to the FCU ==
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set;
* speed,
* heading,
* altitude and
* vertical speed.
This unit is common across all Airbus aircraft built from the A320 onwards. Each of the four Flight Guidance parameters (ie: speed, heading, altitude, V/S) can operate in either "''selected''" or "''managed''" modes when the autopilot is engaged. The current Thrust, Vertical and Lateral modes are shown across the top line of the Primary Flight Display (PFD) as ''Flight Mode Annunciators'' (FMA).

'''Selected Mode''' 
Selected Mode is engaged when the knob is pulled by using the '''Middle Mouse Button''' (MMB). Use the '''scrollwheel''' on your mouse to change the value for that parameter, you can also dial in a value with the scrollwheel while the parameter is in managed mode, and it won't affect the current flight controls until you engage selected mode. The specific Flight Guidance Modes for each of the parameters are;
{|border="1"
! Flight Parameter
! Specific Selected Modes
|-
| SPEED || SPEED, MACH
|-
| HEADING || HDG
|-
| ALTITUDE || ALT
|-
| Vertical Speed || V/S
|}

If both Altitude and Vertical Speed parameters are in selected mode, the flight guidance with follow the vertical speed until the specified altitude has been reached, then the aircraft will remain at that altitude until the altitude value is changed or the altitude parameter managed mode is engaged.

If you don't have a scrollwheel on your mouse, you really should consider getting one, however as a workaround you can change the value of selected mode parameters by pressing F11 to bring up the autopilot dialog window, however you can only change values for a parameter when it is in selected mode. If you do have a scrollwheel and a two button mouse, you shouldn't use the F11 Autopilot dialog window, as the Auto Flight System will overwrite your set values when in managed mode.

'''Managed Mode''' 
Managed Mode is engaged when the knob is pushed by using the '''Left Mouse Button''' (LMB) (which may be on the right if you swap your mouse buttons around because for example you are left-handed). When in Managed Mode the value for the parameter will change to a number of dashes "-". You should only use Managed Mode if you have built a flight plan in the FMS on the MCDU screen. Managed Mode is managed by the Flight Management System and is based on the phase of flight and the flight plan entered depending on the parameters;
{|border="1"
! Flight Parameter
! Managed Mode name
! Managed function
|-
| SPEED || THR CLB, THR CRZ, THR DES || Based on phase of flight from Climb, Cruise and Descent and data entered in PERF page on FMS
|-
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach
|-
| ALTITUDE || CLB, ALT CRZ, DES, G/S || Follows altitude restrictions in the autopilot flight plan and configured cruise altitude in FMS or the Glidescope signal on NAV1 frequency during approach
|-
|}

Generally pilots engage the autopilot not long after take-off and leave it engaged until they have visual contact with the runway and use a combination of selected and managed modes during the flight.

= QFA231 =
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.

== Pre-flight ==

'''Fuel Estimates''' 
Our fuel estimates for this flight are around 20 000kg for the 1 180 NM (which is less than 10% of the range of the aircraft) which is almost impossible to achieve for this aircraft, so we will refuel around 60 000kg.

==== Flight Plan ====
Cruise: FL350 
YSSY depart 16R 
SID: KAMPI 1 
GEROS 
STAR: ARADI 4B 
NZAA approach 05R 

'''Starting FlightGear''' 
Start FlightGear with the following options;
{|border="1"
!Option
!Value
|-
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)
|-
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir>
|-
| atlas || socket,out,1,localhost,5500 udp
|-
| airport || YSSY
|-
| parkpos || Intl057
|-
| timeofday || afternoon
|-
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)
|-
| aircraft || A380
|-
| enable-real-weather-fetch ||
|}

In a different terminal window start Terrasync with a command line something like; ''"nice ./terrasync -S -p 5500 -d <terrasync-scenery-dir>"'' also if there is ATC controlling the airport you may want to start FGcom if you have a headset with microphone.

==== Fuelling and Weight ====
Adjust your view to the System Display '''(11)''' so that you can read the GWCG and FOB values, then from the menu select ''Equipment'' > ''Fuel and Payload''.
The optimum Centre-of-Gravity value (GWCG) is around 32%, however values between 30% and 40% can be used depending on fuel burn estimates (ie: the further you have to travel, the more fuel you can burn, the more the offset towards 40% it can start at, as the CG will go towards 40% as we burn and transfer fuel)
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs
* adjust fuel tanks 4 and 5 to around 9500 lbs
* adjust fuel tanks 6 and 7 to around 9200 lbs
* adjust fuel tanks 8 and 9 to around 7500 lbs
* check GWCG if it is above 36% then
*# add fuel to trim tank number 10 and,
*# add cargo to the bulk and aft cargo areas
* if it is less than 32% then;
*# reduce fuel in the trim tank 10 and,
*# add cargo to the forward cargo area and,
*# reduce cargo from bulk and aft cargo area
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity

==== Pre-flight Checklists ====
There are two checklists presented here, the first is a more complete preparation checklist that is performed upon entering the cockpit, the second pre-flight checklist is performed on every departure.

===== Cockpit Preparation Checklist =====
The cockpit preparation checklist is done at the first flight of the day or where there has been a change-over of crew. It starts at the top left-hand corner of the overhead panel, moves down the left hand-side of the panel, then start at the top of the middle of the panel and work your way down, then across the glareshield panel from left to right, then straight down the front panel and then pedestal.
* move your way down and check each section;
*# ADIRS
*# Probe and Window Heat
*# Flight Control (F/CTL)
*# Fuel Jettison
*# Evacuation
*# Emergency Electrical Power
*# Entertainment
*# Oxygen
*# Calls and Wiper
*# Engine Fire
*# Hydraulics Panel
*# Fuel Panel
*# Electrical Panel
*#* ensure nothing is selected OFF
*#* click ON if EXTERNAL power is AVAIL
*# Cargo Air
*# Air Panel (ensure packs and hot-air are OFF)
*# Cargo Smoke
*# Vents (avionics fan should be on if heavy rain)
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)
*# External Lighting (only NAV lights should be ON if the aircraft is powered)
*# Engine Start (should be in NORM position)
*# click the APU '''Master Sw''' ON
*#* the '''APU''' ECAM page should be automatically displayed
*# Cabin Pressure (should be in AUTO mode)
*# Internal Lighting
*#* click ON '''STORM''' if you are flying at night
*#* click the '''NO-SMOKING''' switch to AUTO

Now move to the Glareshield;
* starting with the EFIS panel, click the darker coloured outer ring of the Barometer knob for either hectopascals or inches of mercury, use the mouse scrollwheel on the lighter coloured inner knob to adjust the barometer value to the current pressure reported under the menu option ''Environment'' > ''Global Weather''. Each increment of the barometer value is 0.33 hPa, so it takes three increments to increase from 1013 hPa to 1014 hPa.
* click the Flight Director ('''FD''') ON
* moving down the front panel, check the lower message section of the E/WD
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)
* moving down to the pedestal, check the System Display permanent data area, that the time is correct, the temperature is correct, Fuel On Board is correct, and Gross Weight is correct
* ensure all '''ENG MASTER''' switches are in the OFF position
* by now the APU should be supplying power, click the '''APU''' button on the ECAM selection panel if it is not currently displayed, check supply voltage and the word 'AVAIL' is present
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)

===== Pre-flight Checklist =====
The pre-flight checklist is less arduous than the preparation checklist and is performed on every departure once route verification has been completed, about 15 minutes before departure.

This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.

==== Entering Flight Plan ====
Adjust your view and zoom into the left-hand captains MCDU display, ensure you can see the full display and the MCDU keyboard and num-pad, this first page is the 'INIT' page for the 'ACTIVE' flight plan.
To use the MCDU, you use your mouse to click inside a field, then click on the keys on the MCDU keyboard and num-pad below (don't use your physical keyboard to enter values)

'''ACTIVE INIT page''' 
[[File:A380-FMS_01.png|none|450px]]
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''
# click inside the ''TO'' field and enter our destination airport '''NZAA'''
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.

'''ACTIVE DEPARTURE page''' 
[[File:A380-FMS_02.png|none|450px]]
# click on '''16R''' from the list of runways
# now click on '''SID''' to go to the next page

'''ACTIVE DEPARTURE SID page''' 
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page

'''ACTIVE ARRIVAL page''' 
# click on '''05R''' from the list of runways
# now click on '''STAR''' to go to the next page

'''ACTIVE ARRIVE STAR page''' 
[[File:A380-FMS_03.png|none|450px]]
The two small up/down arrows at the end of the list of STAR procedures show that more options are available, you can click on the down arrow to go the next list of options, and the up arrow to go back.
# click on '''ARAD4B'''
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.

We are going to add an extra waypoint (in future versions you will be able to modify the flight plan from MCDU, however for the moment we use the Route Manager dialog to do this)
# From the top menu click on ''Autopilot'' > ''Route Manager''
# click on the line for "KAMPI"
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added

'''T.O. PERF page''' 
Finally we set and review the takeoff performance data, from the INIT page;
# click on '''T.O. PERF'''
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft
# review and modify the '''TRANS'''ition altitude (not be confused with the transition level where you would set the pressure barometer to ''STD'') that is appropriate for the area of the departure airport.

Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.

Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.

== Start-up ==
With most of the passengers on-board and cargo loaded, it's almost our scheduled time for pushback. Close the cargo doors by pressing 'd' and 'D' on your keyboard, it will take some time for the doors to close (future release will allow clicking on the doors to open/close), watch the System Display '''DOORS''' page as the cargo door symbols turn from Red to Green. Do the same for the passenger doors by pressing '!' (Shift-1) then '@' (Shift-2) and the ECAM DOORS page will show the symbols turn Red to Green.

==== Before Start checklist ====
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button
# click OFF any external power sources
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)
# check all doors are closed (should all be green)
# check '''thrust levers''' are at IDLE
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)
That completes the 'Before Start Checklist', you should now have obtained clearance for startup and pushback, and made contact with the ground crew for pushback who will request you to release the parking brake ('''Shift-B''') to begin the pushback during or after the engine start procedure.

[[File:A380-overhead-start_01.png|none|450px]]
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.

==== Automatic Startup Procedure ====
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel
# announce "Starting Engine 2 and 3" to ground crew
# click ON '''ENG MASTER 2''' with your left-mouse-button
# the '''ENGINE''' ECAM page should automatically be displayed
# once N2 has reached 10%, click ON '''ENG MASTER 3'''
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases
# once N2 for '''ENGINE 3''' has reached 25%;
#* announce "Starting engine 1 and 4" to ground crew
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)

With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'

==== After Start checklist ====
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel
# check '''GND SPLRS''' are armed, RUD TRIM is reset
# set the '''FLAPS''' to 2
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)
# click OFF '''APU MASTER''' Sw using left-mouse-button
# announce "Clear to Disconnect" to ground crew

while waiting for the ground crew to clear turn the park brake on by pressing Shift-B, check the E/W Display to see if it is ON.
Request taxi instructions from Ground ATC.
Once the ground crew are cleared and you have taxi instructions;
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button
# click to ON '''WING''' on the overhead external lighting panel
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night
# press Shift-B to release the parking brake
# increase throttle and taxi at around 15knots as directed by ATC to the holding point
# while taxing to the holding point, dial-up a selected heading of 158

== Take-off ==
We should now be lined-up on the runway waiting for clearance from ATC.
# on the EFIS panel, set the radar range to 20nm
# check GND-SPOILERS are armed, and the auto-brake is set to RTO
# check selected HEADING is our initial heading (usually the same as the runway)
# check the Flight Director is enabled
# check flaps at 2
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode

Once we have clearance for take-off;
# increase throttle so N1 (the second line from the top) is around 50%
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')
# as we are doing a de-rated takeoff, advance the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line FMA of the Primary Flight Display.
# at 100knots the First Officer should check the Engine display and call-out "Power Set"
# at V1 speed the First Officer should call-out "V1", at which point the Pilot In Command should take their hand off the throttle levers
# at Vr speed the First Officer should call-out "Rotate"
# pull back on the sidestick and try to aim for an angle a bit less than the 10 degrees line on the HUD
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''
# adjust the angle to allow the speed to increase to around '''200 knots''', then press the Auto Pilot (either AP1 or AP2 depending on which seat the Pilot in Command is sitting)
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent
# the first officer should turn ON the air '''PACK 1''' and '''PACK 2''' before 4000ft
# at around 4000ft reduce the flaps to 1
# at around 5000ft retract the flaps (to 0)
# the first officer can turn off all the external lighting at this point

== Climb and Cruise ==
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''
# if ATC direct you to a specific altitude;
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode
## you can also set the V/S at the same time, dial-up a vertical speed and use the middle-mouse-button to engage the Selected Mode
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"
## clear the V/S mode by returning it to Managed mode with the left-mouse-button
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button
# at 18000ft use the left-mouse-button and click with the left-mouse-button on the inner barometer knob on the EFIS panel so it displays "STD"
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''
# if you need to step to a different altitude;
## dial-up the new altitude value
## click with the '''middle-mouse-button''' to engage the Selected mode
## the PFD will change to "ALT" mode
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude

== Descent ==
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;
# the '''DES''' mode will be armed
# and the throttle will be reduced
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track
you may need to use a small amount of speedbrake using CTRL+k to increase and CTRL+j to decrease the amount of spoilers to control the speed during the descent phase.

''Note from another FG user: on my machine, the Ctrl+k and Ctrl+j don't look like they command the speedbrakes, when i ctrl+j several times, the plane enters an uncontrolled spiral dive, a bit as if these keys would instead command some kind of yaw trim
''

''Note from another FG user: on my machine, I can use buttons k and j to increase/decrease speedbrakes. The Ctrl + k/j doesn't do anything.''

== Landing ==

At around 10 000ft you will need to switch over the radio frequencies for the ILS. As long as you have entered the STAR route with the MFD the standby NAV1 frequency will be that of the ILS for the runway you selected, simply switch it over to the active frequency.

If you need to track away from the STAR route, dial-up the heading and use the middle-mouse-button for Selected mode, the FMA on the PFD will now display '''OP DES''' as ''engaged'' and '''DES''' as ''armed''. In '''OP DES''' mode with speed in managed '''THR DES''' mode, the engines will go to idle, and the Flight Path Angle of the aircraft will be varied to meet the currently set speed (either set by the FMS in managed mode, or set by the pilot in selected mode).

When the localiser is in range, '''LOC''' will be ''armed'' and the dot indicators will appear at the bottom of the PFD, press the LOC button just below the HDG knob to engage the localiser when you are within the first dot range.

At around 3000ft the speed should be around 230knots, extend the gears and turn on external lighting for Nose, Landing and Wing lights.

Set the Selected speed to '''200''' knots

When the Glideslope is in range, '''G/S''' will be ''armed'' and the dot indicators will appear on the right side of the PFD, press the '''APPR''' button below the V/S knob to engage the Glidescope and Localiser.

When you are within visual of the runway, reduce the selected speed to '''180 knots''', control your speed by extending the flaps to 1

[[Category:Airbus]]

A-4F Skyhawk operations manual

2012-10-06T17:47:02Z

Thebgland:

{{main article|Douglas A4 Skyhawk}}

By Andy Ross

== Fundamentals ==

=== Grains of Salt ===

I am not a real-life pilot, and I am certainly not a Naval Aviator. The information and instructions here are based on my own research and experience with the FlightGear A-4 flight model. Most of it has at least a basis in truth, but all of it contains at least a little guesswork on my part. Anyone with better sources should feel free to correct this document as needed.

On the whole, I find the FlightGear Skyhawk to be challenging and realistic to fly. Unlike most (perhaps all) consumer military simulators, the flight model for the A-4 is not "dumbed down" to make dogfighting easier for novices. All of the same caveats and procedures that I have read about in books seem to apply well to the FlightGear model. Most other simulators seem to have one or two areas which just "feel" wrong and/or fail to match presumably authoritative sources.

=== Flight Qualities ===

The Skyhawk has a low aspect ratio delta wing. This means that it experiences a very gradual increase in lift with angle of attack, and only a very mild stall at a much higher AoA than a straight-winged aircraft would. While this makes handling generally more benign, it has two important effects that a pilot transitioning from lightplanes must be aware of.

First, while there is no sudden loss of lift at moderate to high AoAs (20-30 units) in the Skyhawk, the induced drag continues to increase with AoA. This means that, when producing maximum lift, the A-4's wing is also producing far more drag on a relative basis than the conventional wing would. The net effect is that low-aspect wings "bleed energy" when at high angles of attack in ways that can be surprising to straight-wing pilots who tend to assume constant speed across maneuvers. This applies both to high-G turns and also to approaches, which are flown in the same high-AoA regime. While a Cessna 172 can change attitude and climb for a go-around with a simple throttle setting, the A-4 is capable of only a very modest climb in approach configuration.

Second, the ability to "use" those higher angle of attacks means that the pilot's stick is correspondingly more sensitive. Full back-stick at stall speed in a Cessna will produce perhaps 16 degrees of AoA. No more elevator authority is needed, because beyond that the aircraft will be stalling anyway. Full back-stick in the A-4 produces at least twice as much pitch change. The pilot needs to be aware of how much elevator is needed for a given maneuver. Simply pulling the stick back to the stop is likely to be very surprising and lead to (depending on the flight environment) a stall, an airframe overstress, or a departure and/or spin. Be gentle.

The A-4's ailerons are tremendously effective. At 350 knots, the real aircraft has been measured to roll at 400° per second, which is matched rather closely by FlightGear. This can be loads of fun, but it also makes "rolling into" a tight turn rather touchy. Be prepared to use some reverse aileron to halt your roll at your desired bank angle or else you may well overshoot.

While the A-4 is an attack jet, and therefore much zippier than a 747 or Cessna 172, its thrust to weight ratio is not in the "why bother with wings" class such as modern fighters like the Su-27 or Rafale. You cannot simply point the Skyhawk's nose to the sky and expect it to climb, nor can you escape from piloting errors simply by applying throttle. It is a pilot's aircraft, and needs to be flown within its capabilities.

=== Cockpit ===
[[File:A4-F-Panel.jpg]]

The Skyhawk cockpit is simple and spare, even when compared to its contemporary aircraft. Unlike modern fighters, all the gauges are convention analog ones and there is no HUD. Nonetheless, the cockpit should be accessible to anyone with experience in lightplanes such as the Cessna 172. The airspeed indicator, vertical speed gauge, and altimeter all operate identically to the ones you are familiar with, and there is a conventional HSI/gyrocompass at the bottom of the panel.

The "scrolling card" artificial horizon is replaced in the A-4 by a full three degree of freedom attitude indicator which shows heading in addition to pitch and roll. It has no travel or rotation limits, making it suitable for aerobatic flight. At the bottom of the instrument (hard to notice if you do not know it is there) is a turn rate indicator.

Something not seen in passenger aircraft cockpits is an accelerometer in the top left corner of the panel. This measures vertical pilot acceleration in G's, and is useful in maneuvering flight to tell the simulator pilot what the real pilot would be feeling. It is also useful in IMC conditions to detect trim/airspeed mismatches. An aircraft flying at trim speed will have show exactly 1G on the gauge. The accelerometer can thus be used as an aid to trimming in conditions where there is no visible (and pitching) horizon to look at. It has a higher resolution for this purpose than the attitude indicator.

The engine in the A-4F is a Pratt & Whitney J52-P8A non-afterburning turbojet which develops 9300 pounds of static thrust under standard sea level conditions. Thrust on a jet is typically measured using N1 (first stage) turbine RPM, expressed as a percentage of the maximum continuous operating speed. (Actually, the real A-4 has an exhaust pressure ratio gauge as well, but that is not modeled yet). The engine is allowed to run as high as 105% during takeoff, but should be kept under 100% at cruise. Be aware that jet engines, unlike piston engines, take several seconds to "spool" to a new power setting once the throttle is moved.

=== Angle of Attack ===

In Navy jets, approaches are flown at a specified angle of attack rather than at particular airspeeds. This allows for a single set of procedures to be used for landings at all gross weight conditions. In a commercial jet flying a predetermined flight plan, there is plenty of time to look up values for approach speed based on current fuel load. When landing an attack jet on a carrier, that is less of an option.

There are two angle of attack indicators in the cockpit. The first is a rotary dial at the top of your panel, which indicates angle of attack in "units". These are not degrees, but simply arbitrary numbers specific to an aircraft model. There is a small tick mark at the 3 o'clock position that indicates the ideal approach AoA. Final approaches under all conditions should be flown at this AoA.

To aid in comprehension during approach, there is also an AoA "indexer" at eye level attached to the windscreen. This is a 3-element lighted display which displays five conditions: on speed (yellow center circle), slightly slow (yellow circle and downward-pointing arrow indicating "push the nose down"), slightly fast (yellow circle and up chevron indicating "pitch up"), very slow (no circle, green downward chevron meaning "pitch down and speed up!"), and very fast (no circle, red upward chevron meaning "pitch up and slow down!").

== Takeoff ==

# Flaps up. The A-4 uses split flaps, which create too much drag to be useful as takeoff lift enhancers. The wing slats are automatically actuated, and do not require pilot operation.
# Elevator trim neutral, or very slightly nose-up. Do not trim for approach speed, as this is too slow for a takeoff climb and will cause the nose wheel to lift too early in the takeoff run.
# Brakes off. Throttle to full. Begin takeoff roll.
# Rotate. Rotation speed for full fuel and no external stores is 145 knots. Rotation in the A-4 is a rapid process, pull the stick back to approximately one half travel, raise the nose to 20-25 units of AoA and hold it there. The aircraft will lift off into ground effect.
# Gear up immediately.
# Do not attempt to climb yet. Best climb speeds in the Skyhawk are 300 knots or greater. Simply hold the nose steady against the horizon and allow airspeed and vertical velocity to increase gradually. Alternatively, on long runways a "Blue Angels" takeoff has the pilot (carefully!) hold the aircraft in ground effect as AoA drops and speed increases. Then, at 250-300 knots, pull up into a 2-3G climb to a deck angle of 45° or so. This is lots of fun and looks very cool in external view.

== Landing ==

=== Approach and Pattern ===

# Plan on arriving over the airfield at 1000-2000 feet AGL and 350 knots. At cruise speeds, the A-4 is a very slippery aircraft and takes a long time to slow down, so be prepared.
# Overfly the desired runway while descending to 1000 feet AGL. Note the runway heading on your gyrocompass. The A-4 has poor rearward visibility; you will not be able to see the runway for reference during significant portions of the landing pattern, and knowing you are on the correct heading is important.
# At the end of the runway, cut throttle (if you have not already) and pull into a 2G, 180° turn to the left. This is called the "brake", and is intended to reduce speed.
# As speed drops through 250 knots, lower the gear. At 200 knots (you should now be in level flight on the downwind leg) begin adding flaps gradually as the AoA increases. The goal is to get the aircraft trimmed (and powered) for level flight at the on-speed AoA of 17.5 units by the end of the downwind leg. ''Warning: with full flaps and at on-speed AoA, the aircraft will want to descend very steeply. Increase throttle proactively as you add flaps, or you will pancake.''
# At the end of the downwind leg, approximately one mile from the runway threshold, begin the turn onto final. In approach configuration, the aircraft must be handled gently; use no more than 30° of bank. Watch for the runway and adjust as necessary. The goal is to roll out of the turn on glideslope and on speed.

Actually, the simplest approach procedure has the pilot line the aircraft up on the centerline far out (7+ miles) from the threshold and at 3000-4000 feet AGL. Pull a hard turn onto final to brake, drop the gear and the flaps, trim to on-speed, and only then start worrying about lineup and glideslope. You will be very high, but the aircraft descends very steeply in approach configuration. Simply drop to the proper glideslope, apply power, and then nurse the throttle all the way to touchdown.

This provides more time per approach to practice the very important throttle technique without having to worry about flying a level pattern at 1000 feet AGL while in approach configuration (which is also very difficult). You can then practice flying level turns in approach configuration, and put it all together later.

=== Final Approach ===

[[File:A4-F-Approach.jpg]]

Fly the final approach using power to control pitch and altitude. This advice is repeated in pilot manuals everywhere, but nowhere is it more important than when flying a jet at very high angles of attack. If you try to correct for a low approach by pulling back on the stick, you will create only a little bit more lift and a lot more drag. Your airspeed will drop rapidly and you will pancake into the ground well short of the threshold. To make matters worse, the engine takes several seconds to "spool" to a new power setting once you move the throttle, making this kind of pancake maneuver very difficult and dangerous to recover from once it happens. Successful landings involve careful attention and practice. Hints and tips that I have found useful:

Trim well. If you fly the approach while trimmed for the proper AoA, then the aircraft will always be on-speed, or very nearly so. If you try to fly a constant AoA approach with the stick, you will rapidly find yourself becoming insane (or dead). Once trimmed, you should need nothing more than throttle and gentle aileron control (and perhaps a gentle nose-down push on the stick once in a while to correct a small glideslope deviation) throughout out the approach.

Get your eyes out of the cockpit. The gauges do not tell you enough. Instead, watch the position of runway threshold. With the aircraft trimmed at approach AoA (you do have it trimmed at approach AoA, right?), the aiming point should be placed about 1/3 of the way from the top of the panel to the windscreen crossbar. If you are too high, you should be aiming the threshold a bit higher on the windscreen; too low means you should be trying to lower it.

Remember how power and trim interact. The trim (again, you have trimmed the aircraft to fly on-speed, right?) selects an airspeed for level flight. If the aircraft is flying faster than trim speed, it will be producing more lift and (this is the important part) pitching upward. If it is flying slower, its nose will be dropping. Pay attention to this tendency. If you have applied power to reduce your rate of decent, but the nose is still going up, reduce power to keep the aircraft at on-speed or else you will overshoot and climb too high. If the nose is dropping nicely to where you want it, start adding power to reduce the rate of drop before you reach the attitude you want lest you drop below the glideslope.

Don't look at the engine RPM gauge once you are stable on the glideslope (unless you think there is a problem, of course). Approach power settings will vary widely depending on aircraft gross weight. Learn to use small throttle movements and listen for the changes, rather than trying to find a specific RPM setting. Try flying approaches at many weight settings to drive this point home; if you are using the RPM gauge as a crutch, flying at different weights is a good way to break this habit.

Bug somebody to implement approach lighting. On real runways, you will have a VASI or PAPI to tell you where you are on the glideslope. On carriers or at Naval Air Stations, you will have a "meatball", which is broadly similar but provides more information - see the carrier "Nimitz" in FlightGear. In the meantime, you can use your ILS receiver as a proxy. With practice, however, I have found that making an approach without glideslope information is not excessively difficult.

=== Touchdown ===

'''Do not flare'''. To begin with, flaring is not part of Navy procedures. Aircraft landing on carriers do not have that option. It is also not easy to do at high angles of attack. A Cessna will cross the threshold with lots of "reserve lift" available to a pilot who pulls back on the yoke, but the Skyhawk is much nearer to stall AoA and producing far more drag than the lightplane would be. It is very easy to "flare" into an unrecoverable stall 30-40 feet in the air.

Instead, simply fly the aircraft onto the ground. If you are on the correct glide slope, your vertical velocity should be 700-1000 feet per minute. At this speed, the aircraft should land firmly but solidly on its gear. If you are coming in shallow, it is possible that it will settle into ground effect without actually touching down. If you are coming down fast and do not have time to correct the glide slope with power, be prepared for a bounce (but again: do not try to correct this with the stick).

'''Do not cut power''' until you are either on the ground or level and in ground effect. It is possible, and likely if you are coming in steep, that the aircraft will bounce on landing. If you cut power before the bounce, you will suddenly find yourself 20-30 feet in the air with an idle engine and well below stall speed. This is bad.

As the aircraft touches down, immediately apply some forward stick to keep the main wheels on the ground. Retract the flaps. Slowly push the nose wheel onto the ground with more forward stick. When trimmed for approach, the aircraft will want to bob up; keep the nose wheel down. Once all three wheels are down, brake.

Alternatively, if you have a long runway, leave the nose wheel in the air and slowly apply back stick until it settles down on its own at 80-100 knots before braking. This minimizes use of the brakes by allowing aerodynamic drag to slow the aircraft as much as possible, and works well also. I don't know what standard Navy procedure was for the landing rollout.

[[Category:Military aircraft]]

User talk:Gijs

2012-10-05T01:01:41Z

Thebgland: Requested a page edit.

{{Archives|[[/Archive 2008-2011|2008-2011]]}}

== Page in need of repair ==

I would love to improve airports and scenery, but http://wiki.flightgear.org/Howto:Make_an_airport is in need of some editiong. It is easy to get lost in,it leaves out steps, and a new developer has no ability to improve his skills. You clearly have the knowledge of how to model airports. Please spread that knowledge.
-----THEbgland--- 21:01, 4 October 2012 (EDT)
 
 

== Idea: Suggested flights with stars ==

How 'bout this idea... Make a star rating system thingy for [[Suggested Flights]]? A template with 0 to 5 stars we could add to a flight so that users can rate the flight.
I dunno how to make it else I would... :)
[[User:PH-JBO|PH-JBO]] 19:38, 22 December 2011 (EST)
: We could use the rating system that is used for aircraft/airports, but that'll require each flight to be on a special page; which is quite a hassle IMO. Don't know of any other option right now...
: [[User:Gijs|Gijs]] 16:24, 23 December 2011 (EST)

== Renaming newly categorised files ==

I saw in [[Special:RecentChanges|recent changes]] that you have renamed many of the files that I have categorised, and I just want to say: {{thumbs up|13}} Thank you! --[[User:Johan G|Johan G]] 15:15, 14 February 2012 (EST)
: Not intentionally only files that you categorised (apparently you categorised ALL file :P), but files that had the basic fgfs-screen names, which is very very bad...
: I'd like to thank you for all the hard work you're doing on the wiki these days. Good to see some more activity!
: [[User:Gijs|Gijs]] 15:17, 14 February 2012 (EST)
:: I didn't really categorise ''all'' files (there's still about 1400 to go...), but thank you anyway. ;-) —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:07, 13 March 2012 (EDT)

== Template documentation ==

Just a heads up.

While having a bit less presence in the FlightGear community (probably a bit of recoil from straining myself, but also due to real life) for a while I drop in now and then for a peek on the Wiki.

Recently I noticed that one of my sup-pages ([http://wiki.flightgear.org/index.php?title=User:Johan_G/Wiki_improvement&oldid=40953 User:Johan G/Wiki improvement]) was a bit different, but noticed I'm the only one editing there. Checking the used templates gave the explanation. Specifically the <nowiki>{{</nowiki>[http://wiki.flightgear.org/index.php?title=Template:Tl&diff=42423&oldid=40924 tl]<nowiki>}}</nowiki> template. ;-)

When you add the <nowiki>{{</nowiki>[[Template:Informative template|informative template]]<nowiki>}}</nowiki>, make sure you leave the <code><nowiki><noinclude></nowiki></code> tag where it was. If you add empty lines and/or spaces, those will be added each time the the template is used with unwanted results. Remember that a space in the beginning of a line will put that remaining text on that line in a "code box". ;-)

''In this specific case the previous edit looked like this,''

<nowiki>{{[[Template:{{{1}}}|{{{1}}}]]}}<noinclude></nowiki>
...

''while the new edit looked like this (spaces represented by underscores),''

<nowiki>{{[[Template:{{{1}}}|{{{1}}}]]}}_</nowiki>
_
<nowiki><noinclude></nowiki>
...

''The result is that''
The template <nowiki>{{</nowiki>informative template<nowiki>}}</nowiki> is a template documenting templates.

''instead of being rendered like this,''

The template <nowiki>{{</nowiki>[[Template:Informative template|informative template]]<nowiki>}}</nowiki> is a template documenting templates.

''got rendered like this:''

The template <nowiki>{{</nowiki>[[Template:Informative template|informative template]]<nowiki>}}</nowiki>
is a template documenting templates

Otherwise I see that you are doing a wonderful job.{{thumbs up}} Just don't strain yourself, will you. :-)

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:49, 13 March 2012 (EDT)

== Unsigned template + Archive pages ==

I had been thinking of moving {{tl|unsigned2}} to {{tl|unsigned}} for a while, but not done it. Good idea to keep the redirection page.

On a totally different matter, when you get to the point when you consider your talk page is to long I hope that you do not delete parts of it, but instead move it to a archive in the form of a subpage, in case you or someone else want to have a look on it in the future.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:03, 19 March 2012 (EDT)

==Deleting of a user page?==
Hi Gijs, erm, I see you deleted my User Page? umm.. Why?
--[[User:Sebasgokart|Sebasgokart]] 10:24, 24 March 2012 (EDT)

: It was deleted because someone else wrote down some discussion about your VA edits being spamlinks or not. Apart from that there was no content on the page, so it was deleted (all the way back in October!!).
: [[User:Gijs|Gijs]] 12:07, 24 March 2012 (EDT)

== Article considered for deletion ==
Hi Gijs, my page is also suggest for being deleted because aparently, someone want to make a page with all the VA which does already exist !
So, I ask you (or if you have good reason) not to delete my articles because it's really anoying to make everyday the same roll-back on the page.
Thx, [[User:Bastien.D|Bastien.D]] 20:00 01 April 2012 (EDT)

: Please see my message on your talk page: [[User talk:Bastien.D#Removing templates]]
: [[User:Gijs|Gijs]] 16:10, 1 April 2012 (EDT)

== Virtual airline template ==

{{thumbs up}} Thank you for the work on [http://wiki.flightgear.org/index.php?title=Template:Virtual_airline_summary&oldid=46998 Template:Virtual airline summary]! I could not have done it better for at least a couple of weeks. :-D —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:21, 9 April 2012 (EDT)

== Missing GPL logo image ==

I noticed that the image for the GLP v.2 logo at the bottom right of every page is missing, but I do not know for how long it has been missing. I do not know where I should point you to help you fix it, yet, but on the source for a downloaded page it is located as below (note the empty <code>src</code> attribute):

<syntaxhighlight lang="html4strict">

<div id="footer">
...
<img src="" alt="GNU GENERAL PUBLIC LICENSE Version 2, June 1991" width="88" height="31"/>
...
</div>

</syntaxhighlight>

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 05:18, 15 April 2012 (EDT)
: I think it's never been there actually. MediaWiki templates do not support the GPL (by default), so it failed to display an icon. But I've removed it now. Will adjust the copyright text slightly as well.
: Thanks! [[User:Gijs|Gijs]] 05:42, 15 April 2012 (EDT)

== Delete article about non-existing partnership ==
Hi Gijs, Through this message on behalf of the group fgbr denuciar (Unitedfreeworld) be using our name in a partnership to build the 747-8i does not exist.
We ask that meets our request and delete the Wiki page that is in putting the group fgbr as a partner working with (Unitedfreeworld).
Here is the page created for them: [[Boeing 747-8i]]

Thank you for your attention.

The Group FGBr thanks.
My prefix is BR-WAG contact.

{{unsigned|07:21, 22 April 2012‎|Wagner Silva}}

: Hi,
: feel free to remove UnitedFreeworld from the author tag. It's a wiki after all ;-) I see no reason the remove the article, just because there is one little fault in it...
: [[User:Gijs|Gijs]] 07:05, 22 April 2012 (EDT)
: PS: Please sign messages on talk pages with <code><nowiki>~~~~</nowiki></code> and do not overwrite existing discussions. Instead, click the "Add topic" link at the top of the screen to add a new subject.

== Old galleries and seemingly unused images ==

Just a heads-up. You probably should do a search before you delete unused images. I noticed that there are a lot of older galleries like e.g. [[FlightGear Newsletter January 2011#New aircraft]] that is not rendering the images. The file description pages will therefore indicate that the images are not in use.

The failed galleries might be a candidate for a bot job.

—[[User:Johan G|Johan G]] ([[User talk:Johan_G|Talk]] | [[Special:Contributions/Johan G|contribs]]) 03:56, 22 April 2012 (EDT)

: Hm, thought I fixed them all. Thanks!
: [[User:Gijs|Gijs]] 07:05, 22 April 2012 (EDT)

== The new main page layout ==

==== A few suggestions ====
* Please add [[Portal:Wiki]] to the Portals in the left-hand menu. (I guess you simply forgot to do that ;-)
* I strongly feel that there should be one single meeting place that is quickly and easily found, ''preferably not on a talk page''. See rationale below.

==== Rationale for a single meeting place ====
:''I'm sorry if you would feel that I am a bit pushy about this, but I feel this is very important.''

For a newcomer there doesn't seem to be a Village pump equivalent, where they can get a feel for the wiki community and ask their very first questions.

There are in fact several places, apart from [irc://#wiki@irc.flightgear.org #wiki@irc.flightgear.org] (wich is currently not mentioned on [[Portal:Wiki]]), used in a similar way (that may or may not be intended for that purpose), some of them being:
* [[Talk:Main Page]]
* [[FlightGear wiki talk:Community portal]]
* [[Help talk:Contents]]
* Your own user talk page ?

The biggest drawback with having such a place on a talk page is that you either have to know it's there, or you more or less have to find it by accident. Also having the more general discussion spread over several (slightly obscure) places add an element of confusion: How would one know where to ask questions, and would anyone have a look there to answer them?

Maybe the statistics on [[FlightGear wiki:Community portal]] could be moved to a separate page, and [[FlightGear wiki talk:Community portal]] could be moved to [[FlightGear wiki:Community portal]]?

A single place for discussion, that is quickly and simply found, would make it easier to reach all of the more active editors without having to resort to invite them all to discussion at their own user talk pages. Reach them for both questions, suggestions and collective coordinated efforts when needed. :-)

==== And last but not least ====
Great to finally see the new layout in action. Great work! {{thumbs up}}

I think it will be a lot easier to navigate around the portals and getting started editing the wiki, and continuing editing with the new layout. :-)

And when I'm at it: Great work categorising all the aircraft. I really mean it! :-)

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:18, 30 April 2012 (EDT)

Nice clean layout. Look forward to working with it...
[[User:Openflight|Openflight]] 07:17, 3 May 2012 (EDT)

== Deletion of Supported Peripherals page(s) ==

Hi Gijs, I was interested in looking at a list of supported joysticks, and followed a [red] link from [[FlightGear Hardware Recommendations]] to [[Supported Peripherals]]. I saw that you moved that page to [[Supported peripherals]] on April 7, 2011 at 11:46 with the comment "No need to capitalise all words in a title.", but then deleted that new page at 11:48 with the comment "deleted "Supported peripherals" ‎ (Copied)". Finally, on February 26, 2012, you deleted the original page because of "Broken redirect". This means that the page does not exist at any of the 2 locations anymore. Is there a way to get the content of the page back? Groetjes! (FYI just created my wiki account to talk to you ;) ) [[User:E2jk|E2jk]] 17:12, 17 May 2012 (EDT)

:I found one copy of the page (all lower case though) in the [http://web.archive.org/web/20100831112110/http://wiki.flightgear.org/index.php/Supported_Peripherals Wayback Machine]. Maybe this could be helpful in case the deletion can't be reversed... [[User:E2jk|E2jk]] 17:22, 17 May 2012 (EDT)

: Hi,
: I can restore the page (nice thing about Mediawiki is that it keeps a record of deleted pages), but I won't do it. The page only contained a small list of Joysticks that have a config file under <tt>[[$FG_ROOT]]/data/Input/Joysticks</tt>. It was far from complete and it's hard to keep such lists up to date. People better check the directory to see if (their version of) FlightGear support a certain joystick.
: I could be wrong of course, maybe there is a need for such a page...?
: Cheers, [[User:Gijs|Gijs]] 17:27, 17 May 2012 (EDT)
: PS: The capitalisation sentence was aimed at the title, not the contents of the article.
: PPS: Now that you have a wiki account, how about using it for a little more than posting on my talk page?! ;-)

::I do agree that this list could be difficult to maintain, but it still is a good resource for people that are thinking about buying new hardware (as is my case). In any way, having at least a link to the folder containing the config files would be nice, IMHO.

::Regarding the wiki, I've started FG for the first time today, so I'm still in full learning mode. Let's see if I have stuff to add/clarify in the coming period ;) [[User:E2jk|E2jk]] 17:42, 17 May 2012 (EDT)

==Deletion of images==
Hi Gijs,

any idea how I can delete images I uploaded, but I don't use anymore?
--[[User:HHS|HHS]] 16:39, 31 July 2012 (EDT)

: Hey,
: Not sure if "normal" users can actually do that, but if you can, it's like deleting a page. Go to the image's page, then click the little arrow next to the search field at the top right of the page and choose "Delete". If that doesn't work; add the {{tl|delete}} template and I'll deal with it.
: Cheers, [[User:Gijs|Gijs]] 18:12, 31 July 2012 (EDT)

== Ready icons missing in Infobox aircraft ==

The {{tl|Ready}} template is no longer called by {{tl|Infobox aircraft}}. For the details have a look at [[Template talk:Infobox aircraft#Ready icons]].

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:22, 16 September 2012 (EDT)

Autobrake

2012-10-01T13:00:47Z

Thebgland:

'''Autobrake systems''' reduce pilot workload during landing, by automatically applying smooth, even braking pressure to maintain a programmed deceleration value. They also reduce workload in a rejected take-off (RTO) scenario, helping to bring the [[aircraft]] to a halt as rapidly as possible.

The system is armed by the pilot, and then works automatically based on flight inputs, notably whether there is weight on the wheels (compression of nose or main landing gear struts). Most systems automatically disengage if the pilot makes a manual braking input.

In normal use, lower autobrake settings are used to prolong tyre, brake and runway surface life. Additionally, since the system measures total deceleration, use of other techniques to slow the aircraft, such as reverse thrust or spoilers, will contribute to deceleration and hence reduce the required brake application.

By way of example, the system in the [[777]] behaves as follows:

* Activation occurs with the nose gear strut compressed. Depending on setting, the target deceleration is 3, 5, 7 or 11 (max) ft-sec^2. Any pilot braking input will disengage the system. The braking effort can be changed before or during brake application.
* In RTO mode, the system arms when ground speed exceeds 80 knots, and activates if the throttles are moved to idle above that speed, while the aircraft is still on the ground (nose gear strut compressed). Once airborne, the system automatically disarms. RTO braking effort corresponds to the maximum autobrake setting, 11 ft-sec^2 deceleration.

== Related content ==
* [[Autobrake internals]] explains how to implement autobrakes in your aircraft.
* [[Auto-spoilers]]

[[Category:Aircraft instruments]]

Autopilot

2012-10-01T12:59:56Z

Thebgland:

[[File:Autopilot.jpg|thumb|270px|The autopilot setting dialog of FlightGear.]]

An '''autopilot''' ('''AP''') is a mechanical, electrical, or hydraulic system used to guide a vehicle without assistance from a human being. Most people understand an autopilot to refer specifically to [[aircraft]], but self-steering gear for ships, boats, space craft and missiles is often also called by this term.

The autopilot of an aircraft is sometimes referred to as "George".

== Autopilot in FlightGear ==
We have a generic one and custom ones written for a certain aircraft, which are supposed to simulate particular autopilot types/models for a specific aircraft.

The generic one can be used for aircraft which don't have a custom autopilot implementation, and seems to work reasonably well on most aircraft using [[JSBSim]]. You can enable it with the "Autopilot Settings" which you can open using the F11-key or in the menu bar using the "Autopilot" item.

In real life, aircraft have specifically-programmed/customized autopilot system to cater for individual aircraft characteristics.
To a certain extent, Flightgear has the possibility to simulate this as well.

So it is possible to write a custom <tt>autopilot.xml</tt> to override the generic autopilot implementation.
This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both.
Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot/aircraft-specific features (for examples, see the b1900d or Citation Bravo in Git/HEAD). [[File:Custom-autopilot-dialog.png|thumb|300px|A custom autopilot dialog]]

Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots).
For example, the [[Piper PA34-200T Seneca II|Seneca II]] and the [[Piper PA-24 Comanche|Piper Comanche]] autopilots can be only used from the virtual cockpit using custom panel hotspots. This is in fact increasingly the case, as new emulations of autopilot systems are implemented using the built-in scripting language [[Nasal scripting language|Nasal]] which provides for much more flexible system design and functionality, compared to the relatively static way of describing autopilot systems and their relevant and modes using only the [[XML]]-configurable autopilot system. In fact, to properly emulate more complex autoflight systems that provide support for more abstract flight modes, using a combination of XML-configurable PID controllers and Nasal is likely to be the most promising approach.

In general, it can be considered to be more complex to provide proper cockpit panel implementations than wiring up the autopilot properties to the standard autopilot GUI dialog, so if an aircraft's autopilot doesn't seem to work properly using cockpit panel hotspots, you may want to try using the standard GUI dialog instead.

Also, please note that not all aircraft/autopilot combinations provide full support for all features offered by the standard autopilot dialog. This may be due to an aircraft's completion status, but also due to technical limitations in certain aircraft/autopilot, so that only certain modes are provided.
This may also apply to aircraft panels, that are seemingly offering functionality that may not yet be implemented.

In addition, JSBSim also features support for a standalone autopilot implementation, that works without any dependency to FlightGear/Nasal.

For further information about programing autopilots in FlightGear look at [[Autopilot Tuning Resources]] and http://www.flightgear.org/Docs/XMLAutopilot/.

== Autopilot Settings ==
The AP Settings dialog can be found at '''Autopilot > Autopilot Settings'''.

=== Heading control ===
* '''Wings Level''': enable this to keep your plane horizontal- usually used at Go-Arounds.
* '''Heading Bug:''' located on the compass rose of your instrument panel is a movable heading bug, the purple triangles that are pointing at your runways heading (283 for KSFO default). This bug is moved around the rose by setting the Heading Bug. The heading bug can be used several ways. When hand flying the aircraft turn the bug to your desired heading. This way you will have a constant visual reminder. If [[ATC|Air Traffic Control]] gives you a new heading move the heading bug to the new heading and you have your visual reminder.
* '''True Heading:''' your true heading as shown on the compass (of the [[Head-up display|HUD]]) and [[Multiplayer Howto|MP Map]].
* '''NAV1 CDI Course:''' used for VOR-by VOR flying like in old days and used with [[ILS]].

=== Velocity control ===
* '''Speed with Throttle:''' speed will be regulated to the selected speed by controlling throttle.
* '''Speed with Pitch:''' your plane will be pushed down or up to reach the selected speed. This can not be used during takeoff, landing or low altitude flights. Doing so could cause a crash.
=== Pitch/Altitude control ===
* '''Vertical Speed:''' set the speed of vertical climb. Usually used as "feet per minute"
* '''Pitch Hold:''' pitch degrees of your plane. Use a negative number to lower your nose.
* '''AoA Hold:''' The Ange of Attack describes the angle of the wings compared to the direction of the circumfluent air. The lift of the wing depends on the AoA. A too high AoA will cause the aircraft to stall.
* '''Altitude Hold:''' the desired altitude of your plane in feet (FL1=100 ft, FL25=2500 ft etc.).
* '''AGL Hold:''' The Altitude about Ground Level. Usually the altitude is given about sea level.
* '''NAV1 Glideslope:''' The vertical slope which led the aircraft from the interception point down to Runway level-used only with [[ILS]].

=== FlightDirector Mode ===
The flight director computes and displays the proper pitch and bank angles required in order for the aircraft to follow a selected path. A simple example: the aircraft is in level flight on a heading of 045 degree and at an altitude of 15000 feet maintaining a speed of 260 kts, the FD bars are thus centered. Then the flight director is set to a new heading of 090 degrees and a new altitude of 20000 feet. The aircraft must thus turn to the right and climb. This is done by rolling to the right and pulling up. The roll bar will deflect to the right and the pitch bar will deflect upwards. The pilot will then pull back on the control column while rolling the aircraft to the right. Once he reaches the proper pitch and bank angle the FD bars will again center and remain centered until it is time to roll back to wings level (when the heading starts to approach 090). When the aircraft approaches 20000 feet the pitch bar will deflect downwards thus commanding the pilot to reduce pitch in order to level off at the new altitude.

The FD is generally used in direct connection with the Autopilot. Where the FD commands the AP to put the aircraft in the attitude necessary to follow a trajectory. The FD/AP combination is typically used in autopilot coupled low instrument approaches, (below 200 feet agl) or CAT II and CAT III ILS instrument approaches.

The exact form of the flight director's display varies with the instrument type either crosshair or command bars.

== Route manager ==
{{main article | Route Manager}}
The Route Manager in FlightGear is something like a very simple FMC- Flight Management Control/Computer.
In FGFS you can input a list of waypoints like NAVAIDS, Fixes and Airports, which the aircraft flies along. You can also add the altitude which the aircraft should have at a certain waypoint. So it is possible to let the aircraft fly along a certain route.

At the moment, it is not possible to add velocities or other constraints.

== See Also ==
[[Advanced Autopilot Tuning Tips]]

== Related content ==
* [[Autopilot Configuration Reference]]
* [[Howto: Design an autopilot]] for a FlightGear aircraft

[[Category:Aircraft instruments]]

Aircraft carrier

2012-10-01T12:58:22Z

Thebgland:

[[File:Carrier3.jpg|thumb|300px|The Nimitz carrier in the San Fransisco bay]]
An '''aircraft carrier''' is a warship designed with a primary mission of deploying and recovering [[aircraft]], acting as a seagoing airbase. Aircraft carriers thus allow a naval force to project air power great distances without having to depend on local bases for staging aircraft operations. Most modern day aircraft carriers are nuclear powered, and thus not dependent upon fuel. Modern carriers can operate for as much as 20 years without having to refuel.

== Carriers in FlightGear ==
FlightGear currently includes four modern aircraft carriers:

* USS Dwight D. Eisenhower
* USS Nimitz
* USS Carl Vinson and the Vinson Battle Group
* Clemenceau

== Related content ==
* [[Howto: Carrier]] teaches how to land on and takeoff from a carrier.
* [[Carrier over MP]] for carrier control over a multiplay network.
[[es:Portaaviones]]
[[nl:Vliegdekschip]]

[[Category:Artificial intelligence]]

Boeing 747-8F

2012-10-01T12:54:01Z

Thebgland:

{{infobox Aircraft
|ready = dualcontrol
|image = Unbenannt3.png
|alt = ac3d
|name = Boeing 747-8F
|type = Airliner/Cargo
|fdm = JSBSim
|authors = Krb1
|status = development
|download = NO
}}
'''Ready'''
* 3d Model

'''Doing'''
*ScreenShots
*A lot of other

'''To do'''
*A Lot
[[File:Unbenannt4.png]]

[[Category:Boeing]]

Boeing 747-400 Tutorial

2012-10-01T12:53:11Z

Thebgland:

{{Main article|Boeing 747-400}}

''Please note that this document does not necessarily reflect the current status of the [[Boeing 747-400]] for [[FlightGear]]. Certain parts won't work or differently with older versions and some things may not even work with the latest release.''

== Normal procedures guide ==
=== Preflight ===
In order to start our preflight checks, we need some power. As we will need some extra time to get confident with the flightdeck, we will use the battery. With the battery alone, we will be provided with basic power for about 30 minutes, which should be enough for us to set up a better power source.

'''Turn the BATTERY switch to ON'''. You will notice that it has a protective cover, click it to open/close it. The battery should remain on at all time, as it acts as a backup for some vital avionics, so let us close it after setting it to ON.

'''Set the BUS TIE switches to AUTO'''. This will allow power to flow propertly through all electrical systems. Set the GEN CONT switches to ON, to allow our engines' generators to provide power to the systems. It is perfectly normal for the OFF lights to be lit at thi time, it just indicates that the generators are not being used at the moment (engines are off), but that they will be used once the engines are started.

Without any engine or APU running, the best way of obtaining longterm power is through external power sources, usually provided by the groundstaff at the airport. Using external power is "cheap", as it does not require the aircraft to burn any fuel.

'''Turn ON EXT PWR 1 and, if available, EXT PWR 2'''. You will find the switches on the electrical panel on the overhead. External power is only available when you are on the ground and the parking brake is set. It can take a couple of seconds till the EXT PWR switches to ON.

Any time the aircraft is powered, nav lights should be enabled, to alert the groundcrew that the aircraft is powered and under control. So '''turn ON the NAV LIGHTS''', which can be found in the lower right part of the overhead panel. Logo and wing lights are optional, but prefered at night.

Ensure that all flight controls are centered and/or in their idle positions. Meaning '''flaps are UP, gear handle in DOWN position.'''

We now move over to the FMC/[[CDU]] (you will find three of those at the pedestal, pick the one that is the easiest to control from your position). '''Click the FMC button''' located at LSK (Line Select Key) 1L (this means the first button down on the left). '''Click IDENT at LSK 1L.''' Ensure that the FMC is reporting accurate information about your current aircraft. '''Click POS INIT at LSK 6R.''' The POS INIT page of the FMC allows you to determine and input your aircraft's current position.

'''Press the CLR button''' in the lower right of the FMC to clear any messages that may be currently displayed.

'''Set all fuel XFEED (crossfeed) switches to ON'''. This will distribute fuel between the main fuel tanks (there are four of them on a 747).

'''Disable NACELLE and WING ANTI-ICE'''. Nacelle anti-ice should only be enabled after the engines are started. Wing anti-ice should only be enabled after takeoff.

'''Rotate the APU switch to START''' (click twice). The switch will rotate back to ON and the APU will be started (this will take several seconds). As soon as AVAIL is displayed on the APU GEN witches, set them to ON (once again this will take a while). The APU has now taken over the job of power source from the battery, which we must leave switched on!

Let's now continue to program the rest of our flight information into the FMC.

The POS INIT page should still be displayed. '''Click the RTE button''' to move to the ROUTE page.

'''Press LSK 6R (TAKEOFF)'''.

'''Enter 20 into the scratchpad and then click LSK 1L''' to set the Takeoff Flap setting. Flaps 20 is the standard flaps setting for takeoffs in the 747. You can also use flaps 10, but it will take longer for you to get airborne.

'''Verify your V1, VR, and V2 speeds.''' These are speeds used to determine if and when you takeoff from the runway. '''Write down or remember your V2 speed''' as we will need this number in a moment

'''Turn the F/D (Flight Director) ON.''' When the autopilot is on, the Flight Director is what controls where your plane goes. When the autopilot is off, the F/D will give us visual cues as to climb pitch and bank angle to keep the aircraft flying safely.

Enter V2 speed into the IAS/MACH indicator on the dashboard. You can adjust the autopilot indicator numbers by clicking the appropriate knob with your left mouse button (to increase value) or middle/3rd mouse button (to lower value). My FMC reported a V2 speed of 144 knots, so I have entered 144 into the IAS/MACH indicator. Immediately after takeoff, you will use aircraft pitch to maintain this speed.

'''Arm LNAV and VNAV''' by clicking on their respective buttons on the MCP. LNAV will control the lateral movement of the aircraft (i.e., follow your flight plan direction) and VNAV will control the vertical movement of the aircraft (get you to your cruise altitude and back down efficiently and safely). At this time we are only arming these autopilot functions. They will not actually control the aircraft until the autopilot is engages after we are airborne.

'''Set HDG to the heading of the takeoff runway.'''

'''Set ALT to 10000.''' You would typically set this to your initial cleared altitude as given by ATC. 10,000 feet will work nicely for most flights.

'''Ensure the autopilot DISENGAGE bar is UP.'''

'''Ensure that fuel control switches are set at CUTOFF''' (knobs pulled out and down). This will ensure that fuel will not flow to the engines

'''Set AUTOBRAKES to RTO.''' This will initiate full braking if something goes wrong during your takeoff roll and you reject (decide to end) the takeoff. Rejected Take Off braking WILL stop the plane VERY quickly if things go badly before you takeoff.

'''Ensure that the SEATBELTS selector is set to AUTO.''' AUTO will turn off the SEATBELT indicator when you are above 10,000 feet.

=== Pushback and start ===
'''Ensure all throttles are at idle.'''

'''Turn ON continuous ignition.''' This will send a continual spark to the engines which will ignite the fuel when it is introduced.

'''Pull the Engine Start Selector for Engine 4.'''

Watch the N2% RPM increase in the EICAS display. Bleed air from the APU is being 'blown' across the engine and is beginning to turn the turbines. '''When the N2% RPM indicator on the EICAS reaches around 14%, switch the Fuel Control Switch for Engine 4 to RUN.''' The engine should start up and then idle back.

'''Repeat this process for engine 1.''' Pull the Start Selector, wait for N2 to reach the magenta line, set Fuel Control to RUN.

'''Now do the same thing for engines 2 and 3.''' As soon as you get the hang of it, you can start engines 1 & 4 and engines 2 & 3 simultaneously.

'''Turn OFF the APU.''' The main engines are now powering the electrical, pneumatic, and hydraulic systems. The APU is no longer needed.

'''Check the upper EICAS (center display) for any warnings.''' If any appear, resolve them before continuing.

=== Taxi and Takeoff ===
Turn TAXI LIGHT ON. Even though it's daytime, it's good practice to turn them on as it makes your aircraft more visible.

'''Set flaps to takeoff configuration.''' The standard for a 747 is flaps 20, but if you set flaps 10 in the FMC earlier on, use 10. The flaps take a minute or so to extend, so extend them well before you begin your takeoff roll.

'''Move the control wheel and the control column to full travel''' in both directions and verify:
• freedom of movement
• that the controls return to center
Altough control surface failures are currently not simulated, it is good to get used to this, as you will/should do it with whatever aircraft you fly.

'''Release parking brake and taxi to the runway.''' As you taxi, review your V1, Vr, and V2 speeds. Ensure all other flight systems are set and you're ready to fly. When the runway is clear of incoming traffic, '''taxi onto the runway and stop''' (called "position and hold").

'''Turn LANDING and STROBE lights ON.'''

'''Arm Autothrottle.''' This will arm the autothrottles of the aircraft for the takeoff.

'''Ensure that F/D is ON, runway heading is set in HDG, IAS is set to V2, LNAV and VNAV are armed, and that altitude is 10,000.''' If all is set, then you're ready to fly!

'''Move throttles slowly forward to around 70% N1, then click the TO/GA button.'''

The TO/GA (Take Off/Go Around) button tells the flight computer to control throttle settings during takeoff and initial climbout. The TO/GA button is located on the yoke in the real cockpit. In FlightGear, this button is not yet implemented, press the SPD button on the glareshield instead.

Apply slight forward pressure on the stick/yoke until you reach around 80 knots to keep the nose gear firmly against the runway. Use rudder to keep the plane centered on the runway. If something goes wrong or you receive an EICAS warning message, quickly return throttles to idle and initiate reverse thrust (Delete key). Autobraking will commence if you are travelling over 85 knots, otherwise apply braking, exit the runway, resolve the problem, and try again.

'''When the copilot announces V1, this means that you're going to fly, or at least try to''', if you experience any problems. You are now going too fast to safely reject the takeoff. Any problems that you encounter should be taken into flight with you.

'''At Rotate, slowly and smoothly pull back on the controls to become airborne.''' You should be leaving the runway by the time V2 is announced.

=== Climb and cruise ===
'''As soon as you're over 500 feet altitude, select one of the A/P ENGAGE buttons''' on the autopilot MCP.

This switches LNAV and VNAV from armed to active. The autopilot is now flying the plane and you can sit back, complete this checklist, and monitor the flight.

You'll notice that as the flight continues that the autopilot will control altitude, speed, and direction.

Monitor the autopilot and speed as the aircraft levels off at 10,000 feet.

'''Turn off the TAXI and LANDING LIGHTS.'''
'''The SEATBELTS indicator may be turned off above 10,000 feet.''' If set to AUTO, it will automatically turn off.

'''Set MCP ALT to your cruise altitude and hit the center of the ALT dial''' to command the autopilot to climb.

=== Approach and landing ===
'''Set AUTOBRAKES.'''

Click the INIT REF button. You will see the APPROACH REF page. This page gives us two flap settings, with their corresponding speeds, that can be used for approach. Flaps 25 is the standard approach flaps setting.

'''Set the HDG to the runway heading. Do not press the SEL button!''' Simply enter the HDG as a reference and as a set altitude in case you abort the landing.

'''Click the INIT REF button''' on the CDU. You will see the APPROACH REF page. This page gives us two flap settings, with their corresponding speeds, that can be used for approach. Flaps 25 is the standard approach flaps setting.

'''Click LSK 1R''' to copy the flaps 25 settings and VREF speed to the scratchpad.

'''Click LSK 4R''' to set the approach flap and approach speed. This will allows the autopilot and flight director to provide accurate flap restriction speeds on approach. Take note of the approach speed value as we will need it in a few moments.

'''As soon as you begin the turn at the VCV VOR (base leg) or your descent, set the IAS/SPEED to approach speed + 5 knots.''' The approach speed is the speed referenced in the FMC previously. In order to set the speed, you must first click the center of the speed adjustment knob and then set the speed to the correct setting. The plane will now begin to decellerate to the indicated speed.

'''Use speedbrakes to slow you''' to your flaps 1 speed if your speed remains high (due to a steep descent) or if your speed exceeds 250 knots below 10,000 feet. You want to be close to your approach speed as you turn to final.

'''Lower the landing gear.''' The landing gear CAN be extended when your speed is below 270 knots and SHOULD be lowered when you set flaps 20. If you are approaching the turn to final and your speed is well above approach speed and below 270 knots, lower the gear to increase drag and help slow you down. Make sure you are at your approach speed with flaps at 25 when you are several miles from the runway.

'''ARM the speedbrake.''' With the speedbrake armed, it will deploy as soon as the main gears touch the runway.

'''Turn LANDING and TAXI lights ON.'''

Ensure that flaps are at 25, the gear is down, and that the plane is properly following the ILS. Sit back and enjoy the autolanding. The autopilot will fully control all aspects of the aircraft until touchdown. If you'd rather land manually, you can disengage the autopilot by pulling down on the DISENGAGE bar, turning A/T ARM off, and setting F/D to OFF. You will then have full control over throttle, pitch, and roll. Manually keep your speed at approach speed + 5 knots and follow the ILS indicators to the runway.

'''As the main wheels touch the ground, bring the throttles to idle and then engage full thrust reversers''' (Delete key). The autopilot will perform a rollout maneuver that will keep the aircraft centered on the runway. Braking is also performed automatically, though engaging thrust reversers will decrease brake heating and wear. Do not touch the controls except to engage thrust reversers - the plane will do everything else.

'''At 80 knots, set throttle back to idle, disengaging thrust reversers.'''

As soon as, or shortly before, the aircraft comes to a complete stop, '''DISENGAGE autopilot, set A/T ARM to OFF, and turn the F/D OFF.''' The aircraft is now in your control and you may begin your taxi. When you apply taxi thrust, the speedbrakes will retract. Exit the runway when able and taxi toward the gate or parking area of your choice. The airport here is HUGE, so you've got plenty of time to work through the remainder of the checklists.

=== Taxi in, parking, and shutdown ===
'''Set flaps to UP.'''

'''Set AUTOBRAKES to OFF.'''

'''Set LANDING and STROBE lights to OFF.'''

'''START the APU.''' This will allow us to turn off the engines, but still power the aircraft until ground power is available.

'''Set the parking brake''' as soon as you're fully stopped at the gate or parking area of your choice.

'''Turn ON APU GEN 1 and APU GEN 2.'''

'''Set FUEL control switches to CUTOFF.''' This will turnoff the engines.

'''Turn OFF the seatbelt indicator.''' This indicates that the passengers may now deplane.

'''Turn OFF the BEACON lights''' to indicate that the plane is properly parked and will not be moving. This alerts ground crew that they are free to connect ground power and unload baggage, etc.

Ground power should now be available. However, ground power is not available at all airports. You would typically switch to ground power and turn off the APU at this time, but if ground power is not available, leave the APU on to power the aircraft until you're done with the shutdown checklist.

'''Turn OFF CONT ignition.'''
'''Turn OFF AUTOSTART.'''
'''Open all XFEEDs.''' This allows fuel to flow freely if the aircraft is refueled on the ground.
'''Turn OFF APU GEN 1 and GEN 2''' (if on)
'''Turn OFF the APU''' (if running)
'''Turn OFF EXT PWR 1 and 2''' (if available)
'''Set all internal and external lighting to OFF.'''
'''Turn off the BATTERY.'''

The aircraft is now in the same cold and dark condition that it was in when we boarded. Congratulations on completing the flight!

{{Appendix|all|
* {{cite web |url=http://smithplanet.com/fs2004/pmdg/ |title=Boeing 747-400 Standard Procedure's Guide, An illustrated guide to getting started with the PMDG 747 |first=Jared |last=Smith |date=2005 }}
* ''747-469/-4F6 Flight Crew Operations Manual''. The Boeing Company (2 September 1993)
}}

[[Category:Boeing]]

Boeing 737-9 MAX

2012-10-01T12:50:22Z

Thebgland:

{{infobox Aircraft
|image =[[File:7378maxpreview.jpg]]
|alt =Boeing 737-9 MAX in AC3D
|name =Boeing 737-9 MAX
|type =Airliner
|livery =No
|authors =Krb1
|fdm =JSBSim
|status =Development
|fgname =737-9 MAX
|download = NO
}}

'''Ready'''
* 3D Model
* A part of XML

'''Doing'''
* 3D Cockpit
* Avionics

'''To Do'''
* A lot

<gallery>
File:1747max.png|Energie
File:2747max.png|max series from the 3d camera in ac3d
File:3747max.png|max series from the right side
File:4747max.png|max series from the front side
</gallery>

[[Category:Boeing]]

Boeing 737 MAX

2012-10-01T12:49:22Z

Thebgland:

{{infobox Aircraft
|image =[[File:7378maxpreview.jpg]]
|alt =Boeing 737-8 MAX in AC3D
|name =Boeing 737-8 MAX
|type =Airliner
|livery =No
|authors =Krb1
|fdm =JSBSim
|status =Development
|fgname =737-8 MAX
|download = NO
}}

'''Ready'''
* 3D Model
* A part of XML

'''Doing'''
* 3D Cockpit
* Avionics

'''To Do'''
* A lot
<gallery>
File:1747max.png|Energie
File:2747max.png|max series from the 3d camera in ac3d
File:3747max.png|max series from the right side
File:4747max.png|max series from the front side
</gallery>

[[Category:Boeing]]

Boeing 737-7 MAX

2012-10-01T12:48:43Z

Thebgland:

{{infobox Aircraft
|image =[[File:7378maxpreview.jpg]]
|alt =Boeing 737-7 MAX in AC3D
|name =Boeing 737-7 MAX
|type =Airliner
|livery =No
|authors =Krb1
|fdm =JSBSim
|status =Development
|fgname =737-7 MAX
|download = NO
}}

'''Ready'''
* 3D Model
* A part of XML

'''Doing'''
* 3D Cockpit
* Avionics

'''To Do'''
* A lot
<gallery>
File:1747max.png|Energie
File:2747max.png|max series from the 3d camera in ac3d
File:3747max.png|max series from the right side
File:4747max.png|max series from the front side
</gallery>

[[Category:Boeing]]

File:F-35.png

2012-08-13T02:41:07Z

Thebgland:

=={{int:filedesc}}==
{{Information
|description={{en|1=The F 35 before take off.}}
|date=2012-08-12
|source={{own}}
|author=[[User:Thebgland|Brady Griffith]]
|permission=
|other_versions=
|other_fields=
}}

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

Template:POTW/2012-33

2012-08-13T02:29:24Z

Thebgland: Created page with "{{POTW |image = Boeing 737-300 Southwest.png |description = The prototype of the Boeing 737-300 rolled out of the Renton plant on 17 January 1984, and first flew on 24 F..."

{{POTW
|image = Boeing 737-300 Southwest.png
|description = The prototype of the Boeing 737-300 rolled out of the Renton plant on 17 January 1984, and first flew on 24 February 1984. After it received its flight certification on 14 November 1984, USAir received the first aircraft on 28 November. A very popular aircraft, Boeing received 252 orders for it in 1985, and over 1000 throughout its production. The 300 series remained in production until 1999 when the last aircraft was delivered to Air New Zealand on December 17, 1999.
|article = Boeing_737-300
}}<noinclude>[[Category:Picture of the Week 2012]]<noinclude>

File:Boeing 737-300 Southwest.png

2012-08-13T02:25:47Z

Thebgland:

=={{int:filedesc}}==
{{Information
|description={{en|1=The southwest livery of the Boeing 737-300, taking off.}}
|date=2012-08-12
|source={{own}}
|author=[[User:Thebgland|Brady Griffith]]
|permission=
|other_versions=
|other_fields=
}}

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

[[Category:Airliners]]
[[Category:Boeing]]

Main Page

2012-08-13T00:13:47Z

Thebgland: Moved the POTD to the Aircraft portal

{{Main page/Header
|title=Welcome to the [[FlightGear wiki]]
|subtitle=''Fly free!''
|rightbox={{Main page/Languages}}
|introduction=
[[Help:Your first article|Get involved]] by starting, improving or extending articles.

|rightcolumn1= [[File:Portal user.png|40px]] </div>
[[Portal:User|Using]] 
[[New to FlightGear]] 
[[Frequently asked questions]] · [[Howto: Understand console output|Common errors]] 
[[Howto: Install scenery|Installing scenery]] · [[Howto: Install aircraft|Installing aircraft]] 
[[Howto: Fly a helicopter|Helicopter flying]]
|rightcolumn2= [[File:Portal developer.png|40px]] </div>
[[Portal:Developer|Developing]] 

[[Portal:Developer/Aircraft|Aircraft]] · [[Portal:Developer/Scenery|Scenery]] 
[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Howto: Create custom terrain|Editing terrain]]
|rightcolumn3= [[File:Portal wiki.png|40px]] </div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|About the wiki]] · [[Help:Contents|Help]] 
[[Help:Your first article|Your first article]] · [[Help:Translate|Translate]] 
[[Special:Categories|Categories]]


|sections=
{{Main page/Leftbox|title=About FlightGear
|logo=FlightGear logo.png
|contents= '''[[FlightGear]]''' is a flight-simulator created by volunteers, and released as free, open-source [[GNU General Public License|GPL]] software. It has been used for [[Professional and educational FlightGear users|academic research, education]], and for fun.

FlightGear comes with a set of illustrated documentation, notably "The Manual", which is available as [http://mapserver.flightgear.org/getstart.pdf PDF] and [http://mapserver.flightgear.org/getstart/ HTML]. This wiki provides aditional documentation on both user and development topics.

=== I am looking for... ===
* [[Portal:User|help on using FlightGear]]
* [[Portal:Developer|how to contribute something to FlightGear]]

}}
{{Main page/Leftbox|title=News
|logo=Nuvola apps knewsticker.png
|contents={{News}} }}
{{Main page/Leftbox|title=Did you know...
|logo=Nuvola apps ktip.png
|contents={{Did you know}} }}

}}

{{Main page/Rightcolumn
|title= [[:Category:Picture of the week|Image of the week]]
|contents= <center style="padding-top:.9em;">{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}</center>
|padding-right=23px
}}

{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Development repository status]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}

Template:POTD/2012/08/12

2012-08-05T18:14:16Z

Thebgland: Created page with "{{POTD |image = Dc3c47-03.jpg |description = The '''Douglas DC3 C-47''' is the military version of the famous DC3 transport aircraft. Shortly before the Allied invasion,..."

{{POTD
|image = Dc3c47-03.jpg
|description = The '''Douglas DC3 C-47''' is the military version of the famous DC3 transport aircraft. Shortly before the Allied invasion, the factories of the Douglas Aircraft Company produced two of them, every hour. At the end of World War II, over 10,000 C-47 rolled from the factory.
|article = Douglas DC-3-C47
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:POTD/2012/08/11

2012-08-04T04:49:45Z

Thebgland: Created page with "{{POTD |image = C17inflight.png |description = The Boeing C-17 Globemaster III is a four-engined transport aircraft used by the United States and her allies. |article ..."

{{POTD
|image = C17inflight.png
|description = The Boeing C-17 Globemaster III is a four-engined transport aircraft used by the United States and her allies.
|article = C-17 Globemaster III
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:POTD/2012/08/10

2012-08-04T04:45:41Z

Thebgland: Created page with "{{POTD |image = Carrier3.jpg |description = An '''aircraft carrier''' is a warship designed with a primary mission of deploying and recovering aircraft, acting as a..."

{{POTD
|image = Carrier3.jpg
|description = An '''aircraft carrier''' is a warship designed with a primary mission of deploying and recovering [[aircraft]], acting as a seagoing airbase. Aircraft carriers thus allow a naval force to project air power great distances without having to depend on local bases for staging aircraft operations. FlightGear currently includes three modern aircraft carriers.
|article = Aircraft carrier
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:POTD/2012/08/9

2012-08-04T04:43:11Z

Thebgland: Created page with "{{POTD |image = Rallye-MS893.jpg |description = The '''Rallye 893''' is a single engined, low wing monoplane of all metal construction, fitted with a fixed tricycle gear..."

{{POTD
|image = Rallye-MS893.jpg
|description = The '''Rallye 893''' is a single engined, low wing monoplane of all metal construction, fitted with a fixed tricycle gear. It has a bulbous cockpit which houses four people and it can be used as a [[Howto:_Do_aerotow_over_the_net|towplane]] for [[:Category:Glider|sailplanes]].
|article = Rallye-MS893E
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:Model Gallery

2012-08-04T04:32:37Z

Thebgland: Added the F-8 Crusader

<noinclude>This is the right place to add aircrafts to the lists in [[Aircraft]], [[:de:Flugzeuge]], [[:es:Aeronaves]], etc.</noinclude>
{{ #switch: {{{section|}}}
| carrier_borne_aircraft =
{{Gallery
|Buccaneer.jpg|[[Blackburn Buccaneer]]
|Douglas_A4.jpg|[[Douglas A-4 Skyhawk]]
|A-6E.jpg|[[Grumman A-6E|Grumman A-6E Intruder]]
|F-8E.jpg|[[F-8 Crusader]]
|F-14.jpg|[[Grumman F-14 Tomcat]]
|Hawker_Seahawk.jpg|[[Hawker Seahawk|Hawker Seahawk FGA6]]
}}
| experimental =
{{Gallery
|BAC_TSR-2_Prototype.jpg|[[BAC TSR-2 Prototype]]
|V22Osprey.jpg|[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]
|X15.jpg|[[North American X-15]]
|YF-23.jpg|[[Northrop/McDonnell Douglas YF-23]]
}}
| helicopters =
{{Gallery
|Ah-1_vietnam_firebase.png|[[AH-1 Cobra]]
|H21c.jpg|[[Boeing-Vertol H21C]]
|CH-47 Chinook.jpg|[[CH-47 Chinook Helicopter]]
|Bo105.jpg|[[Eurocopter Bo105]]
|Ec135.jpg|[[Eurocopter EC135]]
|EC130.jpg|[[Eurocopter EC130 B4]]
|OH-6.png|[[Hughes OH-6 Cayuse]]
|WG13.jpg|[[Lynx WG13]]
|S51.jpg|[[Sikorsky S51]]
|S58.jpg|[[Sikorsky S58]]
|s76c_landed.jpg|[[Sikorsky S76C]]
|Uh60.jpg|[[Sikorsky UH60]]
|Aluette2.jpg|[[Aérospatiale Alouette II|Alouette II]]
|Hup-3.jpg|[[Piasecki HUP-3]]
|R22.jpg|[[Robinson R22]]
}}
| historical_aircraft =
{{Gallery
|Couzinet70.jpg|[[Couzinet 70]]
|dh91.jpg|[[De Havilland D.H. 91 Albatross]]
|Douglas_DC3.jpg|[[Douglas DC-3]]
|ComperSwift.jpg|[[ComperSwift Comper]]
|Lockheed_1049.jpg|[[Lockheed 1049|Lockheed Constellation]]
|314.jpg|[[Boeing 314]]
|DHC-3.jpg|[[de Havilland Canada DHC-3 Otter]]
|1903_Wright_Flyer.jpg|[[Wright Flyer (UIUC)]]
|Short_Empire.jpg|[[Short Empire]]
|Dc-3-splash.png|[[Douglas DC-3-C47]]
}}
| light_civilian_aircraft =
{{Gallery
|A24-liverie-default.png|[[Aeroprakt A24 Viking]]
|Aerostar_700.jpg|[[Aerostar 700]]
|FK9MK2.jpg|[[B&F FK9 Mark 2]]
|Beech99.jpg|[[Beechcraft Model 99]]
|Cessna_172P.jpg|[[Cessna C172|Cessna 172P]] (1982)
|Edgley_Optica_01.jpg|[[Edgley Optica]]
|Piper Cherokee Warrior II.png|[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]
|Pa-24.jpg|[[Piper PA-24 Comanche|Piper Comanche (PA24-250)]]
|Piper j3cub.jpg|[[Piper J3 Cub]] (1946)
|Piper SenecaII.jpg|[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]
|dr400.jpg|[[Robin DR400]]
|Rallye-MS893.jpg|[[Rallye-MS893E]]
}}
| lighter_than_air =
{{Gallery
|Zeppelin_NT.jpg|[[Zeppelin NT]]
|ZF_Navy_free_balloon.jpg|[[ZF Navy free balloon]]
|Submarine_Scout.jpg|[[Submarine Scout]]
|Zeppelin_LZ_121_Nordstern.jpg|[[Zeppelin LZ 121 Nordstern]]
}}
| modern_airliners_narrowbody_midsize =
{{Gallery
|A320-family.jpg|[[Airbus A320 Family]]
|Beechcraft B1900D.png|[[Beechcraft B1900D]]
|707.jpg|[[Boeing 707]]
|717-200.jpg|[[Boeing 717]]
|727-230.2.jpeg|[[Boeing 727-230]]
|737-100.png|[[Boeing 737-100]]
|737-300.jpg|[[Boeing 737-300]]
|Boeing 737-400 British Airways.jpg|[[Boeing 737-400]]
|757-2002.jpg|[[Boeing 757]]
|Picture 11.png|[[Bombardier CRJ-200LR]]
|CRJ700.jpg|[[Bombardier CRJ700 series]]
|CessnaCitationX.jpg|[[Cessna Citation X]]
|Concorde.png|[[Concorde]]
|Fokker50.jpg|[[Fokker 50]]
|Tu154.jpg|[[Tupolev 154]]
}}
| modern_airliners_widebody_jumbo =
{{Gallery
|Airbus.png|[[Airbus A340-600]]
|A350.png|[[Airbus A350]]
|A380.jpg|[[Airbus A380]]
|747-400.jpg|[[Boeing 747-400]]
|Boeing 767-300.png|[[Boeing 767-300]]
|777-200.jpg|[[Boeing 777-200]]
|787.png|[[Boeing 787]]
|IL-96-400 Jet Airways.bmp|[[IL-96-400 Long Ranger(T)]]
}}
| modern_military_aircraft =
{{Gallery
|A-10.jpg|[[Fairchild A-10]]
|B-52F.jpg|[[Boeing B-52]]
|E-3B.jpg|[[Boeing E-3 Sentry]]
|F-15C.jpg|[[F-15C Eagle]]
|F-80C.jpg|[[F-80C Shooting Star]]
|Harrier.jpg|[[British Aerospace Harrier]]
|General_Dynamics_F16.jpg|[[General Dynamics F-16]]
|Cessna T-37.jpg|[[Cessna T-37]]
|Dassault Mirage F.1 at altitude.png|[[Dassault Mirage F.1]]
|Northrop_T-38.jpg|[[Northrop T-38]]
|OV-10A2.jpg|[[North American OV-10A Bronco]]
|Saab_J35.jpg|[[Saab J 35Ã– Draken|Saab J35Ö Draken]]
[[HAL Tejas]]|LCA.jpeg|
|F-22.png|[[Lockheed Martin F-22 Raptor]]
|PC-9M.jpg|[[Pilatus PC-9M]]
|PC-21.jpg|[[Pilatus PC-21]]
}}
| science_fiction =
{{Gallery
|bluebird_hovercraft.jpg|[[Bluebird]]
|UFO.jpg|[[UFO from the 'White Project' of the UNESCO]]
}}
| spacecraft =
{{Gallery
|Shuttle.jpg|[[Space Shuttle]]
|Vostok-1-Exterior.png|[[Vostok-1]]
}}
| ultra_light = 
{{Gallery
|AirwaveXtreme150.jpg|[[Airwave Xtreme 150]]
|Hornet.jpg|[[GDT Hornet (autogyro)]]
|DG-101G_001.jpg|[[Glaser-Dirks DG-101G]]
|DG-300.jpg|[[Glaser-Dirks DG-300]]
|Dragonfly-towing.jpg|[[Dragonfly|Moyes Dragonfly]]
|Paraglider.jpg|[[Paraglider]]
|Asw20.jpg|[[ASW-20 sailplane|Schleicher ASW-20]]
|Sgs233.jpg|[[Schweizer 2-33]]

}}
| vehicles = 
{{Gallery
|AerocarI_1.png|{{int|Taylor Aerocar}}
|Follow_me.jpg|{{int|Follow me}}
|Jeep.jpg|{{int|Jeep}}
|Lamborghini Murcielago LP640 March10.jpg|{{int|Lamborghini Murcielago}}
|M113AS3.jpg|{{int|M113AS3}}
|Mobile_Stairs.jpg|{{int|Mobile Stairs}}
|Pushback.jpg|{{int|Pushback}}
|Snowplow.jpg|{{int|Snowplow}}
}}
| warbirds =
{{Gallery
|Beaufighter.png|[[Bristol Beaufighter]]
|Fokker_DrI.jpg|[[Fokker Dr.I]]
|P51d-mustang.png|[[P-51D Mustang]]
|A6M2_fgfs-screen-166.jpg|[[A6M2 Zero‎]]
|ki-84.jpg|[[Nakajima Ki-84‎]]
|Fw190.jpg|[[Focke-Wulf Fw 190]]
|Sopwith_Camel.png|[[Sopwith Camel]]
|Spitfire.jpg|[[Supermarine Spitfire]]
|MiG-15bis-Exterior.jpg|[[MiG-15]]
|iar80-angry.jpg|[[IAR 80]]
|F4u-park.jpg|[[F4U Corsair]]
|109-1.png|[[Messerschmitt Bf 109]]
}}
}} 
<noinclude>

{{Informative template | 1=
__NOTOC__
==Goal==
This template is used in aircraft/helicopter/vehicle gallery pages and their translations. By using and maintaining this template the translations of the gallery pages can be up to date and synchronised with the least required work possible.

==Usage==
<code><nowiki>{{Model Gallery | section=sectionname}}</nowiki></code>
Replace "sectionname" with the section you want to include.

==Example==
<code><nowiki>{{Model Gallery | section=light_civilian_aircraft}}</nowiki></code>
will be replaced by a gallery structure, that contains the list of "Light civilian aircraft"

===sections===
*carrier_borne_aircraft
*experimental
*helicopters
*historical_aircraft
*light_civilian_aircraft
*lighter_than_air
*modern_airliners_narrowbody_midsize
*modern_airliners_widebody_jumbo
*modern_military_aircraft
*science_fiction
*spacecraft
*ultra_light
*vehicles
*warbirds
}}

[[Category:Templates]]</noinclude>

Template:POTD/2012/08/8

2012-08-04T04:28:21Z

Thebgland: Created page with "{{POTD |image = F-8E.jpg |description = The F-8 Crusader (originally F8U) was a single-engine aircraft carrier-based fighter aircraft built by Vought. |article = F-8..."

{{POTD
|image = F-8E.jpg
|description = The F-8 Crusader (originally F8U) was a single-engine aircraft carrier-based fighter aircraft built by Vought.
|article = F-8_Crusader
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:POTD/2012/08/7

2012-08-03T00:30:25Z

Thebgland: Created page with "{{POTD |image = B-25.jpg |description = The North American B-25 Mitchel; was a twin engine warbird aircraft from the 1940s. Some have been kept flying even into the 2000..."

{{POTD
|image = B-25.jpg
|description = The North American B-25 Mitchel; was a twin engine warbird aircraft from the 1940s. Some have been kept flying even into the 2000s, and can sometimes be seen at airshows.
|article = B-25 Mitchell
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:POTD/2012/08/6

2012-08-03T00:17:46Z

Thebgland: Created page with "{{POTD |image = Cessna 172P.jpg |description = The Cessna 172 Skyhawk is a four-seat, single-engine, high-wing fixed-wing aircraft. First flown in 1955 and still in prod..."

{{POTD
|image = Cessna 172P.jpg
|description = The Cessna 172 Skyhawk is a four-seat, single-engine, high-wing fixed-wing aircraft. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.
|article = Cessna 172P
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Category:Picture of the day

2012-08-03T00:16:31Z

Thebgland:

The '''picture of the day''', which is shown on the [[Main Page|main page]], is an image which is dynamically updated each day with an image from the wiki. The purpose of this is to highlight some features of FlightGear like aircraft.

== Usage ==
<nowiki>{{POTD
|image =
|description =
|article =
}}<noinclude>[[Category:Picture of the Day </nowiki>{{CURRENTYEAR}}-{{CURRENTMONTH}}<nowiki>]]<noinclude></nowiki>

* '''image:''' the name of the image, without <tt>File:</tt>.
* '''description:''' the text to show. Should be minimized to several lines.
* '''article:''' the title of the article where the image is most related to.
Do not forget to add the category and leave the noinclude tags in place!

== Example ==
<nowiki>{{POTD
|image = 25U-004.png
|description = The '''Pilatus PC-9M''' is a fast turboprop military trainer that is easy to handle and a lot of fun to fly, like in this screenshot flying over Snake River running through [[Suggested Flights#Hell.27s_Canyon|Hell's Canyon]].
|article = Pilatus PC-9M
}}<noinclude>[[Category:Picture of the Day </nowiki>{{CURRENTYEAR}}-{{CURRENTMONTH}}<nowiki>]]<noinclude></nowiki>
}}

[[Category:Featured pictures]]

Template:POTD/2012/08/5

2012-08-03T00:10:52Z

Thebgland: Created page with "{{POTD |image = A24-liverie-yellow.png |description = The A-24 Viking is a multipurpose amphibian of JAR-VLA category designed to suit variety of tasks and operation on ..."

{{POTD
|image = A24-liverie-yellow.png
|description = The A-24 Viking is a multipurpose amphibian of JAR-VLA category designed to suit variety of tasks and operation on both land and water.
|article = Aeroprakt A24 Viking
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:POTD/2012/08/4

2012-08-02T23:54:01Z

Thebgland: Created page with "{{POTD |image = SR-71b-1.png |description = The SR-71b is a stealth reconnaissance aircraft. It also holds the title of the fastest air driven aircraft. |article = L..."

{{POTD
|image = SR-71b-1.png
|description = The SR-71b is a stealth reconnaissance aircraft. It also holds the title of the fastest air driven aircraft.
|article = Lockheed SR-71 Blackbird
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Template:POTD/2012/08/3

2012-08-02T23:47:48Z

Thebgland: Created page with "{{POTD |image = F-16 RNLAF J015-demo 2.png |description = The F-16 is a US Air Force Multirole fighter. It is created by General Dynamics. This image uses the RNLAF J015..."

{{POTD
|image = F-16 RNLAF J015-demo 2.png
|description = The F-16 is a US Air Force Multirole fighter. It is created by General Dynamics. This image uses the RNLAF J015-demo Livery.
|article = F-16
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

Main Page

2012-08-02T23:45:11Z

Thebgland: Added a Picture of the day Section

{{Main page/Header
|title=Welcome to the [[FlightGear wiki]]
|subtitle=''Fly free!''
|rightbox={{Main page/Languages}}
|introduction=
[[Help:Your first article|Get involved]] by starting, improving or extending articles.

|rightcolumn1= [[File:Portal user.png|40px]] </div>
[[Portal:User|Using]] 
[[New to FlightGear]] 
[[Frequently asked questions]] · [[Howto: Understand console output|Common errors]] 
[[Howto: Install scenery|Installing scenery]] · [[Howto: Install aircraft|Installing aircraft]] 
[[Howto: Fly a helicopter|Helicopter flying]]
|rightcolumn2= [[File:Portal developer.png|40px]] </div>
[[Portal:Developer|Developing]] 

[[Portal:Developer/Aircraft|Aircraft]] · [[Portal:Developer/Scenery|Scenery]] 
[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Howto: Create custom terrain|Editing terrain]]
|rightcolumn3= [[File:Portal wiki.png|40px]] </div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|About the wiki]] · [[Help:Contents|Help]] 
[[Help:Your first article|Your first article]] · [[Help:Translate|Translate]] 
[[Special:Categories|Categories]]


|sections=
{{Main page/Leftbox|title=About FlightGear
|logo=FlightGear logo.png
|contents= '''[[FlightGear]]''' is a flight-simulator created by volunteers, and released as free, open-source [[GNU General Public License|GPL]] software. It has been used for [[Professional and educational FlightGear users|academic research, education]], and for fun.

FlightGear comes with a set of illustrated documentation, notably "The Manual", which is available as [http://mapserver.flightgear.org/getstart.pdf PDF] and [http://mapserver.flightgear.org/getstart/ HTML]. This wiki provides aditional documentation on both user and development topics.

=== I am looking for... ===
* [[Portal:User|help on using FlightGear]]
* [[Portal:Developer|how to contribute something to FlightGear]]

}}
{{Main page/Leftbox|title=News
|logo=Nuvola apps knewsticker.png
|contents={{News}} }}
{{Main page/Leftbox|title=Did you know...
|logo=Nuvola apps ktip.png
|contents={{Did you know}} }}

}}

{{Main page/Rightcolumn
|title= [[:Category:Picture of the week|Image of the week]]
|contents= <center style="padding-top:.9em;">{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}</center>
|padding-right=23px
}}
{{Main page/Rightcolumn
|title= [[:Category:Picture of the day|Image of the day!]]
|contents= <center style="padding-top:.9em;">{{POTD/{{CURRENTYEAR}}/{{CURRENTMONTH}}/{{CURRENTDAY}}}}</center>
|padding-right=23px
}}
{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Development repository status]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}

Template:POTD/2012/08/2

2012-08-02T23:41:39Z

Thebgland: Created page with "{{POTD |image = B-52-1.png |description = The B-52 is a United States bomber. |article = Boeing B-52 }}<noinclude>Category:Picture of the Day 2012-08<noinclude>"

{{POTD
|image = B-52-1.png
|description = The B-52 is a United States bomber.
|article = Boeing B-52
}}<noinclude>[[Category:Picture of the Day 2012-08]]<noinclude>

File:B-52-2.png

2012-08-02T23:28:00Z

Thebgland:

=={{int:filedesc}}==
{{Information
|description={{en|1=B-52 Taking off}}
|date=2012-08-02
|source={{own}}
|author=[[User:Thebgland|Brady Griffith]]
|permission=
|other_versions=
|other_fields=
}}

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

[[Category:Bomber aircraft]]