Jump to content

Leaderboard


Popular Content

Showing most liked content on 09/05/2021 in all areas

  1. 6 points
  2. 5 points
    Bell P-39C Airacobra - 1st American Volunteer Group, 1942
  3. 4 points
    Dam - Dam - Dam - DamDamDam - DamDamDam
  4. 4 points
    2015... Early test flights of the Boeing F-15F Super Eagle from Eglin AFB !
  5. 4 points
    Supermarine Seafire Mk.IIIC - No.2 Squadron, Royal Dhimari Air Force, 1944 The successful Dhimari counter-attack at Maqazad in the Spring of 1943 proved to be short lived and the Parani bombing of the Dhimari city of Shaqaz during May 1943 led to the deployment of Dhimari P-66 Vanguards and Hurricane IIC's to northern areas of Dhimar leading to a further weakening of the Royal Dhimari Air Force in their desperate attempts to defend the Mazadran Oil Fields and the Valley of Kerman during the summer of 1943. Paran's senior Commander, Brigadier General Abolqasem Mossadegh, followed up by launching Operation Whirlwind in September 1943 and, with Paran gaining air superiority over the Valley of Kerman, it's land forces pushed onwards towards the industrial oil center at Al'Qatan in an audacious attack on the wider Mazadran oil fields. The UK government had long promised Spitfires to modernise the Royal Dhimari Air Force and whilst a handful of war weary Spitfire VB's from Malta were received during the Autumn of 1943 many more fighter aircraft were required. Churchill ordered that 30 new Spitfires were to be transferred to the Royal Dhimari Air Force but, much to the annoyance of the Admiralty, the Ministry of Aircraft Supply ordered that they should all be from the initial batch of 30 interim Seafire IIIC's coming off the Westland production line and all built without wing-folding. Powered by the Rolls-Royce Merlin 55 series engine rated at 1,470 h.p. (with power absorbed by a new four-bladed Rotol propeller) the Seafire IIIC's also featured the slim Aero-Vee air filter and the six-stack ejector type exhausts. Entering service with No.2 Squadron in December 1943 the Seafire IIIC's immediately replaced the P-66D Vanguards and proved to be the equal of the Parani Ki-61's and Bf 109G-6's enabling the Royal Dhimari Air Force to restore air superiority over the Valley of Kerman. Skin Credit: Charles
  6. 3 points
    Flying between two tunnels by @costadario
  7. 3 points
    Douglas A-4E Skyhawk - No.860 Squadron, Royal Netherlands Naval Air Service, 1971
  8. 2 points
  9. 2 points
    I think Ace Combat is owed an apology. Surprised the aircraft could lift the man's tungsten balls.
  10. 2 points
    Giving the new Vulcan a workout high over the English countryside..
  11. 2 points
    I have absolutely no idea! I set up the mission to be a simple intercept of the Airbus (actually the 'real' mission was to intercept a Tu-95 on a recon run off the North Sea coast but I set up a couple of F-15Cs out of Lakenheath to take care of that). The story was that the airliner's navigation equipment had gone down and we would form up on it and lead it down through the clouds and onto the runway. I was as surprised as anyone when I got in visual range, and the flyby to check over the airliner was real. I re-wrote the story in my head on the fly as I tracked the Airbus down and over London until it landed. Funny thing is I've flown the mission a few more times since then because I thought I had set something wrong, maybe with the airliner dropping below stall speed, and it has been absolutely fine... Maybe TK programmed in a secret setting - RandomCatastrophicMishap=TRUE
  12. 2 points
    awesome, your weathering or did the original come like that? more mandatory screenies from todays theme (now in a more appropriate setting)
  13. 2 points
    Kawasaki Ki-100 Otsu - Parani Army Air Force, 1945
  14. 2 points
    Kawasaki Ki-61 Hien - Parani Army Air Force, 1944
  15. 2 points
    Douglas F-6C Skyray - 178th Fighter Interceptor Squadron, United States Air Force, 1966
  16. 1 point
    Most of the best modders in the community have agreed to make their work freely available with few restrictions. These modders have granted blanket permission for you to use their work under the following conditions: 1. The work may not be used in payware projects or in projects that will not be freely distributed under these same terms. 2. The work may not violated any terms of release by converting payware to freeware or freeware to payware. 3. You must give proper credit to the original author in your readme file. 4. If feasible, included the original author's readme along with your new mod file. 5. You must contact the original author for permission of use if more than 30% of the original release is affected by your work. 6. A Mirage Factory file may not be altered or included in a new mod with the permission from a Mirage Factory Member. 7. Any scenery or map tile modifications by Wrench require permission to edit, change, or use. 8. Any uploads of mods to Dev A-Team products are limited to ini edits, and skins/decals. They have requested that NOTHING of theirs be stored or shared or passed around outside their own members-only website. Signatories to this agreement are (latest additions in bold): 101tfs 542Tiger (aka 331KillerBee) 76.IAP-Blackbird AleDucat allenjb42 AmokFloo baffmeister Baltika bender41 bobrock Brain32 CA_Stary Caesar Capitaine Vengeur ChampionsVA56 charley111 CIACHO Cocas column5 comrpnt CoolHand29 (MiGbuster) Corktip14 craigbrierley (Bongodriver) CrimsonRoamer Deadhead Dels Deuces Doghouse drdoyo dwcace erikgen EricJ Erwin_Hans ext FalconCAF FastCargo Firecage FLOGGER23 Fracture Fubar512 gambit168 Geezer Gepard ghostrider883 gillg Gocad GrinchWSLG Heck hgbn hi ho silver HrntFixr JA 37 Viggen Jan Tuma JAT81500 Jarhead1 jeanba JimBeamer#5 johnrey JRBeers JSF_Aggie Jtin Jug Julhelm kct Kesselbrut KingAlbert Klavs81 Krfrge Kulbit80 Longestpants littlesmoke LloydNB Major Lee malibu43 mikeymead MontyCZ mppd muesli PACMAN pcpilot p10ppy Paladrian pappychksix pcpilot PFunk pureblue Rambler 1-1 Raven ravenclaw_007 Red Dragon Designs Royohboy Russouk2004 scouserlad13 Shaolin Sheriff001 Signum Silverbolt Spinners Soulfreak Spitwulf STORM suhsjake Sundowner SUICIDAL Syrinx Tailspin Talos The Trooper thundercheif Timmy Tristan Typhoid USAFMTL (Dave) ValAstur (ex - NazGhul) Veltro2k Viper63 WarlordATF Warwolf01 whiteknight06604 wilco wingwiner WombRaider wpnssgt Wrench, The *** Special Cases ONLY X RAY yakarov79 Zurawski UllyB This applies only to work released individually as freeware. Not as part of a team (unless the team name is listed) or anything released as payware. If you have any questions, please get in contact with the modder and work things out. Also this doesn't apply to SimQH, they can not use anything from this for site for a damn thing.
  17. 1 point
  18. 1 point
    MiG-23PD was the designation of the Ye-230 development aircraft line. It had similar wings like the MiG-21, that is true, the gear system was similar. But it was a dead end development line. The same was Ye-8, which based on MiG-21PF. The intended service designation of the Ye-8 was in fact MiG-23. But it had nothing to do with the real MiG-23. The MiG-21PD, which you mentioned, was only a technology demonstrator. It had only fuel for 10 minutes or so and was unable to retract the landing gear. The MiG-23 based on the Ye-231 development aircraft line, which had not much in common with the MiG-21, beside some electronical equipment. Back to Su-17 vs MiG-27. Both planes were developed, because the soviet frontal aviation realized in the 1960th, that there was no dedicated CAS aircraft available. To modify the MiG-17 and Su-7 from fighters into fighter bombers helped not very much. Thatswhy the construction bureaus MiG and Sukhoi got the task to build a fighter bomber plane which should be able to fly CAS missions and tactical nuclear strikes. Sukhoi took the Su-7 plane and changed the wings in that kind, that the outer wings could swing. This was simple and clever. The development risks were low. The plane was easy to handle for the pilot. Existing weapon stations could be used. Sukhoi decided to add additionaly electronic, like ECM, Laserdesignater etc, as pods on one of the weapon stations. With the last versions this was changed, the Su-17 got the humpback, with enough space for a powerfull electronic package. The latest versions Su-17M4 and Su-22M4 were mighty planes. They were so big and strong, that east german pilots, who after the political change switched from Su-22M4 to Tornado IDS said "In contrast to the "Susi" the "Tony" was a fragile plane!" The Su-17 was a plane with the major focus on CAS. The MiG-23BN was a little bit different. The MiG-23BN was smaller than the mighty Susi. Electronical equipment like Laser or ECM were built in internally. The MiG-23BN had thick armour plates on the sides of the cockpit. The Autopilot, the weapon control system and the navigation system were networked. Thatswhy a MiG-23BN was able to follow a flight path along programmed waypoints automatically and was able to fire weapons automatically and was finally able to land automatically. Only for start the pilot was needed, the rest the plane was able to do it alone, without pilots help. Of course, the accuracy of the automatical weapon release was not good enough to hit small targets with conventional weapons, but it was good enough for hitting a target with a 30kt nuclear bomb. And this was the main task for the MiG-23BN. The CAS role was rather secondary and there the MiG-23BN was not really good. The KH-23 missile was more or less crap and without this missile the MiG-23BN was only a dumb iron dropper. So you can say while the Su-17 was more focused on CAS, the MiG-23BN was more focused on nuclear strike. The MiG-27 was the attempt to implement modern weapon systems into the MiG-23BN airframe. The electronic was much better, the autopilot, for instance, was not longer dangerous for the pilot of the plane. The air intake system was modified, the engine changed. The plane got the ability to defend itself against air opponents. And so on. The MiG-27 was a much better CAS plane than the MiG-23BN, but finally the latest versions of the Su-17 or Su-22 were the better planes.
  19. 1 point
    Nice! The pilot is Italian! This has been such a great year in sports for my country.
  20. 1 point
    I found this photo of a model of the original lift-engine variant. The intakes were moved to the side to fit in the radar, just as was done on the Su-9/11 and the Chinese MiG-21s. WofRussia04_Mig_23-01.jpg (464×349) (impdb.org) This is the prototype in flight: mig23pd-1.jpg (600×296) (bp.blogspot.com) Early MiG-23 development concepts were based on the Ye-8, which was the MiG-21 with the intake under the nose and a small canard. The Ye-8 variants progressed into the 23-01 variants, which were barely flying before they were canceled in favor of the swing wing redesign that became the MiG-23. So, they didn't start with a blank sheet of paper and build a design around the idea of the swing wing and F-4 style intakes... they started with a MiG-21 variant and kept making changes until they got an acceptable design. The time frame was about: 1963-64 for Ye-8 with lift engine concepts, 1966 for the flying 23-01 prototype, and then about 1969 for several flying MiG-23 prototypes. They spent so much time figuring out what wouldn't work that they were left with almost completely different airplane than the starting point. That is what you can see in the development of the F-105 and F-17 (F/A-18) as well. But that doesn't alter the fact that the design started from an existing aircraft and gradually evolved over time. The Super Hornet is one more case to consider: while it looks very similar to the legacy F/A-18A/C Hornets, it is essentially a new aircraft, yet the first thing the Wiki entry says about it is that it is ultimately a derivative of the F-5.
  21. 1 point
    The MiG-23 was an evolution of ongoing V/STOL work done on the MiG-21. I have the really big MiG-23 book that details the evolution of the MIG-21 that led to the MiG-23 that entered service. I won't waste my time scanning in the photos, but the MiG-23 is a derivative of the MiG-21 just as much as the F/A-18 is a derivative of the F-5. MiG spent many man-hours testing/changing the design to get the final form. Another example is the Su-15: it looks different, but it was an evolution of the Su-9/11. Another example of evolution that included a size change was: F-84F -> RF-84F -> F-105.
  22. 1 point
    It happens, the reason 15 years ago I wrote a tutorial on "having 2 aircraft named the same" and how to keep them seperate. hint: as you've discovered, unique names
  23. 1 point
    This was great. The Finns and the Rafale were show-stoppers.
  24. 1 point
  25. 1 point
    Vickers-Supermarine Seafire Mk.IIIC - No.2 Squadron, Royal Dhimari Air Force, 1945
  26. 1 point
  27. 1 point
    eastbound and down rollin up and truckin.... we got a long way to go and a short time to get there....
  28. 1 point
    Avia S-199P - 2nd Fighter Regiment, Parani Air Force, 1947
  29. 1 point
    Avro Vulcan B.2 (MRR) - No.27 Squadron, RAF Strike Command, 1991
  30. 1 point
  31. 1 point
    es muy tarde y no lo probé lo suficiente, pero solucione el inconveniente del mapa de Malvinas. y no hay quien pueda!!! cantaban los halcones.
  32. 1 point
    for variant F, new quadruple bracket ER-4
  33. 1 point
    First flight in the new version of the ODS30AE mod. Well, it would be rude not to..
  34. 1 point
  35. 1 point
    F-4S Phantom de 1.ª Escuadrilla Aeronaval de Ataque sale de ARA Guillermo Brown (V-5)
  36. 1 point
  37. 1 point

    Version

    179 downloads

    SEA HiRes Camo A-7D TW For SF2V and SF2E Credits: ----------------------------- SEA HiRes Camo Skins by NeverEnough Hangar and Loading Screens by NeverEnough A-7E Template by Wrench Escapac Ejection Seat by THE BANDIDOS-TEAM USAFNM1 Pilot by X-ray Installation: ------------------------------ Simply extract the contents of the SEA Pack_A-7D.7z to your desktop or a temporary folder. Then copy/paste the Effects and Objects folder into your Mods\StrikeFighters2, Mods\StrikeFighters2 Europe or Mods\StrikeFighters2 Vietnam folder. If asked to "OVERWRITE" or "Replace The Files In The Destination", click yes. Shift 0 will open and close the canopy. USAFCAMO7, USAFCAMO8, and USAFCAMO9 each have different shark jaws and eyes. Two hangar screens are included. If you would like to use A-7D2_Hangar rather than the default A-7D1_Hangar Screen, edit the included A-7D.INI line to read "HangarScreen=A-7D2_HANGAR.JPG" (without the quotes!). I hope you enjoy!


×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..