Matrix Games Forums

MCM Updates - Western (sorry, no RED info - the detailed info for this will probably on be in Chinese or Russian)

-----------------------------------------
MCH-101 AW.101 Merlin - DB #3898 -

need to change year from 2017 to 2015.
http://www.defense-aerospace.com/articl ... -navy.html

Also, the AN/AES-1 ALMDS should not be a built it sensor, its a pod, as is on the MHC-53E and MH-60S. So, it should be added on the loadout.
https://thaimilitaryandasianregion.word ... licopters/

New DB Entry needed for MCH-101, for 2006 - I imagine it should have the same loadout as a CH53-E for the same time period (maybe/maybe not advanced things like AN/AQS-14A(V)1 but definitely passive towed devices, see #542 US CH-53E 1984 for ideas - I couldn't access a GlobalSecurity.org 2011 article about the craft - maybe you guys have info in JANE's)
http://global.kawasaki.com/en/corp/news ... 303-1.html

Can't find any info on any Airborne Neutralization device for the MCH-101. Also, need cargo loadouts for the MCH-101. That's the C in MCH Check out DB #877, Italian Cargo capable Merlin AW.101 for comparable references.
---------------------------------------------
CH-53E SeaDragon #2793 #4608 - no SeaFox AMNS on the #2793 AN/AQS-14 loadout - but the Seafox is on the #2793 An/AQS-20 loadout. No SeaFox AMNS on the #4608 AN/AQS-24B loadout, but there is one on the #4608 AN/AQS-20 loadout

Also, Cargo options need to be added to the CH-53(all years back to 1984 model), including a GAU-21 .50 cal (GAU-21 should be added to +2004 models only) - it can perform assault support missions nevertheless - dont know why the didn't call it the MCH-53E, but all US Naval Copters are able to do Cargo and the VertRep role
http://www.navy.mil/navydata/fact_displ ... d=400&ct=1
http://www.navy.mil/submit/display.asp?story_id=11442

Also need to add a new DB object for CH-53 in 2019, using AN/AQS-24C
http://www.minwara.org/wp-content/uploa ... asures.pdf

I have not found any source showing ALMDS being used on the CH-53E, so its ok not to have it, even though on the MCH-101
------------------------------------------------
Need to add An/ASQ-235 ArcherFish to DB - its been around for a while - all pictures I've seen appear that there are 4 vehicles on the mount, a sure improvement over SeaFox's single shot
http://money.cnn.com/news/newsfeeds/art ... E77827.htm
http://www.baesystems.com/en/product/ar ... ion-system
-------------------------------------------------
MH-60S #2794 #3713 - AN/ALQ-220 OASIS was also cancelled in conjunction with the AN/AQS-20. In fact the article (I've got a few more for ref if needed) simply states that the MH-60S is too underpowered for ANY tow based AMCM - so AN/ASQ-53 should also be removed. Thats why the RMMV cancellation was a disaster and all efforts of modern MCM Suites for the LCS rest with the CUSV. MH-60S will be relegated to AMNS and ALMDS, but the bottom belongs to CUSV.
http://www.aero-news.net/index.cfm?do=m ... 0103aee8da

AN/AES-1 ALMDS needs to be added to a new entry for MH-60S - again, like MHC-101, its a loadout, not built in. Its went operation in 2017, but 2nd link shows a photo from 2014, being used in Bahrain - not sure when you guys allow systems to be put on - during 'testing' and limited operational use, or full operational status
https://defensesystems.com/articles/201 ... laser.aspx
https://laststandonzombieisland.com/tag ... on-system/

Heh, can't read this website fully because of $$$, but through the grey, you can see that the Navy planned to certify the AN/ASQ-232 SeaFox on the MH-60S back in 2008-11 - I'd say 2013+ is ok to add the SeaFox, as with the CH-53E timesframe
http://www.globalsecurity.org/military/ ... s/amns.htm

Add An/ASQ-235 to MH-60S, but the problem is "WHEN" - I haven't found a "fully operational" source yet, but it is on the Navy Web Site (Heh, I'm sure they stretch the truth as well at times, but who can you trust? )
https://laststandonzombieisland.com/tag ... on-system/
http://www.navy.mil/navydata/fact_displ ... d=425&ct=2
---------------
SeaFox Killer ROV - add AN/ASQ-232 to its name
---------------


thats it for now - will put in requests for CUSV, MQ-8b/c, COBRA. Baracudda, and LCS (screw me, what a mess that ship is) next time

Thanks all. We'll definitely check out all links and follow up when we can. Have updated the db request list to this point.

Mike

A quick search revealed nothing, so sorry if I am missing something. Was wondering whether we could get a generic civilian drone added to the DB?

Any Plans for A Hypothetical Aim-120 Only Upgraded F-14 Bomecat

Hi everyone,

North Korea is still operating the Il-28 Beagle. So please add this...

Thanks

jimmyblond

ORIGINAL: jimmyblond

Hi everyone,

North Korea is still operating the Il-28 Beagle. So please add this...

Thanks

jimmyblond

Huh, surprised this wasn't already in DB3000!

For now I guess we can use the H-5 Beagle -- China (Navy), since it's functionally identical to the NK Il-28s.

BY DESIGN. See Wikipedia.

Both versions of the 23mm Gsh-23M gun mount carried on the various versions of the Backfire (Twin 600 rnds x 2 on the -B's and 1200 rnds on the -C's) have chaff/flare salvos listed as the weapons carried instead of gun bursts.

DB3k wish list updated to this point. Thanks!

Mike

Egyptian's Rafale

[*]#4362 - Rafale C -- Egypt (Air Force), 2017, 8x, F3R[/color]
[*]#4363 - Rafale B -- Egypt (Air Force), 2017, 16x, F3R[/color]

Name : 6 Rafale DM two seaters and eight Rafale EM single seaters ("M" is for "Masr", the Arabic word for "Egypt").

Date : The three first Egyptian Rafales were delivered on 20 July 2015, allowing them to take part in the opening of the expanded Suez Canal in August, and the next three on 28 January 2016. They are in service with the 203 Tactical Fighter Wing ‘Storm’/34 Squadron ‘Wild Wolves’.


Mounts and Loadouts :
- "#333 - SCALP EG -- 2004, Storm Shadow" delivered to Egypt would actually be the export version "#388 - Black Shahine [Storm Shadow] -- 2008".


Comms : Link 16 JTIDS was removed prior delivery to Egypt os it's not a NATO member.


http://www.defenceweb.co.za/index.php?o ... Itemid=107
https://world-defense.com/threads/egypt ... -pod.2313/
http://www.defens-aero.com/2015/06/rafa ... le-dm.html
http://www.taringa.net/comunidades/fana ... gipto.html
http://www.menadefense.net/2017/02/20/l ... precision/
http://www.lopinion.fr/blog/secret-defe ... ayer-21335


Note : waiting for reliable intels on Indian Rafale's equipment before suggesting anything. 36 have to be delivered in 2019.

---

Moroccan F-16

[*]3152 - F-16CJ Blk 52+ Falcon -- Morocco (Air Force), 2012-0, 16x[/color]
[*]3517 - F-16DJ Blk 52+ Falcon -- Morocco (Air Force), 2012-0, 8x[/color]

It seems that HARM missile also is part of the Moroccan Viper loadout :

https://theaviationist.com/2014/05/08/rmaf-f-16-video/

Along with GBU-10/12/24/31/38 :

("Morocco’s Bird of Prey", Paul Giannico, Combat Aircraft - June 2013.)

---------------------------------------------

2016 upgrade

[*]#???? - F-16CJ Blk 52+ Falcon -- Morocco (Air Force), 2016, 16x[/color]
[*]#???? - F-16DJ Blk 52+ Falcon -- Morocco (Air Force), 2016, 8x[/color]

Based on "#3152 - F-16CJ Blk 52+ Falcon -- Morocco (Air Force), 2012-0, 16x" and "#3517 - F-16DJ Blk 52+ Falcon -- Morocco (Air Force), 2012-0, 8x" respectively, I do suggest to create a 2016 version which have its "#1920 - AN/ALQ-187 I-DIAS -- Internal AN/ALQ-184" replaced by "#2215 - AN/ALQ-211(V)4 SIRFC [DECM] -- F-16C".

I assume that "#4397 - AN/ALR-93(V)" could have been upgraded to "#2217 - AN/ALQ-211(V)4 SIRFC [RWR] -- F-16C" too, however I'm not able to source it.
http://www.janes.com/article/65734/moro ... nsive-aids

In 2016 Morocco bought DSU-38 A/B Precision Laser Guided Sets, used with the KMU-572 guidance sets to create the Laser Joint Direct Attack Munition system.
http://www.boeing.com/resources/boeingd ... ounder.pdf
https://www.defense.gov/News/Contracts/ ... le/639406/
http://fr.le360.ma/politique/les-etats- ... ntes-60631

I thus suggest that a loadout with "#2259 - GBU-54(V)1/B LJDAM [Mk82] -- USAF, 2008" is added to this new version.

---

French Mirage 2000D 2016 loadout

[*]#3931 - Mirage 2000D R2.1 -- France (Air Force), 2016, ASTAC Pod[/color]

Since late 2015, there is a "combat proven" 4 x GBU-12 loadout used, which then require a third party laser designator.

However, experience has shown that during an aerial refuel sequence, pilots have to use the PC to keep up and thus have no more speed margin. So, Armée de l'Air have chose to only allow that loadout when no refuel planned. It might fall out of favor.

http://www.defens-aero.com/2015/11/phot ... bu-12.html
http://www.defens-aero.com/2016/04/inte ... suree.html

If you feel like so, I would suggest to create a "Requires Buddy Illumination" & "Not Refuel Capable" loadout with 4x #1906 - GBU-12D/B Paveway II LGB [Mk82].

---------------------------------------------

French Mirage 2000D MLU

A Mid Life Update is planned to extend 55 Mirage 2000D service life to 2030 and beyond, with first updated aircrafts delivered in 2019.

[*]#???? - Mirage 2000D MLU -- France (Air Force), 2019, #55[/color]

It could be based on aicraft #3931 - Mirage 2000D R2.1 with :

- #242 - R.550 Magic 2 Mk2 replaced by #1873 - MICA IR (and MICA Command Datalink added);
- Ability to drop mixed loadouts of, for example, a GBU-12 and a GBU-49.
- #479 - Damocles LDP Pod,#898 - PDLCT Pod and #1771 - Atlis II Pod replaced by the #3149 - Talios LDP-NG Pod.


http://www.dassault-aviation.com/fr/das ... francaise/
http://www.defens-aero.com/2016/07/dga- ... 2000d.html
http://www.combataircraft.net/2016/07/2 ... -upgraded/
http://www.air-cosmos.com/commande-de-l ... 000d-79449

vec l’intégration prévue du futur pod Talios (qui apportera beaucoup non seulement pour le ciblage mais aussi le travail de renseignement) de Thales
https://www.aerobuzz.fr/defense/la-deux ... age-2000d/

---------------------------------------------

French Mirage 2000N conventional loadouts

[*]#3933 - Mirage 2000N K3 -- France (Air Force), 2010-2018, ASMP-A Mod[/color]

It appears that 2000N K3 were also deployed during Operation Harmattan in 2011, performing "conventional strike and recon missions".
http://www.assemblee-nationale.fr/14/rap-info/i1233.asp


http://www.defense.gouv.fr/content/down ... t%3B16.pdf


I thus do suggest that loadouts #19742 and #19744 are added.

---------------------------------------------

[*]#????- Mirage 2000N K3 -- France (Air Force), 2016-2018, Chammal Mod[/color]

Since early November 2015, Mirage 2000N are operationaly using a 4 GBU-12 loadout.





http://www.defense.gouv.fr/air/actus-ai ... -sur-daech
http://www.defense.gouv.fr/air/actus-ai ... la-fayette

I do suggest that a new loadout, which "Requires Buddy Illumination", is created with 2x #1531 - 2000 liter Drop Tank, 4x #1906 - GBU-12D/B Paveway II LGB [Mk82], 1x #242 - R.550 Magic 2 Mk2 -- 1997 (The Magic being there for self defence and also as an AA IR sensor).

Prior to its deployment in Jordania to operate over Irak and Syria, the 2000N had to have its communications devices modified to be encrypted and Link 16 system to be installed.
http://www.defens-aero.com/2015/05/les- ... -irak.html

So I do suggest that a VHF Radio (Secure) and Link 16 JTIDS are added.

---------------------------------------------

[*]#1467 - Mirage 2000N K2 -- France (Air Force), 2011-2011, Harmattan Mod[/color]
Some pictures and an article suggest that the GBU loadouts were in fact ready from 2003-2004.



(2004, Fourty years of the FAS, Strategic Air Force)



"In 2003-2004, all aicrafts were given the ability to carry GBU-12, GBU-16 ou GBU-24 LGBs, target designation being provided by Nancy's Mirage 2000D or designation team on the ground (FAC)."
"Mirage 2000, l'ossature de l'Armée de l'Air", Eric Desplaces & Philippe Roman, Air Fan #319, June 2005.

I thus suggest that this platform is renamed "#1467 - Mirage 2000N K2 -- France (Air Force), 2004-2011, GBU Mod"

---------------------------------------------

- #19743 GBU-22/B LGB [Mk82], Requires Buddy Illumination
I'm on the fence about that loadout. I've never seens such a loadout and I think the GBU is too long to be safely launched while a (centerline) 1300 liter DT is carried. Alternatively, I do no think that the GBU pylons can be fitted on underwing stations. I would recommend to delete that loadout from that platform, unless proven wrong.

1300 liter DT

---

Talios Multi-Function Targeting Pod

[*]#3149 - Talios LDP-NG Pod [FLIR + LRMTS, 40k ft] -- 2019, Damocles Follow-on[/color]

It also have a TV Imagery sensor. It features Targeting to NTISR, Air to Surface and Air to Air mode.


https://www.thalesgroup.com/sites/defau ... 015-hd.pdf

Thanks Jan. Added to this weeks updates to our wishlist.

M

Additional MCM updates -
---------------------------------------

CUSV #2731 - The current MCM sensor for the CUSV, L-3 Klein 5000, is improperly modeled. http://higgshydrographictek.com/wp-cont ... 5000V2.pdf shows a range of 250m and detection examples of 150m, however the DB has it at 0.5nm range. Further, I could only find one article showing the L-3 had been tested with the Textron CUSV, https://www.marinelink.com/news/maritim ... ar-systems, however numerous articles are stating that the Navy is testing with its tried and true AN/AQS-20A and AN/AQS-24 series. The L-3 simply doesn't meet Naval requirements. http://www.navy.mil/navydata/fact_print ... t=2&page=1 https://defensesystems.com/articles/201 ... /uiss.aspx - Therefore the L-3 should be removed from the CUSV and replaced with the AN/AQS-20, 24A, and 24B (will need different versions of the CUSV in the database as only one can be carried at the same time).

Further, I haven't been able to find any details on the specifics of the UISS, which is the Unmanned Influence Sweeping System. Because there are no stats in the database describing detailed differences between sweeping systems, like Mk106 vs OASIS vs Generic Mag/Acous Mine Sweep, I don't yet have a current recommendation for this change. The Generic Sweeper does seem to trigger any mine, although its too close an severely damages the CUSV - thats not a DB issue however, I've address that in another issues/observations thread regarding mines.

Nevetheless, the UISS (or whatever sweeper) cannot be carried simultaneously with a sonar suite. The CUSV is a 'multi single-mission' (like the LCS) platform requiring several different DB objects, because surface ships dont have loadouts. Therefore there should be different CUSV Versions:
a. CUSV - cargo loadout of 2tn, 2sqm, and 4 personnel - this is for the ISR mission of the CUSV, but its been stated that CUSV can be driven and used manually
b. CUSV - Generic Acous/Mag Mine Sweep (until details of the UISS can be known)
c. CUSV - AN/AQS-20A Towed Sonar
d. CUSV - AN/AQS-24A Towed Sonar
e. CUSV - AN/AQS-24B Towed Sonar
f. CUSV - no cargo, nothing towed, but ROV docking capacity for Knifefish UUVs - CUSV models a-e should not have a dock for UUVs

All of the above missions for the CUSV are mutually exclusive and therefore should have unique DB entries.

-------------------------------------------------------------------------------------------

MH-60S #2794 #3713

In above DB Request post, I asked for the AN/ASQ-235 Archerfish AMNS and the AN/AES-1 Airborne Laser Mine Detection system to be added to the MH-60S. I'd like to clarify loadout request additions for the MH-60S.

a. 1x ALMDS, 1x 120 USG Drop Tank
b. 1x AMNS, 1x 120 USG Drop Tank
c. 1x ALMDS, 1x AMNS
d. 2x AMNS

These combinations will allow the proper flexibility needed for the MH-60S to work in conjunction with the CUSV or other surface based MCMs, due to the Navy's findings that the MH-60S is unable to tow the AN/ASQ-20A,24A/B or any influence mine sweeping device.

-------------------------------------------------------------------------------------------

AN/AQS-20A #2471 - Interesting unclassified find - http://www.nmfs.noaa.gov/pr/pdfs/permit ... ea2012.pdf - available only because this was a public safety environmental impact statement, not a military capabilities report - nevertheless, in section 2.3.1.1 shows the AN/AQS-20 having a FWD Sonar, used "to minimize collisions with sub-surface objects", uh, namely mines IMO. Current CMANO model, with Side Sonar only, leaves an awful gap so that the CUSV towing one can actually run right into a mine. Not good. I'll leave it to you guys on how to model this sonar, with this detailed info. I would say the side sonars are the true synthetic aperture sonars, designed for detection and classification, but so the FWD sonar should be able to detect a mine, or "an object" like a whale, and change course, and assume its a mine until classified.

As the AN/AQS-24A,B,C are made by the same manufacturer, I think its perfectly safe to assume that these sonar systems have the same FWD capability.

-------------------------------------------------------------

ESB Expeditionary Sea Base #2684 - Helicopter Specific Magazines need to be created and allocated for this unit - The magazines should hold several dozen SeaFox AMNS. and enough sweeper/sonar equipment for 4 MH-53Es. Regarding the 4 MH-53Es, the database only allows 2 MH-53Es (large aircraft) which is incorrect. This Navy article describes 4 operating spots for MH-53Es. http://www.navsea.navy.mil/Media/News/A ... er-at-sea/

The magazines should also accommodate MH-60S AMCM aircraft, although I have yet to find an article showing an MH-60S MCM mission on the ESB - its perfectly rational to allow such. Therefore it should also contain 8x AMLDS and a few dozen AN/AQS-235 ArcherFish loadouts.

Also, the ESB only has 2x SmallDavit/Dock capacity for CUSVs - the ESB is gigantic - it surely can support 4-8 CUSVs - Having 1x Davit is fine to reduce launch capacity but several CUSVs can fit on that dock. I've see 1/2 LAV Battalion parked on the dock of an ESD (the ESB's cousin without a flight deck)

---------------------------------------------------------------

Updates to LCS - this is a bit complex, due to the multi-mission package capabilities of the LCS

Base LCS Capabilities - http://www.defenseindustrydaily.com/its ... es-016450/
Therefore base LCS has NO VDS SONAR, but has a mine detection sonar apparently. Base LCS having no sonar is one reason Congress is freaking out about the LCS's single-mission role per package. Also the 30mm cannons are not part of the base package, only the ASuW package.

LCS AWS Package - current Helicopter package needs to increase a larger variety of torpedoes to accommodate the MH-60R Helo. It will also need the VDS (the current one is ok) and AN/SQR-20 Multi-Function Towed Array (MFTA) https://defensesystems.com/articles/2016/11/01/lcs.aspx http://www.navy.mil/navydata/fact_displ ... d=412&ct=2 This package doesn't get the 30mm, thats only for the ASuW. AWS package also has a new lightweight towed torpedo decoy(LWT), but I can't find details on it.

LCS ASuW Package - http://www.navy.mil/navydata/fact_displ ... d=437&ct=2 this package contains the 30mm, but no ASW sonar whatsoever.

LCS MCM Package - no ASW sonar, no 30mm, No missiles - just the MCM Package which is defined here - All of the gear however it external to the LCS MCM DB entry (Helos, CSUVs, KnifeFish, etc) - however an LCS Helo Magazine will need to be created foe the LCS MCM Package DB Entry - it will need 2x ALMDS and a few dozen ALMN AN/AQS-235s. http://www.navy.mil/navydata/fact_displ ... d=425&ct=2

The 'Minor-Modified LCS' appears to be the current decision for improving all LCS base package capabilities - OTH NSM/JSM missiles, MFTA, Torp Decoys - but this is meshing with the SSC Requirements (for the post 32 LCS production ships) which would have even more capabilities - and all of this stuff won't happen until +2018, so we can wait for more info on this to solidify. Here is a good article on it https://whitefleet.net/2016/12/11/exami ... d-frigate/

I even watched the Congressional Hearing on the LCS in December - wow, what a mess this ship is!!

-----------------------------------------------------------------------------
#645 Echo Voyager

http://boeing.mediaroom.com/2016-03-10- ... for-Months

The Pier/Dock/Davit=ROV/UUV size means that it can dock inside a CUSV. I don't think so. Too big to even dock in an LCS. As its got enough battery to operate for "months", I don't think it was designed to dock with any ship to be honest. I would simply set it to Pier docking only. Also, I am not sure that the 3000m ROV Operating radius is for. Not allowed to operate more than 3lm from mothership?? WEll, if so, no problem, as it should never have a mothership - its fully independent.

-------------------------------------------------------
AN/DVS-1 Coastal Battlefield Reconnaissance & Analysis (COBRA)
http://www.navy.mil/navydata/fact_displ ... =1237&ct=2
http://www.navy.mil/submit/display.asp?story_id=56748

This is new and needs to be added to the database. From the difference sources of what it can do, I would say it should be modelled like the ALMDS, being able to detect mines in very shallow water and surf conditions, but also be like a ground radar - all very short range, maybe 0.2nm.

It also needs to be available as a loadout for the MQ-8B and MQ-8C UAVs, #3458, #3455, #3456, #4031 - As well, 2x AN/DVS-1 objects need to be added to the LCS MCM Heli Magazine object (requested above), so their UAVs have the payload built into the MCM package. Not needed for standard MC-8b/c use throughout the fleet.

That's it for now, think I'm done with MCM for a while

So, i had a couple questions on Russian kit

1) MIG-35 loadouts: Currently in the DB its max A2A loadout is 4 Adders and 2 Archers, and its only A2G missile is 2 x Krypton C. Its quouted on Deagle as being able to haul 4 each of either Krypton A or C, as well as being able to take the KAB-500S GLONASS guided bomb, with apparently the option for buddy refueling like the Russian 29K does. Wikipedia says its also supposed to be able to haul 4 Khedges and LGBs, though i'm unable to find what source they use for that. Also, given that the 35 has the same two extra hardpoints that the 29K has and Wiki is apparently crediting it with up to 8 A2A missiles, it wouldn't really surprise me if they could drop the 1150 liter tanks to get a 6 Adder/2 Archer loadout like the 29Ks in the DB already do, though thats' admittedly speculatory.

2)Russian LG/TV Bombs in general: Is there a reason these are all at 75% reliability? I can't find any info on reliability issues for KABs that would make them worse than the 85% that seems to be the standard for other LGBs in the DB. Even 'Nam era Walleyes are at 85%. I have to imagine any early issues would be smoothed out by now.

I'm not sure if it has been mentioned, but all versions of the F-24 Hellcat II have PROBE REFUELING under their properties. Since this is supposed to be a naval version of the F-22 shouldn't it be changed to DROGUE REFUELING?

[*]#61 - Tu-142MK Bear F Mod 3 -- Soviet Union [-1991] (Naval Aviation [AV-MF]), 1983-1991[/color]
[*]#770 - Tu-142MZ Bear F Mod 4 -- Russia [1992-] (Navy), 1994[/color]
[*]#990 - Tu-142MK Bear F Mod 3 -- Russia [1992-] (Navy), 1992[/color]
[*]#996 - Tu-142MK-E Bear F Mod 3 -- India (Navy), 1989[/color]
[*]#3800 - Tu-142MK-E Bear F Mod 3 -- India (Navy), 2011[/color]
[*]#2619 - Tu-142MK Bear F Mod 3 -- Ukraine [1992-] (Navy), 1992-1992[/color]

MK : Korshun system.
MZ : Zarechye radio sonobuoy, Sayany ECM.

MK : 1980 (19 November)
ME : 1988 (April), 8 to Indian Navy (INAS 312, Dabolim). Decom 29 March 2017. Albatross’
https://www.indiannavy.gov.in/content/i ... er-jubilee
https://www.indiannavy.nic.in/content/tu-142m

General Data :
- Length : 53 m
- Wingspan : 50 m
- Height : 13.6 m
- Empty Weight : 93900 kg
- Max Weight : 185000 kg (MTOW, in flight after refuel: 187700 kg)
- Max Payload : 9000 kg
- Cockpit visibility, Forward : could be Excellent as it do have a navigator sitting in a glazed nose, Aft : could be Average, rather than Poor, as it does have a tail gunner station.

Sensors :
- MK and ME versions may not have been fitted with "#872 - DECM [Sayany-M]" and would have been fitted with "#2596 - SPS-100 Rezeda" instead.
- MZ version may have been fitted both with "#872 - DECM [Sayany-M]" and "#3330 - SPS-160 Geran".
- No "#788 - ELINT [Kvadrat-2] is mentioned in my sources for the Tu-142.
- #3800 - Tu-142MK-E was equipped with a "#1843 - AES 210E" suite.

Mounts/Stores/Weapons :
- APP-50 may not have been fitted on MK and ME versions.
- MZ version would have been fitted with "#2535 - RGB-16/#2536 - RGB-26/#2537 - RGB-36" instead of "RGB-15/25/55A/75".
- MZ version would have been equipped with "#482 - APR-3" (Oryol-M) instead of "#1735 - APR-2 Orlan-M" (Yastreb-M).
- All versions would have been able to carry 3 torpedoes, not 6. That is 3x APR-2 or 3x AT-3, not both.
- ME (Indian) version would have used "#1123 - AT-3ME [UMGT-1ME Orlan" instead of "#1468 - AT-3 [UMGT-1 Orlan".
- All versions could carry depth charges as Zagon guided depth charge*, #201 - PLAB-250, #2280 - PLAB-120, Ryu-2 nuclear depth charge* and air dropped mines.
* not in the DB, yet, suggestion will follow as more details are found.

Comms :
- as for radios, it does have 3* HF (2 R-857G, 1 R-866) and two UHF (R-832M).

Propulsion:
- Engines : MK variants uses NK-12MV engines while the MZ variant uses NK-12MP engines (same rating, more reliable).
- Military Static SFC at S/L : 0,463 kg/h/kg (0,36 would be at cruise speed @ 11000m)

Fuel:
- 83900 kg


Sources:
- "Russia's Warplanes" Vol.2 (2016), Piotr Butowski, ISBN 978-0-9973092-0-1.
- "Last call for rare Bears", Angad Singh, Combat Aircraft - June 2013.
- "Jane's Aero-Engines" (2001), Bill Gunston.

About the first question. Changes in MiG-29M/M2, MiG-29KR/KUBR and MiG-35/De were requested with credible sources. All we need is wait to see changes in DB3K.

About the second, good point. They discussed about the DB issues last week in this thread. IMO Looks like some soviet/russian entries are very old, from the Cold War, like the reliability of the KAB bomb series.

Wish list updated again to this point.

Mike

---> Thanks a lot for your hard work Mike and Ragnar, it's always a pleasure to dedicate time and resources into research knowing that you guys actually do care. What you provide us probably is the most exhaustive DB in the gaming industry.

---

[*]#271 - A.400M Grizzly -- Belgium (Air Force), 2020-0, 7x[/color]
[*]#1389 - A.400M Atlas [Grizzly] -- France (Air Force), 2014-0, 50x[/color]
[*]#1403 - A.400M Grizzly -- Germany [FRG/Reunified] (Air Force), 2015-0, 53x[/color]
[*]#1419 - A.400M Grizzly -- Spain (Air Force), 0-0, 27x[/color]
[*]#1420 - Atlas C.1 [A.400M Grizzly] -- United Kingdom (Royal Air Force), 2016-0, 22x[/color]
[*]#1423 - A.400M Grizzly -- Turkey (Air Force), 2014-0, 10x[/color]

Mounts and Loadouts:
- it can also transport 116 fully equipped troops, I thus suggest to add Trooper store and loadouts.

- by the way, do you want to make helicopters type of cargo?


Armored plating, chaff/flares dispenser and DIRCM seems to be (retro)fitted on most national versions, not much details though other than telling the Atlas is now able to perform "tactical", in opposition to purely "logistical", missions.

Maybe French #1389's Sensors could be fitted to all version?

http://www.mbda-systems.com/product/saphir-400/
http://www.pemas.pt/israeli-dircm-laser ... rt-planes/
http://www.sfte-ec.org/node/916
https://www.raf.mod.uk/rafbrizenorton/e ... matlas.cfm
https://www.francebleu.fr/infos/societe ... 1465996390
http://www.defense.gouv.fr/terre/actu-t ... e-de-terre


[*]#271 - A.400M Grizzly -- Belgium (Air Force), 2020-0, 7x[/color]

Its name in Belgian service is "A.400M Atlas", deliveries will be made between 2018 and 2020.
http://www.mil.be/fr/materiel/airbus-a400m-atlas


[*]#???? - A.400M -- Luxembourg (Army), 2019, 1x[/color]

- Luxembourg : ordered 1 aircraft, to be delivered in 2019. It will be used from Melsbroek (Brussels) as part of the European Air Transport Command. Pilots are currently flying within Belgian 15th Transport Wing.
http://www.armee.lu/actualites/2015/der-grove-vogel

[*]#???? - A.400M -- Malaysia (Air Force), 2015, 4x[/color]

- Malaysia : ordered 4 aircrafts, first received in 2015, last in 2017. They are operated by the 22 Skuadron on Subang AFB. Buddy stores will be installed on at least two aircrafts, to supplement current KC-130T fleet.


https://airbusdefenceandspace.com/newsr ... air-force/
https://www.nst.com.my/news/2016/01/121 ... m-aircraft

---

[*]#774 - C.160NG Transall -- France (Air Force), 1982-0, 29x[/color]
[*]#1696 - C.160D Transall -- Germany [FRG/Reunified] (Air Force), 1969-0[/color]
[*]#1872 - C.160F Transall -- France (Air Force), 1968-0, 50x[/color]
[*]#1873 - C.160Z Transall -- South Africa (Air Force), 1970-1997[/color]
[*]#1874 - C.160FR Transall -- France (Air Force), 1995-0, 50x[/color]
[*]#2169 - C.160NGR Transall -- France (Air Force), 1996-0, 29x[/color]

- The Transall can airdrop cargo weithing up to 8 tons



[*]#??? - C.160T Transall -- Turkey (Air Force), 1971, 20x[/color]
- Turkey : bought 20 aircraft from the Luftwaffe, delivered in 1971, operated by the 221 Filo from Kayseri Erkilet Airport.

---

[*]#220 - Airbus A.310-304 MRTT -- Germany [FRG/Reunified] (Air Force), 2009[/color]

It can transport 214 passengers/troopers, or 41600 Kg of Cargo, none air-droppable.
http://www.luftwaffe.de/portal/a/luftwa ... tran/a310/

Added to our list. Thanks again Jan for doing such a good job giving us the info we need!

Mike

For the newest Russian corvettes Stereguschiy class, here is a link to a press release about it:
http://rusnavy.com/news/navy/index.php?ELEMENT_ID=16470

Main takeaway is this quote:

Stealth technology was widely used during construction of the ships, as well as 21 patents and 14 new computer programs. Newest physical field reduction solutions were applied too. As a result, designers considerably reduced the ship's radar signature thanks to hull architecture and fire-resistant radar-absorbent fiberglasses applied in tophamper's design.

From that, I'd say that the Corvette warrants at least competitive RCS to modern designs, if not superior. But, the degree is up to CMANO designers.

Edit: a question, is the SM-3 limited to exo-atmospheric interceptions?

72 USAF F-16s getting AESAs (APG-83), work completed by early 2019

http://alert5.com/2017/06/02/usaf-order ... its-f-16s/
https://www.defense.gov/News/Contracts/ ... e/1198370/