Search the Community

View File F-39A/B Griffin Blk 1/5 - Gripen NG for the US Gripen NG for the United States – F-39A/B Griffin Blk 1/5 1.0 Due to a change in US government policy driven by cost overruns, project delays and negative public (aka voter) opinion the USAF F-35A order is halved. To make up the shortfall a cheaper 4.5 generation aircraft is sought to replace the rest of the F-16 fleet. New built F-16s are considered but ultimately a license built US specific version of the Gripen NG is chosen. To help offset the loss of the cancelled F-35 order Lockheed Martin is awarded the contract to build the F-39 along with the US specific modifications. The most important of which is full data/ sensor integration and cooperative war fighting with the F-35A fleet. The USAF designate the US built Gripen the F-39A/B Griffin. The first Block 1 Griffins off the Lockheed Martin production line are identical to the JAS-39E/F and equip CONUS Air National Guard units to replace the F-16 in the air sovereignty role. At the same time Lockheed Martin produce a handful of developmental airframes to integrate the full USAF arsenal of weapons and apply some of the technology from the F-35 program. The probe air-to-air refuelling system is also replaced with a flying boom receptacle. The end result is the F-39A/B Block 5 which is used to replace the F-16 in those USAF units that are not going to be equipped with the F-35A. The Block 5 Griffin is fully compatible with the F-35 and shares the same data link technology. This means Griffin equipped units can be used cost effectively in the low intensity warfare role but when required can be ‘force multiplied’ by the F-35A in a modern battlefield. All Block 1 aircraft will be upgraded to Block 5 standard. Included in this mod are: - F-39A Block 1 Griffin - F-39B Block 1 Griffin - F-39A Block 5 Griffin - F-39B Block 5 Griffin - F-39A Block 5 Griffin Aggressor - F-39B Block 5 Griffin Aggressor - 14 different USAF/ANG squadrons - 22 different skins To Install simply un pack and drop into your mods folder. Notes: - The Block 1 aircraft have a reduced weapons capability compared the Block 5 as they can only carry the weapons currently cleared on the Jas-39 Gripin (Aim-9M, Aim-120C etc) this is reflected in the loadout.ini. - The pilot is a re-skinned JHMCS model to look like the Cobra HMD that is integrated with the Gripin (see last screenshot below). - F-39B Block 5 Aggressor has a cannon even though the two seater doesn’t have one. This is for game play so it will engage you as an aggressor aircraft. Credits: -Gux Column5 Moonjumper Jat CadeteBRA Ianh755 Stipe The Viper Team ravenclaw_007 Enjoy, Dan. P.S. I think this is my favorite 'what if' I have ever done! :-) Submitter dtmdragon Submitted 02/11/2016 Category What If Hangar  

File Name: [Fictional] North American F2J-1A Super Fury 'Blue Angels' File Submitter: Spinners File Submitted: 23 December 2015 File Category: What If Hangar North American F2J-1A Super Fury for STRIKE FIGHTERS 2 This is a very simple mod of Cocas' recent Super Fury to represent the F2J-1A as it might have appeared in service with the 'Blue Angels' aerobatic display team. INSTRUCTIONS 1. From the AIRCRAFT folder drag and drop the F2J-1A folder into your main Aircraft folder. 2. From the DECALS folder drag and drop the F2J-1A folder into your main Decals folder. 3. From the PILOTS folder drag and drop the PILOT_BA folder into your main Pilots folder. CREDITS Thanks to Cocas for bringing us another 'what if' paper project. I love them! As always, thanks to Third Wire for a great little game/sim and for the 'Blue Angels' number decals. Regards Spinners Version 1 - 23/12/15 Click here to download this file

File Name: F-4 Phantom II in Royal New Zealand Air Force service ('What If') File Submitter: dtmdragon File Submitted: 11 September 2015 File Category: What If Hangar F-4 Phantom II in Royal New Zealand Air Force service ('What If') Background (factual): In mid 1964 Operational Requirement No. 5/Air called for a tactical combat aircraft to replace the Canberra. Specifically a long range aircraft with the primary role of counter-air/interdiction and secondary roles of close air support and air defense. In June 1965 The Chief of Air Staff, Air Vice-Marshal (AVM) Morrison was quoted as wanting 18 F-111 aircraft for the RNZAF at a cost of £1.5 million per aircraft. The public and media supported the idea but the Chief of Defense Staff (who was a Naval Officer) and the acting Prime Minister publicly opposed the purchase. In August 1965 the Chiefs of Staff Committee rejected the idea of acquiring long-range interdiction aircraft and in September agreed that close air support should be the primary role of the new combat aircraft. In December came Air Staff Requirement No. 12 with the following requirements of the new combat aircraft: - Ability to provide effective air support to ground forces. - Highly reliable and robust - Self defense capability to evade or counter supersonic interceptors and surface-to-air missiles. - Long range. - Ability to operate closely with American and Australian forces. By May 1966 the RNZAF had finished evaluating six candidate aircraft: - F-4C Phantom II - A-7A Corsair II - Mirage IIIO - F-5A Freedom Fighter - F-104G Starfighter - A-4E Skyhawk In August 1966 the RNZAF officially asked the government to purchase 16 F-4 Phantoms at a total cost of £19 million. Now remember AVM Morrison making it known he wanted the F-111? He would later go on to admit he never wanted the F-111 he had wanted the F-4 all along but given the cost of the F-4 he wanted to make it look more attractive (cost wise) by putting it next to the F-111. The minister of Defense then announced the final stage of the evaluation had been reached and a decision was a few weeks away. The purchase of the F-4 seemed to be all but done... BUT the Treasury department now intervened and recommended purchasing the F-5! The RNZAF High Command was furious! But ultimately powerless to halt the path to purchasing the A-4 Skyhwak that had just begun. Over the next year the RNZAF, Cabinet Defense Committee, Treasury, the Finance Minister and the Chief of Defense wrangled over purchasing the F-4 or an alternative (F-5 or A-4). Then at the end of 1967 the New Zealand Currency was devalued and a squadron of F-4 Phantoms was now instantly out of New Zealand’s price range. It was either 11 Phantoms or 16 Skyhawks. So the Skyhawk it was. So if the Treasury Department hadn't intervened in the procurement process towards the end of 1966 it seems entirely likely that New Zealand would have placed and order for the F-4 Phantom II at the end of that year! And so I give you the F-4D Phantom II in RNZAF Service 1969 to 2002. I chose the F-4D as when the order would have likely been placed in late 1966/ early 1967 the F-4D was the current USAF production model as the first of the F-4E models were only just being built as part of the USAF F-4D contract. The RNZAF F-4D models are built to the same standard as the last USAF F-4D coming off the production line in the late 60's. However like the A-4K in real life they are 'fitted for but not with' ECM/ RHAW equipment. This means the wiring, sensors and cockpit RHAW display are installed but the actual 'black box' control units are not. The reason for this (as in real life with the A-4K) was not an economy measure as most references state (including the Third Wire manual) but because the equipment was in such demand by US forces for use in Vietnam. So the aircraft were delivered without them but with the intention of fitting them at a latter date. However that day simply never came and this is possibly where the additional cost of purchasing/ installing them played a part in it not happening. The Kiwi F-4D Phantoms are capable of caring the full range of the USAF Phantom arsenal including first generation smart weapons. However only the Mk 82/83/84 series bombs and unguided rockets are used by the RNZAF. For the air-to-air role the SUU-23/A gunpod, AIM-7E and AIM-9E are chosen with the AIM-4 Falcons performance in Vietnam causing the RNZAF to steer well clear of it. Four separate Aircraft: F-4D Phantom II RNZAF - Initial aircraft delivered in 1969 fitted for but not with ECM/ RHAW equipment. F-4D Phantom II (72) RNZAF - By 1973 the redundant RHAW display has been removed from the cockpit as well as the empty IRST pod under the nose that was to house the RHAW gear. F-4D Phantom II (78) RNZAF - Second hand attrition aircraft from USAF stocks delivered in 1985 in preparation for the project Kahu upgrade of the fleet. F-4D Phantom II (88) Kahu RNZAF - In 1986 a comprehensive $140 million upgrade program is undertaken. Known as project 'Kahu' the heart of the upgrade is replacing the old AN/APG-109 radar with the modern AN/APG-66(NZ) multi-mode radar. The cockpit is modernized with glass displays, HOTAS and a Ferranti wide-angle HUD. Survivability in increased with the ALR-66 RWR and ALE-40 countermeasure dispensers. The MIL-STD 1553B databus and Litton Industries LN-93 inertial navigation system are also installed. The airframes and engines are completely stripped down and given a life extension with almost all of the aircraft wiring replaced. A smoke abatement system is added along with low voltage formation lights. The aircraft also receive armament upgrades including the capability to fire AIM-9L, AIM-7M, AGM-65B/G and GBU-10 Paveway II laser-guided bombs. The old F-4 Phantom external center drop tanks are also replaced by the F-15 600 gallon HPC tanks as on USAF Phantoms. By the end of 1991 all New Zealand and ex USAF Phantoms have been upgraded to the 'Kahu' standard. More sceen shots and the full 'what if' story here: http://combatace.com/topic/86994-f-4-phantom-ii-in-royal-new-zealand-air-force-service/ Requirments: you will need one of the SF2 games with the F-4D as well the Third Wire DLC A-4K Skyhawk for the decals. Bonus: Included in a separate folder is a RNZAF F-4D for use with the SF2V Air & Ground War Expansion Pack. This is the Kiwi F-4D fitted with the required ECM and stores for operations in the Vietnam War. Credits: - comrad - Sundowner - Dave - eburger68 - Malibu43 - ravenclaw_007 - Bunyap - Chaser617 Released under CombatAce Fair-Use terms. Enjoy! Dan (dtmdragon) Click here to download this file

File Name: 'What if' F-106A 'Extended Service' Skin pack File Submitter: dtmdragon File Submitted: 27 July 2015 File Category: What If Hangar 'What if' F-106A 'Extended Service' Skin pack - 7 Skins based on the early F-15A ghost greys colour scheme. - 2 Skins based on the later F-15A/C mod eagle colour scheme. - 1 Skin based on the grey two tone F-16 colour scheme. - 2 Skins which are FIS markings repainted over the SEA scheme of aircraft that have returned from Vietnam. - 1 Skin which is FIS markings repainted over the SEA Night scheme of aircraft that have returned from Vietnam. - Bonus ADC pilot in orange flight suit (you will have to edit the F-106A_data.ini to use it if you want to) You MUST have the SF2 F-106A pack installed: http://combatace.com/files/file/14246-f-106a-delta-dart-for-sf2/ Credits: - Pasko and his team that did the F-106A above. - Geary for the F-106A templates. Enjoy! Dan (Dtmdragon) Click here to download this file

File Name: F-106A Delta Dart in Vietnam (What if) File Submitter: dtmdragon File Submitted: 21 July 2015 File Category: What If Hangar F-106A in Vietnam (What if) Background: During the late 60’s there were serious discussions in the USAF about deploying the F-106A to the conflict in Vietnam. Obviously this never eventuated but the possibility lead to project Six Shooter which saw a gun pack and an improved visibility canopy added to the F-106A. So what would the Delta Dart have looked like if it had served in the skies above Vietnam? In 1968 the USAF conducted a Tactical Evaluation to evaluate the effectiveness of existing tactical manoeuvres by USAF and USN combat aircraft against the MiG-21 Fishbed. It was called ‘Have Drill/ Have Ferry.’ The ADC evaluated the F-106 and found its radar capable of acquisition of the MIG and that radar snap-up attack could be used to exploit the MiG-21's lack of fire control. The F-106 could use better acceleration to get beyond MiG-21 speed limits. A direct result of this evaluation was the ADC recommendation to “expedite fitting the internal gun, redesigned canopy, radar warning and ECM equipment into the F-106”. So based on the above (factual) information I present the F-106A Delta Dart (69) ‘Nam’ To the SF2 F-106A I have added the following: - Permanently mounted M61A1 Gun Pack (Project Six Shooter) - Internal ALQ-100 ECM - Chaff dispensers - APR-25 RHAW (Audio only) - SEA camouflage (Day and Night) - Pilot in tiger stripped flight suit. - I have also applied the MA-1 FCS ECCM upgrade done to 314 F-106 in 1963. The ECCM system allowed the FCS to reject radar returns resulting from chaff dispersal by a target. As part of the upgrade a final modification resulted in increased missile performance. Modifications to the FCS permitted up to 35 percent more deflection of the Falcon missile’s control surfaces. This resulted in a more agile missile at launch, increasing the missile’s ability to react to a maneuvering target. To portray this in the game I have made changes to the F-106 avionics as well as a specific ECCS AIM-4F missile. Notes: - The AIM-4G has been changed to have no audible growl (It never had it) and is slaved to the radar. This more accurately portrays the employment of the IR guided Falcons. You will have to use the radar to know when you are locked on and in range. (Just like a F-106 pilot would have had to done in real life). - The weapon bay doors are manually activated, I prefer this as the animation doesn’t work with most missile shots when it’s set on automatic. - There is a specific version of the M61A1 gun for the F-106 as when installed in the F-106 its rate of fire was limited to 4500 rounds per minute. Credits for the original SF2 F-106A and SEA skin decals: Pasko Kesselbrut Column5, MKSheppard eburger68 Sundowner Dave DaniloE31 Pasko DaniloE31 Lexx Luthor 76.IAP-Blackbird Cliff7600 Enjoy! Dan (Dtmdragon) Click here to download this file

File Name: Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume II) File Submitter: HomeFries File Submitted: 27 June 2015 File Category: Su-27 Skins Su-27 Fictional Skins: US Navy Fighter Squadrons (Volume II) for DCS World 1.2.14 and later This is a collection of seven skins representing three US Navy fighter squadrons using historical F-14 Tomcat liveries. The squadrons included are: VF-2 Bounty Hunters (CAG, Line birds) VF-111 Sundowners (CAG, Line birds) VF-213 Blacklions (CAG, CO, Line birds) The VF-213 skins date from their 2005 deployment with CVW-8 on the USS Theodore Roosevelt (the "Tomcat Farewell Tour"). Most markings have been westernized, and the pilots have been given USN flightsuits with Naval Aviator wings and squadron patches. The helmet remains Russian made. The VF-2 skins were inspired by GeorgeLKMT's VF-2 CAG skin for Dino Cattaneo's F-14D (for FSX), and the skin was also used as a starting point for my own VF-2 CAG skin. Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs. Be sure to download Volume I. For Compact Installations - A Note About Autoexec.cfg: Rather than copying texture files to their respective livery folders, I prefer to use a series of common texture folders along with unique filenames. This allows a single instance of many of my common textures, and keeps the hard drive footprint to a minimum (especially nice if you run a SSD for your system drive). The installer will add a series of folders to the DCS Texture path; if you do not have these folders created, then it is no problem. The autoexec.cfg included will automatically point to the Texture folder in your Saved Games\DCS folder, and regardless of whether you run the Open Alpha, Open Beta, or Release version of DCS, the path will always point to your Saved Games\DCS\Texture folder. Again, this saves space on your hard drive. If you use your own Autoexec.cfg, then when prompted to overwrite you can click "no". This will create a file called autoexec.new, and you can manually make the updates as you like. Just don't modify the top line with the file date; this is used by the installer for version control. However, feel free to include it in your existing autoexec.cfg, so you don't get prompted to overwrite until there's another update to the autoexec.cfg. If you inadvertently overwrite your autoexec.cfg, it is actually backed up as autoexec.old. Just open it and copy the appropriate information to the new file. For Traditional Installations: If there is an issue with textures not displaying, it is likely a problem with the installer. Please let me know what textures are missing so that I can troubleshoot the issue. Fly Navy! -Home Fries Click here to download this file

File Name: 'What if' KAW Hawker Hunter F.1 with Campiagn File Submitter: dtmdragon File Submitted: 02 March 2015 File Category: What If Hangar 'What if' KAW Hawker Hunter F.1A & F.1B with campiagn 1.0 The back story: In order to meet the Mig-15 threat over Korea and with no capable fighters currently in the RAF inventory the British Ministry of Supply instructs Hawker Aviation to undertake a crash production program of its P.1067 fighter. Project ‘Huntsman’. In less than a year since the prototype flew and two years ahead of schedule the Hawker Hunter is deployed to the Korean Theatre in early 1952. Since the Hunter F.1 designation was already assigned to the first full production Hunters due into service in 1954, the Hunters produced under program ‘Huntsman’ are (unusually) designated Hunter F.1A These aircraft are basically identical to the future production Hunter F.1 the most obvious difference being that they are finished in High Speed Silver. However the lack of paint means these Hunters are 21 Mph faster and 53Kg lighter than the full production F.1 Hunters. Operations over Korea immediately highlighted the Hunters inherent shortcomings. Of most concern was its lack of fuel and endurance with barely an hour’s flight time. Also of concern was the damage done to the fuselage caused by the ejection of spent cartridge links. These concerns (among others) would be addressed in time by future models of the Hunter, but in the skies of Korea in 1952 the lack of range and endurance had to be immediately mitigated. And thus the Hunter F.1B is born with the addition of wing mounted drop tanks installed in theatre. What's in it: - Hawker Hunter F.1A - Hawker Hunter F.1B - Various RAF 43 and 222 Squadron Skins in Camo and High Speed Silver. - NOTE: The camo skins are included as a bonus but the aircraft data.ini files are set up to reflect the high speed silver skins as I have included the weight reduction and increased speed that comes without using camo paint. I found the figures I used in an article about the trial OD green Sabres in Korea. - sounds - pilot - Modified Korea Campaign using the Hunters. This will not change the original campaign in any way, you will see an additional campaign called 'Korean War Hunters Over Korea' that you can select. Missions will be similar to the Sabre, No 43 Squadron is based at Suwon AB (K-13) and No. 222 Squadron at Kimpo AB (K-14). - NOTE: this mod can be added to the Wings Over Korea mod without any change what so ever to the original game play. You will never see these Hunters show up over Korea unless you play the above included campaign or start a single mission with a Hunter. Operations: - canopy open key=10 automatic closing at take off To Install: - Designed to be used with the Wings Over Korea mod but should work without it. - Put everything in you main StrikeFighters2 KAW mods folder - Get the Wings Over Korea mod here: http://combatace.com/files/file/15221-wings-over-korea-1-of-2/ http://combatace.com/files/file/15220-wings-over-korea-2-of-2/ Credits: - Third Wire - Paulopanz Hunter F.1 Skins & Edits for SF2 - Sundowner Hunter F6 Templates. - Do335 Wings Over Korea - Evryone else in the WOK/ KAW team Released under CombatAce Fair-Use terms. Enjoy! Dan (Dtmdragon) Click here to download this file

File Name: P-40S SuperHawk SF2 ('What If') File Submitter: dtmdragon File Submitted: 26 October 2014 File Category: What If Hangar P-40S SuperHawk This is a fictional upgrade of the P-40N Warhawk. Background: With the XP-40Q project failing to get of the ground Curtiss came up with an upgrade to the existing late model P-40 airframes that would give them performance on par with the XP-40Q and the P-51D. The resulting P-40S SuperHawk performs so well it rapidly becomes one of the front line fighters of choice. It will even go on to serve in the Korean War alongside the P-51D. The upgrade: - 2200HP Packard V-2250 engine (Packard built Merlin 1710 upgraded to 2200HP). - Four-bladed Rotol propeller. - 4 x 20mm Hispano Mk II cannons. - K-14 gyro gunsight. - Range: 650 mi (560 nmi, 1,100 km400 nmi (459 mi, 740 km). - Service ceiling: 43,500 ft (13,258 m). - Rate of climb: 3,650 ft/min (18.5 m/s). I have included skins for every late war WWII theatre the P-40 operated in as well as a ‘what if’ USAF WWII ETO and Korea skin. There are skins for the RAAF, RAF, RNZAF, USAF and Soviet Airforce. Credits: - Raven (Big thanks) - Wrench - A. Mariani aka amariani Engoy, Dan dtmdragon Click here to download this file

View File P-51D Colombian Air Force Skin Pack (Fictional) This is a package of two P-51D skins using the current Fuerza Aérea Colombiana grey paint scheme used for the Super Tucano. One version of the skin has a "shark mouth" on the nose. Nationalities are USA and Spain. Installation Instructions: Copy the folders to your Saved Games\DCS\Liveries\P-51D folder. Optional: The release of DCS World 1.2.4 added the ability to add texture paths using the file "autoexec.cfg" in your Saved Games\DCS\Config folder. This will allow you to save hard drive space as long as the skin filenames are unique. My skins support this, so any DDS file with the same name will be identical. In order to enable this feature, add the following line to autoexec.cfg (be sure to create the file if it doesn't exist): table.insert(options.graphics.VFSTexturePaths, "C:/Users/<username>/Saved Games/DCS/Textures") You can use any path (even a different drive), but you must use forward slashes for your path. Backslashes won't work here. Then, you can move all of the DDS files from each of the skin folders to this new folder you've added to your path. Allowing overwrites is not a problem, as I use unique names for each file. Finally, be sure to go into each description.lua file and change all "false" entries to "true." You are free to use any of these skins in other projects as long as proper credit is provided in the readme file. -Home Fries Submitter HomeFries Submitted 06/28/2014 Category Misc/AI Aircraft Skins  

File Name: MiG-29A Georgian Skin (Fictional) File Submitter: HomeFries File Submitted: 28 June 2014 File Category: Mig-29A/G/S Skins NOTE: This only works with DCS World 1.2.16 or earlier. DCS World 1.5/2.0 uses a new MiG-29 model. I originally did this at the request of a friend, who wished to have the Czech camouflage pattern on fictional Georgian MiGs. I used the Czech pattern as a starting point, then used the colors on the Georgian MiG-21 to finish the job. Once I completed the pattern, I eventually decided to release it to the public. In addition to Georgia, the skin is available to Russia, Ukraine, and Insurgents. Installation: These MiG-29A skins do not require you to overwrite any existing "slots"; they exist as individual skins using the standard definition.lua format. Simply put the skins in your Saved Games\DCS\Liveries\ folder; you should be able to extract using the path that exists in this archive file. In order to have the Georgian MiG-29A (and the skins) available for Georgia in the Mission Editor, you will need to update the db_countries.lua file located in DCS World\Scripts\Database. Open the file in a text editor like Notepad++ and search for the following string: -- GEORGIA This is the comment line that starts the Georgia section. In the first section,you will see the following entries: cnt_unit( units.Planes.Plane, "Su-25"); cnt_unit( units.Planes.Plane, "An-26B"); cnt_unit( units.Planes.Plane, "Su-25T"); cnt_unit( units.Planes.Plane, "L-39ZA"); cnt_unit( units.Planes.Plane, "Yak-40"); cnt_unit( units.Planes.Plane, "P-51D"); These are the planes available to Georgia in the mission editor. Just add the following line: cnt_unit( units.Planes.Plane, "MiG-29A"); You may also optionally add that line to the section starting with -- INSURGENTS This opens more possibilities for scenarios, and all of the included skins are available to the Insurgents as well as Russia and the Ukraine. Special thanks to Jack for allowing the use and modification of his enhanced pylon texture, as well as his collaboration in developing MiG-29 skins that are not dependent on the original "slots" of the Flanker 2.5/LOMAC models. Click here to download this file

File Name: New Zealand F-16C/D Block 52+ Fictional Order File Submitter: dtmdragon File Submitted: 27 March 2014 File Category: What If Hangar What If, Royal New Zealand Air Force F-16C/D Block 52 Plus. - No. 75 Squadron, RNZAF Base Ohakea 2014 - 148th Fighter Squadron Arizona ANG 162d Fighter Wing, Tucson ANG Base 2012 You will need the The F-16C Block 50/52 by The Viper Team for the sounds and effects etc http://combatace.com/topic/72842-f-16c-block-5052-by-the-viper-team/ Instillation: As usual simply drop into your mods folder and allow it to override when prompted. Dec 17/2013: Final Delivery. The Royal New Zealand Air force (RNZAF) celebrates the arrival of its first Lockheed Martin F-16C/D aircraft. The first Block 52+ F-16s to be based in New Zealand were received by Sir Jerry Mateparae, Governor-General of New Zealand and Commander-in-Chief of the New Zealand Defense Force. March 4/2012: First Delivery. Lockheed Martin holds a ceremony at its Fort Worth, TX facility to deliver the first F-16 aircraft to the RNZAF. This F-16D was accepted by the U.S. government (as the agent for New Zealand in the FMS process) on Feb 19/12, three month ahead of schedule. The first single-seat F-16C version will fly in March 2012, and be accepted in April 2012. These 2 aircraft and all subsequent deliveries will head to Tucson ANG Base on attachment to the ANG 148th FS for up to two years to train the initial squadron of RNZAF pilots. Jan 2010: F-16 order. The New Zealand Minister of Defence signs an agreement with the U.S. government to purchase 24 Advanced Block 52 F-16s in the ‘Peace Star’ Foreign Military Sales (FMS) program. The agreement includes 16 single-seat F-16Cs and 8 two-seat F-16Ds, associated equipment and services, weapons, initial pilot and aircraft technician training. The RNZAF also announced the re-activation of No. 75 Squadron in anticipation of the order. Aug 2009: The US DSCA announces New Zealand’s formal request for 24 F-16C/D Block 52 aircraft as well as associated equipment and services. The total value, if all options are exercised, could be as high as $2.7 billion. Funds will be provided under the Foreign Military Financing Program with repayments spread over 10 years. The proposed sale includes: 24 F-16C/D Block 52 Plus aircraft with F100-PW-229 Engines, and APG-68v9 radars; 24 Conformal Fuel Tanks (pairs); 30 AN/ALE-47 Countermeasures Dispensing Systems (CMDS); 30 AN/ALR-93 Radar Warning Receivers (RWR); 28 AN/ALQ-211 Advanced Integrated Defensive Electronic Warfare Suites (AIDEWS); 26 Joint Helmet Mounted Cueing Systems; 16 AN/AAQ-33 Sniper ATP; 5 TERMA Modular Reconnaissance Pod (MRP) 24 AN/ARC-238 Single Channel Ground and Airborne Radio System (SINCGARS) radios with HAVE QUICK I/II; 24 Link-16 Multifunctional Information Distribution System-Low Volume Terminals (MIDS-LVT); 24 Global Positioning Systems (GPS) and Embedded GPS/ Inertial Navigation Systems (INS); 24 AN/APX-113 Advanced Identification Friend or Foe (AIFF) Systems; 30 AN/AVS-9 night vision goggles. ENJJPT (Advanced flight training and F-16 operational conversion) for up to 50 initial RNZAF F-16C/D pilots; 30 AIM-120-C7 Advanced Medium Range Air-to Air Missiles (AMRAAM); 60 AIM-9X SIDEWINDER Missiles; 20 AGM-88C HARM Missiles; 50 AGM-65G MAVERICK Missiles; 50 AGM-119A Mk III Penguin ASM Missiles; 30 Joint Direct Attack Munition (JDAM) 2,000 lb bombs; 30 GBU-10, PAVEWAY II 2,000 lb. bombs; 60 Enhanced GBU-12 PAVEWAY II bombs, with dual-mode GPS/laser guidance; 8 AGM-65G Maverick training missiles; 16 Air Combat Maneuvering Instrumentation (ACMI) pods; Note on loadouts: Attack/ CAS loadouts are set for engaging large amounts of armour. However you can select a GBU-49 CAS loadout with the mission editor, along with a few other unique loadout options. Credits: The Viper Team for their stunning viper packs Ravenclaw_007 for his new weapon packs Enjoy, Dan. Click here to download this file

File Name: Fictional ‘What if’ Royal New Zealand Air Force A-7 Corsair II Skins File Submitter: dtmdragon File Submitted: 19 March 2014 File Category: What If Skins Fictional ‘What if’ Royal New Zealand Air Force A-7 Corsair II Skins As requested in MAKO69’s topic (http://combatace.com/topic/82082-a-lot-of-what-if-ideas-for-the-moders/?do=findComment&comment=658905) here are my RNZAF A-7 re-skins. Fact: When the New Zealand Government selected the A-4K Skyhawk for the RNZAF in the late 60’s/ early 70’s the A-7 Corsair II was on the Air Force’s short list along with the F-4 and F-111. A modernised version of the A-7 was again considered in the late 80’s as an alternative to upgrading the RNZAF Skyhawks. You will need the stock Third Wire A-7D and A-7E_74 as well as the Mirage Factory A-7D_84 and A-7K_MF Instillation: As usual simply drop into your mods folder and allow it to override when prompted, none of the aircraft files will be changed just the skins added. Credits: Third Wire and Team Mirage Factory Enjoy, Dan. Click here to download this file