Squadron Organization and Regulations Manual

Squadron Organization and Regulations Manual (SORM) Page 1 Introduction Congratulations on your assignment to a fighter squadron of the Star Fleet. This assignment is an indication of Fleet's confidence in your skills and potential. By joining a fighter squadron, you become part of a proud tradition which extends back, not merely to the formation of your squadron, nor to the beginning of the Mako Project, nor yet even to the founding of the Star Fleet, but to the day when one member of your species first took up arms in the defense of another. Today, fighter pilots put themselves in the way of danger, protecting the citizens of the United Federation of Planets just as their predecessors have done for generations. It should by no means be imagined, however, that only the pilots are vital to the success of a squadron's mission. Without a staff full of mechanics, technicians, logistics specialists, intelligence analysts, stellar cartographers, mission planners, yeomen and mess specialists, the fighters could not fly, the pilots could not perform at peak efficiency. There are no insignificant jobs in a fighter squadron. Whoever you are, whatever your job, you have demonstrated your excellence. Now, we of the squadron are counting on you to continue that excellence, so that together we can fulfil the awesome responsibility we have -- to go in harm's way. CDR S'task FSCO, VF-11 Star Fleet Training Command, Fighter Division History The history of starfleet's fighter project, and ultimately of all fightercraft the Federation may yet use in the Star Fleet, can be traced to the Khitomer Accords of November 2291. With the Klingon Empire dealing with internal problems, and the Romulan Star Empire soon to withdraw all contact, the Federation and the Star Fleet were left without a perceptible major threat to peace. During the seventy-three years between the Khitomer Accords and the reemergence of the Romulan Star Empire, the Star Fleet underwent a major drawdown of its combat forces. Instead of defense, Starships were optimized for exploration. Then, within a year after the initial contact between USS Berlin and seven Romulan warships, USS Enterprise encountered the Borg. Suddenly, the Federation faced a need for combat vessels. Several projects were considered, to fill the need. Before any of them could be implemented, the Borg invaded, and the cataclysmic battle of Wolf 359 ensued. This was to be a harbinger of things to come. In short order, the United Federation of Planets faced wars with the Borg, the Dominion, and the Cardassians (twice). The century of peace was over. In 2376, Star Fleet commissioned the first Mako fighter. Designed to serve as defense for stationary installations such as planets and starbases, the Mako Mk. 1 fulfilled its mission admirably, contributing to the defense of Earth during the second Borg invasion. During the Dominion War, Mk. II Makos of the First Fighter Squadron formed a rearguard. Though many pilots were lost in the battle, their sacrifice enabled several transports full of civilians to escape safely. Despite its excellent service record, there were deficiencies in the Mako that Star Fleet Command felt needed to be addressed. Key amongst these was the fighter's low survivability ratio. Only sixty-five percent of the Makos sent on combat missions were returning. The original Mako designers, along with several members of the Defiant and Sovereign class starship design boards, began work in 2398 to redesign the fighter. The first Mk.III Makos entered service with the newly formed Ninth Fighter Squadron (9FS), in 2401. Before the year was out, the Ninth Fighter Squadron was assigned to USS Gaius Marius, and renamed Carrier Fighter Squadron Nine (VF-9). The assignment was an experiment, intended to test the new fighter's usefulness in new roles -- close air support for Marines, CAP for fleet units, and other missions. The Second Cardassian War saw the baptism by fire of VF-9 and the proof of the carrier-borne fighter concept as a vital part of the Star Fleet. The Assault at B'khai started as a minor confrontation between Star Fleet Marines and a garrison of occupying Cardassian troops. In short time, both sides called for reinforcements. By the end of the battle, an entire Marine Regiment had faced and defeated nearly double their number of Cardassian Army regulars, and a large contingent of Jem'hadar left in Cardassian control after the Dominion war. Though VF-9 lost nearly a quarter of its fighters, they were cited with keeping the death toll among Star Fleet Marines from being higher than it was. Through close air support, artillery suppression, dropship escort, and enemy troop transport interdiction missions, VF-9 ensured the future of carrier-borne fighters in the Star Fleet. Despite these impressive accomplishments, many fighter pilots still felt that the design of the Mako could be improved upon. ASDB indicated a lack of interest in persuing further design changes, so a private firm, Broken Drive's Suzuki Konbinaato, began looking at the question. Recruiting a panel of expert pilots, including most of the Fighter Squadron Commanding Officers in the Fleet, Suzuki quickly focused on the area they felt could be improved most effectively: the fighter's propulsion suite. With its maximum speed of Warp 4.5, the Mako was ineffective in fleet point defense roles, as well as in customs and border patrol roles, where larger ships could easily out run the small fighters. Suzuki quickly developed a new Matter-Antimatter Reactor Assembly and warp engines capable of propelling the small craft to greater velocities, though range was strictly limited. Now being issued to fighter squadrons, the Gueken promises to play an important role in fleet and station defense for many years to come. Mission The basic mission concept for the Gueken was defined in the Design Specification Package as "a vessel capable of: 1. Operating in defense of fixed or mobile installations with minimal resource expenditure; 2.Providing support and defense to ground units, as well as serving as a mobile communications relay, and providing tactical coordination; 3.Operating as a point-defense fighter during Fleet operations, including traffic interdiction. 4.Coordinating with major Fleet units in any conceivable offensive or defensive scenario." The Gueken is a major upgrade from the Mark III Mako. While retaining the Mako's atmospheric capability, which allows the fighter to act in roles such as close air support, artillery coordination and suppression, and drop ship escort for Marine units, the new fighter has significantly improved manuverability, increasing its capablity to assume roles such as traffic interdiction for Fleet point defense, as well as customs / border patrol activities. As a communications relay station and battle coordinator, the Gueken is capable of handling and relaying message traffic on a geometrically scaling level; the more fighters are present, the more message traffic they can handle. The expert systems link to handle the message traffic in a cooperative fashion, rather than each fighter handling every frequency. This relay can be performed without noticeable degradation of the system's normal functionality. Gueken fighters can be carried aboard any ship which has standard shuttlebays; as part of the design specification, no special equipment is required to launch, recover, or maintain the fighters, other than that which can be moved from ship to ship using a standard cargo transporter. Fighter Squadrons A total of ten fighter squadrons currently serve the Star Fleet actively, with an eleventh assigned to Training Command. They are numbered sequentially in order of founding. VF-11, assigned to Star Fleet Training Command, serves a dual purpose. Only 16 pilots are assigned on a permanant basis. Half of these serve as a cadre of flight instructors, training new pilots to handle the Gueken fighter. The other half are trained in enemy tactics, and fly against the other squadrons during "Agressor" training sessions. Stations and Carriers Squadron / Station Carrier Fighter Squadron 1 (VF-1) / USS Quanah Parker 2nd Fighter Squadron (2-FS) Starbase 867, Broken Drive Carrier Fighter Squadron 3 (VF-3) / USS Goddard 4th Fighter Squadron (4-FS) / Starbase 1, Earth 5th Fighter Squadron (5-FS) / Deep Space Gamma 1, Kelsius IV 6th Fighter Squadron (6-FS) / Starbase 4, Vulcan 7th Fighter Squadron (7-FS) / Starbase 968, Bajor 8th Fighter Squadron (8-FS) / Starbase 23 Carrier Fighter Squadron 9 (VF-9) / USS Vanguard 10th Fighter Squadron (10-FS) / Starbase 3, Andor Carrier Fighter Squadron 11 (VF-11) / USS VonBraun, Star Fleet Training Command SORM Page 2a - Gueken Technical Details General Specifications Name: Gueken Fighter, Mark I, Mod 1 Role:Short/Medium-Range Interceptor/Interdictor Length: 10m Speed: Atmospheric: Mach 2 Interstellar: Cruise Mode - Warp 4; Burn-Out Mode - Warp 9.9 Impulse Engines: Standard with Overdrivers Warp Engines: M/ARA Type SCE, Mark IV, Mod 3 Maneuvering: Twenty-Six Type V Reaction Control System (RCS) Thrusters Computer System: Daystrom Model ES924-C Expert System Crew: 1 (2 in trainer version) Gravity: Type III Inertial Dampers Armor: Parametallic polydiburnium with crystalline ablative matrix Armaments: Phaser Cannons, 2 pulse-type Quantum Mini-torpedoes (16 max. Shielding: Tri-layered multiphasic harmonic Misc.: Standard Tractor Beam Variants: Scout (with ECM) Ground Assault Trainer (Crew: 2) Construction Schedule The Gueken fighter is a product of Suzuki Konbinaato, Broken Drive, and all fighters produced to date have been built in their facilities. Negotiations are underway which would allow all H9 compliant facilities to produce the craft. To date, less than one hundred fighters have been produced, with ongoing production to replace older fighters in squadrons, and to replace combat losses. Shields The deflector shield system of the Gueken is a hybrid of Federation and captured Borg technology called multi-layered shielding. The shields are composed of three shield layers nested closely together. The outer layer is optimized for distribution and radiation of thermal energy. The middle layer rotates shield frequency and nutation, absorbing enemy fire and spreading it out along the shield before finally redirecting it into space as thermal energy. The shield can then adapt to the frequency of the enemy weapon and render it useless. The innermost layer is virtually identical to the middle layer, though the nutation is polarized in an opposite direction to the former shield's This redundancy serves two purposes. First, it ensures that the fighter will not be caught unawares by a weapon tuned to the shield's frequency, as no two layers will ever be tuned to the same frequency. Secondly, it ensures an additional margin of survivability during combat situations. The innermost shield forms within five meters of the fighter's hull, with the outer layers forming at an approximate three meter interval beyond that. Shield power is drawn from the fighter's M/ARA. Armor Comprised of layers of the light alloys used in the construction of the Defiant class, the fighter's armor can best be termed ablative parametallic polydiburnium armor. Its surface has the ability to reflect much of the energy from beam weapons (q.v. SHIELDS). The hull is also treated with sensor-absorbing substances designed to reduce the sensor signature of the fighter. While not as stealthy as a cloaked vessel, a lone Gueken can lie in wait powered down and go undetected by any but the most through of scans. Armament Most of the weapons systems carried onboard the Mako fighter have been carried over to the Gueken. The pulse phaser cannon, a hybrid of phaser and disruptor technology, is carried in paired, front-mounted linked configuration. The phaser cannon automatically rotates frequencies, and in conjunction with the expert computer system, can home in on opposing craft shield frequencies, increasing the weapon's effective yield. The missile weapons system has been designed to handle standard issue quantum minitorpedos. More stable than the conventional photon torpedo, and capable of a warhead yield of approximately 18.5 isotons, the quantum weapon is carried in sixteen individual launch tubes, distributed among the fighter's four engine pylons. The maximum velocity of the torpedo's warp sustainer engine is determined by the speed of the launching vessel, as determined by the formula Vmax = V1 + 0.75*V1/C, where V1 is the velocity of the initiating vessel. Computer / Targetting System Following the Federation High Court Decision on the Rights of Synthetic Intellegences as Sapient Beings (UFPHC Ruling 188901, Section 1, Subsection C), the production of new Artificial Intelligences has been halted. While existing AI units can be fitted to the new fighter (with the consent of the AI), the Mako's AI has been replaced by a sophisticated Expert System. Developed by a design team from Memory Alpha in conjunction with the Bynar Institute, the systems onboard each Gueken are operated by an Expert System (ES). The ES monitors the status of the fighter as well as the pilot. As the pilot logs more flight time with the ES, the ES becomes more aware of its pilots needs and abilities. Its link to the holographic targeting heads-up display (HUD) enables it to assist the pilot with tracking multiple targets. While most commands to the computer are verbal, several functions, such as targeting, can be configured to be visually activated (giving a new meaning to the term "look down, shoot down"). With time, the ES will use its knowledge of its pilot's preferences (for attack, maneuvers, etc.) to help the pilot in deciding a plan of action. Using the fighter's incredible communications ability, all fighters in a flight, wing, or squadron can share their telemetry, assembling a composite image of a battle's progress. In addition to increasing the individual pilot's situational awareness, this situational database may be of great use to flight controllers planning mission tactics. Unlike the AI carried in the Mako fighter, the Gueken Expert System has neither self-awareness nor individual personality. The ES is incapable of disobeying or countermanding orders given by the pilot, making it impossible for the pilot to lose control of the craft due to ES interference. If a pilot should be rendered unconscious during a mission, the ES will recognize this and navigate a course to the nearest safe location. In extreme situations, a single pilot can control multiple fighter craft, by slaving their Expert Systems to his own. Cockpit / Ejection System Cockpit controls have been designed to minimize familiarization time for any Mako-qualified pilot. The Gueken retains the two-hand, two-foot control system used in the Mako, in which the pilot's primary hand controls the weapons systems, as well as pitch and roll, while the secondary hand controls velocity. Foot pedals control yaw. Additionally, five configurable multi-function displays can show tactical, engineering, or weapons system status, as well as information from external sources the fighter may be able to access. The holographic head-up display serves as a virtual sixth display, shortening pilot response time in combat situations. Integrated into the rear of the cockpit is the pilot survivability module, known as the Pilot Out In Space Ejection (POISE) capsule. This module is designed to activate in an emergency, giving the pilot a margin of safety in conditions where transporters can not be used, due to distance, intervening shielding, or other unforeseen circumstances. Upon activation, POISE activates explosive bolts, which set off a sequence of events. First, nets deploy around the pilot, then tighten, bringing arms and legs safely within the module's boundaries, to avoid accidental amputation. Then, a multi-segmented Physical shield deploys, enclosing the pilot in a bubble which holds both atmosphere and temperature. Finally, the entire module is propelled clear of the fuselage of the fighter craft. Once POISE has been ejected from the fighter, it contains consumables capable of sustaining the pilot for up to five hours. In addition, it contains a medical stasis generator, which the pilot can use to enter protective hibernation. Though the longest-duration test conducted with this specific hardware is a period of twelve months, it is based upon the same principles as the pods in which the Vaadwaur survived for nearly a millennium. The module is equipped with an automated distress beacon. This beacon is dormant until it is activated by either incoming Star Fleet coded IFF transmissions, or by manual pilot override. Propulsion The propulsion suite of the Void Gueken fighter is comprised of three major systems: the warp drive, impulse engine, and reaction control system (RCS) thrusters. The Gueken uses an enhanced small craft engine, with two microfusion reactors and a mater / antimater reactor assembly (M/ARA) in a sealed unit, along with deuterium and anti-deuterium storage. Reaction Control Thrusters: In vacuum, Newton's laws of motion can be observed in a nearly pure environment, and in a much more obvious fashion than in an atmosphere. Once a fightercraft has established a vector, for instance, it will continue to move in that direction and at that speed for a practically infinate distance, unless thrust is applied to change its momentum. For this reason, the Gueken has a linked group of twenty-four RCS thrusters mounted as far as practical from the fighter's center of gravity. Because of the fighter's low mass, the RCS thrusters provide angular momentum, and thus, agility which can not be matched by larger ships. Impulse Engines At sublight speeds, the fusion reactors power the impellor coils, which lower the aparent mass of the fighter, as well as activating the energetic plasma which serves as reaction mass for propulsion. The actual impulse thrust emitters are located on the trailing edges of the engine mount pylons, providing for thrust vectoring. Warp Engine / Nacelles As defined in the Design Specification, the sealed M/ARA core used in the Gueken has a maximum cruise mode output of 150 cochranes, enabling the craft to reach a speed of warp 4.5 at maximum output. In this mode, the range of the craft is practically limited more by the pilot's endurance than by the fighter's. In burn-out mode, this output increases to a maximum of 2000 cochranes, enabling the craft to reach a speed of warp 9.9. As the name implies, burn-out mode can not be sustained for lengthy periods. The craft's supply of deuterium and anti-deuterium is consumed at a rate which increases on a geometric scale as velocity increases, and the increased violence of the matter-antimatter annihilation reactions causes damage to the dilithium crystals within the intermix chamber. At maximum velocity, the ship's power plant will deplete its consumables literally within minutes. Damaged dilithium crystals must be removed and replaced by qualified engineering crews onboard the squadron's duty station. These damaged crystals can be restructured in a Starship's engineering core, to enable them to be reused. Due to the likelyhood of damage, the Gueken is equiped with four warp nacelles, though it is capable of making warp speed on any one. Designed for the Gueken, the craft's nacelles are the latest in propulsion technology. They use low impedance warp coils which lessen the craft's effect on subspace, as well as lowering the effective power needed for a given mass / speed matrix. Each nacelle contains a complete set of four warp coils, creating a bulky, bulldog look. Under normal conditions, only one coil in each nacelle is actually in use. This arrangement increases the angular distance between the lobes of the warp field, leading to increased manuverability at hyperluminal velocities, though it lowers the overall efficency of the system. For increased efficency, and higher straight-line sprint speeds, the warp field can be flattened by reducing to a standard two-nacelle operation. Should circumstances dictate, any one or all four of the nacelles can be jettisoned. SORM Page 2b - Mako Technical Details General Specifications Name: Mako Fighter, v.III Role: Short/Medium-Range Interceptor/Interdictor Length: 20m Speed: Atmospheric - Mach 2 Interstellar - Warp 4 Impulse Engines: Standard with Overdrivers Warp Engines: MARA I Maneuvering: Four Type V Thrusters Computer System: CLASSIFIED Crew: 1 (2 in Assault version) Gravity: Type III Inertial Dampeners Armor: CLASSIFIED Armaments: Phaser Cannons (1 Std., 2 max.) Enhanced Quantum Mini-torpedoes (6 max.) Shielding: CLASSIFIED Misc.: Standard Tractor Beam Variants: Scout (with ECM) Ground Assault (Crew: 2) Trainer (Crew: 2) Project Overview While runabouts and shuttles handled the Federation's transportation needs, and starships served as its primary defenders and explorers, a fighterbetween the two. A small, fast, highly-maneuverable ship was needed that could engage craft similar to itself, or even large starships and still have a reasonable chance of survival. After the disaster of the Federation's stand against the Borg at Wolf 359, the effortless destruction of the Mars defensive perimeter soon afterwards, and the eventual looming Dominion threat, this void became more apparent. In 2376 Starfleet commissioned the Mako Fighter v.I to fill this gap. The Mako v.I, and its successor, the Mako v.II, are still in use by many Federation members today as first line interceptors or light patrol craft. Alongside the new Defiant, Steamrunner, and Sovereign class starships, Mako fighters fended off a second invasion of the Terran system by the Borg in 2380. Makos also served admirably during the evacuation of Deep Space Nine during the Dominion invasion in 2381, with several flights of fighters sacrificing their lives in a rear-guard action which enabled multiple transports to escape. Despite its excellent service record, there were deficiencies in the Mako that Starfleet Command felt needed to be addressed. Key amongst these was the fighter's low survivability ratio. Only sixty-five percent of the Makos sent on combat missions were returning. The original Mako designers, along with several members of the Defiant and Sovereign class starship design boards, began work in 2398 to redesign the fighter. The end product, commissioned for active duty in 2401, is the Mako v.III. There are several key components added to the v.III. These components have been added to increase a pilot's mission survivability as well as mission success chances. Armor The exact composition of the armor used on the v.III is classified, for Alpha-level clearance only. Comprised of layers of the light alloys used in the construction of the Defiant class, the Mako's armor can best be termed as Ablative Nano-Durasteel armor. Its surface has the ability to reflect most of the energy from beam weapons (see SHIELDS). The hull is also treated with sensor-absorbing substances designed to reduce the sensor signature of the fighter. While not as stealthy as a cloaked vessel, a lone Mako can lie in wait powered down and go undetected by any but the most thorough of scans. Most damage that is suffered by the craft, short of a critical hull breach, can eventually be repaired by the onboard automated nanotechnology repair system. The nanites are a part of the armor, laying dormant until armor is damaged. Computer / Targetting System Like the armor, the exact details of the computer system are classified for Alpha-level clearance only. Developed by a design team from Memory Alpha in conjunction with the Bynar Institute, the system onboard each Mako is operated by an artificial intelligence (AI). The AI monitors the status of the fighter as well as the pilot. As the pilot logs more flight time with the AI, the more aware the AI becomes of its pilots needs and abilities. Its link to the holographic targeting heads-up display (HUD) enables it to assist the pilot with tracking multiple targets. With time, the AI will use its knowledge of its pilot's preferences (for attack, maneuvers, etc.) to help the pilot in deciding a plan of action. If this information is shared amongst a squadron, a wing, or a flight, the AI can help a flight control officer plan the tactics for a mission. In case the fighter becomes inoperable due to damage or maintenance, the AIs are portable and can be transferred between Makos. This allows a pilot to maintain the symbiotic relationship that forms between himself and the computer system. If the pilot should be hurt during a mission, the AI will recognize this and navigate a course to the nearest safe location, taking whatever means necessary to ensure the survival of the wounded pilot. Note: It should be explained that the AI will not perform any actions without authorization from the pilot. This prevents the pilot from losing control due to AI interference. The AI will develop a personality, but its programming limits this personality from expanding beyond specific parameters. While most commands to the computer are verbal, several functions, such as targeting, can be configured to be visually activated (giving a new meaning to the term "look down, shoot down"). Weapons Smaller versions of the weapons systems used by the Defiant class were created for the Mako. First of these is the phaser cannon, a hybrid of phaser and disruptor technology. The phaser cannon automatically rotates frequencies, and when used with the Mako's computer system, can determine a target's shield frequency. The second weapon is the enhanced quantum mini-torpedo, a more stable warhead system than the photon torpedo. This variant of the torpedo is smaller in size than a standard QT, with an acceleration from standing to Warp 9.2 in four nanoseconds. The torpedo also features a loiter mode, allowing it to be used as a mine that will attack a pre-programmed target. The combination of these two systems in testing have proven deadly. A squadron of nine Makos have been able to cripple and destroy a Vorcha-class Klingon attack cruiser. Despite this stunning capability, it must be noted that these weapon platforms were chosen explicitly with a Borg invasion in mind. Shields The exact details of the shielding of the v.III is classified, requiring Starfleet CINC clearance for full disclosure. The deflector shield system of the Mako represents another hybrid, this time of Federation and captured Borg technology. Called Multi-layered Shielding, the shields composed of several static shield layers nested closely together. Each layer has a specific function. The outer layer is unusual and little information has been released on it. The middle-layer rotates shield frequency and rotation, absorbing enemy fire and then spreads it out along the shield and finally redirecting into space. The shield can then adapt to the frequency of that weapon and render the enemy weapon useless. The function of the inner-layer is unknown. The shield lies within 5 meters of the actual hull. There is an approximate 3 meter interval between each shield. Power is taken form the warp engine. Other added features: The v.III is the first of the Mako-class that is warp- and atmosphere-capable. This allows the fighter to serve as a planetary assault/defense vessel. It also expands the range of the fighter, giving it a short- to medium-range. Long-range missions would require a ship specified for fighter carrier duty. The Mako's impulse engines are enhanced with overdrivers, allowing the fighter incredible sublight speed acceleration and maneuverability. SORM Page 3 - Squadron Organization Introduction A fighter squadron is a large and complex organization which uses a hierarchal structure to function efficiently. Similar to a starship, a squadron has a Commanding Officer, an Executive Officer (sometimes called a First Officer), and various divisions and departments, each with a DivO or Department Head, as well as various officers and enlisted specialists. Unlike the average starship however, a fighter squadron is specialized, dedicated to the task of maintaining, supporting, and fielding fighters at peak efficiency. The staff of a fighter squadron is divided into four departments: Flight, Operations, Engineering, and Logistics. Each department has a department head, usually the senior officer in that field. Departments are further divided into divisions, and each division has a division officer, or DivO. Flight Department Because of the specialized mission of a fighter squadron, both the CO and XO must be pilots. It is not unusual for pilots to also fill billites in the Operations Department, leading to a squadron being smaller than the Table of Organization (TOO) would suggest. At optimal staffing, a fighter squadron will have thirty-six pilots. These pilots are subdivided into flights of three to six pilots, and may also be grouped into wings of two or more flights. Flights are led by Flight Leaders, wings by Wing Commanders. Operations Department The Operations Department is concerned with the day to day operation of the squadron, and is comprised of the Administration, Intelligence, Navigation, and Communications divisions. Administration Division Because of the unique mission of the fighter squadron, and the resulting deviations from normal Star Fleet duty stations, a squadron orientation officer is assigned. The Chaplin has been trained to respond to the religious needs of the crew, and has been trained to recognize and cater to the requirements of a large number of Federation religions. By special arrangements with the majority of the Federation's religious decision-making bodies, this individual has been authorized to effect any of the ceremonies and rituals which may be required during an extended mission, including marriages, divorces, baptisms, last rites, and other religion-specific duties. An educational services officer is assigned to assist personnel in furthering their individual knowledge, skills, and educational attainments during long deployments. Administrative specialists (called yeomen) maintain records, ensure accurate reports are made as scheduled, and perform other duties as assigned. Each department has at least one yeoman. Divisions which require dedicated administrative assistance are also assigned a yeoman who is specifically responsible for that division. The CO's yeoman, along with the senior yeoman, provide direct administrative support to the CO and XO in consolidating and maintaining both internal and external administrative matters. They are also responsible for ensuring personnel records are up to date, scheduling and tracking personnel and promotion reviews, and departmental personnel assignments. The Command Master Chief is tasked with counseling enlisted crew members in the areas of career, performance, and personal matters, as well as being a direct link between the CO and the enlisted crew. Navigation Division The FlightOps computer onboard the carrier or station where the fighter squadron is assigned is the primary source for position updates, chronometer calibration, and course determinations. It uses navigation and time beacons, sensor inputs, and complicated algorithms to ensure that the Navigator is presented with precise, up-to-date data and course plots, so he can pass these on to the fighters of the squadron. It is imperative that the navigational data be monitored and cross-checked at all times. To this end, Navigational Specialists, called Quartermasters, stand watch in stellar cartography. They are responsible to the CO, XO, and Flight Control Officer of the Watch (FCOW) during their watch. In addition to maintaining an accurate plot of the motions of the ship or station, the Quartermaster gang is responsible for updating and maintaining the navigational charts used by the FlightOps computer and the individual fightercraft. Computer technicians are also assigned to the Navigational department, to maintain, repair, and oversee the navigational system components and equipment. One technician is on watch at any time Stellar Cartography is manned. Communications Division The ability to transmit and receive messages from other ships of the Federation and alien races, Starbases and planets, is an important part of squadron operations. Ensuring this ability to communicate is the task of the Communications Division. Electronics Technicians of the Communications Division perform repair and maintenance on the fightercraft's com systems, as well as maintaining a communications watch in the squadron's Combat Information Center (CIC). Intelligence Division A fighter squadron must always have the most accurate, up-to-date situational information available. Weather dealing with an established threat like the Romulans, Borg, or Cardassians, or entering a first contact situation with a new, potentially threatening species, the analysts of the Intelligence Division are constantly at work in CIC, sifting through data, analyzing intercepted communications, trying to assemble the best, most complete picture possible of the situation facing the squadron. Engineering Department The Engineering Department, led by the Chief Engineer, is responsible for the proper maintenance and repair of impulse and warp drive propulsion, life support systems, fighter weapons systems, deflector systems, ECM and ECCM units, and all other Physical components and systems of the Gueken fighter. Engine Systems Division Engineers assigned to this division have responsibility for maintenance, repair, and calibration of fighter warp drives, impulse engines, and reaction control system thrusters. Matter / Antimatter Specialists ensure the efficient tuning of the sealed M/ARA units aboard the Gueken fighters. Dilithium Crystal technicians monitor the status, consumption rates, and recrystalization of this vital component of the engine. Structural Engineering Specialists monitor and maintain the Inertial Dampening System (IDS) and hull integrity. Life Support Technicians maintain the fighter's artificial gravity generators, atmospheric quality regulators, humidity and temperature regulators. Weapons Systems Division Kilogram for kilogram, no unit of the Star Fleet is more powerful than the Gueken fighter in terms of offensive capacity. The Engineers of this division maintain and repair the pulse phaser cannons and minitorps carried by the fighter. Phaser Technicians carefully maintain and calibrate the pulse phaser cannon carried by the fighters, while Torpedoman's Mates care for the launch and stowage systems for the quantum minitorps. Flight Deck Division Though the operation and maintenance of the squadron's fighters are the responsibility of the Flight and Engineering departments, respectively, the safe and efficient operation of the hanger decks, launch and recovery bays, and all objects therein fall to the personnel of the Flight Deck Division. Movement of any craft within the Hanger Bay or on the Flight Deck is controlled by the Flight Deck Officer and by numerous Flight Deck Control Specialists. The Cat officer controls the launch of craft from the Flight Deck, while the Landing Signal Officer controls recovery operations. Plane Captains are enlisted specialists who are assigned individual responsibility for a given fightercraft's maintenance. They take cognizance over the fighter from the moment the pilot climbs out of the cockpit until the moment she climbs back in. It is their responsiblity to have the craft fueled, armed, provided with accurate navigational data and appropriate charts before flight. Logistics Department Though modern fabrication and replication systems onboard ships and stations of the Star Fleet have made routine of most requisition and supply issues, there are still some items which are used in sufficient quantity, or are of sufficient size or complexity that it is more efficient to store finished products than to spend the energy to carry raw materials and synthesize the product on demand. Additionally, significant stores of critical spares and consumables are maintained for use during red alert situations when power for replication or fabrication systems may be unavailable. Logistics department Storekeepers store, maintain, inventory, and deliver such supplies as necessary. SORM Page 4 - Operations and Alerts Standard Operations Daily Routines Fighter squadrons, like most other duty stations in the Star Fleet, operate on an around the clock schedule. A schedule of activities is maintained by the Administration Division, and promulgated to the crew in the Plan of the Day (POD), which is accessible from any PADD or ship's console. The POD is updated by the Yeoman of the Watch at the end of each watch. Timekeeping Units of the Star Fleet spend most of their time among the stars, and a fighter squadron is no exception. Timekeeping, therefore, becomes a matter of supreme importance, there being no planetary rotation to use in verifying the time of day. In keeping with the practice of the Star Fleet, the Quartermasters of the Navigation Division maintain chronometers which measure a 24 hour day. Tied to the time kept at the Fleet Observatory in San Francisco, Earth, Pacific Standard Time has been adopted as the standard for measuring time aboard most Star Fleet vessels and stations. The 24 hour clock is also used, to eliminate any possible confusion in establishing the time of an occurrence, past or scheduled. The hours begin at 00:00 (midnight), and count up through 23:59 (the minute before midnight). Watches, Shifts, and Patrols With the exception of the Commanding Officer, Executive Officer, and Department Heads, all squadron personnel are assigned to a shift section. There are three shift sections, each having an equal portion of personnel from each department or division. Each of these sections takes a turn at being on watch, as designated in the watchbill, and promulgated in the POD. An occasional exception to the three-shift schedule is the flight department. As emergency situations often call for all the fighters of the squadron to be fielded at one time, arrangements are made for this eventuality. Alert Conditions Green This is the normal status of the squadron. No dangerous conditions exist within the patrol boundaries of the squadron. Watches and Patrols are stood as assigned by the watchbill and PoD. Yellow A hazardous or potentially hazardous condition exists either within the squadron's patrol area, or within its immediate vicinity. This condition may be set by the CO, XO, or CIC Officer of the Watch. The on-watch shift remains on duty, and prepares for possible danger. Second shift goes on duty, and joins first shift at duty stations. Third shift is awakened, but does not come on duty. Each station reports to CIC when manned and ready. Red Also known as Battle Stations or General Quarters, Red Alert is set when a life threatening condition exists within the squadron's patrol area or its immediate vicinity, or elements of the squadron are in an offensive or defensive situation which has, or may soon result in the use of weapons. May be set by the CO or XO. Third shift goes on duty, and reports to duty stations. All pilots report to their craft, and standby for possible scramble. Credits The VF-9 SORM was written by Dawn McKnight, with some material having been developed by Reggie Allen, Belinda Crawford, and Chris O'Sullivan. Technical assistance provided by R. S. Pylman