Skip to content
View in the app

A better way to browse. Learn more.

HarpGamer

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Requests for the HCDB (Official DB of HCE) and HCDB2

Featured Replies

  • Replies 1k
  • Views 260.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Already done.

  • Enrique, if you would be so kind, can you post a list of the carriers where you think capacity needs to be adjusted, and some authority for the requested change. (And, as you know, HCCW has its own th

Posted Images

Some fighter-bomber airborne radars are flagge as LDSD and AS(airborne), when very probably should be LDSD and SS(airborne), I think is a typo keeped for long time.

Also another few qualified as RO I think should be AS.

 

I think this is a complete list:

40977 APG-63(V)1 AESA

43483 APG-63(V)2 AESA

43670 APG-63(V)3 AESA

43311 APG-66(V)2

43335 APG-66(V)3

43220 APG-68(V)5

43300 APG-68(V)10

43555 APG-82(V)1 AESA

43425 APQ-104 (For F-8E(FN) and F-8P Crusader, is flagged as RO, I think it should be AS).

43361 APQ-113 (For F-111E, is flagged as RO and SS, I think it should be AS and SS).

43497 APQ-161 (For F-111F, is flagged as RO and SS, I think it should be AS and SS).

 

Thank you. Very helpful.

This is terrific. A few tiny things: INTL Helix A has 600+ NM range, seems a bit much.

 

This is because of the permanently attached external fuel tanks. This INTL entry now belongs to China, but will still be Ka-28 Helix.

And another thing.... Almost all of the new USN/USMC F/A 18 family needs a Small Aircraft runway, making it impossible to land on US aircraft carriers. Not to be a pest, this is a beautiful thing you are doing....

And another thing.... Almost all of the new USN/USMC F/A 18 family needs a Small Aircraft runway, making it impossible to land on US aircraft carriers. Not to be a pest, this is a beautiful thing you are doing....

 

Intentional but temporary. I should have probably included the rest of the changes but I am tackling Super Hornet now and the issue will be fixed up in the next version.

A not very transcendent type, but discovered working on the USS Porter/Sea Shield 2017 scenario:

 

Romanian IAR-330 Puma Naval (2008+), only three delivered from 2008.

The Puma Naval is equipped with RDR-1500B radar, RWR (Or ESM), FLIR, BAE-1 UMTohan 45 Kg deep charges, SIN-100 dipping sonar and Stingray ASW torpedoes (Torpedoes added from September 2015).

 

Sources:

http://www.rumaniamilitary.ro/radarul-de-pe-puma-naval

http://www.rumaniamilitary.ro/un-elicopter-antisubmarin-puma-naval-prima-varianta

http://www.rumaniamilitary.ro/iar-ghimbav-livreaza-joi-ultimul-elicopter-iar-330-puma-naval

http://www.aripi-argintii.ro/aparatdezbor.php?p=52

More urgent is probably the update of the SPY- series of radars, mainly the ranges and matching platforms (SPY-1 are all PESA radars, HF and SS capables), but many data are scarce or doubtful:

 

SPY-1A: range stated as 175 nm in the DB (a typo, as commented), probably should be 275, or at least 250 as in the Smarter Radars article.

Employed by:

Ticonderoga-class cruisers up to CG-58, with SPS-49(V)1-3 as long range back-up.

 

SPY-1B: range stated as 175 nm in the DB, probably should be 275.

Employed by:

Ticonderoga-class cruisers from CG-59 (USS Princeton), with SPS-49(V)7-8 as long range back-up.

 

SPY-1B(V): range probably should be 275. Upgrade to -1B version, retrofitted to CG-59 and up.

Employed by:

Ticonderoga-class cruisers from CG-59 (USS Princeton), with SPS-49(V)7-8 as long range back-up.

 

SPY-1D: range stated as 175 nm in the DB, probably should be 275, as stated in SITREP 47, page 12 (In relation to Japanese warships of Senkaku crisis).

Employed by:

Burke-class up to DDG-90 (USS Chafee).

Kongo-class (Japan, in the DB equipped with the older SPY-1B).

The first four of Alvaro de Bazan-class (Spain, in the DB equipped with older SPY-1B).

 

SPY-1D(V): Add new entry. Improved variant, range stated in some sources as a 10-15% more, perhaps 316 nm, but I don't find now the reference: https://mostlymissiledefense.com/2012/08/03/ballistic-missile-defense-the-aegis-spy-1-radar-august-3-2012/

Employed by:

Burke-class from DDG-91 (USS Pinckney) onwards to DDG-123 (USS Lenah H. Sutcliffe Higbee).

Atago-class (Japan, in the DB equipped with older SPY-1B).

King Sejong the Great (KDX-III)-class (South Korea, in the DB equipped with older SPY-1B).

The fifth ship (F-105 Cristobal Colon, in the DB equipped with older SPY-1B) of Alvaro de Bazan-class (Spain).

Hobart-class (Australia, Spanish-designed).

Aegis Ashore (In the DB equipped with older SPY-1B).

 

SPY-1F: probably no changes on its 185 nm ranges, but modes should be HF/SS as the rest of SPY-1 types, and not HF/AS.

Range is stated as 54% of SPY-1D.

Employed only by Norwegian Nansen-class (Spanish designed).

 

SPY-3 MFR/DBR X-band: range stated in the DB as 344 nm, and in SITREP 50, page 8 as 113 nm. Has HF and SS modes, but not simultaneously. Is AESA. Only three faces, all the other SPY- have four faces.

Employed by Zumwalt and Gerald Ford classes.

Link not so easy to find: https://en.wikipedia.org/wiki/AN/SPY-3

 

SPY-4 VSR (previously SPY-2 VSR) S-band: range stated in SITREP 50, page 8 as 239 nm. Has HF and SS modes. Is AESA.

Employed only by Gerald Ford-class (discarded its use in Zumwalt because budgetary reasons).

 

SPY-6(V) AMDR: range stated in the DB as 250 nm, and in SITREP 50, page 8 as 522 nm. Has HF and SS modes. Is AESA.

To be employed by Burkes Flight III from 2023 (First boat and proposed sometimes by CG(X).

http://defenseph.net/drp/index.php?topic=170.0;wap2(States range of SPY-1(D) as 400 nm, and SPY-6 as 945 nm).

Might we see the LRASM in MK 61 VLS cells in this or a future version? Alaso, a niggle: Many versions of the NH90 helicopter have a Russian attack loadout in the "ferry" spot. Thanks.

Might we see the LRASM in MK 61 VLS cells in this or a future version? Alaso, a niggle: Many versions of the NH90 helicopter have a Russian attack loadout in the "ferry" spot. Thanks.

 

Thanks. Probably a typo digit in the DB entry.

I see #2382 Bunker Hill (CG54/15) has SQR-19B TACTAS, and she should be equipped with the more effective TB-37U MFTA, as the older #3106 Bunker Hill (CG54/10), as the other ships of the Cruiser Modification Program (I was reworking for HCDB2 the Dynamic Moongose 2015 scenario).

 

Probably the same errour in #42 Bunker Hill (CG70/10).

A little incoherence in the AIM-120 missile variants:

AIM-120A: PH=70, Range=40.

AIM-120B: PH=70, Range=40.

AIM-120C: PH=75, Range=40.

AIM-120C5: PH=75, Range=44.

AIM-120C6: PH=85, Range=44. I think this PH value is a typo and it should be 75.

AIM-120C7: PH=75, Range=44.

AIM-120D: PH=80, Range=60.

  • 2 weeks later...

Another irregurity discovered working in a scenario (when comparing 2009 with 2015 Burkes, is not exhaustive), only the latest two mounts are erroneous, with many void VLS.

 

- Entry 3 Burke Flt IIA (DD103/09):

 

- Mount 60114 Mk41 VLS x32 DDG79 05: 32xVLS, 26xTACTOM + 24xESSM (Quad-packed in 6xVLS) = 32 occupied VLS.

 

- Mount 60155 Mk41 VLS x64 DDG79 08: 64xVLS, 28xTACTOM + 28xSM-2MR + 8xVL ASROC = 64 occupied VLS.

 

- Entry 4 Burke Flt IIA (DD103/15):

 

- Mount 60172 Mk41 VLS x32 DDG81 15: 32xVLS, 26xTACTOM + 20xESSM (Quad-packed in 5xVLS) = 31 occupied VLS, probably should be + 24xESSM (Quad-packed in 6xVLS) = 32 occupied VLS.

(Affected Burkes entries 4, 5, 2221, 2122, 2265 and 2).

 

- Mount 57361 Mk41 VLS x64 DDG81 15: 64xVLS, 24xTACTOM + 24xSM-6MR + 8xVL ASROC = 56 occupied VLS, lacks 8xVLS to be occupied, perhaps with SM-3.

(Affected Burkes entries 4, 5, 6, 2122, 2265, 2 and 7).

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.