= Ramp Marshall =

A '''Ramp Marshall''' is a person who guides aircraft using hand (and wand) signals at a parking ramp. This new feature is now available on a more generalized scale in FlightGear. Until this gets merged into the fgdata repository, you can get this from omega95's fgdata clone or the new Singapore Scenery development.

Currently, support can be added to airports with the ufo but soon, ramp marshalls will be added automatically if a parking spot's flag is set to enable it. This will integrate FlightGear parking positions, ramp marshalls and other features that might come up related to parking ramps or gates.

These are videos of the first prototype of the ramp marshall.

{{#ev:youtube | c_KEbyv_h5A}} {{#ev:youtube | Hz4WU8nsdls}}

= Adding Ramp Marshall Support =

== Adding Ramp Marshall Compatibility to Aircraft ==

[[File:A330-200 Ramp Marshall Compatibility - getting position with ac3D.png|thumb|525px|Demonstrating how to get x-position of nose gear with ac3D for ramp marshall compatibility.]]

It's actually very simple to add ramp marshall compatibility to an aircraft, the only file required to be edited is the aircraft's '''-set.xml''' file. (or common xml file for aircraft groups) The user is still required to use some kind of 3D modeling program to get the position.

1. Open the Aircraft's model file (containing the gears) with a 3D modeling program and get the '''x''' position of the bottom of the nose gear. (Or the position you want to rest at the ramp)

2. Add the following code within the '''<sim> ... <model> ... </model></sim>''' tags in the aircraft's '''-set.xml''' file. (or common xml file for aircraft groups)

<syntaxhighlight lang="xml">
<ramp>
<x-m type="float">-15.9664</x-m>
<class type="string">2</class>
</ramp>
</syntaxhighlight>

The '''x''' position from the 3D model is in the <x-m> tag and the aircraft class is in the <class> tag. With the current models, the aircraft classes are as follows -
* 0 - 747s, 777-300s, A340s, A380s
* 1 - 777-300s, A330-300s, 787s
* 2 - A330-200s, 757s, 767s
* 3 - A320s (includes A318s, A319s and A321s), 737s and other aircraft in general. This works for CRJs, E-jets etc.

This should be all! The ramp marshall should be able to ''recognize'' the aircraft and guide it to the right position at the ramp!

== Adding Ramp Marshalls to an Airport ==

'''NOTE -''' In the future, this will change because ramp marshall positions are going to be connected to an airport's '''groundnet.xml''' file.

[[File:ramp-marshall-arpt-1.png|thumb|320px]]

[[File:ramp-marshall-arpt-2.png|thumb|320px]]

1. Start up FlightGear with the '''ufo''' at the airport you want to place ramp marshalls.

2. Hit the '''L''' key on the keyboard to bring up the model selection dialog and select '''$FGDATA/Models/Airport/Ramp/ramp.xml'''. Using the ufo's scenery editing tools, place (and adjust) ramp marshalls everywhere you want. To make it simpler, click on the exact position you want the airplane to come to a stop. This will usually be at the end of a parking ramp's taxiway lines. Then, you will only have to change the heading.

3. Once you've finished placing all the models, hit the '''D''' key to dump the stg lines onto the console. (Do not close FlightGear yet) Copy the stg lines into a blank file. (name does not matter)

4. Open up the Nasal console and execute the following function.

<syntaxhighlight lang="javascript">
ramp_marshall.convert_stg();
</syntaxhighlight>

5. Choose the stg file you pasted the dumped stg lines in to convert the file into a readable xml ramp position file. The converted file can be found '''$FGHOME/Export'''.

6. Copy the exported file (it will be called '''ramps-export.xml''') to '''$FGDATA/AI/Airports/<icao>/ramps.xml'''. For example, if you want these ramps at Singapore Changi Intl. Airport (WSSS), you'd put it in '''$FGDATA/AI/Airports/<icao>/WSSS.xml'''.

= Contributing to the Module =

== Teach the Ramp Marshall new signals ==

{{WIP}}

== Using dfferent models or textures ==

{{WIP}}

= Further development =

== Visual Docking Guidance System ==

{{WIP}}

== External Links ==
* https://gitorious.org/~omega95/fg/omega95s-fgdata
* http://flightgear.org/forums/viewtopic.php?f=30&t=20572
* https://gitorious.org/fg-singapore-scenery

== Related ==
* http://flightgear.org/forums/viewtopic.php?f=30&t=20572

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

Ramp Marshall

2013-08-07T16:00:55Z

Omega1174: /* Adding Ramp Marshall Compatibility to Aircraft */

2012-08-16T07:58:57Z

Omega1174: /* gEdit */

File:Philosopher's nasal highlighting in gEdit.jpeg

2012-08-16T07:58:11Z

Omega1174:

=={{int:filedesc}}==
{{Information
|description={{en|1=Nasal Syntax Highlighting in GIMP, created by Philosopher}}
|date=2012-08-16
|source={{own}}
|author=[[User:Omega1174|Omega1174]]
|permission=
|other_versions=
|other_fields=
}}

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

Howto:Syntax highlighting for Nasal

2012-08-16T07:56:38Z

Omega1174:

2012-06-01T05:00:04Z

Omega1174: /* Airbus A330-223 operators */

{{infobox Aircraft
|image = A332-splash.png
|name = Airbus A330-200 Series
|type = Wide-body Airliner
|fdm = JSBSim
|status = Git Development Version
|authors = Narendran Muraleedharan, Chris Mueffelmann, A320neo Developers
|fgname = A330-203, A330-223, A330-243
|download = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main/archive-tarball/master
|development = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main
}}
The '''Airbus A330-200 series''' project consists of the '''Airbus A330-203''' (A330-200 with ''General Electric CF6-80E1 Engines''), '''Airbus A330-223''' (A330-200 with ''Pratt and Whitney PW4000 Engines'') and the '''Airbus A330-243''' (A330-200 with ''Rolls Royce Trent 772B-69 Engines''). The project uses theOmegaHangar's new [[Airbus A320neo|Airbus A320/30/40]] cockpit and systems and new Airbus A330-200 models. Note that the aircraft is still in development and a release has not yet been made. Feel free to start a discussion in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 the forum topic] if you'd like to contribute to the project.

==Airbus Systems==

===Airbus Fly-By-Wire===
The Airbus fly-by-wire (adapted from the Airbus A320neo fly-by-wire) is a system which continuously takes in the pilot's stick input, uses them as Pitch/Roll-Rate commands, and calculates the required surface deflection to achieve the commanded rate. The fly-by-wire also provides flight envelope protection and the soft/hard bank feature.

====Pitch/Roll-Rate and G-Force Command====
For the Roll Axis, the stick all the way to the left commands a negative 30 degrees roll rate and all the way to the right commands a positive 30 degrees roll rate.

As for the Pitch Axis, the commands are divided according to the airspeed of the aircraft. If the Airspeed is under 210 knots, pitch-rate is used and over 210 knots, g-force is used. Under 210 knots, pulling the stick all the way to the back commands a 30 degrees pitch rate and pushing it all the way forward commands a negative 30 degrees pitch rate. Over 210 knots, pulling the stick all the way to the back commands a 2.75G acceleration and pushing it all the way forward commands a -0.75G acceleration.

====Flight Envelope Protection====
For the Roll Axis, having the stick less than half way deflected either side, you get what's called a ''soft bank''. With a soft bank, the aircraft can't exceed 33 degrees of bank to either side. If the stick is deflected more than half way, you get a hard bank and the aircraft can be banked up till 67 degrees to either side.

For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.

=== Hydraulics System ===
The Airbus A320, A330 and [[Airbus A340|A340]] series have similar hydraulic systems. There are three hydraulic systems on the aircraft, each having it's own reservoir- the '''GREEN''' system, the '''YELLOW''' system and the '''BLUE''' system.

The Green system is powered by the Left Engine's Hydraulic Pump, the yellow by the Right Engine's Hydraulic Pump and the Blue System with an Electric Pump. During normal operation, each hydraulic system should have their hydraulic pressure between 2500 and 3000 PSI. (Pounds per Square Inch) The engine systems control the surfaces, stabilizers, flaps/slats and landing gears while the electric pump system connect to only the surfaces and stabilizers. In case a system fails, an alternate system can be used. The yellow system also has an electric pump which can be used to power the hydraulics using external power when the aircraft is on the ground.

The Yellow and Green Hydraulic systems have a power transfer unit which is used to transfer hydraulic pressure between the pumps in case there is a 500 PSI difference between the pressures in the green and yellow systems.

All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.

'''MORE SYSTEMS INFORMATION COMING SOON'''

== Example Flights ==

We'll show 2 example flights- a flight that uses a company route from the default flight database and a custom planned flight.

=== MIA134 from Brisbane to Singapore (Company Route) ===

MIA134 is one of merlion's alternate-day flights from Brisbane to Singapore. We'll just be using this as an example and you can use the same procedures from any route from the company database. (Take a look at our database flights below) Flight MIA134 is flown with an Airbus A330-243 (Rolls Royce Trent 772B-60 Engines) virtually registered S-QDAZ.

First, start-up at any of the parking ramps at Brisbane's (YBBN) International Apron. As Brisbane doesn't have parking positions at the moment, start-up on runway 01 and taxi-to (best using pushback) a parking gate in the International Apron.

==== Pre-Flight Planning ====

To start with the pre-flight planning, we need electrical power. For Airports that provide external power, we can use that and for other airports, the APU can provide power. At Brisbane, external power is available, so make sure your ground services dialog has external power box enabled and turn on '''EXT PWR''' from the ''Overhead Panel''. (View)

Before we start anything, let's make sure everything's how they should be. Make sure only the following Overhead panel buttons have OFF showing on them- HYD YELLOW ELEC PUMP, ENG1, ENG2 and CTR TNK LTK FUEL PUMPS 1 AND 2, BAT1, BAT2, GEN1, GEN2 and APU GEN. EXT PWR should show ON. Now, look at the Pedestal and make sure both engine master switches are at OFF, the throttle is at idle, the engine mode is set to NORM, the speed-brakes are at 0, the parking brake is ON and the Flaps Lever is at 0. Let's now start with the pre-flight planning.

* Turn to the ''FMGC/mCDU View'' and turn on the Airbus mCDU by rotating (scroll) the BRT knob to full.

* Click on DATA and then A/C STATUS. Make sure the ACTIVE NAV DATABASE is ''27MAY-26AUG MIADatav3.1''. If not, please re-download the ''Database/Company/routes.xml'' file from gitorious.

* Now, click on INIT to head to the routes initialization page. You can initialize the company route by entering the company route ID (reference below) or the departure and arrival ICAOs. I normally enter the departure and arrival ICAOs as that way, it gives you all available routes you can choose from. So enter '''YBBN/WSSS''' and click on the LSK (Line Selector Key) next to FROM/TO.

* The mCDU will show 2 available routes (MIABNESIN1 and MIABNESIN2) which you can scroll through using the left and right arrow keys on the mCDU keypad. We'll be using MIABNESIN2 for this flight, so view that and click on the LSK next to INSERT. Once you do that, you should see that MIASINBNE2 would be written under CO_RTE and YBBN/WSSS would be written under FROM/TO.

* Enter the Flight Number '''MIA134''' and click on the LSK next to FLT NUM. '''(OPTIONAL)'''

* If you want, you can also enter a COST INDEX for the flight (normally between 25 and 40). '''(OPTIONAL)'''

* If you have an alternate route (not supported atm), you can enter the Alternate airport ICAO and RTE ID in the ALTN/CO_RTE Field.

* The final step in the INIT A page is your cruise altitude and Temperature. We'll be cruising at Flight Level 360 (FL360/36,000 ft) and checking the ''Environment>Weather Dialog'', it's about -55 degrees at that altitude, so enter '''360/-55''' and hit the LSK next to CRZ ALT/TEMP.

''NOTE: To get the '''-''', press on the '''+/-''' key in the keypad twice.''

* After INIT A is complete, let's proceed to INIT B (aka. FUEL PREDICTION Page), click on the RIGHT ARROW KEY on the keypad to go there.

''NOTE: Please skip the next 2 steps for the moment as this part requires fixing.''

* Once there, the trip fuel/time should show about 120 blocks of fuel (atm, it shows 24 but it will be fixed soon) required for the flight. The Aircraft can hold a maximum of 172.5 Blocks (1 Block = 804 KG JET-A Fuel). It should also show that the total flight will be about 442 minutes long using the initialized route. That is 8 hours and 22 minutes, a decent time for about 4000 miles.

* We'll take 10% fuel with us for reserves, so enter '''0/10''' and hit the LSK next to RSV. The mCDU will automatically calculate our extra fuel, TOW (Take-off Weight) and LW (Landing Weight).

* Now, click on F-PLN to go to the Primary Flight-plan Management Page. Here, you'll see the automatically initialized flight plan which you can scroll through using the up and down arrow keys on the keypad. Atm, we don't need to make any changes to our flight-plan as the company route sets everything perfect for us. We'll come back to F-PLN Lateral Revision (LAT REV) in the next custom planned example flight.

* We need to select a DEPARTURE and ARRIVAL procedure for our flight. To select a DEPARTURE Terminal Procedure, click on the LSK next to YBBN (Right above F-PLN DISCONTINUITY) and click on the LSK next to DEPARTURE.

* I'll be using runway 19 for departure (Currently Winds are 200@9), so I click on the LSK next to 19.

* Our first waypoint (after YBBN) is WOODY, so I want a DEPARTURE PROCEDURE that'll take me to WOODY. A procedure available for Runway 19 is ''WODY2A.19'' (at the end of the list). Select that and hit the LSK next to INSERT.

* Now, for the arrival procedure, you want to find your last waypoint before WSSS, so go to the F-PLN page and scroll to the end. With this route, ''REPOV'' is the last waypoint. (With MIABNESIN1, LAVAX is the last waypoint.

* Scroll back up and click on the LSK next to DEST WSSS and then select ARRIVAL.

* We'll be landing on Runway 20R (usually the default intl. runway at WSSS), so I select 20R. For the Arrival Procedure, select and INSERT REME6B.20R as that procedure starts at REPOV.

''NOTE: Small sections based on the PERF, DIR and PROG pages are remaining but we'll get back to that once it's completely functional.''

We have completed out basic flight-planning. We will focus on Radio Navigation later. Let's now fuel up for the flight. As we entered in the mCDU, we'll be starting with 130 blocks of fuel for this 8 and a half hour flight. That's 104,500 KG JET-A fuel. Open the Fuel Truck dialog, enable to truck, connect it to the aircraft, enter '''104500''' in hte REQUEST KG and Start Filling up the aircraft. Once the fueling is complete, we can disconnect the fuel truck and proceed to starting up the aircraft. Remember to first disconnect all ground services and remove the chokes.

==== Manual Engines Start-Up Procedure ====

* Turn on the Beacon Lights from the Lighting Control Panel.

* Look up at the overhead panel and turn on the APU by turning on the APU MASTER SW and the START button. You should hear the APU spooling. Once it's started, turn off the APU START switch and turn on the APU GEN.

* To get fuel to the engines, you need to turn on the LTK PUMPS, so turn on all the ENG1, ENG2 and CTR TNK FUEL PUMPS.

* Switch to Pedestal View and in the throttle quadrant, set the Engine MODE to START, and then turn both engine master switches to ON.

* Keep an eye on the Upper ECAM. When both Engine N1% exceeds 25%, the engines are started and running. Turn the Engine MODE back to NORM and turn off the APU.

* Turn on the Navigation Lights.

Release Parking Brakes and use 2 notches of Flaps for take-off. Pushback and taxi to the runway as usual. While taxiing, you could set your autopilot and other preferences. For autopilot, I'm going to make sure everything is disarmed and then set speed to IAS:250|MACH:0.72, altitude to 36000 ft (switch the black knob in behind the ALT knob to 1000 for easier scrolling, V/S to 2200 and finally click on the HDG knob to turn it to ''Managed'' Mode. You can also set ND and Lower ECAM Display Pages- I use the NAV page on the ND with 40 nm range (VORD, NDB and ARPT selected), and normally keep the FUEL page on the Lower ECAM. If you need to check another system, you can use the switching panel to change to that display.

Finally, remember to set your altimeter setting. Get your altimeter setting from Environment>Weather and scroll the altimeter setting knob on the Glare-shield panel to that reading.

''NOTE: Managed Mode means the FMGC tells the computer where the plane should go. This is equivalent to LNAV on Boeing aircraft.''

==== Take-off and Cruise ====

Once you're holding short, revise your reference speeds. At this weight, they'd be- V1:140, Vr:150, V2:156.

When the runway is clear (and/or you have ATC's permission), taxi on to the runway and turn on the Strobe Lights. Power up the throttle all the way, and rotate at Vr and make sure you're airborne by V2. Retract your gears and when you reach the respective flaps extension speeds (PRINTED ON THE MAIN PANEL), retract the respective flaps. Once you've maintained a steady climb, turn on the A/THR and AP1 from the Glare-shield panel.

The autopilot will automatically fly the departure procedure you entered and then transition to the F-PLN (flight-plan) from the Company Route. Once over 10000 ft, switch to 280 KIAS Speed and keep climbing, Around 18000 ft, switch to mach (setting at 0.72) and reduce the V/S to around 1800 fpm.

Once you're over FL260 (26000 ft), reduce your V/S to 1000 fpm and increase mach to 0.78. Then sit back and relax (or go do something else) while the computer automatically takes you to your destination.

'''REST COMING UP SOON'''

=== GA860 from Jakarta to Hong Kong ===

GA860 is a daily ''Garuda Indonesia'' Route flown with an Airbus A330-243.

'''More Info about this example Flight coming soon...'''

== Liveries ==
The Airbus A330-200 series have liveries for each variant (203, 223 an 243) and are managed by Chris Mueffelmann. Please let us know if you're creating a livery by changing the status on the livery below so that duplicates are avoided.

=== Airbus A330-203 operators ===

''ALL LIVERIES COMPLETE!''

{|
| valign="top" |
* Afriqiyah Airways - '''COMPLETED'''
* Air Europa - '''COMPLETED'''
* Air France - '''COMPLETED'''
* EVA Air - '''COMPLETED'''
* EVA Air (Hello Kitty) - '''COMPLETED'''
| valign="top" |
* KLM Royal Dutch Airline - '''COMPLETED'''
* Qantas Airways - '''COMPLETED'''
* Qatar Airways - '''COMPLETED'''
* TAM Linhas Aereas - '''COMPLETED'''
* Turkish - '''COMPLETED'''
|}

=== Airbus A330-223 operators ===
{|
| valign="top" |
* Air Berlin - '''COMPLETED'''
* Air Caraibes
* Air Greenland - '''COMPLETED'''
* Air India - '''COMPLTED'''
* Atlasjet - '''COMPLETED'''
* Brussels Airlines - '''COMPLETED'''
* China Southern - '''COMPLETED'''
* Delta Airlines - '''COMPLETED'''
* Edelweiss Air - '''COMPLETED'''
| valign="top" |
* Eurofly - '''COMPLETED'''
* Hong Kong Airlines - '''DEVEL''' (''Narendran'')
* Korean Air - '''COMPLETED'''
* Malaysia Airlines - '''COMPLETED'''
* Royal Jordanian - '''COMPLETED'''
* Swiss International Air Lines - '''COMPLETED'''
* TAM Linhas Aereas- '''COMPLETED'''
* TAP Portugal - '''COMPLETED'''
* Vietnam Airlines - '''COMPLETED'''
|}

===Airbus A330-243 operators===
{|
| valign="top" |
* Aeroflot
* Air China - '''COMPLETED'''
* Air Europa - '''COMPLETED'''
* Air Nigeria
* Air Transat - '''COMPLETED'''
* Avianca - '''COMPLETED'''
* China Eastern - '''DEVEL''' (''Chris'')
* Corsairfly - '''DEVEL''' (''Chris'')
* Cyprus Airways - '''COMPLETED'''
* Egyptair - '''COMPLETED'''
* Emirates - '''COMPLETED'''
* Etihad - '''COMPLETED'''
* Garuda Indonesia - '''COMPLETED'''
* Gulf Air
* Hainan Airlines
* Hawaiian Air
| valign="top" |
* Hi Fly - '''COMPLETED'''
* Hong Kong Airlines
* Jet Airways - '''COMPLETED'''
* Middle East Airlines
* Monarch Airways
* Oman Air
* Sichuan Airlines - '''COMPLETED'''
* South African Airways - '''COMPLETED'''
* SriLankan Airlines - '''COMPLETED'''
* Thomas Cook Airlines - '''COMPLETED'''
* Thomas Cook Scandinavia - '''COMPLETED'''
* US Airways
* Virgin Australia
* XL Airways
* Yemenia Airlines - '''COMPLETED'''
|}

==Default Flight Database==

The Default Flight Database contains [[Merlion Virtual Airlines]] Airbus A330-200 Routes. This database can be used by anyone, whether he/she is a merlion pilot or not. The example flight above explains how to use routes from the Flight Database.

If you fly for a different Virtual Airline which uses the Airbus A330-200 (203/223/243), please contact your staff for the flight database.

* Current Active Database - '''MIA_Data_v3.1''' ''(27MAY-26AUG)''
* Previous (Standby) Database - '''MIA_Data_v3.0''' (DOES NOT EXIST YET)

===Available Routes Tables===

''The following routes are complete and available.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA131 || WSSS || YBBN || S-QDAZ || MIASINBNE1, MIASINBNE2
|-
| MIA132 || YBBN || NZAA || S-QDAZ || MIABNEAKL1
|-
| MIA133 || NZAA || YBBN || S-QDAZ || MIAAKLBNE1
|-
| MIA134 || YBBN || WSSS || S-QDAZ || MIABNESIN1, MIABNESIN2
|-
| MIA135 || WSSS || FAJS || S-QDBZ || MIASINJNB1
|-
| MIA136 || FAJS || SBGR || S-QDBZ || MIAJNBGRU1
|-
| MIA137 || SBGR || FAJS || S-QDBZ || MIAGRUJNB1
|-
| MIA138 || FAJS || WSSS || S-QDBZ || MIAJNBSIN1
|-
| MIA139 || WSSS || RJGG || S-QDCZ || MIASINNGO1
|-
| MIA140 || RJGG || KLAX || S-QDCZ || MIANGOLAX1
|-
| MIA141 || KLAX || RJGG || S-QDCZ || MIALAXNGO1
|-
| MIA142 || RJGG || WSSS || S-QDCZ || MIANGOSIN1, MIANGOSIN2
|}

''The following Routes will be available soon.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA143 || WSSS || UHWW || S-QDDZ || MIASINVVO1
|-
| MIA144 || UHWW || CYVR || S-QDDZ || MIAVVOVYR1
|-
| MIA145 || CYVR || UHWW || S-QDDZ || MIAVYRVVO1
|-
| MIA146 || UHWW || WSSS || S-QDDZ || MIAVVOSIN1
|-
| MIA147 || WSSS || OMDB || S-QDEZ || MIASINDXB1, MIASINDXB2
|-
| MIA148 || OMDB || EDDF || S-QDEZ || MIADXBFRA1, MIADXBFRA2
|-
| MIA149 || EDDF || OMDB || S-QDEZ || MIAFRADXB1
|-
| MIA150 || OMDB || WSSS || S-QDEZ || MIADXBSIN1, MIASXBSIN2
|-
| MIA151 || WSSS || LEBL || S-QDFZ || MIASINBCN1
|-
| MIA152 || LEBL || TNCM || S-QDFZ || MIABCNSXM1
|-
| MIA153 || TNCM || LEBL || S-QDFZ || MIASXMBCN1
|-
| MIA154 || LEBL || WSSS || S-QDFZ || MIABCNSIN1
|-
| MIA155 || WSSS || LEBL || S-QDGZ || MIASINBCN1
|-
| MIA156 || LEBL || KMIA || S-QDGZ || MIABCNMIA1
|-
| MIA157 || KMIA || LEBL || S-QDGZ || MIAMIABCN1
|-
| MIA158 || LEBL || WSSS || S-QDGZ || MIABCNSIN1
|-
| MIA159 || WSSS || EHAM || S-QDHZ || MIASINAMS1, MIASINAMS2
|-
| MIA160 || EHAM || KMIA || S-QDHZ || MIAAMSMIA1
|-
| MIA161 || KMIA || EHAM || S-QDHZ || MIAMIAAMS1
|-
| MIA162 || EHAM || WSSS || S-QDHZ || MIAAMSSIN1, MIAAMSSIN2
|-
| MIA163 || WSSS || UUDD || S-QDIZ || MIASINDME1
|-
| MIA164 || UUDD || KJFK || S-QDIZ || MIADMEJFK1
|-
| MIA165 || KJFK || UUDD || S-QDIZ || MIAJFKDME1, MIAJFKDME2
|-
| MIA166 || UUDD || WSSS || S-QDIZ || MIADMESIN1, MIADMESIN2
|}

==Important developments remaining==

''We have completed the highest priority developments on the list, if you'd like us to do anything for the aircraft, please make a note below.''

==Important Recently Completed Developments==

* Modeled the Rolls Royce Trent 772B-60 Engines for the A330-243
* Animated Flaps, Speed-brakes and Parking Brake Levers (NOT PICK, ONLY TRANS/ROTATE)
* Animated the Throttle Quadrant (incl. Engine cutoffs - REQUIRED FOR MANUAL START-UP) - ''Manual Start-up is now possible''
* Fixed the '''Blue''' Hydraulic System
* Completed Separate Engine Sounds for the each variant

== External link ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]

{{Airbus}}

[[Category:Airliners]]

Airbus A330-200 (Old)

2012-05-31T18:06:07Z

Omega1174: /* Airbus A330-223 operators */

{{infobox Aircraft
|image = A332-splash.png
|name = Airbus A330-200 Series
|type = Wide-body Airliner
|fdm = JSBSim
|status = Git Development Version
|authors = Narendran Muraleedharan, Chris Mueffelmann, A320neo Developers
|fgname = A330-203, A330-223, A330-243
|download = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main/archive-tarball/master
|development = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main
}}
The '''Airbus A330-200 series''' project consists of the '''Airbus A330-203''' (A330-200 with ''General Electric CF6-80E1 Engines''), '''Airbus A330-223''' (A330-200 with ''Pratt and Whitney PW4000 Engines'') and the '''Airbus A330-243''' (A330-200 with ''Rolls Royce Trent 772B-69 Engines''). The project uses theOmegaHangar's new [[Airbus A320neo|Airbus A320/30/40]] cockpit and systems and new Airbus A330-200 models. Note that the aircraft is still in development and a release has not yet been made. Feel free to start a discussion in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 the forum topic] if you'd like to contribute to the project.

==Airbus Systems==

===Airbus Fly-By-Wire===
The Airbus fly-by-wire (adapted from the Airbus A320neo fly-by-wire) is a system which continuously takes in the pilot's stick input, uses them as Pitch/Roll-Rate commands, and calculates the required surface deflection to achieve the commanded rate. The fly-by-wire also provides flight envelope protection and the soft/hard bank feature.

====Pitch/Roll-Rate and G-Force Command====
For the Roll Axis, the stick all the way to the left commands a negative 30 degrees roll rate and all the way to the right commands a positive 30 degrees roll rate.

As for the Pitch Axis, the commands are divided according to the airspeed of the aircraft. If the Airspeed is under 210 knots, pitch-rate is used and over 210 knots, g-force is used. Under 210 knots, pulling the stick all the way to the back commands a 30 degrees pitch rate and pushing it all the way forward commands a negative 30 degrees pitch rate. Over 210 knots, pulling the stick all the way to the back commands a 2.75G acceleration and pushing it all the way forward commands a -0.75G acceleration.

====Flight Envelope Protection====
For the Roll Axis, having the stick less than half way deflected either side, you get what's called a ''soft bank''. With a soft bank, the aircraft can't exceed 33 degrees of bank to either side. If the stick is deflected more than half way, you get a hard bank and the aircraft can be banked up till 67 degrees to either side.

For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.

=== Hydraulics System ===
The Airbus A320, A330 and [[Airbus A340|A340]] series have similar hydraulic systems. There are three hydraulic systems on the aircraft, each having it's own reservoir- the '''GREEN''' system, the '''YELLOW''' system and the '''BLUE''' system.

The Green system is powered by the Left Engine's Hydraulic Pump, the yellow by the Right Engine's Hydraulic Pump and the Blue System with an Electric Pump. During normal operation, each hydraulic system should have their hydraulic pressure between 2500 and 3000 PSI. (Pounds per Square Inch) The engine systems control the surfaces, stabilizers, flaps/slats and landing gears while the electric pump system connect to only the surfaces and stabilizers. In case a system fails, an alternate system can be used. The yellow system also has an electric pump which can be used to power the hydraulics using external power when the aircraft is on the ground.

The Yellow and Green Hydraulic systems have a power transfer unit which is used to transfer hydraulic pressure between the pumps in case there is a 500 PSI difference between the pressures in the green and yellow systems.

All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.

'''MORE SYSTEMS INFORMATION COMING SOON'''

== Example Flights ==

We'll show 2 example flights- a flight that uses a company route from the default flight database and a custom planned flight.

=== MIA134 from Brisbane to Singapore (Company Route) ===

MIA134 is one of merlion's alternate-day flights from Brisbane to Singapore. We'll just be using this as an example and you can use the same procedures from any route from the company database. (Take a look at our database flights below) Flight MIA134 is flown with an Airbus A330-243 (Rolls Royce Trent 772B-60 Engines) virtually registered S-QDAZ.

First, start-up at any of the parking ramps at Brisbane's (YBBN) International Apron. As Brisbane doesn't have parking positions at the moment, start-up on runway 01 and taxi-to (best using pushback) a parking gate in the International Apron.

==== Pre-Flight Planning ====

To start with the pre-flight planning, we need electrical power. For Airports that provide external power, we can use that and for other airports, the APU can provide power. At Brisbane, external power is available, so make sure your ground services dialog has external power box enabled and turn on '''EXT PWR''' from the ''Overhead Panel''. (View)

Before we start anything, let's make sure everything's how they should be. Make sure only the following Overhead panel buttons have OFF showing on them- HYD YELLOW ELEC PUMP, ENG1, ENG2 and CTR TNK LTK FUEL PUMPS 1 AND 2, BAT1, BAT2, GEN1, GEN2 and APU GEN. EXT PWR should show ON. Now, look at the Pedestal and make sure both engine master switches are at OFF, the throttle is at idle, the engine mode is set to NORM, the speed-brakes are at 0, the parking brake is ON and the Flaps Lever is at 0. Let's now start with the pre-flight planning.

* Turn to the ''FMGC/mCDU View'' and turn on the Airbus mCDU by rotating (scroll) the BRT knob to full.

* Click on DATA and then A/C STATUS. Make sure the ACTIVE NAV DATABASE is ''27MAY-26AUG MIADatav3.1''. If not, please re-download the ''Database/Company/routes.xml'' file from gitorious.

* Now, click on INIT to head to the routes initialization page. You can initialize the company route by entering the company route ID (reference below) or the departure and arrival ICAOs. I normally enter the departure and arrival ICAOs as that way, it gives you all available routes you can choose from. So enter '''YBBN/WSSS''' and click on the LSK (Line Selector Key) next to FROM/TO.

* The mCDU will show 2 available routes (MIABNESIN1 and MIABNESIN2) which you can scroll through using the left and right arrow keys on the mCDU keypad. We'll be using MIABNESIN2 for this flight, so view that and click on the LSK next to INSERT. Once you do that, you should see that MIASINBNE2 would be written under CO_RTE and YBBN/WSSS would be written under FROM/TO.

* Enter the Flight Number '''MIA134''' and click on the LSK next to FLT NUM. '''(OPTIONAL)'''

* If you want, you can also enter a COST INDEX for the flight (normally between 25 and 40). '''(OPTIONAL)'''

* If you have an alternate route (not supported atm), you can enter the Alternate airport ICAO and RTE ID in the ALTN/CO_RTE Field.

* The final step in the INIT A page is your cruise altitude and Temperature. We'll be cruising at Flight Level 360 (FL360/36,000 ft) and checking the ''Environment>Weather Dialog'', it's about -55 degrees at that altitude, so enter '''360/-55''' and hit the LSK next to CRZ ALT/TEMP.

''NOTE: To get the '''-''', press on the '''+/-''' key in the keypad twice.''

* After INIT A is complete, let's proceed to INIT B (aka. FUEL PREDICTION Page), click on the RIGHT ARROW KEY on the keypad to go there.

''NOTE: Please skip the next 2 steps for the moment as this part requires fixing.''

* Once there, the trip fuel/time should show about 120 blocks of fuel (atm, it shows 24 but it will be fixed soon) required for the flight. The Aircraft can hold a maximum of 172.5 Blocks (1 Block = 804 KG JET-A Fuel). It should also show that the total flight will be about 442 minutes long using the initialized route. That is 8 hours and 22 minutes, a decent time for about 4000 miles.

* We'll take 10% fuel with us for reserves, so enter '''0/10''' and hit the LSK next to RSV. The mCDU will automatically calculate our extra fuel, TOW (Take-off Weight) and LW (Landing Weight).

* Now, click on F-PLN to go to the Primary Flight-plan Management Page. Here, you'll see the automatically initialized flight plan which you can scroll through using the up and down arrow keys on the keypad. Atm, we don't need to make any changes to our flight-plan as the company route sets everything perfect for us. We'll come back to F-PLN Lateral Revision (LAT REV) in the next custom planned example flight.

* We need to select a DEPARTURE and ARRIVAL procedure for our flight. To select a DEPARTURE Terminal Procedure, click on the LSK next to YBBN (Right above F-PLN DISCONTINUITY) and click on the LSK next to DEPARTURE.

* I'll be using runway 19 for departure (Currently Winds are 200@9), so I click on the LSK next to 19.

* Our first waypoint (after YBBN) is WOODY, so I want a DEPARTURE PROCEDURE that'll take me to WOODY. A procedure available for Runway 19 is ''WODY2A.19'' (at the end of the list). Select that and hit the LSK next to INSERT.

* Now, for the arrival procedure, you want to find your last waypoint before WSSS, so go to the F-PLN page and scroll to the end. With this route, ''REPOV'' is the last waypoint. (With MIABNESIN1, LAVAX is the last waypoint.

* Scroll back up and click on the LSK next to DEST WSSS and then select ARRIVAL.

* We'll be landing on Runway 20R (usually the default intl. runway at WSSS), so I select 20R. For the Arrival Procedure, select and INSERT REME6B.20R as that procedure starts at REPOV.

''NOTE: Small sections based on the PERF, DIR and PROG pages are remaining but we'll get back to that once it's completely functional.''

We have completed out basic flight-planning. We will focus on Radio Navigation later. Let's now fuel up for the flight. As we entered in the mCDU, we'll be starting with 130 blocks of fuel for this 8 and a half hour flight. That's 104,500 KG JET-A fuel. Open the Fuel Truck dialog, enable to truck, connect it to the aircraft, enter '''104500''' in hte REQUEST KG and Start Filling up the aircraft. Once the fueling is complete, we can disconnect the fuel truck and proceed to starting up the aircraft. Remember to first disconnect all ground services and remove the chokes.

==== Manual Engines Start-Up Procedure ====

* Turn on the Beacon Lights from the Lighting Control Panel.

* Look up at the overhead panel and turn on the APU by turning on the APU MASTER SW and the START button. You should hear the APU spooling. Once it's started, turn off the APU START switch and turn on the APU GEN.

* To get fuel to the engines, you need to turn on the LTK PUMPS, so turn on all the ENG1, ENG2 and CTR TNK FUEL PUMPS.

* Switch to Pedestal View and in the throttle quadrant, set the Engine MODE to START, and then turn both engine master switches to ON.

* Keep an eye on the Upper ECAM. When both Engine N1% exceeds 25%, the engines are started and running. Turn the Engine MODE back to NORM and turn off the APU.

* Turn on the Navigation Lights.

Release Parking Brakes and use 2 notches of Flaps for take-off. Pushback and taxi to the runway as usual. While taxiing, you could set your autopilot and other preferences. For autopilot, I'm going to make sure everything is disarmed and then set speed to IAS:250|MACH:0.72, altitude to 36000 ft (switch the black knob in behind the ALT knob to 1000 for easier scrolling, V/S to 2200 and finally click on the HDG knob to turn it to ''Managed'' Mode. You can also set ND and Lower ECAM Display Pages- I use the NAV page on the ND with 40 nm range (VORD, NDB and ARPT selected), and normally keep the FUEL page on the Lower ECAM. If you need to check another system, you can use the switching panel to change to that display.

Finally, remember to set your altimeter setting. Get your altimeter setting from Environment>Weather and scroll the altimeter setting knob on the Glare-shield panel to that reading.

''NOTE: Managed Mode means the FMGC tells the computer where the plane should go. This is equivalent to LNAV on Boeing aircraft.''

==== Take-off and Cruise ====

Once you're holding short, revise your reference speeds. At this weight, they'd be- V1:140, Vr:150, V2:156.

When the runway is clear (and/or you have ATC's permission), taxi on to the runway and turn on the Strobe Lights. Power up the throttle all the way, and rotate at Vr and make sure you're airborne by V2. Retract your gears and when you reach the respective flaps extension speeds (PRINTED ON THE MAIN PANEL), retract the respective flaps. Once you've maintained a steady climb, turn on the A/THR and AP1 from the Glare-shield panel.

The autopilot will automatically fly the departure procedure you entered and then transition to the F-PLN (flight-plan) from the Company Route. Once over 10000 ft, switch to 280 KIAS Speed and keep climbing, Around 18000 ft, switch to mach (setting at 0.72) and reduce the V/S to around 1800 fpm.

Once you're over FL260 (26000 ft), reduce your V/S to 1000 fpm and increase mach to 0.78. Then sit back and relax (or go do something else) while the computer automatically takes you to your destination.

'''REST COMING UP SOON'''

=== GA860 from Jakarta to Hong Kong ===

GA860 is a daily ''Garuda Indonesia'' Route flown with an Airbus A330-243.

'''More Info about this example Flight coming soon...'''

== Liveries ==
The Airbus A330-200 series have liveries for each variant (203, 223 an 243) and are managed by Chris Mueffelmann. Please let us know if you're creating a livery by changing the status on the livery below so that duplicates are avoided.

=== Airbus A330-203 operators ===

''ALL LIVERIES COMPLETE!''

{|
| valign="top" |
* Afriqiyah Airways - '''COMPLETED'''
* Air Europa - '''COMPLETED'''
* Air France - '''COMPLETED'''
* EVA Air - '''COMPLETED'''
* EVA Air (Hello Kitty) - '''COMPLETED'''
| valign="top" |
* KLM Royal Dutch Airline - '''COMPLETED'''
* Qantas Airways - '''COMPLETED'''
* Qatar Airways - '''COMPLETED'''
* TAM Linhas Aereas - '''COMPLETED'''
* Turkish - '''COMPLETED'''
|}

=== Airbus A330-223 operators ===
{|
| valign="top" |
* Air Berlin - '''COMPLETED'''
* Air Caraibes
* Air Greenland - '''COMPLETED'''
* Air India - '''DEVEL''' (''Narendran'')
* Atlasjet - '''COMPLETED'''
* Brussels Airlines - '''COMPLETED'''
* China Southern - '''COMPLETED'''
* Delta Airlines - '''COMPLETED'''
* Edelweiss Air - '''COMPLETED'''
| valign="top" |
* Eurofly - '''COMPLETED'''
* Hong Kong Airlines
* Korean Air - '''COMPLETED'''
* Malaysia Airlines - '''COMPLETED'''
* Royal Jordanian - '''COMPLETED'''
* Swiss International Air Lines - '''COMPLETED'''
* TAM Linhas Aereas- '''COMPLETED'''
* TAP Portugal - '''COMPLETED'''
* Vietnam Airlines - '''COMPLETED'''
|}

===Airbus A330-243 operators===
{|
| valign="top" |
* Aeroflot
* Air China - '''COMPLETED'''
* Air Europa - '''COMPLETED'''
* Air Nigeria
* Air Transat - '''COMPLETED'''
* Avianca - '''DEVEL''' (''Chris'')
* China Eastern - '''DEVEL''' (''Chris'')
* Corsairfly - '''DEVEL''' (''Chris'')
* Cyprus Airways - '''COMPLETED'''
* Egyptair - '''COMPLETED'''
* Emirates - '''COMPLETED'''
* Etihad - '''COMPLETED'''
* Garuda Indonesia - '''COMPLETED'''
* Gulf Air
* Hainan Airlines
* Hawaiian Air
| valign="top" |
* Hi Fly - '''DEVEL''' (''Chris'')
* Hong Kong Airlines
* Jet Airways - '''COMPLETED'''
* Middle East Airlines
* Monarch Airways
* Oman Air
* Sichuan Airlines - '''COMPLETED'''
* South African Airways - '''COMPLETED'''
* SriLankan Airlines - '''COMPLETED'''
* Thomas Cook Airlines - '''COMPLETED'''
* Thomas Cook Scandinavia - '''COMPLETED'''
* US Airways
* Virgin Australia
* XL Airways
* Yemenia Airlines - '''DEVEL''' (''Chris'')
|}

==Default Flight Database==

The Default Flight Database contains [[Merlion Virtual Airlines]] Airbus A330-200 Routes. This database can be used by anyone, whether he/she is a merlion pilot or not. The example flight above explains how to use routes from the Flight Database.

If you fly for a different Virtual Airline which uses the Airbus A330-200 (203/223/243), please contact your staff for the flight database.

* Current Active Database - '''MIA_Data_v3.1''' ''(27MAY-26AUG)''
* Previous (Standby) Database - '''MIA_Data_v3.0''' (DOES NOT EXIST YET)

===Available Routes Tables===

''The following routes are complete and available.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA131 || WSSS || YBBN || S-QDAZ || MIASINBNE1, MIASINBNE2
|-
| MIA132 || YBBN || NZAA || S-QDAZ || MIABNEAKL1
|-
| MIA133 || NZAA || YBBN || S-QDAZ || MIAAKLBNE1
|-
| MIA134 || YBBN || WSSS || S-QDAZ || MIABNESIN1, MIABNESIN2
|-
| MIA135 || WSSS || FAJS || S-QDBZ || MIASINJNB1
|-
| MIA136 || FAJS || SBGR || S-QDBZ || MIAJNBGRU1
|-
| MIA137 || SBGR || FAJS || S-QDBZ || MIAGRUJNB1
|-
| MIA138 || FAJS || WSSS || S-QDBZ || MIAJNBSIN1
|-
| MIA139 || WSSS || RJGG || S-QDCZ || MIASINNGO1
|-
| MIA140 || RJGG || KLAX || S-QDCZ || MIANGOLAX1
|-
| MIA141 || KLAX || RJGG || S-QDCZ || MIALAXNGO1
|-
| MIA142 || RJGG || WSSS || S-QDCZ || MIANGOSIN1, MIANGOSIN2
|}

''The following Routes will be available soon.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA143 || WSSS || UHWW || S-QDDZ || MIASINVVO1
|-
| MIA144 || UHWW || CYVR || S-QDDZ || MIAVVOVYR1
|-
| MIA145 || CYVR || UHWW || S-QDDZ || MIAVYRVVO1
|-
| MIA146 || UHWW || WSSS || S-QDDZ || MIAVVOSIN1
|-
| MIA147 || WSSS || OMDB || S-QDEZ || MIASINDXB1, MIASINDXB2
|-
| MIA148 || OMDB || EDDF || S-QDEZ || MIADXBFRA1, MIADXBFRA2
|-
| MIA149 || EDDF || OMDB || S-QDEZ || MIAFRADXB1
|-
| MIA150 || OMDB || WSSS || S-QDEZ || MIADXBSIN1, MIASXBSIN2
|-
| MIA151 || WSSS || LEBL || S-QDFZ || MIASINBCN1
|-
| MIA152 || LEBL || TNCM || S-QDFZ || MIABCNSXM1
|-
| MIA153 || TNCM || LEBL || S-QDFZ || MIASXMBCN1
|-
| MIA154 || LEBL || WSSS || S-QDFZ || MIABCNSIN1
|-
| MIA155 || WSSS || LEBL || S-QDGZ || MIASINBCN1
|-
| MIA156 || LEBL || KMIA || S-QDGZ || MIABCNMIA1
|-
| MIA157 || KMIA || LEBL || S-QDGZ || MIAMIABCN1
|-
| MIA158 || LEBL || WSSS || S-QDGZ || MIABCNSIN1
|-
| MIA159 || WSSS || EHAM || S-QDHZ || MIASINAMS1, MIASINAMS2
|-
| MIA160 || EHAM || KMIA || S-QDHZ || MIAAMSMIA1
|-
| MIA161 || KMIA || EHAM || S-QDHZ || MIAMIAAMS1
|-
| MIA162 || EHAM || WSSS || S-QDHZ || MIAAMSSIN1, MIAAMSSIN2
|-
| MIA163 || WSSS || UUDD || S-QDIZ || MIASINDME1
|-
| MIA164 || UUDD || KJFK || S-QDIZ || MIADMEJFK1
|-
| MIA165 || KJFK || UUDD || S-QDIZ || MIAJFKDME1, MIAJFKDME2
|-
| MIA166 || UUDD || WSSS || S-QDIZ || MIADMESIN1, MIADMESIN2
|}

==Important developments remaining==

''We have completed the highest priority developments on the list, if you'd like us to do anything for the aircraft, please make a note below.''

==Important Recently Completed Developments==

* Modeled the Rolls Royce Trent 772B-60 Engines for the A330-243
* Animated Flaps, Speed-brakes and Parking Brake Levers (NOT PICK, ONLY TRANS/ROTATE)
* Animated the Throttle Quadrant (incl. Engine cutoffs - REQUIRED FOR MANUAL START-UP) - ''Manual Start-up is now possible''
* Fixed the '''Blue''' Hydraulic System
* Completed Separate Engine Sounds for the each variant

== External link ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]

{{Airbus}}

[[Category:Airliners]]

Airbus A330-200 (Old)

2012-05-30T03:25:24Z

Omega1174: /* SQ118 from Singapore to Kuala Lumper */

{{infobox Aircraft
|image = A332-splash.png
|name = Airbus A330-200 Series
|type = Wide-body Airliner
|fdm = JSBSim
|status = Git Development Version
|authors = Narendran Muraleedharan, Chris Mueffelmann, A320neo Developers
|fgname = A330-203, A330-223, A330-243
|download = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main/archive-tarball/master
|development = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main
}}
The '''Airbus A330-200 series''' project consists of the '''Airbus A330-203''' (A330-200 with ''General Electric CF6-80E1 Engines''), '''Airbus A330-223''' (A330-200 with ''Pratt and Whitney PW4000 Engines'') and the '''Airbus A330-243''' (A330-200 with ''Rolls Royce Trent 772B-69 Engines''). The project uses theOmegaHangar's new [[Airbus A320neo|Airbus A320/30/40]] cockpit and systems and new Airbus A330-200 models. Note that the aircraft is still in development and a release has not yet been made. Feel free to start a discussion in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 the forum topic] if you'd like to contribute to the project.

==Airbus Systems==

===Airbus Fly-By-Wire===
The Airbus fly-by-wire (adapted from the Airbus A320neo fly-by-wire) is a system which continuously takes in the pilot's stick input, uses them as Pitch/Roll-Rate commands, and calculates the required surface deflection to achieve the commanded rate. The fly-by-wire also provides flight envelope protection and the soft/hard bank feature.

====Pitch/Roll-Rate and G-Force Command====
For the Roll Axis, the stick all the way to the left commands a negative 30 degrees roll rate and all the way to the right commands a positive 30 degrees roll rate.

As for the Pitch Axis, the commands are divided according to the airspeed of the aircraft. If the Airspeed is under 210 knots, pitch-rate is used and over 210 knots, g-force is used. Under 210 knots, pulling the stick all the way to the back commands a 30 degrees pitch rate and pushing it all the way forward commands a negative 30 degrees pitch rate. Over 210 knots, pulling the stick all the way to the back commands a 2.75G acceleration and pushing it all the way forward commands a -0.75G acceleration.

====Flight Envelope Protection====
For the Roll Axis, having the stick less than half way deflected either side, you get what's called a ''soft bank''. With a soft bank, the aircraft can't exceed 33 degrees of bank to either side. If the stick is deflected more than half way, you get a hard bank and the aircraft can be banked up till 67 degrees to either side.

For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.

=== Hydraulics System ===
The Airbus A320, A330 and [[Airbus A340|A340]] series have similar hydraulic systems. There are three hydraulic systems on the aircraft, each having it's own reservoir- the '''GREEN''' system, the '''YELLOW''' system and the '''BLUE''' system.

The Green system is powered by the Left Engine's Hydraulic Pump, the yellow by the Right Engine's Hydraulic Pump and the Blue System with an Electric Pump. During normal operation, each hydraulic system should have their hydraulic pressure between 2500 and 3000 PSI. (Pounds per Square Inch) The engine systems control the surfaces, stabilizers, flaps/slats and landing gears while the electric pump system connect to only the surfaces and stabilizers. In case a system fails, an alternate system can be used. The yellow system also has an electric pump which can be used to power the hydraulics using external power when the aircraft is on the ground.

The Yellow and Green Hydraulic systems have a power transfer unit which is used to transfer hydraulic pressure between the pumps in case there is a 500 PSI difference between the pressures in the green and yellow systems.

All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.

'''MORE SYSTEMS INFORMATION COMING SOON'''

== Example Flights ==

We'll show 2 example flights- a flight that uses a company route from the default flight database and a custom planned flight.

=== MIA134 from Brisbane to Singapore (Company Route) ===

MIA134 is one of merlion's alternate-day flights from Brisbane to Singapore. We'll just be using this as an example and you can use the same procedures from any route from the company database. (Take a look at our database flights below) Flight MIA134 is flown with an Airbus A330-243 (Rolls Royce Trent 772B-60 Engines) virtually registered S-QDAZ.

First, start-up at any of the parking ramps at Brisbane's (YBBN) International Apron. As Brisbane doesn't have parking positions at the moment, start-up on runway 01 and taxi-to (best using pushback) a parking gate in the International Apron.

==== Pre-Flight Planning ====

To start with the pre-flight planning, we need electrical power. For Airports that provide external power, we can use that and for other airports, the APU can provide power. At Brisbane, external power is available, so make sure your ground services dialog has external power box enabled and turn on '''EXT PWR''' from the ''Overhead Panel''. (View)

Before we start anything, let's make sure everything's how they should be. Make sure only the following Overhead panel buttons have OFF showing on them- HYD YELLOW ELEC PUMP, ENG1, ENG2 and CTR TNK LTK FUEL PUMPS 1 AND 2, BAT1, BAT2, GEN1, GEN2 and APU GEN. EXT PWR should show ON. Now, look at the Pedestal and make sure both engine master switches are at OFF, the throttle is at idle, the engine mode is set to NORM, the speed-brakes are at 0, the parking brake is ON and the Flaps Lever is at 0. Let's now start with the pre-flight planning.

* Turn to the ''FMGC/mCDU View'' and turn on the Airbus mCDU by rotating (scroll) the BRT knob to full.

* Click on DATA and then A/C STATUS. Make sure the ACTIVE NAV DATABASE is ''27MAY-26AUG MIADatav3.1''. If not, please re-download the ''Database/Company/routes.xml'' file from gitorious.

* Now, click on INIT to head to the routes initialization page. You can initialize the company route by entering the company route ID (reference below) or the departure and arrival ICAOs. I normally enter the departure and arrival ICAOs as that way, it gives you all available routes you can choose from. So enter '''YBBN/WSSS''' and click on the LSK (Line Selector Key) next to FROM/TO.

* The mCDU will show 2 available routes (MIABNESIN1 and MIABNESIN2) which you can scroll through using the left and right arrow keys on the mCDU keypad. We'll be using MIABNESIN2 for this flight, so view that and click on the LSK next to INSERT. Once you do that, you should see that MIASINBNE2 would be written under CO_RTE and YBBN/WSSS would be written under FROM/TO.

* Enter the Flight Number '''MIA134''' and click on the LSK next to FLT NUM. '''(OPTIONAL)'''

* If you want, you can also enter a COST INDEX for the flight (normally between 25 and 40). '''(OPTIONAL)'''

* If you have an alternate route (not supported atm), you can enter the Alternate airport ICAO and RTE ID in the ALTN/CO_RTE Field.

* The final step in the INIT A page is your cruise altitude and Temperature. We'll be cruising at Flight Level 360 (FL360/36,000 ft) and checking the ''Environment>Weather Dialog'', it's about -55 degrees at that altitude, so enter '''360/-55''' and hit the LSK next to CRZ ALT/TEMP.

''NOTE: To get the '''-''', press on the '''+/-''' key in the keypad twice.''

* After INIT A is complete, let's proceed to INIT B (aka. FUEL PREDICTION Page), click on the RIGHT ARROW KEY on the keypad to go there.

''NOTE: Please skip the next 2 steps for the moment as this part requires fixing.''

* Once there, the trip fuel/time should show about 120 blocks of fuel (atm, it shows 24 but it will be fixed soon) required for the flight. The Aircraft can hold a maximum of 172.5 Blocks (1 Block = 804 KG JET-A Fuel). It should also show that the total flight will be about 442 minutes long using the initialized route. That is 8 hours and 22 minutes, a decent time for about 4000 miles.

* We'll take 10% fuel with us for reserves, so enter '''0/10''' and hit the LSK next to RSV. The mCDU will automatically calculate our extra fuel, TOW (Take-off Weight) and LW (Landing Weight).

* Now, click on F-PLN to go to the Primary Flight-plan Management Page. Here, you'll see the automatically initialized flight plan which you can scroll through using the up and down arrow keys on the keypad. Atm, we don't need to make any changes to our flight-plan as the company route sets everything perfect for us. We'll come back to F-PLN Lateral Revision (LAT REV) in the next custom planned example flight.

* We need to select a DEPARTURE and ARRIVAL procedure for our flight. To select a DEPARTURE Terminal Procedure, click on the LSK next to YBBN (Right above F-PLN DISCONTINUITY) and click on the LSK next to DEPARTURE.

* I'll be using runway 19 for departure (Currently Winds are 200@9), so I click on the LSK next to 19.

* Our first waypoint (after YBBN) is WOODY, so I want a DEPARTURE PROCEDURE that'll take me to WOODY. A procedure available for Runway 19 is ''WODY2A.19'' (at the end of the list). Select that and hit the LSK next to INSERT.

* Now, for the arrival procedure, you want to find your last waypoint before WSSS, so go to the F-PLN page and scroll to the end. With this route, ''REPOV'' is the last waypoint. (With MIABNESIN1, LAVAX is the last waypoint.

* Scroll back up and click on the LSK next to DEST WSSS and then select ARRIVAL.

* We'll be landing on Runway 20R (usually the default intl. runway at WSSS), so I select 20R. For the Arrival Procedure, select and INSERT REME6B.20R as that procedure starts at REPOV.

''NOTE: Small sections based on the PERF, DIR and PROG pages are remaining but we'll get back to that once it's completely functional.''

We have completed out basic flight-planning. We will focus on Radio Navigation later. Let's now fuel up for the flight. As we entered in the mCDU, we'll be starting with 130 blocks of fuel for this 8 and a half hour flight. That's 104,500 KG JET-A fuel. Open the Fuel Truck dialog, enable to truck, connect it to the aircraft, enter '''104500''' in hte REQUEST KG and Start Filling up the aircraft. Once the fueling is complete, we can disconnect the fuel truck and proceed to starting up the aircraft. Remember to first disconnect all ground services and remove the chokes.

==== Manual Engines Start-Up Procedure ====

* Turn on the Beacon Lights from the Lighting Control Panel.

* Look up at the overhead panel and turn on the APU by turning on the APU MASTER SW and the START button. You should hear the APU spooling. Once it's started, turn off the APU START switch and turn on the APU GEN.

* To get fuel to the engines, you need to turn on the LTK PUMPS, so turn on all the ENG1, ENG2 and CTR TNK FUEL PUMPS.

* Switch to Pedestal View and in the throttle quadrant, set the Engine MODE to START, and then turn both engine master switches to ON.

* Keep an eye on the Upper ECAM. When both Engine N1% exceeds 25%, the engines are started and running. Turn the Engine MODE back to NORM and turn off the APU.

* Turn on the Navigation Lights.

Release Parking Brakes and use 2 notches of Flaps for take-off. Pushback and taxi to the runway as usual. While taxiing, you could set your autopilot and other preferences. For autopilot, I'm going to make sure everything is disarmed and then set speed to IAS:250|MACH:0.72, altitude to 36000 ft (switch the black knob in behind the ALT knob to 1000 for easier scrolling, V/S to 2200 and finally click on the HDG knob to turn it to ''Managed'' Mode. You can also set ND and Lower ECAM Display Pages- I use the NAV page on the ND with 40 nm range (VORD, NDB and ARPT selected), and normally keep the FUEL page on the Lower ECAM. If you need to check another system, you can use the switching panel to change to that display.

Finally, remember to set your altimeter setting. Get your altimeter setting from Environment>Weather and scroll the altimeter setting knob on the Glare-shield panel to that reading.

''NOTE: Managed Mode means the FMGC tells the computer where the plane should go. This is equivalent to LNAV on Boeing aircraft.''

==== Take-off and Cruise ====

Once you're holding short, revise your reference speeds. At this weight, they'd be- V1:140, Vr:150, V2:156.

When the runway is clear (and/or you have ATC's permission), taxi on to the runway and turn on the Strobe Lights. Power up the throttle all the way, and rotate at Vr and make sure you're airborne by V2. Retract your gears and when you reach the respective flaps extension speeds (PRINTED ON THE MAIN PANEL), retract the respective flaps. Once you've maintained a steady climb, turn on the A/THR and AP1 from the Glare-shield panel.

The autopilot will automatically fly the departure procedure you entered and then transition to the F-PLN (flight-plan) from the Company Route. Once over 10000 ft, switch to 280 KIAS Speed and keep climbing, Around 18000 ft, switch to mach (setting at 0.72) and reduce the V/S to around 1800 fpm.

Once you're over FL260 (26000 ft), reduce your V/S to 1000 fpm and increase mach to 0.78. Then sit back and relax (or go do something else) while the computer automatically takes you to your destination.

'''REST COMING UP SOON'''

=== GA860 from Jakarta to Hong Kong ===

GA860 is a daily ''Garuda Indonesia'' Route flown with an Airbus A330-243.

'''More Info about this example Flight coming soon...'''

== Liveries ==
The Airbus A330-200 series have liveries for each variant (203, 223 an 243) and are managed by Chris Mueffelmann. Please let us know if you're creating a livery by changing the status on the livery below so that duplicates are avoided.

=== Airbus A330-203 operators ===

''ALL LIVERIES COMPLETE!''

{|
| valign="top" |
* Afriqiyah Airways - '''COMPLETED'''
* Air Europa - '''COMPLETED'''
* Air France - '''COMPLETED'''
* EVA Air - '''COMPLETED'''
* EVA Air (Hello Kitty) - '''COMPLETED'''
| valign="top" |
* KLM Royal Dutch Airline - '''COMPLETED'''
* Qantas Airways - '''COMPLETED'''
* Qatar Airways - '''COMPLETED'''
* TAM Linhas Aereas - '''COMPLETED'''
* Turkish - '''COMPLETED'''
|}

=== Airbus A330-223 operators ===
{|
| valign="top" |
* Air Berlin - '''COMPLETED'''
* Air Caraibes
* Air Greenland - '''COMPLETED'''
* Air India
* Atlasjet - '''DEVEL''' (''Chris'')
* Brussels Airlines - '''COMPLETED'''
* China Southern - '''COMPLETED'''
* Delta Airlines - '''COMPLETED'''
* Edelweiss Air - '''COMPLETED'''
| valign="top" |
* Eurofly
* Hong Kong Airlines
* Korean Air - '''COMPLETED'''
* Malaysia Airlines - '''COMPLETED'''
* Royal Jordanian - '''COMPLETED'''
* Swiss International Air Lines - '''COMPLETED'''
* TAM Linhas Aereas- '''COMPLETED'''
* TAP Portugal - '''COMPLETED'''
* Vietnam Airlines - '''COMPLETED'''
|}

===Airbus A330-243 operators===
{|
| valign="top" |
* Aeroflot
* Air China - '''COMPLETED'''
* Air Europa - '''COMPLETED'''
* Air Nigeria
* Air Transat - '''DEVEL''' (''Chris'')
* Avianca
* Berkut Air
* China Eastern
* Corsairfly
* Cyprus Airways - '''COMPLETED'''
* Egyptair - '''COMPLETED'''
* Emirates - '''COMPLETED'''
* Etihad - '''COMPLETED'''
* Garuda Indonesia - '''COMPLETED'''
* Gulf Air
* Hainan Airlines
| valign="top" |
* Hawaiian Air
* Hifly Airways
* Hong Kong Airlines
* Jet Airways - '''COMPLETED'''
* Middle East Airlines
* Monarch Airways
* Oman Air
* Sichuan Airlines - '''COMPLETED'''
* South African Airways - '''COMPLETED'''
* SriLankan Airlines - '''COMPLETED'''
* Thomas Cook Airlines - '''DEVEL''' (''Chris'')
* Thomas Cook Scandinavia - '''DEVEL''' (''Chris'')
* US Airways
* Virgin Australia
* XL Airways
* Yemenia Airlines
|}

==Default Flight Database==

The Default Flight Database contains [[Merlion Virtual Airlines]] Airbus A330-200 Routes. This database can be used by anyone, whether he/she is a merlion pilot or not. The example flight above explains how to use routes from the Flight Database.

If you fly for a different Virtual Airline which uses the Airbus A330-200 (203/223/243), please contact your staff for the flight database.

* Current Active Database - '''MIA_Data_v3.1''' ''(27MAY-26AUG)''
* Previous (Standby) Database - '''MIA_Data_v3.0''' (DOES NOT EXIST YET)

===Available Routes Tables===

''The following routes are complete and available.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA131 || WSSS || YBBN || S-QDAZ || MIASINBNE1, MIASINBNE2
|-
| MIA132 || YBBN || NZAA || S-QDAZ || MIABNEAKL1
|-
| MIA133 || NZAA || YBBN || S-QDAZ || MIAAKLBNE1
|-
| MIA134 || YBBN || WSSS || S-QDAZ || MIABNESIN1, MIABNESIN2
|-
| MIA135 || WSSS || FAJS || S-QDBZ || MIASINJNB1
|-
| MIA136 || FAJS || SBGR || S-QDBZ || MIAJNBGRU1
|-
| MIA137 || SBGR || FAJS || S-QDBZ || MIAGRUJNB1
|-
| MIA138 || FAJS || WSSS || S-QDBZ || MIAJNBSIN1
|-
| MIA139 || WSSS || RJGG || S-QDCZ || MIASINNGO1
|-
| MIA140 || RJGG || KLAX || S-QDCZ || MIANGOLAX1
|-
| MIA141 || KLAX || RJGG || S-QDCZ || MIALAXNGO1
|-
| MIA142 || RJGG || WSSS || S-QDCZ || MIANGOSIN1, MIANGOSIN2
|}

''The following Routes will be available soon.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA143 || WSSS || UHWW || S-QDDZ || MIASINVVO1
|-
| MIA144 || UHWW || CYVR || S-QDDZ || MIAVVOVYR1
|-
| MIA145 || CYVR || UHWW || S-QDDZ || MIAVYRVVO1
|-
| MIA146 || UHWW || WSSS || S-QDDZ || MIAVVOSIN1
|-
| MIA147 || WSSS || OMDB || S-QDEZ || MIASINDXB1, MIASINDXB2
|-
| MIA148 || OMDB || EDDF || S-QDEZ || MIADXBFRA1, MIADXBFRA2
|-
| MIA149 || EDDF || OMDB || S-QDEZ || MIAFRADXB1
|-
| MIA150 || OMDB || WSSS || S-QDEZ || MIADXBSIN1, MIASXBSIN2
|-
| MIA151 || WSSS || LEBL || S-QDFZ || MIASINBCN1
|-
| MIA152 || LEBL || TNCM || S-QDFZ || MIABCNSXM1
|-
| MIA153 || TNCM || LEBL || S-QDFZ || MIASXMBCN1
|-
| MIA154 || LEBL || WSSS || S-QDFZ || MIABCNSIN1
|-
| MIA155 || WSSS || LEBL || S-QDGZ || MIASINBCN1
|-
| MIA156 || LEBL || KMIA || S-QDGZ || MIABCNMIA1
|-
| MIA157 || KMIA || LEBL || S-QDGZ || MIAMIABCN1
|-
| MIA158 || LEBL || WSSS || S-QDGZ || MIABCNSIN1
|-
| MIA159 || WSSS || EHAM || S-QDHZ || MIASINAMS1, MIASINAMS2
|-
| MIA160 || EHAM || KMIA || S-QDHZ || MIAAMSMIA1
|-
| MIA161 || KMIA || EHAM || S-QDHZ || MIAMIAAMS1
|-
| MIA162 || EHAM || WSSS || S-QDHZ || MIAAMSSIN1, MIAAMSSIN2
|-
| MIA163 || WSSS || UUDD || S-QDIZ || MIASINDME1
|-
| MIA164 || UUDD || KJFK || S-QDIZ || MIADMEJFK1
|-
| MIA165 || KJFK || UUDD || S-QDIZ || MIAJFKDME1, MIAJFKDME2
|-
| MIA166 || UUDD || WSSS || S-QDIZ || MIADMESIN1, MIADMESIN2
|}

==Important developments remaining==

''We have completed the highest priority developments on the list, if you'd like us to do anything for the aircraft, please make a note below.''

==Important Recently Completed Developments==

* Modeled the Rolls Royce Trent 772B-60 Engines for the A330-243
* Animated Flaps, Speed-brakes and Parking Brake Levers (NOT PICK, ONLY TRANS/ROTATE)
* Animated the Throttle Quadrant (incl. Engine cutoffs - REQUIRED FOR MANUAL START-UP) - ''Manual Start-up is now possible''
* Fixed the '''Blue''' Hydraulic System
* Completed Separate Engine Sounds for the each variant

== External link ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]

{{Airbus}}

[[Category:Airliners]]