The original version of this vessel, pre-Starships, can be found here for purposes of comparison, for those interested in such things.
King’s Protector-class Heavy Escort
Production Data
Origin: United Federation of Planets
Class and Type: King’s Protector-class Heavy Escort
Year Launched: 2285
Hull Data
Structure: 25
Size/Decks: 4/4 decks
Length/Height/Beam: 148/20/70 meters
Complement: 43
Operational Data
Atmosphere Capable: No
Transporters: 2 standard, 2 emergency, 2 cargo
Cargo Units: 40
Shuttlebay: No
Shuttlecraft: None
Tractor Beams: 1 AV
Separation System: No
Sensor System: Class 2a (+2/BB)
Operations System: Class 2R (CC)
Life Support: Class 2 (C)
Propulsion Data
Impulse System: RSV (.7c) (D)
Warp System: PB-32 Mod 3 (Warp 6/7/8) (D)
Tactical Data
Phaser Banks: Type VII (x2/B)
Penetration: 4/3/3/0/0
Deflector Shield: CIDSS-2 (C)
Protection/Threshold: 14/3
Miscellaneous Data
Maneuver Modifers: +1 C, +1 H, +2 T
Traits: Nimble
Description/History: With the expansion of the frontier in the mid- to late-23rd century, the need for a fast, sturdy, and relatively inexpensive escort vessel became more prominent. The King’s Protector class arose from that need. While capable of independent operation for short periods of time, they are usually deployed in packs of 3 to 5 vessels. Their primary missions, alone or in battle groups, have been border/system patrol duty and escorting colony ships and cargo carriers. In addition, some have also found themselves part of space station defense squadrons, especially if the station occupies a strategic area of space. These squadrons are typically 8 to 12 vessels in size.
The design was first approved in 2281, but there were a number of delays, as well as some design changes, en route to the launch of the King’s Protector in 2285. One of the side effects of these delays was the ability of the design and construction team to upgrade the ship’s deflector system to the slightly larger, but more powerful and reliable, CIDSS-2 system instead of the original design’s PFF 3 system.
Early design specs called for a photon torpedo system, but after some analysis it was decided that a sufficiently powerful system couldn’t be installed because of space limitations. The ship’s mission depended more on large numbers and high maneuverability than individual firepower, so attention was instead turned towards improving guidance and drive systems. Its more-than-ample RSV impulse drive system makes the ship remarkably quick and nimble at sublight speeds. It is also somewhat faster at warp than many other ships of its class, a fact that has caught more than one raider by surprise. Over the course of its short service life so far, the King’s Protector-class has proven to be a remarkably tough ship for its size.
Named for noted Federation and Starfleet security chiefs and others famed for protecting those under their care, there are currently 61 King’s Protector-class escorts in service, with another 80 in various stages of production in different shipyards. There have been 4 lost in the line of duty to date.
Notable Ships in Service
* U.S.S. Alexander Pitt (NCC-7594) - Security chief of U.S.S. Endeavour. Sacrificed his own life to save the lives of his crewmates after a Klingon ambush in 2291.
* U.S.S. Aramis (NCC-7534)
* U.S.S. Athos (NCC-7532)
* U.S.S. Carmen De Falco (NCC-7566) - Security chief of U.S.S. Constitution under Garth of Izar. Killed in action during the Axanar Rebellion.
* U.S.S. D’Artagnan (NCC-7535)
* U.S.S. David Blanchard (NCC-7587)
* U.S.S. Donald Mappin (NCC-7567)
* U.S.S. King’s Protector (NCC-7531) - Lead ship of the line. Named for its designed task by an architect with poetic sensibilities.
* U.S.S. Louis Firetti (NCC-7542)
* U.S.S. Patrick Riley (NCC-7568)
* U.S.S. Porthos (NCC-7533)
* U.S.S. Sea Tyger (NCC-7590) - Bodyguard for Federation President Isaac Long from 2253-2258. A Regulan, he foiled three separate assassination attempts before retiring and seeking, as he put it, "less strenuous employment."
EDIT: Revised a couple of registry numbers to better fit my campaign's timeline.
Reply With Quote
I never knew he had such an important role in Federation history... 
