https://wiki.flightgear.org/w/api.php?action=feedcontributions&feedformat=atom&user=Scotth1FlightGear wiki - User contributions [en]2026-05-27T14:52:43ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=Airbus_A350_XWB&diff=61851Airbus A350 XWB2013-07-27T13:14:20Z<p>Scotth1: </p>
<hr />
<div>{{non-stable}}<br />
{{aero-stub}}<br />
<br />
{{infobox Aircraft<br />
|name =Airbus A350XWB<br />
|type =Airliner<br />
|fdm =JSBSim<br />
|status =Under development<br />
|authors =ACJZA, Sbyx, PK-001<br />
|fgname =A350-800, A350-900, A350-1000<br />
}}<br />
<br />
The '''Airbus A350''' is a long-range, mid-size, wide-body family of airliners currently under development by European manufacturing group [[:Category:Airbus|Airbus]]. The A350 will be the first Airbus with fuselage and wing structures made primarily of carbon fibre-reinforced plastic. The A350 is designed to compete with the [[Boeing 777]] and the [[Boeing 787]]. Airbus claims that it will be more fuel-efficient, with up to 8% lower operating cost than the Boeing 787. It is scheduled to enter into airline service in 2013.<br />
<br />
== Work stage ==<br />
<br />
=== Completed ===<br />
* Engines <br />
* Model<br />
<br />
=== In progress ===<br />
* Liveries<br />
* XML's<br />
* Cabin<br />
* Cockpit<br />
<br />
=== To do ===<br />
* Animations<br />
{{Airbus}}<br />
<br />
[[Category:Airliners]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=59626Airbus A3802013-04-25T13:30:25Z<p>Scotth1: small updates to status</p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|liverydbid = 5<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status-fdm = 4<br />
|status-systems = 4<br />
|status-cockpit = 4<br />
|status-model = 4<br />
|fgname = A380<br />
|download = <br />
|development = http://gitorious.org/airbus-aircraft/a380<br />
}}<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest freight aircraft, with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,700 kilometres (8,500 nm), sufficient to fly from Sydney to Helsinki, or Concepción to Dubai for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
An [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: [[$FG_ROOT]]/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions<br />
* auto changeover level<br />
* Environment Control System (cabin pressurisation)<br />
* auto-tuned VOR on NAV2<br />
* anti-ice and air packs take bleed air<br />
* Rembrandt lighting for;<br />
** cockpit lighting<br />
** cockpit panel lighting<br />
** wing lighting<br />
** landing lights<br />
** tail logo lighting<br />
** cabin lighting<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localizer and approach<br />
* Flight Director, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS<br />
* ND nearby airports display switch on EFIS<br />
* ND traffic display switch on EFIS<br />
* airspeed AP control on FCU selectable between knots or mach value<br />
* altitude selectable between 100ft and 1000ft<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* localizer and Glide scope indicators on PFD<br />
* E/WD<br />
* updated Nav Display<br />
** ARC mode<br />
** ROSE mode<br />
** aerodrome moving map with 'ZOOM' scale in PLAN mode<br />
** nearby airports on ND^<br />
** multi-player and AI traffic on ND<br />
** VOR/ADF left-hand and right-hand display<br />
* E/WD checklists<br />
* gear lever and indicators<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel<br />
* air panel<br />
* anti-ice panel<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC<br />
** electrical DC<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance<br />
** Active Flight Plan<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and <del>speed brake</del><br />
* <del>cabin interior</del><br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* <del>engine start sounds</del><br />
* <del>complete PFD and EFIS selection switches</del><br />
* <del>complete ND EFIS selection switches</del>^<br />
* <del>complete ND display modes</del><br />
** PLAN<br />
** <del>LS</del><br />
** <del>VOR</del><br />
** <del>MAP</del><br />
* add standard procedure check-lists to EWD<br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
** <del>DOOR</del><br />
** <del>APU</del><br />
** <del>ENGINE</del><br />
** COND<br />
** WHEEL<br />
** PRESSURE<br />
** BLEED<br />
** <del>ELEC AC</del><br />
** <del>ELEC DC</del><br />
** <del>FUEL</del><br />
** HYDRAULIC<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* <del>gear lever and indicators</del><br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; <del>cabin pressure</del> and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* <del>fix up scaling of texture sizes</del><br />
* ATN/FANS+ <br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Airliners]]<br />
[[Category:Quadjets]]<br />
[[Category:Cargo aircraft]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A330-200_(Old)&diff=51315Airbus A330-200 (Old)2012-06-28T13:28:43Z<p>Scotth1: /* Airbus A330-203 operators */</p>
<hr />
<div>{{infobox Aircraft<br />
|image = A332-splash.png<br />
|name = Airbus A330-200 Series<br />
|type = Wide-body Airliner<br />
|fdm = JSBSim<br />
|status = v2.0, Git Development Version<br />
|authors = Narendran M, Chris M, Zhuang T, Geir M, Kyle D, A320neo Developers<br />
|fgname = A330-203, A330-223, A330-243<br />
|download = http://theomegahangar.yolasite.com/aircraft.php<br />
|development = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main<br />
}}<br />
<br />
This aircraft package is now rembrandt compatible! (Simply checkout the rembrandt branch from the git repository to get it)<br />
<br />
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. 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.<br />
<br />
==Airbus Systems==<br />
<br />
===Airbus Fly-By-Wire===<br />
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.<br />
<br />
====Pitch/Roll-Rate and G-Force Command====<br />
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.<br />
<br />
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. <br />
<br />
====Flight Envelope Protection====<br />
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.<br />
<br />
For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.<br />
<br />
=== Hydraulics System ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.<br />
<br />
'''MORE SYSTEMS INFORMATION COMING SOON'''<br />
<br />
== Example Flights ==<br />
<br />
We'll show 2 example flights- a flight that uses a company route from the default flight database and a custom planned flight.<br />
<br />
=== MIA134 from Brisbane to Singapore (Company Route) ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Pre-Flight Planning ====<br />
<br />
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)<br />
<br />
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.<br />
<br />
* Turn to the ''FMGC/mCDU View'' and turn on the Airbus mCDU by rotating (scroll) the BRT knob to full.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* Enter the Flight Number '''MIA134''' and click on the LSK next to FLT NUM. '''(OPTIONAL)'''<br />
<br />
* If you want, you can also enter a COST INDEX for the flight (normally between 25 and 40). '''(OPTIONAL)'''<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
''NOTE: To get the '''-''', press on the '''+/-''' key in the keypad twice.''<br />
<br />
* 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.<br />
<br />
''NOTE: Please skip the next 2 steps for the moment as this part requires fixing.''<br />
<br />
* 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.<br />
<br />
* 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).<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* I'll be using runway 19 for departure (Currently Winds are 200@9), so I click on the LSK next to 19.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* Scroll back up and click on the LSK next to DEST WSSS and then select ARRIVAL.<br />
<br />
* 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.<br />
<br />
''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.''<br />
<br />
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.<br />
<br />
==== Manual Engines Start-Up Procedure ====<br />
<br />
* Turn on the Beacon Lights from the Lighting Control Panel.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* Switch to Pedestal View and in the throttle quadrant, set the Engine MODE to START, and then turn both engine master switches to ON.<br />
<br />
* 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.<br />
<br />
* Turn on the Navigation Lights.<br />
<br />
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.<br />
<br />
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.<br />
<br />
''NOTE: Managed Mode means the FMGC tells the computer where the plane should go. This is equivalent to LNAV on Boeing aircraft.''<br />
<br />
==== Take-off and Cruise ====<br />
<br />
Once you're holding short, revise your reference speeds. At this weight, they'd be- V1:140, Vr:150, V2:156.<br />
<br />
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.<br />
<br />
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. <br />
<br />
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. <br />
<br />
'''REST COMING UP SOON'''<br />
<br />
=== Custom Emirates Flight from Frankfurt to Munich ===<br />
<br />
This flight was requested by Detlef N. (MIA0283), and video tutorials were recorded for different sections of the flight. The videos can be viewed below or in the ''FlightGear Airbus'' YouTube channel. Thank you for watching!<br />
<br />
==== Flight Planning ====<br />
<br />
{{#ev:youtube|R66q_10dwKw|480|Part 1: Flight Planning}}<br />
<br />
==== Manual Start-up ====<br />
<br />
{{#ev:youtube|8TI14RJDn2k|480|Part 2: Manual Start-up}}<br />
<br />
==== Take-off and Climb ====<br />
<br />
{{#ev:youtube|IpkdhebC4-o|480|Part 3: Take-off and Climb}}<br />
<br />
''NOTE: Cruise skipped due to the fact that it may be '''boring'''''...<br />
<br />
==== Descent and Autoland ====<br />
<br />
{{#ev:youtube|NeX3samzrqU|480|Part 4: Descent and Autoland}}<br />
<br />
== Liveries ==<br />
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.<br />
<br />
=== Airbus A330-203 operators ===<br />
<br />
''ALL LIVERIES COMPLETE!''<br />
<br />
{|<br />
| valign="top" |<br />
* Afriqiyah Airways - '''COMPLETED'''<br />
* Air Algérie<br />
* Air Caledonie International (Aircalin)<br />
* Air Europa - '''COMPLETED'''<br />
* Air France - '''COMPLETED'''<br />
* Air Mauritius<br />
* Alitalia<br />
* EVA Air - '''COMPLETED'''<br />
* EVA Air (Hello Kitty) - '''COMPLETED'''<br />
| valign="top" |<br />
* Jet Airways<br />
* Jetstar Airways<br />
* KLM Royal Dutch Airline - '''COMPLETED'''<br />
* Qantas Airways - '''COMPLETED'''<br />
* Qatar Airways - '''COMPLETED'''<br />
* TAM Linhas Aereas - '''COMPLETED'''<br />
* TAP Air Portugal<br />
* Turkish - '''COMPLETED'''<br />
|}<br />
<br />
=== Airbus A330-223 operators ===<br />
{|<br />
| valign="top" |<br />
* Air Berlin - '''COMPLETED'''<br />
* Air Caraibes<br />
* Air Greenland - '''COMPLETED'''<br />
* Air India - '''COMPLTED'''<br />
* Atlasjet - '''COMPLETED'''<br />
* Brussels Airlines - '''COMPLETED'''<br />
* China Southern - '''COMPLETED'''<br />
* Delta Airlines - '''COMPLETED'''<br />
* Edelweiss Air - '''COMPLETED'''<br />
| valign="top" |<br />
* Eurofly - '''COMPLETED'''<br />
* Hong Kong Airlines - '''COMPLETED'''<br />
* Korean Air - '''COMPLETED'''<br />
* Malaysia Airlines - '''COMPLETED'''<br />
* Royal Jordanian - '''COMPLETED'''<br />
* Swiss International Air Lines - '''COMPLETED'''<br />
* TAM Linhas Aereas- '''COMPLETED''' <br />
* TAP Portugal - '''COMPLETED'''<br />
* Vietnam Airlines - '''COMPLETED'''<br />
|}<br />
<br />
===Airbus A330-243 operators===<br />
{|<br />
| valign="top" |<br />
* Aeroflot<br />
* Air China - '''COMPLETED'''<br />
* Air Europa - '''COMPLETED'''<br />
* Air Nigeria<br />
* Air Transat - '''COMPLETED'''<br />
* Avianca - '''COMPLETED'''<br />
* China Eastern - '''COMPLETED'''<br />
* Corsairfly - '''COMPLETED'''<br />
* Cyprus Airways - '''COMPLETED'''<br />
* Egyptair - '''COMPLETED'''<br />
* Emirates - '''COMPLETED'''<br />
* Etihad - '''COMPLETED'''<br />
* Garuda Indonesia - '''COMPLETED'''<br />
* Gulf Air<br />
* Hainan Airlines<br />
* Hawaiian Air<br />
| valign="top" |<br />
* Hi Fly - '''COMPLETED'''<br />
* Hong Kong Airlines - '''COMPLETED'''<br />
* Jet Airways - '''COMPLETED'''<br />
* Middle East Airlines<br />
* Monarch Airways<br />
* Oman Air<br />
* Sichuan Airlines - '''COMPLETED'''<br />
* South African Airways - '''COMPLETED'''<br />
* SriLankan Airlines - '''COMPLETED'''<br />
* Thomas Cook Airlines - '''COMPLETED'''<br />
* Thomas Cook Scandinavia - '''COMPLETED'''<br />
* US Airways<br />
* Virgin Australia<br />
* XL Airways<br />
* Yemenia Airlines - '''COMPLETED'''<br />
|}<br />
<br />
==Default Flight Database==<br />
<br />
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.<br />
<br />
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.<br />
<br />
* Current Active Database - '''MIA_Data_v3.1''' ''(27MAY-26AUG)''<br />
* Previous (Standby) Database - '''MIA_Data_v3.0''' (DOES NOT EXIST YET)<br />
<br />
===Available Routes Tables===<br />
<br />
''The following routes are complete and available.''<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)<br />
|-<br />
| MIA131 || WSSS || YBBN || S-QDAZ || MIASINBNE1, MIASINBNE2<br />
|-<br />
| MIA132 || YBBN || NZAA || S-QDAZ || MIABNEAKL1<br />
|-<br />
| MIA133 || NZAA || YBBN || S-QDAZ || MIAAKLBNE1<br />
|-<br />
| MIA134 || YBBN || WSSS || S-QDAZ || MIABNESIN1, MIABNESIN2<br />
|-<br />
| MIA135 || WSSS || FAJS || S-QDBZ || MIASINJNB1<br />
|-<br />
| MIA136 || FAJS || SBGR || S-QDBZ || MIAJNBGRU1<br />
|-<br />
| MIA137 || SBGR || FAJS || S-QDBZ || MIAGRUJNB1<br />
|-<br />
| MIA138 || FAJS || WSSS || S-QDBZ || MIAJNBSIN1<br />
|-<br />
| MIA139 || WSSS || RJGG || S-QDCZ || MIASINNGO1<br />
|-<br />
| MIA140 || RJGG || KLAX || S-QDCZ || MIANGOLAX1<br />
|-<br />
| MIA141 || KLAX || RJGG || S-QDCZ || MIALAXNGO1<br />
|-<br />
| MIA142 || RJGG || WSSS || S-QDCZ || MIANGOSIN1, MIANGOSIN2<br />
|}<br />
<br />
''The following Routes will be available soon.''<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)<br />
|-<br />
| MIA143 || WSSS || UHWW || S-QDDZ || MIASINVVO1<br />
|-<br />
| MIA144 || UHWW || CYVR || S-QDDZ || MIAVVOVYR1<br />
|-<br />
| MIA145 || CYVR || UHWW || S-QDDZ || MIAVYRVVO1<br />
|-<br />
| MIA146 || UHWW || WSSS || S-QDDZ || MIAVVOSIN1<br />
|-<br />
| MIA147 || WSSS || OMDB || S-QDEZ || MIASINDXB1, MIASINDXB2<br />
|-<br />
| MIA148 || OMDB || EDDF || S-QDEZ || MIADXBFRA1, MIADXBFRA2<br />
|-<br />
| MIA149 || EDDF || OMDB || S-QDEZ || MIAFRADXB1<br />
|-<br />
| MIA150 || OMDB || WSSS || S-QDEZ || MIADXBSIN1, MIASXBSIN2<br />
|-<br />
| MIA151 || WSSS || LEBL || S-QDFZ || MIASINBCN1<br />
|-<br />
| MIA152 || LEBL || TNCM || S-QDFZ || MIABCNSXM1<br />
|-<br />
| MIA153 || TNCM || LEBL || S-QDFZ || MIASXMBCN1<br />
|-<br />
| MIA154 || LEBL || WSSS || S-QDFZ || MIABCNSIN1<br />
|-<br />
| MIA155 || WSSS || LEBL || S-QDGZ || MIASINBCN1<br />
|-<br />
| MIA156 || LEBL || KMIA || S-QDGZ || MIABCNMIA1<br />
|-<br />
| MIA157 || KMIA || LEBL || S-QDGZ || MIAMIABCN1<br />
|-<br />
| MIA158 || LEBL || WSSS || S-QDGZ || MIABCNSIN1<br />
|-<br />
| MIA159 || WSSS || EHAM || S-QDHZ || MIASINAMS1, MIASINAMS2<br />
|-<br />
| MIA160 || EHAM || KMIA || S-QDHZ || MIAAMSMIA1<br />
|-<br />
| MIA161 || KMIA || EHAM || S-QDHZ || MIAMIAAMS1<br />
|-<br />
| MIA162 || EHAM || WSSS || S-QDHZ || MIAAMSSIN1, MIAAMSSIN2<br />
|-<br />
| MIA163 || WSSS || UUDD || S-QDIZ || MIASINDME1<br />
|-<br />
| MIA164 || UUDD || KJFK || S-QDIZ || MIADMEJFK1<br />
|-<br />
| MIA165 || KJFK || UUDD || S-QDIZ || MIAJFKDME1, MIAJFKDME2<br />
|-<br />
| MIA166 || UUDD || WSSS || S-QDIZ || MIADMESIN1, MIADMESIN2<br />
|}<br />
<br />
==Important developments remaining==<br />
<br />
''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.''<br />
<br />
==Important Recently Completed Developments==<br />
<br />
* Modeled the Rolls Royce Trent 772B-60 Engines for the A330-243<br />
* Animated Flaps, Speed-brakes and Parking Brake Levers (NOT PICK, ONLY TRANS/ROTATE)<br />
* Animated the Throttle Quadrant (incl. Engine cutoffs - REQUIRED FOR MANUAL START-UP) - ''Manual Start-up is now possible''<br />
* Fixed the '''Blue''' Hydraulic System<br />
* Completed Separate Engine Sounds for the each variant<br />
<br />
== External link ==<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Airliners]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A330-200_(Old)&diff=51314Airbus A330-200 (Old)2012-06-28T13:08:49Z<p>Scotth1: /* Airbus A330-203 operators */</p>
<hr />
<div>{{infobox Aircraft<br />
|image = A332-splash.png<br />
|name = Airbus A330-200 Series<br />
|type = Wide-body Airliner<br />
|fdm = JSBSim<br />
|status = v2.0, Git Development Version<br />
|authors = Narendran M, Chris M, Zhuang T, Geir M, Kyle D, A320neo Developers<br />
|fgname = A330-203, A330-223, A330-243<br />
|download = http://theomegahangar.yolasite.com/aircraft.php<br />
|development = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main<br />
}}<br />
<br />
This aircraft package is now rembrandt compatible! (Simply checkout the rembrandt branch from the git repository to get it)<br />
<br />
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. 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.<br />
<br />
==Airbus Systems==<br />
<br />
===Airbus Fly-By-Wire===<br />
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.<br />
<br />
====Pitch/Roll-Rate and G-Force Command====<br />
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.<br />
<br />
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. <br />
<br />
====Flight Envelope Protection====<br />
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.<br />
<br />
For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.<br />
<br />
=== Hydraulics System ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.<br />
<br />
'''MORE SYSTEMS INFORMATION COMING SOON'''<br />
<br />
== Example Flights ==<br />
<br />
We'll show 2 example flights- a flight that uses a company route from the default flight database and a custom planned flight.<br />
<br />
=== MIA134 from Brisbane to Singapore (Company Route) ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Pre-Flight Planning ====<br />
<br />
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)<br />
<br />
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.<br />
<br />
* Turn to the ''FMGC/mCDU View'' and turn on the Airbus mCDU by rotating (scroll) the BRT knob to full.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* Enter the Flight Number '''MIA134''' and click on the LSK next to FLT NUM. '''(OPTIONAL)'''<br />
<br />
* If you want, you can also enter a COST INDEX for the flight (normally between 25 and 40). '''(OPTIONAL)'''<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
''NOTE: To get the '''-''', press on the '''+/-''' key in the keypad twice.''<br />
<br />
* 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.<br />
<br />
''NOTE: Please skip the next 2 steps for the moment as this part requires fixing.''<br />
<br />
* 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.<br />
<br />
* 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).<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* I'll be using runway 19 for departure (Currently Winds are 200@9), so I click on the LSK next to 19.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* Scroll back up and click on the LSK next to DEST WSSS and then select ARRIVAL.<br />
<br />
* 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.<br />
<br />
''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.''<br />
<br />
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.<br />
<br />
==== Manual Engines Start-Up Procedure ====<br />
<br />
* Turn on the Beacon Lights from the Lighting Control Panel.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* Switch to Pedestal View and in the throttle quadrant, set the Engine MODE to START, and then turn both engine master switches to ON.<br />
<br />
* 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.<br />
<br />
* Turn on the Navigation Lights.<br />
<br />
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.<br />
<br />
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.<br />
<br />
''NOTE: Managed Mode means the FMGC tells the computer where the plane should go. This is equivalent to LNAV on Boeing aircraft.''<br />
<br />
==== Take-off and Cruise ====<br />
<br />
Once you're holding short, revise your reference speeds. At this weight, they'd be- V1:140, Vr:150, V2:156.<br />
<br />
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.<br />
<br />
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. <br />
<br />
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. <br />
<br />
'''REST COMING UP SOON'''<br />
<br />
=== Custom Emirates Flight from Frankfurt to Munich ===<br />
<br />
This flight was requested by Detlef N. (MIA0283), and video tutorials were recorded for different sections of the flight. The videos can be viewed below or in the ''FlightGear Airbus'' YouTube channel. Thank you for watching!<br />
<br />
==== Flight Planning ====<br />
<br />
{{#ev:youtube|R66q_10dwKw|480|Part 1: Flight Planning}}<br />
<br />
==== Manual Start-up ====<br />
<br />
{{#ev:youtube|8TI14RJDn2k|480|Part 2: Manual Start-up}}<br />
<br />
==== Take-off and Climb ====<br />
<br />
{{#ev:youtube|IpkdhebC4-o|480|Part 3: Take-off and Climb}}<br />
<br />
''NOTE: Cruise skipped due to the fact that it may be '''boring'''''...<br />
<br />
==== Descent and Autoland ====<br />
<br />
{{#ev:youtube|NeX3samzrqU|480|Part 4: Descent and Autoland}}<br />
<br />
== Liveries ==<br />
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.<br />
<br />
=== Airbus A330-203 operators ===<br />
<br />
''ALL LIVERIES COMPLETE!''<br />
<br />
{|<br />
| valign="top" |<br />
* Afriqiyah Airways - '''COMPLETED'''<br />
* Air Europa - '''COMPLETED'''<br />
* Air France - '''COMPLETED'''<br />
* EVA Air - '''COMPLETED'''<br />
* EVA Air (Hello Kitty) - '''COMPLETED'''<br />
* Jetstar Airways<br />
| valign="top" |<br />
* KLM Royal Dutch Airline - '''COMPLETED'''<br />
* Qantas Airways - '''COMPLETED'''<br />
* Qatar Airways - '''COMPLETED'''<br />
* TAM Linhas Aereas - '''COMPLETED'''<br />
* Turkish - '''COMPLETED'''<br />
|}<br />
<br />
=== Airbus A330-223 operators ===<br />
{|<br />
| valign="top" |<br />
* Air Berlin - '''COMPLETED'''<br />
* Air Caraibes<br />
* Air Greenland - '''COMPLETED'''<br />
* Air India - '''COMPLTED'''<br />
* Atlasjet - '''COMPLETED'''<br />
* Brussels Airlines - '''COMPLETED'''<br />
* China Southern - '''COMPLETED'''<br />
* Delta Airlines - '''COMPLETED'''<br />
* Edelweiss Air - '''COMPLETED'''<br />
| valign="top" |<br />
* Eurofly - '''COMPLETED'''<br />
* Hong Kong Airlines - '''COMPLETED'''<br />
* Korean Air - '''COMPLETED'''<br />
* Malaysia Airlines - '''COMPLETED'''<br />
* Royal Jordanian - '''COMPLETED'''<br />
* Swiss International Air Lines - '''COMPLETED'''<br />
* TAM Linhas Aereas- '''COMPLETED''' <br />
* TAP Portugal - '''COMPLETED'''<br />
* Vietnam Airlines - '''COMPLETED'''<br />
|}<br />
<br />
===Airbus A330-243 operators===<br />
{|<br />
| valign="top" |<br />
* Aeroflot<br />
* Air China - '''COMPLETED'''<br />
* Air Europa - '''COMPLETED'''<br />
* Air Nigeria<br />
* Air Transat - '''COMPLETED'''<br />
* Avianca - '''COMPLETED'''<br />
* China Eastern - '''COMPLETED'''<br />
* Corsairfly - '''COMPLETED'''<br />
* Cyprus Airways - '''COMPLETED'''<br />
* Egyptair - '''COMPLETED'''<br />
* Emirates - '''COMPLETED'''<br />
* Etihad - '''COMPLETED'''<br />
* Garuda Indonesia - '''COMPLETED'''<br />
* Gulf Air<br />
* Hainan Airlines<br />
* Hawaiian Air<br />
| valign="top" |<br />
* Hi Fly - '''COMPLETED'''<br />
* Hong Kong Airlines - '''COMPLETED'''<br />
* Jet Airways - '''COMPLETED'''<br />
* Middle East Airlines<br />
* Monarch Airways<br />
* Oman Air<br />
* Sichuan Airlines - '''COMPLETED'''<br />
* South African Airways - '''COMPLETED'''<br />
* SriLankan Airlines - '''COMPLETED'''<br />
* Thomas Cook Airlines - '''COMPLETED'''<br />
* Thomas Cook Scandinavia - '''COMPLETED'''<br />
* US Airways<br />
* Virgin Australia<br />
* XL Airways<br />
* Yemenia Airlines - '''COMPLETED'''<br />
|}<br />
<br />
==Default Flight Database==<br />
<br />
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.<br />
<br />
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.<br />
<br />
* Current Active Database - '''MIA_Data_v3.1''' ''(27MAY-26AUG)''<br />
* Previous (Standby) Database - '''MIA_Data_v3.0''' (DOES NOT EXIST YET)<br />
<br />
===Available Routes Tables===<br />
<br />
''The following routes are complete and available.''<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)<br />
|-<br />
| MIA131 || WSSS || YBBN || S-QDAZ || MIASINBNE1, MIASINBNE2<br />
|-<br />
| MIA132 || YBBN || NZAA || S-QDAZ || MIABNEAKL1<br />
|-<br />
| MIA133 || NZAA || YBBN || S-QDAZ || MIAAKLBNE1<br />
|-<br />
| MIA134 || YBBN || WSSS || S-QDAZ || MIABNESIN1, MIABNESIN2<br />
|-<br />
| MIA135 || WSSS || FAJS || S-QDBZ || MIASINJNB1<br />
|-<br />
| MIA136 || FAJS || SBGR || S-QDBZ || MIAJNBGRU1<br />
|-<br />
| MIA137 || SBGR || FAJS || S-QDBZ || MIAGRUJNB1<br />
|-<br />
| MIA138 || FAJS || WSSS || S-QDBZ || MIAJNBSIN1<br />
|-<br />
| MIA139 || WSSS || RJGG || S-QDCZ || MIASINNGO1<br />
|-<br />
| MIA140 || RJGG || KLAX || S-QDCZ || MIANGOLAX1<br />
|-<br />
| MIA141 || KLAX || RJGG || S-QDCZ || MIALAXNGO1<br />
|-<br />
| MIA142 || RJGG || WSSS || S-QDCZ || MIANGOSIN1, MIANGOSIN2<br />
|}<br />
<br />
''The following Routes will be available soon.''<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)<br />
|-<br />
| MIA143 || WSSS || UHWW || S-QDDZ || MIASINVVO1<br />
|-<br />
| MIA144 || UHWW || CYVR || S-QDDZ || MIAVVOVYR1<br />
|-<br />
| MIA145 || CYVR || UHWW || S-QDDZ || MIAVYRVVO1<br />
|-<br />
| MIA146 || UHWW || WSSS || S-QDDZ || MIAVVOSIN1<br />
|-<br />
| MIA147 || WSSS || OMDB || S-QDEZ || MIASINDXB1, MIASINDXB2<br />
|-<br />
| MIA148 || OMDB || EDDF || S-QDEZ || MIADXBFRA1, MIADXBFRA2<br />
|-<br />
| MIA149 || EDDF || OMDB || S-QDEZ || MIAFRADXB1<br />
|-<br />
| MIA150 || OMDB || WSSS || S-QDEZ || MIADXBSIN1, MIASXBSIN2<br />
|-<br />
| MIA151 || WSSS || LEBL || S-QDFZ || MIASINBCN1<br />
|-<br />
| MIA152 || LEBL || TNCM || S-QDFZ || MIABCNSXM1<br />
|-<br />
| MIA153 || TNCM || LEBL || S-QDFZ || MIASXMBCN1<br />
|-<br />
| MIA154 || LEBL || WSSS || S-QDFZ || MIABCNSIN1<br />
|-<br />
| MIA155 || WSSS || LEBL || S-QDGZ || MIASINBCN1<br />
|-<br />
| MIA156 || LEBL || KMIA || S-QDGZ || MIABCNMIA1<br />
|-<br />
| MIA157 || KMIA || LEBL || S-QDGZ || MIAMIABCN1<br />
|-<br />
| MIA158 || LEBL || WSSS || S-QDGZ || MIABCNSIN1<br />
|-<br />
| MIA159 || WSSS || EHAM || S-QDHZ || MIASINAMS1, MIASINAMS2<br />
|-<br />
| MIA160 || EHAM || KMIA || S-QDHZ || MIAAMSMIA1<br />
|-<br />
| MIA161 || KMIA || EHAM || S-QDHZ || MIAMIAAMS1<br />
|-<br />
| MIA162 || EHAM || WSSS || S-QDHZ || MIAAMSSIN1, MIAAMSSIN2<br />
|-<br />
| MIA163 || WSSS || UUDD || S-QDIZ || MIASINDME1<br />
|-<br />
| MIA164 || UUDD || KJFK || S-QDIZ || MIADMEJFK1<br />
|-<br />
| MIA165 || KJFK || UUDD || S-QDIZ || MIAJFKDME1, MIAJFKDME2<br />
|-<br />
| MIA166 || UUDD || WSSS || S-QDIZ || MIADMESIN1, MIADMESIN2<br />
|}<br />
<br />
==Important developments remaining==<br />
<br />
''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.''<br />
<br />
==Important Recently Completed Developments==<br />
<br />
* Modeled the Rolls Royce Trent 772B-60 Engines for the A330-243<br />
* Animated Flaps, Speed-brakes and Parking Brake Levers (NOT PICK, ONLY TRANS/ROTATE)<br />
* Animated the Throttle Quadrant (incl. Engine cutoffs - REQUIRED FOR MANUAL START-UP) - ''Manual Start-up is now possible''<br />
* Fixed the '''Blue''' Hydraulic System<br />
* Completed Separate Engine Sounds for the each variant<br />
<br />
== External link ==<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Airliners]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=51192Airbus A3802012-06-26T12:28:04Z<p>Scotth1: add notes about rembrandt</p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|liverydbid = 5<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status-fdm = 4<br />
|status-systems = 4<br />
|status-cockpit = 4<br />
|status-model = 4<br />
|fgname = A380<br />
|download = <br />
|development = http://gitorious.org/airbus-aircraft/a380<br />
}}<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest [[:Category:Transport aircraft|freight aircraft]], with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
An [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions<br />
* auto changeover level<br />
* Environment Control System (cabin pressurisation)<br />
* auto-tuned VOR on NAV2<br />
* anti-ice and air packs take bleed air<br />
* Rembrandt lighting for;<br />
** cockpit lighting<br />
** cockpit panel lighting<br />
** wing lighting<br />
** landing lights<br />
** tail logo lighting<br />
** cabin lighting<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localiser and approach<br />
* FlightDirector, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS<br />
* ND nearby airports display switch on EFIS<br />
* ND traffic display switch on EFIS<br />
* airspeed AP control on FCU selectable between knots or mach value<br />
* altitude selectable between 100ft and 1000ft<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* localiser and Glidescope indicators on PFD<br />
* E/WD<br />
* updated Nav Display<br />
** ARC mode<br />
** ROSE mode<br />
** aerodrome moving map with 'ZOOM' scale in PLAN mode<br />
** nearby airports on ND^<br />
** multi-player and AI traffic on ND<br />
** VOR/ADF left-hand and right-hand display<br />
* E/WD checklists<br />
* gear lever and indicators<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel<br />
* air panel<br />
* anti-ice panel<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC<br />
** electrical DC<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance<br />
** Active Flight Plan<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and <del>speed brake</del><br />
* cabin interior<br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* engine start sounds^<br />
* complete PFD and EFIS selection switches<br />
* <del>complete ND EFIS selection switches</del>^<br />
* <del>complete ND display modes</del><br />
** PLAN<br />
** LS^<br />
** VOR^<br />
** <del>MAP</del><br />
* add standard procedure check-lists to EWD<br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
** <del>DOOR</del><br />
** <del>APU</del><br />
** <del>ENGINE</del><br />
** COND<br />
** WHEEL<br />
** PRESSURE<br />
** BLEED<br />
** <del>ELEC AC</del><br />
** <del>ELEC DC</del><br />
** <del>FUEL</del><br />
** HYDRAULIC<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* <del>gear lever and indicators</del><br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; <del>cabin pressure</del> and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* fix up scaling of texture sizes^<br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Airliners]]<br />
[[Category:Quadjets]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A320neo/Development&diff=49790Airbus A320neo/Development2012-05-12T23:43:42Z<p>Scotth1: /* Navigation Display */</p>
<hr />
<div>=ToDo List=<br />
==Electrical==<br />
;Files<br />
: /Nasal/electrical.nas - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Nasal/electrical.nas]<br />
<br />
;Notes<br />
: Aircraft already uses '''Syd Adam's''' ''Jet Electrical'' system.<br />
<br />
;To Do<br />
: Move Nasal file to a dedicated directory in the ''Systems'' folder?<br />
<br />
==Hydraulic==<br />
;Asigned Developers<br />
: Narendran<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Files<br />
: All Hydraulic files in ''/Systems/Hydraulics'' Directory<br />
<br />
;Notes<br />
: Will start work on the hydraulic system as soon as the cockpit is ready<br />
<br />
==Instruments==<br />
<br />
;Assigned Developers<br />
: Jon<br />
: Narendran<br />
<br />
;Branch Name<br />
: develop<br />
<br />
;Notes<br />
: PFD - Rebuild 3D Instrument, use better textures and markers - COMPLETE<br />
: Upper ECAM (EICAS) - Rebuild 2D Instrument with latest A320 ECAM Layout (3 section)<br />
<br />
==Pneumatics==<br />
;Asigned Developers<br />
: Narendran<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Notes<br />
: Include basic pneumatic air pressure system, also include system cooling functions.<br />
<br />
<br />
==Fly by Wire==<br />
;Asigned Developers<br />
: Narendran<br />
: Jon Ortuondo (Bicyus)<br />
: Polly<br />
<br />
;Branch name<br />
: fbw-devel<br />
<br />
;Notes<br />
: 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.<br />
<br />
;Files<br />
: Systems/Airbus-fbw/'''Airbus-fbw.nas''' - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.nas]<br />
: Systems/Airbus-fbw/'''Airbus-fbw.xml''' - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.xml]<br />
<br />
;To Do<br />
: Move fbw.nas and a320-fbw.xml to common Systems directory. - ''DONE''<br />
: Update FDM from Airbus-fbw branch<br />
: Further tune PIDs (Polly/Jon?)<br />
: Implement mechanical backup law (requires better systems)<br />
: Study and Implement Flare Mode for NORMAL LAW<br />
<br />
==FMGC, FCU and mCDU==<br />
;Asigned Developer(s)<br />
: Narendran<br />
<br />
;Branch name<br />
: flight<br />
<br />
;Notes<br />
: Using data from smart cockpit and equicom. [http://www.smartcockpit.com/plane/airbus/A320/]<br />
: Making a whole new Autopilot/Route Manager system. < Most of this is complete, but the PIDs need to be played with. (Polly)<br />
: FCU is basically just the old 'Mode Control Panel' but that too requires some extra scripting.<br />
<br />
;Resources<br />
: Equicom mCDU Emulator [http://www.equicom.net/mcdu/]<br />
: SmartCockpit FMGS Doc [http://www.smartcockpit.com/pdf/plane/airbus/A320/misc/0011/]<br />
: SmartCockpit Systems Briefing [http://www.smartcockpit.com/pdf/plane/airbus/A320/misc/0002/]<br />
: SmartCockpit Autoflight Systems [http://www.smartcockpit.com/pdf/plane/airbus/A320/systems/0025/]<br />
<br />
;Completed Sections<br />
:FMGC (AP1, AP2, NAV, A-THR)<br />
:FCU (aka. MCP)<br />
:FMGC (WP Transition Manager)<br />
:mCDU > DATA<br />
:mCDU > F-PLN<br />
:mCDU > LAT REV A<br />
:mCDU > VER REV (SIMPLE)<br />
:mCDU > INIT A<br />
:mCDU > FLT SRC<br />
:mCDU > INIT B (FUEL PRED)<br />
:mCDU > RAD NAV<br />
<br />
;Sections in Progress<br />
:mCDU > LAT REV B (TP)<br />
: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.<br />
:mCDU > PERF<br />
<br />
;Remaining Sections<br />
:mCDU > DIR<br />
:mCDU > PROG<br />
:mCDU > MCDU MENU<br />
:mCDU > WP SRC<br />
:mCDU > NAVAID SRC<br />
:mCDU > RWY SRC<br />
:mCDU > SEC F-PLN<br />
:mCDU > AIRPORT<br />
:mCDU > ATC COMM<br />
<br />
==ECAM procedures and Alarms systems==<br />
;Asigned Developers<br />
: Jon<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Notes<br />
: ''Functionalize'' ALL ECAM Pages :P<br />
<br />
==New Cocpit Model & xml==<br />
;Asigned Developers<br />
: Narendran<br />
: Jon A. Ortuondo (bicyus) - xml<br />
<br />
;Project > Repository > Branch<br />
: FlightGear Airbus Development > airbus-a320neo-devel ([https://gitorious.org/flightgear-airbus-development/airbus-a320neo-devel]) > ''flightdeck''<br />
<br />
;Files<br />
: All Flightdeck models are in root<br />
<br />
;Notes<br />
: Basic shell, panel, glaresheild, sidesticks, seats and pedestal models complete. These have also been textured.<br />
: Overhead panel will be derived from the old one but model will be improved<br />
: Cockpit has been ported into FlightGear<br />
<br />
;To Do<br />
: Animations and re-positioning of instruments - STARTED<br />
: Re-make PFD and EICAS? (current versions are not too realistic)<br />
<br />
==Navigation Display==<br />
;Asigned Developers<br />
: Scott<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Notes<br />
: 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.<br />
: 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.<br />
<br />
;Status<br />
: Base files applied<br />
: resolving minor adjustments on each of the "mode" displays<br />
: committed ARC/ROSE NAV, VOR, LS modes, supports WPT, ARPT, NDB, VORD EFIS switches<br />
<br />
==Low Priority / Unstarted==<br />
<br />
===Rembrandt Lighting===<br />
<br />
===A319neo and A321neo interior===<br />
<br />
;Please edit if anyone wants to take up any unstarted sections.<br />
<br />
=Proposals=<br />
==Directory structure==<br />
<br />
A320neo<br />
└── Systems<br />
├── electric<br />
│ ├── left_bus.nas<br />
│ └── right_bus.nas<br />
├── fbw<br />
│ ├── Airbus-fbw.nas<br />
│ └── Airbus-fbw.xml<br />
└── hydraulic<br />
├── blue.nas<br />
├── green.nas<br />
├── hydraulics.xml<br />
└── yellow.nas<br />
<br />
==Alternate Nasal Only Structure==<br />
<br />
A320neo<br />
└── Nasal<br />
├── electrical<br />
│ └── electrical.nas<br />
├── pneumatic<br />
│ └── pneumatic.nas<br />
├── hydraulic<br />
│ └── hydraulic.nas<br />
└── mCDU<br />
├── main_loop.nas<br />
├── functions.nas<br />
└── navdata.nas</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A320neo/Development&diff=49663Airbus A320neo/Development2012-05-07T04:45:27Z<p>Scotth1: /* Navigation Display */</p>
<hr />
<div>=ToDo List=<br />
==Electrical==<br />
;Files<br />
: /Nasal/electrical.nas - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Nasal/electrical.nas]<br />
<br />
;Notes<br />
: Aircraft already uses '''Syd Adam's''' ''Jet Electrical'' system.<br />
<br />
;To Do<br />
: Move Nasal file to a dedicated directory in the ''Systems'' folder?<br />
<br />
==Hydraulic==<br />
;Asigned Developers<br />
: Narendran<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Files<br />
: All Hydraulic files in ''/Systems/Hydraulics'' Directory<br />
<br />
;Notes<br />
: Will start work on the hydraulic system as soon as the cockpit is ready<br />
<br />
==Instruments==<br />
<br />
;Assigned Developers<br />
: Jon<br />
: Narendran<br />
<br />
;Branch Name<br />
: develop<br />
<br />
;Notes<br />
: PFD - Rebuild 3D Instrument, use better textures and markers - COMPLETE<br />
: Upper ECAM (EICAS) - Rebuild 2D Instrument with latest A320 ECAM Layout (3 section)<br />
<br />
==Pneumatics==<br />
;Asigned Developers<br />
: Narendran<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Notes<br />
: Include basic pneumatic air pressure system, also include system cooling functions.<br />
<br />
<br />
==Fly by Wire==<br />
;Asigned Developers<br />
: Narendran<br />
: Jon Ortuondo (Bicyus)<br />
: Polly<br />
<br />
;Branch name<br />
: fbw-devel<br />
<br />
;Notes<br />
: 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.<br />
<br />
;Files<br />
: Systems/Airbus-fbw/'''Airbus-fbw.nas''' - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.nas]<br />
: Systems/Airbus-fbw/'''Airbus-fbw.xml''' - [https://gitorious.org/airbus-aircraft/a320neo/blobs/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.xml]<br />
<br />
;To Do<br />
: Move fbw.nas and a320-fbw.xml to common Systems directory. - ''DONE''<br />
: Update FDM from Airbus-fbw branch<br />
: Further tune PIDs (Polly/Jon?)<br />
: Implement mechanical backup law (requires better systems)<br />
: Study and Implement Flare Mode for NORMAL LAW<br />
<br />
==FMGC, FCU and mCDU==<br />
;Asigned Developer(s)<br />
: Narendran<br />
<br />
;Branch name<br />
: flight<br />
<br />
;Notes<br />
: Using data from smart cockpit and equicom. [http://www.smartcockpit.com/plane/airbus/A320/]<br />
: Making a whole new Autopilot/Route Manager system. < Most of this is complete, but the PIDs need to be played with. (Polly)<br />
: FCU is basically just the old 'Mode Control Panel' but that too requires some extra scripting.<br />
<br />
;Resources<br />
: Equicom mCDU Emulator [http://www.equicom.net/mcdu/]<br />
: SmartCockpit FMGS Doc [http://www.smartcockpit.com/pdf/plane/airbus/A320/misc/0011/]<br />
: SmartCockpit Systems Briefing [http://www.smartcockpit.com/pdf/plane/airbus/A320/misc/0002/]<br />
: SmartCockpit Autoflight Systems [http://www.smartcockpit.com/pdf/plane/airbus/A320/systems/0025/]<br />
<br />
;Completed Sections<br />
:FMGC (AP1, AP2, NAV, A-THR)<br />
:FCU (aka. MCP)<br />
:FMGC (WP Transition Manager)<br />
:mCDU > DATA<br />
:mCDU > F-PLN<br />
:mCDU > LAT REV A<br />
:mCDU > VER REV (SIMPLE)<br />
:mCDU > INIT A<br />
:mCDU > FLT SRC<br />
:mCDU > INIT B (FUEL PRED)<br />
:mCDU > RAD NAV<br />
<br />
;Sections in Progress<br />
:mCDU > LAT REV B (TP)<br />
: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.<br />
:mCDU > PERF<br />
<br />
;Remaining Sections<br />
:mCDU > DIR<br />
:mCDU > PROG<br />
:mCDU > MCDU MENU<br />
:mCDU > WP SRC<br />
:mCDU > NAVAID SRC<br />
:mCDU > RWY SRC<br />
:mCDU > SEC F-PLN<br />
:mCDU > AIRPORT<br />
:mCDU > ATC COMM<br />
<br />
==ECAM procedures and Alarms systems==<br />
;Asigned Developers<br />
: Jon<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Notes<br />
: ''Functionalize'' ALL ECAM Pages :P<br />
<br />
==New Cocpit Model & xml==<br />
;Asigned Developers<br />
: Narendran<br />
: Jon A. Ortuondo (bicyus) - xml<br />
<br />
;Project > Repository > Branch<br />
: FlightGear Airbus Development > airbus-a320neo-devel ([https://gitorious.org/flightgear-airbus-development/airbus-a320neo-devel]) > ''flightdeck''<br />
<br />
;Files<br />
: All Flightdeck models are in root<br />
<br />
;Notes<br />
: Basic shell, panel, glaresheild, sidesticks, seats and pedestal models complete. These have also been textured.<br />
: Overhead panel will be derived from the old one but model will be improved<br />
: Cockpit has been ported into FlightGear<br />
<br />
;To Do<br />
: Animations and re-positioning of instruments - STARTED<br />
: Re-make PFD and EICAS? (current versions are not too realistic)<br />
<br />
==Navigation Display==<br />
;Asigned Developers<br />
: Scott<br />
<br />
;Branch name<br />
: develop<br />
<br />
;Notes<br />
: 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.<br />
: 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.<br />
<br />
;Status<br />
: Base files applied<br />
: resolving minor adjustments on each of the "mode" displays<br />
<br />
==Low Priority / Unstarted==<br />
<br />
===Rembrandt Lighting===<br />
<br />
===A319neo and A321neo interior===<br />
<br />
;Please edit if anyone wants to take up any unstarted sections.<br />
<br />
=Proposals=<br />
==Directory structure==<br />
<br />
A320neo<br />
└── Systems<br />
├── electric<br />
│ ├── left_bus.nas<br />
│ └── right_bus.nas<br />
├── fbw<br />
│ ├── Airbus-fbw.nas<br />
│ └── Airbus-fbw.xml<br />
└── hydraulic<br />
├── blue.nas<br />
├── green.nas<br />
├── hydraulics.xml<br />
└── yellow.nas<br />
<br />
==Alternate Nasal Only Structure==<br />
<br />
A320neo<br />
└── Nasal<br />
├── electrical<br />
│ └── electrical.nas<br />
├── pneumatic<br />
│ └── pneumatic.nas<br />
├── hydraulic<br />
│ └── hydraulic.nas<br />
└── mCDU<br />
├── main_loop.nas<br />
├── functions.nas<br />
└── navdata.nas</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Talk:A_standard_CDU_framework_for_FlightGear&diff=40080Talk:A standard CDU framework for FlightGear2012-02-04T14:11:39Z<p>Scotth1: /* Performance considerations */</p>
<hr />
<div>Can we have the standard CDU framework discussion here?<br />
<br />
Anyway, about the layers, I was thinking - display animations (OSGText), 3D model, central functioning - MENU, FUNCTIONS/PAGES). About the menu and function/pages, we could use a common menu and have the best/most functional functions/pages from each of the CDUs combined.<br />
<br />
- Omega<br />
<br />
== Scratching my head about what "my" CDU actually did do... ==<br />
<br />
Well, hello (again, I should say)<br />
<br />
Some initial information: I am not longer "working" with FlightGear. My project has moved on and "we" don't need a FlightGear CDU anymore, hence I won't be able to spend "work time" on it...<br />
<br />
That aside, here are some things I think to remember from "my" CDU:<br />
<br />
* It isn't "mine". I started of on Gjis CDU, took his 3D graphics and started to work my way in from his initial XML based approach so all the kudos to him as I learned from his. That said, I am going to drop the "" and call my CDU the one you can get from gitorious https://gitorious.org/~hcc23.<br />
* Beware of NASAL and performance: I encourage you to checkout my CDU and run it (if it still is compatible)... The frame rate really really drops :( I remember having some IRC discussions about that and think to remember the problem being the NASAL garbage collector...<br />
* I tried to generate a rather reusable piece of software. <br />
** The 3D model is seprate<br />
** The key binding is separate<br />
** The [[Nasal_CDU_Framework| backend]] to generate (Honywell-)CDU style pages is independent from the code that defines the content of those pages<br />
** There is some [[Howto:_Coding_a_Boeing_CDU#The_Code_Framework | documentation]] on how to actually generate content for the pages.<br />
<br />
Overall I think having a [[CDU]] would make FlightGear an even better/cooler sim. Chopping the problem up also seems to be a great idea.<br />
<br />
Unfortunately I won't have the same availability as when I coded the stuff that now sits in my gitorious account and most likely I won't be able to fully understand my code either. And to make matters worse, I most likely won't check this page very often (although I will keep trying to keep up at least a couple of days/weeks...) So send me a private message via the forum as that reaches me and I can then respond. (Or google any of my email addresses and ping me directly...)<br />
<br />
Thanks for making FlightGear the really cool sim it is :)<br />
<br />
[[User:Hcc23|Hcc23]] 18:05, 2 February 2012 (EST)<br />
<br />
== XML ==<br />
Looking at the suggested XML markup, I'd really suggest to stick to the PropertyList format instead, despite its verbosity, there are so many advantages for XML files encoded in the PropertyList format.--[[User:Hooray|Hooray]] 08:26, 3 February 2012 (EST)<br />
<br />
== Embedded Nasal code ==<br />
The proposal says "Pages can retrieve property values #{property-tree} and call nasal functions ${NasalRef.nasalClass.function()}". The question is if, and how, that would ideally work for functions passing parameters between XML<->Nasal? The example is just using an empty argument list. Is this only going to be dealt with using "global" properties instead of Nasal arguments?--[[User:Hooray|Hooray]] 03:09, 4 February 2012 (EST)<br />
<br />
== Embedding Nasal code ==<br />
Looking at the suggested markup, it would definitely be possible to implement this without any changes to the C++ source code, i.e. by using Nasal itself: Nasal does have support for parsing XML (also non-PropertyList XML) and there are a bunch of helpers provided in $FG_ROOT/Nasal/io.nas. So it would in fact be possible to come up with our own XML schema, parse it in Nasal space and even support embedded Nasal. Nasal can dynamically compile(), bind() and call() code. If that's really the way we want to proceed, there's no need for C++ work.--[[User:Hooray|Hooray]] 03:17, 4 February 2012 (EST)<br />
<br />
== Supporting CSS-type styles in XML ==<br />
Looking at the markup, that should also be possible to support from Nasal without C++ changes. One would need to introduce a Nasal wrapper that dynamically maps the "CSS" markup to OSGText animations.--[[User:Hooray|Hooray]] 03:21, 4 February 2012 (EST)<br />
<br />
== Performance considerations ==<br />
Hcc23 pointed out that his CDU implementation affected frame rate negatively, presumably due to some garbage collection related Nasal issues. While there are some GC related issues in the Nasal engine, I don't think that's necessarily the case here: I didn't do any debugging or profiling yet, but looking at the code in question, there isn't necessarily very much allocation and deallocation taking place (besides string concatenation), especially when compared to other complex Nasal systems such as the bombable addon or the local weather system. However, due to the lack of a 2D drawing API, we are working around some serious FG limitations and abusing the XML instruments system quite heavily meanwhile. For example, looking at Omega95's VSD instrument, there are some things pretty obvious: this is less than 10 kbytes of fairly simple Nasal code, compared to > '''150 kbytes of XML animation code'''. The XML-configurable instrumentation system was probably never intended for such uses. 150 kbytes of XML animation code quite certainly means that there's a fair amount of processing involved, including some serious property tree I/O, too. So, I wouldn't be too quick pointing at the Nasal GC here. Invocation of the GC can be somewhat reduced by caching and reusing variables, i.e. by not always allocating new variables during each loop iteration, but rather reusing previously allocated variables, such as by using Nasal hashes ("objects") for this. So, before Nasal is completely disregarded here, it might be worth doing some profiling (SGTimeStamp) to see how much time is actually spent processing all those XML animations (in complex instruments). --[[User:Hooray|Hooray]] 04:02, 4 February 2012 (EST)<br />
<br />
:In my mind the lack of a 2D drawing API and heavy use of XML animation code is also relevant when trying to implement "non-standard" HUDs, which easily could be considered displays as well. [[User:Johan G|Johan G]] 07:30, 4 February 2012 (EST)<br />
<br />
:: Do we currently have any HUDs that are truly complex? I was really just referring to the performance considerations mentioned earlier, because I am not convinced that all lag can be attributed to Nasal and its GC. Obviously, getting a 2D drawing API would be great at some point, for a number of reasons - but that's a long standing feature request, and core devs know and agree on that: [[FlightGear Glass Cockpits]] (5 years old now). In the meantime, it would be important to check where exactly the lag is created in the first place.--[[User:Hooray|Hooray]] 08:41, 4 February 2012 (EST)<br />
<br />
:: Access to a 2D drawing API is becoming essential to where my thinking is evolving, as can be seen in my rantings on the page. As for Nasal performance hits, I agree that it may not necessarily be the performance hog some make it out to be. I have written a lot of Nasal code the A380 and I believe I get frame rates that are better than some other aircraft with less Nasal. I think anyone who spends enough time in Nasal has a good idea of how to work within the performance bounds of how it is called. --[[User:Scotth1|Scotth1]] 09:11, 4 February 2012 (EST)</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40068A standard CDU framework for FlightGear2012-02-04T06:32:43Z<p>Scotth1: </p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures. This is completely a wishlist on my behalf and very very draft.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
The Markup (XML based) for the page definition should encapsulate both the layout of page components, and the flow of actions.<br />
Pages can retrieve property values #{property-tree} and call nasal functions ${NasalRef.nasalClass.function()}<br />
<br />
<syntaxhighlight lang="xml"><br />
<?xml version="1.0"?><br />
<page><br />
<title>Page Title</title><br />
<body><br />
<group><br />
<group style="valign:left; width:50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: red">Literal Text</text><br />
</row><br />
<row><br />
<text style="size: 12pt; colour: green">#{/instrumentation/flightdirector/myproperty}</text><br />
<text style="size: 12pt; colour: red">${NasalRef.nasalClass.function()</text><br />
</row><br />
</group><br />
<group style="valign: right; width: 50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: #1169C0">Destination:</text><br />
<input value="${/instrumentation/flightdirector/dest-airport}" style="colour: green; width: 150px"/><br />
</row><br />
</group><br />
<group style="halign: bottom"><br />
<row><br />
<button style="valign: left; background-colour: #E0E0E0" action="NasalModule.nasalObject.function()">Lookup</button><br />
<button style="valign: right; background-texture: Aircraft/MyAircraft/Tetxtures/button-texture.png" action="page2">Next Page</button><br />
<row><br />
</group><br />
</group><br />
</body><br />
</page><br />
</syntaxhighlight><br />
<br />
Wishlist of elements;<br />
# title<br />
# body - all child elements are drawable<br />
# group - groups children elements as on layout object<br />
# row - provides a relative row layout object<br />
# text - draws some literal text or text from an expression<br />
# input - draws a clickable hotspot that can receive virtual keyboard input and sets property with value<br />
# button - draws a button object that is also a hotspot, calls nasal function on click<br />
# canvas - create a texture object that we can use OpenGL statements to draw on (pass-through)<br />
# mesh - create a 3D mesh object<br />
<br />
== Components ==<br />
<br />
==== MainLoop ====<br />
<br />
pseudo code<br />
<br />
'''init:'''<br />
<br />
KeypadManager keypad = KeypadManager.getQwertyKeypadManager("keyboard-left");<br />
KeypadManager keypad2 = KeypadManager.getThalesCDUKeypad("keypad-right");<br />
me.registerKeypadManager(keypad);<br />
me.registerKeypadManager(keypad2);<br />
Screen cduScreen = ObjectModel.getObjectById("cdu-left");<br />
PageRenderer pgRender = new PageRenderer(cduScreen);<br />
PageLayoutEngine layout = new FreeformLCDLayout(640, 420);<br />
PageLayoutEngine layout2 = new GridLEDLayout(40, 6);<br />
pgRender.setLayoutEngine(layout2);<br />
pgRender.loadPage("ident.xml");<br />
<br />
<br />
'''loadPage(page):'''<br />
<br />
Page pg= PageParser.parse(page);<br />
me.calculateBoxLayout(pg);<br />
me.draw();<br />
<br />
<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40067A standard CDU framework for FlightGear2012-02-04T06:32:08Z<p>Scotth1: </p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures. This is completely a wishlist on my behalf and very very draft.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
The Markup (XML based) for the page definition should encapsulate both the layout of page components, and the flow of actions.<br />
Pages can retrieve property values #{property-tree} and call nasal functions ${NasalRef.nasalClass.function()}<br />
<br />
<syntaxhighlight lang="xml"><br />
<?xml version="1.0"?><br />
<page><br />
<title>Page Title</title><br />
<body><br />
<group><br />
<group style="valign:left; width:50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: red">Literal Text</text><br />
</row><br />
<row><br />
<text style="size: 12pt; colour: green">#{/instrumentation/flightdirector/myproperty}</text><br />
<text style="size: 12pt; colour: red">${NasalRef.nasalClass.function()</text><br />
</row><br />
</group><br />
<group style="valign: right; width: 50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: #1169C0">Destination:</text><br />
<input value="${/instrumentation/flightdirector/dest-airport}" style="colour: green; width: 150px"/><br />
</row><br />
</group><br />
<group style="halign: bottom"><br />
<row><br />
<button style="valign: left; background-colour: #E0E0E0" action="NasalModule.nasalObject.function()">Lookup</button><br />
<button style="valign: right; background-texture: Aircraft/MyAircraft/Tetxtures/button-texture.png" action="page2">Next Page</button><br />
<row><br />
</group><br />
</group><br />
</body><br />
</page><br />
</syntaxhighlight><br />
<br />
Wishlist of elements;<br />
# title<br />
# body - all child elements are drawable<br />
# group - groups children elements as on layout object<br />
# row - provides a relative row layout object<br />
# text - draws some literal text or text from an expression<br />
# input - draws a clickable hotspot that can receive virtual keyboard input and sets property with value<br />
# button - draws a button object that is also a hotspot, calls nasal function on click<br />
# canvas - create a texture object that we can use OpenGL statements to draw on (pass-through)<br />
# mesh - create a 3D mesh object<br />
<br />
== Components ==<br />
<br />
==== MainLoop ====<br />
<br />
pseudo code<br />
<br />
*init:*<br />
<br />
KeypadManager keypad = KeypadManager.getQwertyKeypadManager("keyboard-left");<br />
KeypadManager keypad2 = KeypadManager.getThalesCDUKeypad("keypad-right");<br />
me.registerKeypadManager(keypad);<br />
me.registerKeypadManager(keypad2);<br />
Screen cduScreen = ObjectModel.getObjectById("cdu-left");<br />
PageRenderer pgRender = new PageRenderer(cduScreen);<br />
PageLayoutEngine layout = new FreeformLCDLayout(640, 420);<br />
PageLayoutEngine layout2 = new GridLEDLayout(40, 6);<br />
pgRender.setLayoutEngine(layout2);<br />
pgRender.loadPage("ident.xml");<br />
<br />
<br />
*loadPage(page):*<br />
<br />
Page pg= PageParser.parse(page);<br />
me.calculateBoxLayout(pg);<br />
me.draw();<br />
<br />
<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40066A standard CDU framework for FlightGear2012-02-04T06:31:14Z<p>Scotth1: /* MainLoop */</p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures. This is completely a wishlist on my behalf and very very draft.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
The Markup (XML based) for the page definition should encapsulate both the layout of page components, and the flow of actions.<br />
Pages can retrieve property values #{property-tree} and call nasal functions ${NasalRef.nasalClass.function()}<br />
<br />
<syntaxhighlight lang="xml"><br />
<?xml version="1.0"?><br />
<page><br />
<title>Page Title</title><br />
<body><br />
<group><br />
<group style="valign:left; width:50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: red">Literal Text</text><br />
</row><br />
<row><br />
<text style="size: 12pt; colour: green">#{/instrumentation/flightdirector/myproperty}</text><br />
<text style="size: 12pt; colour: red">${NasalRef.nasalClass.function()</text><br />
</row><br />
</group><br />
<group style="valign: right; width: 50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: #1169C0">Destination:</text><br />
<input value="${/instrumentation/flightdirector/dest-airport}" style="colour: green; width: 150px"/><br />
</row><br />
</group><br />
<group style="halign: bottom"><br />
<row><br />
<button style="valign: left; background-colour: #E0E0E0" action="NasalModule.nasalObject.function()">Lookup</button><br />
<button style="valign: right; background-texture: Aircraft/MyAircraft/Tetxtures/button-texture.png" action="page2">Next Page</button><br />
<row><br />
</group><br />
</group><br />
</body><br />
</page><br />
</syntaxhighlight><br />
<br />
Wishlist of elements;<br />
# title<br />
# body - all child elements are drawable<br />
# group - groups children elements as on layout object<br />
# row - provides a relative row layout object<br />
# text - draws some literal text or text from an expression<br />
# input - draws a clickable hotspot that can receive virtual keyboard input and sets property with value<br />
# button - draws a button object that is also a hotspot, calls nasal function on click<br />
# canvas - create a texture object that we can use OpenGL statements to draw on (pass-through)<br />
# mesh - create a 3D mesh object<br />
<br />
== Components ==<br />
<br />
==== MainLoop ====<br />
<br />
pseudo code<br />
<br />
*init:*<br />
<syntaxhighlighting><br />
KeypadManager keypad = KeypadManager.getQwertyKeypadManager("keyboard-left");<br />
KeypadManager keypad2 = KeypadManager.getThalesCDUKeypad("keypad-right");<br />
me.registerKeypadManager(keypad);<br />
me.registerKeypadManager(keypad2);<br />
Screen cduScreen = ObjectModel.getObjectById("cdu-left");<br />
PageRenderer pgRender = new PageRenderer(cduScreen);<br />
PageLayoutEngine layout = new FreeformLCDLayout(640, 420);<br />
PageLayoutEngine layout2 = new GridLEDLayout(40, 6);<br />
pgRender.setLayoutEngine(layout2);<br />
pgRender.loadPage("ident.xml");<br />
</syntaxhighlighting><br />
<br />
*loadPage(page):*<br />
<syntaxhighlighting><br />
Page pg= PageParser.parse(page);<br />
me.calculateBoxLayout(pg);<br />
me.draw();<br />
</syntaxhighlighting><br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40065A standard CDU framework for FlightGear2012-02-04T06:30:02Z<p>Scotth1: </p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures. This is completely a wishlist on my behalf and very very draft.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
The Markup (XML based) for the page definition should encapsulate both the layout of page components, and the flow of actions.<br />
Pages can retrieve property values #{property-tree} and call nasal functions ${NasalRef.nasalClass.function()}<br />
<br />
<syntaxhighlight lang="xml"><br />
<?xml version="1.0"?><br />
<page><br />
<title>Page Title</title><br />
<body><br />
<group><br />
<group style="valign:left; width:50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: red">Literal Text</text><br />
</row><br />
<row><br />
<text style="size: 12pt; colour: green">#{/instrumentation/flightdirector/myproperty}</text><br />
<text style="size: 12pt; colour: red">${NasalRef.nasalClass.function()</text><br />
</row><br />
</group><br />
<group style="valign: right; width: 50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: #1169C0">Destination:</text><br />
<input value="${/instrumentation/flightdirector/dest-airport}" style="colour: green; width: 150px"/><br />
</row><br />
</group><br />
<group style="halign: bottom"><br />
<row><br />
<button style="valign: left; background-colour: #E0E0E0" action="NasalModule.nasalObject.function()">Lookup</button><br />
<button style="valign: right; background-texture: Aircraft/MyAircraft/Tetxtures/button-texture.png" action="page2">Next Page</button><br />
<row><br />
</group><br />
</group><br />
</body><br />
</page><br />
</syntaxhighlight><br />
<br />
Wishlist of elements;<br />
# title<br />
# body - all child elements are drawable<br />
# group - groups children elements as on layout object<br />
# row - provides a relative row layout object<br />
# text - draws some literal text or text from an expression<br />
# input - draws a clickable hotspot that can receive virtual keyboard input and sets property with value<br />
# button - draws a button object that is also a hotspot, calls nasal function on click<br />
# canvas - create a texture object that we can use OpenGL statements to draw on (pass-through)<br />
# mesh - create a 3D mesh object<br />
<br />
== Components ==<br />
<br />
==== MainLoop ====<br />
<br />
pseudo code<br />
<br />
init:<br />
KeypadManager keypad = KeypadManager.getQwertyKeypadManager("keyboard-left");<br />
KeypadManager keypad2 = KeypadManager.getThalesCDUKeypad("keypad-right");<br />
me.registerKeypadManager(keypad);<br />
me.registerKeypadManager(keypad2);<br />
Screen cduScreen = ObjectModel.getObjectById("cdu-left");<br />
PageRenderer pgRender = new PageRenderer(cduScreen);<br />
PageLayoutEngine layout = new FreeformLCDLayout(640, 420);<br />
PageLayoutEngine layout2 = new GridLEDLayout(40, 6);<br />
pgRender.setLayoutEngine(layout2);<br />
pgRender.loadPage("ident.xml");<br />
<br />
loadPage(page):<br />
Page pg= PageParser.parse(page);<br />
me.calculateBoxLayout(pg);<br />
me.draw();<br />
<br />
<br />
<br />
<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40063A standard CDU framework for FlightGear2012-02-04T01:26:40Z<p>Scotth1: /* Page Definition Markup */</p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures. This is completely a wishlist on my behalf and very very draft.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
The Markup (XML based) for the page definition should encapsulate both the layout of page components, and the flow of actions.<br />
Pages can retrieve property values #{property-tree} and call nasal functions ${NasalRef.nasalClass.function()}<br />
<br />
<syntaxhighlight lang="xml"><br />
<?xml version="1.0"?><br />
<page><br />
<title>Page Title</title><br />
<body><br />
<group><br />
<group style="valign:left; width:50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: red">Literal Text</text><br />
</row><br />
<row><br />
<text style="size: 12pt; colour: green">#{/instrumentation/flightdirector/myproperty}</text><br />
<text style="size: 12pt; colour: red">${NasalRef.nasalClass.function()</text><br />
</row><br />
</group><br />
<group style="valign: right; width: 50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: #1169C0">Destination:</text><br />
<input value="${/instrumentation/flightdirector/dest-airport}" style="colour: green; width: 150px"/><br />
</row><br />
</group><br />
<group style="halign: bottom"><br />
<row><br />
<button style="valign: left; background-colour: #E0E0E0" action="NasalModule.nasalObject.function()">Lookup</button><br />
<button style="valign: right; background-texture: Aircraft/MyAircraft/Tetxtures/button-texture.png" action="page2">Next Page</button><br />
<row><br />
</group><br />
</group><br />
</body><br />
</page><br />
</syntaxhighlight><br />
<br />
Wishlist of elements;<br />
# title<br />
# body - all child elements are drawable<br />
# group - groups children elements as on layout object<br />
# row - provides a relative row layout object<br />
# text - draws some literal text or text from an expression<br />
# input - draws a clickable hotspot that can receive virtual keyboard input and sets property with value<br />
# button - draws a button object that is also a hotspot, calls nasal function on click<br />
# canvas - create a texture object that we can use OpenGL statements to draw on (pass-through)<br />
# mesh - create a 3D mesh object at offset position<br />
<br />
== Components ==<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40017A standard CDU framework for FlightGear2012-02-03T12:57:46Z<p>Scotth1: </p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures. This is completely a wishlist on my behalf and very very draft.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
The Markup (XML based) for the page definition should encapsulate both the layout of page components, and the flow of actions.<br />
Pages can retrieve property values and call nasal functions.<br />
<br />
<?xml version="1.0"?><br />
<page><br />
<title>Page Title</title><br />
<body><br />
<group><br />
<group style="valign:left; width:50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: red">Literal Text</text><br />
</row><br />
<row><br />
<text style="size: 12pt; colour: green">${/instrumentation/flightdirector/myproperty}</text><br />
<text style="size: 12pt; colour: red">#{NasalModule.nasalObject.function()</text><br />
</row><br />
</group><br />
<group style="valign: right; width: 50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: #1169C0">Destination:</text><br />
<input value="${/instrumentation/flightdirector/dest-airport}" style="colour: green; width: 150px"/><br />
</row><br />
</group><br />
<group style="halign: bottom"><br />
<row><br />
<button style="valign: left; background-colour: #E0E0E0" action="NasalModule.nasalObject.function()">Lookup</button><br />
<button style="valign: right; background-texture: Aircraft/MyAircraft/Tetxtures/button-texture.png" action="page2">Next Page</button><br />
<row><br />
</group><br />
</group><br />
</body><br />
</page><br />
<br />
<br />
== Components ==<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40016A standard CDU framework for FlightGear2012-02-03T12:55:43Z<p>Scotth1: /* Architecture */</p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures. This is completely a wishlist on my behalf and very very draft.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
The Markup (XML based) for the page definition should encapsulate both the layout of page components, and the flow of actions.<br />
Pages can retrieve property values and call nasal functions.<br />
<br />
<?xml version="1.0"?><br />
<page><br />
<title>Page Title</title><br />
<body><br />
<group><br />
<group style="valign:left; width:50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: red">Literal Text</text><br />
</row><br />
<row><br />
<text style="size: 12pt; colour: green">${/instrumentation/flightdirector/myproperty}</text><br />
<text style="size: 12pt; colour: red">#{NasalModule.nasalObject.function()</text><br />
</row><br />
</group><br />
<group style="valign: right; width: 50%"><br />
<row><br />
<text style="valign: left; size: 12pt; colour: #1169C0">Destination:</text><br />
<input value="${/instrumentation/flightdirector/dest-airport}" style="colour: green; width: 150px"/><br />
</row><br />
</group><br />
<group style="halign: bottom"><br />
<row><br />
<button style="valign: left; background-colour: #E0E0E0" action="NasalModule.nasalObject.function()">Lookup</button><br />
<button style="valign: right; background-texture: Aircraft/MyAircraft/Tetxtures/button-texture.png" action="page2">Next Page</button><br />
<row><br />
</group><br />
</group><br />
</body><br />
</page><br />
<br />
== Components ==<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40015A standard CDU framework for FlightGear2012-02-03T12:15:45Z<p>Scotth1: /* Architecture */</p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
== Page Definition Markup ==<br />
<br />
== Components ==<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=File:FGMCDUOverview.png&diff=40014File:FGMCDUOverview.png2012-02-03T12:14:31Z<p>Scotth1: </p>
<hr />
<div></div>Scotth1https://wiki.flightgear.org/w/index.php?title=A_standard_CDU_framework_for_FlightGear&diff=40013A standard CDU framework for FlightGear2012-02-03T12:13:51Z<p>Scotth1: </p>
<hr />
<div>{{Stub}}<br />
* Last updated: 01/2012<br />
* Contributors: <br />
<br />
<br />
= Introduction =<br />
<br />
As of 01/2012, we are unfortunately approaching a situation where we are having too many different CDU implementations with little (or none) reuse and sharing of existing code - at the moment, there are least 4-5 different projects:<br />
<br />
* Hcc23's CDU: http://wiki.flightgear.org/Howto:_Development_of_the_CDU<br />
* Gijs' CDU: http://wiki.flightgear.org/Howto:_Coding_a_Boeing_CDU<br />
* Scotth1's CDU: http://gitorious.org/airbus-aircraft/a380<br />
* Skyop's CDU: http://flightgear.org/forums/viewtopic.php?f=4&t=11863&hilit=skyop+crj&start=195#p135105<br />
* Omega95's CDU: http://flightgear.org/forums/viewtopic.php?f=18&t=15082<br />
<br />
<br />
All of them implemented in [[Nasal]]. Now, what we really need is someone to examine all versions and see if/how they could be combined, unified and eventually integrated, so that we end up with a single version that is well understood, can be well documented and well-maintained, usable by all aircraft developers, catering for all different needs.<br />
<br />
There's a fair share of common features required for pretty much any CDU/MCDU, especially these SHARED low level requirements are largely identical among these FMS front ends.<br />
<br />
For example, this includes instantiating an addressable "screen region" and providing hooks to write alphanumeric text to it, as well as dealing with events, i.e. for key handling.<br />
<br />
So, ideally, we could come up with a layered design where generic CDU components could be identified to allow people instantiating and parametrizing CDU-related components.<br />
Nasal's OOP support is powerful enough to allow people to override such features easily.<br />
<br />
Aircraft specific differences are best addressed by parametrization during CDU-instantiation, rather than by duplicating redundant code.<br />
<br />
<br />
In real-life, there are only like 3 different FMS/FMC/CDU implementations for airliners:<br />
<br />
* Thales<br />
* Honeywell<br />
* Smiths Industries (now GE Aviation)<br />
<br />
And the same units from one manufacturer are often used in different aircraft (eg: A320, MD-11, 757 and 767 all use the same Honeywell FMS). The majority of the database format is covered by an [[ARINC]] standard.<br />
<br />
For smaller aircraft (like biz-jets, turboprops and military trainers) one also has to consider other manufacturers like:<br />
<br />
* Barco<br />
* Esterline<br />
* Universal Avionics Systems<br />
<br />
<br />
It is OK to have different initial implementations, all the versions we have at the moment have different ways of implementing different functionality. We could say this is exploring the problem-space.<br />
<br />
But we are getting closer to building up a set of requirements that could be built into a common set of instruments and functions...<br />
<br />
We are thinking of one "framework" of sorts for connecting a 3D model of the CDU to the property tree, and another framework for it's internal software, both with provisions for customising.<br />
<br />
There are two distinct streams:<br />
<br />
* the first is the physical representation of a keypad, screen etc, this is either the traditional LED grid screen, some specialised function keys and general letter/number keypad, the second type of physical representation is the newer LCD monitor type, such as used on 787 and A380 and a few others. This includes page flow, text management and key management.<br />
<br />
* The second stream is the back-end processes of the FMS, calculating flight plans, lateral/vertical guidance and interfacing with the route manager and autopilot.<br />
<br />
Well, even if you were to find 100 different manufacturers of CDUs, FMCs and FMS there'd still be a great deal of shared functionality and shared requirements, i.e. things that would be identical among ALL implementations, such as addressing a 2D screen region, rendering formatted text at certain coordinates, responding to key events, querying a navigational datatbase, making certain geospatial calculations.<br />
<br />
So, yes, the idea is to come up with a list of these shared requirements and find the greatest common denominator for each component so that a set of layered frameworks can be created, to enable users to reuse code as much as possible, while still being able to customize and parametrize functionality as required.<br />
<br />
Some things are currently not yet possible/feasible to do from scripting space (i.e. they require new scripting hooks) , but there are many things that are quite possible already and which should eventually be standardized, i.e. by coming up with a dedicated Nasal module that handles all details and which can be reused by aircraft developers easily.<br />
<br />
We need to come up with our own module by getting all people to communicate their requirements, so that the existing designs can be reviewed and improved eventually.<br />
This is more complex work than coming up with some workaround from scratch, but it's more worthwhile in the long run.<br />
<br />
In many aspects, FlightGear follows implicitly the MVC pattern already - simply because of the property tree, which already causes a separation of concerns to a certain degree.<br />
<br />
= Architecture =<br />
Provided below are some design option architectures.<br />
[[File:FGMCDUOverview.png]]<br />
<br />
<br />
<br />
<br />
= References =<br />
* http://flightgear.org/forums/viewtopic.php?f=4&t=15082&p=148624&hilit=autopilot#p148624<br />
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32302.html<br />
<br />
[[Category:Nasal]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=39431A380 Tutorial2012-01-18T13:17:24Z<p>Scotth1: /* Landing */</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle so N1 (the second line from the top) is around 50%<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a de-rated takeoff, advance the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line FMA of the Primary Flight Display.<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the sidestick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1''' and '''PACK 2''' before 4000ft<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== Climb and Cruise ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== Descent ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track<br />
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.<br />
<br />
''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<br />
''<br />
<br />
''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.''<br />
<br />
== Landing ==<br />
<br />
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.<br />
<br />
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).<br />
<br />
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.<br />
<br />
At around 3000ft the speed should be around 230knots, extend the gears and turn on external lighting for Nose, Landing and Wing lights.<br />
<br />
Set the Selected speed to '''200''' knots<br />
<br />
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.<br />
<br />
When you are within visual of the runway, reduce the selected speed to '''180 knots''', control your speed by extending the flaps to 1</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=33837Airbus A3802011-09-03T13:08:40Z<p>Scotth1: </p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status = Under development<br />
|fgname = A380<br />
|download = http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.0.0/A380_1.0.zip<br />
|development = http://gitorious.org/airbus-aircraft/a380/trees/master<br />
}}<br />
<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest [[:Category:Transport aircraft|freight aircraft]], with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
A [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions<br />
* auto changeover level<br />
* Environment Control System (cabin pressurisation)<br />
* auto-tuned VOR on NAV2<br />
* anti-ice and air packs take bleed air<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localiser and approach<br />
* FlightDirector, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS<br />
* ND nearby airports display switch on EFIS<br />
* ND traffic display switch on EFIS<br />
* airspeed AP control on FCU selectable between knots or mach value<br />
* altitude selectable between 100ft and 1000ft<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* localiser and Glidescope indicators on PFD<br />
* E/WD<br />
* updated Nav Display<br />
** ARC mode<br />
** ROSE mode<br />
** aerodrome moving map with 'ZOOM' scale in PLAN mode<br />
** nearby airports on ND^<br />
** multi-player and AI traffic on ND<br />
** VOR/ADF left-hand and right-hand display<br />
* E/WD checklists<br />
* gear lever and indicators<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel<br />
* air panel<br />
* anti-ice panel<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC<br />
** electrical DC<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance<br />
** Active Flight Plan<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and <del>speed brake</del><br />
* cabin interior<br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* engine start sounds^<br />
* complete PFD and EFIS selection switches<br />
* <del>complete ND EFIS selection switches</del>^<br />
* <del>complete ND display modes</del><br />
** PLAN<br />
** LS^<br />
** VOR^<br />
** <del>MAP</del><br />
* add standard procedure check-lists to EWD<br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
** <del>DOOR</del><br />
** <del>APU</del><br />
** <del>ENGINE</del><br />
** COND<br />
** WHEEL<br />
** PRESSURE<br />
** BLEED<br />
** <del>ELEC AC</del><br />
** <del>ELEC DC</del><br />
** <del>FUEL</del><br />
** HYDRAULIC<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* <del>gear lever and indicators</del><br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; <del>cabin pressure</del> and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* fix up scaling of texture sizes^<br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Aircraft]]<br />
[[Category:Aircraft TODO]]<br />
[[Category:Airliners]]<br />
[[Category:Civilian aircraft]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=33836Airbus A3802011-09-03T13:02:37Z<p>Scotth1: /* To Do */</p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status = Under development<br />
|fgname = A380<br />
|download = http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.0.0/A380_1.0.zip<br />
|development = http://gitorious.org/airbus-aircraft/a380/trees/master<br />
}}<br />
<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest [[:Category:Transport aircraft|freight aircraft]], with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
A [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (now with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions<br />
* auto changeover level<br />
* Environment Control System (cabin pressurisation)<br />
* auto-tuned VOR on NAV2<br />
* anti-ice and air packs take bleed air<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localiser and approach<br />
* FlightDirector, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* airspeed AP control on FCU selectable between knots or mach value<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* localiser and Glidescope indicators on PFD<br />
* E/WD<br />
* updated Nav Display<br />
* E/WD checklists<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel<br />
* air panel<br />
* anti-ice panel<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC<br />
** electrical DC<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance<br />
** Active Flight Plan<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and <del>speed brake</del><br />
* cabin interior<br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* engine start sounds^<br />
* complete PFD and EFIS selection switches<br />
* <del>complete ND EFIS selection switches</del>^<br />
* <del>complete ND display modes</del><br />
** PLAN<br />
** LS^<br />
** VOR^<br />
** <del>MAP</del><br />
* add standard procedure check-lists to EWD<br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
** <del>DOOR</del><br />
** <del>APU</del><br />
** <del>ENGINE</del><br />
** COND<br />
** WHEEL<br />
** PRESSURE<br />
** BLEED<br />
** <del>ELEC AC</del><br />
** <del>ELEC DC</del><br />
** <del>FUEL</del><br />
** HYDRAULIC<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* <del>gear lever and indicators</del><br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; <del>cabin pressure</del> and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* fix up scaling of texture sizes^<br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Aircraft]]<br />
[[Category:Aircraft TODO]]<br />
[[Category:Airliners]]<br />
[[Category:Civilian aircraft]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=32916Airbus A3802011-07-14T13:47:46Z<p>Scotth1: mark off completed tasks in to-do list.</p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status = Under development<br />
|fgname = A380<br />
|download = http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.0.0/A380_1.0.zip<br />
|development = http://gitorious.org/airbus-aircraft/a380/trees/master<br />
}}<br />
<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest [[:Category:Transport aircraft|freight aircraft]], with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
A [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (now with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions<br />
* auto changeover level<br />
* Environment Control System (cabin pressurisation)<br />
* auto-tuned VOR on NAV2<br />
* anti-ice and air packs take bleed air<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localiser and approach<br />
* FlightDirector, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* airspeed AP control on FCU selectable between knots or mach value<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* localiser and Glidescope indicators on PFD<br />
* E/WD<br />
* updated Nav Display<br />
* E/WD checklists<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel<br />
* air panel<br />
* anti-ice panel<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC<br />
** electrical DC<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance<br />
** Active Flight Plan<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and <del>speed brake</del><br />
* cabin interior<br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* engine start sounds<br />
* complete PFD and EFIS selection switches<br />
* complete ND EFIS selection switches<br />
* <del>complete ND display modes</del><br />
** PLAN<br />
** LS<br />
** VOR<br />
** <del>MAP</del><br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
** <del>DOOR</del><br />
** <del>APU</del><br />
** <del>ENGINE</del><br />
** COND<br />
** WHEEL<br />
** PRESSURE<br />
** BLEED<br />
** <del>ELEC AC</del><br />
** <del>ELEC DC</del><br />
** <del>FUEL</del><br />
** HYDRAULIC<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* <del>gear lever and indicators</del><br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; <del>cabin pressure</del> and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* fix up scaling of texture sizes<br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Aircraft]]<br />
[[Category:Aircraft TODO]]<br />
[[Category:Airliners]]<br />
[[Category:Civilian aircraft]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=FlightGear_hangars&diff=32118FlightGear hangars2011-06-06T13:46:34Z<p>Scotth1: /* Hangars */</p>
<hr />
<div>''See [[Links]] for an overall listing of FlightGear related external websites''<br />
<br />
FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version. <br />
<br />
Be careful with external links! <br />
<br />
=== Official hangars ===<br />
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar]<br />
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)<br />
* [http://liveries.flightgear.org FlightGear Liveries]<br />
<br />
=== Hangars ===<br />
* [http://alphashangar.co.nr/ Alpha-J's Hangar] (Aircraft, Liveries, Scenery, AI, etc.)<br />
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] <br />
* <s>[http://bravosflightgear.yolasite.com/ Bravo's FlightGear] (Airbus A318-100) </s><br />
* [http://ltts.crlt.indiana.edu/grn/flightgear/ Buckaroo's Hangar] (Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a yasim intro)<br />
* [http://members.cox.net/davidculp/hangar.html Dave's Hangar] (also [http://daveshangar.blogspot.com/ Dave's Hangar Blog])<br />
* [http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar] (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)<br />
* [http://flier95-flightgear.blogspot.com/ Flier95's Hangar] (Blog format)<br />
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)<br />
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)<br />
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons)<br />
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (156+ original aircraft)<br />
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles) <br />
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)<br />
* [http://icestar-fghangar.web44.net/ Icecode's & Star's Hangar] (under development)<br />
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)<br />
* [http://flightgear.bplaced.de/ longfly's hangar] (not only German!)<br />
** [http://www.flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts] (under development)<br />
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)<br />
* [http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar] (5+ liveries & mods)<br />
* [http://theomegahangar.webs.com Omega Hangar] (Mobile Stairway)<br />
* [http://sites.google.com/site/pjedvajflightgear/ pjedvaj's Hangar] (Sukhoi T-50 PAK-FA,, Mikoyan-Gurevich MiG-21bis, Pilatus PC-21, Pilatus PC-9M) <br />
* [http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar] (a few well made aircraft)<br />
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many non-english aircraft articles)<br />
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)<br />
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)<br />
* [http://skyopshangar.byethost17.com/ Skyop's FlightGear Hangar] (717, 757-200, A300, A320-family, A330-300, A340-300, ATR 72, CRJ900, Paper airplane, & scenery)<br />
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]<br />
* [http://sydhangar.daffodil.uk.com/ Syd's Hangar ] (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)<br />
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)<br />
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)<br />
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]<br />
* [https://www.gitorious.org/airbus-aircraft Airbus Aircraft Development Git] (A320, A330, A340-300, A380 - various authors)<br />
<br />
==== Livery hangars ====<br />
* [http://www.AAliveries.yolasite.com/ Armchair Ace Liveries] (Aircraft Modifications and liveries)<br />
* [http://berwickskins.yolasite.com/ Berwick-skins]<br />
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]<br />
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]<br />
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]<br />
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]<br />
<br />
==== Homepages, blogs, etc. ====<br />
<br />
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]<br />
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)<br />
* [http://www.fguk.eu/ FlightGear United Kingdom] <br />
* [http://www.flightgear-germany.de/ FlightGear Germany] (DE)<br />
* [http://flightgear2009.blogspot.com/ Flight Gear Brasil 2009] (non-english)<br />
* [http://www.shialeweb.com/caballerosaguila/news.php Caballeros Aguila] (non-english)<br />
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]<br />
* [http://tehwarlock.tk/ Tehwarlock Blog]<br />
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)<br />
* [http://www.jaunty.bplaced.net/flightgear/index.php a small FlightGear page]<br />
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)<br />
<br />
=== Other FlightGear repositories/mirrors ===<br />
* [http://www.unitedfreeworld.com/ unitedfreeworld] (scenery, plane models, and livery)<br />
* [http://www.flightgearplanes.com Flightgear Planes Website]<br />
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft] <br />
<br />
=== Old Hangars ===<br />
* [http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]<br />
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002) <br />
<br />
=== Related content ===<br />
* [[Table of models]]<br />
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]<br />
<br />
[[Category:List]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=FlightGear_hangars&diff=32117FlightGear hangars2011-06-06T13:43:29Z<p>Scotth1: /* Hangars */</p>
<hr />
<div>''See [[Links]] for an overall listing of FlightGear related external websites''<br />
<br />
FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version. <br />
<br />
Be careful with external links! <br />
<br />
=== Official hangars ===<br />
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar]<br />
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)<br />
* [http://liveries.flightgear.org FlightGear Liveries]<br />
<br />
=== Hangars ===<br />
* [http://alphashangar.co.nr/ Alpha-J's Hangar] (Aircraft, Liveries, Scenery, AI, etc.)<br />
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] <br />
* <s>[http://bravosflightgear.yolasite.com/ Bravo's FlightGear] (Airbus A318-100) </s><br />
* [http://ltts.crlt.indiana.edu/grn/flightgear/ Buckaroo's Hangar] (Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a yasim intro)<br />
* [http://members.cox.net/davidculp/hangar.html Dave's Hangar] (also [http://daveshangar.blogspot.com/ Dave's Hangar Blog])<br />
* [http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar] (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)<br />
* [http://flier95-flightgear.blogspot.com/ Flier95's Hangar] (Blog format)<br />
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)<br />
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)<br />
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons)<br />
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (156+ original aircraft)<br />
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles) <br />
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)<br />
* [http://icestar-fghangar.web44.net/ Icecode's & Star's Hangar] (under development)<br />
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)<br />
* [http://flightgear.bplaced.de/ longfly's hangar] (not only German!)<br />
** [http://www.flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts] (under development)<br />
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)<br />
* [http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar] (5+ liveries & mods)<br />
* [http://theomegahangar.webs.com Omega Hangar] (Mobile Stairway)<br />
* [http://sites.google.com/site/pjedvajflightgear/ pjedvaj's Hangar] (Sukhoi T-50 PAK-FA,, Mikoyan-Gurevich MiG-21bis, Pilatus PC-21, Pilatus PC-9M) <br />
* [http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar] (a few well made aircraft)<br />
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many non-english aircraft articles)<br />
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)<br />
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)<br />
* [http://skyopshangar.byethost17.com/ Skyop's FlightGear Hangar] (717, 757-200, A300, A320-family, A330-300, A340-300, ATR 72, CRJ900, Paper airplane, & scenery)<br />
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]<br />
* [http://sydhangar.daffodil.uk.com/ Syd's Hangar ] (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)<br />
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)<br />
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)<br />
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]<br />
* [https://www.gitorious.org/airbus-aircraft Airbus Aircraft] (A320, A330, A340-300, A380)<br />
<br />
==== Livery hangars ====<br />
* [http://www.AAliveries.yolasite.com/ Armchair Ace Liveries] (Aircraft Modifications and liveries)<br />
* [http://berwickskins.yolasite.com/ Berwick-skins]<br />
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]<br />
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]<br />
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]<br />
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]<br />
<br />
==== Homepages, blogs, etc. ====<br />
<br />
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]<br />
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)<br />
* [http://www.fguk.eu/ FlightGear United Kingdom] <br />
* [http://www.flightgear-germany.de/ FlightGear Germany] (DE)<br />
* [http://flightgear2009.blogspot.com/ Flight Gear Brasil 2009] (non-english)<br />
* [http://www.shialeweb.com/caballerosaguila/news.php Caballeros Aguila] (non-english)<br />
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]<br />
* [http://tehwarlock.tk/ Tehwarlock Blog]<br />
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)<br />
* [http://www.jaunty.bplaced.net/flightgear/index.php a small FlightGear page]<br />
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)<br />
<br />
=== Other FlightGear repositories/mirrors ===<br />
* [http://www.unitedfreeworld.com/ unitedfreeworld] (scenery, plane models, and livery)<br />
* [http://www.flightgearplanes.com Flightgear Planes Website]<br />
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft] <br />
<br />
=== Old Hangars ===<br />
* [http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]<br />
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002) <br />
<br />
=== Related content ===<br />
* [[Table of models]]<br />
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]<br />
<br />
[[Category:List]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=FlightGear_hangars&diff=32116FlightGear hangars2011-06-06T13:43:00Z<p>Scotth1: /* Hangars */</p>
<hr />
<div>''See [[Links]] for an overall listing of FlightGear related external websites''<br />
<br />
FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version. <br />
<br />
Be careful with external links! <br />
<br />
=== Official hangars ===<br />
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar]<br />
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)<br />
* [http://liveries.flightgear.org FlightGear Liveries]<br />
<br />
=== Hangars ===<br />
* [http://alphashangar.co.nr/ Alpha-J's Hangar] (Aircraft, Liveries, Scenery, AI, etc.)<br />
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] <br />
* <s>[http://bravosflightgear.yolasite.com/ Bravo's FlightGear] (Airbus A318-100) </s><br />
* [http://ltts.crlt.indiana.edu/grn/flightgear/ Buckaroo's Hangar] (Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a yasim intro)<br />
* [http://members.cox.net/davidculp/hangar.html Dave's Hangar] (also [http://daveshangar.blogspot.com/ Dave's Hangar Blog])<br />
* [http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar] (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)<br />
* [http://flier95-flightgear.blogspot.com/ Flier95's Hangar] (Blog format)<br />
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)<br />
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)<br />
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons)<br />
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (156+ original aircraft)<br />
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles) <br />
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)<br />
* [http://icestar-fghangar.web44.net/ Icecode's & Star's Hangar] (under development)<br />
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)<br />
* [http://flightgear.bplaced.de/ longfly's hangar] (not only German!)<br />
** [http://www.flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts] (under development)<br />
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)<br />
* [http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar] (5+ liveries & mods)<br />
* [http://theomegahangar.webs.com Omega Hangar] (Mobile Stairway)<br />
* [http://sites.google.com/site/pjedvajflightgear/ pjedvaj's Hangar] (Sukhoi T-50 PAK-FA,, Mikoyan-Gurevich MiG-21bis, Pilatus PC-21, Pilatus PC-9M) <br />
* [http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar] (a few well made aircraft)<br />
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many non-english aircraft articles)<br />
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)<br />
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)<br />
* [http://skyopshangar.byethost17.com/ Skyop's FlightGear Hangar] (717, 757-200, A300, A320-family, A330-300, A340-300, ATR 72, CRJ900, Paper airplane, & scenery)<br />
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]<br />
* [http://sydhangar.daffodil.uk.com/ Syd's Hangar ] (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)<br />
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)<br />
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)<br />
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]<br />
* [https://www.gitorious.org/airbus-aircraft] (A320, A330, A340-300, A380)<br />
<br />
==== Livery hangars ====<br />
* [http://www.AAliveries.yolasite.com/ Armchair Ace Liveries] (Aircraft Modifications and liveries)<br />
* [http://berwickskins.yolasite.com/ Berwick-skins]<br />
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]<br />
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]<br />
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]<br />
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]<br />
<br />
==== Homepages, blogs, etc. ====<br />
<br />
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]<br />
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)<br />
* [http://www.fguk.eu/ FlightGear United Kingdom] <br />
* [http://www.flightgear-germany.de/ FlightGear Germany] (DE)<br />
* [http://flightgear2009.blogspot.com/ Flight Gear Brasil 2009] (non-english)<br />
* [http://www.shialeweb.com/caballerosaguila/news.php Caballeros Aguila] (non-english)<br />
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]<br />
* [http://tehwarlock.tk/ Tehwarlock Blog]<br />
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)<br />
* [http://www.jaunty.bplaced.net/flightgear/index.php a small FlightGear page]<br />
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)<br />
<br />
=== Other FlightGear repositories/mirrors ===<br />
* [http://www.unitedfreeworld.com/ unitedfreeworld] (scenery, plane models, and livery)<br />
* [http://www.flightgearplanes.com Flightgear Planes Website]<br />
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft] <br />
<br />
=== Old Hangars ===<br />
* [http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]<br />
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002) <br />
<br />
=== Related content ===<br />
* [[Table of models]]<br />
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]<br />
<br />
[[Category:List]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=31620A380 Tutorial2011-05-13T14:13:27Z<p>Scotth1: /* Take-off */</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle so N1 (the second line from the top) is around 50%<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a de-rated takeoff, advance the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line FMA of the Primary Flight Display.<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the sidestick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1''' and '''PACK 2''' before 4000ft<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== Climb and Cruise ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== Descent ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track<br />
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.<br />
<br />
== Landing ==<br />
<br />
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.<br />
<br />
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''. This will keep the vertical speed at whatever it was, when the mode was engaged, you should then set a selected V/S value and set the selected altitude to whatever your next way-point would be.<br />
<br />
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.<br />
<br />
At around 3000ft the speed should be around 230knots, extend the gears and turn on external lighting for Nose, Landing and Wing lights.<br />
<br />
Set the Selected speed to '''200''' knots<br />
<br />
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.<br />
<br />
When you are within visual of the runway, reduce the selected speed to '''180 knots''', control your speed by extending the flaps to 1</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=31307Airbus A3802011-04-27T13:31:52Z<p>Scotth1: </p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status = Under development<br />
|fgname = A380<br />
|download = http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.0.0/A380_1.0.zip<br />
|development = http://gitorious.org/airbus-aircraft/a380/trees/master<br />
}}<br />
<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest [[:Category:Transport aircraft|freight aircraft]], with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
A [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (now with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions^<br />
* changeover level^<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localiser and approach<br />
* FlightDirector, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* E/WD (mostly)<br />
* updated Nav Display^<br />
* E/WD checklists^<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel^<br />
* air panel^<br />
* anti-ice panel^<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC^<br />
** electrical DC^<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance^<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and speed brake<br />
* cabin interior<br />
* fine tune flap movements and slat droop<br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* engine start sounds<br />
* complete PFD and EFIS selection switches<br />
* complete ND EFIS selection switches<br />
* <del>complete ND display modes</del><br />
** PLAN<br />
** LS<br />
** VOR<br />
** <del>MAP</del><br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
** <del>DOOR</del><br />
** <del>APU</del><br />
** <del>ENGINE</del><br />
** COND<br />
** WHEEL<br />
** PRESSURE<br />
** BLEED<br />
** <del>ELEC AC</del><br />
** <del>ELEC DC</del><br />
** <del>FUEL</del><br />
** HYDRAULIC<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* gear lever and indicators<br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; cabin pressure and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* fix up scaling of texture sizes<br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Aircraft]]<br />
[[Category:Aircraft TODO]]<br />
[[Category:Airliners]]<br />
[[Category:Civilian aircraft]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=31292A380 Tutorial2011-04-27T12:48:54Z<p>Scotth1: </p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 (the second line from the top) is around 50%<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a de-rated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line FMA of the Primary Flight Display.<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the sidestick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1''' and '''PACK 2''' before 4000ft<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== Climb and Cruise ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== Descent ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track<br />
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.<br />
<br />
== Landing ==<br />
<br />
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.<br />
<br />
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''. This will keep the vertical speed at whatever it was, when the mode was engaged, you should then set a selected V/S value and set the selected altitude to whatever your next way-point would be.<br />
<br />
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.<br />
<br />
At around 3000ft the speed should be around 230knots, extend the gears and turn on external lighting for Nose, Landing and Wing lights.<br />
<br />
Set the Selected speed to '''200''' knots<br />
<br />
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.<br />
<br />
When you are within visual of the runway, reduce the selected speed to '''180 knots''', control your speed by extending the flaps to 1</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Template:POTW/2011-16&diff=31202Template:POTW/2011-162011-04-24T13:43:22Z<p>Scotth1: qantas brandname was originally an acronym (Queensland And Northern Territory Aerial Services) so there is no U after the Q.</p>
<hr />
<div>{| class="prettytable" style="background-color:#efefef; width: 100%;" <br />
| align="center" |[[File:Fgfs-screen-012.png|300px]]<br />
|-<br />
| align="left" | A qantas passenger jet on a simulated flight from [[Brisbane International Airport]] to [[Sydney International Airport]], Australia<br />
<div style="text-align:right;">'''[[FlightGear_Newsletter_April_2011#Suggested_flights|Read more...]] | [[:Category:Picture of the week 2011|Archive]]'''</div><br />
|}<br />
<br />
<noinclude>[[Category:Picture of the week 2011]]</noinclude></div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=30912A380 Tutorial2011-04-10T07:32:37Z<p>Scotth1: /* Landing */</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 is around 50<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a derated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line of the PFD<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the joystick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1'''<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== Climb and Cruise ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== Descent ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track<br />
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.<br />
<br />
== Landing ==<br />
<br />
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.<br />
<br />
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''. This will keep the vertical speed at whatever it was, when the mode was engaged, you should then set a selected V/S value and set the selected altitude to whatever your next way-point would be.<br />
<br />
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.<br />
<br />
At around 3000ft the speed should be around 230knots, extend the gears and turn on external lighting for Nose, Landing and Wing lights.<br />
<br />
Set the Selected speed to '''200''' knots<br />
<br />
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.<br />
<br />
When you are within visual of the runway, reduce the selected speed to '''180 knots''', control your speed by extending the flaps to 1</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=30911A380 Tutorial2011-04-10T06:44:17Z<p>Scotth1: </p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 is around 50<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a derated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line of the PFD<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the joystick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1'''<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== Climb and Cruise ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== Descent ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track<br />
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.<br />
<br />
== Landing ==<br />
<br />
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.<br />
<br />
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''. This will keep the vertical speed at whatever it was, when the mode was engaged, you should then set a selected V/S value and set the selected altitude to whatever your next way-point would be.<br />
<br />
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.<br />
<br />
At around 3000ft the speed should be around 230knots, extend the gears and turn on external lighting for Nose, Landing and Wing lights.<br />
<br />
Set the Selected speed to '''200''' knots<br />
<br />
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.<br />
<br />
When you are within visual of the runway, reduce the selected speed to '''180 knots''', control your speed by extending the flaps to 1</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=30910A380 Tutorial2011-04-10T06:43:40Z<p>Scotth1: /* DESCENT */</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 is around 50<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a derated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line of the PFD<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the joystick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1'''<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== CLIMB and CRUISE ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== DESCENT ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track<br />
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.<br />
<br />
== Landing ==<br />
<br />
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.<br />
<br />
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''. This will keep the vertical speed at whatever it was, when the mode was engaged, you should then set a selected V/S value and set the selected altitude to whatever your next way-point would be.<br />
<br />
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.<br />
<br />
At around 3000ft the speed should be around 230knots, extend the gears and turn on external lighting for Nose, Landing and Wing lights.<br />
<br />
Set the Selected speed to '''200''' knots<br />
<br />
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.<br />
<br />
When you are within visual of the runway, reduce the selected speed to '''180 knots''', control your speed by extending the flaps to 1</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=30909A380 Tutorial2011-04-10T06:18:16Z<p>Scotth1: </p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 is around 50<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a derated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line of the PFD<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the joystick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1'''<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== CLIMB and CRUISE ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== DESCENT ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
# once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track<br />
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.<br />
<br />
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.</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=30908A380 Tutorial2011-04-10T05:08:28Z<p>Scotth1: </p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 is around 50<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a derated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line of the PFD<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the joystick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have '''FLEX''', '''SRS''' and '''HDG''' flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1'''<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== CLIMB and CRUISE ==<br />
# the PFD should now display '''THR CLB''', '''CLB''', '''NAV'''<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== DESCENT ==<br />
As the aircraft approaches the Top-of-Descent (T/D) pseudo waypoint;<br />
# the '''DES''' mode will be armed<br />
# and the throttle will be reduced<br />
once past the T/D waypoint, the aircraft will engage the '''DES''' mode and start the descent towards the airport along the STAR track</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=30907A380 Tutorial2011-04-10T04:32:00Z<p>Scotth1: </p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 is around 50<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a derated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line of the PFD<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the joystick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have FLEX, SRS and HDG flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1'''<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== CLIMB and CRUISE ==<br />
# the PFD should now display THR CLB, CLB, NAV<br />
# if ATC direct you to a specific altitude;<br />
## dial-up the altitude and use the middle-mouse-button to engage the Selected mode<br />
## 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<br />
## the PFD should now display "V/S" in green on the top ''engaged'' line and "ALT" in cyan on the second ''armed'' line<br />
## once the selected altitude has been reached, the ''armed'' mode will be cleared and the ''engaged'' mode will become "ALT"<br />
## clear the V/S mode by returning it to Managed mode with the left-mouse-button<br />
## to return to Managed CLB mode, click the altitude knob with the left-mouse-button<br />
# 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"<br />
# at the cross-over altitude (around 28000ft) the speed should automatically change to the mach value<br />
# at the cruise altitude, the managed altitude mode will change to '''ALT CRZ''' and the speed will change to '''MACH'''<br />
# if you need to step to a different altitude;<br />
## dial-up the new altitude value<br />
## click with the '''middle-mouse-button''' to engage the Selected mode<br />
## the PFD will change to "ALT" mode<br />
## to return the managed mode, click the altitude knob with the left-mouse-button, you will remain at the current altitude<br />
<br />
== DESCENT ==</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=30906A380 Tutorial2011-04-10T04:05:19Z<p>Scotth1: </p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br /><br />
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. <br />
<br />
One of the most complete free websites is [http://www.navdata.at/ www.navdata.at] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br /><br />
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/<br />
<br />
'''Scenery Tiles'''<br /><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br /><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br /><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br /><br />
YSSY depart 16R<br /><br />
SID: KAMPI 1<br /><br />
GEROS <br /><br />
STAR: ARADI 4B<br /><br />
NZAA approach 05R<br /><br />
<br />
<br />
'''Starting FlightGear'''<br /><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br /><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br /><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br /><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br /><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br /><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARAD4B''' <br />
# click on '''ACTIVE''' at the top of the page, a drop-down menu will appear, then select '''INIT'''.<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br /><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback''' (use ''Equipment'' -> ''Pushback'' to display the pushback vehicle)<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' and '''STROBE''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night<br />
# press Shift-B to release the parking brake<br />
# increase throttle and taxi at around 15knots as directed by ATC to the holding point<br />
# while taxing to the holding point, dial-up a selected heading of 158<br />
<br />
== Take-off ==<br />
We should now be lined-up on the runway waiting for clearance from ATC.<br />
# on the EFIS panel, set the radar range to 20nm<br />
# check GND-SPOILERS are armed, and the auto-brake is set to RTO<br />
# check selected HEADING is our initial heading (usually the same as the runway)<br />
# check the Flight Director is enabled<br />
# check flaps at 2<br />
# SPEED, ALTITUDE and V/S should be in '''Managed''' Mode, and HEADING should be in '''Selected''' Mode<br />
<br />
Once we have clearance for take-off;<br />
# increase throttle a little so N1 is around 50<br />
# wait for the engines to stabilise, then set throttle to the first indent (use '''SHIFT+Pg Up''')<br />
# as we are doing a derated takeoff, increment the throttle one more to the FLEX indent (press again '''SHIFT+Pg Up''')<br />
# The A/THR should automatically be engaged and '''FLEX''' should now appear at the top line of the PFD<br />
# at 100knots the First Officer should check the Engine display and call-out "Power Set"<br />
# 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<br />
# at Vr speed the First Officer should call-out "Rotate"<br />
# pull back on the joystick and try to aim for an angle a bit less than the 10 degrees line on the HUD<br />
# once positive climb has been established (generally around 300ft AGL) the First Officer should '''retract the gears'''<br />
# 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)<br />
# the top line of PFD should have FLEX, SRS and HDG flight mode annunciators displayed<br />
# push the '''HEADING''' knob with the Left-Mouse-Button to Managed Mode, the aircraft should track towards the first waypoint (KAMBI)<br />
# when the white FMA on the PFD for '''THR LVR''' appears, press '''SHIFT+Pg DOWN''' to reduce thrust to the CL indent<br />
# the first officer should turn ON the air '''PACK 1'''<br />
# at around 4000ft reduce the flaps to 1<br />
# at around 5000ft retract the flaps (to 0)<br />
# the first officer can turn off all the external lighting at this point<br />
<br />
== CLIMB ===<br />
# the PFD should now display THR CLB, CLB, NAV<br />
# at 18000ft use the left-mouse-button and click on the barometer knob on the EFIS panel so it displays "STD"</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Bindings&diff=30176Bindings2011-03-12T23:43:15Z<p>Scotth1: looks like property-set has been replaced with property-assign</p>
<hr />
<div>'''Bindings''' define what happens when a user:<br />
* [[Howto: Make a clickable panel#Pick|clicks an object]] in the [[scenery]] or an [[aircraft]]<br />
* press a key on the keyboard or [[joystick]]<br />
* clicks a [[menu]] item<br />
* click a buttons or fields in a dialog<br />
You can assign multiple bindings to one object/button/key.<br />
<br />
All give codes are examples, found on various places in the [[FlightGear]] package.<br />
<br />
== Commands ==<br />
=== dialog-show ===<br />
Shows a dialog, which should be present in <tt>[[$FG ROOT]]/gui/Dialogs</tt>. <br />
<binding><br />
<command>dialog-show</command><br />
<dialog-name>location-in-air</dialog-name><br />
</binding><br />
* '''dialog-name:''' the name of the dialog, as designated in its .xml file.<br />
<br />
=== nasal ===<br />
[[Nasal]] is frequently used for complicated systems.<br />
<binding><br />
<command>nasal</command><br />
<script>b777.afds.input(0,1);</script><br />
</binding><br />
<br />
=== property-adjust ===<br />
Increases or decreases a property's value with a given step. Maximum and minimum values are optional.<br />
<binding><br />
<command>property-adjust</command><br />
<property>/controls/lighting/panel-norm</property><br />
<step>-0.05</step><br />
<min>0</min><br />
<max>1</max><br />
</binding><br />
<br />
=== property-cycle ===<br />
Cycles between a list of values and assigns one to a property. The value-list can vary in length.<br />
<binding><br />
<command>property-cycle</command><br />
<property>/autopilot/autobrake/setting</property><br />
<value type="string">ARM</value><br />
<value type="string">DISARM</value><br />
<value type="string">OFF</value><br />
</binding><br />
<br />
=== property-randomize ===<br />
Assigns a random value (between min and max) to a property.<br />
<binding><br />
<command>property-randomize</command><br />
<property>/orientation/pitch-deg</property><br />
<min>0</min><br />
<max>360</max><br />
</binding><br />
<br />
=== property-set ===<br />
'''''This command appears to be deprecated since V2.0'''''<br />
<del>One of the most important commands. It sets a property to a predefined value.<br />
<code><br />
<binding><br />
<command>property-set</command><br />
<property>/autopilot/settings/target-speed-kt</property><br />
<value>0</value><br />
</binding><br />
</code><br />
</del><br />
<br />
=== property-assign ===<br />
One of the most important commands. It sets a property to a predefined value.<br />
<binding><br />
<command>property-assign</command><br />
<property>/autopilot/settings/target-speed-kt</property><br />
<value>0</value><br />
</binding><br />
<br />
=== property-swap ===<br />
Swaps the values of two properties.<br />
<binding><br />
<command>property-swap</command><br />
<property>/instrumentation/comm/frequencies/selected-mhz</property><br />
<property>/instrumentation/comm/frequencies/standby-mhz</property><br />
</binding><br />
<br />
=== property-toggle ===<br />
Toggles the value of a property on each click, between true (1) and false (0).<br />
<binding><br />
<command>property-toggle</command><br />
<property>/controls/gear/gear-down</property><br />
</binding><br />
Or if defined it toggles between two values.<br />
<binding><br />
<command>property-toggle</command><br />
<property>/controls/gear/gear-down</property><br />
<value>2</value><br />
<value>3</value><br />
</binding></div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=28643A380 Tutorial2011-02-21T12:17:45Z<p>Scotth1: /* Automatic Startup Procedure */</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br/><br />
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. <br />
<br />
One of the most complete free websites is [[http://www.navdata.at/ www.navdata.at]] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br/><br />
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/<br />
<br />
'''Scenery Tiles'''<br/><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br/><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br/><br />
YSSY depart 16R<br/><br />
SID: KAMPI 1<br/><br />
GEROS <br/><br />
STAR: ARADI 2B<br/><br />
NZAA approach 05R<br/><br />
<br />
<br />
'''Starting FlightGear'''<br/><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br/><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br/><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br/><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br/><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br/><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARADI2B''' <br />
# click on '''ACTIVE''' at the top of the page, this will take us back to the INIT page<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br/><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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 (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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback'''<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 765kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Howto_talk:Animated_jetways_(Type_1)&diff=28609Howto talk:Animated jetways (Type 1)2011-02-20T12:56:05Z<p>Scotth1: Created page with "A380 includes this in the fgdata and git dev repository versions. ~~~~"</p>
<hr />
<div>A380 includes this in the fgdata and git dev repository versions.<br />
<br />
[[User:Scotth1|Scotth1]] 07:56, 20 February 2011 (EST)</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Howto:Animated_jetways_(Type_1)&diff=28608Howto:Animated jetways (Type 1)2011-02-20T12:55:40Z<p>Scotth1: A380 includes this in the fgdata and git dev repository versions.</p>
<hr />
<div>[[File:777jetwaybeaf.jpg|thumb|right|300px|Before and after; jetways connecting to a [[Boeing 777-200]]]]<br />
<br />
This article describes the animated jetway system by [[User:Skyop|Skyop]], how to use it, and how to implement it.<br />
<br />
=Usage=<br />
<br />
[[File:KLAS_jetways.png|thumb|right|300px|Animated jetway connected to a [[Boeing 737-300]] at Las Vegas McCarran International Airport (KLAS)]]<br />
[[File:Movjetway-night.jpg|thumb|right|300px|Jetways at Reno International Airport (KRNO) lighting up during the night]]<br />
<br />
Currently, the following airports implement animated jetways in their scenery:<br />
<br />
* Ted Stevens Anchorage International Airport (PANC) ([[TerraSync]]-only)<br />
* Las Vegas McCarran International Airport (KLAS) (TerraSync-only)<br />
* Reno International Airport (KRNO) (TerraSync-only)<br />
<br />
'''Note that when TerraSyncing an airport, you have to tell [[FlightGear]] to load the new jetway models. To do this, set the <tt>/sim/paths/use-custom-scenery-data</tt> property to "true" in [[FGRun]]. Command-line users, use the <tt>--prop:/sim/paths/use-custom-scenery-data=true</tt> switch.'''<br />
<br />
The following aircraft are animated-jetway capable (a package of updated <tt>-set.xml</tt> files for the [[Airbus A380|A380]], [[Boeing 737-300|733]], [[Boeing 747-400|744]], and [[Boeing 777-200|772ER]] can be downloaded [http://www.4shared.com/file/fLzcEEfI/movjetway-sets.html here]):<br />
<br />
* [[Airbus A320]]<br />
* [[Airbus A380]]<br />
* [[Boeing 737-300]] (separate download)<br />
* [[Boeing 747-400]] (separate download)<br />
* [[Boeing 777-200ER]] (separate download)<br />
* [[Boeing 787|Boeing 787-8]] (second jetway disabled, it goes through an engine)<br />
* [[Bombardier CRJ-200LR]]<br />
<br />
First determine if the jetway is clickable and is animated. To do this, press Ctrl-C. If the polygons of the jetway are outlined in yellow, then it is indeed animated.<br />
<br />
Now align your airliner so that the nosegear is centered on the marking line and is directly over the "T" at the end of it. Click the jetway; if your aircraft does not include the required positioning information, you'll get a tooltip informing you that the jetway cannot be extended. Otherwise, the jetway should begin to position itself and eventually connect to your aircraft. Congratulations!<br />
<br />
=Implementation=<br />
<br />
==For aircraft developers==<br />
<br />
To make your aircraft animated jetway-capable, you'll need to specify the following in your aircraft's -set.xml:<br />
<br />
* The amount at which to extend the jetway (<tt>x-tra</tt>)<br />
* The amount at which to lower/raise the jetway by rotating it along its Y axis (<tt>y-rot</tt>)<br />
* The amount at which to rotate the jetway along its Z axis (<tt>z-rot</tt>)<br />
* The amount at which to rotate the hood to extend it to the aircraft (<tt>hood-rot</tt>)<br />
<br />
They should be added within the <tt>&lt;aircraft&gt;</tt> tag in the root of your XML file (but still within <tt>&lt;PropertyList&gt;</tt> of course!).<br />
<br />
For instance, here's the jetway positioning information for the Boeing 737-300.<br />
<br />
<aircraft><br />
<jetway-pos><br />
<x-tra>-1</x-tra><br />
<y-rot>-4</y-rot><br />
<z-rot>21</z-rot><br />
<hood-rot>5</hood-rot><br />
</jetway-pos><br />
</aircraft><br />
<br />
Here's the positioning information for the Boeing 777-200ER. Note the <tt>&lt;jetway2-pos&gt;</tt>, which describes positioning information for the second jetway.<br />
<br />
<aircraft><br />
<jetway-pos><br />
<x-tra>-1</x-tra><br />
<y-rot>4</y-rot><br />
<z-rot>16</z-rot><br />
<hood-rot>2</hood-rot><br />
</jetway-pos><br />
<jetway2-pos><br />
<x-tra>2.5</x-tra><br />
<y-rot>5</y-rot><br />
<z-rot>46</z-rot><br />
<hood-rot>2</hood-rot><br />
</jetway2-pos><br />
</aircraft><br />
<br />
Last but certainly not least, the A380:<br />
<br />
<aircraft><br />
<jetway-pos><br />
<x-tra>-2</x-tra><br />
<y-rot>2</y-rot><br />
<z-rot>18</z-rot><br />
<hood-rot>0</hood-rot><br />
</jetway-pos><br />
<jetway2-pos><br />
<x-tra>2.5</x-tra><br />
<y-rot>2.5</y-rot><br />
<z-rot>45</z-rot><br />
<hood-rot>0</hood-rot><br />
</jetway2-pos><br />
<jetway3-pos><br />
<x-tra>4</x-tra><br />
<y-rot>5</y-rot><br />
<z-rot>47</z-rot><br />
<hood-rot>3</hood-rot><br />
</jetway3-pos><br />
</aircraft><br />
<br />
The following will describe how to get these values. I will be using [[Blender]] for this purpose, but any 3D modeling program that can read [[AC3D]] files will suffice.<br />
<br />
First, open up your 3D modeling suite and import one of the jetway models. They are located at <tt>(TerraSync directory)/Models/Airport</tt>, and are available through [[TerraSync]] or the [http://scenemodels.flightgear.org/modelbrowser.php?shared=7 Airport section of the FlightGear Scenery Database model directory] (look for "jetway-movable.xml," "jetway-movable-2.xml," or "jetway-movable-3.xml").<br />
<br />
Now import your aircraft model (in this case, I am using [[User:Gijs|Gijs']] [[Boeing 747-400]]). Align it with the marking line as if you were piloting it.<br />
<br />
[[File:Ajetway-air-tut1.png|800px]]<br />
<br />
Now select the following objects: Tunnel2, Tunnel3, Rotunda2, Entrance, and Hood. Move them along their X axis until you think you have the correct length to extend the jetway. ''(Hint: You can always "retract" the jetway by moving these objects by a negative value!)''<br />
<br />
[[File:Ajetway-air-tut2.png|800px]]<br />
<br />
Now select the following objects: Tunnel1Rotunda, Tunnel1, Tunnel2, Tunnel3, Rotunda2, Entrance, and Hood. Rotate them along the Z axis with the center of axis being at 0,0,0 (X,Y,Z) until the jetway's movable rotunda is a couple meters or so away from the aircraft. In Blender, I could simply move my cursor to 0,0,0 and set the rotation pivot to cursor mode. The procedure will be different depending on what 3D modeling software you are using, of course. You may have to undo this step if you find that you extended the jetway too much or too little in the previous step.<br />
<br />
[[File:Ajetway-air-tut3.png|800px]]<br />
<br />
Once you are happy with the jetway's extension/rotation, use the amount you extended the jetway along its X axis as your <tt>&lt;x-tra&gt;</tt> value and the amount you rotated the jetway along its Z axis as your <tt>&lt;z-rot&gt;</tt> value.<br />
<br />
In-game, the jetway's entrance will automatically rotate itself to compensate for the rest of the jetway's rotation, so there is no need to manipulate the entrance.<br />
<br />
Now, undo all transformations you have done to the jetway until it is in the same state as it was when you imported it. Select the following objects: Tunnel1, Tunnel2, Rotunda2, Entrance, and Hood. Rotate them along the Y axis with the center of axis being at 1.5,0,4 until the entrance of the jetway aligns with the door of the aircraft vertically. Use the value you rotated the jetway at as your <tt>&lt;y-rot&gt;</tt> value ''(note: the values should be inverted, so if you rotated the jetway along its Y axis -2 degrees to get it 2 degrees up, you should use 2 instead of -2)''.<br />
<br />
[[File:Ajetway-air-tut4.png|800px]]<br />
<br />
Finally, we have one last value to fill in: <tt>&lt;hood-rot&gt;</tt>. It simply specifies how much the jetway's hood should extend itself by rotation. You can simply use some common sense here: obviously, this would be something along the lines of 0 for jumbo jets and 5 for a Boeing 737-like aircraft. Be careful not to set this value to something too high, otherwise the hood will appear to detach itself from the jetway!<br />
<br />
Eventually, you should end up with an <tt>&lt;aircraft&gt;</tt> tree that resembles the examples above. Load up your aircraft in-game and taxi to an animated jetway. Click it, and hope everything works well!<br />
<br />
[[File:Ajetway-air-tut5.jpg|800px]]<br />
<br />
The procedure for utilizing a second or third jetway is essentially the same. The only difference is that some center of axis coordinates need to be changed (i.e., rotating the entire jetway by its Z axis from point 18,-5,0 instead of 0,0,0.<br />
<br />
==For scenery developers==<br />
<br />
[[File:Animatedjetway1.jpg|thumb|right|270px|A gate with one animated jetway; note the style, the details, and the level walking passage]]<br />
<br />
Simply place a <tt>Models/Airport/jetway-movable.xml</tt> wherever you want- note that the origin of the jetway models are always at the terminal rotunda of the first jetway. You can download the movable jetway models through [[TerraSync]] or from [http://scenemodels.flightgear.org/modelbrowser.php?shared=7 the Airport section of the FlightGear Scenery Database model directory] (look for "jetway-movable.xml," "jetway-movable-2.xml," or "jetway-movable-3.xml").<br />
<br />
==For scenery modelers==<br />
<br />
The default animated jetway design is very common throughout the world, and found in practically all major United States airports. If you wish to create your own style though (i.e. glass jetways), then the simplest method would be to retexture one of the default animated jetways and copy the contents of its XML file (but change the <tt>&lt;path&gt;</tt>, of course).<br />
<br />
You could create an entirely different jetway model, but you must keep the object names the same, and everything in the '''exact''' same location. Copy the contents of the XML file for one of the default animated jetways (but change the <tt>&lt;path&gt;</tt>, of course).<br />
<br />
=External links=<br />
<br />
* [http://tinypic.com/player.php?v=ajul44&s=4 Video showcasing the animation]<br />
* [http://www.4shared.com/file/fLzcEEfI/movjetway-sets.html Package of updated -set.xml files for various aircraft]<br />
* [http://www.flightgear.org/forums/viewtopic.php?t=8728 Development thread]<br />
<br />
[[Category:Scenery]]<br />
[[Category:Scenery enhancement]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airports_under_construction&diff=27540Airports under construction2011-01-13T23:23:14Z<p>Scotth1: oops missed a column</p>
<hr />
<div>== Preface ==<br />
<br />
=== Found a beacon in the middle of the runway in [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal LMML] or some other faults? ===<br />
First you have to know that 90 % of the airports have "bad layouts" at the moment and at some places even maps are not updated (have a [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal look here] i.e.). Most of the airports need updates. This is a lot of work when you think about the 20’000 airports in the database. When you read the tutorials how to build airports you can do it yourself and submit your work. Or someone of the contributors here will once start to work on your "wish" - but please be patient and do not send any messages/mails to contributors. You can go to the forum ([http://www.flightgear.org/forums/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.<br />
<br />
== Airports under construction ==<br />
In this article you find a list of all airports which currently are under construction. You can also see if an airport is "finished" and if the data is already submited to the current database of the mapserver (apt.dat). <br />
<br />
=== Avaiability of new/changed airports needs some time ===<br />
In FlightGear there is a common workflow to edit airports. First expierenced contributors have to change the airport data with "taxidraw". Then they submit the new data to the mapserver (main scenery data files/airport data file apt.dat). Meantime other contributors can also submit some scenery to the custom scenery database (for downloading via TerraSync). But for runways, taxiways, beacons, frequencies the apt.dat-File needs an update anyway and maybe also the base scenery around the airport needs an update. Please be patient with updates. It needs more time than you expected.<br />
<br />
== Submit your work plans and schedule your activities ==<br />
Please feel free to edit this page and submit your "pending airport" directly.<br />
<br />
=== Current Activities ===<br />
<br />
{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"<br />
|-<br />
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments<br />
|-<br />
|EDWG||gral||x||||||2010-02-03||||<br />
|-<br />
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions<br />
|-<br />
|EDWL||gral||x||||||2010-02-03||||<br />
|-<br />
|EDWY||gral||x||||||2010-02-03||||<br />
|-<br />
|EEKE||henrikp||x||||||2010-10||||<br />
|-<br />
|EERU||henrikp||x||||||2010-10||||<br />
|-<br />
|EEKA||henrikp||x||||||2010-10||||<br />
|-<br />
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail<br />
|-<br />
|EGKK||karla||||x||x||2010-02-13||2010-02-07||fully complete; over 60 customized buildings and other features with highly detailed day and night textures; full taxiway signs; AI traffic, parking and taxiways; available as direct download (see forum) or on Git/Git<br />
|-<br />
|EHGG||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|EHAM||Gijs||x||x||x||x||x|| || ||<br />
|- <br />
|EHLE||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHVK||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHEH||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHKD||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHTX||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|EHAL||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHRD||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHLW||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|KCHO||Catchatyou||x|| || ||2010-12-05|| ||The basic structure of the airport is almost complete, and once the airport is correctly modeled, I will be adding the parking lot, hangars...||<br />
|-<br />
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways<br />
|-<br />
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.<br />
|-<br />
|KSFO||karla|| ||x|| ||2010-08-06 ||2010-08-27 ||Terminal 2 fully remodelled; new day and night textures; new light masts; jetways included; actual T2 under reconstruction 2010; available as direct download (see forum) or on Git/Git<br />
|-<br />
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs<br />
|-<br />
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)<br />
|-<br />
|RPLL||D-SKY1||||x||x||2009-12-03||2010-02-11||T1, T2, T3, Tower, AI ground network, AI traffic, ATC freqs. Todo: taxi- and runways redesign<br />
|-<br />
|SBBG||Prestes||x||x|| ||2009-12-26 || ||<br />
|-<br />
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz<br />
|-<br />
|SBPK||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|SBRG||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|SUMU||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues<br />
|-<br />
|VTBD||D-SKY1||||x||x||2010-11-27 || ||Work in progress<br />
|-<br />
|YSSY||scotth1||x||x||x|| ||2011-01-11||adjusted aprons, taxiways, moved windsocks, AI ground network submitted. very basic International terminal yet to be submitted, TODO: domestic terminal, cargo terminal<br />
|}<br />
<br />
== Submit your wishes ==<br />
If you wish to add an airport or think this or another airport needs a change '''[http://www.flightgear.org/forums/viewtopic.php?f=5&t=6749 you have to post in the forum (scenery enhancement)]'''. But first search the forum with the ICAO code of the airport and be sure that you have read all the posts about this airport. And please submit also some links to images and information you have about/from this airport.<br />
<br />
== Links ==<br />
* [http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] <sup>1)</sup><br />
* [http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] <sup>1)</sup><br />
* [http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear Git]<br />
* [[Taxidraw|TaxiDraw Tutorial]]<br />
* [http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]<br />
* [http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]<br />
<br />
<sup>1)</sup> "mapserver.flightgear.org" is NOT "mpmap02.flightgear.org". The mpmap02 is hosted on another server and could reflect an older apt.dat.gz than the current one of the mapserver or of the Git server.<br />
<br />
=== Other airport work related pages in the FlightGear wiki ===<br />
* List of [[Developed Airports]] with buildings and [[Signs]] already included in the [[FlightGear Scenery Database]]<br />
* [[Germany|Current work in Germany]]<br />
* [[Current Scenery Projects]]<br />
* [[FlightGear User Created Helipad List]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airports_under_construction&diff=27539Airports under construction2011-01-13T23:22:14Z<p>Scotth1: updated YSSY with taxidraw and submitted to Jon Stockill</p>
<hr />
<div>== Preface ==<br />
<br />
=== Found a beacon in the middle of the runway in [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal LMML] or some other faults? ===<br />
First you have to know that 90 % of the airports have "bad layouts" at the moment and at some places even maps are not updated (have a [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal look here] i.e.). Most of the airports need updates. This is a lot of work when you think about the 20’000 airports in the database. When you read the tutorials how to build airports you can do it yourself and submit your work. Or someone of the contributors here will once start to work on your "wish" - but please be patient and do not send any messages/mails to contributors. You can go to the forum ([http://www.flightgear.org/forums/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.<br />
<br />
== Airports under construction ==<br />
In this article you find a list of all airports which currently are under construction. You can also see if an airport is "finished" and if the data is already submited to the current database of the mapserver (apt.dat). <br />
<br />
=== Avaiability of new/changed airports needs some time ===<br />
In FlightGear there is a common workflow to edit airports. First expierenced contributors have to change the airport data with "taxidraw". Then they submit the new data to the mapserver (main scenery data files/airport data file apt.dat). Meantime other contributors can also submit some scenery to the custom scenery database (for downloading via TerraSync). But for runways, taxiways, beacons, frequencies the apt.dat-File needs an update anyway and maybe also the base scenery around the airport needs an update. Please be patient with updates. It needs more time than you expected.<br />
<br />
== Submit your work plans and schedule your activities ==<br />
Please feel free to edit this page and submit your "pending airport" directly.<br />
<br />
=== Current Activities ===<br />
<br />
{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"<br />
|-<br />
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments<br />
|-<br />
|EDWG||gral||x||||||2010-02-03||||<br />
|-<br />
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions<br />
|-<br />
|EDWL||gral||x||||||2010-02-03||||<br />
|-<br />
|EDWY||gral||x||||||2010-02-03||||<br />
|-<br />
|EEKE||henrikp||x||||||2010-10||||<br />
|-<br />
|EERU||henrikp||x||||||2010-10||||<br />
|-<br />
|EEKA||henrikp||x||||||2010-10||||<br />
|-<br />
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail<br />
|-<br />
|EGKK||karla||||x||x||2010-02-13||2010-02-07||fully complete; over 60 customized buildings and other features with highly detailed day and night textures; full taxiway signs; AI traffic, parking and taxiways; available as direct download (see forum) or on Git/Git<br />
|-<br />
|EHGG||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|EHAM||Gijs||x||x||x||x||x|| || ||<br />
|- <br />
|EHLE||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHVK||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHEH||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHKD||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHTX||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|EHAL||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHRD||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHLW||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|KCHO||Catchatyou||x|| || ||2010-12-05|| ||The basic structure of the airport is almost complete, and once the airport is correctly modeled, I will be adding the parking lot, hangars...||<br />
|-<br />
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways<br />
|-<br />
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.<br />
|-<br />
|KSFO||karla|| ||x|| ||2010-08-06 ||2010-08-27 ||Terminal 2 fully remodelled; new day and night textures; new light masts; jetways included; actual T2 under reconstruction 2010; available as direct download (see forum) or on Git/Git<br />
|-<br />
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs<br />
|-<br />
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)<br />
|-<br />
|RPLL||D-SKY1||||x||x||2009-12-03||2010-02-11||T1, T2, T3, Tower, AI ground network, AI traffic, ATC freqs. Todo: taxi- and runways redesign<br />
|-<br />
|SBBG||Prestes||x||x|| ||2009-12-26 || ||<br />
|-<br />
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz<br />
|-<br />
|SBPK||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|SBRG||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|SUMU||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues<br />
|-<br />
|VTBD||D-SKY1||||x||x||2010-11-27 || ||Work in progress<br />
|-<br />
|YSSY||scotth1||x||x|| ||2011-01-11||adjusted aprons, taxiways, moved windsocks, AI ground network submitted. very basic International terminal yet to be submitted, TODO: domestic terminal, cargo terminal<br />
|}<br />
<br />
== Submit your wishes ==<br />
If you wish to add an airport or think this or another airport needs a change '''[http://www.flightgear.org/forums/viewtopic.php?f=5&t=6749 you have to post in the forum (scenery enhancement)]'''. But first search the forum with the ICAO code of the airport and be sure that you have read all the posts about this airport. And please submit also some links to images and information you have about/from this airport.<br />
<br />
== Links ==<br />
* [http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] <sup>1)</sup><br />
* [http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] <sup>1)</sup><br />
* [http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear Git]<br />
* [[Taxidraw|TaxiDraw Tutorial]]<br />
* [http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]<br />
* [http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]<br />
<br />
<sup>1)</sup> "mapserver.flightgear.org" is NOT "mpmap02.flightgear.org". The mpmap02 is hosted on another server and could reflect an older apt.dat.gz than the current one of the mapserver or of the Git server.<br />
<br />
=== Other airport work related pages in the FlightGear wiki ===<br />
* List of [[Developed Airports]] with buildings and [[Signs]] already included in the [[FlightGear Scenery Database]]<br />
* [[Germany|Current work in Germany]]<br />
* [[Current Scenery Projects]]<br />
* [[FlightGear User Created Helipad List]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=27360A380 Tutorial2011-01-04T03:10:10Z<p>Scotth1: split preparation and pre-flight checklists</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br/><br />
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. <br />
<br />
One of the most complete free websites is [[http://www.navdata.at/ www.navdata.at]] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br/><br />
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/<br />
<br />
'''Scenery Tiles'''<br/><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages, Warnings and Checklist display (along with Engine Display above form the "E/W Display")<br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# Multi-Function Display (MFD) screens - display FMGS information<br />
# Keyboard and Corsor Control Units (KCCD) Keyboard and num-pad for entering FMGS information<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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)<br />
<br />
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.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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).<br />
<br />
'''Selected Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
<br />
'''Managed Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br/><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br/><br />
YSSY depart 16R<br/><br />
SID: KAMPI 1<br/><br />
GEROS <br/><br />
STAR: ARADI 2B<br/><br />
NZAA approach 05R<br/><br />
<br />
<br />
'''Starting FlightGear'''<br/><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklists ====<br />
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.<br />
<br />
===== Cockpit Preparation Checklist =====<br />
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.<br />
* move your way down and check each section;<br />
*# ADIRS<br />
*# Probe and Window Heat<br />
*# Flight Control (F/CTL)<br />
*# Fuel Jettison<br />
*# Evacuation<br />
*# Emergency Electrical Power<br />
*# Entertainment<br />
*# Oxygen<br />
*# Calls and Wiper<br />
*# Engine Fire<br />
*# Hydraulics Panel<br />
*# Fuel Panel <br />
*# Electrical Panel<br />
*#* ensure nothing is selected OFF<br />
*#* click ON if EXTERNAL power is AVAIL<br />
*# Cargo Air<br />
*# Air Panel (ensure packs and hot-air are OFF)<br />
*# Cargo Smoke<br />
*# Vents (avionics fan should be on if heavy rain) <br />
*# Anti Ice panel (wing anti-ice should be OFF while on the ground)<br />
*# External Lighting (only NAV lights should be ON if the aircraft is powered)<br />
*# Engine Start (should be in NORM position)<br />
*# click the APU '''Master Sw''' ON<br />
*#* the '''APU''' ECAM page should be automatically displayed<br />
*# Cabin Pressure (should be in AUTO mode)<br />
*# Internal Lighting<br />
*#* click ON '''STORM''' if you are flying at night<br />
*#* click the '''NO-SMOKING''' switch to AUTO<br />
<br />
Now move to the Glareshield;<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
<br />
===== Pre-flight Checklist =====<br />
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.<br />
<br />
<br />
This completes our pre-flight preparation checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br/><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br/><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br/><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br/><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br/><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARADI2B''' <br />
# click on '''ACTIVE''' at the top of the page, this will take us back to the INIT page<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br/><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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 (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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying checks Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# click OFF any external power sources<br />
# Request external power disconnection from ground crew (CTRL-e will toggle the connection of ground external power)<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback'''<br />
# check all doors are closed (should all be green)<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# click with left-mouse-button '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 20kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated (otherwise ingestion of engine exhaust)<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=27313Airbus A3802011-01-03T02:49:02Z<p>Scotth1: </p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status = Under development<br />
|fgname = A380<br />
|download = http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.0.0/A380_1.0.zip<br />
|development = http://gitorious.org/airbus-aircraft/a380/trees/master<br />
}}<br />
<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest [[:Category:Transport aircraft|freight aircraft]], with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (now with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions^<br />
* changeover level^<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localiser and approach<br />
* FlightDirector, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* E/WD (mostly)<br />
* updated Nav Display^<br />
* E/WD checklists^<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel^<br />
* air panel^<br />
* anti-ice panel^<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC^<br />
** electrical DC^<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance^<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and speed brake<br />
* cabin interior<br />
* fine tune flap movements and slat droop<br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* engine start sounds<br />
* complete PFD and EFIS selection switches<br />
* complete ND EFIS selection switches<br />
* <del>complete ND display modes</del><br />
** PLAN<br />
** LS<br />
** VOR<br />
** <del>MAP</del><br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
** <del>DOOR</del><br />
** <del>APU</del><br />
** <del>ENGINE</del><br />
** COND<br />
** WHEEL<br />
** PRESSURE<br />
** BLEED<br />
** <del>ELEC AC</del><br />
** <del>ELEC DC</del><br />
** <del>FUEL</del><br />
** HYDRAULIC<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* gear lever and indicators<br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; cabin pressure and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* fix up scaling of texture sizes<br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Aircraft]]<br />
[[Category:Aircraft TODO]]<br />
[[Category:Airliners]]<br />
[[Category:Civilian aircraft]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=Airbus_A380&diff=27289Airbus A3802011-01-02T23:46:33Z<p>Scotth1: update completed to-do list</p>
<hr />
<div>{{infobox Aircraft<br />
|image = A380 in flight.png<br />
|name = Airbus A380<br />
|type = Airliner<br />
|livery = Airbus, Singapore, Qantas<br />
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton<br />
|fdm = JSBSim<br />
|status = Under development<br />
|fgname = A380<br />
|download = http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.0.0/A380_1.0.zip<br />
|development = http://gitorious.org/airbus-aircraft/a380/trees/master<br />
}}<br />
<br />
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.<br />
<br />
The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest [[:Category:Transport aircraft|freight aircraft]], with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).<br />
<br />
== Aircraft help ==<br />
<br />
=== Startup ===<br />
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)<br />
# Start APU by clicking Master SW on the overhead<br />
# Optionally enter flight plan on MFD<br />
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]<br />
# click on strobe and beacon lighting<br />
# Switch Engine Start to IGN/START on overhead<br />
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair<br />
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal<br />
# you can turn off the APU by clicking the APU Master Sw.<br />
<br />
=== Takeoff ===<br />
# release parking brake<br />
# Flaps to position 2 (0-4)<br />
# Push throttle to around 50% N1 and wait to stabilise<br />
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent<br />
# Get Vr speed (~165 kts) and rotate<br />
# pitch up to around 10deg and maintain 210kts<br />
# Gear up<br />
# AP1 enabled, push HDG to managed mode if flight plan entered<br />
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down<br />
# Before THR ACCEL retract flaps fully<br />
<br />
=== Airbus Flight Guidance ===<br />
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from; <br />
# the flight plan as entered on the MFD<br />
# the current phase of flight<br />
# the performance characteristics as entered on the MFD<br />
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.<br />
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]<br />
<br />
=== Flight Management System ===<br />
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.<br />
<br />
If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.<br />
<br />
== Development status/Issues/Todo ==<br />
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].<br />
<br />
=== Complete ===<br />
* basic model<br />
** fuselage<br />
** wings (now with wing flex)<br />
** vertical and horizontal stabilisers<br />
** flaps and slats<br />
** engines, pylons and wing-tips<br />
* FDM<br />
* autopilot tuning<br />
* engine, wind, seat-belt chime sounds<br />
* pushback<br />
* gear retraction and doors<br />
* fuel tanks<br />
* cargo, crew and passenger point mass<br />
* CL, FLEX and TOGA thrust detents and A/THR<br />
* majority of FMS<br />
* SID/STAR parser<br />
* Flight Guidance Computer<br />
* simple electrical system<br />
* door system, just needs objects to animate! <br />
* animated jetway positions^<br />
* changeover level^<br />
<br />
==== Glareshield ====<br />
* altitude selected mode<br />
* heading selected mode<br />
* speed selected mode<br />
* vertical managed mode<br />
** SRS<br />
** CLB<br />
** OP CLB<br />
** CRZ<br />
** DES<br />
** OP DES<br />
* lateral managed mode<br />
** NAV<br />
** LOC<br />
* speed managed mode<br />
** CLB<br />
** CRZ<br />
** DES<br />
* localiser and approach<br />
* FlightDirector, AP 1 and AP 2<br />
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting<br />
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)<br />
<br />
==== Front Panel ====<br />
* FMA on PFD (active and some armed lateral, vertical and thrust)<br />
* indicated speed ribbon on PFD<br />
* E/WD (mostly)<br />
* updated Nav Display^<br />
* E/WD checklists^<br />
<br />
==== Overhead ====<br />
* apu start<br />
* engine IGN <br />
* strobe, beacon, nav lights, landing, nose<br />
* seat-belt and no-smoking switches<br />
* electrical panel^<br />
* air panel^<br />
* anti-ice panel^<br />
<br />
==== Pedestal ====<br />
* Flaps lever<br />
* MFD keyboard and number pad<br />
* ECAM/SD page select<br />
* System Display (ECAM/SD) (many pages)<br />
** permanent data zone<br />
** doors<br />
** cruise<br />
** engines<br />
** apu<br />
** fuel<br />
** electrical AC^<br />
** electrical DC^<br />
* engine master switches<br />
* MFD (several pages)<br />
** active init<br />
** active departure and SID<br />
** active arrival and STAR<br />
** T.O. Performance<br />
** CRZ Performance^<br />
<br />
<br />
=== To Do ===<br />
* window and door cut-outs (to work with door system and lighting)<br />
* animate parking brake and speed brake<br />
* cabin interior<br />
* fine tune flap movements and slat droop<br />
* <del>tune LOC and G/S</del><br />
* flap/slat position on PFD<br />
* <del>livery refresh</del><br />
* <del>landing</del>, wing, tail and cabin lighting<br />
* <del>landing, wing, tail lighting switches</del><br />
* engine start sounds<br />
* complete PFD and EFIS selection switches<br />
* any modes of ND and EFIS selection switches<br />
* <del>complete MAP mode ND display</del><br />
* complete remaining ECAM pages (skeleton pages already in-place)<br />
* complete remaining MFD pages (too numerous to list)<br />
* <del>animation for air/cond overhead panel</del><br />
* <del>animation for elec overhead panel</del><br />
* complete fuel overhead panel<br />
* radio panels on pedestal<br />
* gear lever and indicators<br />
* thrust levers<br />
* auto-brake selector<br />
* standby instruments<br />
* <del>calculation of V speeds as part of FMS</del><br />
* air systems; cabin pressure and temperature <br />
* <del>complete DC and AC electrical system</del><br />
* <del>replace digit textures with text animation</del><br />
* fix up scaling of texture sizes<br />
<br />
<br />
^ = in recent Git development repository<br />
<br />
== External links ==<br />
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]<br />
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]<br />
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]<br />
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]<br />
<br />
{{Airbus}}<br />
<br />
[[Category:Aircraft]]<br />
[[Category:Aircraft TODO]]<br />
[[Category:Airliners]]<br />
[[Category:Civilian aircraft]]</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=27206A380 Tutorial2010-12-30T22:43:46Z<p>Scotth1: update some formatting</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br/><br />
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. <br />
<br />
One of the most complete free websites is [[http://www.navdata.at/ www.navdata.at]] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br/><br />
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/<br />
<br />
'''Scenery Tiles'''<br/><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages and Checklist display <br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# MCDU screens - for entering FMS flight plan and Performance data<br />
# MCDU Keyboard and num-pad<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake/Ground Spoilers lever<br />
<br />
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 FCU on the glareshield, the Flight Director, Auto Pilot and Auto Thrust should be illuminated.<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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 modes for Thrust, Vertical and Lateral modes are shown across the top line of the Primary Flight Display as ''Flight Mode Annunciators'' (FMA).<br />
<br />
'''Selected Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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, there should be no need to use the F11 Autopilot dialog window.<br />
<br />
<br />
'''Managed Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br/><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 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.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br/><br />
YSSY depart 16R<br/><br />
SID: KAMPI 1<br/><br />
GEROS <br/><br />
STAR: ARADI 2B<br/><br />
NZAA approach 05R<br/><br />
<br />
<br />
'''Starting FlightGear'''<br/><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
| ''terrasync'' || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
| fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
| atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
| airport || YSSY<br />
|-<br />
| parkpos || Intl057<br />
|-<br />
| timeofday || afternoon<br />
|-<br />
| prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
| aircraft || A380<br />
|-<br />
| enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklist ====<br />
The pre-flight checklist starts at the bottom left-hand corner of the overhead panel, moves up the left hand-side of the panel, then back down the middle of the panel, then across the glareshield panel, then straight down the front panel and then pedestal.<br />
* move your way up and check each section; WIPER, OXYGEN, F/CTL, ADIRS, HYD, FUEL, ELEC, AIR, ANTI-ICE, CAB PRESSURE (only ELEC, AIR and ANTI-ICE are currently functional)<br />
* most of the external lighting should be '''OFF''' except for the NAV lights which should already be '''ON'''<br />
* click the APU '''Master Sw''' ON<br />
* the '''APU''' ECAM page should be automatically displayed<br />
* check internal lighting (click ON '''STORM''' if you are flying at night)<br />
* click the '''NO-SMOKING''' switch to AUTO<br />
* 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.<br />
* click the Flight Director ('''FD''') ON<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all '''ENG MASTER''' switches are in the OFF position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the '''park-brake''' is ON (currently not animated, but displayed on E/W Display)<br />
This completes our pre-flight checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br/><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br/><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br/><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br/><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br/><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARADI2B''' <br />
# click on '''ACTIVE''' at the top of the page, this will take us back to the INIT page<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br/><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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 (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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying check Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the '''T.O.''' Tab on the T.O. Perf page on the MCDU<br />
# click to AUTO the '''SEAT BELT''' switch on the overhead internal lighting panel with left-mouse-button<br />
# Request external power disconnection from ground crew<br />
# Check all '''EXT''' AVAIL indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback'''<br />
# check all doors are closed<br />
# check '''thrust levers''' are at IDLE<br />
# click the '''BEACON''' to ON on the overhead external lighting panel<br />
# check '''parking brake''' ON (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# set '''ENGINE START''' to IGN START on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 20kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated<br />
# using the middle-mouse-button click '''ENGINE START''' to NORM on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night</div>Scotth1https://wiki.flightgear.org/w/index.php?title=File:A380-overhead-start_01.png&diff=27187File:A380-overhead-start 01.png2010-12-30T13:25:06Z<p>Scotth1: uploaded a new version of &quot;File:A380-overhead-start 01.png&quot;: Reverted to version as of 12:29, 30 December 2010</p>
<hr />
<div>order of switches on the overhead for Before Start, Engine Start procedure and After Start checklists.</div>Scotth1https://wiki.flightgear.org/w/index.php?title=File:A380-overhead-start_01.png&diff=27186File:A380-overhead-start 01.png2010-12-30T13:21:29Z<p>Scotth1: uploaded a new version of &quot;File:A380-overhead-start 01.png&quot;</p>
<hr />
<div>order of switches on the overhead for Before Start, Engine Start procedure and After Start checklists.</div>Scotth1https://wiki.flightgear.org/w/index.php?title=A380_Tutorial&diff=27185A380 Tutorial2010-12-30T13:20:26Z<p>Scotth1: up to after-start checklist done.</p>
<hr />
<div>''This is a draft working version of a tutorial to help understand how to fly the A380, and use Airbus Flight Guidance systems''<br />
<br />
= Flying the A380 =<br />
<br />
== Objectives ==<br />
This tutorial takes a 3 hour flight from Sydney (YSSY) to Auckland (NZAA) and will help;<br />
* Familiarise you with key cockpit controls<br />
* Provide guidance on weight control<br />
* Introduce features of the Airbus Flight Guidance controls<br />
* Introduce operation of Flight Management Systems<br />
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.<br />
<br />
== Before You Start ==<br />
'''FMS Database Files'''<br/><br />
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. <br />
<br />
One of the most complete free websites is [[http://www.navdata.at/ www.navdata.at]] from the front page of the site;<br />
* click on "SID/STAR" in the top navigation bar, <br />
* then click on "Download" from the left-hand menu,<br />
* select "Level-D 767" from the available addons drop-down list ('''note:''' this is different than "767PIC")<br />
* 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<br />
* save the ZIP file somewhere, we will un-zip it later.<br />
* select "NZAA - Auckland" from the stored airports drop-down list, again click on the folder icon to download and save somewhere you can remember.<br />
<br />
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.<br />
<br />
'''YSSY Models'''<br/><br />
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 scenery for YSSY, simply unpack either the tbz (for Linux and Mac users) or zip (for Windows users) file under <FG-Home>/data/<br />
<br />
'''Scenery Tiles'''<br/><br />
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.<br />
<br />
== Overview of Cockpit Components ==<br />
<br />
[[File:A380-cockpit-components 01.png|none|500px]]<br />
<br />
# Ignition start switch<br />
# APU Master start switch<br />
# External Lighting switches - includes strobe, landing, beacon etc<br />
# Internal Lighting switches - includes no smoking, seat belts and storm<br />
# Flight Control Unit (FCU) Panel - controls speed, heading, altitude and vertical speed<br />
# EFIS Panel - include barometric pressure, PFD data display and Nav Display range<br />
# Engine Display - displays N1, N2, EGT<br />
# Messages and Checklist display <br />
# Navigation Display (ND)<br />
# Primary Flight Display (PFD)<br />
# System Display (SD/ECAM)<br />
# MCDU screens - for entering FMS flight plan and Performance data<br />
# MCDU Keyboard and num-pad<br />
# Engine Master Switches<br />
# Radio Management Panel (RMP)<br />
# ECAM selection switches<br />
# Flaps lever<br />
# Speedbrake lever<br />
<br />
<br />
<br />
== Introduction to the FCU ==<br />
The Flight Control Unit is in the middle of the glareshield, it has controls for the Flight Guidance System to set; <br />
* speed, <br />
* heading, <br />
* altitude and <br />
* vertical speed. <br />
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 modes for Thrust, Vertical and Lateral are mapped to specific Flight Guidance Modes that are shown across the top line of the Primary Flight Display.<br />
<br />
'''Selected Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter<br />
! Specific Selected Modes<br />
|-<br />
| SPEED || SPEED, MACH<br />
|-<br />
| HEADING || HDG<br />
|-<br />
| ALTITUDE || ALT<br />
|-<br />
| Vertical Speed || V/S<br />
|}<br />
<br />
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.<br />
<br />
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, there should be no need to use the F11 Autopilot dialog window.<br />
<br />
<br />
'''Managed Mode'''<br/><br />
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;<br />
{|border="1"<br />
! Flight Parameter <br />
! Managed Mode name<br />
! Managed function<br />
|-<br />
| 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<br />
|-<br />
| HEADING || NAV, LOC || Follows waypoints in the autopilot flight plan or the localiser signal on NAV1 radio frequency during approach<br />
|-<br />
| 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<br />
|-<br />
|}<br />
<br />
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.<br />
<br />
<br />
= QFA231 =<br />
Scheduled flight Qantas 231 will depart Gate 57 from [[Sydney International Airport]] to Auckland International Airport with flight time of around 3 hours.<br />
<br />
== Pre-flight ==<br />
<br />
'''Fuel Estimates'''<br/><br />
Our fuel estimates for this flight are around 23 000kg for the 1 168 NM (which is less than 10% of the range of the aircraft) which is too light for this aircraft, so ensure you have between 50 000kg and 80 000kg.<br />
<br />
<br />
==== Flight Plan ====<br />
Cruise: FL350<br/><br />
YSSY depart 16R<br/><br />
SID: KAMPI 1<br/><br />
GEROS <br/><br />
STAR: ARADI 2B<br/><br />
NZAA approach 05R<br/><br />
<br />
<br />
'''Starting FlightGear'''<br/><br />
Start FlightGear with the following options;<br />
{|border="1"<br />
!Option<br />
!Value<br />
|-<br />
|terrasync || enabled with atlas protocol and scenery directory pointing to both default scenery and terrasync directories (see below)<br />
|-<br />
|fg-scenery || $FG_ROOT/data/Scenery:<terrasync-scenery-dir><br />
|-<br />
|atlas || socket,out,1,localhost,5500 udp<br />
|-<br />
|airport || YSSY<br />
|-<br />
|parkpos || Intl057<br />
|-<br />
|timeofday || afternoon<br />
|-<br />
|prop:sim/paths/use-custom-scenery-data || false (only required for FlightGear versions after 2.0.0)<br />
|-<br />
|aircraft || A380<br />
|-<br />
|enable-real-weather-fetch ||<br />
|}<br />
<br />
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.<br />
<br />
==== Fuelling and Weight ====<br />
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''.<br />
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 30% as we burn and transfer fuel)<br />
* Firstly adjust fuel tanks 0 and 3 down to around 9500 lbs<br />
* adjust fuel tanks 4 and 5 to around 9500 lbs<br />
* adjust fuel tanks 6 and 7 to around 9200 lbs<br />
* adjust fuel tanks 8 and 9 to around 7500 lbs<br />
* check GWCG if it is above 36% then<br />
*# add fuel to trim tank number 10 and,<br />
*# add cargo to the bulk and aft cargo areas<br />
* if it is less than 32% then;<br />
*# reduce fuel in the trim tank 10 and,<br />
*# add cargo to the forward cargo area and,<br />
*# reduce cargo from bulk and aft cargo area<br />
So for this short flight aim to have Fuel-On-Board around 60 000 kilograms and as close to 32-33% Centre-of-Gravity<br />
<br />
==== Pre-flight Checklist ====<br />
The pre-flight checklist starts at the bottom left-hand corner of the overhead panel, moves up the left hand-side of the panel, then back down the middle of the panel, then across the glareshield panel, then straight down the front panel and then pedestal.<br />
* move your way up and check each section; WIPER, OXYGEN, F/CTL, ADIRS, HYD, FUEL, ELEC, AIR, ANTI-ICE, CAB PRESSURE (only ELEC, AIR and ANTI-ICE are currently functional)<br />
* most of the external lighting should be '''OFF''' except for the NAV lights which should already be '''ON'''<br />
* click the APU Master Sw '''ON'''<br />
* the '''APU''' ECAM page should be automatically displayed<br />
* check internal lighting (click on '''STORM''' if you are flying at night)<br />
* click the NO-SMOKING switch to '''AUTO'''<br />
* 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 ring 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.<br />
* click the Flight Director (FD) '''ON'''<br />
* moving down the front panel, check the lower message section of the E/WD <br />
* check standby instruments, autobrake is set to '''RTO''' and gear lever is down (not currently modelled)<br />
* 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<br />
* ensure all engine master switches are in the '''OFF''' position<br />
* 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<br />
* check flaps lever is fully retracted at '''0''' and speed-brake/spoilers are retracted <br />
* lastly check the park-brake is '''ON''' (currently not animated, but displayed on E/W Display)<br />
This completes our pre-flight checklist, if you are at a ATC controlled airport you would normally request departure information at this point.<br />
<br />
==== Entering Flight Plan ====<br />
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.<br />
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)<br />
<br />
'''ACTIVE INIT page'''<br/><br />
[[File:A380-FMS_01.png|none|450px]]<br />
# First click inside ''FLT NBR'' field, then set the Flight Number to '''QFA231'''<br />
# click inside the ''TO'' field and enter our destination airport '''NZAA'''<br />
# next click inside the ''CRZ FL'' field and enter our cruise flight level of '''350'''<br />
# click on the '''DEPARTURES''' option on the MCDU page, this will take you to the next page.<br />
<br />
<br />
'''ACTIVE DEPARTURE page'''<br/><br />
[[File:A380-FMS_02.png|none|450px]]<br />
# click on '''16R''' from the list of runways<br />
# now click on '''SID''' to go to the next page<br />
<br />
<br />
'''ACTIVE DEPARTURE SID page'''<br/><br />
# click on '''KAMPI1''', as there are no transition points for this SID, you will now go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVAL page'''<br/><br />
# click on '''05R''' from the list of runways<br />
# now click on '''STAR''' to go to the next page<br />
<br />
<br />
'''ACTIVE ARRIVE STAR page'''<br/><br />
[[File:A380-FMS_03.png|none|450px]]<br />
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.<br />
# click on '''ARADI2B''' <br />
# click on '''ACTIVE''' at the top of the page, this will take us back to the INIT page<br />
<br />
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)<br />
# From the top menu click on ''Autopilot'' > ''Route Manager''<br />
# click on the line for "KAMPI"<br />
# then click inside the orange input field and enter 'GEROS@35000' and click the '''Add''' button<br />
# review the full flight plan, notice the Top-of-Descent pseudo-waypoint has been added<br />
<br />
'''T.O. PERF page'''<br/><br />
Finally we set and review the takeoff performance data, from the INIT page;<br />
# click on '''T.O. PERF'''<br />
# note the V1 balanced field speed and the Vr rotate speed (Vr and V2 are calculated based on weight, pressure, altitude and temperature)<br />
# for heavier loads, you should increase the '''THR RED'' altitude to 1400ft or 1500 ft<br />
# 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.<br />
<br />
Not modelled in the current release, but in future releases; by clicking on the '''CLB''' tab would allow you review CLB parameters.<br />
<br />
Now is a good time to review your flight plan, from the top menu select ''Equipment'' > ''Map''.<br />
<br />
== Start-up ==<br />
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 (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. <br />
<br />
==== Before Start checklist ====<br />
# Pilot Flying check Takeoff Data, Pilot Not Flying should cross-check takeoff data<br />
# Pilot flying should select the T.O. Perf ('''T.O.''') page on the MCDU<br />
# click to '''AUTO''' the SEAT BELT switch on the overhead internal lighting panel with left-mouse-button<br />
# Request external power disconnection from ground crew<br />
# Check all EXT '''AVAIL''' indicators on overhead electrical panel are '''not''' illuminated<br />
# Obtain clearance for '''startup and pushback'''<br />
# check all doors are closed<br />
# check thrust levers are at '''IDLE'''<br />
# click the BEACON to '''ON''' on the overhead external lighting panel<br />
# check parking brake '''ON''' (not currently animated, but status displayed on E/W Display)<br />
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.<br />
<br />
[[File:A380-overhead-start_01.png|none|450px]]<br />
Items 1, 2, 3 and the NAV and BEACON of 5 should be ON or AUTO by now.<br />
<br />
==== Automatic Startup Procedure ====<br />
# set ENGINE START to '''IGN START''' on the overhead panel<br />
# announce "Starting Engine 2 and 3" to ground crew<br />
# click ON '''ENG MASTER 2''' with your left-mouse-button<br />
# the '''ENGINE''' ECAM page should automatically be displayed<br />
# once N2 has reached 10%, click ON '''ENG MASTER 3'''<br />
# both pilots should monitor the ECAM page and E/W Display as N1 and N2 increase and Oil pressure increases<br />
# once N2 for '''ENGINE 3''' has reached 25%;<br />
#* announce "Starting engine 1 and 4" to ground crew<br />
#* click ON '''ENG MASTER 1''' and repeat steps 3 - 6 above for engines 1 and 4<br />
# check engine idle parameters are normal (N1 = 20%, N2 = 60%, Fuel Flow = 20kg/h, EGT = 380C - 390C)<br />
<br />
With the engines running at idle, the startup procedure is complete, continue to the 'After Start Checklist'<br />
<br />
==== After Start checklist ====<br />
# ensure the '''APU BLEED''' on the overhead AIR panel is no longer illuminated<br />
# using the right-mouse-button click ENGINE START to '''NORM''' on the overhead panel<br />
# check '''GND SPLRS''' are armed, RUD TRIM is reset<br />
# set the '''FLAPS''' to 2<br />
# set WING and ENGINE '''ANTI-ICE''' as required on the overhead panel (check E/W Display for "ANTI ICE CHECK" memo)<br />
# click OFF '''APU MASTER''' Sw using left-mouse-button<br />
# announce "Clear to Disconnect" to ground crew<br />
<br />
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.<br />
Request taxi instructions from Ground ATC.<br />
Once the ground crew are cleared and you have taxi instructions;<br />
# click to TAXI the '''NOSE''' sw on the overhead external lighting panel with left-mouse-button<br />
# click to ON '''WING''' on the overhead external lighting panel<br />
# click to AUTO '''LOGO''' on the overhead external lighting panel if flying at night</div>Scotth1https://wiki.flightgear.org/w/index.php?title=File:A380-overhead-start_01.png&diff=27184File:A380-overhead-start 01.png2010-12-30T12:29:56Z<p>Scotth1: order of switches on the overhead for Before Start, Engine Start procedure and After Start checklists.</p>
<hr />
<div>order of switches on the overhead for Before Start, Engine Start procedure and After Start checklists.</div>Scotth1