TEXT: SAN ANTONIO CLASS FRIGATE
  Troop / Vehicle Transport – Commissioned, 2368
  FEDERATION
  HULL DATA
  Structure
  40
  Size / Decks
  7 / 21
  Length / Height / Beam
  501 / 93 / 327
  Compliment
  400 (up to 1000 troops)
  PROPULSION DATA
  Impulse System
  FIG-5 (.92c / D)
  Warp System
  LF-35 (6 / 9.2 / 9.8) (D)
  OPERATIONAL DATA
  Atmosphere Capable
  YES
  Transporters
  4 standard, 4 emergency
  Cargo Units
  50
  Shuttlebay
  2a, 1 hangar deck
  Shuttlecraft
  14 size worth (+20 / hangar deck)
  Tractor Beams
  1ad, 1fd
  Separation System
  NONE
  Cloaking Device
  NONE
  Sensor System
  Class-3 (+3 / D)
  Operations System
  Class-2 (C)
  Life Support
  Class-3 (D)
  TACTICAL DATA
  Phaser Arrays
  Type-X (x3 / D)
  Penetration
  4 / 3 / 3 / 0 / 0
  Torpedoes
  Mk80 (x4 / D)
  Penetration
  4 / 4 / 4 / 4 / 4
  Deflector Shield
  FSQ-7 (CC)
  Protection / Threshold
  17 / 4
  MISCELLANEOUS DATA
  Maneuver Modifiers
  +1 C, +2 H, +2 T
  Traits
  None
  STAR TREK ROLE PLAYING GAME
  
  MISSIONS
  The San Antonio class "Frigate" is an atmospheric-capable starship that embarks, transports, and lands elements of a landing 
  force for expeditionary missions. Several different, space-faring cultures currently operate this kind of ship, including the Klingons, 
  Romulans, and prior to the Dominion War, the Cardassians. The ships are generally designed to transport troops into a war zone 
  onto a planet's surface, primarily using landing craft, although invariably they also have the capability to land and disembark their 
  personnel directly.
  San Antonio class ships can carry a compliment of troops, up to 1000 strong; as well as a hangar deck carrying up to 2 squadrons 
  of fighters (24 in total), or the equivalent size and payload in runabouts, other shuttle-type craft (such as the Delta Flyer class), as 
  well as vehicles designed for use on a planet's surface, on land, or in the water. 
  FEATURES
  The most striking feature of the San Antonio class is the huge hangar-deck that occupies the equivalent of 3 decks worth of space 
  in the upper section of the vessel's primary hull. This hangar deck is capable of housing, and launching up to two dozen 
  starfighters, and is also a fully functional transport and maintenance deck for moving vehicles such as shuttlecraft and runabouts 
  into a combat-zone, or into a search-and-rescue mission area.
  Similar in design to the Akira class; the San Antonio class is designed on a wider spaceframe, with longer nacelles attached to the 
  main hull by two sets of extending pylons. The more forward pylons, which are attached very close to the saucer section of the 
  ship has been debated as a possible design flaw by placing the warp-nacelles too close to a heavily occupied section of the 
  vessel.
  However, since the San Antonio class has been in service this design has not proven to cause any problems with ship's function, 
  nor the safety or well-being of the people serving aboard San Antonio class ships. Designed for atmospheric flight; the San Antonio 
  class is a very maneuverable ship, especially in space. And most flight control officers serving aboard a San Antonio find it easy to 
  control the ship, even in tight evasive maneuvers, do to the trim body design.
  BACKGROUND
  Development of the San Antonio class began during the Federation / Cardassian war, but the design was shelved when the 
  Galaxy class came across the drawing board. And eventually the original San Antonio class designs were paired down into the 
  sleeker, and more powerful Akira class. The San Antonio class was put into production about the same time as the Akira class, and 
  more ships were actually ordered of this design than of the Akira.
  It was presumed that if a Romulan, or possibly a Borg invasion were to take place there would be a need for a ship capable of 
  moving troops and weapons into position quickly, and in bulk. Thus the San Antonio featured the same warp and impulse engine 
  designs as the Akira, but to make room for troops and vehicles several of the San Antonio's systems were scaled back – weapons 
  were given the standard specs, while sensors, operations, and life support were all scaled back. Shielding remained consistent 
  with the Akira design specifications. Bulk cargo-space was drastically reduced.
  The first San Antonio class ship was commissioned in 2368. And the ship has seen service in the Dominion War (especially during 
  the liberation of Betazed), and continues to be a valued part of Starfleet's more military compliment of starships that include the 
  Akira, Defiant, and Saber classes.
  SHIPS IN SERVICE
  NAME
  REGISTRY
  NOTES
  San Antonio
  NCC-62539
  Class ship. Destroyed, in 2378, in a skirmish with the Borg
  New Berlin
  NCC-62931
  In service, on assignment along the Klingon / Federation border
  Mesa Verde
  NCC-62566
  Participated in the Liberation of Betazed. Heavily damaged.
  ShiKar
  NCC-62887
  Commanded by Captain Torvek.  Named for the Capitol City on Vulcan.
  Khitomer
  NCC-63132
  Named for the Klingon world, site of the Khitomer massacre (2346).
  Manhattan
  NCC-62854
  Destroyed in 2375, during the Dominion War, in battle with Breen forces.
  San Diego
  NCC-63381
  Active duty. Assigned as an emergency rescue and evac transport for the Bajoran sector.
  Anchorage
  NCC-63516
  Destroyed, 2386, by a Gelshmorian raider, while protecting a Tellarite colony.
  Dallas
  NCC-63104
  Commanded by Captain Richard Albright. Active duty, out of Starbase 234.
  La Barre
  NCC-63559
  Named for the birthplace of Captain Jean-Luc Picard. Commanded by Captain Tedric Faldo.
  Davenport
  NCC-63577
  Active duty, on search-and-rescue duty, with a home-base at Starbase Earhart.
  
SOURCE: textdata/thevault/Star Trek RPG/Decipher/Ships/Starfleet_San-Antonio.pdf