Editing Caerleon

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:
 +
 
{{InfoBoxSmallCraft
 
{{InfoBoxSmallCraft
 
| image = [[File:Caerleon.jpg|191px]]
 
| image = [[File:Caerleon.jpg|191px]]
Line 30: Line 31:
  
 
==Description==
 
==Description==
Introduced in 3093, the '''Caerleon''' soon spread across the states and worlds of the former [[Free Worlds League]] and into the general mercenary market. Designed as a battle armor transport capable of carrying a complete platoon, the Caerleon was named for an ancient fortress associated with the legendary figure known as King Arthur. With more than twenty tons of ferro-aluminum armor, the Caerleon closely resembled a fortress in the eyes of the infantry it was transporting.<ref name="TRO:3145FWLp48+"/>
+
Introduced in 3093, the Caerleon soon spread across the states and worlds of the former [[Free Worlds League]] and into the general mercenary market. Designed as a battle armor transport capable of carrying a complete platoon, the Caerleon was named for an ancient fortress associated with the legendary figure known as King Arthur. With more than twenty tons of ferro-aluminum armor, the Caerleon closely resembled a fortress in the eyes of the infantry it was transporting.<ref name="TRO:3145FWLp48+"/>
  
 
Critics of the Caerleon argued that it needed either a larger engine or greater firepower to meet the requirements of being a boarding craft or an assault craft, but Nimakachi steadfastly ignored such criticisms and continued to produce the Caerleon in its original pattern with the full approval of the troopers who relied on it. Whatever the critics' views on the size of the engine in the Caerleon or its firepower, the Caerleon's handling problems in atmosphere were well-documented, and the cause of a number of combat losses.<ref name="TRO:3145FWLp48+"/>
 
Critics of the Caerleon argued that it needed either a larger engine or greater firepower to meet the requirements of being a boarding craft or an assault craft, but Nimakachi steadfastly ignored such criticisms and continued to produce the Caerleon in its original pattern with the full approval of the troopers who relied on it. Whatever the critics' views on the size of the engine in the Caerleon or its firepower, the Caerleon's handling problems in atmosphere were well-documented, and the cause of a number of combat losses.<ref name="TRO:3145FWLp48+"/>
Line 41: Line 42:
 
* Bay 1: Battle Armor compartment (20 tons), 1 Door
 
* Bay 1: Battle Armor compartment (20 tons), 1 Door
 
* Bay 2: Cargo (4.5 tons), 1 Door
 
* Bay 2: Cargo (4.5 tons), 1 Door
 +
 +
==Notes==
 +
All crew quarters aboard a Caerleon were Steerage-class.<ref name="TRO:3145FWLp48+"/>
  
 
==Design Quirks==
 
==Design Quirks==
Line 47: Line 51:
 
* [[Easy to Maintain]]
 
* [[Easy to Maintain]]
 
* [[Fast Reload]]
 
* [[Fast Reload]]
 
==Notes==
 
All crew quarters aboard a Caerleon were Steerage-class.<ref name="TRO:3145FWLp48+"/>
 
  
 
==References==
 
==References==

Please note that all contributions to BattleTechWiki are considered to be released under the GNU FDL 1.2 (see BattleTechWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Advanced templates:

Editing: {{Merge}}   {{Moratorium}}   {{Otheruses| | | }}

Notices: {{NoEdit}}   {{Sign}}   {{Unsigned|name}}   {{Welcome}}

Administration: {{Essay}}   {{Policy}}   {{Procedure}}

Template used on this page: