FlightGear wiki - User contributions [en]

A6M2 Zero manual

2014-07-17T02:53:18Z

JayVS: The Official FGFS Reisen Manual

== A6M2 Reisen "Zero" Fighter Aircraft ==

=== A Little History ===

[[File:A6M2.gif|framed|right|A6M2 Zero in a light left bank over the Pacific]]

The A6M-series aircraft developed during the Second World War were exceptional warplanes employed by the Imperial Japanese forces, namely the Imperial Navy. The A6M2 Reisen, nicknamed the "Zero", was by far the most used and most recognizable Japanese fighter. The A6M5 and A6M8 were power-packed fighters decked out with 20mm cannon and 7.7mm machine guns. The A6M2 was the easiest to handle, more maneuverable, and had decent range. Above all, it was carrier-capable, and this aided the Imperial cause during the Pacific War.

The Reisen's most problematic issue was survivability. The Zero was known to the Americans as the "paper tube", due to its lack of armour and structural defenses. The aircraft lit up easily, and practically any gun in the Allied arsenal could shoot down one of these fighters.

The A6M2 was remarkable in its abilities as a turning fighter. The American tactic was centered around speed, armour, and heavy armament, and the Japanese exploited this to the limit. The Zero was initially turned down by many manufacturers after the military specified how spectacular the requirements would have to be, but a company called Mitsubishi took up the challenge and developed one of the most successful fighters of World War II. The Reisen was incredibly difficult to line up in a gunsight at low speeds; however, at higher velocities the aircraft's controls would start to be sluggish or even seize up altogether. The Allies countered this frightening aspect with their "Cat" series. These included the Navy variants of the Bearcat, Hellcat, Tigercat, and the Wildcat. The Hellcat was by far the best answer to the growing problem of the enemy over the horizon.

Zeroes continued to fight till they breathed their last in 1945. The Allies were victorious after bloody wars in the Pacific and the European theatre. The wars in Africa and China were all but over, and the Americans began their search for a surviving Reisen.

Only one airworthy A6M2 remains today, and the other two known about lie at the bottom of the Pacific, where teams of divers and historians have probed the depths, searching for answers to the legendary fighter, the A6M2 Reisen "Zero".

=== The Manual ===

==== A6M2 Controls====

*CTRL-B: Toggle Engine Boost (2 stages)
*CTRL-D: Open / Close Canopy
*CTRL-L: Toggle Tailwheel Lock
*SHIFT-C: Catapult Launch
*O/o: Down/up Hook
*L: Engage Launch bar
*l: Open Livery Dialog

==== Summary ====

This manual is intended for use in FlightGear, and is not related to any flight dynamics in the real world. Please note, the Zero's FDM is not very accurate, but this manual will serve mainly to help with engine procedures and dogfighting readiness. Also, for information on the tailwheel and basic ground maneuvering, visit the [http://forum.flightgear.org/viewtopic.php?f=49&t=23554 FG Forum topic--A6M2 Zero Ground Maneuvering].

==== Ground Start-up and Take-off====

To start the A6M2 in FlightGear isn't difficult in the least. Based solely on the simulator and not real procedures, here is how to work the engine on start-up.
------------------------------------------
Cold morning? Give the throttle around 15%. If it's any old day (or night), go over the review check.

As follows:

* Assuming you are on a runway, and if not then scroll down for a link to ground maneuvering in the Zero:
* Check any lights (the Zero currently has none, so night flight is near suicidal unless you are flawless in IFR).
* Raise throttle to 10%. (For a snappy start, which is terrible for the engine life but may be necessary if you have to get away from the airfield in a hurry will be best, raise the throttle to around 50% and lever it around till the starter ignites.)
* Check fuel. This is just a reminder as you should have already.
* Check battery (not currently a problem; the Reisen is really an out-of-the-box fighter). On?
* Primer (same issue)? 5x?
* Now make sure your canopy is thoroughly latched. If it isn't the dust and whatnot that gets kicked up from the propeller will hit you in the face.
* Look over your shoulders (you should have approximately two shoulders, if I recall correctly) and throw your stick around to assure your control surfaces are in working order. Twist the stick if it is capable for rudder. If you are a keyboard and mouse user, apply these techniques as needed. (K&M users: rudder is usually the Enter key and the Insert key. On occasion it is the 0 key. Control surfaces such as ailerons and elevators are triggered by your mouse whilst in Control Mode [right-click once].) Go to the limit to make sure your aircraft is in peak condition. This is required of any pilot regardless of occupation, even to today.
* Now make sure your parking brake is set to ON.
* Flaps one notch. If your strip is short, two is OK. No more than two notches, as the final ones are for landing ONLY.
* Throttle 90% military power AFTER releasing brake.
* The Zero will lurch to the left and nose down after about 60 knots (could be wrong about the speed there), so be ready to give it a little right rudder to balance it out. The fighter likes to josh around on the takeoff, so just be ready to counter its humor with rudder and watch your speed.
* The Zero is remarkable in its minimum rotation speed. After the plane has nosed down and is level, pull back on the stick and rotate around 60-80 KIAS.
* Retract gear ASAP.
* Retract flaps one notch after reaching 90 KIAS.
* Retract final notch of flaps after 100 KIAS.
* The Zero will sink after retracting flaps. No worries. Just counter with elevator.
* IMPORTANT: When at slower speeds the Zero is influenced heavily by the prop torque. To counter this, tap the right aileron trim. (T16000M Thrustmaster users: tap twice on the button assigned.)
* When reaching high speeds in a dive or just as a result of speed gain, trim it out left to level the aeroplane.

Congratulations, pilot! You have successfully taken off in the famous A6M2 Reisen! Now for some real fun!

==== In-flight Operations ====

Controls:

*Ctrl+b: Engine Boost. This activates a compressor under the central manifold that revs the engine to high RPMs. Can be hit twice. On the third hit it will go back to normal mode. Observe the RPM increase in the little meter to the lower right of the cockpit dash, filled in halfway in red. The needle will jump forward when Ctrl+b is hit.

*Be wary of overheating. Although it isn't implemented in FGFS, the engine will overheat. To counter this problem, observe your speed meter and adjust engine throttle/boost as needed.

'''''To be continued...! Questions? Comments? Feel free to send a request to me [mailto:helldiversquadron@gmail.com Send a request to Friend].'''''

---Hello, all! This is Friend here to remind you about the upcoming air combat e-book, ''Intercept at 11,000''. The book will be on dogfighting, maneuvering, and smart choices during aerial engagements. Targeted audience: FlightGear and War Thunder community, but can be applied elsewhere.

For more information, please contact HSOTF at helldiversquadron.wordpress.com. Thanks!

A6M2 Zero manual

2014-07-17T02:51:41Z

JayVS:

== A6M2 Reisen "Zero" Fighter Aircraft ==

=== A Little History ===

[[File:Http://wiki.flightgear.org/File:A6M2.gif|framed|right|A6M2 Zero in a light left bank over the Pacific]]

The A6M-series aircraft developed during the Second World War were exceptional warplanes employed by the Imperial Japanese forces, namely the Imperial Navy. The A6M2 Reisen, nicknamed the "Zero", was by far the most used and most recognizable Japanese fighter. The A6M5 and A6M8 were power-packed fighters decked out with 20mm cannon and 7.7mm machine guns. The A6M2 was the easiest to handle, more maneuverable, and had decent range. Above all, it was carrier-capable, and this aided the Imperial cause during the Pacific War.

The Reisen's most problematic issue was survivability. The Zero was known to the Americans as the "paper tube", due to its lack of armour and structural defenses. The aircraft lit up easily, and practically any gun in the Allied arsenal could shoot down one of these fighters.

The A6M2 was remarkable in its abilities as a turning fighter. The American tactic was centered around speed, armour, and heavy armament, and the Japanese exploited this to the limit. The Zero was initially turned down by many manufacturers after the military specified how spectacular the requirements would have to be, but a company called Mitsubishi took up the challenge and developed one of the most successful fighters of World War II. The Reisen was incredibly difficult to line up in a gunsight at low speeds; however, at higher velocities the aircraft's controls would start to be sluggish or even seize up altogether. The Allies countered this frightening aspect with their "Cat" series. These included the Navy variants of the Bearcat, Hellcat, Tigercat, and the Wildcat. The Hellcat was by far the best answer to the growing problem of the enemy over the horizon.

Zeroes continued to fight till they breathed their last in 1945. The Allies were victorious after bloody wars in the Pacific and the European theatre. The wars in Africa and China were all but over, and the Americans began their search for a surviving Reisen.

Only one airworthy A6M2 remains today, and the other two known about lie at the bottom of the Pacific, where teams of divers and historians have probed the depths, searching for answers to the legendary fighter, the A6M2 Reisen "Zero".

=== The Manual ===

==== A6M2 Controls====

*CTRL-B: Toggle Engine Boost (2 stages)
*CTRL-D: Open / Close Canopy
*CTRL-L: Toggle Tailwheel Lock
*SHIFT-C: Catapult Launch
*O/o: Down/up Hook
*L: Engage Launch bar
*l: Open Livery Dialog

==== Summary ====

This manual is intended for use in FlightGear, and is not related to any flight dynamics in the real world. Please note, the Zero's FDM is not very accurate, but this manual will serve mainly to help with engine procedures and dogfighting readiness. Also, for information on the tailwheel and basic ground maneuvering, visit the [http://forum.flightgear.org/viewtopic.php?f=49&t=23554 FG Forum topic--A6M2 Zero Ground Maneuvering].

==== Ground Start-up and Take-off====

To start the A6M2 in FlightGear isn't difficult in the least. Based solely on the simulator and not real procedures, here is how to work the engine on start-up.
------------------------------------------
Cold morning? Give the throttle around 15%. If it's any old day (or night), go over the review check.

As follows:

* Assuming you are on a runway, and if not then scroll down for a link to ground maneuvering in the Zero:
* Check any lights (the Zero currently has none, so night flight is near suicidal unless you are flawless in IFR).
* Raise throttle to 10%. (For a snappy start, which is terrible for the engine life but may be necessary if you have to get away from the airfield in a hurry will be best, raise the throttle to around 50% and lever it around till the starter ignites.)
* Check fuel. This is just a reminder as you should have already.
* Check battery (not currently a problem; the Reisen is really an out-of-the-box fighter). On?
* Primer (same issue)? 5x?
* Now make sure your canopy is thoroughly latched. If it isn't the dust and whatnot that gets kicked up from the propeller will hit you in the face.
* Look over your shoulders (you should have approximately two shoulders, if I recall correctly) and throw your stick around to assure your control surfaces are in working order. Twist the stick if it is capable for rudder. If you are a keyboard and mouse user, apply these techniques as needed. (K&M users: rudder is usually the Enter key and the Insert key. On occasion it is the 0 key. Control surfaces such as ailerons and elevators are triggered by your mouse whilst in Control Mode [right-click once].) Go to the limit to make sure your aircraft is in peak condition. This is required of any pilot regardless of occupation, even to today.
* Now make sure your parking brake is set to ON.
* Flaps one notch. If your strip is short, two is OK. No more than two notches, as the final ones are for landing ONLY.
* Throttle 90% military power AFTER releasing brake.
* The Zero will lurch to the left and nose down after about 60 knots (could be wrong about the speed there), so be ready to give it a little right rudder to balance it out. The fighter likes to josh around on the takeoff, so just be ready to counter its humor with rudder and watch your speed.
* The Zero is remarkable in its minimum rotation speed. After the plane has nosed down and is level, pull back on the stick and rotate around 60-80 KIAS.
* Retract gear ASAP.
* Retract flaps one notch after reaching 90 KIAS.
* Retract final notch of flaps after 100 KIAS.
* The Zero will sink after retracting flaps. No worries. Just counter with elevator.
* IMPORTANT: When at slower speeds the Zero is influenced heavily by the prop torque. To counter this, tap the right aileron trim. (T16000M Thrustmaster users: tap twice on the button assigned.)
* When reaching high speeds in a dive or just as a result of speed gain, trim it out left to level the aeroplane.

Congratulations, pilot! You have successfully taken off in the famous A6M2 Reisen! Now for some real fun!

==== In-flight Operations ====

Controls:

*Ctrl+b: Engine Boost. This activates a compressor under the central manifold that revs the engine to high RPMs. Can be hit twice. On the third hit it will go back to normal mode. Observe the RPM increase in the little meter to the lower right of the cockpit dash, filled in halfway in red. The needle will jump forward when Ctrl+b is hit.

*Be wary of overheating. Although it isn't implemented in FGFS, the engine will overheat. To counter this problem, observe your speed meter and adjust engine throttle/boost as needed.

'''''To be continued...! Questions? Comments? Feel free to send a request to me [mailto:helldiversquadron@gmail.com Send a request to Friend].'''''

---Hello, all! This is Friend here to remind you about the upcoming air combat e-book, ''Intercept at 11,000''. The book will be on dogfighting, maneuvering, and smart choices during aerial engagements. Targeted audience: FlightGear and War Thunder community, but can be applied elsewhere.

For more information, please contact HSOTF at helldiversquadron.wordpress.com. Thanks!

A6M2 Zero manual

2014-07-17T02:44:49Z

JayVS:

== A6M2 Reisen "Zero" Fighter Aircraft ==

=== A Little History ===

The A6M-series aircraft developed during the Second World War were exceptional warplanes employed by the Imperial Japanese forces, namely the Imperial Navy. The A6M2 Reisen, nicknamed the "Zero", was by far the most used and most recognizable Japanese fighter. The A6M5 and A6M8 were power-packed fighters decked out with 20mm cannon and 7.7mm machine guns. The A6M2 was the easiest to handle, more maneuverable, and had decent range. Above all, it was carrier-capable, and this aided the Imperial cause during the Pacific War.

The Reisen's most problematic issue was survivability. The Zero was known to the Americans as the "paper tube", due to its lack of armour and structural defenses. The aircraft lit up easily, and practically any gun in the Allied arsenal could shoot down one of these fighters.

The A6M2 was remarkable in its abilities as a turning fighter. The American tactic was centered around speed, armour, and heavy armament, and the Japanese exploited this to the limit. The Zero was initially turned down by many manufacturers after the military specified how spectacular the requirements would have to be, but a company called Mitsubishi took up the challenge and developed one of the most successful fighters of World War II. The Reisen was incredibly difficult to line up in a gunsight at low speeds; however, at higher velocities the aircraft's controls would start to be sluggish or even seize up altogether. The Allies countered this frightening aspect with their "Cat" series. These included the Navy variants of the Bearcat, Hellcat, Tigercat, and the Wildcat. The Hellcat was by far the best answer to the growing problem of the enemy over the horizon.

Zeroes continued to fight till they breathed their last in 1945. The Allies were victorious after bloody wars in the Pacific and the European theatre. The wars in Africa and China were all but over, and the Americans began their search for a surviving Reisen.

Only one airworthy A6M2 remains today, and the other two known about lie at the bottom of the Pacific, where teams of divers and historians have probed the depths, searching for answers to the legendary fighter, the A6M2 Reisen "Zero".

=== The Manual ===

==== A6M2 Controls====

*CTRL-B: Toggle Engine Boost (2 stages)
*CTRL-D: Open / Close Canopy
*CTRL-L: Toggle Tailwheel Lock
*SHIFT-C: Catapult Launch
*O/o: Down/up Hook
*L: Engage Launch bar
*l: Open Livery Dialog

==== Summary ====

This manual is intended for use in FlightGear, and is not related to any flight dynamics in the real world. Please note, the Zero's FDM is not very accurate, but this manual will serve mainly to help with engine procedures and dogfighting readiness. Also, for information on the tailwheel and basic ground maneuvering, visit the [http://forum.flightgear.org/viewtopic.php?f=49&t=23554 FG Forum topic--A6M2 Zero Ground Maneuvering].

==== Ground Start-up and Take-off====

To start the A6M2 in FlightGear isn't difficult in the least. Based solely on the simulator and not real procedures, here is how to work the engine on start-up.
------------------------------------------
Cold morning? Give the throttle around 15%. If it's any old day (or night), go over the review check.

As follows:

* Assuming you are on a runway, and if not then scroll down for a link to ground maneuvering in the Zero:
* Check any lights (the Zero currently has none, so night flight is near suicidal unless you are flawless in IFR).
* Raise throttle to 10%. (For a snappy start, which is terrible for the engine life but may be necessary if you have to get away from the airfield in a hurry will be best, raise the throttle to around 50% and lever it around till the starter ignites.)
* Check fuel. This is just a reminder as you should have already.
* Check battery (not currently a problem; the Reisen is really an out-of-the-box fighter). On?
* Primer (same issue)? 5x?
* Now make sure your canopy is thoroughly latched. If it isn't the dust and whatnot that gets kicked up from the propeller will hit you in the face.
* Look over your shoulders (you should have approximately two shoulders, if I recall correctly) and throw your stick around to assure your control surfaces are in working order. Twist the stick if it is capable for rudder. If you are a keyboard and mouse user, apply these techniques as needed. (K&M users: rudder is usually the Enter key and the Insert key. On occasion it is the 0 key. Control surfaces such as ailerons and elevators are triggered by your mouse whilst in Control Mode [right-click once].) Go to the limit to make sure your aircraft is in peak condition. This is required of any pilot regardless of occupation, even to today.
* Now make sure your parking brake is set to ON.
* Flaps one notch. If your strip is short, two is OK. No more than two notches, as the final ones are for landing ONLY.
* Throttle 90% military power AFTER releasing brake.
* The Zero will lurch to the left and nose down after about 60 knots (could be wrong about the speed there), so be ready to give it a little right rudder to balance it out. The fighter likes to josh around on the takeoff, so just be ready to counter its humor with rudder and watch your speed.
* The Zero is remarkable in its minimum rotation speed. After the plane has nosed down and is level, pull back on the stick and rotate around 60-80 KIAS.
* Retract gear ASAP.
* Retract flaps one notch after reaching 90 KIAS.
* Retract final notch of flaps after 100 KIAS.
* The Zero will sink after retracting flaps. No worries. Just counter with elevator.
* IMPORTANT: When at slower speeds the Zero is influenced heavily by the prop torque. To counter this, tap the right aileron trim. (T16000M Thrustmaster users: tap twice on the button assigned.)
* When reaching high speeds in a dive or just as a result of speed gain, trim it out left to level the aeroplane.

Congratulations, pilot! You have successfully taken off in the famous A6M2 Reisen! Now for some real fun!

==== In-flight Operations ====

Controls:

*Ctrl+b: Engine Boost. This activates a compressor under the central manifold that revs the engine to high RPMs. Can be hit twice. On the third hit it will go back to normal mode. Observe the RPM increase in the little meter to the lower right of the cockpit dash, filled in halfway in red. The needle will jump forward when Ctrl+b is hit.

*Be wary of overheating. Although it isn't implemented in FGFS, the engine will overheat. To counter this problem, observe your speed meter and adjust engine throttle/boost as needed.

'''''To be continued...! Questions? Comments? Feel free to send a request to me [mailto:helldiversquadron@gmail.com Send a request to Friend].'''''

---Hello, all! This is Friend here to remind you about the upcoming air combat e-book, ''Intercept at 11,000''. The book will be on dogfighting, maneuvering, and smart choices during aerial engagements. Targeted audience: FlightGear and War Thunder community, but can be applied elsewhere.

For more information, please contact HSOTF at helldiversquadron.wordpress.com. Thanks!

A6M2 Zero manual

2014-07-17T02:42:56Z

JayVS: The Official FGFS Reisen Manual

== A6M2 Reisen "Zero" Fighter Aircraft ==

=== A Little History ===

The A6M-series aircraft developed during the Second World War were exceptional warplanes employed by the Imperial Japanese forces, namely the Imperial Navy. The A6M2 Reisen, nicknamed the "Zero", was by far the most used and most recognizable Japanese fighter. The A6M5 and A6M8 were power-packed fighters decked out with 20mm cannon and 7.7mm machine guns. The A6M2 was the easiest to handle, more maneuverable, and had decent range. Above all, it was carrier-capable, and this aided the Imperial cause during the Pacific War.

The Reisen's most problematic issue was survivability. The Zero was known to the Americans as the "paper tube", due to its lack of armour and structural defenses. The aircraft lit up easily, and practically any gun in the Allied arsenal could shoot down one of these fighters.

The A6M2 was remarkable in its abilities as a turning fighter. The American tactic was centered around speed, armour, and heavy armament, and the Japanese exploited this to the limit. The Zero was initially turned down by many manufacturers after the military specified how spectacular the requirements would have to be, but a company called Mitsubishi took up the challenge and developed one of the most successful fighters of World War II. The Reisen was incredibly difficult to line up in a gunsight at low speeds; however, at higher velocities the aircraft's controls would start to be sluggish or even seize up altogether. The Allies countered this frightening aspect with their "Cat" series. These included the Navy variants of the Bearcat, Hellcat, Tigercat, and the Wildcat. The Hellcat was by far the best answer to the growing problem of the enemy over the horizon.

Zeroes continued to fight till they breathed their last in 1945. The Allies were victorious after bloody wars in the Pacific and the European theatre. The wars in Africa and China were all but over, and the Americans began their search for a surviving Reisen.

Only one airworthy A6M2 remains today, and the other two known about lie at the bottom of the Pacific, where teams of divers and historians have probed the depths, searching for answers to the legendary fighter, the A6M2 Reisen "Zero".

=== The Manual ===

==== A6M2 Controls====

*CTRL-B: Toggle Engine Boost (2 stages)
*CTRL-D: Open / Close Canopy
*CTRL-L: Toggle Tailwheel Lock
*SHIFT-C: Catapult Launch
*O/o: Down/up Hook
*L: Engage Launch bar
*l: Open Livery Dialog

==== Summary ====

This manual is intended for use in FlightGear, and is not related to any flight dynamics in the real world. Please note, the Zero's FDM is not very accurate, but this manual will serve mainly to help with engine procedures and dogfighting readiness. Also, for information on the tailwheel and basic ground maneuvering, visit the [http://forum.flightgear.org/viewtopic.php?f=49&t=23554 FG Forum topic--A6M2 Zero Ground Maneuvering].

==== Ground Start-up and Take-off====

To start the A6M2 in FlightGear isn't difficult in the least. Based solely on the simulator and not real procedures, here is how to work the engine on start-up.
------------------------------------------
Cold morning? Give the throttle around 15%. If it's any old day (or night), go over the review check.

As follows:

* Assuming you are on a runway, and if not then scroll down for a link to ground maneuvering in the Zero:
* Check any lights (the Zero currently has none, so night flight is near suicidal unless you are flawless in IFR).
* Raise throttle to 10%. (For a snappy start, which is terrible for the engine life but may be necessary if you have to get away from the airfield in a hurry will be best, raise the throttle to around 50% and lever it around till the starter ignites.)
* Check fuel. This is just a reminder as you should have already.
* Check battery (not currently a problem; the Reisen is really an out-of-the-box fighter). On?
* Primer (same issue)? 5x?
* Now make sure your canopy is thoroughly latched. If it isn't the dust and whatnot that gets kicked up from the propeller will hit you in the face.
* Look over your shoulders (you should have approximately two shoulders, if I recall correctly) and throw your stick around to assure your control surfaces are in working order. Twist the stick if it is capable for rudder. If you are a keyboard and mouse user, apply these techniques as needed. (K&M users: rudder is usually the Enter key and the Insert key. On occasion it is the 0 key. Control surfaces such as ailerons and elevators are triggered by your mouse whilst in Control Mode [right-click once].) Go to the limit to make sure your aircraft is in peak condition. This is required of any pilot regardless of occupation, even to today.
* Now make sure your parking brake is set to ON.
* Flaps one notch. If your strip is short, two is OK. No more than two notches, as the final ones are for landing ONLY.
* Throttle 90% military power AFTER releasing brake.
* The Zero will lurch to the left and nose down after about 60 knots (could be wrong about the speed there), so be ready to give it a little right rudder to balance it out. The fighter likes to josh around on the takeoff, so just be ready to counter its humor with rudder and watch your speed.
* The Zero is remarkable in its minimum rotation speed. After the plane has nosed down and is level, pull back on the stick and rotate around 60-80 KIAS.
* Retract gear ASAP.
* Retract flaps one notch after reaching 90 KIAS.
* Retract final notch of flaps after 100 KIAS.
* The Zero will sink after retracting flaps. No worries. Just counter with elevator.
* IMPORTANT: When at slower speeds the Zero is influenced heavily by the prop torque. To counter this, tap the right aileron trim. (T16000M Thrustmaster users: tap twice on the button assigned.)
* When reaching high speeds in a dive or just as a result of speed gain, trim it out left to level the aeroplane.

Congratulations, pilot! You have successfully taken off in the famous A6M2 Reisen! Now for some real fun!

==== In-flight Operations ====

Controls:

*Ctrl+b: Engine Boost. This activates a compressor under the central manifold that revs the engine to high RPMs. Can be hit twice. On the third hit it will go back to normal mode. Observe the RPM increase in the little meter to the lower right of the cockpit dash, filled in halfway in red. The needle will jump forward when Ctrl+b is hit.

*Be wary of overheating. Although it isn't implemented in FGFS, the engine will overheat. To counter this problem, observe your speed meter and adjust engine throttle/boost as needed.

'''''To be continued...! Questions? Comments? Feel free to send a request to me [http://mailto:helldiversquadron@gmail.com Send a request to Friend].'''''

---Hello, all! This is Friend here to remind you about the upcoming air combat e-book, ''Intercept at 11,000''. The book will be on dogfighting, maneuvering, and smart choices during aerial engagements. Targeted audience: FlightGear and War Thunder community, but can be applied elsewhere.

For more information, please contact HSOTF at helldiversquadron.wordpress.com. Thanks!

User:Friend

2014-06-13T19:53:25Z

JayVS: Callsign: Friend

Callsign "Friend":

http://mpserver15.flightgear.org/modules/fgtracker/?FUNCT=FLIGHTS&CALLSIGN=Friend

Registered Commander of Helldiver Squadron Offensive Tactical Force (HSOTF), a virtual air command group.

Flies mainly fighters of all types, and on occasion bombers.

Member of FGUK.

Former callsign: "ForHire".

Registered under HSOTF: 29 kills, 3 losses

A-10 Thunderbolt II FDM

2014-04-16T13:47:35Z

JayVS: The A-10 Thunderbolt II's FDM for beginners

First Draft: April 14, 2014
Subject: A-10 Thunderbolt II/Warthog Close Support Attack Jet Flight Dynamics
Type: Documentation and Analysis
Author: Friend, USAAF, and others

The A-10 Thunderbolt II

The A-10 Thunderbolt II, better known as the “Warthog”, is a fixed-wing attack aircraft designed by Fairchild Republic and is operated exclusively by the United States of America Air Force (USAF). The aircraft is powered by two General Electric TF34-GE-100A turbofans, 9,065 lbf (40.32 kN) each. The A-10 is straight-winged, with a wingspan of 17.53 meters. It can carry a wide variety of ordnance and payload, but is better known for its 30 mm rotary cannon affixed off-center in the nose. It has the only USAAF aircraft ever designed solely for close support roles, and has proved itself on the battlefield as the ultimate ground support aircraft.
The A-10A has 11 (8× under-wing and 3× under-fuselage pylon stations) with a capacity of 16,000 lb (7,260 kg) and the capability to carry the following payload:

• Rockets:
4× LAU-61/LAU-68 rocket pods (each with 19× / 7× Hydra 70 mm rockets, respectively)
4× LAU-5003 rocket pods (each with 19× CRV7 70 mm rockets)
6× LAU-10 rocket pods (each with 4× 127 mm (5.0 in) Zuni rockets)
• Missiles:
2× AIM-9 Sidewinders air-to-air missiles for self-defense
6× AGM-65 Maverick air-to-surface missiles
• Bombs:
Mark 80 series of unguided iron bombs or
Mk 77 incendiary bombs or
BLU-1, BLU-27/B Rockeye II, Mk20, BL-755[146] and CBU-52/58/71/87/89/97 cluster bombs or
Paveway series of Laser-guided bombs or
Joint Direct Attack Munition (A-10C)[147] or
Wind Corrected Munitions Dispenser (A-10C)
• Other:
SUU-42A/A Flares/Infrared decoys and chaff dispenser pod or
AN/ALQ-131 or AN/ALQ-184 ECM pods or
Lockheed Martin Sniper XR or LITENING targeting pods (A-10C) or
2× 600 US gallon Sargent Fletcher drop tanks for increased range/loitering time.

The A-10A will be the aircraft variant discussed here for the purposes of flight dynamics.

A-10A:
The A-10 has the tendency to lose center of gravity (COG) when the pitch is at its extremes. The aircraft cannot pull out of a harsh dive easily, nor can it climb quickly. At a level pitch of 0, maintaining 330 knots (kt), the pilot cannot simply pull back and hope to loop completely. The aircraft will stall at 120 kt and will continue to lose airspeed unless it is put into a dive to regain such. Once over 130 kt is reached, the dive must be leveled out, but the A-10 is slow to react in these situations. A full loop is not advised unless you have over 350 kt of airspeed to start with and all control surfaces are level—this includes flaps, spoilers, etc.
A snap roll is not an issue if the aircraft is lightly loaded and has reasonable speed. A minimum of 150 kt is required for a very quick snap roll. A slow roll requires level pitch and constant adjustments to keep it so, as well as an airspeed of 200 KIAS for a guaranteed safe roll. The A-10’s aileron systems are quick to react but if combined with faulty elevator levels it can be fatal.
The engines, once spooled to full military power, are relentless in their ability to pull the A-10 from the ground into the air. They are large and positioned out of the aerodynamic center (ADC), thus aiding in preventing excessive pitch moment (PIM).
Fuel is a constant worry. As it is burned the aircraft will regain its ability to perform maneuvers previously unreachable. Rolls and loops are now an option; however, it is necessary to maintain a throttle below the highest level—otherwise, the fuel consumption will be too high.
The weapon primarily used is the GAU-8 30 mm Avenger rotary cannon, capable of firing incendiary and depleted-uranium armor-piercing rounds. The cannon fires a fixed rate of 3,900 rounds per minute (rpm). It is the main weapon and is optimized for a slant range of 4,000 feet (1,220 m) with the A-10 in a 30 degree dive. Its accuracy is enough to place 80% of its shots within a 40-foot (12.4 m) diameter circle from 4,000 feet (1,220 m) while in flight.
The ordnance available in FlightGear is limited, and the best setup for ground attack is as follows (see the picture):

[[File:Payload Options.png|thumb|Options in the A-10]]

Notice the gross weight. This is your MTOW, or Maximum Take-Off Weight.

Guidelines:
• Don’t pull fast on the stick, up or down.
• When changing pitch, keep an eye on the P-ladder.
• If it starts to buck when you nose down, pull up while jinking the stick from side to side, just slightly. That will pull you out of this problem.
• If you’ve pulled up to high, then you will start to spin uncontrollably. This will be fatal in a matter of seconds unless you center the stick and jink the stick slightly in all four directions. Place throttle at 50% military power. Dive. Pull out sharply while not pulling to the extreme—that’s what got you into this situation.
• When turning, you are liable to spin like the above situation unless you adjust pitch to slightly above the 0.0-degree mark while pulling to the side you want. It is essential that the pitch is constantly checked.
• The A-10 also has a reaction system for the pitch—it takes a few times of pulling back to make a difference. If you pull back a little, it will make a minor adjustment, and a little more will do the same. But if you pull back a little farther, it suddenly pulls up sharply. You must be aware of this or you can end up bucking or spinning.
• Firing the gun requires focus and zoom. Zoom in to the HUD so you can aim accurately. Come down at a 30-degree dive, preferably, and fire around 4,000 ft from the target. The aircraft will shake from side to side as the rudders attempt to automatically correct the recoil symptoms. You must also correct them, though, as it will significantly slow and even stall the aircraft if you fire too long. Fire in one to two-second bursts—never longer than three seconds; this is to avoid flight issues. It will also overheat the barrels if you fire too long, although this has not been implemented in FlightGear.
• When firing the 30 mm, make sure to watch your round counter—it is in blue digits off to the left side below the HUD glass; it is below the switches board under the HUD glass.
• To aim the MK-82s, switch from NAV mode to CCIP on the HUD dial, as you should already have done. CCIP will provide the same HUD but will include an aiming recticle. The recticle is a circle with a single dot in the center. The circle represents the max blast radius but, depending on the terrain, this might not always be the case. Never release bombs when you are close the ground. The CCIP only works when the correct angle is reached to drop the bombs point-first. This gets you rather close to the ground, and that can be hazardous. To avoid this, go full throttle, dive at a 15-degree slant, and drop as soon as the recticle shows up on the HUD. Of course you may want to make sure the target is in the sights before you release the ordnance. The MK-82s are free-fall iron bombs, meaning that they have no guidance systems in place to get them to their target. Instead, they go where you go. A few users on YouTube made the mistake of telling viewers to aim bombs with the velocity marker (the little crosshair circle that moves around), or VM, which predicts via computer where your craft will go next. This IS NOT true. Do not aim any ordnance with the VM. That will get you killed. It is worth it to train and understand that you won’t get it perfect on the first few runs. Strafing is difficult in regards to aiming a gun that moves the aircraft around, but aiming a free-fall bomb is even harder, depending on the terrain.
• The weapons were mentioned to tell you about the flight dynamics, or FDM. When you release a payload, the A-10 will lurch to that side (unless you have activated Wings Level or something), and you will have to adjust. This can be treacherous if you are in mountainous terrain and can’t simply go where you want to. Think ahead what side will lurch and be prepared to compensate. LAU-68s won’t have as much as an effect, but releasing tanks or bombs will. Firing the AIM-9s depends on what mood FlightGear is in, and I have confirmed this with quite a few fellow pilots. HSOTF13, for example, fired the AIM-9s at a mountainside to relieve the A-10 he was flying (he was suffering engine failure and needed to jettison everything), only to discover that it did nothing to help. He was defenseless and falling out of the sky. In contrast, I fired an AIM-9 at a dummy airliner in a scenario. Knowing that it didn’t have an effect yesterday, I figured it would be fine. Flying at 14,000 ft and suffering a lurch to the left ended my mission—I had pulled too sharp and lost a control surface—the aileron, courtesy of Bombable. Thank you, Flug.
• The weapons can be activated on the weapons panel under the Master Arm and Gun Rate switches. To configure your payload, go to Menu>Fuel & Payload.
• The A-10 is a joy to fly once you have mastered the feelings and movements of this aircraft. Don’t play around—you will die.
• Rule of thumb—know your limits, and know the A-10’s.
• In the near future HSOTF will implement a better FDM, as well as expanding the payload, missile and bomb guidance, countermeasures, and gun rate. We will also try to implement the vision of the future—TV screens in FlightGear. The A-10 relies on these for targeting, but it is hard to do it by HUD alone in FlightGear.
• Don’t EVER get into a dogfight. The AIM-9s don’t track, despite what they say, and you will die if you engage a fighter. Not only can they out-maneuver you, but they are equipped with weapons for fighting in the air. You are slow, not by any means agile, and, though you are designed for high-survivability, you will find yourself staring at the AIM-120 streaking at you.

That’s the first draft. Soon I’ll expand with the help of my fellow HSOTF pilots.

G’day, mates!

--Friend, Commander of HSOTF and Chief Instructor

A-10 Thunderbolt II FDM

2014-04-15T04:02:40Z

JayVS: A Helping Hand with the A-10's unique FDM

First Draft: April 14, 2014
Subject: A-10 Thunderbolt II/Warthog Close Support Attack Jet Flight Dynamics
Type: Documentation and Analysis
Author: Friend, USAAF, and others

The A-10 Thunderbolt II

The A-10 Thunderbolt II, better known as the “Warthog”, is a fixed-wing attack aircraft designed by Fairchild Republic and is operated exclusively by the United States of America Air Force (USAAF). The aircraft is powered by two General Electric TF34-GE-100A turbofans, weighing 9,065 lbf (40.32 kN) each. The A-10 is straight-winged, with a wingspan of 17.53 meters. It can carry a wide variety of ordnance and payload, but is better known for its 30 mm rotary cannon affixed off-center in the nose. It has the only USAAF aircraft ever designed solely for close support roles, and has proved itself on the battlefield as the ultimate ground support aircraft.
The A-10A has 11 (8× under-wing and 3× under-fuselage pylon stations) with a capacity of 16,000 lb (7,260 kg) and the capability to carry the following payload:

• Rockets:
4× LAU-61/LAU-68 rocket pods (each with 19× / 7× Hydra 70 mm rockets, respectively)
4× LAU-5003 rocket pods (each with 19× CRV7 70 mm rockets)
6× LAU-10 rocket pods (each with 4× 127 mm (5.0 in) Zuni rockets)
• Missiles:
2× AIM-9 Sidewinders air-to-air missiles for self-defense
6× AGM-65 Maverick air-to-surface missiles
• Bombs:
Mark 80 series of unguided iron bombs or
Mk 77 incendiary bombs or
BLU-1, BLU-27/B Rockeye II, Mk20, BL-755[146] and CBU-52/58/71/87/89/97 cluster bombs or
Paveway series of Laser-guided bombs or
Joint Direct Attack Munition (A-10C)[147] or
Wind Corrected Munitions Dispenser (A-10C)
• Other:
SUU-42A/A Flares/Infrared decoys and chaff dispenser pod or
AN/ALQ-131 or AN/ALQ-184 ECM pods or
Lockheed Martin Sniper XR or LITENING targeting pods (A-10C) or
2× 600 US gallon Sargent Fletcher drop tanks for increased range/loitering time.

The A-10A will be the aircraft variant discussed here for the purposes of flight dynamics.

A-10A:
The A-10 has the tendency to lose center of gravity (COG) when the pitch is at its extremes. The aircraft cannot pull out of a harsh dive easily, nor can it climb quickly. At a level pitch of 0, maintaining 330 knots (kt), the pilot cannot simply pull back and hope to loop completely. The aircraft will stall at 120 kt and will continue to lose airspeed unless it is put into a dive to regain such. Once over 130 kt is reached, the dive must be leveled out, but the A-10 is slow to react in these situations. A full loop is not advised unless you have over 350 kt of airspeed to start with and all control surfaces are level—this includes flaps, spoilers, etc.
A snap roll is not an issue if the aircraft is lightly loaded and has reasonable speed. A minimum of 150 kt is required for a very quick snap roll. A slow roll requires level pitch and constant adjustments to keep it so, as well as an airspeed of 200 KIAS for a guaranteed safe roll. The A-10’s aileron systems are quick to react but if combined with faulty elevator levels it can be fatal.
The engines, once spooled to full military power, are relentless in their ability to pull the A-10 from the ground into the air. They are large and positioned out of the aerodynamic center (ADC), thus aiding in preventing excessive pitch moment (PIM).
Fuel is a constant worry. As it is burned the aircraft will regain its ability to perform maneuvers previously unreachable. Rolls and loops are now an option; however, it is necessary to maintain a throttle below the highest level—otherwise, the fuel consumption will be too high.
The weapon primarily used is the GAU-8 30 mm Avenger rotary cannon, capable of firing incendiary and depleted-uranium armor-piercing rounds. The cannon fires a fixed rate of 3,900 rounds per minute (rpm). It is the main weapon and is optimized for a slant range of 4,000 feet (1,220 m) with the A-10 in a 30 degree dive. Its accuracy is enough to place 80% of its shots within a 40-foot (12.4 m) diameter circle from 4,000 feet (1,220 m) while in flight.
The ordnance available in FlightGear is limited, and the best setup for ground attack is as follows (see the picture):

[[File:Payload Options.png|thumb|Options in the A-10]]

Notice the gross weight. This is your MTOW, or Maximum Take-Off Weight.

Guidelines:
• Don’t pull fast on the stick, up or down.
• When changing pitch, keep an eye on the P-ladder.
• If it starts to buck when you nose down, pull up while jinking the stick from side to side, just slightly. That will pull you out of this problem.
• If you’ve pulled up to high, then you will start to spin uncontrollably. This will be fatal in a matter of seconds unless you center the stick and jink the stick slightly in all four directions. Place throttle at 50% military power. Dive. Pull out sharply while not pulling to the extreme—that’s what got you into this situation.
• When turning, you are liable to spin like the above situation unless you adjust pitch to slightly above the 0.0-degree mark while pulling to the side you want. It is essential that the pitch is constantly checked.
• The A-10 also has a reaction system for the pitch—it takes a few times of pulling back to make a difference. If you pull back a little, it will make a minor adjustment, and a little more will do the same. But if you pull back a little farther, it suddenly pulls up sharply. You must be aware of this or you can end up bucking or spinning.
• Firing the gun requires focus and zoom. Zoom in to the HUD so you can aim accurately. Come down at a 30-degree dive, preferably, and fire around 4,000 ft from the target. The aircraft will shake from side to side as the rudders attempt to automatically correct the recoil symptoms. You must also correct them, though, as it will significantly slow and even stall the aircraft if you fire too long. Fire in one to two-second bursts—never longer than three seconds; this is to avoid flight issues. It will also overheat the barrels if you fire too long, although this has not been implemented in FlightGear.
• When firing the 30 mm, make sure to watch your round counter—it is in blue digits off to the left side below the HUD glass; it is below the switches board under the HUD glass.
• To aim the MK-82s, switch from NAV mode to CCIP on the HUD dial, as you should already have done. CCIP will provide the same HUD but will include an aiming recticle. The recticle is a circle with a single dot in the center. The circle represents the max blast radius but, depending on the terrain, this might not always be the case. Never release bombs when you are close the ground. The CCIP only works when the correct angle is reached to drop the bombs point-first. This gets you rather close to the ground, and that can be hazardous. To avoid this, go full throttle, dive at a 15-degree slant, and drop as soon as the recticle shows up on the HUD. Of course you may want to make sure the target is in the sights before you release the ordnance. The MK-82s are free-fall iron bombs, meaning that they have no guidance systems in place to get them to their target. Instead, they go where you go. A few users on YouTube made the mistake of telling viewers to aim bombs with the velocity marker (the little crosshair circle that moves around), or VM, which predicts via computer where your craft will go next. This IS NOT true. Do not aim any ordnance with the VM. That will get you killed. It is worth it to train and understand that you won’t get it perfect on the first few runs. Strafing is difficult in regards to aiming a gun that moves the aircraft around, but aiming a free-fall bomb is even harder, depending on the terrain.
• The weapons were mentioned to tell you about the flight dynamics, or FDM. When you release a payload, the A-10 will lurch to that side (unless you have activated Wings Level or something), and you will have to adjust. This can be treacherous if you are in mountainous terrain and can’t simply go where you want to. Think ahead what side will lurch and be prepared to compensate. LAU-68s won’t have as much as an effect, but releasing tanks or bombs will. Firing the AIM-9s depends on what mood FlightGear is in, and I have confirmed this with quite a few fellow pilots. HSOTF13, for example, fired the AIM-9s at a mountainside to relieve the A-10 he was flying (he was suffering engine failure and needed to jettison everything), only to discover that it did nothing to help. He was defenseless and falling out of the sky. In contrast, I fired an AIM-9 at a dummy airliner in a scenario. Knowing that it didn’t have an effect yesterday, I figured it would be fine. Flying at 14,000 ft and suffering a lurch to the left ended my mission—I had pulled too sharp and lost a control surface—the aileron, courtesy of Bombable. Thank you, Flug.
• The weapons can be activated on the weapons panel under the Master Arm and Gun Rate switches. To configure your payload, go to Menu>Fuel & Payload.
• The A-10 is a joy to fly once you have mastered the feelings and movements of this aircraft. Don’t play around—you will die.
• Rule of thumb—know your limits, and know the A-10’s.
• In the near future HSOTF will implement a better FDM, as well as expanding the payload, missile and bomb guidance, countermeasures, and gun rate. We will also try to implement the vision of the future—TV screens in FlightGear. The A-10 relies on these for targeting, but it is hard to do it by HUD alone in FlightGear.
• Don’t EVER get into a dogfight. The AIM-9s don’t track, despite what they say, and you will die if you engage a fighter. Not only can they out-maneuver you, but they are equipped with weapons for fighting in the air. You are slow, not by any means agile, and, though you are designed for high-survivability, you will find yourself staring at the AIM-120 streaking at you.

That’s the first draft. Soon I’ll expand with the help of my fellow HSOTF pilots.

G’day, mates!

--Friend, Commander of HSOTF and Chief Instructor

File:Payload Options.png

2014-04-15T04:00:58Z

JayVS: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Options in the A-10}}
|date=2014-04-14 20:59:25
|source={{own}}
|author=[[User:JayVS|JayVS]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

F-16CJ HUD Project Newsletter

2014-02-06T17:04:36Z

JayVS: The F-16CJ's HUD Project Newsletter

[[File:F-16CJ HUD on B-17F AI Bomber Formation.png|thumb|F-16CJ HUD on B-17F AI Bomber Formation, 2014-02-05]]

[[File:F-16CJ HUD 2, Mirage 2000-5 Import.png|thumb|f-16cj HUD 2]]

The F-16CJ is a rendition of the F-16 Fighting Falcon fighter jet, modeled and scripted by members of [http://www.fguk.eu FGUK].

It has a fully functioning M61-A1 20mm Vulcan cannon, autopilot (hit the F11 key), and a select few liveries. The topic of this newsletter is to display whatever new information comes out for the progress in the following project:

'''The F-16CJ Head-Up Display Project '''

The [http://en.wikipedia.org/wiki/Head-up_display Head-Up Display] is currently a basic fighter jet setup, with targeting circles and basic navigation data displays. However, it lacks the necessary data displays for dogfighting, bombing, etc. If you are interested in contributing to the project, visit the FlightGear Forum link listed below.

Many thanks to all,

--Friend, Commander of [http://helldiversquadron.wordpress.com HSOTF]

'''''Links:'''''

[http://forum.flightgear.org/viewtopic.php?f=71&t=22014 The FlightGear Forum topic]

[[Helldiver Squadron]]

[[Canvas]]

[[Nasal]]

[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Docs/README.hud;hb=HEAD HUD Documents?]

File:F-16CJ HUD 2, Mirage 2000-5 Import.png

2014-02-06T17:04:10Z

JayVS: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=f-16cj HUD 2}}
|date=2014-02-06 09:02:21
|source={{own}}
|author=[[User:JayVS|JayVS]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Fighter aircraft]]
[[Category:Military aircraft]]
[[Category:HUD]]

General Dynamics F-16 Fighting Falcon

2014-02-06T17:00:14Z

JayVS: The F-16 Fighting Falcon

{{infobox Aircraft
|ready = airrefuel
|image = General_Dynamics_F16.jpg
|name = General Dynamics F16
|type = Military aircraft
|fdm = JSBSim
|status = Production
|authors = Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
|fgname = f16
}}
The '''General Dynamics F-16 Fighting Falcon''' is a multirole jet fighter aircraft,orginally developed by General Dynamics for the United States Air Force. Currently, a newer and updated version of this fine aircraft, the F-16CJ, is being developed by members of [http://www.fguk.eu FGUK] and [http://wiki.flightgear.org/User:JayVS JayVS]. The development can be followed on their website or on the wiki article:
[[F-16CJ]]

[[F-16CJ HUD Project Newsletter]]

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

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

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

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

[[Category:Military aircraft]]

{{Lockheed}}

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

General Dynamics F-16 Fighting Falcon

2014-02-06T16:59:14Z

JayVS: The F-16 Fighting Falcon

{{infobox Aircraft
|ready = airrefuel
|image = General_Dynamics_F16.jpg
|name = General Dynamics F16
|type = Military aircraft
|fdm = JSBSim
|status = Production
|authors = Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
|fgname = f16
}}
The '''General Dynamics F-16 Fighting Falcon''' is a multirole jet fighter aircraft,orginally developed by General Dynamics for the United States Airforce. Currently, a newer and updated version of this fine aircraft, the F-16Cj, is being developed by members of [www.fguk.eu FGUK] and [http://wiki.flightgear.org/User:JayVS JayVS]. The development can be followed on their website or on the wiki article:
[[F-16CJ]]

[[F-16CJ HUD Project Newsletter]]

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

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

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

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

[[Category:Military aircraft]]

{{Lockheed}}

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

F-16CJ

2014-02-06T01:01:42Z

JayVS: The F-16CJ Fighting Falcon

[[File:F-16CJ.PNG|thumb|F-16CJ Pulling a high-g- maneuver while escaping an attack from behind.]]

The F-16Cj is a better and more advanced version of the F-16 Fighting Falcon in FlightGear. The original [[F-16]] was too slow to load the model and had no payload options or reliable autopilot. Now, the [http://www.fguk.eu FGUK] team has developed the F-16CJ.

Currently, the HUDs are being heavily modified for realism. Follow progress here: [[F-16CJ HUD Project Newsletter]]

F-16CJ

2014-02-06T01:00:39Z

JayVS: The F-16CJ Fighting Falcon

[[File:F-16CJ.PNG|thumb|F-16CJ Pulling a high-g- maneuver while escaping an attack from behind.]]

The F-16Cj is a better and more advanced version of the F-16 Fighting Falcon in FlightGear. The original [[F-16]] was too slow to load the model and had no flare launch system, payload options, or reliable autopilot. Now, the [http://www.fguk.eu FGUK] team has developed the F-16CJ.

Currently, the HUDs are being heavily modified for realism. Follow progress here: [[F-16CJ HUD Project Newsletter]]

F-16CJ

2014-02-06T01:00:04Z

JayVS: The F-16CJ Fighting Falcon

[[File:F-16CJ.PNG|thumb|F-16CJ Pulling a high-g- maneuver while escaping an attack from behind.]]

The F-16Cj is a better and more advanced version of the F-16 Fighting Falcon in FlightGear. The original [[F-16]] was too slow to load the model and had no falre lauch system, payload options, or reliable autopilot. Now, the [http://www.fguk.eu FGUK] team has developed the F-16CJ.

Currently, the HUDs are being heavily modified for realism. Follow progress here: [[F-16CJ HUD Project Newsletter]]

File:F-16CJ.PNG

2014-02-06T00:59:26Z

JayVS: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=F-16CJ Pulling a high-g- maneuver while escaping an attack from behind.}}
|date=2014-02-05 16:57:12
|source={{own}}
|author=[[User:JayVS|JayVS]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Fighter Aircraft]]
[[Category:Military Aircraft]]

F-16CJ HUD Project Newsletter

2014-02-06T00:48:32Z

JayVS: The F-16CJ's HUD Project Newsletter

[[File:F-16CJ HUD on B-17F AI Bomber Formation.png|thumb|F-16CJ HUD on B-17F AI Bomber Formation, 2014-02-05]]

The F-16CJ is a rendition of the F-16 Fighting Falcon fighter jet, modeled and scripted by members of [http://www.fguk.eu FGUK].

It has a fully functioning M61-A1 20mm Vulcan cannon, autopilot (hit the F11 key), and a select few liveries. The topic of this newsletter is to display whatever new information comes out for the progress in the following project:

'''The F-16CJ Head-Up Display Project '''

The [http://en.wikipedia.org/wiki/Head-up_display Head-Up Display] is currently a basic fighter jet setup, with targeting circles and basic navigation data displays. However, it lacks the necessary data displays for dogfighting, bombing, etc. If you are interested in contributing to the project, visit the FlightGear Forum link listed below.

Many thanks to all,

--Friend, Commander of [http://helldiversquadron.wordpress.com HSOTF]

'''''Links:'''''

[http://forum.flightgear.org/viewtopic.php?f=71&t=22014 The FlightGear Forum topic]

[[Helldiver Squadron]]

[[Canvas]]

[[Nasal]]

[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Docs/README.hud;hb=HEAD HUD Documents?]

File:F-16CJ HUD on B-17F AI Bomber Formation.png

2014-02-06T00:48:04Z

JayVS: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=F-16CJ HUD on B-17F AI Bomber Formation, 2014-02-05}}
|date=2014-02-05 16:45:42
|source={{own}}
|author=[[User:JayVS|JayVS]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Fighter aircraft]]

FlightGear Newsletter February 2014

2014-02-06T00:39:08Z

JayVS:

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

{{Note|This newsletter is currently being written by our contributors, people like YOU:

We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.}}

== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].

=== Random Buildings ===

=== Project Rembrandt ===
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].

=== Canvas System ===

The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&t=22014 FG Forum Topic]

=== High Level Architecture ===

=== Usability Improvements ===

=== Getting involved as a programmer ===
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.

If you are interested in contributing as a core developer, please see [[Howto:Start core development]].

== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.

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

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===

=== Updated aircraft ===

==== '''Sikorsky SH-60 Bravo Seahawk''' ====
'''James Cusick, (X7cusick8X)'''

[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]

The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast.

Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk!
The updates include:

Integrated Pushback

Selectable payloads

95% complete folding animation for carrier deck transit

New Liveries

FDM Fixes

and more

=== Liveries ===

== Scenery corner ==
=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
== Aircraft reviews ==

== Wiki updates ==
=== Translators required ===
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}

== Community news ==
=== FlightGear on YouTube ===
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

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

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

To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].

=== YASim looking for a new maintainer ===

{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.

Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)

So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too,
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch.
Suggestions for that means in practice, are most welcome!

Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}

{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my
latencies here are measured in weeks.
Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}

<references/>

=== Call for volunteers ===
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support

=== Did you know ===

[[Category:FlightGear Newsletter]]


[[Category:Changes after 2.12]]

F-16CJ HUD Project Newsletter

2014-02-06T00:35:41Z

JayVS: The F-16CJ's HUD Project Newsletter

The F-16CJ is a rendition of the F-16 Fighting Falcon fighter jet, modeled and scripted by members of [http://www.fguk.eu FGUK].

It has a fully functioning M61-A1 20mm Vulcan cannon, autopilot (hit the F11 key), and a select few liveries. The topic of this newsletter is to display whatever new information comes out for the progress in the following project:

'''The F-16CJ Head-Up Display Project '''

The [http://en.wikipedia.org/wiki/Head-up_display Head-Up Display] is currently a basic fighter jet setup, with targeting circles and basic navigation data displays. However, it lacks the necessary data displays for dogfighting, bombing, etc. If you are interested in contributing to the project, visit the FlightGear Forum link listed below.

Many thanks to all,

--Friend, Commander of [http://helldiversquadron.wordpress.com HSOTF]

'''''Links:'''''

[http://forum.flightgear.org/viewtopic.php?f=71&t=22014 The FlightGear Forum topic]

[[Helldiver Squadron]]

[[Canvas]]

[[Nasal]]

[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Docs/README.hud;hb=HEAD HUD Documents?]

2013-01-22T14:58:18Z

JayVS:

JayVS is an aircraft creator and has customized many existent aircraft in [[FlightGear|Flightgear]]. He is a college student who has created numerous animations, mostly using [[Blender]] and [[Gimp]].

JayVS goes under the callsign 'Friend', and usually either escorts other aircraft in [[multiplayer]], acts as a bounty hunter in [[multiplayer]], or tests his aircraft in singleplayer. He is frequently on the FlightGear Forum site, as well.
All of his customized or recreated aircraft have or are able to have the [[Bombable]] feature, a plugin that allows aircraft with armament to be able to actually destroy other craft with the same feature enabled. He is currently working on a customized Beaufighter, equipping it with a larger armament, as well as the [[Bombable]] feature.

User:JayVS

2013-01-22T14:41:12Z

JayVS: Created page with " JayVS is an aircraft creator and has customized many existent aircraft in Flightgear. He is a college student who has created numerous animations, mostly u..."