Editing DropShip
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision
Your text
Line 1:
Line 1: − [[File:Union cutaway color TM.png|right|300px|thumb|''Union''-class DropShip cutaway]] + [[File:Union cutaway color TM.png|right|300px|thumb|''Union''-class DropShip cut-away ]] A '''DropShip''' is defined as a type of spaceship massing between 200 and 100,000 tons that is itself incapable of faster-than-light (FTL) travel. They essentially conduct all other aspects of space travel, including transit between planets and [[jump point]]s and planetary landings. For FTL interstellar movement, they dock with [[JumpShip]]s by means of a [[docking collar]]. A '''DropShip''' is defined as a type of spaceship massing between 200 and 100,000 tons that is itself incapable of faster-than-light (FTL) travel. They essentially conduct all other aspects of space travel, including transit between planets and [[jump point]]s and planetary landings. For FTL interstellar movement, they dock with [[JumpShip]]s by means of a [[docking collar]]. Line 5:
Line 5: DropShips are the workhorse of interplanetary space travel. It is the DropShips (and occasionally their smaller cousins, the [[Small Craft]]) that move cargo and passengers between planetary surfaces, orbits, space stations and jump points. While transport is their primary role, some have been built for special purposes and act as tugs, rescue ships, fighter carriers or even designated combat DropShips. Accordingly, a wide and diverse variety of DropShip types exist. DropShips are the workhorse of interplanetary space travel. It is the DropShips (and occasionally their smaller cousins, the [[Small Craft]]) that move cargo and passengers between planetary surfaces, orbits, space stations and jump points. While transport is their primary role, some have been built for special purposes and act as tugs, rescue ships, fighter carriers or even designated combat DropShips. Accordingly, a wide and diverse variety of DropShip types exist. − Even though many DropShips serve as military spaceships, naval terms such as "Corvette": "Destroyer": "Cruiser" etc. are never applied to them; these are exclusively used for true [[WarShip]]s, i.e. the huge Combat JumpShips that outclass DropShips by an order of magnitude (typically massing several hundred thousand or even millions of tons). + Even though many DropShips serve as military spaceships, naval terms such as "Corvette", "Destroyer", "Cruiser" etc. are never applied to them; these are exclusively used for true [[WarShip]]s, i.e. the huge Combat JumpShips that outclass DropShips by an order of magnitude (typically massing several hundred thousands or even millions of tons). ==History== ==History== − The term "DropShip" was first used in the [[twenty-second century]] to describe the cargo-carrying shuttles then in use to ferry cargo and passengers between the JumpShips of that era. It was not until the [[twenty-fifth century]] when "DropShip" became the official designation for a type of ship more sophisticated than the earlier [[DropShuttle|shuttles]]. Instead of being carried within the hull of a JumpShip, these vessels were now attached on the outside and would "drop" away once it had arrived. By the [[thirty-first century]], there were over 250 DropShip designs on record, though only approximately 100 were still in service, with twenty of those constituting the majority of DropShips in existence.<ref name=BSS20>''BattleSpace'' rulebook, pp. 18–20</ref><ref name=DJOM8>''DropShips and JumpShips - Operations Manual'', pp. 4–8</ref><ref name=AT69>''AeroTech 2'', pp. 66–69</ref> + The term "DropShip" was first used in the [[22nd century]] to describe the cargo-carrying shuttles then in use to ferry cargo and passengers between the JumpShips of that era. It was not until the [[25th century]] when "DropShip" became the official designation for a type of ship more sophisticated than the earlier [[DropShuttle|shuttles]]. Instead of being carried within the hull of a JumpShip, these vessels were now attached on the outside and would "drop" away once it had arrived. By the [[31st century]], there were over 250 DropShip designs on record, though only approximately 100 were still in service, with twenty of those constituting the majority of DropShips in existence.<ref name=BSS20>''BattleSpace - Sourcebook'', p. 18-20</ref><ref name=DJOM8>''DropShips and JumpShips - Operations Manual'', p. 4-8</ref><ref name=AT69>''AeroTech 2'', p. 66-69</ref> ==Construction== ==Construction== − While DropShips come in a variety of shapes and sizes, the heart of every DropShip is its engineering section, which is comprised of two systems: a power plant and an [[Interplanetary Drive - DropShips| + While DropShips come in a variety of shapes and sizes, the heart of every DropShip is its engineering section, which is comprised of two systems: a power plant and an [[Interplanetary Drive - Dropships| engine]]. The fusion engine works by expelling plasma through shielded exhaust nozzles to create thrust. All DropShips have a main exhaust nozzle to propel the ship forward at a steady acceleration. The most advanced also have numerous plasma exhaust nozzles dotting their hulls to control steering, but such devices are fragile and expensive, leaving many DropShips equipped with hardier but less efficient chemical rockets to fulfill this role. The plasma exhaust is created as a by-product of nuclear fusion and requires a constant supply of fuel in the form of liquid H<sub>2</sub>, which is carried aboard in large storage tanks and fed to the drive by one of two systems. The one found on all DropShips is a heat-expansion system where the H<sub>2</sub> is fed into a heated chamber; here the high temperature causes it to expand, with the resulting pressure forcing it into the engine core. Military DropShips will also have a series of high-speed pumps which can supply a constant stream of fuel for the engine, allowing for rapid changes in thrust. Unlike the engine core, the fusion plant which provides power for the DropShip is a closed system, reprocessing its own by-products and requiring little additional fuel. It can however tap into the same H<sub>2</sub> storage tanks used by the engines when needed.<ref name=BSS20/><ref name=DJOM8/><ref name=AT69/> engine]]. The fusion engine works by expelling plasma through shielded exhaust nozzles to create thrust. All DropShips have a main exhaust nozzle to propel the ship forward at a steady acceleration. The most advanced also have numerous plasma exhaust nozzles dotting their hulls to control steering, but such devices are fragile and expensive, leaving many DropShips equipped with hardier but less efficient chemical rockets to fulfill this role. The plasma exhaust is created as a by-product of nuclear fusion and requires a constant supply of fuel in the form of liquid H<sub>2</sub>, which is carried aboard in large storage tanks and fed to the drive by one of two systems. The one found on all DropShips is a heat-expansion system where the H<sub>2</sub> is fed into a heated chamber; here the high temperature causes it to expand, with the resulting pressure forcing it into the engine core. Military DropShips will also have a series of high-speed pumps which can supply a constant stream of fuel for the engine, allowing for rapid changes in thrust. Unlike the engine core, the fusion plant which provides power for the DropShip is a closed system, reprocessing its own by-products and requiring little additional fuel. It can however tap into the same H<sub>2</sub> storage tanks used by the engines when needed.<ref name=BSS20/><ref name=DJOM8/><ref name=AT69/> Line 21:
Line 21: ===DropShip Category=== ===DropShip Category=== − DropShips are based around two basic hull forms, aerodyne and spheroid. Depending on their intended role, DropShips can be constructed following either of these two alternative approaches. + DropShips are based around two basic hullforms, aerodyne and spheroid. Depending on their intended role, DropShips can be constructed following either of these two alternative approaches. − Although all DropShips are either of the spheroid or the aerodyne subtype, there is arguably a third one: ships which are limited to operating in deep space for one reason or another and would be destroyed when attempting to enter an atmosphere or land on a planet, rendering the differences between aerodyne and spheroid designs irrelevant to them. Examples include the superlarge ''[[Behemoth (DropShip class)|Behemoth]]'' class cargo hauler, which is a spheroid design but has insufficient acceleration for planetary operations and is too large and fragile to operate in gravity, and the nominally aerodyne ''[[Achilles (DropShip class)|Achilles]]'' and ''[[Vengeance (DropShip class)|Vengeance]]''-class military DropShips which were never designed for atmospheric operations. + Although all DropShips are either of the spheroid or the aerodyne subtype, there is arguably a third one: ships which are limited to operating in deep space for one reason or another and would be destroyed when attempting to enter an atmosphere or land on a planet, rendering the differences between aerodyne and spheroid designs irrelevant to them. Examples include the superlarge ''[[Behemoth (DropShip)|Behemoth]]'' class cargo hauler, which is a spheroid design but has insufficient acceleration for planetary operations and is too large and fragile to operate in gravity, and the nominally aerodyne ''[[Achilles (DropShip)|Achilles]]'' and ''[[Vengeance]]'' class military DropShips which were never designed for atmospheric operations. ====Aerodyne DropShips==== ====Aerodyne DropShips==== − Aerodyne DropShips are shaped roughly similar to conventional aircraft, using their aerodynamic hull shape to generate lift within an atmosphere. This makes these DropShips ideally suited for atmospheric operations, at the expense of being more expensive and harder to produce than spheroid ships and with more restrictive size requirements. Many aerodynes also require runways to land and take off, limiting where they can operate. To facilitate atmospheric and deep space travel, most aerodynes are equipped with two sets of exhaust nozzles, one on the bottom and one on the rear. Aerodynes will use their bottom thrusters and transit drive during space operations, then switch over to after thrusters and maneuver drive when in an atmosphere. While taking up additional space, this alleviates the issue of internal orientation by allowing the vessel's nose and rear to remain "forward" and "aft" at all times.<ref name=BSS20/><ref name=DJOM8/><ref name=AT69/> + Aerodyne DropShips are shaped roughly similar to conventional aircraft, using their aerodynamic hull shape to generate lift within an atmosphere. This makes these DropShips ideally suited for atmospheric operations, at the expense of being more expensive and harder to produce than sphereoid ships and with more restrictive size requirements. Many aerodynes also require runways to land and take off, limiting where they can operate. To facilitate atmospheric and deep space travel, most aerodynes are equipped with two sets of exhaust nozzles, one on the bottom and one on the rear. Aerodynes will use their bottom thrusters and transit drive during space operations, then switch over to after thrusters and maneuver drive when in an atmosphere. While taking up additional space, this alleviates the issue of internal orientation by allowing the vessel's nose and rear to remain "forward" and "aft" at all times.<ref name=BSS20/><ref name=DJOM8/><ref name=AT69/> ====Spheroid DropShips==== ====Spheroid DropShips==== − Spheroid DropShips are so named for their rounded hulls, making them easier and cheaper to construct. Their simple design also makes them sturdier and allows them to be built much larger than aerodyne DropShips, with the largest spheroid outmassing the largest aerodyne many times over. Spheroid DropShips have a single engine drive positioned on the ship's bottom which is used to vertically descend onto a planetary surface and take off in the same way. This allows spheroid DropShips to operate independent from runways or even spaceports, making them ideal for exploring unknown planets and giving them a tactical advantage in military operations. However, their simple and versatile landing and takeoff pattern requires more fuel and can cause significant damage to the ground. They also cannot travel through the atmosphere as quickly as aerodyne vessels and their method of flight is more unstable, making them less practical for atmospheric combat. A complex system of thrusters positioned around the hull and controlled by the main computer helps make atmospheric flight and landing possible, but if these systems are damaged a spheroid DropShip can easily lose control and crash.<ref name=BSS20/><ref name=DJOM8/><ref>''DropShips and JumpShips - Operations Manual'', pp. 20–22</ref><ref name=AT69/><ref>''AeroTech 2'', pp. 11, 37</ref> + Spheroid DropShips are so named for their rounded hulls, making them easier and cheaper to construct. Their simple design also makes them more sturdy and allows them to be built much larger than aerodyne DropShips, with the largest spheroid outmassing the largest aerodyne many times over. Spheroid DropShips have a single engine drive positioned on the ship's bottom which is used to vertically descend onto a planetary surface and take off in the same way. This allows spheroid DropShips to operate independent from runways or even spaceports, making them ideal for exploring unknown planets and giving them a tactical advantage in military operations. However, their simple and versatile landing and takeoff pattern requires more fuel and can cause significant damage to the ground. They also cannot travel through the atmosphere as quickly as aerodyne vessels and their method of flight is more unstable, making them less practical for atmospheric combat. A complex system of thrusters positioned around the hull and controlled by the main computer helps make atmospheric flight and landing possible, but if these systems are damaged a spheriod DropShip can easily lose control and crash.<ref name=BSS20/><ref name=DJOM8/><ref>''DropShips and JumpShips - Operations Manual'', p. 20-22</ref><ref name=AT69/><ref>''AeroTech 2'', p. 11, 37</ref> ===Classification of DropShips=== ===Classification of DropShips=== Line 35:
Line 35: * Assault - This primarily military DropShip is designed for maximum firepower. Typically used for anti-[[aerospace fighter]] and anti-DropShip operations, they can be used for ground assault purposes, though this is rare. Some models of assault ships carry anti-WarShip weaponry and are referred to as Pocket WarShips; this type of DropShip is also known to carry limited quantities of [[BattleMech|BattleMechs]], [[battle armor]], marines, and aerospace fighters, usually just enough to provide "point-blank" defense. * Assault - This primarily military DropShip is designed for maximum firepower. Typically used for anti-[[aerospace fighter]] and anti-DropShip operations, they can be used for ground assault purposes, though this is rare. Some models of assault ships carry anti-WarShip weaponry and are referred to as Pocket WarShips; this type of DropShip is also known to carry limited quantities of [[BattleMech|BattleMechs]], [[battle armor]], marines, and aerospace fighters, usually just enough to provide "point-blank" defense. − **<span id="Pocket WarShip">Pocket WarShip</span> - A military DropShip type based on the assault DropShips. These ships are designed to carry [[Capital Missile|Capital Missiles]] and sometimes [[:Category:Sub-Capital Weapons|Sub-Capital Weaponry]]. Most are typically heavily armed with standard BattleMech-scale weaponry. Early versions of this ship type were known as '''Q-Ships'''. Following the [[Jihad]], with so many nations' shipyards damaged or destroyed, many factions turned to these as the backbone of their navies. + ** <span id="Pocket WarShip">Pocket WarShip</span> - A military DropShip type based on the Assault DropShips. These ships are designed to carry [[Capital Missile|Capital Missiles]] and sometimes [[:Category:Sub-Capital Weapons|Sub-Capital Weaponry]]. Most are typically heavily armed with standard BattleMech-scale weaponry. Early versions of this ship type were known as '''Q-Ships'''. Following the [[Jihad]], with so many nations' shipyards damaged or destroyed, many factions turned to these as the backbone of their navies. * Fighter Carrier or Aerospace Carrier - Designed for carrying/supporting aerospace fighter craft operations. Though other DropShips are referred to as 'Mech carriers, troop carriers, etc., a ship described as a "carrier" is understood to be a fighter carrier. These ships typically have '''CV''' (for '''C'''arrier '''V'''essel) appended to their name, as in ''[[Leopard CV]]''. * Fighter Carrier or Aerospace Carrier - Designed for carrying/supporting aerospace fighter craft operations. Though other DropShips are referred to as 'Mech carriers, troop carriers, etc., a ship described as a "carrier" is understood to be a fighter carrier. These ships typically have '''CV''' (for '''C'''arrier '''V'''essel) appended to their name, as in ''[[Leopard CV]]''. *Cargo Ship - Typically civilian model of ship, used for hauling bulk cargo. Some ships are fitted to transport liquids and are usually referred to as Liquid Carriers. *Cargo Ship - Typically civilian model of ship, used for hauling bulk cargo. Some ships are fitted to transport liquids and are usually referred to as Liquid Carriers. Line 46:
Line 46: ==DropShip Operations== ==DropShip Operations== − Once a DropShip has arrived at a system's jump point and detached from its JumpShip, it can begin the long journey to its destination point within the system. This depends on the star system in question, where the DropShip is trying to travel to, and how fast the ship accelerates during the course of its journey. Thanks to their powerful fusion engines and fuel reserves, DropShips can travel interplanetary distances by constantly accelerating towards their destination then, at the midway point, flipping around and using their engines to decelerate at the same rate. Assuming the distance between the start and end point are known, this can be calculated with T = 2√(D/A), where T equals time in hours, D is distance in kilometers from the starting point to midway point, and A is acceleration in kilometers per hour per hour. In most cases it would take several days or more for a DropShip to travel between a jump point and a planet in-system. During this time the DropShip will be burning fuel to maintain its constant acceleration and deceleration and any maneuvering it must undertake. The most common way of expressing this is by burn-day, which is the amount of fuel burned by accelerating at 1 G for one day.<ref>''BattleSpace'' rulebook, p. 52</ref> + Once a DropShip has arrived at a system's jump point and detached from its JumpShip, it can begin the long journey to its destination point within the system. This depends on the star system in question, where the DropShip is trying to travel to, and how fast the ship accelerates during the course of its journey. Thanks to their powerful fusion engines and fuel reserves, DropShips can travel interplanetary distances by constanting accelerating towards their destination then, at the midway point, flipping around and using their engines to decelerate at the same rate. Assuming the distance between the start and end point are known, this can be calculated with T = 2√(D/A), where T equals time in hours, D is distance in kilometers from the starting point to midway point, and A is acceleration in kilometers per hour per hour. In most cases it would take several days or more for a DropShip to travel between a jump point and a planet in-system. During this time the DropShip will be burning fuel to maintain its constant acceleration and deceleration and any maneuvering it must undertake. The most common way of expressing this is by burn-day, which is the amount of fuel burned by accelerating at 1 G for one day.<ref>''BattleSpace - Rulebook'', p. 52</ref> − When landing or lifting off from a planet, DropShips can do so vertically if spheroid or horizontally if aerodyne; aerodynes may also land horizontally if the planet lacks an atmosphere. Vertical landings and takeoffs are more versatile as they require only as much space as to fit the DropShip, but are more difficult as a DropShip at low velocity is more unstable, burns more fuel and causes ground damage. Horizontal landings and takeoffs require a runway of at least 600 meters, though experience pilots can land on shorter stretches using their bottom thrusters. Once grounded, cargo is typically offloaded or loaded by DropShip crew members, usually wearing [[Exoskeleton]]s to make the job go quicker, though some military units will use their 'Mechs to help speed up the process.<ref>''BattleSpace'' rulebook, pp. 53–57</ref> + When landing or lifting off from a planet, DropShips can do so vertically if sphereoid or horizontally if aerodyne; aerodynes may also land horizontally if the planet lacks an atmosphere. Verticle landings and takeoffs are more versatile as they require only as much space as to fit the DropShip, but are more difficult as a DropShip at low velocity is more unstable, burns more fuel and causes ground damage. Horizontal landings and takeoffs require a runway of at least 600 meters, though experience pilots can land on shorter stretches using their bottom thrusters. Once grounded, cargo is typically offloaded or loaded by DropShip crew members, usually wearing [[Exoskeleton]]s to make the job go quicker, though some military units will use their 'Mechs to help speed up the process.<ref>''BattleSpace - Rulebook'', p. 53-57</ref> − During combat operations, military DropShips that land to disembark their cargo will typically do so well away from the front lines as a means of preserving them, both for their incredible expense and for their ability to withdraw troops from a losing engagement. In instances where troops must be landed closer to an enemy force, or where a DropShip cannot land due to hazardous terrain, it may instead carry out a '''Combat Drop'''. In a combat drop, BattleMechs and [[battle armor]]ed troopers will exit the DropShip while at high altitude or in orbit. These units use their integral [[jump jets]] or disposable jet packs to control their descent and safely land, but even among well-trained forces a combat drop is a hazardous endeavor. For orbital combat drops, a special [[Drop Cocoon]] is used which protects the unit during atmospheric reentry then falls away.<ref>''JumpShips and DropShips'', pp. 42–43</ref><ref>''BattleSpace'' rulebook, p. 37</ref> A variation on this tactic is known as the [[Hover-Drop Maneuver]]. + During combat operations, military DropShips that land to disembark their cargo will typically do so well away from the front lines as a means of preserving them, both for their incredible expense and for their ability to withdraw troops from a losing engagement. In instances where troops must be landed closer to an enemy force, or where a DropShip cannot land due to hazardous terrain, it may instead carry out a '''Combat Drop'''. In a combat drop, BattleMechs and [[battle armor]]ed troopers will exit the DropShip while at high altitude or in orbit. These units use their integral [[jump jets]] or disposable jet packs to control their descent and safely land, but even among well-trained forces a combat drop is a hazardous endeavor. For orbital combat drops, a special [[Drop Cocoon]] is used which protects the unit during atmospheric reentry then falls away.<ref>''JumpShips and DropShips'', p. 42-43</ref><ref>''BattleSpace - Rulebook'', p. 37</ref> A variation on this tactic is known as the [[Hover-Drop Maneuver]]. − Maintaining a DropShip is a constant endeavor, not least because many will be decades if not centuries old. Reducing wear and tear by avoiding atmospheric operations or active maneuvering can help, but nothing short of mothballing it will help preserve a DropShip that doesn't have a well-trained crew to look after it. Even for the smaller DropShips, the weekly maintenance needed to keep the vessel running can cost hundreds of [[C-bill]]s, never mind repairing and replacing components or armor due to battle damage. Having a well-oiled crew is also important for a DropShip, though on most civilian vessels only the senior crew will sign on with a permanent contract, with the rest signing on for a limited time span. For security reasons, a military DropShip's crew will all be permanent members who have gone through extensive screening. Crew wages vary by vessel and era, but in the middle of the thirty-first century the average DropShip pilot earned 550 C-bills a month at minimum, while an engineer earned 450 C-bills.<ref>''BattleSpace'' rulebook, pp. 57–62</ref> + Maintaining a DropShip is a constant endeavor, not least because many will be decades if not centuries old. Reducing wear and tear by avoiding atmospheric operations or active maneuvering can help, but nothing short of mothballing it will help preserve a DropShip that doesn't have a well-trained crew to look after it. Even for the smaller DropShips, the weekly maintenance needed to keep the vessel running can cost hundreds of [[C-bill]]s, nevermind repairing and replacing components or armor due to battle damage. Having a well-oiled crew is also important for a DropShip, though on most civilian vessels only the senior crew will sign on with a permanent contract, with the rest signing on for a limited time span. For security reasons, a military DropShip's crew will all be permanent members who have gone through extensive screening. Crew wages vary by vessel and era, but in the middle of the 31st century the average DropShip pilot earned 550 C-bills a month at minimum, while an engineer earned 450 C-bills.<ref>''BattleSpace - Rulebook'', p. 57-62</ref> ==Manufacturing== ==Manufacturing== − The smallest known spaceship to meet the DropShip criteria is arguably the 200-ton [[K-1|K-1 DropShuttle]], although it is generally classified as a [[Small Craft]] instead. The largest DropShip ever constructed is the 100,000-ton ''[[Behemoth (DropShip_class)|Behemoth]]'', which due to its sheer size is incapable of entering gravity wells stronger than 0.6 g. The biggest DropShip that can actually enter the atmosphere in standard gravity is the 52,000-ton ''[[Mammoth]]''. + The smallest known spaceship to meet the DropShip criteria is arguably the 200-ton [[K-1|K-1 DropShuttle]], although it is generally classified as a [[Small Craft]] instead. The largest DropShip ever constructed is the 100,000-ton ''[[Behemoth (DropShip_class)|Behemoth]]'', which due to its sheer size is incapable of entering gravity wells stronger than .6 g. The biggest DropShip that can actually enter the atmosphere in standard gravity is the 52,000-ton ''[[Mammoth]]''. The most common military [[BattleMech]] transport classes are the ''[[Leopard]]'' (one [[lance]]: 4 'Mechs, 2 fighters), the ''[[Union]]'' (one [[company]]: 12 'Mechs, 2 fighters), and the much rarer ''[[Overlord]]'' (one [[battalion]]: 36 'Mechs, 6 fighters); the most common aerospace fighter carrier is the ''[[Leopard CV]]'' class (one squadron: 6 fighters). The most common military [[BattleMech]] transport classes are the ''[[Leopard]]'' (one [[lance]]: 4 'Mechs, 2 fighters), the ''[[Union]]'' (one [[company]]: 12 'Mechs, 2 fighters), and the much rarer ''[[Overlord]]'' (one [[battalion]]: 36 'Mechs, 6 fighters); the most common aerospace fighter carrier is the ''[[Leopard CV]]'' class (one squadron: 6 fighters). Line 152:
Line 152: |civilian |civilian |[[DropShip#Spheroid_DropShips|spheroid]] |[[DropShip#Spheroid_DropShips|spheroid]] − |An advanced fully automated, self-loading civilian cargo carrier developed at the end of the Star League, almost identical to ''[[Cargomaster]]'' class. After a series of lost prototypes, the design was canceled. + |An advanced fully automated, self-loading civilian cargo carrier developed at the end of the Star League, almost identical to [[Cargomaster]] class. After a series of lost prototypes, the design was cancelled. |- |- |''[[Cargomaster]]'' |''[[Cargomaster]]'' Line 159:
Line 159: |military |military |[[DropShip#Spheroid_DropShips|spheroid]] |[[DropShip#Spheroid_DropShips|spheroid]] − |An advanced fully automated, self-loading military cargo carrier developed at the end of the Star League, it had slightly better fuel reserves but was otherwise identical to the ''[[Cargoking]]'' class. However due to manufacturing cost, only one prototype was built and was later dismantled.<ref>''Technical Readout: 3026 Revised'', p. 116: Production of the ''Cargomaster'' was canceled in the midst of the First Succession War; no more than 1 prototype was constructed</ref> + |An advanced fully automated, self-loading military cargo carrier developed at the end of the Star League, it had slightly better fuel reserves but was otherwise identical to the [[Cargoking]] class. However due to manufacturing cost, only one prototype was built and was later dismantled.<ref>''Technical Readout: 3026 Revised'', p. 116: Production of the ''CargoMaster'' was cancelled in the midst of the 1st Succession War; no more than 1 prototype was constructed.</ref> |- |- |''[[Carrier]]'' |''[[Carrier]]'' Line 168:
Line 168: |Clan built heavily armed fighter carrier (10 Fighters). |Clan built heavily armed fighter carrier (10 Fighters). |- |- − |''[[Claymore (DropShip class)|Claymore]]'' + |''[[Claymore]]'' |1,400 |1,400 |[[3054]] |[[3054]] Line 180:
Line 180: |military |military |[[DropShip#Spheroid_DropShips|spheroid]] |[[DropShip#Spheroid_DropShips|spheroid]] − |A [[Word_of_Blake|Word of Blake]] drone monitor platform based on the [[K-1]] DropShuttle. + |A [[Word_of_Blake|Word of Blake]] drone monitor platform based on the [[K-1]] dropshuttle. |- |- |''[[Colossus_(DropShip_class)|Colossus]]'' |''[[Colossus_(DropShip_class)|Colossus]]'' Line 189:
Line 189: |Designed to move an entire combined arms regiment (36 'Mechs, 72 vehicles, 12 platoons). |Designed to move an entire combined arms regiment (36 'Mechs, 72 vehicles, 12 platoons). |- |- − |''[[Condor (DropShip class)|Condor]]'' + |''[[Condor_(DropShip_class)|Condor]]'' |4,500 |4,500 |[[2801]] |[[2801]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Troop transport (20 light vehicles, 12 platoons). |Troop transport (20 light vehicles, 12 platoons). |- |- Line 200:
Line 200: |[[2602]] |[[2602]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] − |Star League era 'Mech transport (Four 'Mechs, Two Fighters). Clans have refitted the DropShip to carry five 'Mechs. + |Star League era 'Mech transport (4 'Mechs, 2 Fighters). Clans have refitted theirs to carry 5 'Mechs. |- |- − |''[[Conquistador (DropShip class)|Conquistador]]'' + |''[[Conquistador]]'' |17,400 |17,400 |[[3063]] |[[3063]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Combined assault transport and command ship (24 'Mechs, 18 Fighters, 12 heavy vehicles, 16 platoons, 20 battle armor squads). Extensive command facilities. Highly automated, requires only skeleton crew. Bays and quarters can be converted into a field hospital when empty. |Combined assault transport and command ship (24 'Mechs, 18 Fighters, 12 heavy vehicles, 16 platoons, 20 battle armor squads). Extensive command facilities. Highly automated, requires only skeleton crew. Bays and quarters can be converted into a field hospital when empty. − |- − |''[[Czar]]'' − |6,400 − |[[2462]] − |military/civilian − |[[DropShip#Spheroid DropShips|spheroid]] − |Early Infantry transport (Two Infantry Platoons). Obsolete by the [[thirty-first century]], the ship carried two Cargo bays of 1,900 tons for it's troops with a Small Craft Bay. Built with Primitive technology, the ship would fade away used as civilian transport it's final years of service. |- |- |''[[Danais (DropShip class)|Danais]]'' |''[[Danais (DropShip class)|Danais]]'' Line 221:
Line 214: |[[2728]] |[[2728]] |civilian |civilian − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Unarmed cargo ship based on the slightly larger [[Union]] class. A popular and numerous class, being one of the few DropShip types that the Star League allowed subjugated periphery states to build themselves. The armed and upgraded blockade runner version introduced by the [[Taurian Concordat]] is known as the [[Trojan]]. |Unarmed cargo ship based on the slightly larger [[Union]] class. A popular and numerous class, being one of the few DropShip types that the Star League allowed subjugated periphery states to build themselves. The armed and upgraded blockade runner version introduced by the [[Taurian Concordat]] is known as the [[Trojan]]. |- |- Line 228:
Line 221: |[[2600]] |[[2600]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Star League era 'Mech carrier (36 'Mechs), eventually replaced by the superior [[Overlord]] class. |Star League era 'Mech carrier (36 'Mechs), eventually replaced by the superior [[Overlord]] class. |- |- Line 235:
Line 228: |[[2445]] |[[2445]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] − |Among the earliest purpose-built military designs. Used by the [[Terran Hegemony]], the design was used ferry infantry, vehicles and some variants as Fighter Carriers. + |Among the earliest purpose-built military designs. Used by the [[Terran Hegemony]], the design was used ferry infantry, vehicles and some variants as Fighter Carriers. |- |- − |''[[Excalibur (DropShip class)|Excalibur]]'' + |''[[Excalibur_(DropShip_class)|Excalibur]]'' |16,000 |16,000 |[[2786]] |[[2786]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Combined arms transport (12 'Mechs, 90 heavy vehicles, 12 platoons). |Combined arms transport (12 'Mechs, 90 heavy vehicles, 12 platoons). |- |- Line 252:
Line 245: |Heavily armed combined arms transport (12 'Mechs, 12 heavy vehicles, 3 platoons). Noteworthy for mounting a Long Tom heavy artillery piece; capable of securing its landing zone by itself. |Heavily armed combined arms transport (12 'Mechs, 12 heavy vehicles, 3 platoons). Noteworthy for mounting a Long Tom heavy artillery piece; capable of securing its landing zone by itself. |- |- − |''[[Fury (DropShip class)|Fury]]'' + |''[[Fury_(DropShip_class)|Fury]]'' |1,850 |1,850 |[[2638]] |[[2638]] Line 263:
Line 256: |[[2531]] |[[2531]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Common tank transport (15 heavy vehicles). An upgraded version was launched in [[3055]]. |Common tank transport (15 heavy vehicles). An upgraded version was launched in [[3055]]. |- |- Line 270:
Line 263: |[[3096]] |[[3096]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] − |Free Worlds League build Fighter Carrier (18 Fighters) + |Free World League build Fighter Carrier (18 Fighters) |- |- |''[[Hamilcar]]'' |''[[Hamilcar]]'' Line 277:
Line 270: |[[3054]] |[[3054]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Specialized space assault transport (8 'Mechs, 4 Fighters). |Specialized space assault transport (8 'Mechs, 4 Fighters). |- |- Line 284:
Line 277: |[[3055]] |[[3055]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Heavily armed troop/tank transport (12 heavy vehicles, 4 platoons). |Heavily armed troop/tank transport (12 heavy vehicles, 4 platoons). |- |- Line 291:
Line 284: |[[3053]] |[[3053]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Troop/tank transport (36 heavy vehicles, 12 platoons). Shares many components with [[Overlord]] class, making production and maintenance easier. |Troop/tank transport (36 heavy vehicles, 12 platoons). Shares many components with [[Overlord]] class, making production and maintenance easier. |- |- Line 298:
Line 291: |[[3074]] |[[3074]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] − |The ship was noted for its high speed and multiple anti-WarShip armaments. + |The ship was noted for its high speed and multiple anti-warship armaments. |- |- |''[[Intruder]]'' |''[[Intruder]]'' Line 305:
Line 298: |[[2656]] |[[2656]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Heavily armed assault transport (2 Fighters, 4 platoons). |Heavily armed assault transport (2 Fighters, 4 platoons). |- |- Line 312:
Line 305: |[[2343]] |[[2343]] |civilian |civilian − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] − |Based on a [[Terran Hegemony]] design introduced in the early [[twenty-fifth century]] and the first bulk-cargo DropShips; eventually replaced as a class by the [[Mule]]. + |Based on a [[Terran Hegemony]] design introduced in the early 25th century and the first bulk-cargo DropShips; eventually replaced as a class by the [[Mule]]. |- |- |[[K-1 DropShuttle]] |[[K-1 DropShuttle]] Line 319:
Line 312: |[[2536]] |[[2536]] |civilian |civilian − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Passenger/cargo shuttle. Usually classed as a [[Small Craft]], not a DropShip. Clan version known as [[K-1_DropShuttle#Variants|K1-C]] is identical except for better armor and upgraded (though similar) weaponry. |Passenger/cargo shuttle. Usually classed as a [[Small Craft]], not a DropShip. Clan version known as [[K-1_DropShuttle#Variants|K1-C]] is identical except for better armor and upgraded (though similar) weaponry. |- |- Line 326:
Line 319: |[[3054]] |[[3054]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Designated patrol/assault craft. |Designated patrol/assault craft. |- |- Line 348:
Line 341: |military |military |[[DropShip#Aerodyne_DropShips|aerodyne]] |[[DropShip#Aerodyne_DropShips|aerodyne]] − |Standard BattleMech transport (4 'Mechs, 2 Fighters) since Star League era. Affectionately referred to as the "Brick". 1,800 ton upgraded version launched in [[3056]]. + |Standard BattleMech transport (4 'Mechs, 2 Fighters) since Star League era. Affectionally referred to as the "Brick". 1,800 ton upgraded version launched in [[3056]]. |- |- |''[[Leopard CV]]'' |''[[Leopard CV]]'' Line 375:
Line 368: |[[2808]] |[[2808]] |civilian |civilian − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Cargo carrier. Largest DropShip capable of planetary operations. |Cargo carrier. Largest DropShip capable of planetary operations. |- |- Line 382:
Line 375: |[[2449]] |[[2449]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |First 'Mech carrier ever (4 'Mechs), designed off a freighter design of the same name. Predecessor of the [[Confederate]] class. Flawed design, discontinued soon after introduction for inadequate armor and weapons. |First 'Mech carrier ever (4 'Mechs), designed off a freighter design of the same name. Predecessor of the [[Confederate]] class. Flawed design, discontinued soon after introduction for inadequate armor and weapons. |- |- − |''[[Mercer (DropShip class)|Mercer]]'' + |''[[Mercer]]'' |4,500 |4,500 |[[3065]] |[[3065]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Heavily armed and armored assault transport (10 'Mechs). |Heavily armed and armored assault transport (10 'Mechs). |- |- Line 396:
Line 389: |[[3063]] |[[3063]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Assault DropShip (2 Fighters). |Assault DropShip (2 Fighters). |- |- − |''[[Mingo]]'' + |''[[Miraborg]]'' − |5,000 − |[[2315]] − |Civilian − |[[DropShip#Spheroid DropShips|spheroid]] − |Cargo Transport. A Primitive Dropship/DropShuttle designed dock internally with [[Conestoga (JumpShip class)|''Conestoga'']]-class cargo JumpShip as part of colonization efforts of the [[Terran Alliance]]. It would fall out favor due to not having docking collar of a KF Boom to let it dock with modern/standard JumpShips. − |- − |''[[Miraborg (DropShip class)|Miraborg]]'' |9,750 |9,750 |[[3053]] |[[3053]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Fighter carrier (30 Fighters). Originally named "Charybdis" during its design phase, the class was renamed in memory of [[Tyra Miraborg]] shortly before the launch of the first ship. |Fighter carrier (30 Fighters). Originally named "Charybdis" during its design phase, the class was renamed in memory of [[Tyra Miraborg]] shortly before the launch of the first ship. |- |- Line 417:
Line 403: |[[2652]] |[[2652]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Star League predecessor to the [[Model 97]] tug which was described as a refit of the Model 96 class. |Star League predecessor to the [[Model 97]] tug which was described as a refit of the Model 96 class. |- |- Line 424:
Line 410: |[[3051]] |[[3051]] |civilian |civilian − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Designated tug/rescue ship. |Designated tug/rescue ship. |- |- Line 431:
Line 417: |[[2759]] |[[2759]] |civilian |civilian − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Standard passenger liner. |Standard passenger liner. |- |- Line 445:
Line 431: |[[3056]] |[[3056]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Heavily armed troop transport (12 platoons). |Heavily armed troop transport (12 platoons). |- |- Line 452:
Line 438: |[[3065]] |[[3065]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Powerful assault DropShip (6 fighters, 9 [[small craft]], 27 battle armor squads), also provided to [[Clan Nova Cat]]. Ship carries a limited quantity of [[Teleoperated Capital Missile|teleoperated capital missiles]]. |Powerful assault DropShip (6 fighters, 9 [[small craft]], 27 battle armor squads), also provided to [[Clan Nova Cat]]. Ship carries a limited quantity of [[Teleoperated Capital Missile|teleoperated capital missiles]]. |- |- − |''[[Noruff (DropShip class)|Noruff]]'' + |''[[Noruff]]'' |1,900 |1,900 |[[3056]] |[[3056]] Line 462:
Line 448: |Designated assault craft. Only one prototype known to exist by [[3057]]. |Designated assault craft. Only one prototype known to exist by [[3057]]. |- |- − |''[[Okinawa (DropShip class)|Okinawa]]'' + |''[[Okinawa]]'' |4,500 |4,500 |[[3055]] |[[3055]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Fighter carrier (18 Fighters). |Fighter carrier (18 Fighters). |- |- Line 473:
Line 459: |[[3063]] |[[3063]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] − |Combined arms transport (5 'Mechs, 4 Fighters, 10 tanks, 1 elemental Star) developed from venerable Fortress class. + |Combined arms transport (5 'Mechs, 4 Fighters, 10 tanks, 1 elemental star) developed from venerable Fortress class. |- |- |''[[Overlord]]'' |''[[Overlord]]'' Line 480:
Line 466: |[[2762]] |[[2762]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Common BattleMech transport (36 'Mechs, 6 Fighters). |Common BattleMech transport (36 'Mechs, 6 Fighters). |- |- Line 487:
Line 473: |[[2818]] |[[2818]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Fighter transport (45 'Mechs). Clan redesign of the classic [[Overlord]] class. |Fighter transport (45 'Mechs). Clan redesign of the classic [[Overlord]] class. |- |- Line 494:
Line 480: |[[2623]] |[[2623]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Star League era DropShip class designed as "little more than large gun platforms" for WarShip escort. |Star League era DropShip class designed as "little more than large gun platforms" for WarShip escort. |- |- Line 501:
Line 487: |[[2657]] |[[2657]] |civilian |civilian − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |The design was known for its luxurious amenities. |The design was known for its luxurious amenities. |- |- − |''[[Rose (DropShip class)|Rose]]'' + |''[[Rose]]'' |16,000 |16,000 |[[3054]] |[[3054]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Heavily armed freighter with advanced avionics, designed to have an inconspicuous appearance. Can carry 1 platoon of infantry and 4 [[Small Craft]]. |Heavily armed freighter with advanced avionics, designed to have an inconspicuous appearance. Can carry 1 platoon of infantry and 4 [[Small Craft]]. |- |- Line 515:
Line 501: |[[2875]] |[[2875]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Clan battle armor carrier (15 Elemental Points). Based off the ''[[Intruder]]'' design. |Clan battle armor carrier (15 Elemental Points). Based off the ''[[Intruder]]'' design. |- |- − |''[[Saturn (DropShuttle class)|Saturn]] '' + |''[[Saturn_(DropShuttle_class)|Saturn]] '' − |1,200 + |1,200 − |[[2243]] + |[[2243]] − |military + |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Used by the Terran Alliance as colonial patrol ship. It is one oldest known DropShip designs used for military purposes. |Used by the Terran Alliance as colonial patrol ship. It is one oldest known DropShip designs used for military purposes. − |- + |- |''[[Seeker]]'' |''[[Seeker]]'' |6,700 |6,700 |[[2815]] |[[2815]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Troop transport (64 light vehicles, 4 platoons). |Troop transport (64 light vehicles, 4 platoons). |- |- Line 536:
Line 522: |[[3100]] |[[3100]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] − |Early thirty-second century troop/tank transport (20 battle armor squads & 12 light vehicles) utilized by the Free Worlds League. + |Early 32nd Century troop/tank transport (20 battle armor squads & 12 light vehicles) utilized by the Free World League. |- |- − |''[[Titan (DropShip class)|Titan]]'' + |''[[Titan_(DropShip_class)|Titan]]'' |12,000 |12,000 |[[2647]] |[[2647]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Heavily armed fighter carrier (18 Fighters). Extinct in the [[Inner Sphere]] powers, but still in use with the Clans. |Heavily armed fighter carrier (18 Fighters). Extinct in the [[Inner Sphere]] powers, but still in use with the Clans. |- |- Line 550:
Line 536: |[[2593]] |[[2593]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Common troop/tank transport (45 heavy vehicles, 8 light vehicles, 4 platoons). Upgraded version launched in [[3057]]. |Common troop/tank transport (45 heavy vehicles, 8 light vehicles, 4 platoons). Upgraded version launched in [[3057]]. |- |- Line 557:
Line 543: |[[2720]] |[[2720]] |civilian |civilian − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] − |"Blockade runner" version of the ubiquitous unarmed [[Danais (DropShip class)|Danais]] class merchant, introduced by the [[Taurian Concordat]]. Features 2 [[Small Craft]] bays and weapons which are typically concealed to appear like a common Danais class vessel. + |"Blockade runner" version of the ubiquitous unarmed [[Danais]] class merchant, introduced by the [[Taurian Concordat]]. Features 2 [[Small Craft]] bays and weapons which are typically concealed to appear like a common Danais class vessel. |- |- |''[[Trutzburg]]'' |''[[Trutzburg]]'' − |6,000 + |6,000 − |[[3112]] + |[[3112]] − |military + |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] − |A combined arms transport ship, one few made in Lyran Commonwealth in the thirty-second century. (6 fighters, 12 BattleMechs, 4 battle armor Squads) + |A Combined Arms transport ship, one few made in Lyran Commonwealth in the 32nd Century. (6 fighters, 12 BattleMechs, 4 battle armor Squads) − |- + |- |''[[Union]]'' |''[[Union]]'' |3,500 |3,500 |[[2708]] |[[2708]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |Standard BattleMech transport (12 'Mechs, 2 Fighters). Iconic DropShip class. |Standard BattleMech transport (12 'Mechs, 2 Fighters). Iconic DropShip class. |- |- Line 578:
Line 564: |[[2829]] |[[2829]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |'Mech transport (15 'Mechs). Clan redesign of the venerable [[Union]] class. |'Mech transport (15 'Mechs). Clan redesign of the venerable [[Union]] class. |- |- Line 585:
Line 571: |[[2715]] |[[2715]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] |Tiny, superfast infantry transport from the Star League era. The design became extinct during the [[Succession Wars (History)|Succession Wars]]. |Tiny, superfast infantry transport from the Star League era. The design became extinct during the [[Succession Wars (History)|Succession Wars]]. |- |- − |''[[Vengeance (DropShip class)|Vengeance]]'' + |''[[Vengeance]]'' |10,000 |10,000 |[[2682]] |[[2682]] |military |military − |[[DropShip#Aerodyne DropShips|aerodyne]] + |[[DropShip#Aerodyne_DropShips|aerodyne]] − |Fighter carrier (40 [[aerospace fighter|fighters]], 3 [[small craft]]). + |Fighter carrier (40 [[fighters]], 3 [[small craft]]). |- |- − |''[[Vulture (DropShip class)|Vulture]]'' + |''[[Vulture_(DropShip_class)|Vulture]]'' |3,500 |3,500 |[[2312]] |[[2312]] |military |military − |[[DropShip#Spheroid DropShips|spheroid]] + |[[DropShip#Spheroid_DropShips|spheroid]] |These ships carried infantry and a limited number of light vehicles it main payload. They were known to be similar to what became the [[Seeker]] class that was based on the Vulture. |These ships carried infantry and a limited number of light vehicles it main payload. They were known to be similar to what became the [[Seeker]] class that was based on the Vulture. |- |- Line 619:
Line 605: ==Bibliography== ==Bibliography== <div class="desktop-3-col"> <div class="desktop-3-col"> − * ''[[AeroTech]]'' + *''[[AeroTech]]'' − * ''[[AeroTech 2]]'' + *''[[AeroTech 2]]'' − * ''[[AeroTech 2 Record Sheets]]'' + *''[[AeroTech 2 Revised Edition|Aerotech 2 Revised]]'' − * ''[[AeroTech 2 Revised Edition|AeroTech 2 Revised]]'' + *''[[AeroTech 2 Record Sheets]]'' − * ''[[BattleSpace]]'' + *''[[BattleSpace]]'' − * ''[[Strategic Operations]]'' + *''[[Strategic Operations]]'' − * ''[[Technical Readout: 3025]]'' + *''[[Technical Readout: 3025]]'' − * ''[[Technical Readout: 3026 Revised]]'' + *''[[Technical Readout: 3026 Revised]]'' − * ''[[Technical Readout: 3057]]'' + *''[[Technical Readout: 3057]]'' − * ''[[Technical Readout: 3057 Revised]]'' + *''[[Technical Readout: 3057 Revised]]'' − * ''[[Technical Readout: 3067]]'' + *''[[Technical Readout: 3067]]'' − * ''[[Technical Readout: 3075]]'' + *''[[Technical Readout: 3075]]'' − * ''[[Total Warfare]]'' + *''[[Total Warfare]]'' </div> </div>
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | [[File:Union cutaway color TM.png|right|300px|thumb|''Union''-class DropShip | + | [[File:Union cutaway color TM.png|right|300px|thumb|''Union''-class DropShip cut-away ]] |
A '''DropShip''' is defined as a type of spaceship massing between 200 and 100,000 tons that is itself incapable of faster-than-light (FTL) travel. They essentially conduct all other aspects of space travel, including transit between planets and [[jump point]]s and planetary landings. For FTL interstellar movement, they dock with [[JumpShip]]s by means of a [[docking collar]]. | A '''DropShip''' is defined as a type of spaceship massing between 200 and 100,000 tons that is itself incapable of faster-than-light (FTL) travel. They essentially conduct all other aspects of space travel, including transit between planets and [[jump point]]s and planetary landings. For FTL interstellar movement, they dock with [[JumpShip]]s by means of a [[docking collar]]. | ||
| Line 5: | Line 5: | ||
DropShips are the workhorse of interplanetary space travel. It is the DropShips (and occasionally their smaller cousins, the [[Small Craft]]) that move cargo and passengers between planetary surfaces, orbits, space stations and jump points. While transport is their primary role, some have been built for special purposes and act as tugs, rescue ships, fighter carriers or even designated combat DropShips. Accordingly, a wide and diverse variety of DropShip types exist. | DropShips are the workhorse of interplanetary space travel. It is the DropShips (and occasionally their smaller cousins, the [[Small Craft]]) that move cargo and passengers between planetary surfaces, orbits, space stations and jump points. While transport is their primary role, some have been built for special purposes and act as tugs, rescue ships, fighter carriers or even designated combat DropShips. Accordingly, a wide and diverse variety of DropShip types exist. | ||
| − | Even though many DropShips serve as military spaceships, naval terms such as "Corvette" | + | Even though many DropShips serve as military spaceships, naval terms such as "Corvette", "Destroyer", "Cruiser" etc. are never applied to them; these are exclusively used for true [[WarShip]]s, i.e. the huge Combat JumpShips that outclass DropShips by an order of magnitude (typically massing several hundred thousands or even millions of tons). |
==History== | ==History== | ||
| − | The term "DropShip" was first used in the [[ | + | The term "DropShip" was first used in the [[22nd century]] to describe the cargo-carrying shuttles then in use to ferry cargo and passengers between the JumpShips of that era. It was not until the [[25th century]] when "DropShip" became the official designation for a type of ship more sophisticated than the earlier [[DropShuttle|shuttles]]. Instead of being carried within the hull of a JumpShip, these vessels were now attached on the outside and would "drop" away once it had arrived. By the [[31st century]], there were over 250 DropShip designs on record, though only approximately 100 were still in service, with twenty of those constituting the majority of DropShips in existence.<ref name=BSS20>''BattleSpace - Sourcebook'', p. 18-20</ref><ref name=DJOM8>''DropShips and JumpShips - Operations Manual'', p. 4-8</ref><ref name=AT69>''AeroTech 2'', p. 66-69</ref> |
==Construction== | ==Construction== | ||
| − | While DropShips come in a variety of shapes and sizes, the heart of every DropShip is its engineering section, which is comprised of two systems: a power plant and an [[Interplanetary Drive - | + | While DropShips come in a variety of shapes and sizes, the heart of every DropShip is its engineering section, which is comprised of two systems: a power plant and an [[Interplanetary Drive - Dropships| |
engine]]. The fusion engine works by expelling plasma through shielded exhaust nozzles to create thrust. All DropShips have a main exhaust nozzle to propel the ship forward at a steady acceleration. The most advanced also have numerous plasma exhaust nozzles dotting their hulls to control steering, but such devices are fragile and expensive, leaving many DropShips equipped with hardier but less efficient chemical rockets to fulfill this role. The plasma exhaust is created as a by-product of nuclear fusion and requires a constant supply of fuel in the form of liquid H<sub>2</sub>, which is carried aboard in large storage tanks and fed to the drive by one of two systems. The one found on all DropShips is a heat-expansion system where the H<sub>2</sub> is fed into a heated chamber; here the high temperature causes it to expand, with the resulting pressure forcing it into the engine core. Military DropShips will also have a series of high-speed pumps which can supply a constant stream of fuel for the engine, allowing for rapid changes in thrust. Unlike the engine core, the fusion plant which provides power for the DropShip is a closed system, reprocessing its own by-products and requiring little additional fuel. It can however tap into the same H<sub>2</sub> storage tanks used by the engines when needed.<ref name=BSS20/><ref name=DJOM8/><ref name=AT69/> | engine]]. The fusion engine works by expelling plasma through shielded exhaust nozzles to create thrust. All DropShips have a main exhaust nozzle to propel the ship forward at a steady acceleration. The most advanced also have numerous plasma exhaust nozzles dotting their hulls to control steering, but such devices are fragile and expensive, leaving many DropShips equipped with hardier but less efficient chemical rockets to fulfill this role. The plasma exhaust is created as a by-product of nuclear fusion and requires a constant supply of fuel in the form of liquid H<sub>2</sub>, which is carried aboard in large storage tanks and fed to the drive by one of two systems. The one found on all DropShips is a heat-expansion system where the H<sub>2</sub> is fed into a heated chamber; here the high temperature causes it to expand, with the resulting pressure forcing it into the engine core. Military DropShips will also have a series of high-speed pumps which can supply a constant stream of fuel for the engine, allowing for rapid changes in thrust. Unlike the engine core, the fusion plant which provides power for the DropShip is a closed system, reprocessing its own by-products and requiring little additional fuel. It can however tap into the same H<sub>2</sub> storage tanks used by the engines when needed.<ref name=BSS20/><ref name=DJOM8/><ref name=AT69/> | ||
| Line 21: | Line 21: | ||
===DropShip Category=== | ===DropShip Category=== | ||
| − | DropShips are based around two basic | + | DropShips are based around two basic hullforms, aerodyne and spheroid. Depending on their intended role, DropShips can be constructed following either of these two alternative approaches. |
| − | Although all DropShips are either of the spheroid or the aerodyne subtype, there is arguably a third one: ships which are limited to operating in deep space for one reason or another and would be destroyed when attempting to enter an atmosphere or land on a planet, rendering the differences between aerodyne and spheroid designs irrelevant to them. Examples include the superlarge ''[[Behemoth (DropShip | + | Although all DropShips are either of the spheroid or the aerodyne subtype, there is arguably a third one: ships which are limited to operating in deep space for one reason or another and would be destroyed when attempting to enter an atmosphere or land on a planet, rendering the differences between aerodyne and spheroid designs irrelevant to them. Examples include the superlarge ''[[Behemoth (DropShip)|Behemoth]]'' class cargo hauler, which is a spheroid design but has insufficient acceleration for planetary operations and is too large and fragile to operate in gravity, and the nominally aerodyne ''[[Achilles (DropShip)|Achilles]]'' and ''[[Vengeance]]'' class military DropShips which were never designed for atmospheric operations. |
====Aerodyne DropShips==== | ====Aerodyne DropShips==== | ||
| − | Aerodyne DropShips are shaped roughly similar to conventional aircraft, using their aerodynamic hull shape to generate lift within an atmosphere. This makes these DropShips ideally suited for atmospheric operations, at the expense of being more expensive and harder to produce than | + | Aerodyne DropShips are shaped roughly similar to conventional aircraft, using their aerodynamic hull shape to generate lift within an atmosphere. This makes these DropShips ideally suited for atmospheric operations, at the expense of being more expensive and harder to produce than sphereoid ships and with more restrictive size requirements. Many aerodynes also require runways to land and take off, limiting where they can operate. To facilitate atmospheric and deep space travel, most aerodynes are equipped with two sets of exhaust nozzles, one on the bottom and one on the rear. Aerodynes will use their bottom thrusters and transit drive during space operations, then switch over to after thrusters and maneuver drive when in an atmosphere. While taking up additional space, this alleviates the issue of internal orientation by allowing the vessel's nose and rear to remain "forward" and "aft" at all times.<ref name=BSS20/><ref name=DJOM8/><ref name=AT69/> |
====Spheroid DropShips==== | ====Spheroid DropShips==== | ||
| − | Spheroid DropShips are so named for their rounded hulls, making them easier and cheaper to construct. Their simple design also makes them | + | Spheroid DropShips are so named for their rounded hulls, making them easier and cheaper to construct. Their simple design also makes them more sturdy and allows them to be built much larger than aerodyne DropShips, with the largest spheroid outmassing the largest aerodyne many times over. Spheroid DropShips have a single engine drive positioned on the ship's bottom which is used to vertically descend onto a planetary surface and take off in the same way. This allows spheroid DropShips to operate independent from runways or even spaceports, making them ideal for exploring unknown planets and giving them a tactical advantage in military operations. However, their simple and versatile landing and takeoff pattern requires more fuel and can cause significant damage to the ground. They also cannot travel through the atmosphere as quickly as aerodyne vessels and their method of flight is more unstable, making them less practical for atmospheric combat. A complex system of thrusters positioned around the hull and controlled by the main computer helps make atmospheric flight and landing possible, but if these systems are damaged a spheriod DropShip can easily lose control and crash.<ref name=BSS20/><ref name=DJOM8/><ref>''DropShips and JumpShips - Operations Manual'', p. 20-22</ref><ref name=AT69/><ref>''AeroTech 2'', p. 11, 37</ref> |
===Classification of DropShips=== | ===Classification of DropShips=== | ||
| Line 35: | Line 35: | ||
* Assault - This primarily military DropShip is designed for maximum firepower. Typically used for anti-[[aerospace fighter]] and anti-DropShip operations, they can be used for ground assault purposes, though this is rare. Some models of assault ships carry anti-WarShip weaponry and are referred to as Pocket WarShips; this type of DropShip is also known to carry limited quantities of [[BattleMech|BattleMechs]], [[battle armor]], marines, and aerospace fighters, usually just enough to provide "point-blank" defense. | * Assault - This primarily military DropShip is designed for maximum firepower. Typically used for anti-[[aerospace fighter]] and anti-DropShip operations, they can be used for ground assault purposes, though this is rare. Some models of assault ships carry anti-WarShip weaponry and are referred to as Pocket WarShips; this type of DropShip is also known to carry limited quantities of [[BattleMech|BattleMechs]], [[battle armor]], marines, and aerospace fighters, usually just enough to provide "point-blank" defense. | ||
| − | **<span id="Pocket WarShip">Pocket WarShip</span> - A military DropShip type based on the | + | ** <span id="Pocket WarShip">Pocket WarShip</span> - A military DropShip type based on the Assault DropShips. These ships are designed to carry [[Capital Missile|Capital Missiles]] and sometimes [[:Category:Sub-Capital Weapons|Sub-Capital Weaponry]]. Most are typically heavily armed with standard BattleMech-scale weaponry. Early versions of this ship type were known as '''Q-Ships'''. Following the [[Jihad]], with so many nations' shipyards damaged or destroyed, many factions turned to these as the backbone of their navies. |
* Fighter Carrier or Aerospace Carrier - Designed for carrying/supporting aerospace fighter craft operations. Though other DropShips are referred to as 'Mech carriers, troop carriers, etc., a ship described as a "carrier" is understood to be a fighter carrier. These ships typically have '''CV''' (for '''C'''arrier '''V'''essel) appended to their name, as in ''[[Leopard CV]]''. | * Fighter Carrier or Aerospace Carrier - Designed for carrying/supporting aerospace fighter craft operations. Though other DropShips are referred to as 'Mech carriers, troop carriers, etc., a ship described as a "carrier" is understood to be a fighter carrier. These ships typically have '''CV''' (for '''C'''arrier '''V'''essel) appended to their name, as in ''[[Leopard CV]]''. | ||
*Cargo Ship - Typically civilian model of ship, used for hauling bulk cargo. Some ships are fitted to transport liquids and are usually referred to as Liquid Carriers. | *Cargo Ship - Typically civilian model of ship, used for hauling bulk cargo. Some ships are fitted to transport liquids and are usually referred to as Liquid Carriers. | ||
| Line 46: | Line 46: | ||
==DropShip Operations== | ==DropShip Operations== | ||
| − | Once a DropShip has arrived at a system's jump point and detached from its JumpShip, it can begin the long journey to its destination point within the system. This depends on the star system in question, where the DropShip is trying to travel to, and how fast the ship accelerates during the course of its journey. Thanks to their powerful fusion engines and fuel reserves, DropShips can travel interplanetary distances by | + | Once a DropShip has arrived at a system's jump point and detached from its JumpShip, it can begin the long journey to its destination point within the system. This depends on the star system in question, where the DropShip is trying to travel to, and how fast the ship accelerates during the course of its journey. Thanks to their powerful fusion engines and fuel reserves, DropShips can travel interplanetary distances by constanting accelerating towards their destination then, at the midway point, flipping around and using their engines to decelerate at the same rate. Assuming the distance between the start and end point are known, this can be calculated with T = 2√(D/A), where T equals time in hours, D is distance in kilometers from the starting point to midway point, and A is acceleration in kilometers per hour per hour. In most cases it would take several days or more for a DropShip to travel between a jump point and a planet in-system. During this time the DropShip will be burning fuel to maintain its constant acceleration and deceleration and any maneuvering it must undertake. The most common way of expressing this is by burn-day, which is the amount of fuel burned by accelerating at 1 G for one day.<ref>''BattleSpace - Rulebook'', p. 52</ref> |
| − | When landing or lifting off from a planet, DropShips can do so vertically if | + | When landing or lifting off from a planet, DropShips can do so vertically if sphereoid or horizontally if aerodyne; aerodynes may also land horizontally if the planet lacks an atmosphere. Verticle landings and takeoffs are more versatile as they require only as much space as to fit the DropShip, but are more difficult as a DropShip at low velocity is more unstable, burns more fuel and causes ground damage. Horizontal landings and takeoffs require a runway of at least 600 meters, though experience pilots can land on shorter stretches using their bottom thrusters. Once grounded, cargo is typically offloaded or loaded by DropShip crew members, usually wearing [[Exoskeleton]]s to make the job go quicker, though some military units will use their 'Mechs to help speed up the process.<ref>''BattleSpace - Rulebook'', p. 53-57</ref> |
| − | During combat operations, military DropShips that land to disembark their cargo will typically do so well away from the front lines as a means of preserving them, both for their incredible expense and for their ability to withdraw troops from a losing engagement. In instances where troops must be landed closer to an enemy force, or where a DropShip cannot land due to hazardous terrain, it may instead carry out a '''Combat Drop'''. In a combat drop, BattleMechs and [[battle armor]]ed troopers will exit the DropShip while at high altitude or in orbit. These units use their integral [[jump jets]] or disposable jet packs to control their descent and safely land, but even among well-trained forces a combat drop is a hazardous endeavor. For orbital combat drops, a special [[Drop Cocoon]] is used which protects the unit during atmospheric reentry then falls away.<ref>''JumpShips and DropShips'', | + | During combat operations, military DropShips that land to disembark their cargo will typically do so well away from the front lines as a means of preserving them, both for their incredible expense and for their ability to withdraw troops from a losing engagement. In instances where troops must be landed closer to an enemy force, or where a DropShip cannot land due to hazardous terrain, it may instead carry out a '''Combat Drop'''. In a combat drop, BattleMechs and [[battle armor]]ed troopers will exit the DropShip while at high altitude or in orbit. These units use their integral [[jump jets]] or disposable jet packs to control their descent and safely land, but even among well-trained forces a combat drop is a hazardous endeavor. For orbital combat drops, a special [[Drop Cocoon]] is used which protects the unit during atmospheric reentry then falls away.<ref>''JumpShips and DropShips'', p. 42-43</ref><ref>''BattleSpace - Rulebook'', p. 37</ref> A variation on this tactic is known as the [[Hover-Drop Maneuver]]. |
| − | Maintaining a DropShip is a constant endeavor, not least because many will be decades if not centuries old. Reducing wear and tear by avoiding atmospheric operations or active maneuvering can help, but nothing short of mothballing it will help preserve a DropShip that doesn't have a well-trained crew to look after it. Even for the smaller DropShips, the weekly maintenance needed to keep the vessel running can cost hundreds of [[C-bill]]s, | + | Maintaining a DropShip is a constant endeavor, not least because many will be decades if not centuries old. Reducing wear and tear by avoiding atmospheric operations or active maneuvering can help, but nothing short of mothballing it will help preserve a DropShip that doesn't have a well-trained crew to look after it. Even for the smaller DropShips, the weekly maintenance needed to keep the vessel running can cost hundreds of [[C-bill]]s, nevermind repairing and replacing components or armor due to battle damage. Having a well-oiled crew is also important for a DropShip, though on most civilian vessels only the senior crew will sign on with a permanent contract, with the rest signing on for a limited time span. For security reasons, a military DropShip's crew will all be permanent members who have gone through extensive screening. Crew wages vary by vessel and era, but in the middle of the 31st century the average DropShip pilot earned 550 C-bills a month at minimum, while an engineer earned 450 C-bills.<ref>''BattleSpace - Rulebook'', p. 57-62</ref> |
==Manufacturing== | ==Manufacturing== | ||
| − | The smallest known spaceship to meet the DropShip criteria is arguably the 200-ton [[K-1|K-1 DropShuttle]], although it is generally classified as a [[Small Craft]] instead. The largest DropShip ever constructed is the 100,000-ton ''[[Behemoth (DropShip_class)|Behemoth]]'', which due to its sheer size is incapable of entering gravity wells stronger than | + | The smallest known spaceship to meet the DropShip criteria is arguably the 200-ton [[K-1|K-1 DropShuttle]], although it is generally classified as a [[Small Craft]] instead. The largest DropShip ever constructed is the 100,000-ton ''[[Behemoth (DropShip_class)|Behemoth]]'', which due to its sheer size is incapable of entering gravity wells stronger than .6 g. The biggest DropShip that can actually enter the atmosphere in standard gravity is the 52,000-ton ''[[Mammoth]]''. |
The most common military [[BattleMech]] transport classes are the ''[[Leopard]]'' (one [[lance]]: 4 'Mechs, 2 fighters), the ''[[Union]]'' (one [[company]]: 12 'Mechs, 2 fighters), and the much rarer ''[[Overlord]]'' (one [[battalion]]: 36 'Mechs, 6 fighters); the most common aerospace fighter carrier is the ''[[Leopard CV]]'' class (one squadron: 6 fighters). | The most common military [[BattleMech]] transport classes are the ''[[Leopard]]'' (one [[lance]]: 4 'Mechs, 2 fighters), the ''[[Union]]'' (one [[company]]: 12 'Mechs, 2 fighters), and the much rarer ''[[Overlord]]'' (one [[battalion]]: 36 'Mechs, 6 fighters); the most common aerospace fighter carrier is the ''[[Leopard CV]]'' class (one squadron: 6 fighters). | ||
| Line 152: | Line 152: | ||
|civilian | |civilian | ||
|[[DropShip#Spheroid_DropShips|spheroid]] | |[[DropShip#Spheroid_DropShips|spheroid]] | ||
| − | |An advanced fully automated, self-loading civilian cargo carrier developed at the end of the Star League, almost identical to | + | |An advanced fully automated, self-loading civilian cargo carrier developed at the end of the Star League, almost identical to [[Cargomaster]] class. After a series of lost prototypes, the design was cancelled. |
|- | |- | ||
|''[[Cargomaster]]'' | |''[[Cargomaster]]'' | ||
| Line 159: | Line 159: | ||
|military | |military | ||
|[[DropShip#Spheroid_DropShips|spheroid]] | |[[DropShip#Spheroid_DropShips|spheroid]] | ||
| − | |An advanced fully automated, self-loading military cargo carrier developed at the end of the Star League, it had slightly better fuel reserves but was otherwise identical to the | + | |An advanced fully automated, self-loading military cargo carrier developed at the end of the Star League, it had slightly better fuel reserves but was otherwise identical to the [[Cargoking]] class. However due to manufacturing cost, only one prototype was built and was later dismantled.<ref>''Technical Readout: 3026 Revised'', p. 116: Production of the ''CargoMaster'' was cancelled in the midst of the 1st Succession War; no more than 1 prototype was constructed.</ref> |
|- | |- | ||
|''[[Carrier]]'' | |''[[Carrier]]'' | ||
| Line 168: | Line 168: | ||
|Clan built heavily armed fighter carrier (10 Fighters). | |Clan built heavily armed fighter carrier (10 Fighters). | ||
|- | |- | ||
| − | |''[[ | + | |''[[Claymore]]'' |
|1,400 | |1,400 | ||
|[[3054]] | |[[3054]] | ||
| Line 180: | Line 180: | ||
|military | |military | ||
|[[DropShip#Spheroid_DropShips|spheroid]] | |[[DropShip#Spheroid_DropShips|spheroid]] | ||
| − | |A [[Word_of_Blake|Word of Blake]] drone monitor platform based on the [[K-1]] | + | |A [[Word_of_Blake|Word of Blake]] drone monitor platform based on the [[K-1]] dropshuttle. |
|- | |- | ||
|''[[Colossus_(DropShip_class)|Colossus]]'' | |''[[Colossus_(DropShip_class)|Colossus]]'' | ||
| Line 189: | Line 189: | ||
|Designed to move an entire combined arms regiment (36 'Mechs, 72 vehicles, 12 platoons). | |Designed to move an entire combined arms regiment (36 'Mechs, 72 vehicles, 12 platoons). | ||
|- | |- | ||
| − | |''[[ | + | |''[[Condor_(DropShip_class)|Condor]]'' |
|4,500 | |4,500 | ||
|[[2801]] | |[[2801]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Troop transport (20 light vehicles, 12 platoons). | |Troop transport (20 light vehicles, 12 platoons). | ||
|- | |- | ||
| Line 200: | Line 200: | ||
|[[2602]] | |[[2602]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
| − | |Star League era 'Mech transport ( | + | |Star League era 'Mech transport (4 'Mechs, 2 Fighters). Clans have refitted theirs to carry 5 'Mechs. |
|- | |- | ||
| − | |''[[ | + | |''[[Conquistador]]'' |
|17,400 | |17,400 | ||
|[[3063]] | |[[3063]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Combined assault transport and command ship (24 'Mechs, 18 Fighters, 12 heavy vehicles, 16 platoons, 20 battle armor squads). Extensive command facilities. Highly automated, requires only skeleton crew. Bays and quarters can be converted into a field hospital when empty. | |Combined assault transport and command ship (24 'Mechs, 18 Fighters, 12 heavy vehicles, 16 platoons, 20 battle armor squads). Extensive command facilities. Highly automated, requires only skeleton crew. Bays and quarters can be converted into a field hospital when empty. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|''[[Danais (DropShip class)|Danais]]'' | |''[[Danais (DropShip class)|Danais]]'' | ||
| Line 221: | Line 214: | ||
|[[2728]] | |[[2728]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Unarmed cargo ship based on the slightly larger [[Union]] class. A popular and numerous class, being one of the few DropShip types that the Star League allowed subjugated periphery states to build themselves. The armed and upgraded blockade runner version introduced by the [[Taurian Concordat]] is known as the [[Trojan]]. | |Unarmed cargo ship based on the slightly larger [[Union]] class. A popular and numerous class, being one of the few DropShip types that the Star League allowed subjugated periphery states to build themselves. The armed and upgraded blockade runner version introduced by the [[Taurian Concordat]] is known as the [[Trojan]]. | ||
|- | |- | ||
| Line 228: | Line 221: | ||
|[[2600]] | |[[2600]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Star League era 'Mech carrier (36 'Mechs), eventually replaced by the superior [[Overlord]] class. | |Star League era 'Mech carrier (36 'Mechs), eventually replaced by the superior [[Overlord]] class. | ||
|- | |- | ||
| Line 235: | Line 228: | ||
|[[2445]] | |[[2445]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
| − | |Among the earliest purpose-built military designs. Used by the [[Terran Hegemony]], the design was used ferry infantry, vehicles and some variants as Fighter Carriers. | + | |Among the earliest purpose-built military designs. Used by the [[Terran Hegemony]], the design was used ferry infantry, vehicles and some variants as Fighter Carriers. |
|- | |- | ||
| − | |''[[ | + | |''[[Excalibur_(DropShip_class)|Excalibur]]'' |
|16,000 | |16,000 | ||
|[[2786]] | |[[2786]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Combined arms transport (12 'Mechs, 90 heavy vehicles, 12 platoons). | |Combined arms transport (12 'Mechs, 90 heavy vehicles, 12 platoons). | ||
|- | |- | ||
| Line 252: | Line 245: | ||
|Heavily armed combined arms transport (12 'Mechs, 12 heavy vehicles, 3 platoons). Noteworthy for mounting a Long Tom heavy artillery piece; capable of securing its landing zone by itself. | |Heavily armed combined arms transport (12 'Mechs, 12 heavy vehicles, 3 platoons). Noteworthy for mounting a Long Tom heavy artillery piece; capable of securing its landing zone by itself. | ||
|- | |- | ||
| − | |''[[ | + | |''[[Fury_(DropShip_class)|Fury]]'' |
|1,850 | |1,850 | ||
|[[2638]] | |[[2638]] | ||
| Line 263: | Line 256: | ||
|[[2531]] | |[[2531]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Common tank transport (15 heavy vehicles). An upgraded version was launched in [[3055]]. | |Common tank transport (15 heavy vehicles). An upgraded version was launched in [[3055]]. | ||
|- | |- | ||
| Line 270: | Line 263: | ||
|[[3096]] | |[[3096]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
| − | |Free | + | |Free World League build Fighter Carrier (18 Fighters) |
|- | |- | ||
|''[[Hamilcar]]'' | |''[[Hamilcar]]'' | ||
| Line 277: | Line 270: | ||
|[[3054]] | |[[3054]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Specialized space assault transport (8 'Mechs, 4 Fighters). | |Specialized space assault transport (8 'Mechs, 4 Fighters). | ||
|- | |- | ||
| Line 284: | Line 277: | ||
|[[3055]] | |[[3055]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Heavily armed troop/tank transport (12 heavy vehicles, 4 platoons). | |Heavily armed troop/tank transport (12 heavy vehicles, 4 platoons). | ||
|- | |- | ||
| Line 291: | Line 284: | ||
|[[3053]] | |[[3053]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Troop/tank transport (36 heavy vehicles, 12 platoons). Shares many components with [[Overlord]] class, making production and maintenance easier. | |Troop/tank transport (36 heavy vehicles, 12 platoons). Shares many components with [[Overlord]] class, making production and maintenance easier. | ||
|- | |- | ||
| Line 298: | Line 291: | ||
|[[3074]] | |[[3074]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
| − | |The ship was noted for its high speed and multiple anti- | + | |The ship was noted for its high speed and multiple anti-warship armaments. |
|- | |- | ||
|''[[Intruder]]'' | |''[[Intruder]]'' | ||
| Line 305: | Line 298: | ||
|[[2656]] | |[[2656]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Heavily armed assault transport (2 Fighters, 4 platoons). | |Heavily armed assault transport (2 Fighters, 4 platoons). | ||
|- | |- | ||
| Line 312: | Line 305: | ||
|[[2343]] | |[[2343]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
| − | |Based on a [[Terran Hegemony]] design introduced in the early | + | |Based on a [[Terran Hegemony]] design introduced in the early 25th century and the first bulk-cargo DropShips; eventually replaced as a class by the [[Mule]]. |
|- | |- | ||
|[[K-1 DropShuttle]] | |[[K-1 DropShuttle]] | ||
| Line 319: | Line 312: | ||
|[[2536]] | |[[2536]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Passenger/cargo shuttle. Usually classed as a [[Small Craft]], not a DropShip. Clan version known as [[K-1_DropShuttle#Variants|K1-C]] is identical except for better armor and upgraded (though similar) weaponry. | |Passenger/cargo shuttle. Usually classed as a [[Small Craft]], not a DropShip. Clan version known as [[K-1_DropShuttle#Variants|K1-C]] is identical except for better armor and upgraded (though similar) weaponry. | ||
|- | |- | ||
| Line 326: | Line 319: | ||
|[[3054]] | |[[3054]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Designated patrol/assault craft. | |Designated patrol/assault craft. | ||
|- | |- | ||
| Line 348: | Line 341: | ||
|military | |military | ||
|[[DropShip#Aerodyne_DropShips|aerodyne]] | |[[DropShip#Aerodyne_DropShips|aerodyne]] | ||
| − | |Standard BattleMech transport (4 'Mechs, 2 Fighters) since Star League era. | + | |Standard BattleMech transport (4 'Mechs, 2 Fighters) since Star League era. Affectionally referred to as the "Brick". 1,800 ton upgraded version launched in [[3056]]. |
|- | |- | ||
|''[[Leopard CV]]'' | |''[[Leopard CV]]'' | ||
| Line 375: | Line 368: | ||
|[[2808]] | |[[2808]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Cargo carrier. Largest DropShip capable of planetary operations. | |Cargo carrier. Largest DropShip capable of planetary operations. | ||
|- | |- | ||
| Line 382: | Line 375: | ||
|[[2449]] | |[[2449]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|First 'Mech carrier ever (4 'Mechs), designed off a freighter design of the same name. Predecessor of the [[Confederate]] class. Flawed design, discontinued soon after introduction for inadequate armor and weapons. | |First 'Mech carrier ever (4 'Mechs), designed off a freighter design of the same name. Predecessor of the [[Confederate]] class. Flawed design, discontinued soon after introduction for inadequate armor and weapons. | ||
|- | |- | ||
| − | |''[[ | + | |''[[Mercer]]'' |
|4,500 | |4,500 | ||
|[[3065]] | |[[3065]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Heavily armed and armored assault transport (10 'Mechs). | |Heavily armed and armored assault transport (10 'Mechs). | ||
|- | |- | ||
| Line 396: | Line 389: | ||
|[[3063]] | |[[3063]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Assault DropShip (2 Fighters). | |Assault DropShip (2 Fighters). | ||
|- | |- | ||
| − | |''[[ | + | |''[[Miraborg]]'' |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|9,750 | |9,750 | ||
|[[3053]] | |[[3053]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Fighter carrier (30 Fighters). Originally named "Charybdis" during its design phase, the class was renamed in memory of [[Tyra Miraborg]] shortly before the launch of the first ship. | |Fighter carrier (30 Fighters). Originally named "Charybdis" during its design phase, the class was renamed in memory of [[Tyra Miraborg]] shortly before the launch of the first ship. | ||
|- | |- | ||
| Line 417: | Line 403: | ||
|[[2652]] | |[[2652]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Star League predecessor to the [[Model 97]] tug which was described as a refit of the Model 96 class. | |Star League predecessor to the [[Model 97]] tug which was described as a refit of the Model 96 class. | ||
|- | |- | ||
| Line 424: | Line 410: | ||
|[[3051]] | |[[3051]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Designated tug/rescue ship. | |Designated tug/rescue ship. | ||
|- | |- | ||
| Line 431: | Line 417: | ||
|[[2759]] | |[[2759]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Standard passenger liner. | |Standard passenger liner. | ||
|- | |- | ||
| Line 445: | Line 431: | ||
|[[3056]] | |[[3056]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Heavily armed troop transport (12 platoons). | |Heavily armed troop transport (12 platoons). | ||
|- | |- | ||
| Line 452: | Line 438: | ||
|[[3065]] | |[[3065]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Powerful assault DropShip (6 fighters, 9 [[small craft]], 27 battle armor squads), also provided to [[Clan Nova Cat]]. Ship carries a limited quantity of [[Teleoperated Capital Missile|teleoperated capital missiles]]. | |Powerful assault DropShip (6 fighters, 9 [[small craft]], 27 battle armor squads), also provided to [[Clan Nova Cat]]. Ship carries a limited quantity of [[Teleoperated Capital Missile|teleoperated capital missiles]]. | ||
|- | |- | ||
| − | |''[[ | + | |''[[Noruff]]'' |
|1,900 | |1,900 | ||
|[[3056]] | |[[3056]] | ||
| Line 462: | Line 448: | ||
|Designated assault craft. Only one prototype known to exist by [[3057]]. | |Designated assault craft. Only one prototype known to exist by [[3057]]. | ||
|- | |- | ||
| − | |''[[ | + | |''[[Okinawa]]'' |
|4,500 | |4,500 | ||
|[[3055]] | |[[3055]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Fighter carrier (18 Fighters). | |Fighter carrier (18 Fighters). | ||
|- | |- | ||
| Line 473: | Line 459: | ||
|[[3063]] | |[[3063]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
| − | |Combined arms transport (5 'Mechs, 4 Fighters, 10 tanks, 1 elemental | + | |Combined arms transport (5 'Mechs, 4 Fighters, 10 tanks, 1 elemental star) developed from venerable Fortress class. |
|- | |- | ||
|''[[Overlord]]'' | |''[[Overlord]]'' | ||
| Line 480: | Line 466: | ||
|[[2762]] | |[[2762]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Common BattleMech transport (36 'Mechs, 6 Fighters). | |Common BattleMech transport (36 'Mechs, 6 Fighters). | ||
|- | |- | ||
| Line 487: | Line 473: | ||
|[[2818]] | |[[2818]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Fighter transport (45 'Mechs). Clan redesign of the classic [[Overlord]] class. | |Fighter transport (45 'Mechs). Clan redesign of the classic [[Overlord]] class. | ||
|- | |- | ||
| Line 494: | Line 480: | ||
|[[2623]] | |[[2623]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Star League era DropShip class designed as "little more than large gun platforms" for WarShip escort. | |Star League era DropShip class designed as "little more than large gun platforms" for WarShip escort. | ||
|- | |- | ||
| Line 501: | Line 487: | ||
|[[2657]] | |[[2657]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|The design was known for its luxurious amenities. | |The design was known for its luxurious amenities. | ||
|- | |- | ||
| − | |''[[ | + | |''[[Rose]]'' |
|16,000 | |16,000 | ||
|[[3054]] | |[[3054]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Heavily armed freighter with advanced avionics, designed to have an inconspicuous appearance. Can carry 1 platoon of infantry and 4 [[Small Craft]]. | |Heavily armed freighter with advanced avionics, designed to have an inconspicuous appearance. Can carry 1 platoon of infantry and 4 [[Small Craft]]. | ||
|- | |- | ||
| Line 515: | Line 501: | ||
|[[2875]] | |[[2875]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Clan battle armor carrier (15 Elemental Points). Based off the ''[[Intruder]]'' design. | |Clan battle armor carrier (15 Elemental Points). Based off the ''[[Intruder]]'' design. | ||
|- | |- | ||
| − | |''[[ | + | |''[[Saturn_(DropShuttle_class)|Saturn]] '' |
| − | |1,200 | + | |1,200 |
| − | |[[2243]] | + | |[[2243]] |
| − | |military | + | |military |
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Used by the Terran Alliance as colonial patrol ship. It is one oldest known DropShip designs used for military purposes. | |Used by the Terran Alliance as colonial patrol ship. It is one oldest known DropShip designs used for military purposes. | ||
| − | |- | + | |- |
|''[[Seeker]]'' | |''[[Seeker]]'' | ||
|6,700 | |6,700 | ||
|[[2815]] | |[[2815]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Troop transport (64 light vehicles, 4 platoons). | |Troop transport (64 light vehicles, 4 platoons). | ||
|- | |- | ||
| Line 536: | Line 522: | ||
|[[3100]] | |[[3100]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
| − | |Early | + | |Early 32nd Century troop/tank transport (20 battle armor squads & 12 light vehicles) utilized by the Free World League. |
|- | |- | ||
| − | |''[[ | + | |''[[Titan_(DropShip_class)|Titan]]'' |
|12,000 | |12,000 | ||
|[[2647]] | |[[2647]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Heavily armed fighter carrier (18 Fighters). Extinct in the [[Inner Sphere]] powers, but still in use with the Clans. | |Heavily armed fighter carrier (18 Fighters). Extinct in the [[Inner Sphere]] powers, but still in use with the Clans. | ||
|- | |- | ||
| Line 550: | Line 536: | ||
|[[2593]] | |[[2593]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Common troop/tank transport (45 heavy vehicles, 8 light vehicles, 4 platoons). Upgraded version launched in [[3057]]. | |Common troop/tank transport (45 heavy vehicles, 8 light vehicles, 4 platoons). Upgraded version launched in [[3057]]. | ||
|- | |- | ||
| Line 557: | Line 543: | ||
|[[2720]] | |[[2720]] | ||
|civilian | |civilian | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
| − | |"Blockade runner" version of the ubiquitous unarmed [[ | + | |"Blockade runner" version of the ubiquitous unarmed [[Danais]] class merchant, introduced by the [[Taurian Concordat]]. Features 2 [[Small Craft]] bays and weapons which are typically concealed to appear like a common Danais class vessel. |
|- | |- | ||
|''[[Trutzburg]]'' | |''[[Trutzburg]]'' | ||
| − | |6,000 | + | |6,000 |
| − | |[[3112]] | + | |[[3112]] |
| − | |military | + | |military |
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
| − | |A | + | |A Combined Arms transport ship, one few made in Lyran Commonwealth in the 32nd Century. (6 fighters, 12 BattleMechs, 4 battle armor Squads) |
| − | |- | + | |- |
|''[[Union]]'' | |''[[Union]]'' | ||
|3,500 | |3,500 | ||
|[[2708]] | |[[2708]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|Standard BattleMech transport (12 'Mechs, 2 Fighters). Iconic DropShip class. | |Standard BattleMech transport (12 'Mechs, 2 Fighters). Iconic DropShip class. | ||
|- | |- | ||
| Line 578: | Line 564: | ||
|[[2829]] | |[[2829]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|'Mech transport (15 'Mechs). Clan redesign of the venerable [[Union]] class. | |'Mech transport (15 'Mechs). Clan redesign of the venerable [[Union]] class. | ||
|- | |- | ||
| Line 585: | Line 571: | ||
|[[2715]] | |[[2715]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
|Tiny, superfast infantry transport from the Star League era. The design became extinct during the [[Succession Wars (History)|Succession Wars]]. | |Tiny, superfast infantry transport from the Star League era. The design became extinct during the [[Succession Wars (History)|Succession Wars]]. | ||
|- | |- | ||
| − | |''[[ | + | |''[[Vengeance]]'' |
|10,000 | |10,000 | ||
|[[2682]] | |[[2682]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Aerodyne_DropShips|aerodyne]] |
| − | |Fighter carrier (40 [[ | + | |Fighter carrier (40 [[fighters]], 3 [[small craft]]). |
|- | |- | ||
| − | |''[[ | + | |''[[Vulture_(DropShip_class)|Vulture]]'' |
|3,500 | |3,500 | ||
|[[2312]] | |[[2312]] | ||
|military | |military | ||
| − | |[[DropShip# | + | |[[DropShip#Spheroid_DropShips|spheroid]] |
|These ships carried infantry and a limited number of light vehicles it main payload. They were known to be similar to what became the [[Seeker]] class that was based on the Vulture. | |These ships carried infantry and a limited number of light vehicles it main payload. They were known to be similar to what became the [[Seeker]] class that was based on the Vulture. | ||
|- | |- | ||
| Line 619: | Line 605: | ||
==Bibliography== | ==Bibliography== | ||
<div class="desktop-3-col"> | <div class="desktop-3-col"> | ||
| − | * ''[[AeroTech]]'' | + | *''[[AeroTech]]'' |
| − | * ''[[AeroTech 2]]'' | + | *''[[AeroTech 2]]'' |
| − | * ''[[AeroTech 2 | + | *''[[AeroTech 2 Revised Edition|Aerotech 2 Revised]]'' |
| − | * ''[[AeroTech 2 | + | *''[[AeroTech 2 Record Sheets]]'' |
| − | * ''[[BattleSpace]]'' | + | *''[[BattleSpace]]'' |
| − | * ''[[Strategic Operations]]'' | + | *''[[Strategic Operations]]'' |
| − | * ''[[Technical Readout: 3025]]'' | + | *''[[Technical Readout: 3025]]'' |
| − | * ''[[Technical Readout: 3026 Revised]]'' | + | *''[[Technical Readout: 3026 Revised]]'' |
| − | * ''[[Technical Readout: 3057]]'' | + | *''[[Technical Readout: 3057]]'' |
| − | * ''[[Technical Readout: 3057 Revised]]'' | + | *''[[Technical Readout: 3057 Revised]]'' |
| − | * ''[[Technical Readout: 3067]]'' | + | *''[[Technical Readout: 3067]]'' |
| − | * ''[[Technical Readout: 3075]]'' | + | *''[[Technical Readout: 3075]]'' |
| − | * ''[[Total Warfare]]'' | + | *''[[Total Warfare]]'' |
</div> | </div> | ||