https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=Gsagostinho&feedformat=atomFlightGear wiki - User contributions [en]2024-03-29T08:38:33ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=Cessna_172P/info&diff=116344Cessna 172P/info2018-10-09T00:38:13Z<p>Gsagostinho: </p>
<hr />
<div><includeonly>{{infobox aircraft<br />
| name = Cessna 172P Skyhawk<br />
| hangar = fgdata<br />
| image = c172p-preview2.jpg<br />
| image2 = c172p-panel-landing.jpg<br />
| type = Civil aircraft/Civil utility aircraft<br />
| config = High wing aircraft/Fixed gear aircraft<br />
| propulsion = Propeller aircraft/Single-engine aircraft<br />
| manufacturer = Cessna<br />
| authors = David Megginson/Gilberto Agostinho/Wayne Bragg/Juan Vera del Campo/onox/Fernando Barbosa/Daniel Dubreuil/Jonathan Schellhase/Israel Hernandez/Tuomas Kuosmanen/Anders Gidenstam/Waldo Kitty/algefaen<br />
| fdm = JSBSim<br />
| fgname = c172p<br />
| status-fdm = 5<br />
| status-systems = 5<br />
| status-cockpit = 5<br />
| status-model = 5<br />
| ready = tutorials/checklist<br />
| devel-repo = {{github url|user=c172p-team|repo=c172p}}<br />
| download = {{github zip file|user=c172p-team|repo=c172p|full=1}}<br />
| liverydbid = 70<br />
| forumtid = 25157<br />
| note = {{LangSwitch<br />
| ar = هذه هيا طائرة فلايت جير الإفتراضية ويتم توزيعها كجزء من حزمة البرنامج<br />
| ca = Aquest és l'avió predeterminat de FlightGear i es distribueix com a part del paquet base.<br />
| en = This is the default FlightGear aircraft and is distributed as part of the base package.<br />
| de = Dies ist das FlightGear Standardflugzeug und im Basispaket der Software enthalten.<br />
| es = Este es el avión predeterminado de FlightGear y se distribuye como parte de la descarga de FlightGear. <br />
| it = Questo è l'aeromobile predefinito di FlightGear ed è distribuito come parte del pacchetto di base.<br />
| ru = Этот самолёт является летательным аппаратом по умолчанию в FlightGear и распространяется, как часть базового пакета.<br />
| zh = 这是FlightGear的默认机型,并被包括在FlightGear主程序中。<br />
}}<br />
| navbar = 1<br />
}}</includeonly><noinclude><br />
This is the aircraft infobox subpage of the [[Cessna 172P]].<br />
[[Category:Aircraft infobox documentation]]<br />
</noinclude></div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P/info&diff=116343Cessna 172P/info2018-10-09T00:36:40Z<p>Gsagostinho: </p>
<hr />
<div><includeonly>{{infobox aircraft<br />
| name = Cessna 172P Skyhawk<br />
| hangar = fgdata<br />
| image = c172p-preview2.jpg<br />
| image2 = c172p-panel-landing.jpg<br />
| type = Civil aircraft/Civil utility aircraft<br />
| config = High wing aircraft/Fixed gear aircraft<br />
| propulsion = Propeller aircraft/Single-engine aircraft<br />
| manufacturer = Cessna<br />
| authors = David Megginson/Gilberto Agostinho/Wayne Bragg/Juan Vera del Campo/onox/Fernando Barbosa/Daniel Dubreuil/Jonathan Schellhase/Israel Hernandez/Tuomas Kuosmanen/Anders Gidenstam/Waldo Kitty/algefaen<br />
| fdm = JSBSim<br />
| fgname = c172p<br />
| status-fdm = 5<br />
| status-systems = 5<br />
| status-cockpit = 5<br />
| status-model = 5<br />
| ready = tutorials/checklist<br />
| devel-repo = {{github url|user=Juanvvc|repo=c172p-detailed}}<br />
| download = {{github zip file|user=Juanvvc|repo=c172p-detailed|full=1}}<br />
| liverydbid = 70<br />
| forumtid = 25157<br />
| note = {{LangSwitch<br />
| ar = هذه هيا طائرة فلايت جير الإفتراضية ويتم توزيعها كجزء من حزمة البرنامج<br />
| ca = Aquest és l'avió predeterminat de FlightGear i es distribueix com a part del paquet base.<br />
| en = This is the default FlightGear aircraft and is distributed as part of the base package.<br />
| de = Dies ist das FlightGear Standardflugzeug und im Basispaket der Software enthalten.<br />
| es = Este es el avión predeterminado de FlightGear y se distribuye como parte de la descarga de FlightGear. <br />
| it = Questo è l'aeromobile predefinito di FlightGear ed è distribuito come parte del pacchetto di base.<br />
| ru = Этот самолёт является летательным аппаратом по умолчанию в FlightGear и распространяется, как часть базового пакета.<br />
| zh = 这是FlightGear的默认机型,并被包括在FlightGear主程序中。<br />
}}<br />
| navbar = 1<br />
}}</includeonly><noinclude><br />
This is the aircraft infobox subpage of the [[Cessna 172P]].<br />
[[Category:Aircraft infobox documentation]]<br />
</noinclude></div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=116319Cessna 172P2018-10-07T22:42:02Z<p>Gsagostinho: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
The Cessna 172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:c172p-preview5.jpg|center|700px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 36" bush tires<br />
* pontoons<br />
* amphibious<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialogue).<br />
<br />
Carburettor icing is also modelled. Accumulating carburettor ice will result in loss of power. Applying carb heat will help to melt it. If the engine starts to cough when carb heat is applied, it means that ice has indeed been accumulated in the carburettor and now is being melted. To reduce a cough during the melting process, one can lean the mixture. <br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialogue. These include cones under the wings, a fuel truck, a ground power unit and ladders. The ground power can be used to recharge the battery and the fuel truck can be used to refuelling the tanks. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-panel-lighting.jpg|700px|center|Cessna 172P cockpit at night]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:c172p-ground-objects.jpg|300px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
[[File:c172p-panel-closeup.jpg|300px||thumb|Cessna 172P before starting the engine]]<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-preview0.jpg|300px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-preview4.jpg|300px||thumb|Cessna 172P about to touch down]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you are experiencing grey windows, you do not have the minimum FlightGear version to run this aircraft. Consider upgrading your Flight Gear version.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why doesn't the aircraft move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-preview5.jpg|Cessna 172P high over Italy<br />
c172p-preview7.jpg|PT-IAO on a soft dirt runway <br />
c172p-preview0.jpg|Panel view, about to take off<br />
c172p-preview2.jpg|Parked and secured <br />
c172p-preview13.jpg|Night lighting effects<br />
c172p-preview1.jpg|Float variant taking off<br />
c172p-preview3.jpg|Ski variant over Freiburg<br />
c172p-preview4.jpg|About to land at Aosta Airport<br />
c172p-panel-closeup.jpg|Panel close-up<br />
c172p-preview6.jpg|Hazy day over Naples<br />
c172p-preview8.jpg|Sightseeing at Chapada Diamantina<br />
c172p-preview9.jpg|Bush take off<br />
c172p-preview12.jpg|Night flight with dimmed post lights<br />
c172p-panel-lighting.jpg|Full post lighting<br />
c172p-preview10.jpg|Amphibian variant at Hawaii<br />
c172p-preview11.jpg|Bush variant<br />
c172p-panel-landing.jpg|About to land<br />
c172p-ground-objects.jpg|PT-IAO with ground objects<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-parked.jpg|N35799 livery parked at Camden Airport (YSCN)<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
</gallery><br />
<br />
== External links ==<br />
* {{Wikipedia|Cessna 172|lang=en}}<br />
* [http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf Cessna 172 checklist at aerodynamicaviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[ar:Cessna 172P]]<br />
[[ca:Cessna 172P]]<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[nl:Cessna 172P]]<br />
[[ru:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=116318Cessna 172P2018-10-07T22:20:37Z<p>Gsagostinho: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
The Cessna 172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:c172p-preview5.jpg|center|700px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 36" bush tires<br />
* pontoons<br />
* amphibious<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialogue).<br />
<br />
Carburettor icing is also modelled. Accumulating carburettor ice will result in loss of power. Applying carb heat will help to melt it. If the engine starts to cough when carb heat is applied, it means that ice has indeed been accumulated in the carburettor and now is being melted. To reduce a cough during the melting process, one can lean the mixture. <br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialogue. These include cones under the wings, a fuel truck, a ground power unit and ladders. The ground power can be used to recharge the battery and the fuel truck can be used to refuelling the tanks. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-panel-lighting.jpg|700px|center|Cessna 172P cockpit at night]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:c172p-ground-objects.jpg|300px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
[[File:c172p-panel-closeup.jpg|300px||thumb|Cessna 172P before starting the engine]]<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-preview0.jpg|300px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-panel-landing.jpg|300px||thumb|Cessna 172P about to touch down]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you are experiencing grey windows, you do not have the minimum FlightGear version to run this aircraft. Consider upgrading your Flight Gear version.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why doesn't the aircraft move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
c172p-equipment.jpg|All equipment; external power unit, fuel tank, ladder, wing safety cones, wheel chocks, pitot tube cover & tie-downs<br />
c172p-bush.jpg|Cessna 172P with 36" bush tires<br />
c172p-parked.jpg|N35799 livery parked at Camden Airport (YSCN)<br />
c172p-cover.jpg|Cessna 172P with pitot tube cover and nose wheel chock placed<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* {{Wikipedia|Cessna 172|lang=en}}<br />
* [http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf Cessna 172 checklist at aerodynamicaviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[ar:Cessna 172P]]<br />
[[ca:Cessna 172P]]<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[nl:Cessna 172P]]<br />
[[ru:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=116317Cessna 172P2018-10-07T22:18:55Z<p>Gsagostinho: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
The Cessna 172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:c172p-preview5.jpg|center|700px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 36" bush tires<br />
* pontoons<br />
* amphibious<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialogue).<br />
<br />
Carburettor icing is also modelled. Accumulating carburettor ice will result in loss of power. Applying carb heat will help to melt it. If the engine starts to cough when carb heat is applied, it means that ice has indeed been accumulated in the carburettor and now is being melted. To reduce a cough during the melting process, one can lean the mixture. <br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialogue. These include cones under the wings, a fuel truck, a ground power unit and ladders. The ground power can be used to recharge the battery and the fuel truck can be used to refuelling the tanks. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-panel-lighting.jpg|700px|center|Cessna 172P cockpit at night]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:c172p-ground-objects.jpg|300px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-preview0.jpg|300px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-panel-landing.jpg|300px||thumb|Cessna 172P about to touch down]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you are experiencing grey windows, you do not have the minimum FlightGear version to run this aircraft. Consider upgrading your Flight Gear version.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why doesn't the aircraft move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
c172p-equipment.jpg|All equipment; external power unit, fuel tank, ladder, wing safety cones, wheel chocks, pitot tube cover & tie-downs<br />
c172p-bush.jpg|Cessna 172P with 36" bush tires<br />
c172p-parked.jpg|N35799 livery parked at Camden Airport (YSCN)<br />
c172p-cover.jpg|Cessna 172P with pitot tube cover and nose wheel chock placed<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* {{Wikipedia|Cessna 172|lang=en}}<br />
* [http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf Cessna 172 checklist at aerodynamicaviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[ar:Cessna 172P]]<br />
[[ca:Cessna 172P]]<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[nl:Cessna 172P]]<br />
[[ru:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=116316Cessna 172P2018-10-07T22:16:05Z<p>Gsagostinho: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
The Cessna 172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:c172p-preview5.jpg|center|800px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 36" bush tires<br />
* pontoons<br />
* amphibious<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialogue).<br />
<br />
Carburettor icing is also modelled. Accumulating carburettor ice will result in loss of power. Applying carb heat will help to melt it. If the engine starts to cough when carb heat is applied, it means that ice has indeed been accumulated in the carburettor and now is being melted. To reduce a cough during the melting process, one can lean the mixture. <br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialogue. These include cones under the wings, a fuel truck, a ground power unit and ladders. The ground power can be used to recharge the battery and the fuel truck can be used to refuelling the tanks. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-panel-lighting.jpg|500px|center|Cessna 172P cockpit at night]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touch down]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you are experiencing grey windows, you do not have the minimum FlightGear version to run this aircraft. Consider upgrading your Flight Gear version.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why doesn't the aircraft move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
c172p-equipment.jpg|All equipment; external power unit, fuel tank, ladder, wing safety cones, wheel chocks, pitot tube cover & tie-downs<br />
c172p-bush.jpg|Cessna 172P with 36" bush tires<br />
c172p-parked.jpg|N35799 livery parked at Camden Airport (YSCN)<br />
c172p-cover.jpg|Cessna 172P with pitot tube cover and nose wheel chock placed<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* {{Wikipedia|Cessna 172|lang=en}}<br />
* [http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf Cessna 172 checklist at aerodynamicaviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[ar:Cessna 172P]]<br />
[[ca:Cessna 172P]]<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[nl:Cessna 172P]]<br />
[[ru:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P/info&diff=116315Cessna 172P/info2018-10-07T22:12:25Z<p>Gsagostinho: </p>
<hr />
<div><includeonly>{{infobox aircraft<br />
| name = Cessna 172P Skyhawk<br />
| hangar = fgdata<br />
| image = c172p-preview2.jpg<br />
| image2 = c172p-panel-landing.jpg<br />
| type = Civil aircraft/Civil utility aircraft<br />
| config = High wing aircraft/Fixed gear aircraft<br />
| propulsion = Propeller aircraft/Single-engine aircraft<br />
| manufacturer = Cessna<br />
| authors = David Megginson/Gilberto Agostinho/Wayne Bragg/Juan Vera del Campo/onox/Fernando Barbosa/Daniel Dubreuil/Jonathan Schellhase/Israel Hernandez/Tuomas Kuosmanen/Anders Gidenstam/Waldo Kitty/algefaen<br />
| fdm = JSBSim<br />
| fgname = c172p<br />
| status-fdm = 4<br />
| status-systems = 5<br />
| status-cockpit = 5<br />
| status-model = 4<br />
| ready = tutorials/checklist<br />
| devel-repo = {{github url|user=Juanvvc|repo=c172p-detailed}}<br />
| download = {{github zip file|user=Juanvvc|repo=c172p-detailed|full=1}}<br />
| liverydbid = 70<br />
| forumtid = 25157<br />
| note = {{LangSwitch<br />
| ar = هذه هيا طائرة فلايت جير الإفتراضية ويتم توزيعها كجزء من حزمة البرنامج<br />
| ca = Aquest és l'avió predeterminat de FlightGear i es distribueix com a part del paquet base.<br />
| en = This is the default FlightGear aircraft and is distributed as part of the base package.<br />
| de = Dies ist das FlightGear Standardflugzeug und im Basispaket der Software enthalten.<br />
| es = Este es el avión predeterminado de FlightGear y se distribuye como parte de la descarga de FlightGear. <br />
| it = Questo è l'aeromobile predefinito di FlightGear ed è distribuito come parte del pacchetto di base.<br />
| ru = Этот самолёт является летательным аппаратом по умолчанию в FlightGear и распространяется, как часть базового пакета.<br />
| zh = 这是FlightGear的默认机型,并被包括在FlightGear主程序中。<br />
}}<br />
| navbar = 1<br />
}}</includeonly><noinclude><br />
This is the aircraft infobox subpage of the [[Cessna 172P]].<br />
[[Category:Aircraft infobox documentation]]<br />
</noinclude></div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview13.jpg&diff=116314File:C172p-preview13.jpg2018-10-07T22:03:25Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview11.jpg&diff=116313File:C172p-preview11.jpg2018-10-07T22:03:25Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview12.jpg&diff=116312File:C172p-preview12.jpg2018-10-07T22:03:25Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview10.jpg&diff=116311File:C172p-preview10.jpg2018-10-07T22:03:25Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview9.jpg&diff=116310File:C172p-preview9.jpg2018-10-07T22:03:24Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview8.jpg&diff=116309File:C172p-preview8.jpg2018-10-07T22:03:24Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview5.jpg&diff=116308File:C172p-preview5.jpg2018-10-07T22:03:24Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview7.jpg&diff=116307File:C172p-preview7.jpg2018-10-07T22:03:23Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview6.jpg&diff=116306File:C172p-preview6.jpg2018-10-07T22:03:23Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview4.jpg&diff=116305File:C172p-preview4.jpg2018-10-07T22:03:23Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview3.jpg&diff=116304File:C172p-preview3.jpg2018-10-07T22:03:23Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview2.jpg&diff=116303File:C172p-preview2.jpg2018-10-07T22:03:22Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview0.jpg&diff=116302File:C172p-preview0.jpg2018-10-07T22:03:22Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-preview1.jpg&diff=116301File:C172p-preview1.jpg2018-10-07T22:03:22Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-panel-lighting.jpg&diff=116300File:C172p-panel-lighting.jpg2018-10-07T22:03:22Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-panel-landing.jpg&diff=116299File:C172p-panel-landing.jpg2018-10-07T22:03:21Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-panel-closeup.jpg&diff=116298File:C172p-panel-closeup.jpg2018-10-07T22:03:21Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C172p-ground-objects.jpg&diff=116297File:C172p-ground-objects.jpg2018-10-07T22:03:21Z<p>Gsagostinho: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Screenshot of the [[Cessna 172P]]}}<br />
|date=2018-10-07<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 172 screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=116296Cessna 172P2018-10-07T20:36:32Z<p>Gsagostinho: improved wording</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
The Cessna 172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:C172p-bodensee-panorama.jpg|center|800px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 36" bush tires<br />
* pontoons<br />
* amphibious<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialogue).<br />
<br />
Carburettor icing is also modelled. Accumulating carburettor ice will result in loss of power. Applying carb heat will help to melt it. If the engine starts to cough when carb heat is applied, it means that ice has indeed been accumulated in the carburettor and now is being melted. To reduce a cough during the melting process, one can lean the mixture. <br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialogue. These include cones under the wings, a fuel truck, a ground power unit and ladders. The ground power can be used to recharge the battery and the fuel truck can be used to refuelling the tanks. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-ALS-flashlight2.jpg|500px|center|Cessna 172P's flashlight in the cockpit]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touch down]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you are experiencing grey windows, you do not have the minimum FlightGear version to run this aircraft. Consider upgrading your Flight Gear version.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why doesn't the aircraft move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
c172p-equipment.jpg|All equipment; external power unit, fuel tank, ladder, wing safety cones, wheel chocks, pitot tube cover & tie-downs<br />
c172p-bush.jpg|Cessna 172P with 36" bush tires<br />
c172p-parked.jpg|N35799 livery parked at Camden Airport (YSCN)<br />
c172p-cover.jpg|Cessna 172P with pitot tube cover and nose wheel chock placed<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* {{Wikipedia|Cessna 172|lang=en}}<br />
* [http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf Cessna 172 checklist at aerodynamicaviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[ar:Cessna 172P]]<br />
[[ca:Cessna 172P]]<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[nl:Cessna 172P]]<br />
[[ru:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=106928Cessna 172P2017-02-12T12:04:48Z<p>Gsagostinho: /* Features */</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
A C172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:C172p-bodensee-panorama.jpg|center|800px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 31" bush tires<br />
* pontoons<br />
* amphibian<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialog).<br />
<br />
Carburettor icing is also modelled. Accumulating carburettor ice will result in loss of power. Applying carb heat will help to melt it. If the engine starts to cough when carb heat is applied, it means that ice has indeed been accumulated in the carburettor and now is being melt. To reduce the cough during the melting process, one can lean the mixture. <br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialog. These include cones under the wings, a fuel truck, a ground power unit and ladders. The ground power can be used to recharge the battery and the fuel truck can be used to refuelling the tanks. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-ALS-flashlight2.jpg|500px|center|Cessna 172P's flashlight in the cockpit]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touchdown]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you experience grey windows, you do not have the correct FlightGear version. This aircraft requires 3.5 or above.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why the aircraft doesn't move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]<br />
* [http://www.atlasaviation.com/checklists/cessna-172/cessna_172_checklist.htm Cessna 172 checklists at AtlasAviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=106927Cessna 172P2017-02-12T12:00:41Z<p>Gsagostinho: /* FAQ */</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
A C172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:C172p-bodensee-panorama.jpg|center|800px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 31" bush tires<br />
* pontoons<br />
* amphibian<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialog).<br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialog. These include cones under the wings, a fuel truck, a ground power unit and ladders. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-ALS-flashlight2.jpg|500px|center|Cessna 172P's flashlight in the cockpit]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touchdown]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you experience grey windows, you do not have the correct FlightGear version. This aircraft requires 3.5 or above.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why the aircraft doesn't move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]<br />
* [http://www.atlasaviation.com/checklists/cessna-172/cessna_172_checklist.htm Cessna 172 checklists at AtlasAviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Input_device&diff=105869Input device2016-11-14T12:09:03Z<p>Gsagostinho: /* Joystick or yoke? */ adding gliders to table, explaining the table</p>
<hr />
<div>Could you imagine a pilot in his or her [[:Category:Cessna|Cessna]] controlling the machine with a keyboard alone? For getting the proper feeling of flight you will need a '''joystick/yoke''' plus [[rudder]] pedals, right? <br />
<br />
FlightGear has integrated joystick support, which automatically detects any joystick, yoke, or pedals attached. Just try it! If this does work for you, lean back and be happy! You can see what FlightGear has detected your joystick as in the Help > Joystick Configuration dialog from the [[menu]]. <br />
<br />
Unfortunately, for the above mentioned versatility, chances are your joystick does not work out of the box. This article explains you how to make FlightGear recognise your device<br />
<br />
== Joystick or yoke? ==<br />
{| cellpadding="4" cellspacing="0" align="right" style="clear:right; background:#fafafa; font-size: 85%; border: 1px solid #CCCCCC;" <br />
|-<br />
| [[File:CH Products Fighterstick USB.jpg|x199px|CH Products Fighterstick USB]]<br />
| [[File:Saitek Pro Flight Cessna Yoke front.jpg|300px|Saitek Pro Flight Cessna Yoke]]<br />
|-<br />
| CH Products Fighterstick USB<br />
| Saitek Pro Flight Cessna Yoke<br />
|}<br />
The two most common control devices on aircraft are the joystick (left picture) and yoke (right picture). Joysticks can be found on military fighters, helicopters and Airbus [[airliner]]s, while yokes are used on almost all other fixed wing aircraft, including Boeing airliners.<br />
<br />
Joysticks are generally a lot cheaper, starting at $10. Yokes start at $100. When you are new to flightsimming, buying a cheap (ca. $20) joystick might be a good way to find out if it's something for you.<br />
<br />
The following table should help you decide which one is best suited for you:<br />
{| class="wikitable"<br />
!<br />
! Joystick<br />
! Yoke<br />
|-<br />
! style="text-align:left;" | Price<br />
| $10+<br />
| $100+<br />
|-<br />
! style="text-align:left;" | General aviation<br />
| {{no}}<br />
| {{yes}}<br />
|-<br />
! style="text-align:left;" | Gliders<br />
| {{yes}}<br />
| {{no}}<br />
|-<br />
! style="text-align:left;" | Helicopter<br />
| {{yes}}<br />
| {{no}}<br />
|-<br />
! style="text-align:left;" | Fighters<br />
| {{yes}}<br />
| {{no}}<br />
|-<br />
! style="text-align:left;" | Most airliners including Boeing<br />
| {{no}}<br />
| {{yes}}<br />
|-<br />
! style="text-align:left;" | Airbus<br />
| {{yes}}<br />
| {{no}}<br />
|}<br />
<br />
It should be noted that any type of input device (be it a joystick, a yoke or even a gamepad) will work with '''all''' aircraft in FlightGear and that the table above only suggests which ones are more suited to specific types of aircraft given how they are flown in real life.<br />
<br />
Some reviews of flight simulation hardware can be found in [[:Category:Hardware reviews]].<br />
<br />
== Built-in joystick support ==<br />
In order for joystick auto-detection to work, a joystick bindings xml file must exist for each joystick. This file describes what axes and buttons are to be used to control which functions in FlightGear. The associations between functions and axes or buttons are called "bindings".<br />
<br />
FlightGear includes a large number of such bindings files for a variety of manufacturers. Chances are high that your joystick will be recognised straight away, so let's try that first. You can confirm whether it was recognised by looking in the <tt>Help > Joystick Configuration</tt> dialog. "Used for" should contain a name/description of your joystick. It will contain "default" when FlightGear did not recognise your joystick.<br />
<br />
Most of the time when your joystick is not recognised, it is because of a missing name definition in the respective bindings file. Because FlightGear is used on all kind of operating systems, names vary a lot. You can find the files under <tt>[[$FG_ROOT]]/Input/Joysticks/</tt> (despite the name, yokes and pedals are also found here!). For example, if you have a CH Products joystick, look in the folder <tt>[[$FG_ROOT]]/Input/Joysticks/CH</tt> for a file that might work for your joystick. When such a file exists, do the following:<br />
# Launch FlightGear with the joystick connected.<br />
# Look under Help > Joystick Configuration and check the name behind "Joystick #0:". <br />
# Open your joystick's bindings file in a XML editor and add the following code to the file, below the already-present <code><name></code> tags.<br />
# <syntaxhighlight lang="xml"><name>The EXACT name you found under step 2; including spaces, capitals etc.</name></syntaxhighlight><br />
# Please report this name [http://forum.flightgear.org/viewforum.php?f=24 at our forum], so it can be added to the official file (and next releases).<br />
<br />
Please note that the latest config files are always to be found at {{fgdata file|Input/Joysticks}}. This link may contain additional binding files that were not included in the latest stable release.<br />
<br />
If there is no file for your joystick, you will have to create such a file. We will discuss that in [[Joystick#Writing or editing joystick binding xml files|a later section]], by cutting and pasting bindings from the examples that are included with FlightGear.<br />
<br />
=== Multiple devices on Windows ===<br />
In case you have two USB devices (for instance a yoke plus pedals) to a Windows computer, there may be cases, where the same driver name is reported twice. In this case, you can get at least the yoke to work by assigning it number 0 (out of 0 and 1), by adding a line to <tt>[[$FG_ROOT]]/joystick.xml</tt> like:<br />
<syntaxhighlight lang="xml"><js n="0" include="Input/Joysticks/Saitek/ST290-Pro.xml"/></syntaxhighlight><br />
if you also have pedals (or another joystick), just add more lines, similar to:<br />
<syntaxhighlight lang="xml"><js n="1" include="Input/Joysticks/Saitek/Pro-Flight-Rudder-Pedals.xml"/></syntaxhighlight><br />
<br />
To make sure that the first input device is indeed the yoke, rotate the yoke ([[aileron]] control) and observe the Help > Joystick Configuration dialog. If the aileron value does not change, you have to make the yoke the preferred device first. For doing so, enter the Windows "Control panel", open "Game controllers" and select the "Advanced" button. Here you can select the yoke as the "Preferred" device. Afterwards you can check that assignment by restarting FlightGear. The yoke should now control the aileron.<br />
<br />
== Adding support for your joystick ==<br />
=== Verifying your joystick is working ===<br />
==== Linux ====<br />
Reboot your system and immediately enter on the [[command line]] <br />
<br />
<syntaxhighlight lang="bash"><br />
dmesg | grep Joystick <br />
</syntaxhighlight><br />
<br />
which pipes the boot message to grep which then prints every line in the boot message that contains the string “Joystick”. When you do this with a Saitek joystick attached, you will see a line similar to this one: <br />
<br />
<syntaxhighlight><br />
input0: USB HID v1.00 Joystick [SAITEK CYBORG 3D USB] on usb2:3.0 <br />
</syntaxhighlight><br />
<br />
This line tells us that a joystick has identified itself as SAITEK CYBORG 3D USB to the operating system. It does not tell us that the joystick driver sees your joystick. You can verify that the joystick driver sees the joystick by entering:<br />
<br />
<syntaxhighlight><br />
js_demo <br />
</syntaxhighlight><br />
<br />
If your joystick is not recognized by the driver, you may have to manually load the joystick device module with the command:<br />
<br />
<syntaxhighlight><br />
modprobe joydev<br />
</syntaxhighlight><br />
<br />
==== Windows ====<br />
Go to <tt>Start > Control Panel > Game Controller</tt> and see whether the dialog displays (and responses) on your joystick. <br />
<br />
=== Confirming that the driver recognizes your joystick ===<br />
FlightGear ships with a utility called js_demo. It will report the number of joysticks attached to a system, their respective "names" and their capabilities. Under Linux, you can run js_demo from the folder /FlightGear/bin as follows: <br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd /usr/local/FlightGear/bin <br />
$ js_demo<br />
</syntaxhighlight><br />
<br />
Under Windows, open a command shell (<tt>Start > All Programs > Accessories > Command Prompt</tt>), go to the FlightGear binary folder and start the program as follows (given FlightGear is installed under <tt>C:/Program Files/Flightgear</tt>) <br />
<br />
<syntaxhighlight lang="dos"><br />
C:<br />
cd /Program Files/FlightGear/bin/win32 <br />
js_demo.exe <br />
</syntaxhighlight><br />
<br />
<!--If js_demo.exe is not included in your version, download it [http://fgfs.beggabaur.de/forum/js_demo.exe here].--><br />
<br />
On our system, the first few lines of output are (stop the program with C if it is quickly scrolling past your window!) as follows: <br />
<br />
<syntaxhighlight><br />
Joystick test program. <br />
Joystick 0: “CH PRODUCTS CH FLIGHT SIM YOKE USB ” <br />
Joystick 1: “CH PRODUCTS CH PRO PEDALS USB” <br />
Joystick 2 not detected <br />
Joystick 3 not detected <br />
Joystick 4 not detected <br />
Joystick 5 not detected <br />
Joystick 6 not detected <br />
Joystick 7 not detected <br />
+——————–JS.0———————-+——————–JS.1———————-+ <br />
| Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 Ax:6 | Btns Ax:0 Ax:1 Ax:2 | <br />
+———————————————-+———————————————-+ <br />
| 0000 +0.0 +0.0 +1.0 -1.0 -1.0 +0.0 +0.0 . | 0000 -1.0 -1.0 -1.0 . . . . . | <br />
</syntaxhighlight><br />
<br />
First note that js demo reports which number is assigned to each joystick recognized by the driver. Also, note that the “name” each joystick reports is also included between quotes. We will need the names for each bindings file when we begin writing the binding xml files for each joystick.<br />
<br />
=== Identifying the numbering of axes and buttons ===<br />
Axis and button numbers can be identified using js demo as follows. By observing the output of js demo while working your joystick axes and buttons you can determine what axis and button numbers are assigned to each joystick axis and button. It should be noted that numbering generally starts with zero. <br />
<br />
The buttons are handled internally as a binary number in which bit 0 (the least significant bit) represents button 0, bit 1 represents button 1, etc., but this number is displayed on the screen in hexadecimal notation, so: <br />
<br />
* 0001 ⇒ button 0 pressed <br />
* 0002 ⇒ button 1 pressed <br />
* 0004 ⇒ button 2 pressed <br />
* 0008 ⇒ button 3 pressed <br />
* 0010 ⇒ button 4 pressed <br />
* 0020 ⇒ button 5 pressed <br />
* 0040 ⇒ button 6 pressed <br />
* ... etcp to ... <br />
* 8000 ⇒ button 15 pressed <br />
* ... and ... <br />
* 0014 ⇒ buttons 2 and 4 pressed simultaneously <br />
* ... etc. <br />
<br />
For Linux users, there is another option for identifying the “name” and the numbers assigned to each axis and button. Most Linux distributions include a very handy program, “jstest”. With a CH Product Yoke plugged into the system, the following output lines are displayed by jstest: <br />
<br />
<syntaxhighlight lang="bash"><br />
jstest /dev/js3 <br />
Joystick (CH PRODUCTS CH FLIGHT SIM YOKE USB ) has 7 axes and 12 buttons. Driver version is 2.1.0 <br />
Testing…(interrupt to exit) <br />
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:on 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off <br />
</syntaxhighlight><br />
<br />
Note the “name” between parentheses. This is the name the system associates with your joystick. <br />
<br />
When you move any control, the numbers change after the axis number corresponding to that moving control and when you depress any button, the “off” after the button number corresponding to the button pressed changes to “on”. In this way, you can quickly write down the axes numbers and button numbers for each function without messing with binary.<br />
<br />
In most modern repositories, there is a graphical version of this program, called "jstest-gtk", where you are given a list of attached devices to choose from, and then get a graphical representation of all axes and buttons.<br />
<br />
=== Calibration ===<br />
For many/most joysticks this step might not be necessary. If either, the centre position of the joystick does not yield near-zero values for relevant axes, or if the maximum value for an axis cannot be reached, or is reached too early, you need to calibrate the joystick. (Note that some calibration problems can be fixed with the flighgear joystick configuration files, but not all, e.g. if the maximum value is reached too early)<br />
<br />
==== Linux ====<br />
The program "jscal" (install from repositories if not already available on your system) provides a calibration routine for joysticks. You need to know or find out the device name of your joystick (usually /dev/js0 or /dev/input/js0 - instead of 0 a different number might need to be used, look at output of js_demo to figure out which). For example to calibrate the joystick with device name /dev/input/js0, execute<br />
<syntaxhighlight lang="bash">jscal -c /dev/input/js0<br />
</syntaxhighlight><br />
and follow instructions.<br />
The calibration is retained until the joystick is unplugged, or the computer rebooted. In order to save it for future use, execute <br />
<syntaxhighlight lang="bash">jscal -p /dev/input/js0<br />
</syntaxhighlight><br />
which will print the command that needs to be entered to restore the calibration, for example<br />
<syntaxhighlight lang="bash">jscal -s 6,1,0,8171,8171,65936,65374,1,0,8166,8166,65928,65494,1,0,128,128,4194176,4227201,1,0,128,128,4194176,4227201,1,0,0,0,536854528,536854528,1,0,0,0,536854528,536854528 /dev/input/js0<br />
</syntaxhighlight><br />
Copy the command you obtained into your startup script in order to restore calibration automatically.<br />
<br />
Recent versions of jscal have this simplified, you can store and restore your calibration settings.<br />
After calibration store the settings:<br />
<syntaxhighlight lang="bash">jscal-store /dev/input/js0<br />
</syntaxhighlight><br />
<br />
Then in your startup script recall the settings for the given device:<br />
<syntaxhighlight lang="bash">jscal-restore /dev/input/js0<br />
</syntaxhighlight><br />
<br />
However if you have multiple controllers connected, they might be renumbered on pluging/repluging. Best way to insure you get the correct calibration is to create a custom '''udev''' rule-set that you put into /etc/udev/rules.d/00-joystick.rules, similar to the following example:<br />
<syntaxhighlight lang="bash"><br />
#joystick rules to make the names persistent and reload the stored calibration profile<br />
ACTION!="add|change", GOTO="joystick_end"<br />
SUBSYSTEM!="input", GOTO="joystick_end"<br />
<br />
KERNEL=="js*", ATTRS{idProduct}=="a02f", ATTRS{idVendor}=="12bd", SYMLINK+="input/joystick" RUN+="/etc/udev/scripts/joycal.sh"<br />
KERNEL=="js*", ATTRS{name}=="Logitech Logitech Racing Wheel", SYMLINK+="input/logiwheel" RUN+="/etc/udev/scripts/wheelcal.sh"<br />
<br />
LABEL="joystick_end"<br />
</syntaxhighlight><br />
<br />
Then the scripts called would be as follows:<br />
*/etc/udev/scripts/joycal.sh:<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
jscal-restore /dev/input/joystick<br />
</syntaxhighlight><br />
*/etc/udev/scripts/wheelcal.sh<br />
<syntaxhighlight lang="bash"><br />
#!/bin/sh<br />
jscal-restore /dev/input/logiwheel<br />
</syntaxhighlight><br />
<br />
Now each time you plug/replug your joysticks/controllers they will get the persistent device names, and will get the correct calibration profile restored.<br />
<br />
<br />
The calibration is even more comfortable using the program "jstest-gtk", also available from most repositories. Starting this you are given a list of all attached joysticks with their device names. Pick the one you wish to inspect or calibrate and click 'Properties', then calibrate. This calibration tool offers the possibility to fine-tune the calibration by editing the numbers. The program manipulates the same internals as jscal so you can use jscal to save the calibration information for later use, as before.<br />
<br />
=== Writing or editing joystick binding xml files ===<br />
At this point, you have confirmed that the operating system and the joystick driver both recognize your joystick(s). You also know of several ways to identify the joystick “name” your joystick reports to the driver and operating system. You will need a written list of what control functions you wish to have assigned to which axis and button and the corresponding numbers. <br />
<br />
Make the following table from what you learned from js demo or jstest above (pencil and paper is fine). Here we assume there are 5 axes including 2 axes associated with the hat. <br />
<br />
{| class="prettytable"<br />
! align="center" bgcolor="#EFEFEF" | Axis<br />
! align="center" bgcolor="#EFEFEF" | Button<br />
|- <br />
|elevator = 0 <br />
|view cycle = 0 <br />
|- <br />
|rudder = 1 <br />
|all brakes = 1 <br />
|- <br />
|aileron = 2 <br />
|up trim = 2 <br />
|- <br />
|throttle = 3 <br />
|down trim = 3 <br />
|-<br />
|leftright hat = 4 <br />
|extend flaps = 4 <br />
|- <br />
|foreaft hat = 5 <br />
|retract flaps = 5 <br />
|-<br />
| <br />
|decrease RPM = 6 <br />
|-<br />
|<br />
|increase RPM = 7 <br />
|}<br />
<br />
We will assume that our hypothetical joystick supplies the “name” QUICK STICK 3D USB to the system and driver. With all the examples included with FlightGear, the easiest way to get a so far unsupported joystick to be auto detected, is to edit an existing binding xml file. Look at the xml files in the sub-folders of '''/FlightGear/Input/Joysticks/'''. After evaluating several of the xml binding files supplied with FlightGear, we decide to edit the file <tt>[[$FG_ROOT]]/Input/Joysticks/Saitek/Cyborg-Gold-3d-USB.xml</tt>.<br />
<br />
This file has all the axes functions above assigned to axes and all the button functions above assigned to buttons. This makes our editing almost trivial. <br />
<br />
Before we begin to edit, we need to choose a name for our bindings xml file, create the folder for the QS joysticks, and copy the original xml file into this directory with this name. <br />
<br />
<syntaxhighlight lang="bash"><br />
$ cd /usr/local/FlightGear/Input/Joysticks <br />
$ mkdir QS <br />
$ cd QS <br />
$ cp /usr/local/FlightGear/Input/Joysticks/Saitek/ <br />
Cyborg-Gold-3d-USB.xml QuickStick.xml <br />
</syntaxhighlight><br />
<br />
Here, we obviously have supposed a Linux/UNIX system with FlightGear being installed under '''/usr/local/FlightGear'''. For a similar procedure under Windows with FlightGear being installed under C:/Program Files/FlightGear, open a command shell and type <br />
<br />
<syntaxhighlight lang="dos"><br />
C: <br />
cd /Program Files/FlightGear/Input/Joysticks <br />
mkdir QS <br />
cd QS <br />
copy /Program Files/FlightGear/Input/Joysticks/Saitek/ <br />
Cyborg-Gold-3d-USB.xml QuickStick.xml <br />
</syntaxhighlight><br />
<br />
Next, open QuickStick.xml with your favorite editor. Before we forget to change the joystick name, search for the line containing <name>. You should find the line <br />
<br />
<syntaxhighlight lang="xml"><name>SAITEK CYBORG 3D USB</name></syntaxhighlight><br />
<br />
and change it to <br />
<br />
<syntaxhighlight lang="xml"><name>QUICK STICK 3D USB</name></syntaxhighlight><br />
<br />
This line illustrates a key feature of xml statements. They begin with a <tag> and end with a </tag>. <br />
<br />
You can now compare your table to the comment table at the top of your file copy. Note that the comments tell us that the Saitek elevator was assigned to axis 1. Search for the string <br />
<br />
<syntaxhighlight lang="xml"><axis n="1"></syntaxhighlight><br />
<br />
and change this to <br />
<br />
<syntaxhighlight lang="xml"><axis n="0"></syntaxhighlight><br />
<br />
Next, note that the Saitek rudder was assigned to axis 2. Search for the string <br />
<br />
<syntaxhighlight lang="xml"><axis n="2"></syntaxhighlight><br />
<br />
and change this to <br />
<br />
<syntaxhighlight lang="xml"><axis n="1"></syntaxhighlight><br />
<br />
Continue comparing your table with the comment table for the Saitek and changing the axis numbers and button numbers accordingly. Since QUICKSTICK USB and the Saitek have the same number of axes but different number of buttons, you must delete the buttons left over. Just remember to double check that you have a closing tag for each opening tag or you will get an error using the file. <br />
<br />
Finally, be good to yourself (and others when you submit your new binding file to a FlightGear developers or users archive!), take the time to change the comment table in the edited file to match your changed axis and button assignments. The new comments should match the table you made from the js demo output. Save your edits. <br />
<br />
Several users have reported that the numbers of axes and buttons assigned to functions may be different with the same joystick under Windows and Linux. The above procedure should allow one to easily change a binding xml file created for a different operating system for use by their operating system.<br />
<br />
You can tell how FlightGear has interpretted your joystick setup by selecting <tt>Help > Joystick Configuration</tt> from the menu.<br />
<br />
== Joystick support via .fgfsrc entries ==<br />
Fortunately, there is a tool available now, which takes most of the burden from the average user who, maybe, is not that experienced with XML, the language which these files are written in. <br />
<br />
For configuring your joystick using this approach, open a command shell (command prompt under windows, to be found under Start|All programs|Accessories). Change to the directory <tt>[[$FG_ROOT]]/bin</tt> via e.g. (modify to your path) <br />
<br />
<syntaxhighlight lang="dos">cd C:/Program Files/FlightGear/bin</syntaxhighlight><br />
<br />
and invoke the tool fgjs via <br />
<br />
<syntaxhighlight lang="bash">./fgjs --fg-root=$FG_ROOT</syntaxhighlight><br />
<br />
on a UNIX/Linux machine, or via <br />
<br />
<syntaxhighlight lang="dos">fgjs --fg-root=$FG_ROOT</syntaxhighlight><br />
<br />
on a Windows machine. The program will tell you which joysticks, if any, were detected. Now follow the commands given on screen, i.eṁove the axis and press the buttons as required. Be careful, a minor touch already “counts” as a movement. Check the reports on screen. If you feel something went wrong, just re-start the program. <br />
<br />
After you are done with all the axis and switches, the directory above will hold a file called fgfsrc.js. If the FlightGear base directory FlightGear does not already contain an options file .fgfsrc (under UNIX)/system.fgfsrc (under Windows) mentioned above, just copy <br />
<br />
'''fgfsrc.js''' into '''.fgfsrc''' (UNIX)/'''system.fgfsrc''' (Windows) <br />
<br />
and place it into the directory FlightGear base directory FlightGear. In case you already wrote an options file, just open it as well as fgfsrc.js with an editor and copy the entries from fgfsrc.js into .fgfsrc/system.fgfsrc. One hint: The output of fgjs is UNIX formatted. As a result, Windows Editor may not display it the proper way. I suggest getting an editor being able to handle UNIX files as well, for example [https://notepad-plus-plus.org/ Notepad++]. <!-- My favorite freeware file editor for that purpose, although somewhat dated, is still PFE, to be obtained from http://www.lancs.ac.uk/people/cpaap/pfe/. --> <br />
<br />
The the axis/button assignment of fgjs should, at least, get the axis assignments right, its output may need some tweaking. There may be axes moving the opposite way they should, the dead zones may be too small etc. For instance, I had to change <br />
<br />
<syntaxhighlight><br />
--prop:/input/joysticks/js[1]/axis[1]/binding/factor=-1.0<br />
</syntaxhighlight><br />
<br />
into <br />
<br />
<syntaxhighlight><br />
--prop:/input/joysticks/js[1]/axis[1]/binding/factor=1.0<br />
</syntaxhighlight><br />
<br />
(USB CH Flightsim Yoke under Windows XP). Thus, here is a short introduction into the assignments of joystick properties. <br />
<br />
Basically, all axes settings are specified via lines having the following structure: <br />
<br />
<syntaxhighlight><br />
--prop:/input/joysticks/js[n]/axis[m]/binding/command=property-scale <br />
--prop:/input/joysticks/js[n]/axis[m]/binding/property=/controls/steering option<br />
--prop:/input/joysticks/js[n]/axis[m]/binding/dead-band=db<br />
--prop:/input/joysticks/js[n]/axis[m]/binding/offset=os<br />
--prop:/input/joysticks/js[n]/axis[m]/binding/factor=fa<br />
</syntaxhighlight><br />
<br />
where <br />
<br />
{| class="prettytable"<br />
! align="center" bgcolor="#EFEFEF" | <br />
! align="center" bgcolor="#EFEFEF" | <br />
|- <br />
|n<br />
|number of device (usually starting with 0) <br />
|-<br />
|m<br />
|number of axis (usually starting with 0)<br />
|-<br />
|steering option<br />
|elevator, aileron, rudder, throttle, mixture, pitch <br />
|-<br />
|dead-band<br />
|range, within which signals are discarded; useful to avoid jittering for minor yoke movements<br />
|-<br />
|offset<br />
|specifies, if device not centered in its neutral position <br />
|-<br />
|factor<br />
|controls sensitivity of that axis; defaults to +1, with a value of -1 reversing the behavior <br />
|}<br />
<br />
You should be able to at least get your joystick working along these lines. Concerning all the finer points, for instance, getting the joystick buttons working, John Check has written a very useful README being included in the base package to be found under '''FlightGear/Docs/Readme/Joystick.html'''. In case of any trouble with your input device, it is highly recommended to have a look into this document.<br />
<br />
== More about programming joystick XML files ==<br />
=== General tips ===<br />
* When testing a new xml file it is best to start FlightGear via a command window (rather than the GUI interface). Any error messages will then be displayed in the terminal. Error messages will give both a message and a line number, helping you pinpoint any errors.<br />
* Errors can be detected on initial startup or at runtime. Both types of errors will be displayed in the terminal.<br />
* One of the most common errors is including a character that makes XML choke. Such characters include<br>& < --<br>These characters will cause problems even if simply included in comments or within scripts.<br />
* If your scripts contain any of these characters, you have to enclose the scripts in <script><![CDATA[...]]></script>. Alternatively, you can 'escape' the characters, ie "<" becomes "&amp;lt;".<br />
* You can reload your edited joystick file without restarting FlightGear by selecting "Debug" &gt; "Reload Input" from the main simulator window.<br />
* You can find many examples of different ways to program joysticks simply by examining the joystick xml files that are packaged with FlightGear. See the directory FlightGear/data/input/joysticks<br />
* Many advanced functions can be programmed using the Nasal scripting language. These scripts are enclosed in <script></script> tags in the XML file. Helpful:<br />
** A guide to the [[Nasal scripting language]] in FlightGear <br />
** [[Nasal FAQ]]<br />
** [[Howto: Write simple scripts in Nasal]]<br />
* You can explore the internal property tree to see many variables that can be altered using joystick buttons or axes (File/Browse Internal Properties)<br />
* You can test bits of Nasal code and do some other useful things using the Nasal Console (Debug/Nasal Console).<br />
* All Nasal code shares a common namespace, so it's possible to set a variable in one nasal binding, and to read it in another.<br />
<br />
=== Useful hints for scripts ===<br />
Some particularly useful ideas for programming scripts within joystick XML files:<br />
* getprop and setprop can be used for getting & setting properties from the internal properties tree:<br />
<syntaxhighlight lang="nasal"><br />
var brake = !getprop("/controls/gear/brake-parking");<br />
setprop("/controls/gear/brake-parking", brake);<br />
</syntaxhighlight><br />
* You can also make your own values on the property tree:<br />
<syntaxhighlight lang="nasal"><br />
setprop("/input/joysticks/js[0]/myjoystick-modifier", 1);<br />
var mod = getprop("/input/joysticks/js[0]/myjoystick-modifier");<br />
</syntaxhighlight><br />
* You can print to terminal using the print function. This is very useful for debugging.<br />
<syntaxhighlight lang="nasal"><br />
print("Just", " a ", "test");<br />
</syntaxhighlight><br />
* You can display info in FlightGear via a popup. This is useful for giving the user feedback about changes that may not be obvious via the panel. It can also be useful for debugging. Example:<br />
<br />
<syntaxhighlight lang="nasal"><br />
gui.popupTip("Parking Brake ON");<br />
</syntaxhighlight><br />
<br />
Arguments for gui.popupTip must be strings, so if you want to display other types of variables they should be formatted with something like sprintf:<br />
<br />
<syntaxhighlight lang="nasal"><br />
gui.popupTip(sprintf("Elevator trim: %d", 100 * getprop("/controls/flight/elevator-trim")));<br />
</syntaxhighlight><br />
<br />
Or<br />
<br />
<syntaxhighlight lang="nasal"><br />
thv = getprop("/controls/engines/engine[0]/mixture");<br />
gui.popupTip("Thrust vector " ~ int(thv * 120 - 20));<br />
</syntaxhighlight><br />
<br />
* You can just start using variables, ie,<br />
<syntaxhighlight lang="nasal"><br />
x = 10;<br />
</syntaxhighlight><br />
<br />
But [http://wiki.flightgear.org/index.php/Nasal_scripting_language#Variables for various reasons] it is generally better to declare variables with the "var" statement:<br />
<syntaxhighlight lang="nasal"><br />
var x = 10;<br />
</syntaxhighlight><br />
<br />
Note that "var" creates variables that are local in scope, but since all bindings for a joystick share the same scope, it will be seen across each script in the joystick file.<br />
<br />
* You can include a section of script that runs on startup to initialize variables, create functions, etc. Example:<br />
<syntaxhighlight lang="xml"><br />
<PropertyList><br />
<name type="string">My joystick name</name><br />
<name type="string">My joystick name #2</name><br />
<nasal><br />
<script><br />
#initialize variables<br />
f1 = f2 = 0;<br />
left_brake = right_brake = 0;<br />
# create a function to be used with all buttons<br />
getmod = func { getprop("/input/joysticks/js[0]/t-flight-hotas-x-modifier" ) }<br />
</script><br />
</nasal><br />
</syntaxhighlight><br />
<br />
* Sample code for firing weapons with the joystick is found on the [[Gun Effects]] page.<br />
<br />
== Related content ==<br />
{{Forum|24|Hardware}}<br />
* [[Head tracking]]<br />
* [[Joystick xml library]] <br />
* [[Force feedback]]<br />
* [[Troubleshooting input devices]]<br />
* [[Writing Joystick Code: Part 1]]<br />
<br />
== External links ==<br />
* [http://www.flightgear.org/Docs/getstart/getstartch3.html#x8-360003.6 The FlightGear Manual]<br />
* [http://sourceforge.net/projects/hapticsforfg/ Force Feedback]<br />
<br />
[[Category:Hardware]]<br />
[[Category:Joysticks and Yokes]]<br />
<br />
[[de:Joystick]]<br />
[[es:Joystick]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Scenery&diff=105868Scenery2016-11-14T10:45:19Z<p>Gsagostinho: /* Related content */ adding wlbragg's sceneries of the list of projects</p>
<hr />
<div>[[File:Obiou.png|thumb|270px|The Isère region in France.]]<br />
[[File:Worldscenery-text.jpg|thumb|270px|Scenery tiles]]<br />
'''Scenery''' is the landscape in [[FlightGear]] (or any other simulator). The "mint" or unchanged just-downloaded FlightGear comes with 2 square degrees of scenery near San Francisco, California. The rest of the world is available via download. Details and accuracy vary from place to place.<br />
<br />
The scenery data is released as [[World Scenery]] collections, available through download in 10x10 degree chunks from the [http://flightgear.org/legacy-Downloads/scenery.html the FlightGear website]. Please note that the packages there are only updated very infrequently, so instead you can use [[TerraSync]] to download up-to-date scenery as you fly by.<br />
<br />
Some high-quality third-party scenery has also been released for FlightGear. However, because anyone may contribute models or terrain data to the official FlightGear scenery, third-party scenery add-ons are not as common as in other flight simulator projects.<br />
<br />
== Status ==<br />
By the end of this year (2015), the FlightGear Project's hosting for the [http://scenemodels.flightgear.org/ scenemodels] database and website and the [[TerraSync]] repository will no longer be available. As a result, the FlightGear Project is searching for a replacement, even just a temporary one. The technical requirements are roughly these:<br />
* A [http://www.postgresql.org/ PostgreSQL] database (with the [http://postgis.net/ PostGIS] extension) of approximately 40 GB, with capacity to expand (this is for the scenemodels database).<br />
* An Apache webserver, PHP, access to the database and the usual toolkit for hosting the scenemodels website<br />
* An SVN server with 140+ GB for the TerraSync repository.<br />
* Enough bandwith to serve the data.<br />
* One or more reverse proxies serving TerraSync requests (not much storage required, just bandwidth).<br />
If you can provide the above, are able to provide help, or have any serious ideas for a replacement, please get in touch via the [http://forum.flightgear.org/viewtopic.php?p=263629#p263629 forum topic] or the [http://sourceforge.net/p/flightgear/mailman/message/34605975/ mailing list topic]<br />
<br />
— ''{{cite web<br />
|url = http://forum.flightgear.org/viewtopic.php?p=263629#p263629<br />
|title = Scenemodels and terrasync are going down<br />
|author = Torsten<br />
|date = Nov 9th, 2015<br />
}}''<br />
<br />
{{FGCquote<br />
|1= Having the OSM database, probably augmented with our scenemodels, elevation model, navdb, apt.dat, groundnet etc. as the data backend and being able to render the scenery at runtime would be fantastic.<br />
|2= {{cite web<br />
| url = http://forum.flightgear.org/viewtopic.php?p=267920#p267920<br />
| title = <nowiki>Re: OSM, the death of scene models?</nowiki><br />
| author = <nowiki>Torsten</nowiki><br />
| date = Dec 9th, 2015<br />
| added = Dec 9th, 2015<br />
| script_version = 0.23<br />
}}<br />
}}<br />
<br />
{{FGCquote<br />
|1= Sadly, our scenery generation process is in a state of transition right now, so it's not easy/quick (possible?) to do a full world rebuild to reflect an updated apt.dat file. <br />
|2= {{cite web<br />
| url = http://sourceforge.net/p/flightgear/mailman/message/34679413/<br />
| title = <nowiki>Re: [Flightgear-devel] New apt.dat on the X-Plane Scenery Gateway</nowiki><br />
| author = <nowiki>Curtis Olson</nowiki><br />
| date = Dec 8th, 2015<br />
| added = Dec 8th, 2015<br />
| script_version = 0.23<br />
}}<br />
}}<br />
{{FGCquote<br />
|1= Martin, our scenery builder and infrastructure provider for many years has decided to leave the project, there will be no new scenery release for a while.<br />
|2= {{cite web<br />
| url = http://sourceforge.net/p/flightgear/mailman/message/34679633/<br />
| title = <nowiki>Re: [Flightgear-devel] New apt.dat on the X-Plane Scenery Gateway</nowiki><br />
| author = <nowiki>Torsten Dreyer</nowiki><br />
| date = Dec 8th, 2015<br />
| added = Dec 8th, 2015<br />
| script_version = 0.23<br />
}}<br />
}}<br />
{{FGCquote<br />
|1= can we start with a funding the operation of the new home for scenemodels, terrasync and the scenery generation tools (approx 3.000$/year), please?<br />
|2= {{cite web<br />
| url = http://forum.flightgear.org/viewtopic.php?p=266127#p266127<br />
| title = <nowiki>Re: FlightGear Development Push</nowiki><br />
| author = <nowiki>Torsten</nowiki><br />
| date = Nov 26th, 2015<br />
| added = Nov 26th, 2015<br />
| script_version = 0.23<br />
}}<br />
}}<br />
<br />
{{FGCquote<br />
|1= I think trying to come up with 3k/year for infrastructure costs would be a good goal. It will help FG immediately, and it'll serve as a test case - if it's hard to come up with that kind of money, then funding development salaries will be impossible anyway. If this turns out to be easy... well, worth further discussion perhaps. <br />
|2= {{cite web<br />
| url = http://forum.flightgear.org/viewtopic.php?p=267019#p267019<br />
| title = <nowiki>Re: FlightGear Development Push</nowiki><br />
| author = <nowiki>Thorsten</nowiki><br />
| date = Dec 2nd, 2015<br />
| added = Dec 2nd, 2015<br />
| script_version = 0.23<br />
}}<br />
}}<br />
<br />
{{FGCquote<br />
|1= I download the latest planet and run osm2pgsql - here are a few numbers:<br />
The complete planet dump file is approx. 30GB. download yours here (pick the pbf).<br />
The import into a postgresql database takes something between one day (hexacore, 64GB RAM, 4 disks RAID10 7200RPM 4TB Array) to one week (average quad core, 8GB, single consumer market HD) and explodes to several hundret GB for the database (depends a lot on filesystem params).<br />
<br />
I would not recommend this procedure for the average user. <br />
<br />
For the brave, the excellent howto is here: https://switch2osm.org/serving-tiles/manually-building-a-tile-server-14-04/<br />
|2= {{cite web<br />
| url = http://forum.flightgear.org/viewtopic.php?p=267920#p267920<br />
| title = <nowiki>Re: OSM, the death of scene models?</nowiki><br />
| author = <nowiki>Torsten</nowiki><br />
| date = Dec 9th, 2015<br />
| added = Dec 9th, 2015<br />
| script_version = 0.23<br />
}}<br />
}}<br />
<br />
== Related content ==<br />
{{portal|Portal:Developer/Scenery|scenery development}}<br />
* [[Howto:Install scenery|Installing scenery]]<br />
* [[Using TerraGear|Constructing scenery]]<br />
* [[Landmark Wish List]]<br />
* [[Next Generation Scenery]]<br />
<br />
=== Recommended Scenery ===<br />
* [[Developed Airports]] - airports with at least one non-generic airport building placed<br />
* [[Suggested Airports]] - airports ranked by scenery quality<br />
<br />
=== Scenery Projects ===<br />
* [[Brest]]<br />
* [[FlightGear NL]]<br />
* [[Germany]]<br />
* [[Custom France Scenery]]<br />
*[[Project Hong Kong]]<br />
*[[Project Venezuela]]<br />
* Papillon81's git repositories at {{gitorious url}} for scenery (Frankfurt, Singapore).<br />
* [[User:Wlbragg#Kansas_Custom_Scenery|Kansas Custom Scenery]]<br />
* [[User:Wlbragg#Ohio_Custom_Scenery|Ohio Custom Scenery]]<br />
<br />
== External links ==<br />
* [http://www.flightgear.org/download/scenery/ Scenery download page]<br />
* [http://scenemodels.flightgear.org/submission/ Webtools to add/edit/update unitary and massive import of shared model positions]<br />
<br />
{{Terra}}<br />
<br />
[[Category:Scenery| ]]<br />
<br />
[[es:Escenario]]<br />
[[fr:Scenery]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=102982Cessna 172P2016-08-12T18:32:04Z<p>Gsagostinho: </p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
A C172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:C172p-bodensee-panorama.jpg|center|800px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 31" bush tires<br />
* pontoons<br />
* amphibian<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialog).<br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialog. These include cones under the wings, a fuel truck, a ground power unit and ladders. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-ALS-flashlight2.jpg|500px|center|Cessna 172P's flashlight in the cockpit]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touchdown]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you experience grey windows, you do not have the correct FlightGear version. This aircraft requires 3.5 or above.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why the aircraft doesn't move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]<br />
* [http://www.atlasaviation.com/checklists/cessna-172/cessna_172_checklist.htm Cessna 172 checklists at AtlasAviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=User_talk:Bugman&diff=102609User talk:Bugman2016-07-31T22:14:50Z<p>Gsagostinho: /* Duplicates of c182s pages */</p>
<hr />
<div>== The collapsible script template ==<br />
Noticed the {{tl|collapsible script}} template. That will probably come in handy in many places.<br />
<br />
I had no idea that there was such a thing as <code>{{obr}}#'''tag''': {{cbr}}</code>. That may be useful later when I have played around with it.<br />
<br />
Hmm, I see the template defaults to Dec Vadic's Imperial Arem Star. lol ;-)<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:12, 16 October 2015 (EDT)<br />
<br />
: There are quite a few places in the wiki cluttered up by long scripts or code segments. I guess it is mainly Nasal, though some other parts could benefit from other templates using collapsible NavFrame elements. The <code>{{obr}}#'''tag''': {{cbr}}</code> concept is quite useful for programmatically adding tags in templates, avoiding the initial HTML parsing, but it isn't perfect. Anyway, I can see it spreading on the wiki already :) As for the template default, I hope no one is curious and tries it out!<br />
<br />
:[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:14, 18 October 2015 (EDT)<br />
<br />
: Let me add that <code>{{obr}}#'''tag''': {{cbr}}</code> allows for transclusion within any HTML tag, which is normally not possible.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:51, 19 October 2015 (EDT)<br />
<br />
<br />
: ''The newsletter template discussion was moved to [[FlightGear wiki:Village pump#Newsletter templates]] ([http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=88787#Newsletter_templates perm]).''<br />
<br />
== German FGAddon translation ==<br />
<br />
Hi Edward,<br />
<br />
are you still working on the [[De/FGAddon|German translation of the FGAddon article]]? If not, should I go ahead with the translation?<br />
<br />
Cheers<br />
<br />
[[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 05:32, 7 April 2016 (EDT)<br />
<br />
: Hi! I'm on holiday and have been distracted by other work. Go for it!<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 23:52, 11 April 2016 (EDT)<br />
<br />
:: Okay, thank you.<br />
::[[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 00:10, 12 April 2016 (EDT)<br />
<br />
== Lockheed P-38 Lightning ==<br />
thanks for renaming that file... i can't believe that i misspelled that like that... sometimes the fingers think they know what the brain is trying to write :lol: <br />
[[User:Wkitty42|Wkitty42]] ([[User talk:Wkitty42|talk]]) 11:16, 1 June 2016 (EDT)<br />
<br />
: No problems! I often have the same problem :) Anyway, if you need any pages or files moved, just say.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:19, 1 June 2016 (EDT)<br />
<br />
== The <aircraft>/info template ==<br />
<br />
Hi,<br />
<br />
It seems the new template for the aircraft info box or <aircraft>/info page doesn't show '_' (underscore) in the --aircraft= field. The old info box template did so it is probably a bug? [[User:AndersG|AndersG]] ([[User talk:AndersG|talk]]) 15:21, 23 June 2016 (EDT)<br />
<br />
: Thanks for spotting that! I can see that that is a problem with the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23titleparts #titleparts] function: "All underscores are automatically replaced with spaces". That is rather annoying. I might then create {{param|fgname1}} to {{param|fgname10}} as an alternative, as the number of <code>*-set.xml</code> files with underscores is very low.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:38, 23 June 2016 (EDT)<br />
<br />
== The so caled "Emilianh H's hangar" ==<br />
<br />
Hi, <br />
<br />
While I appreciate your efforts, I would also appreciate it if this labeling would be possibly omitted, also not directly linked to.<br />
<br />
I would also had appreciated some sort of preliminary discussion/warning prior to such labeling/linking if it would have taken place.<br />
<br />
Thanks for your understanding<br />
<br />
[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:07, 15 July 2016 (EDT)<br />
<br />
: No problems. I'm just experimenting with this, to allow for automated link creation for the new aircraft infobox template (see [[User:Bugman/Infobox Aircraft]]). This also includes the important note that the aircraft is {{tl|non-GPL}}. Note that in the end, all wiki aircraft pages will be identified by hangar when available. But for the <code>| hangar = emilianh</code> parameter value, the heading "Emilian H's Hangar" has been removed. See [[User:Bugman/Infobox Aircraft#IAR 80]].<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:16, 15 July 2016 (EDT)<br />
<br />
:: Thanks, however unfortunatley link to "website" still shows. How about "Aircraft by $Name" instead of "$Name's hangar" ? what happens if $Name has n aircraft hosted in m places?<br />
<br />
:: Regards,<br />
<br />
::[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:22, 15 July 2016 (EDT)<br />
<br />
::: I don't quite follow, but we should be able to expand on the [[User:Bugman/Infobox Aircraft]] to match all aircraft author's needs. That is the aim of this new template to replace {{tl|infobox aircraft}}. Click on the 'Edit' link, and then search for <code>emilianh</code> to see all the customisations I have made. We can change this to anything, to help automate the infobox creation. I thought I'd use your aircraft as a testing example for improving GitLab support in [[User:Bugman/Infobox Aircraft]] and [[:Category:Repository link templates]].<br />
<br />
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:30, 15 July 2016 (EDT)<br />
<br />
::::The [[User:Bugman/Infobox Aircraft]] still displays the website and the devel-repo links. I, personally, for my aircraft, would prefer it if those were not ever shown, and only the download link was available. However I now noticed that on the actual [[IAR 80]] page it is properly hidden.<br />
::::As for the second part of my previous question, what happens if I had say the iar80 hosted on github, the l10 on gitlab, and some other aircraft hosted on somesite.somwhere.else, to what does the "hangar" point to?<br />
::::I understand that in this particular case you were using it to improve an example gitlab based "hangar".<br />
::::Regards, [[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:55, 15 July 2016 (EDT)<br />
<br />
::::: That is because you removed the <code>hangar</code> and <code>aircraft</code> parameters from [[IAR 80/info]], and added <code>download</code>, removing most of the automated aspects of the template. How the <code>| hangar = emilianh</code> parameter value automates the template creation is totally up to the aircraft author - and it is directly coded into the template. I have created most of these in the [[User:Bugman/Infobox Aircraft]] testing template with direct author feedback. So for excluding the website and devel-repo links, that would simply require removing those lines in [[User:Bugman/Infobox Aircraft]], where the <code>emilianh</code> hangar parameter is found. Feel free to customise [[User:Bugman/Infobox Aircraft]] for the <code>| hangar = emilianh</code> parameter as you wish. You'll see the result in the [[User:Bugman/Infobox Aircraft#IAR 80]] when previewing the changes. You can also change <code>emilianh</code> to any value you wish.<br />
<br />
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:14, 15 July 2016 (EDT)<br />
<br />
== Duplicates of c182s pages ==<br />
<br />
Hi Bugman, <br />
<br />
We have renamed the Cessna 182S project from c182 to c182s, and to reflect that change I created a new wiki page for it. It turns out that wasn't necessary as I could have moved the previous page to a new name, so now I have two mais wiki pages and two infoboxes:<br />
<br />
http://wiki.flightgear.org/Cessna_182S<br />
<br />
http://wiki.flightgear.org/Cessna_182S/info<br />
<br />
http://wiki.flightgear.org/Cessna_182<br />
<br />
http://wiki.flightgear.org/Cessna_182/info<br />
<br />
I would like to delete the last two (the ones without the S). How can I do that, could you please give me a hand?<br />
<br />
Thanks a lot!<br />
<br />
[[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
: To preserve history, I'll delete the first two now, then move the last two to the first two. I think only admins can move and rename pages. Anyway, it'll be done asap.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:44, 31 July 2016 (EDT)<br />
<br />
:: I see, thanks a lot and sorry for the mess.<br />
<br />
:: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
::: Done. I've left redirects, as there are many links to the original. These links should really be updated to the new pages. Click on [[Cessna 182]], at the top of the page you will see "Redirected from [[Cessna 182]]", click on that link, click on "What links here", then hunt down and update all links. Cheers!<br />
<br />
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 13:10, 31 July 2016 (EDT)<br />
<br />
:::: Thanks a lot, Bugman, I really appreciate it!<br />
<br />
:::: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
::::: You're welcome! Most of the links to the old [[Cessna 182]] will be in {{tl|Cessna}}. Minimally that one should be updated. I'll let you chase up these old links.<br />
<br />
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 14:59, 31 July 2016 (EDT)<br />
<br />
:::::: I see now what you mean. I updated that link and I will keep an eye for any older ones. Cheers.<br />
<br />
:::::: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
:::::: There are a lot more ;) See [[Special:WhatLinksHere/Cessna_182]]. The double redirects are especially important to remove, as these will be flagged here: [[Special:DoubleRedirects]].<br />
<br />
:::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:13, 31 July 2016 (EDT)<br />
<br />
::::::: So, I did that for all those links (plus a bunch more that I found with the search), but here are a couple of things:<br />
::::::: * some of those links can't be edited (e.g. http://wiki.flightgear.org/FlightGear_Newsletter_March_2016 )<br />
::::::: * there are mentions in this very page here, should we really remove it? If we do, this conversation will make much less sense for a 3rd person<br />
::::::: * there is an image of the very old c182, which I don't even know if is the model S or not<br />
:::::::<br />
::::::: Would you mind taking a look at [[Special:WhatLinksHere/Cessna_182]]?<br />
<br />
::::::: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
:::::::: Thank you! That saves the admins a lot of cleanup work. For such redirect links, it is ok to leave the locked articles and, especially, the talk pages. You have fixed as many links as an admin would, so this is perfect wiki maintenance. Cheers!<br />
<br />
:::::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 17:47, 31 July 2016 (EDT)<br />
<br />
::::::::: Glad to hear that! :-)<br />
<br />
::::::::: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=C182s&diff=102606C182s2016-07-31T20:08:37Z<p>Gsagostinho: Redirected page to Cessna 182S</p>
<hr />
<div>#REDIRECT [[Cessna 182S]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=User_talk:Bugman&diff=102605User talk:Bugman2016-07-31T20:08:02Z<p>Gsagostinho: </p>
<hr />
<div>== The collapsible script template ==<br />
Noticed the {{tl|collapsible script}} template. That will probably come in handy in many places.<br />
<br />
I had no idea that there was such a thing as <code>{{obr}}#'''tag''': {{cbr}}</code>. That may be useful later when I have played around with it.<br />
<br />
Hmm, I see the template defaults to Dec Vadic's Imperial Arem Star. lol ;-)<br />
<br />
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:12, 16 October 2015 (EDT)<br />
<br />
: There are quite a few places in the wiki cluttered up by long scripts or code segments. I guess it is mainly Nasal, though some other parts could benefit from other templates using collapsible NavFrame elements. The <code>{{obr}}#'''tag''': {{cbr}}</code> concept is quite useful for programmatically adding tags in templates, avoiding the initial HTML parsing, but it isn't perfect. Anyway, I can see it spreading on the wiki already :) As for the template default, I hope no one is curious and tries it out!<br />
<br />
:[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:14, 18 October 2015 (EDT)<br />
<br />
: Let me add that <code>{{obr}}#'''tag''': {{cbr}}</code> allows for transclusion within any HTML tag, which is normally not possible.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:51, 19 October 2015 (EDT)<br />
<br />
<br />
: ''The newsletter template discussion was moved to [[FlightGear wiki:Village pump#Newsletter templates]] ([http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=88787#Newsletter_templates perm]).''<br />
<br />
== German FGAddon translation ==<br />
<br />
Hi Edward,<br />
<br />
are you still working on the [[De/FGAddon|German translation of the FGAddon article]]? If not, should I go ahead with the translation?<br />
<br />
Cheers<br />
<br />
[[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 05:32, 7 April 2016 (EDT)<br />
<br />
: Hi! I'm on holiday and have been distracted by other work. Go for it!<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 23:52, 11 April 2016 (EDT)<br />
<br />
:: Okay, thank you.<br />
::[[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 00:10, 12 April 2016 (EDT)<br />
<br />
== Lockheed P-38 Lightning ==<br />
thanks for renaming that file... i can't believe that i misspelled that like that... sometimes the fingers think they know what the brain is trying to write :lol: <br />
[[User:Wkitty42|Wkitty42]] ([[User talk:Wkitty42|talk]]) 11:16, 1 June 2016 (EDT)<br />
<br />
: No problems! I often have the same problem :) Anyway, if you need any pages or files moved, just say.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:19, 1 June 2016 (EDT)<br />
<br />
== The <aircraft>/info template ==<br />
<br />
Hi,<br />
<br />
It seems the new template for the aircraft info box or <aircraft>/info page doesn't show '_' (underscore) in the --aircraft= field. The old info box template did so it is probably a bug? [[User:AndersG|AndersG]] ([[User talk:AndersG|talk]]) 15:21, 23 June 2016 (EDT)<br />
<br />
: Thanks for spotting that! I can see that that is a problem with the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23titleparts #titleparts] function: "All underscores are automatically replaced with spaces". That is rather annoying. I might then create {{param|fgname1}} to {{param|fgname10}} as an alternative, as the number of <code>*-set.xml</code> files with underscores is very low.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:38, 23 June 2016 (EDT)<br />
<br />
== The so caled "Emilianh H's hangar" ==<br />
<br />
Hi, <br />
<br />
While I appreciate your efforts, I would also appreciate it if this labeling would be possibly omitted, also not directly linked to.<br />
<br />
I would also had appreciated some sort of preliminary discussion/warning prior to such labeling/linking if it would have taken place.<br />
<br />
Thanks for your understanding<br />
<br />
[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:07, 15 July 2016 (EDT)<br />
<br />
: No problems. I'm just experimenting with this, to allow for automated link creation for the new aircraft infobox template (see [[User:Bugman/Infobox Aircraft]]). This also includes the important note that the aircraft is {{tl|non-GPL}}. Note that in the end, all wiki aircraft pages will be identified by hangar when available. But for the <code>| hangar = emilianh</code> parameter value, the heading "Emilian H's Hangar" has been removed. See [[User:Bugman/Infobox Aircraft#IAR 80]].<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:16, 15 July 2016 (EDT)<br />
<br />
:: Thanks, however unfortunatley link to "website" still shows. How about "Aircraft by $Name" instead of "$Name's hangar" ? what happens if $Name has n aircraft hosted in m places?<br />
<br />
:: Regards,<br />
<br />
::[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:22, 15 July 2016 (EDT)<br />
<br />
::: I don't quite follow, but we should be able to expand on the [[User:Bugman/Infobox Aircraft]] to match all aircraft author's needs. That is the aim of this new template to replace {{tl|infobox aircraft}}. Click on the 'Edit' link, and then search for <code>emilianh</code> to see all the customisations I have made. We can change this to anything, to help automate the infobox creation. I thought I'd use your aircraft as a testing example for improving GitLab support in [[User:Bugman/Infobox Aircraft]] and [[:Category:Repository link templates]].<br />
<br />
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:30, 15 July 2016 (EDT)<br />
<br />
::::The [[User:Bugman/Infobox Aircraft]] still displays the website and the devel-repo links. I, personally, for my aircraft, would prefer it if those were not ever shown, and only the download link was available. However I now noticed that on the actual [[IAR 80]] page it is properly hidden.<br />
::::As for the second part of my previous question, what happens if I had say the iar80 hosted on github, the l10 on gitlab, and some other aircraft hosted on somesite.somwhere.else, to what does the "hangar" point to?<br />
::::I understand that in this particular case you were using it to improve an example gitlab based "hangar".<br />
::::Regards, [[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:55, 15 July 2016 (EDT)<br />
<br />
::::: That is because you removed the <code>hangar</code> and <code>aircraft</code> parameters from [[IAR 80/info]], and added <code>download</code>, removing most of the automated aspects of the template. How the <code>| hangar = emilianh</code> parameter value automates the template creation is totally up to the aircraft author - and it is directly coded into the template. I have created most of these in the [[User:Bugman/Infobox Aircraft]] testing template with direct author feedback. So for excluding the website and devel-repo links, that would simply require removing those lines in [[User:Bugman/Infobox Aircraft]], where the <code>emilianh</code> hangar parameter is found. Feel free to customise [[User:Bugman/Infobox Aircraft]] for the <code>| hangar = emilianh</code> parameter as you wish. You'll see the result in the [[User:Bugman/Infobox Aircraft#IAR 80]] when previewing the changes. You can also change <code>emilianh</code> to any value you wish.<br />
<br />
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:14, 15 July 2016 (EDT)<br />
<br />
== Duplicates of c182s pages ==<br />
<br />
Hi Bugman, <br />
<br />
We have renamed the Cessna 182S project from c182 to c182s, and to reflect that change I created a new wiki page for it. It turns out that wasn't necessary as I could have moved the previous page to a new name, so now I have two mais wiki pages and two infoboxes:<br />
<br />
http://wiki.flightgear.org/Cessna_182S<br />
<br />
http://wiki.flightgear.org/Cessna_182S/info<br />
<br />
http://wiki.flightgear.org/Cessna_182<br />
<br />
http://wiki.flightgear.org/Cessna_182/info<br />
<br />
I would like to delete the last two (the ones without the S). How can I do that, could you please give me a hand?<br />
<br />
Thanks a lot!<br />
<br />
[[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
: To preserve history, I'll delete the first two now, then move the last two to the first two. I think only admins can move and rename pages. Anyway, it'll be done asap.<br />
<br />
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:44, 31 July 2016 (EDT)<br />
<br />
:: I see, thanks a lot and sorry for the mess.<br />
<br />
:: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
::: Done. I've left redirects, as there are many links to the original. These links should really be updated to the new pages. Click on [[Cessna 182]], at the top of the page you will see "Redirected from [[Cessna 182]]", click on that link, click on "What links here", then hunt down and update all links. Cheers!<br />
<br />
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 13:10, 31 July 2016 (EDT)<br />
<br />
:::: Thanks a lot, Bugman, I really appreciate it!<br />
<br />
:::: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
::::: You're welcome! Most of the links to the old [[Cessna 182]] will be in {{tl|Cessna}}. Minimally that one should be updated. I'll let you chase up these old links.<br />
<br />
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 14:59, 31 July 2016 (EDT)<br />
<br />
:::::: I see now what you mean. I updated that link and I will keep an eye for any older ones. Cheers.<br />
<br />
:::::: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])<br />
<br />
:::::: There are a lot more ;) See [[Special:WhatLinksHere/Cessna_182]]. The double redirects are especially important to remove, as these will be flagged here: [[Special:DoubleRedirects]].<br />
<br />
:::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:13, 31 July 2016 (EDT)<br />
<br />
::::::: So, I did that for all those links (plus a bunch more that I found with the search), but here are a couple of things:<br />
::::::: * some of those links can't be edited (e.g. http://wiki.flightgear.org/FlightGear_Newsletter_March_2016 )<br />
::::::: * there are mentions in this very page here, should we really remove it? If we do, this conversation will make much less sense for a 3rd person<br />
::::::: * there is an image of the very old c182, which I don't even know if is the model S or not<br />
:::::::<br />
::::::: Would you mind taking a look at [[Special:WhatLinksHere/Cessna_182]]?<br />
<br />
::::::: [[User:Gsagostinho|Gsagostinho]] ([[User talk:Gsagostinho|talk]])</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=Cessna_C182&diff=102604Cessna C1822016-07-31T20:05:26Z<p>Gsagostinho: Redirected page to Cessna 182S</p>
<hr />
<div>#REDIRECT [[Cessna 182S]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=C182&diff=102603C1822016-07-31T20:05:19Z<p>Gsagostinho: Redirected page to Cessna 182S</p>
<hr />
<div>#REDIRECT [[Cessna 182S]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:Cessna_182S_at_LEBL.jpg&diff=102602File:Cessna 182S at LEBL.jpg2016-07-31T20:04:27Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Cessna 182S Skylane departing from Barcelona-El Prat Airport (LEBL). This is FlightGear's screenshot of the month March 2016.}}<br><br />
{{de|1=Cessna 182S Skylane beim Abflug von Barcelona-El Prat (LEBL). Dies ist FlightGear's Screenshot des Monats März 2016.}}<br />
|date=2016-03-08<br />
|source={{own}}<br />
|author=[[User:Dg-505|Jonathan S. (DG-505)]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
[[Category:Cessna 182S screenshots]]<br />
[[Category:Screenshots of airports in Spain]]<br />
[[Category:Screenshots of scenery in Europe]]<br />
[[Category:Screenshot of the month|2016 03]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-1.jpg&diff=102601File:C182-1.jpg2016-07-31T20:03:36Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-1}}<br />
|date=2016-02-16 23:04:22<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
[[Category:Cessna 182S cockpit screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:Cessna_182_with_procedural_lights.jpg&diff=102600File:Cessna 182 with procedural lights.jpg2016-07-31T20:03:30Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=Cessna 182S at St. Barthélemy Airport (TFFJ) with procedural generated lights.}}<br><br />
{{de|1=Cessna 182S auf dem Flughafen Flughafen St. Barthélemy (TFFJ) mit procedural generierter Beleuchtung.}}<br />
|date=2016-03-15<br />
|source={{own}}<br />
|author=[[User:Dg-505|Jonathan S.]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]<br />
[[Category:Screenshots of airports in France]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-external4.jpg&diff=102599File:C182-external4.jpg2016-07-31T20:02:36Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-external4}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-rosskopf-at-dusk.jpg&diff=102598File:C182-rosskopf-at-dusk.jpg2016-07-31T20:02:30Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-rosskopf-at-dusk}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]<br />
[[Category:Cessna 182S cockpit screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-external3.jpg&diff=102597File:C182-external3.jpg2016-07-31T20:02:14Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-external3}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-external2.jpg&diff=102596File:C182-external2.jpg2016-07-31T20:02:09Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-external2}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-night-take-off.jpg&diff=102595File:C182-night-take-off.jpg2016-07-31T20:02:04Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-night-take-off}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]<br />
[[Category:Cessna 182S cockpit screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-4.jpg&diff=102594File:C182-4.jpg2016-07-31T20:01:58Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-4}}<br />
|date=2016-02-16 23:04:28<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-external1.jpg&diff=102593File:C182-external1.jpg2016-07-31T20:01:53Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-external1}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-external-at-night.jpg&diff=102592File:C182-external-at-night.jpg2016-07-31T20:01:48Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-external-at-night}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-external6.jpg&diff=102591File:C182-external6.jpg2016-07-31T20:01:44Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-external6}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-external5.jpg&diff=102590File:C182-external5.jpg2016-07-31T20:01:39Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=c182-external5}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinhohttps://wiki.flightgear.org/w/index.php?title=File:C182-rain.jpg&diff=102589File:C182-rain.jpg2016-07-31T20:01:34Z<p>Gsagostinho: </p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=C182-rain}}<br />
|date=2016-07-25<br />
|source={{own}}<br />
|author=[[User:Gsagostinho|Gsagostinho]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
<br />
[[Category:Cessna 182S screenshots]]</div>Gsagostinho