Home Random Page


CATEGORIES:

BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism






TYPE-10 PERSONNEL SHUTTLE

Type: Heavy long-range warp shuttle.
Accommodation: Two flight crew, two passengers.
Power Plant: One 250 cochrane warp engine, two 800 millicochrane impulse engines, four RCS thrusters.
Dimensions: Length, 9.64 m; beam, 5.82 m; height 3.35 m.
Mass: 19.73 metric tones.
Performance:Warp 5.
Armament: Three Type-V phaser emitters, two micro-torpedo launchers, jamming devices.

Developed specifically for the Defiant-class starship project, the Type-10 Personnel Shuttle is the largest departure from the traditional role of an auxiliary craft that Starfleet has made in the past century. Short of a dedicated fighter craft, the Type-10 is one of the most powerful auxiliary ships, with only the bulkier Type-11 being more heavily equipped. Nonetheless, the shuttle sports increased hull armor and the addition of micro-torpedo launchers, as well as a suite of tactical jamming devices. A larger warp coil assembly, as well as torpedo stores, makes the Type-10 much more heavier then other shuttles. Elements from the Defiant-class project that were incorporated into the shuttle include armored bussard collectors, as well as a complex plasma venting system for use during possible warp core breech situations. This bulky craft is equipped with a powerful navigation deflector that allows it to travel at high-warp, and a complex sensor system makes this shuttle suitable for reconnaissance work. Able to hold its own in battle situations, the Type-10 is seeing limited deployment on Defiant-class starships, as well as border patrol vessels and combat-ready ships.

 

WORK BEE

Type: Utility craft.
Accommodation: One operator.
Power Plant: One microfusion reactor, four RCS thrusters.
Dimensions: Length, 4.11 m; beam, 1.92 m; height 1.90 m.
Mass: 1.68 metric tones.
Performance:Maximum delta-v, 4,000 m/sec.
Armament: None

The Work Bee is a capable stand-alone craft used for inspection of spaceborne hardware, repairs, assembly, and other activates requiring remote manipulators. The fully pressurized craft has changed little in design during the past 150 years, although periodic updates to the internal systems are done routinely. Onboard fuel cells and microfusion generators can keep the craft operational for 76.4 hours, and the life-support systems can provide breathable air, drinking water and cooling for the pilot for as long as fifteen hours. If the pilot is wearing a pressure suit or SEWG, the craft allows for the operator to exit while conducting operations. Entrance and exit is provided by the forward window, which lifts vertically to allow the pilot to come and go.

A pair of robotic manipulator arms is folded beneath the main housing, and allows for work to be done through pilot-operated controls. In addition, the Work Bee is capable of handling a cargo attachment that makes it ideal for transferring cargo around large Starbase and spaceborne construction facilities. The cargo attachment features additional microfusion engines for supporting the increased mass.



 

10.0 SABER CLASS FLIGHT OPERATIONS

Operations aboard a Saber class starship fall under one of four categories: flight operations, primary mission operations, secondary mission operations, and flight deck operations.

Flight Operations are all operations that relate directly to the function of the starship itself, which include power generation, starship upkeep, environmental systems, and any other system that is maintained and used to keep the vessel space worthy.

Primary Mission Operations entail all tasks assigned and directed from the Main Bridge, and typically require full control and discretion over ship navigation and ship's resources.

Secondary Mission operations are those operations that are not under the direct control of the Main Bridge, but do not impact Primary Mission Operations. Some examples of secondary mission operations include long-range cultural, diplomatic or scientific programs run by independent or semi-autonomous groups aboard the starship.

Flight Deck Operations are those operations that typically fall under Secondary Mission operations, but fall under the control of the Tactical Information Center. It is not uncommon for Flight Deck Operations to supercede Primary Mission Operations, particularly in combat missions.

 

10.1 MISSION TYPES

Saber-class ships are classified as mission-oriented vessels. While it can be used for any mission that is necessary, to be absolutely efficient in achieving its goals, a Saber should be of the proper variant for the mission assigned to it.

Saber-class vessels make use of modular technology, just as do most other Starfleet vessels. But, due to the compact, intertwined nature of the ship's systems, when a Saber has a change in its mission parameters, it requires a significant change-out time (typically weeks to months) to adapt to a new variant. Each Saber falls into one of four types of variant and focuses on those mission for which that types was built.

The following is a list of mission types and the variants that typically are assigned to them:

  • Federation Policy and Diplomacy:The FF/FFU -D is a Diplomatic Courier. Its main mission is transportation of diplomatic personnel to various destinations, to provide diplomatic facilities for low level conferences, summits, and treaty discussions, and to transport vital cargo of a political nature. It has decreased scientific and weapon capacities, to allow for addition VIP quarters, conference rooms, meeting halls, private offices, secured communication equipment, and increased entertainment facilities.
  • Deep-space Exploration / Contact with Alien Lifeforms: The FF/FFU -E is a Scout ship. It is the variant described in the previous documentation, with a mission of exploration, observation/data gathering, first-contact, scientific and patrol type missions.
  • Ongoing Scientific Investigation:TheFF/FFU -S is a Science ship. The main purpose of this vessel is to act as a base of operations for the gathering of scientific data. This variant has decreased weapon load-outs, and next to no diplomatic facilities, to allow room for increased science labs, probes, and mission specific experiments/equipment.
  • Tactical/Defensive Operations:TheFF/FFU -P is a Patrol ship, with the main purpose of guarding borders and patrolling shipping lanes. It has decreased scientific and diplomatic facilities to allow room for increased torpedo storage, additional security personnel, additional shield generators, and improved tactical sensors and communication equipment.
  • Emergency/Search and Rescue: Any variant can be called in to aid in an emergency. Typical Missions include answering standard Federation emergency beacons, extraction of Federation or Non-Federation citizens in distress, retrieval of Federation or Non-Federation spacecraft in distress, small scale station/outpost evacuation - planetary evacuation is not feasible.

 

10.2 OPERATING MODES

The normal flight and mission operations of the Saber class starship are conducted in accordance with a variety of Starfleet standard operating rules, determined by the current operational state of the starship. These operational states are determined by the Commanding Officer, although in certain specific cases, the Computer can automatically adjust to a higher alert status.

The major operating modes are:

  • Cruise Mode: The normal operating condition of the ship.
  • Yellow Alert: Designates a ship wide state of increased preparedness for possible crisis situations.
  • Red Alert: Designates an actual state of emergency in which the ship or crew is endangered, immediately impending emergencies, or combat situations.
  • External Support Mode: State of reduced activity that exists when a ship is docked at a starbase or other support facility.
  • Reduced Power Mode: this protocol is invoked in case of a major failure in spacecraft power generation, in case of critical fuel shortage, or in the event that a tactical situation requires severe curtailment of onboard power generation.

During Cruise Mode, the ship's operations are run on three 8-hour shifts designated Alpha, Beta, and Gamma. Should a crisis develop, it may revert to a four-shift system of six hours to keep crew fatigue down.

Typical Shift command is as follows:

  1. Alpha Shift: Captain (CO)
  2. Beta Shift: Executive Officer (XO)
  3. Gamma Shift: Second Officer

 

10.3 SEPARATED FLIGHT MODE

Due to the unique shape of her hull, the Saber class does not have a separated flight mode. While the hull can eject the warp nacelle assembly quickly, her lack of a clearly identifiable saucer section precludes independent flight of the primary hull.

 

10.4 LANDING MODE

Due to the unique shape of her hull, the Saber class cannot land within a gravity well and maintain hull integrity for Transatmospheric operations. This does not mean that the hull cannot withstand a landing - quite the contrary, in an extreme emergency, the Saber class could effect a surface landing while only losing an estimated 45% of hull integrity while structural members are estimated to have failure rates as high as 75%. While integrity is not high enough to allow for deep-space operations, enough of the internal volume and structural members should remain to allow for a landing that is safe for her crew.

 

10.5 MAINTENANCE

Though much of a modern starship's systems are automated, they do require regular maintenance and upgrade. Maintenance is typically the purview of the Engineering, but personnel from certain divisions that are more familiar with them can also maintain specific systems.

Maintenance of onboard systems is almost constant, and varies in severity. Everything from fixing a stubborn replicator, to realigning the Dilithium matrix is handled by technicians and engineers on a regular basis. Not all systems are checked centrally by Main Engineering; to do so would occupy too much computer time by routing every single process to one location. To alleviate that, systems are compartmentalized by deck and location for checking. Department heads are expected to run regular diagnostics of their own equipment and report anomalies to Engineering to be fixed.

Systems Diagnostics
All key operating systems and subsystems aboard the ship have a number of preprogrammed diagnostic software and procedures for use when actual or potential malfunctions are experienced. These various diagnostic protocols are generally classified into five different levels, each offering a different degree of crew verification of automated tests. Which type of diagnostic is used in a given situation will generally depend upon the criticality of a situation, and upon the amount of time available for the test procedures.

Level 1 Diagnostic -This refers to the most comprehensive type of system diagnostic, which is normally conducted on ship's systems. Extensive automated diagnostic routines are performed, but a Level 1 diagnostic requires a team of crew members to physically verify operation of system mechanisms and to system readings, rather than depending on the automated programs, thereby guarding against possible malfunctions in self-testing hardware and software. Level 1 diagnostics on major systems can take several hours, and in many cases, the subject system must be taken off-line for all tests to be performed.

Level 2 Diagnostic -This refers to a comprehensive system diagnostic protocol, which, like a Level 1, involves extensive automated routines, but requires crew verification of fewer operational elements. This yields a somewhat less reliable system analysis, but is a procedure that can be conducted in less than half the time of the more complex tests.

Level 3 Diagnostic -This protocol is similar to Level 1 and 2 diagnostics but involves crew verification of only key mechanics and systems readings. Level 3 diagnostics are intended to be performed in ten minutes or less.

Level 4 Diagnostic -This automated procedure is intended for use whenever trouble is suspected with a given system. This protocol is similar to Level 5, but involves more sophisticated batteries of automated diagnostics. For most systems, Level 4 diagnostics can be performed in less than 30 seconds.

Level 5 Diagnostic -This automated procedure is intended for routine use to verify system performance. Level 5 diagnostics, which usually require less than 2.5 seconds, are typically performed on most systems on at least a daily basis, and are also performed during crisis situations when time and system resources are carefully managed.

 

11.0 EMERGENCY OPERATIONS


Date: 2015-12-11; view: 237


<== previous page | next page ==>
NAVIGATION DEFLECTOR | EMERGENCY MEDICAL OPERATIONS
doclecture.net - lectures - 2014-2017 year. Copyright infringement or personal data (0.006 sec.)