Rocket & Missile Programs of the GCK

## Introduction

The GCK began rocket & missile research in earnest in 19AF subsequent to the capture of Aerah flying bomb plans during the West Aerah Intervention. With the creation of a research program based out of Nordburg, Neuu Uthenland, the GCK set after reverse engineering and improving the technology.

Each branch of the *Allkomma*nd originally had its own research and development initiatives towards rocket and missile development. This resulted in several small unique development programs, nearly all of which can trace their origins in 19AF (1941). This would result in the operational introduction of the GCK's first guided missiles, namely the SSM-2 *Arrouu* in 24AF and the ASM-3 in 25AF. Non-military rocketry experimental development in turn began in 25AF with the *Transkontinental-Airpostale* project for high speed rocket mail.

Ballistic missile research was jumpstarted in 24AF with the secret signing of the *Greck*-Osterrecht Technical Cooperation Treaty, which involved the exchange of Osterrecht's ballistic missile technologies for support developing the first MRBM via ballistic cruise or boost-glide technology. The public introduction of this treaty in July 25AF prompted the Nordisle Autonomous Scientific Region to issue *The Nasr Report on Implications of Suborbital & Orbital Technologies,* which forecasted that suborbital and orbital "aircraft" would supersede air superiority as the dominant military playing field. Subsequent to this, in January 26AF the *Greckaf* organized the Office for Suborbital and Orbital Projects, or OSOP, and began work on the GCK's first steps at a full fledged space program.

## Military Rockets & Missiles

### Unguided Rockets

*Note: the unguided rocket category is defined as rockets designed without the original expectation of guidance, thus many prototype guided missiles originally tested sans guidance system are classified under their respective categories.*

#### DRB-2

Formally designed for rocket assisted take off purposes, the **DRB-2 (Disposable Rocket Booster-2)** is a simple, primitive solid fueled rocket first designed and produced for the XSSM-1 project in 19AF, and would continue to see use as launch boosters for the SSM-2 & ASM-1 *Arrouu* systems through 24AF, when they would begin to be phased out in lieu of the succeeding DRB-3 design. While it would share the DRB designation with the subsequent Darby family of boosters, they would not be used commonly enough for the Darby moniker to be applied to them.

#### DRB-3 through DRB-6: the "Darby" family

Beginning in 24AF (1946), a new series of booster rockets were introduced, this time intended specifically for a variety of rocket and missile projects based out of Nordburg instead of as an aviation booster: larger, heavier and profoundly more powerful, these boosters represented an epoch change in GCK rocket and missile programs. The single pipe DRB-3 unit weighed just under a ton at 1750 lb weight, and would produce 33,000lbf/150KN thrust with a 5.3 second burn time. This model would undergo aviation testing, but its heavy weight and profound force would restrict its application potential for aviation. It itself would serve as the powerplant for the experimental XAAM-2 project, as well as playing a role in the later stages of multiple XSAM projects and the XSSM-4 project, and as boosters for late production SSM-2 units. The type's major production presence lead to it commonly being referred to as a "**Darby Three**" or "**Lean Darby**" booster.

The DRB-3 rocketmotor would however see further experimentation; a quartet of DRB-3s were bound into a singular unit via the 3.5 ton **DRB-4.** Producing a massive for the time 132,000lbf/600KN thrust with a 5.3 second burn time, the DRB-4 (also known as a "**Darby Four**" or "**Stout Darby**" booster) was well suited for launching and accelerating ramjet powered missile designs to speeds where the ramjets could take over, making the **DRB-4** the primary first stage unit for the airbreathing XSAM-2 and XSSM-4 projects. Early on in the production of the Darby Four, an improved variant was introduced with stabilizing fins, known as the **DRB-4B,** which would see serial production as the initial booster for the XSAM-1 and XSSM-4 projects.

Subsequently, the evolution of the DRB-3 linneage led to the **DRB-5** doubling the fuel capacity of the DRB-4 arrangement, resulting in a 7 ton booster producing 132,000lbf/600KN during its 10.6 second burntime. Essentially a scaled up DRB-4B, the "**Darby Five**" or "**Tall Darby**" was created specifically for the XSAM-4 project, but is expected to see further use in subsequent rocketry developments. Penultimate to this, the **DRB-6** adds enlarged stabilizers with a quartet of DRB-3 boosters in the 10.5 ton "**Big Darby**" arrangement. Furthermore and perhaps most substantially in variation to the Tall Darby which preceded it, the Big Darby attempts to trade thrust for burn time by utilizing alternate twin engine burns in its main stage, giving the type a 21.2 second burn time and between 300KN and 900KN of thrust dependent on mission profile via the tertiary DRB-3 boosters, making the Big Darby a mark of the GCK's first tentative steps into ballistic rocketry.

#### DRB-7/SSM-5H "Foolish Devil I"

(finless unguided variant of *Lucifyr I*)

## Guided Missiles

### Surface to Air Missiles

The *Allkommand,* noting the limitations in the XSSM-1 and SSM-2 programs, did not pursue anti-aircraft technologies with the same interest as it did anti-surface rockets. The navy felt that the threat posed by jet and rocket powered aircraft (and, it assumed, rockets and missiles) was best addressed with higher rates of fire in tandem with radar assisted targeting, resulting in developing the complex T24M1-9/20 Lig-AA apparat for shipboard deployment. Given the size commitments of early missile systems and the anticipation that naval units would be fighting waves of enemy aircraft, this was found to be a superior option, and SAM development was not pursued by the navy. The *Grecka* in turn felt that larger caliber AAA was the solution to defense of land installations, as they anticipated higher flying bomber formations as the primary threat. The army's SAM development in earnest would not begin until 24 AF (1946), predominantly on political & economic grounds as analysts noted that at altitude thousands of 102mm and 127mm shells would need to be fired per average target takedown. Begrudgingly based on this cost assessment a development project was begun, but at a much lower priority than the XASM, XSSM and XAAM programs, and accordingly experiencing slower progress than other design processes.

#### XSAM-1

Unlike surface targeted missiles utilizing the *Ekko* signal tracking system, the GCK's **XSAM-1** program essentially had to begin entirely from scratch, as all of its other projects had all at some level drawn lineage from the Aerah inspired XSSM-1's technologies, albeit with a number of progressive improvements to the design's propulsion and targeting technologies. Combined with the *Allkommand* retaining a general doctrinal preference for a radar-targeted 127mm gun project, this would result in a prolonged development process on the propulsion, targeting and guidance axis. With *Nasr II* pulsejets being inefficient at higher altitudes and the issue only moderately addressed via the *Nasr IV* motorpulsejet design, and with the *Nasr I & III* jet projects being reserved for manned aircraft projects, development was centered around the *Nasr V* ramjet engine. Given inherent inaccuracies of the available technologies, it was determined that the XSAM-1 would require a profoundly large warhead and very high speed to reduce the odds of interception by hostile bomber's defensive capabilities.

Guidance consideration was made towards line of site manual control, but given the presumed very high altitude of operations this option was quickly discarded; the airfleet's experimental *Marxsman* beam-riding technology previously tested on the failed XAAM-1 was considered next in tandem with the concept of using radar in lieu of optical targeting. This was shown to be ineffective at the ranges the project was intended to engage at as beam-riding loses accuracy proportionately in relation to distance to target. These challenges ultimately culminated in the development of multi stage, multi sensory targeting arrangements, also known as the MUSTMUSE system.
While it would take some time to perfect the necessary technologies to fully introduce an effective surface to air missile, the physical structure of the missile was designed in a timely fashion, and testing of the unarmed, unguided **XSAM-1Aa** prototype in an unguided form would begin in 25AF, utilizing basic inertial guidance technology to stabilize what was the largest ground based missile yet produced by the GCK as a placeholder. The first multistage design tested at Nordburg, the XASM-1 relied on the new DRB-4 solid fuel booster to vertically launch the missile and accelerate it to a speed wherein the second stage's four *Nasr V* ramjets can take over.

Beginning in early 26AF, testing moved to the lengthened **XSAM-1B** design, representing the first flight deployment of the MUSTMUSE apparat. Subvariants in testing, the **XSAM-1Ba** and **XSAM-1Bb**, represented different configurations for its launch stage. While the MUSTMUSE system would prove effective and additionally remarkably resistant to hostile countermeasures, the size of the XSAM-1 drew criticism: at over 43 feet in overall length when assembled atop the more conservative DRB-4 booster rendered the type profoundly unwieldy, and likely only utilizable from fixed defensive positions. Never-the-less, development continued: predominantly due to a lack of substantial rival projects. While design work is underway for a **XSAM-1Bc** (horizontal launch) and **XSAM-1Bd** (vertical launch) navalized variants, the *Grecken* remains ambivalent at best to the project, given the difficulty of integrating the type into existing designs and the performance sacrifices required to incorporate the large missile system into the next generation of designs: these concerns ultimately facilitated the development of the **XSAM-2B project**

#### XSAM-2A

Developed in parallel with the complex XSAM-1 project, the **XSAM-2** mirrors the design philosophy proposed by a joint airfleet and naval aviation design requirement for a minimal stand-off ASM that was issued in 23AF; similarly, in contrast to the large and complex XSAM-1, the XSAM-2 represents what might be considered the GCK's effort at making the most minimal SAM missile system with its existent technologies. Pioneering the use of a *neckcouul* styled air intake, the XSAM-2 only has space for limited liquid fuel for its *Nasr V* ramjet engine, with the rest of the nosecone featuring ground control receivers: at present, the XSAM-2 lacks a warhead, making the type stand out as one not likely to enter production but more as a technological development and demonstration design. It does however represent a distinct change in the tone of GCK missile design, and may be an indication of future technical approaches. Various configurations of boosters are being tested with this program via the **XSAM-2Aa, XSAM-2Ab,** and **XSAM-2Ac** configurations.

#### XSAM-2B

While development of the XSAM-1 project continued to make progress into 26AF, the large size of the missile raised serious concerns about its potential as a deployable weapon system: decidedly too large and too heavy for readily utilizable road mobile deployment and accordingly not reviewed favorably by the navy, who did not plan in incorporating the design into the next ordering cycle of warships currently on the drawing boards. Seen as only useful from fixed groundbased positions, it was clear that a need existed for a smaller, more portable design.

### Surface to Surface Missiles

Being the GCK's first missile development programs, the *Grecken* and *Grecka* both shared considerable technological exchange over the course of their development of surface to surface missiles. These programs both originated with the XSSM-1 design, itself developed from captured Aerah technologies acquired during the Four Day War in 19AF. Both the army and navy programwere headquartered in Nordburg, Neuu Uthenland, beginning in 20AF (1942), which would in turn grow to encompass testing for all varieties of guided missile projects. Existent technologies established by the Holschiev-Uzervertz design were tested and analyzed with the XSSM-1 project, and adjustments were made given technological and tactical considerations into the operational SSM-2 model by 24AF; the subsequent XSSM-3 project proved technically and logistically challenging as the ultimate extension of the Aerah-derived design school, and has not proven successful.

#### XSSM-1 & XSSM-1B

Originally designed by Holschiev-Uzervertz as a failed competitor for Aerah's *Fliegendebombe* project, prototypes of this design were found in West Aerah during the occupation in 19AF (1941), disassembled, and shipped back to the *greckstatt* for analysis. The original design relied on inertial guidance system, which handicapped the design considerably against moving targets: GCK technicians combined radio direction finding with passive radar detection technologies to implement the *Ekko* guidance system, allowing a missile to home in on radio broadcasts. This invention combined with the acquisition of the Holschiev-Uzervertz design airframe (designated as the **XSSM-1** by the *Grecka)* jumpstarted the GCK's surface-to-surface missile program.

The XSSM-1 and its development the **XSSM-1B** (a more compact, shorter range version with a larger warhead and reduced fuel capacity) were tested between 20 and 22AF (1942-1944) by both the navy (which referred to the type as the **Type 19Bis Ashm**) and army, with both branches conducting testing based out of Nordburg, Neuu Uthenland. Naval testing was conducted aboard the submarine S-39 *Falcata* in the internal waters of the Uthen Sea. Subsequent to these tests the *Allkommand* moved its focus to the indigenous designed SSM-2 in 22AF (1944) as both branches preferred a smaller missile more tailored to the capabilities of the *Ekko* guidance system, and development of the XSSM-1B was terminated in 22AF without operational deployment in lieu of this new design.

#### SSM-2 & ASM-1 "*Arrouu*" families

During testing of the XSSM-1B both the navy and army determined that a smaller missile was preferable to the Aerah derived missile then being tested, as a smaller design would be easier to deploy in the field as well as more effectively scaled in relation to the operating range of the *Ekko* guidance system. Accordingly, these two branches cooperated to develop a shorter range, more compact design utilizing the same basic technologies. The **XSSM-2** (**SSM-2** after being accepted into service in 24AF) featured a folding delta wing and X tail and slung the *Nasr II* pulsejet fully underneath the body, and reduced range to a total burn radius of 60 miles versus the potential 200+miles of the XSSM-1. The type shared a very similar operation profile to its predecessor: like the XSSM-1, it required booster rockets and a catapult for launch, making the type rather large and inefficient to install on naval vessels, but was never-the-less smaller and better designed for sea-based operations. Also like its predecessor, the SSM-2 was tested aboard *SCK Falcata* as the **Type 24 Ashm** in the Uthen Sea between 22-24AF (1944-1946).

##### Development & Introduction of Early Models

The design improved considerably on its predecessor but remained difficult to deploy by sea, particularly when the installation of a single launch ramp would often require the removal of one or more turrets from existing ships large enough to support the type's considerable launch facilities. These variables lead the navy to decline installing the SSM-2 on surface ships in the 24AF naval ordering cycle and instead focusing on development of missile submarines; the army on the other hand began deploying the SSM-2 as a shore defense weapon with mobile batteries replacing the aging Ulysses Ul203 SPGs at the *Forts uff de Nord und Sutt Narrouus* in 24AF, and began appearing in the Central Emihst territories by 25AF. **Type 24 Ashms** also see limited service with the *Grecken*, where the type is formally operational in very small numbers aboard an unknown but small number of converted missile submarines. The *Grecken* would in turn go on to cooperate with the *Greckaf* with testing of an airdropped variant, developing into the ASM-1.

Unarmed developments of the type continued as the **SSM-2B**, included the experimental **SSM-2Ba** & **SSM-2Bb** variants as a target drone for anti aircraft gunnery crews and **SSM-2Bc** as an unmanned reconnaissance platform. Both of these variants had limited success; while the SSM-2Ba & Bb target drones (the Ba returning to the inertial guidance system of the original XSSM-1 designs, while the Bb was remotely controlled) well replicated the attack profile of a jet or rocket weapon, its comparative lack of maneuverability, short flight time & lack of reusability rendered the type unsuitable for long term use, and was relegated essentially only to be used for research of future anti-aircraft technologies until purpose built rocket or jet propelled target drones were introduced. The SSM-2Bc variant suffered from both of these shortcomings, as well as from vibrations from the pulsejet having detrimental effects on the drone's camera systems. As manned aircraft utilizing the *Nasr IV* motorpulsejet used numerous engines in an effort to average out the vibrations, testing of the 2Bc variant was suspended in favor of developments in the XSSM-3.

##### Later Models

By 25AF, while the SSM-2 was only in its second operational year it was already anticipated that the SSM-2 would likely be superseded with the XSSM-4B by the next ordering cycle in 28AF, However noteworthy advancements had been made since the beginning of the SSM-2's testing in 22AF and it was determined that an improved variant of the SSM-2 series should incorporate these improvements as a stopgap until the type could be fully replaced. The **SSM-2D**, also referred to as the *Arrouu II* or *Super Arrouu,* featured redesigned nosecone, wing and tail structures based on wind tunnel testing undertaken for the XASM-3 and XASM-4 projects. To facilitate mounting a pair of *Lean Darby* boosters to the fueselage the wing was raised from a fuselage centerline position to a high shoulder, prompting a replacement of the bomb styled unswept X-tail with a swept inverted V-tail to maintain optimal aerodynamic flow over the control surfaces. Via the two *Lean Darby* boosters, the SSM-2D no longer required a combination of RATO and catapult for launches, and could effectively take off from an a short angled launch ramp. A limited transitional production run introducing these modifications was implemented to mitigate assembly line disruptions, with the **SSM-2Ca** featuring the improved nose and **SSM-2Cb** adding to this the redesigned tail; remaining 2C variants would later be disarmed and converted into radio controlled target drones (designated as the **SSM-2Fa** and **Fb** in parallel to the original Ca and Cb designations) post operational introduction of the standardized 2D variant, which is forecast to operationally succeed the original SSM-2 design by 26AF. The **SSM-2E** designation has been reserved for potential MUSTMUSE systems implementation onto the *Arrouu II* design.

#### XSSM-3, XASM-2 & XAAM-1 family

##### Early development as an anti-shipping missile

While the SSM-2 *"Arrouu"* was selected for use by the army and navy in 24AF as the first GCK cruise missile system to be formally adopted, design work continued on a higher performing design intended for use against hardened and more heavily defended targets; the XSSM-1's & SSM-2s roughly 400mph cruising speed meant that the type could be intercepted by piston engine fighters. Warheadless dummy SSM-2Bs were used in tests at the Nordburg proving grounds in 23AF as fast moving aerial targets by *Grecken* naval assets*,* demonstrating that against prepared military targets only 1 out of every 5 missiles could be expected to successfully damage a target in a supported naval formation; success against smaller and weaker targets or against isolated units was considerably more impressive, but demonstrated the shortcomings of the SSM-2 design. Accordingly, a faster, heavier missile was to be developed specifically with these harder targets in mind, and the XSSM-3 project commenced in 23AF.

The **XSSM-3** was the GCK's first multi-engined cruise missile, originally powered by two *Nasr II* pulse jet engines and allowing projected speeds in excess of 600mph with a 2,000lb warhead. As such, testing began in 24AF. Larger, heavier and more expensive than the SSM-2/Type 24, it could not be effectively operated off of the army's new mobile launchers or the navy's testbed cruise missile submarines; surface based test launches were instead exclusively conducted from a 200ft long fixed land based launch catapult erected at the Nordburg proving grounds. Given these operational restrictions, neither branch expressed interest in fielding the design in spite of its superior performance. Mirroring the test program for the SSM-2/Type 24, airdropped tests of the XSSM-3 derivative the XASM-2 were conducted aboard the airship *Kolonist*, where it was found that the heavier XSSM-3 design had a higher failure rate than the preceding design due to its low launch speed, high stall speed and heavier weight. Subsequent to these tests, the XSSM-3 project required considerable redesign work in order to replace the *Nasr II* pulsejets with the improved *Nasr IV* motorpulsejets, severely cutting into the range of the new reengined **XSSM-3B** system to such a degree that the air fleet elected not to pursue further development as an ASM system. Further development of the XSSM-3B manifested as the **XAAM-1** system, for which a line of sight range was not considered a deficiency;

##### Development as a strategic missile & Cancellation

With early efforts into utilizing the design as an air or land based anti-shipping missile, and later as the GCK's first efforts at an air to air missile, resulted in conclusive failures, the XSSM-3 project was cancelled for the first time from further development in 25AF: the XSSM-3 system was too large to easily deploy from ships or existent mobile launchers in a horizontal launch scheme, and not tactically viable as a permanently emplaced system in the context of its original intended uses. However, the introduction of the *Stout Darby*, *Tall Darby* and *Big Darby* booster rocket systems opened up the potential for vertical launch systems which lead to a last-minute review of the program. Reengining the design with the *Nasr V* ramjet gave the design further performance potential, mirroring the development progress of the subsequent and smaller XSSM-4 system, and subsequentially development was authorized on the **XSSM-3C** system. However, the type's role had changed yet again: no longer being considered as a heavy alternative to the SSM-2, the XSSM-3C, while not formally acknowledged as such, was now being developed under the guise of a strategic deterrence system to deliver chemical warheads against enemy territory.

Testing of the XSSM-3C system was in its infancy when the first of the *Lucifyr* series of ballistic missiles entered testing at Nordburg, and it quickly became evident that the ballistic missiles would have profoundly superior capabilities to a cruise missile against stationary targets in the strategic deterrence model. While the XSSM-3C retained a roughly 100 mile range from its origins as an anti-shipping missile, the 360 mile range of the *Lucifyr I* and 760 mile range of the *Lucifyr II*, combined with the impossibility of reliably intercepting a ballistic missile versus the comparative difficulty of doing so for a cruise missle, put the XSSM-3C program in jeopardy yet again. The SDK advised that the type would only be considered for further development if a range of 1,000 miles could be delivered, as the landbased *Lucifyr II* system could not reach targets in Pteroslavia or Isperia. The final guise of the XSSM-3 design, the **XSSM-3D**, added a quartet of drop tanks above and below the missile's double delta wing, and was projected to have a 500 mile range. Development did not proceed, and the project was finally cancelled in 26AF in tandem with the limited introduction of the SSM-5.

#### XSSM-4 "Club"

Subsequent to the cancellation (albeit briefly as the type resurrected as a strategic deterrence weapon) of the XSSM-3 program in 25AF, it seemed that further development of the GCK's SSM program would require major technological developments in order to offer substantial improvement on the ramp-launched designs previously fielded; with official state policy directing that all turbojet engines be focused on manned interceptor aircraft in order to expedite the development of designs capable of catching up with high flying bombers, missile designers were essentially restricted to the Aerah derived *Nasr II* pulsejet which was profoundly ineffective at altitude, the *Nasr IV* motorpulsejet which solved the altitude issue but remained complicated and inefficient, and the *Nasr V* ramjet system, which could not reach sufficient speeds from existent launch ramps to operate efficiently. Prior to now, all GCK missile designs had been horizontally launched, but starting this year the XSAM-1 began conducting its first vertical launch tests using the newly developed DRB-3 & DRB-4 boosters. This opened up an entirely new avenue of launching options, and it was determined that the XASM-4 design was most suitable for adaptation for vertical launch.

With minor programming modifications made to account for the reorientation from vertical to horizontal flight, an XASM-4Cb design was mounted to a DRB-4 booser with a pair of additional DRB-3 boosters attached to the XASM-4Cb's flanks, resulting in what has been redesignated as the **XSSM-4** system. In tandem with the *Stout Darby Club* vertical launch system, the **XSSM-4B** designation is assigned to development of a horizontally launched variant utilizing the Type 24 mobile launch system developed for the SSM-2 with the shorter XASM-4Aa derived design. While development of the XASM-4 has slowed due to delays in developing a suitable successor to the *Ekko* guidance system, the design's aerodynamics and handling capabilities are well enough established that Nordburg hopes to complete initial testing by year's end and is optimistically conducting preliminary research into mounting the MUSTMUSE system for anti-aircraft purposes the following year.

#### *Lucifyr* Ballistic Missile Family

Under the 7th Budget in 24AF the GCK acquired, under the *Greck*-Osterrecht Technical Cooperation Treaty, import and licensing rights for the (missile name) from Osterrecht as part of a cooperative development program for a new, longer range ballistic cruise missile. When formally revealed in late 25AF, this project was formally organized under the *Daedalus* program designation as a civil research initiative; a polite fiction as the primary purpose of these designs was the delivery of *Nosoi* warheads as part of the duties of the recently reorganized *Strategikdeterrence-Kommand* (SDK) the prior year. Between the 7th and 8th Budgets, this program would result in three distinct ballistic missile platforms that were the foundation of the GCK's ballistic missile deterrence.

##### SSM-5/Type 26 *Lucifyr I* SRBM & SLBMs

Osterrecht built (Osterrecht name for missiles) missiles, designated as the **XSSM-5 *Lucifyr I*** while undergoing military trials at Nordburg and as the **Daedalus I** when used for civilian research purposes and rocket mail projects, began testing later that year. A direct copy of the Osterrecht Rubicon R2 design, the **SSM-5B** soon followed once production lines could be established, and mirrored the imported *Lucifyr I*'s 170 mile operating range and other performance characteristics. By late 25AF the **XSSM-5E/Type 26** **SLBM** variant would be ready for testing aboard a new purpose built experimental submarine, *S-XXX*. Despite design issues with the testbed, major progress was made in the development of submarine launched ballistic missiles: ultimately, the *Grecken's* experience testing sea-based *Lucifyr I* missiles ]guided the development of the smaller size of the *Lucifyr IV**.*** *S-XXX* would be the only GCK submarine to operate carrying the original *Lucifyr I* SLBM design, with the (1950 SSB class) being built to utilize the subsequent *Lucifyr IV*.

Production of the *Lucifyr I* series in military and civil form was minimal, due to assembly lines being shared with the *Lucifyr II* and *Lucifyr III* projects, the latter of which would eventually have production priority. The penultimate development of the *Lucifyr I*, the **XSSM-5G/SSM-7B/Type 28 *Lucifyr IV* SLBM**, replaced the type's fins with Vernier rockets to allow for narrower silo installations aboard submarines, and featured a minor range reduction given fuel used for these purposes that the *Grecken* found acceptable. In this form, the design would be accepted into broader service aboard the (class name) diesel ballistic missile and (class name) nuclear ballistic missile submarines laid down in 28AF. Additionally, un-stabilized finless variants of the *Lucifyr I* design, known as the **SSM-5H**, have been developed as boosters for future launch platforms, typically in association with the **Daedalus** and **Morningstar** programs.

##### XSSM-5C & XSSM-5D *Lucifyr II* SRBM

To help minimize the evident scale of Osterrecht technical contributions from foreign intelligence parties, when indigenously manufactured versions of the of the **XSSM-5C** entered limited production in 25AF alongside the smaller SSM-5B, the designation **XSSM-5D** was applied to make it appear that Osterrecht had in fact only provided the Rubicon R2 per the still secretive treaty. Like the SSM-5B *Lucifyr I*, military production of this type was minimal, particularly as the two designs shared an assembly line given considerable overlap in parts, which ultimately handicapped quantity of production of both types. By the end of 25AF the GCK was focusing its attention on the technical cooperation element of the treaty with the development of a *ballistikkruise* missile system developed from the Rubicon R3, initially designated as the **XSSM-5F** in further efforts at obfuscating the level of cooperation between the two powers. Civilian research of the XSSM-5D type would be conducted under the **Daedalus II** moniker. No further military development of the XSSM-5C or 5D(improved missile design) would be conducted, as the *ballistikkruise* concept of the XSSM-5D was preferred by the army.

##### XSSM-5F/SSM-6 *Lucifyr III* MRBM

The culmination of the *Greck*-Osterrecht Technical Cooperation Treaty, the **SSM-6** combines the respective technical expertise of the Osterrecht ballistic missile program with the GCK's technical expertise towards cruise missiles in the form of a glide-boosted "*ballistikkruise*-missile". With a range of 760 miles, the type dramatically outranges comparable foreign developments, and while not readily suitable for submarine deployment--with the navy instead electing to further develop the smaller, shorter range *Lucifyr I* design in parallel instead--the *Lucifyr III* has been selected as the primary land-based deterrence platform for the *SDK*. Testing of the XSSM-5D (later redesignated as the XSSM-6 when revealed to the public in 25AF) experienced a rapid development process on account of the combined technical expertise of the two parties. As per the terms of the 24AF treaty, the type is expected to be licensed for production to Osterrecht as the Rubicon R4. Civilian utilization of this type would be conducted under the **Daedalus III** designation.

In collaboration with the Nordisle Autonomous Scientific Region, development of a manned reconnaissance variant of the *Lucifyr III* design, codenamed ***Morningstar***, began mid 25AF.

##### XSSM-5G/SSM-7 Lucifyr *IV SRBM*/ Type 28 *Lucifyr IV* SLBM

The cumulative development of the *Lucifyr* ballistic missile series, the **XSSM-5G** (later redesignated as the **SSM-7** in army service and **Type 28 SLBM** in naval use) *Lucifyr IV* is an improved development of the *Lucifyr I* design. Designed with naval deployment in mind, removal of the stabilizing fins was the primary point of technical divergence, as the navy sought to have narrower silos in order to facilitate easier installation aboard its first-generation main production run of ballistic missile submarines, the (class name) of 28AF. In order to facilitate this, a replacement stabilization method was required: this was facilitated through the dual introduction of stabilizing thrusters and folding trellised aerodynamic surfaces in order to facilitate its more compact design. Furthermore, the *Lucifyr IV* combined technical developments from after the *Lucifyr I* design with the improved engine of the *Lucifyr II* and *Lucifyr III* designs, resulting in a change of thrust from 267KN to 363KN and accordingly improved performance.

### Air to Surface Missiles

Air to surface guided missiles grew out of a logical extension of unguided rocket projects and tentative exploration of glide bomb technologies. Predominantly, these projects were overseen by the *Greckaf*, with the *Grecken's* naval aviation interests in time growing to collaborate with their rival branch. At present, the airfleet's operational air to surface guided missile capabilities are limited to a special testing unit, comprised of a total of four aircraft and an airship, capable of deploying the formally operational ASM-1 *Arrouu* design, with pre-production work continuing on the successive ASM-3 *Slingshot* and ASM-4 *Club* designs*,* which are operational presently only in drone form while awaiting decisions regarding guidance technologies.

#### ASM-1 *"Arrouu"*

The *Greckaf* lacked a large enough conventional bomber for aerial deployment of guided missiles, and furthermore did little pursue their development until the operational introduction of the SSM-2 in 24AF. A modified variant, known as the **XASM-1** in *Greckaf* trials, was tested for aerial deployment aboard the airship *Kolonist* beginning in 22AF (1944). The ASM-1 varied from the groundbased variant in that it featured a short timer for activation of its rocket-boosters to allow time for the missile to put distance between it and its launch-ship, before accelerating and activating its pulse-jet. Testing aboard *Kolonist* revealed that the success of air launches was highly influenced by weather given the relatively high stall speed of the ASM-1's delta wing, but engineers remained optimistic that with higher launch speeds this issue could be rectified.

Aerial launch testing was moved to a pair of specially converted motherships, dubbed *Castor* and *Pollux,* beginning in 24AF. These seven-engine aircraft were each conjoined out of a pair of obsolete (INSERT AIRCRAFT NAME HERE) heavy bombers, and were capable of carrying up to three of the XASM-1 missiles at a time; while their low speed and altitude capabilities made the *Greckaf* consider the type as a stopgap measure at best, they would function as testbeds for several subsequent air launch missile platforms. While the XASM-1 successfully passed testing when conducted from the *Castor* and *Pollux* motherships and has been formally accepted for operational service as the **ASM-1**, the *Greckaf* presently lacks a suitable operational launch platform for the design, and it has yet to be operationally fielded beyond the test squadron based out of Nordisle, making the type's operational status symbolic at best. Subsequent to testing of the succeeding XASM-3 and XASM-4 designs, development of the ASM-1 was suspended in favor of these more promising designs.

Mirroring the SSM-2 program, unarmed drone variants of the ASM-1 were produced in limited numbers, with the **ASM-1Ba** and **ASM-1Bb** being used both for target practice by anti-aircraft crews as well as operational launch exercises for future missile bomber crews. No parallel of the SSM-2Bc were built, given failures in land based testing of the type.

#### XASM-2

Developed off of the failed XSSM-3 project, the **XASM-2** shared the same strengths and weaknesses of its progenitor: very high speed and heavy payload, but decided difficulty in effective operations due to its size, weight and stall speed. Aerial tests from *Kolonist* were unsuccessful due to the slow launch speed of the zeppelin, as the type's pulsejet engines did not perform well at the mothership's comparably low launch speed, and its larger size prevented rapid acceleration with existent RATO packs. *Castor* and *Pollux* were unable to sling the larger missile while clearing the type's landing gear, resulting in the modification of a (four engine transport) for use as a mothership. While more successful than the failed *Kolonist* test launches, the logistics of this arrangement were substantially disadvantageous. Consideration was made for replacing the *Nasr II* pulsejets with a *Nasr IV* motorpulsejet arrangement in order to bypass the speed and size challenges with launching the design, and indeed this development path was pursued for the XAAM-1, but this option was not selected for the air to surface project given profound range reduction.

Subsequent to this, development focus turned to the **XASM-2B**, powered by the experimental *Nasr V* ramjet system. Aerial testing of the *Nasr V* powered XASM-2B continues as of March 1947, and wind tunnel mockups of the **XASM-2Ca** and **2Cb** designs are presently being tested with aerodynamic improvements to the tail and wing structure. However, *Allkommand* reviews of the project were not favorable on account of its profound size and difficulty to deliver to the combat area given the same; with the smaller and more affordable XASM-4 project delivering a guided missile at least half again faster than the ASM-1 project, further development of the XASM-2 project was suspended by 25AF.

#### ASM-3 "Slingshot"

When the performance and capabilities of the SSM-2/ASM-1 *Arrouu* system were being explored via testing in 22AF, air fleet trials showed that while the type met technical requirements sufficiently its large size rendered the type logistically challenging to deploy; while modified (7 engine testbed) aircraft could effectively deploy multiple examples of the type at a time, the missile's large size substantially handicapped its implementation as only proposed conversions of strategic bombers could deliver a single missile to a combat area, and even then would conceptually require support for targeting purposes. In 23AF, a joint navy-airfleet requirement was issued which called for the minimum size of air to surface missile capable of operating at ranges outside of anti-aircraft range. This requirement resulted in the **XASM-3** and XASM-4 designs, utilizing the *Nasr II* pulsejet and *Nasr V* ramjet respectively.

In stark contrast to the dramatically more technically ambitious XASM-2 project, the XASM-3 system did not seek to exceed the performance capabilities of its predecessor, and rather sought to deliver something closer to the ASM-1's performance in a more readily deployable manner. The design sacrificed range and warhead size for a considerably smaller weapon, with roughly half the capability of the ASM-1 in terms of range and payload. A prototype of the design began testing the following year and was reviewed favorably on account of its general utility in contrast to the ASM-1 system, with the **ASM-3Ba** and **3Bb** drone variants being ordered into production before the XASM-3's original missile variant reaching approval under the name "Slingshot." The original armed **XASM-3Aa** remains in development with interest towards other options for guidance in lieu of the large *Ekko* system. A variant using a DRB-3 solid fuel booster as its propulsion system, designated the **XASM-3C**, was used for research into solid propellant systems, as all previous GCK missile projects had utilized either pulse jets or ramjets.

#### ASM-4, XSAM-3 & XSSM-4 "Club" family

Originating from the same joint airfleet-navy requirement for a minimal stand-off guided weapon issued in 23AF, the **XASM-4** utilized the newer advanced *Nasr V* ramjet for its propulsion system, and was the first GCK missile design purpose built with a ramjet. While previously utilized in the XASM-2 project, the more conservative expectations of the XASM-4 combined with the highly potent ramjet propulsion system produced a design comparable in size to the ASM-1 *Arrouu* while sharing the high speed--if not to the same extent--of the complex and unweildy XASM-2. Inversely, the downside of the design meant that it was impractical for the powerplant to operate when launched from catapult, as much higher speeds were required before it could operate efficiently, which initially prevented its development into an effective surface launched weapon. Nevertheless, the XASM-4 entered testing the subsequent year and proceeded quickly, as it relied on essentially the same level of technological capability as the earlier ASM-1 system.

While the earlier ASM-1 design would formally be accepted into service in 24AF while the XASM-4 was entering development, production of the ASM-1 would be very limited due to highly restricted launch options, namely being a pair of converted motherships or an airship. Accordingly, the XASM-4 design's development has been viewed very competitively as a logical successor to the ASM-1 project, with limited production of the type underway as the **XASM-4Aa** with an *Ekko* guidance system and **ASM-4B** as a remote controlled target drone, receiving the moniker "*Club*" for its portly body. The **XASM-4Ca** and **4Cb** variants feature an extended fuselage for heavier warheads or potentially other guidance system arrangements; further development of this type is underway as the XSSM-4 design.

### Air to Air Missiles

Air to air missiles, along with surface to air missiles, lagged behind surface to surface missiles in the GCK's research efforts. While the novel technology's technical challenges were not fully nor immediately resolved with regards to SSMs, the range benefits of being able to strike targets at ranges otherwise restricted to naval aviation (of which the GCK had been long handicapped by small aircraft carriers) spurred testing and development programs which the army imitated once rendered feasible. In terms of aerial combat, the air fleet did not find there to be a pressing unresolved need that merited these programs until 23AF, when long range, high altitude reconnaissance flights by Karadwynn began to be detected over the GCK's Central Emihst territories, spurring a spree of R&D projects by the airfleet to help shore up a perceived deficiency in *greck* air defenses.

#### XAAM-1

While the primary outcome of these efforts was the limited introduction of the *Nasr IV* propelled *Houuler* interceptor in late 24AF, the air fleet simultaneously conducted studies on utilizing ASM systems presently under development as an anti-aircraft weapon; however the *Nasr II* pulsejet engine profoundly failed to provide perquisite performance at medium and high altitudes. Attention turned to an air to air development of the aborted XSSM-3B project, with the double *Nasr IV* powered **XAAM-1** entering testing at the same time as the first *Houuler* interceptors entered service.

Towed behind a modified He-3 bomber medium bomber and guided via the newly developed *Marxman* beam riding system, the XAAM-1 would undergo limited testing, quickly being rejected in 24AF for numerous reasons, including but not limited to the difficulty of landing the missile as a glider if not fired in combat, let alone the type's very large size and rushed conversion from an already troubled original design. While unsuccessful, the *Marxman* system pioneered with the XAAM-1 would persist into its successor design. Proposals for a *Nasr V* ramjet propelled variant paralleling the XASM-2 development chain were not pursued due to the complex and inefficient towed launch system.

#### XAAM-2

Subsequent to the cancellation of the stillborn XAAM-1 project, attention was turned to a less rushed and more logistically feasible design based off of the DRB-3 "Lean Darby" solid fueled booster that had been introduced that year and was seeing utilization with the XSAM-1, XSAM-2 and XSSM-4 surface launched missile projects: utilizing this propulsion system permitted a considerably smaller design than competing efforts based off of the *Nasr* jet series. Combined with the *Marxman* beam riding system pioneered on the previous XAAM-1 project, this permitted the development of a succeeding design that was much smaller than its ill-conceived predecessor, and testing of the **XAAM-2** would begin in 25AF. The 1,750lb DRB-3 booster has a very short burn time, but produced an incredible 33,000 lbf during its five point three seconds of operation, well capable of pushing the XAAM-2 into supersonic speeds during its attack run.

While its very short range of over a mile is sufficient to keep the launching aircraft out of range of enemy aircraft's defensive weaponry, and its quarter ton warhead is enough to have an large aerial blast effect radius, the type has limited air-to-air applications beyond use against bombers. Their large size precluded more than a pair of the devices being carried on most interceptors: doctrinally, the interceptor would be expected to soften up formations with XAAM-2s, then finish off crippled targets with its guns. Further testing is expected for the XAAM-2 as an anti-surface weapon, although no known XASM designation has been offered for the design.

## Civil Rocket Programs

Civil research rocketry programs within the GCK existed in very limited form prior to the jumpstarting of the GCK's military rocket and missile programs in 19AF predominantly due to lack of commercial or industrial applications of the technology; the military did not consider the technology an improvement on existent artillery and anti-aircraft equipment, and beyond amateur hobbyist-enthusiasts there was little impetus for funding further projects. Some civil research had made its way into state awareness in the 10sAF via the introduction of rocket assisted take off or RATO technologies, which was also explored with regards to civil aviation with limited success.

With the establishment in 20AF of military cruise missile programs at Nordburg, a substantial amount of whatever private rocketry research that had previously existed within the GCK was quickly drawn into these given the substantial funding offered there. These military programs differed from overseas initiatives in nations such as Aerah and Osterrecht, as the *Allkommand* placed considerably more interest in tactical missile systems than strategic ones; accordingly, there was a comparatively minimal interest in inertial guidance systems due to their comparative inaccuracy and instead focused exclusively on homing or guidance technologies, thus limiting the range of 1st generation GCK tactical missiles to at most 50 or 60 miles. However, with Aerah and Osterrecht both making progress with inertially guided ballistic missiles over the course of the 20sAF, strategic missiles as deterrence weapons--armed with chemical weapons--became conceptually feasible, if not officially sanctionable by merit of the *greckstatt's* political dogmas: while the GCK had discretely deployed chemical weapons developed by the labour army's *Spezchemgruppe-Nosoi* along the Evonland border as early as 4AF, these weapons were not formally acknowledged by the GCK, nor was the chemical deterrence doctrine publicly discussed. *Allkommand* strategists found the concept worth pursuing, as potentially ballistic missiles could not only extend the range of the chemical weapons installed along the *Greck*-Evon frontier, but additionally extend the chemical deterrence capability across the Gulf of Laurent to Pteroslavia.

Based predominantly on these considerations, in 24AF the rocketry research institute at Nordburg formed a decidedly discrete ballistic missile research and development bureau. Simultaneous to this, discrete political overtures were commenced with the government of Osterrecht over the potential of licensing or otherwise cooperating on development of a similar technical system. The Nordburg BMRD program ultimately bifurcated into two starting projects, codenames **Daedalus** and **Ikarus**; Daedalus would comprise of any foreign derived technical efforts, while Ikarus in turn was a wholly indigenous development project.

Long range rocketry however could be publically explored through non-military applications, and per the GCK's 25th anniversary a considerable political emphasis was created in support of the *Greck-Technikuuonderprograms.* Among the goals laid out in these programs was the development of highspeed international rocketmail, which politically allowed the GCK to announce its own ballistic rocket development program that year during the anniversary celebrations.

### Daedalus Program

#### Daedalus I

(civilian Lucifyr I for sounding rocket research)

#### Daedalus II

(civilian Lucifyr II for rocket mail project)

#### Daedalus III

(Daedalus II+Ikarus II/III design elements re ramrockets/ramjets?)

### Ikarus Program

#### Ikarus I

(Darby series derived sounding rocket, primitive. Likely replaced by Daedalus program)

#### Ikarus II

(testbed for Ikarus III technologies at smaller scale)