SoP: Exploration: Difference between revisions

From Citadel Station RP Wiki
No edit summary
m (Changed protection settings for "SoP: Exploration" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite)))
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Header - Administration}}
[[Category:Administration]]
{{Header - Standard Operating Procedures}}
{{Header - Standard Operating Procedures}}
[[Category:Standard Operating Procedures]]
[[Category:Standard Operating Procedures]]
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}
{{SOP_TITLE|Exploration / Pilots}}
<center><h1>Exploration/Pilots</h1></center>
{{TOC_RIGHT}}
{{TOC_RIGHT}}


==Exploration==
<span id="fleet-operations"></span>
= Fleet Operations =
 
This page is relevant for those working aboard a NSV/NEV-class installation.
 
Inside contains special procedures and protocols necessary for the successful operation of a Nanotrasen excursionary vessel.
 
<span id="primer"></span>
== Primer ==
 
Whereas planetary bases and orbital stations are often the go-to installations for a given sector, Nanotrasen’s top of the line vessels are utilized for scouting and investigation of the great unknown.
 
You will often operate at distances that make response teams and rescues infeasible, or in some cases, impossible. With great risks come great rewards, however - compensation is ''greatly'' increased for those willing to weather the stresses of deep-space exploration.
 
<span id="vessels"></span>
== Vessels ==
 
New-generation NEV/NSV-class cruisers built after 2560 come with a variety of features to improve crew safety, comfort, and efficiency, including:
 
* Civillian decks and staffing, including a full entertainment and catering suite.
* In-built mini-dormitories, and a full cryosleep solution for when one can’t make it to the next step.
* Proper facilities for Heads of Staff, and safe rooms for emergency protection.
* State-of-the-art FTL transit (pending) and repulsor generators.
* Matter-beam disperser generators for emergency path-clearing operations.
* A full complement of department transit shuttles, as well as general purpose scouting shuttles within a hanger deck.
* Redundant reactor cores and power generation.
* And more!
 
<span id="command"></span>
= Command =
 
On NEV/NSV-class installations, Command obtains additional responsibilities other than simply managing their department.
 
* '''All''' heads of staff are expected to:
** Be EVA trained, or obtain EVA training within one week of posting.
** Be trained in disaster response to common scenarios aboard a Nanotrasen vessel, including but not limited to fire, boarders, and structural damage.
** Assist in the operations of the ship, in addition to their department. The ship comes '''before''' your department.
* Command is responsible for organizing flight plans, shuttlecraft operations, and excursions.
* Command is responsible for planning the route that the ship will take to accomplish its directives.
* Command is responsible for monitoring the ship’s status, and undertaking necessary actions to protect the ship’s integrity.
** Remember: There is no '''emergency transfer shuttles''' in deep space. Current-generation NEV/NSV-class cruisers are versatile, and ''valuable'' assets to the Company. Abandoning the ship is an absolute last resort.
* '''Bridge Officers''' are elevated to the role of pseudo-command in terms of sector and voidcraft operations on these vessels, as opposed to mere secretaries and coordinators.
 
<span id="pilots"></span>
= Pilots =
 
Anyone piloting a vessel / shuttlecraft must strictly adhere to the following restrictions:
 
* Pilots must be trained for duty for the class of vessel they are operating.
** Learner pilots must be accompanied by a trainer while flying. They may '''not''' fly alone.
* Pilots must keep communications open with Engineering for callouts on ship statuses and potential problems.
* Pilots '''must''' be of sound mind and without any disruptions to their judgements.
** '''Alcohol, Ambrosia, and other recreational substances are strictly prohibited while on-duty.'''
** Any psychological conditions documented must be cleared by Medical Staff for someone to be eligible to be employed as a Pilot.
** Any unexplained &amp; volatile alterations to behavior or suspected tapmering mid-operation is acceptable cause to switch out a Pilot until mental state may be ascertained.
* A pilot is considered on-duty and flying for the '''full''' duration of the operation.
** Stopping at a planet does not mean you are off-duty and free to drink. Remember, you may need to move at a moment’s notice.
** The only exception is if there is an on-call replacement for you who is ready and willing to go in your place.
* Pilots are held to a higher standard for availability while on duty. If you require private time, '''clock off.'''
* Pilots should ''avoid'' flying alone.
** There are many circumstances where this is not possible to mandate. Thus, make a best-faith attempt at ensuring a backup is able to take over in case of incapacitation.
* Pilots are not obligated to maintain a presence on board their vessel at all times - only to maintain the capability to fly it.
** Pilots should not be ordered to remain behind to 'guard' a parked vessel. They are free to disembark and join an active mission at will.
** The Pilot ''is'' still responsible for the security of their assigned vessel. All reasonable measures must be taken to ensure NanoTrasen property cannot be stolen before the Pilot may disembark.
 
<span id="exploration"></span>
= Exploration =
 
NSV/NEV-class installations are generally operated to scout, as well as investigate points of interest within their local sectors. As such, they are staffed with a variety of shuttlecraft to facilitate crew movement.
 
* No crewmember is '''obligated''' to partake in excursions, other than designated roles like the Pathfinder and Pilots.
* No crewmember is inherently '''disallowed''' from partaking in excursions under all circumstances.
** Crewmembers should be deployed based on the mission’s need and one’s skill-set. You would not bring non-combatants to a bug hunt, and you should not bring ''only'' combatants to a beacon station during a repair operation.
 
<span id="away-teams"></span>
== Away Teams ==
 
Away teams may be formed, and deployed, in these circumstances:
 
* Command authorization. This obviously overrules all of the below.
* Pathfinder authorization; this '''only''' applies to the Pathfinder’s excursion shuttle.
** Only the Research Director or the Captain may veto such a launch.
* Bridge Officers authorizing an excursion when there is no Command available.
** Bridge Officers may not utilize the Pathfinder’s excursion shuttle or equipment without their explicit permission.
** Bridge Officers may not abandon the ship to pilot shuttlecraft themselves unless there is available personnel to man the bridge in their place, '''and''' there are no pilots willing / wanting to pilot.
* Pilots authorizing an excursion when there is no Command available.
** Pilots may not utilize the Pathfinder’s excursion shuttle or equipment without their explicit permission.
** Bridge Officers may veto the launch during an emergency.
* Heads of Staff, and department staff in general, may utilize their own department shuttlecraft, if one exists, for any purpose constituent to their department’s operations.
** Command staff may veto the launch even if it is not their own department - the department head and the Captain obvioulsy overrule in these cases, if they exist.
** Bridge Officers may veto the launch during an emergency.
* For anyone but the Pathfinder, it is expected to obtain permission from the relevant head of staff before launching, if one exists, or Command / Bridge Officers in general, if they don’t. It is unacceptable to take shuttles out wordlessly.
 
<span id="transit-navigation"></span>
= Transit &amp; Navigation =
 
The broad responsibilities of Pilots, Bridge Officers, and the Command staff include the transit and navigation of the installation and any provided shuttlecraft during the pursuance of assigned directives.
 
<span id="maneuvers"></span>
== Maneuvers ==
 
The Command staff is expected to communicate with pilots during ship maneuvers. Newer ships contain a variety of specialized shuttlecraft, and performing safe transit while
 
* Preplan all routes if at all possible.
** This will usually not be feasible due to limited data on sector topography.
* Ensure all shuttlecraft have knowledge of the primary installation’s motion. Shuttlecraft are unable to operate for long periods without a host ship, and searching for a lost shuttlecraft is not just time-consuming, but also puts its crew at risk.
* Observe minimal safe distance from encountered hazards.
** Flying through hazards is to be avoided.
** Clipping the edge of an asteroid belt (or worse) can still result in ship damage.
* Observe maximum safe speed for your ship / shuttle’s stopping distance.
** You should be able to stop in time for a hazard popping up on sensors - longer sensors, and/or better propulsion allow for higher allowances on braking distance.
* Ensure knowledge of all maneuvers are received by coordination on the Bridge, if at all possible.
 
<span id="takeoff-landing"></span>
== Takeoff / Landing ==
 
Shuttlecraft perform many maneuvers during the course of a shift. They are '''deadly''' to anyone caught inside a hanger bay during landing!
 
* '''Always''' radio in before docking. Give at least ten seconds for the hanger to be cleared.
* '''Always''' respect landing lights. Shuttlecraft approach at extreme speeds, and will easily kill an unprotected individual upon impact!
* '''Always''' clear out of the hanger during shuttle docking / undocking. It is not worth the risk.
* Do '''not''' hang around inside the hanger longer than necessary. Other ships may need to take off and land.
 
<span id="encounters"></span>
== Encounters ==
 
While the Frontier is a sparse place, common exploration of the assigned sector-groups may place the crew in contact of other spacefaring factions.
 
* Registered Corporations are not to be interfered with, unless a Nanotrasen Employee is in danger, or there is a suspected breach of Admiralty Law.
* Unregistered vessels should be treated with caution and scrutiny. Privateers and free-roaming mercenaries are not unheard of, and the installation is not equipped for a protracted conflict.
* Command is in charge of first-contact communications when at all possible, whether towards lesser-known colonies / vessels or towards unidentified species!
* A full Command staff discussion must be conducted before authorizing unregistered vessels to physically dock with the installation, or approach within boarding distance.
 
<span id="ftl-travel"></span>
== FTL Travel ==
 
Most shuttlecraft are unable to sustain their own transit engines for FTL jumps.
 
As such, the primary ship '''must''' exercise caution as to not leave crewmembers behind. Communications from other sectors can be impossible - Coommand must ascertain the status of all shuttles prior to transit maneuvers.
 
It is not acceptable to leave crew behind during a jump outside of an '''absolute''' emergency.
 
<span id="shuttlecraft"></span>
= Shuttlecraft =
 
A full set of shuttlecraft is usually provided to frontier installations for the purposes of exploration, scouting, and retrieval.
 
Shuttlecraft clearly marked as a departmental utility shuttle are under the command of their respective departments, and the (acting) Captain.
 
All other shuttlecraft are operated and managed by pilots and bridge officers.
 
* Pilots have priority for shuttlecraft. Bridge Officers are there to handle ship operations first and foremost, and should only fly as a backup, if at all.
* Much like with heads of staff, bridge officers '''may not''' leave the ship to fly a shuttle if there is no one else to handle the bridge, or if a head of staff prohibits them from leaving.
* Pilots do not have authority over department shuttlecraft. They may only take them if the department in question (or the acting / Captain) gives permission to do so.
 
<span id="piloting"></span>
== Piloting ==
 
In addition to the usual guidelines for pilots, shuttlecraft pilots should be aware of the following guidelines:
 
* Always file flight plans. Given the current lack of networked management systems, even a PDA and confirmation from a Command member, a bulletin posted in the bridge, etc, are acceptable. This makes recovery easier in the event of an emergency.
* Secure your shuttle. Losing it can end with you marooned, or worse. The shuttle is often your only reliable source of long range communications, as well as extraction.
* Use the distress beacon sooner rather than later - optimally the moment control is near-permanently lost, or structural integrity is heavily compromised. You do not want to fall unconscious before sending out a distress call.
* '''You''' bear the burden of responsibility for ensuring everyone makes it safely to a destination, and back. Ensure continuous headcounts are done.
** Even if someone else is directing the '''mission''', you, as a pilot, must be aware of your crew. There is no excuse for being unaware of a missing crewmember, or in some cases, an extra.
 
<span id="maintenance"></span>
== Maintenance ==
 
Shuttlecraft sustain damage far more easily than larger ships. As such, some special guidelines are in place for shuttle operations.
 
* Exercise caution while flying, especially if you do not have a shield. A bad hit from a meteor can easily render vital systems inoperable.
* Light damage can usually be repaired with materials on hand. Be sure to check for hidden issues, like broken wiring and gas pipes underneath flooring.
* If a shuttle has sustained systems damage, it is best to return to base for repairs as soon as possible.
* Shuttles with damage that severely impact operations are not allowed to be used for missions outside of a dire emergency.
* Always charge the SMES before every trip. It is usually your only source of power while on excursion, and losing power mid-flight is often lethal.
 
<span id="special---the-exploration-department"></span>
= Special - The Exploration Department =
 
Some installations, usually planetary / orbital stations, are fitted with a standing Exploration department.
 
The Exploration department is the standby away team of an installation, led by the Pathfinder.
 
<span id="the-pathfinder"></span>
== The Pathfinder ==
 
The Pathfinder retains their regular duties of scouting and away operations. The only difference is that they now have a full departmental staff at their back and call.
 
The Pathfinder is considered senior staff within the Research department, and work under the RD, with specific exceptions. [[SoP: Chain of Command|Chain of Command]] specifies what the relationship between the Pathfinder and the RD is.
 
<span id="the-department"></span>
== The Department ==
 
On such installations, the Pathfinder is often given a far more equipped department. One can expect to find:


*Gateway/Shuttle expeditions are to be organized by the Pathfinder unless CentComm commands otherwise. If two or more [[Explorer|Exploration]] crewmembers wish to embark on an expedition when no Pathfinder is available, they may do so after faxing notice of their intent to Central Command. The [[Facility Director]] should not be starting expeditions on their own without orders directly from Central Command.
* A full briefing room
*Any two Heads of Staff may prevent an expedition from leaving, though only if they have a valid reason for preventing it. Any Heads of Staff that are found to be preventing an organized and equipped expedition from leaving shall be considered as exceeding official authority, provided the minimum requirements for leaving, as listed under the next section, are met.
* A miniature rescue bay
*Heads of staff should <b>not</b> be participating in gateway missions or expeditions without explicit consent of the Facility Director. Central Command may override this restriction if they deem it necessary.
* A pilot’s prep room
* An explorer prep room
* Extraneous areas otherwise built into the ship or spread out elsewhere
* Heightened security measures
* Any additional shuttles provided in addition to the exploration cruiser, like the prototype scouting vessel.


====Initial Away Team====
The Exploration department further receives additional staffing of a number of Explorers and Field Medics. Pilots are granted access, as it is expected that pilots fly for the Pathfinder outside of circumstances dictating otherwise.
An initial expedition team must consist of the following where reasonably possible. A Pathfinder or equivalent should ideally make requests for staff via the PDA department relay, command channel with the appropriate heads of staff, or station announcements.


*The Pathfinder, acting as the leadership role for the expedition. In instances where the Pathfinder and another Head of Staff are present on an expedition, the Pathfinder retains command of the expedition. If the Pathfinder is incapacitated, any present Head of Staff assumes command.
* It is recommended to bring additional crew, like sappers, security escorts, etc, as necessary.
*All available [[Explorer|Exploration]] crew members. This is their primary mission purpose, after all. They should be armed and armored with whatever equipment Research can provide. Their first goal should be to identify any threats near the landing site or gateway endpoint and ensure the path is clear for other members, before the next stage of the expedition.
*An [[Engineer]] may accompany to play the role of sapper, equipped with general purpose tools for hacking, construction, and deconstruction. One goal of the engineer should be to set up a telecommunications relay, if the site is discovered to be habitable and able maintain crew for a large part of the shift.
*A [[Scientist]] may accompany the initial expedition, equipped with camera, scientific instruments, and clipboard with pen and papers for taking notes. This can be the Research Director but it is preferred that a normal scientist come along instead. It may be better, however, if the scientist arrives after the site is cleaned and prepared.
*A [[Medical Doctor]], [[Paramedic]], or [[Search and Rescue]] crew member to play the role of medic, equipped with one of each type of first aid kit, and at least one cryobag for emergencies.
*If reasonably available, a [[Security Officer]] equipped with lethal ranged weapons of choice, or equipment from storage as assigned by the expedition leader. Their goal should be to secure the landing site with the initial team, and prevent any creatures from compromising the gateway or shuttle and making it back to the station.
*A [[Pilot]] should accompany any expeditions via shuttle, as their skills can be required to make a hasty departure, or ferry crew members to and from the landing zone to obtain additional supplies or return any casualties.
*Volunteers may enlist to join the initial expedition, if they sign a waiver before departing on the expedition, and have the required skills to fulfill one of the above roles.


If only one crewmember is occupying a department, they may not accept this request without going Off Duty, or receiving the approval of their Department Head. If no Department Head is present, any crewmember or crewmembers abandoning their department to embark on an expedition should be treated as a violation of [[Corporate Regulations]] &sect;222.
The Exploration department, much like the Pathfinder, still answers to the Research Director while not on an away mission. [[SoP: Chain of Command|Chain of Command]] specifies the specifics of its command structure, in cases of disagreements.


Regardless of rank or certification, no crewmember may pilot and maneuver the Expedition shuttle, unless authorized for the purposes of emergency retrieval or reaction during a Code Red situation, without at least one additional passenger capable of piloting the shuttle. Due to retrieval concerns in the event of an unexpected emergency, solo piloting of the shuttle should be treated as a violation of [[Corporate Regulations]] &sect;215, &sect;222, and &sect;402.
<span id="excursions"></span>
== Excursions ==


====Pre-Mission Setup====
The following guidelines '''must''' be met for excursions:


*All weapon-trained crew may be offered the opportunity to arm themselves from Security supplies or Research products. Crew armed in such a manner shall return the weaponry obtained to the armory for storage after the expedition is over.
* The minimum team size is '''two'''. Even a Pathfinder should not be going out alone, outside of emergencies.
*It is heavily recommended that, when possible, energy weaponry should be used. Friendly fire incidents are easier to treat when surgery is not required in the field.
* Only a Pathfinder, RD, or (acting) FD may authorize an expedition.
*All participants must bring a shortwave radio. Confirm a shared frequency on all shortwaves before embarking. Setting up a communications relay at the landing zone, while an admirable endeavor, is optional.
** If one does not exist, a fax to Central Command suffices if no negative response is received within five minutes.
*The participants should be in sealed pressure suits unless the destination is already known, and confirmed to have a habitable atmosphere.
** In these cases, the minimum team size is raised to '''three.'''
*Internals must be turned on prior to crossing the threshold of the gateway, and during all shuttle flights for the initial expedition.
** This may not be done within the first 15-30 minutes of the shift. It is not acceptable to take the shuttle out during this time, as a Pathfinder / RD may still be on ths way.
*Magboots are recommended, but not required.
* As per Chain of Command, the RD / (acting) FD may veto an expedition. This is unlikely to come into play under normal circumstances.
*As each team member's loadout is complete, they should wait outside the gateway or shuttle until the mission begins.
** A Pathfinder is expected to notify the RD, or if one does not exist, the FD, of an excursion five minutes or more in advance of departure. They do '''not''' have to wait for a confirmation.
* The shuttle must be secured at all times.
** '''The shuttle is your lifeline.''' Losing it can mean marooning, or worse.
** If going to a hostile sector, ensure one person who is '''armed''' stays behind to watch the shuttle. This is usually the pilot.


====Mid-Mission Operations====
<span id="weapon-permits"></span>
== Weapon Permits ==


*If separated from the group, or in an airless environment, establish communication immediately with other members of the group. If you are unable to re-establish communications, wait where you are for rescue. If you are in danger of running out of oxygen or supplies, move back towards the start of the mission, following any marker beacons that were laid down.
The Exploration department is given weapons permits valid '''on an away mission only.'''
*Once present with the whole group, and no longer in an airless environment, all members but the assigned team leader should turn off their long range communications until separated again.
*If the group is scattered due to an imprecise gateway destination target, and the location of the return gateway is unknown, first objective is to locate and calibrate the return gateway. Return gateway can be calibrated using a multitool on the control panel in the center of the gate.
*Any artifacts or strange life forms should be documented as soon as it is safe to do so. If possible, they should be brought back. Having an artifact handling container may help with this.
*If an expedition participant is injured and needs surgery, they should be evacuated to the station immediately. The expedition should not proceed unless their role is satisfied by someone else, or they return to continue. (That said, you're allowed to use your better judgment. You're not going to get banned because someone died and you decided to keep going. That risk is kind of part of the whole point of things.)


====Post-Mission Debriefing====
Members and volunteers may freely carry weapons inside the department for staging purposes.


*The returning crew are not to leave the gateway room or shuttle hangar until allowed to do so by the Head of Security, or if the HoS is absent, by the Pathfinder, or next in command. During this time, participants should be screened for contraband, health, and mental well-being before returning to the rest of the station.
All weaponry must be stored in a reasonable location while not in use.
*If any staff are at risk of health complications such as parasitic life forms, viral infections, insanity, etc, they are to be immediately evacuated to the Medical Department for treatment.
*Excluding items that the Research Department wants to study, Security is to confiscate any contraband discovered during the mission.
*All weapons and armor taken for the trip should be returned to the armory, even if it was originally brought to the station through cargo. The exception is the [[Explorer|exploration]] equipment produced by Research, which can be stored securely in Research while the explorers are off duty.
*Other excess supplies are to be returned to their rightful departments.
*A post-mission report should be faxed to Central Command detailing any discoveries located, and if any artifacts are recovered, if they will be returned to Central Command at the end of the shift or if they will be stored in Research to be collected after the shift ends.
*At this point, if the destination is habitable to normal crew without preparation, or if engineers wish to make it so, they may embark on follow-up expeditions to occupy and utilize the area for their purposes. This can '''only''' be done if the destination is safe for crew habitation, and a [[Pilot]] is available in the case of shuttle destinations, or the gateway prep area being cleaned of dangerous items for gateway destinations.


===Exploration Weapon Permits===
Bringing any armamanets, including one’s machete, outside the department is not authorized by the provided permit.


It has been ruled that all relevant employees be issued weapon permits to allow for personal protection in the course of carrying out the duties assigned to NanoTrasen’s specialized departments. As such, weaponry and permits have been distributed to those departments affected by this provision. The ownership of an Exploration weapon permit represents the employee’s entitlement to carry any weapon conducive to maintaining a safe environment when engaged in off-station activities, or during transit to engage in such activities. The Exploration weapon permit does not grant its bearer the right to bear or display arms inside a NanoTrasen facility, unless for the purposes of transportation to or from the Research or Security departments. Secure lockers have been provided for the express storage of these weapons. The on-station carrying of assigned melee weaponry, including but not limited to survival knives and machetes, outside of the Exploration department is equally unlawful. Failure to properly secure all weaponry within the relevant department may result in penalties, up to and including the revocation of this Departmental weapon permit or the revocation of Departmental certification for an unstated period of time.
<span id="crew-restrictions"></span>
Under specific circumstances, namely the announcement of Codes: Red or Delta, the restrictions barring the carry or usage of assigned or recovered weaponry may be waived by an acting member of the on-site Command Staff. In the event that no Security crewmembers are available – either by incapacitation or other condition – these restrictions may also be lifted on Code: Yellow.
== Crew Restrictions ==


===Crew Restrictions: Special Concerns===
Given the physical demands expected of Exploration, as well as the high relative danger they are exposed to, the following restrictions apply to candidates:


*Due to concerns regarding the physical demands expected of [Exploration], including but not limited to resilience and physical strength, Central Command has determined that any NanoTrasen employee under [2'6"/76.2cm] may not be employed on any NanoTrasen facility [Exploration] team. Transfer to the [Exploration] department after the assignment of another Departmental role is equally unlawful. However, employees matching [disqualifying criteria (2'6"/76.2cm)] may volunteer for, and be selected to go on, scientific expeditions as auxiliaries. This ruling may be appealed in the future.
* No one below the height of 2’6” may be hired to Exploration.
**This policy has the following exceptions: NanoTrasen employees may be employed by the [Exploration] department if fulfilling the role of [Pilot/Aviator]. All other provisions apply.
* No one belonging to the following species / races may be hired to Exploration:
** Xenochimera
** Adherents

Latest revision as of 23:39, 19 March 2024


SoP: Exploration

Fleet Operations

This page is relevant for those working aboard a NSV/NEV-class installation.

Inside contains special procedures and protocols necessary for the successful operation of a Nanotrasen excursionary vessel.

Primer

Whereas planetary bases and orbital stations are often the go-to installations for a given sector, Nanotrasen’s top of the line vessels are utilized for scouting and investigation of the great unknown.

You will often operate at distances that make response teams and rescues infeasible, or in some cases, impossible. With great risks come great rewards, however - compensation is greatly increased for those willing to weather the stresses of deep-space exploration.

Vessels

New-generation NEV/NSV-class cruisers built after 2560 come with a variety of features to improve crew safety, comfort, and efficiency, including:

  • Civillian decks and staffing, including a full entertainment and catering suite.
  • In-built mini-dormitories, and a full cryosleep solution for when one can’t make it to the next step.
  • Proper facilities for Heads of Staff, and safe rooms for emergency protection.
  • State-of-the-art FTL transit (pending) and repulsor generators.
  • Matter-beam disperser generators for emergency path-clearing operations.
  • A full complement of department transit shuttles, as well as general purpose scouting shuttles within a hanger deck.
  • Redundant reactor cores and power generation.
  • And more!

Command

On NEV/NSV-class installations, Command obtains additional responsibilities other than simply managing their department.

  • All heads of staff are expected to:
    • Be EVA trained, or obtain EVA training within one week of posting.
    • Be trained in disaster response to common scenarios aboard a Nanotrasen vessel, including but not limited to fire, boarders, and structural damage.
    • Assist in the operations of the ship, in addition to their department. The ship comes before your department.
  • Command is responsible for organizing flight plans, shuttlecraft operations, and excursions.
  • Command is responsible for planning the route that the ship will take to accomplish its directives.
  • Command is responsible for monitoring the ship’s status, and undertaking necessary actions to protect the ship’s integrity.
    • Remember: There is no emergency transfer shuttles in deep space. Current-generation NEV/NSV-class cruisers are versatile, and valuable assets to the Company. Abandoning the ship is an absolute last resort.
  • Bridge Officers are elevated to the role of pseudo-command in terms of sector and voidcraft operations on these vessels, as opposed to mere secretaries and coordinators.

Pilots

Anyone piloting a vessel / shuttlecraft must strictly adhere to the following restrictions:

  • Pilots must be trained for duty for the class of vessel they are operating.
    • Learner pilots must be accompanied by a trainer while flying. They may not fly alone.
  • Pilots must keep communications open with Engineering for callouts on ship statuses and potential problems.
  • Pilots must be of sound mind and without any disruptions to their judgements.
    • Alcohol, Ambrosia, and other recreational substances are strictly prohibited while on-duty.
    • Any psychological conditions documented must be cleared by Medical Staff for someone to be eligible to be employed as a Pilot.
    • Any unexplained & volatile alterations to behavior or suspected tapmering mid-operation is acceptable cause to switch out a Pilot until mental state may be ascertained.
  • A pilot is considered on-duty and flying for the full duration of the operation.
    • Stopping at a planet does not mean you are off-duty and free to drink. Remember, you may need to move at a moment’s notice.
    • The only exception is if there is an on-call replacement for you who is ready and willing to go in your place.
  • Pilots are held to a higher standard for availability while on duty. If you require private time, clock off.
  • Pilots should avoid flying alone.
    • There are many circumstances where this is not possible to mandate. Thus, make a best-faith attempt at ensuring a backup is able to take over in case of incapacitation.
  • Pilots are not obligated to maintain a presence on board their vessel at all times - only to maintain the capability to fly it.
    • Pilots should not be ordered to remain behind to 'guard' a parked vessel. They are free to disembark and join an active mission at will.
    • The Pilot is still responsible for the security of their assigned vessel. All reasonable measures must be taken to ensure NanoTrasen property cannot be stolen before the Pilot may disembark.

Exploration

NSV/NEV-class installations are generally operated to scout, as well as investigate points of interest within their local sectors. As such, they are staffed with a variety of shuttlecraft to facilitate crew movement.

  • No crewmember is obligated to partake in excursions, other than designated roles like the Pathfinder and Pilots.
  • No crewmember is inherently disallowed from partaking in excursions under all circumstances.
    • Crewmembers should be deployed based on the mission’s need and one’s skill-set. You would not bring non-combatants to a bug hunt, and you should not bring only combatants to a beacon station during a repair operation.

Away Teams

Away teams may be formed, and deployed, in these circumstances:

  • Command authorization. This obviously overrules all of the below.
  • Pathfinder authorization; this only applies to the Pathfinder’s excursion shuttle.
    • Only the Research Director or the Captain may veto such a launch.
  • Bridge Officers authorizing an excursion when there is no Command available.
    • Bridge Officers may not utilize the Pathfinder’s excursion shuttle or equipment without their explicit permission.
    • Bridge Officers may not abandon the ship to pilot shuttlecraft themselves unless there is available personnel to man the bridge in their place, and there are no pilots willing / wanting to pilot.
  • Pilots authorizing an excursion when there is no Command available.
    • Pilots may not utilize the Pathfinder’s excursion shuttle or equipment without their explicit permission.
    • Bridge Officers may veto the launch during an emergency.
  • Heads of Staff, and department staff in general, may utilize their own department shuttlecraft, if one exists, for any purpose constituent to their department’s operations.
    • Command staff may veto the launch even if it is not their own department - the department head and the Captain obvioulsy overrule in these cases, if they exist.
    • Bridge Officers may veto the launch during an emergency.
  • For anyone but the Pathfinder, it is expected to obtain permission from the relevant head of staff before launching, if one exists, or Command / Bridge Officers in general, if they don’t. It is unacceptable to take shuttles out wordlessly.

Transit & Navigation

The broad responsibilities of Pilots, Bridge Officers, and the Command staff include the transit and navigation of the installation and any provided shuttlecraft during the pursuance of assigned directives.

Maneuvers

The Command staff is expected to communicate with pilots during ship maneuvers. Newer ships contain a variety of specialized shuttlecraft, and performing safe transit while

  • Preplan all routes if at all possible.
    • This will usually not be feasible due to limited data on sector topography.
  • Ensure all shuttlecraft have knowledge of the primary installation’s motion. Shuttlecraft are unable to operate for long periods without a host ship, and searching for a lost shuttlecraft is not just time-consuming, but also puts its crew at risk.
  • Observe minimal safe distance from encountered hazards.
    • Flying through hazards is to be avoided.
    • Clipping the edge of an asteroid belt (or worse) can still result in ship damage.
  • Observe maximum safe speed for your ship / shuttle’s stopping distance.
    • You should be able to stop in time for a hazard popping up on sensors - longer sensors, and/or better propulsion allow for higher allowances on braking distance.
  • Ensure knowledge of all maneuvers are received by coordination on the Bridge, if at all possible.

Takeoff / Landing

Shuttlecraft perform many maneuvers during the course of a shift. They are deadly to anyone caught inside a hanger bay during landing!

  • Always radio in before docking. Give at least ten seconds for the hanger to be cleared.
  • Always respect landing lights. Shuttlecraft approach at extreme speeds, and will easily kill an unprotected individual upon impact!
  • Always clear out of the hanger during shuttle docking / undocking. It is not worth the risk.
  • Do not hang around inside the hanger longer than necessary. Other ships may need to take off and land.

Encounters

While the Frontier is a sparse place, common exploration of the assigned sector-groups may place the crew in contact of other spacefaring factions.

  • Registered Corporations are not to be interfered with, unless a Nanotrasen Employee is in danger, or there is a suspected breach of Admiralty Law.
  • Unregistered vessels should be treated with caution and scrutiny. Privateers and free-roaming mercenaries are not unheard of, and the installation is not equipped for a protracted conflict.
  • Command is in charge of first-contact communications when at all possible, whether towards lesser-known colonies / vessels or towards unidentified species!
  • A full Command staff discussion must be conducted before authorizing unregistered vessels to physically dock with the installation, or approach within boarding distance.

FTL Travel

Most shuttlecraft are unable to sustain their own transit engines for FTL jumps.

As such, the primary ship must exercise caution as to not leave crewmembers behind. Communications from other sectors can be impossible - Coommand must ascertain the status of all shuttles prior to transit maneuvers.

It is not acceptable to leave crew behind during a jump outside of an absolute emergency.

Shuttlecraft

A full set of shuttlecraft is usually provided to frontier installations for the purposes of exploration, scouting, and retrieval.

Shuttlecraft clearly marked as a departmental utility shuttle are under the command of their respective departments, and the (acting) Captain.

All other shuttlecraft are operated and managed by pilots and bridge officers.

  • Pilots have priority for shuttlecraft. Bridge Officers are there to handle ship operations first and foremost, and should only fly as a backup, if at all.
  • Much like with heads of staff, bridge officers may not leave the ship to fly a shuttle if there is no one else to handle the bridge, or if a head of staff prohibits them from leaving.
  • Pilots do not have authority over department shuttlecraft. They may only take them if the department in question (or the acting / Captain) gives permission to do so.

Piloting

In addition to the usual guidelines for pilots, shuttlecraft pilots should be aware of the following guidelines:

  • Always file flight plans. Given the current lack of networked management systems, even a PDA and confirmation from a Command member, a bulletin posted in the bridge, etc, are acceptable. This makes recovery easier in the event of an emergency.
  • Secure your shuttle. Losing it can end with you marooned, or worse. The shuttle is often your only reliable source of long range communications, as well as extraction.
  • Use the distress beacon sooner rather than later - optimally the moment control is near-permanently lost, or structural integrity is heavily compromised. You do not want to fall unconscious before sending out a distress call.
  • You bear the burden of responsibility for ensuring everyone makes it safely to a destination, and back. Ensure continuous headcounts are done.
    • Even if someone else is directing the mission, you, as a pilot, must be aware of your crew. There is no excuse for being unaware of a missing crewmember, or in some cases, an extra.

Maintenance

Shuttlecraft sustain damage far more easily than larger ships. As such, some special guidelines are in place for shuttle operations.

  • Exercise caution while flying, especially if you do not have a shield. A bad hit from a meteor can easily render vital systems inoperable.
  • Light damage can usually be repaired with materials on hand. Be sure to check for hidden issues, like broken wiring and gas pipes underneath flooring.
  • If a shuttle has sustained systems damage, it is best to return to base for repairs as soon as possible.
  • Shuttles with damage that severely impact operations are not allowed to be used for missions outside of a dire emergency.
  • Always charge the SMES before every trip. It is usually your only source of power while on excursion, and losing power mid-flight is often lethal.

Special - The Exploration Department

Some installations, usually planetary / orbital stations, are fitted with a standing Exploration department.

The Exploration department is the standby away team of an installation, led by the Pathfinder.

The Pathfinder

The Pathfinder retains their regular duties of scouting and away operations. The only difference is that they now have a full departmental staff at their back and call.

The Pathfinder is considered senior staff within the Research department, and work under the RD, with specific exceptions. Chain of Command specifies what the relationship between the Pathfinder and the RD is.

The Department

On such installations, the Pathfinder is often given a far more equipped department. One can expect to find:

  • A full briefing room
  • A miniature rescue bay
  • A pilot’s prep room
  • An explorer prep room
  • Extraneous areas otherwise built into the ship or spread out elsewhere
  • Heightened security measures
  • Any additional shuttles provided in addition to the exploration cruiser, like the prototype scouting vessel.

The Exploration department further receives additional staffing of a number of Explorers and Field Medics. Pilots are granted access, as it is expected that pilots fly for the Pathfinder outside of circumstances dictating otherwise.

  • It is recommended to bring additional crew, like sappers, security escorts, etc, as necessary.

The Exploration department, much like the Pathfinder, still answers to the Research Director while not on an away mission. Chain of Command specifies the specifics of its command structure, in cases of disagreements.

Excursions

The following guidelines must be met for excursions:

  • The minimum team size is two. Even a Pathfinder should not be going out alone, outside of emergencies.
  • Only a Pathfinder, RD, or (acting) FD may authorize an expedition.
    • If one does not exist, a fax to Central Command suffices if no negative response is received within five minutes.
    • In these cases, the minimum team size is raised to three.
    • This may not be done within the first 15-30 minutes of the shift. It is not acceptable to take the shuttle out during this time, as a Pathfinder / RD may still be on ths way.
  • As per Chain of Command, the RD / (acting) FD may veto an expedition. This is unlikely to come into play under normal circumstances.
    • A Pathfinder is expected to notify the RD, or if one does not exist, the FD, of an excursion five minutes or more in advance of departure. They do not have to wait for a confirmation.
  • The shuttle must be secured at all times.
    • The shuttle is your lifeline. Losing it can mean marooning, or worse.
    • If going to a hostile sector, ensure one person who is armed stays behind to watch the shuttle. This is usually the pilot.

Weapon Permits

The Exploration department is given weapons permits valid on an away mission only.

Members and volunteers may freely carry weapons inside the department for staging purposes.

All weaponry must be stored in a reasonable location while not in use.

Bringing any armamanets, including one’s machete, outside the department is not authorized by the provided permit.

Crew Restrictions

Given the physical demands expected of Exploration, as well as the high relative danger they are exposed to, the following restrictions apply to candidates:

  • No one below the height of 2’6” may be hired to Exploration.
  • No one belonging to the following species / races may be hired to Exploration:
    • Xenochimera
    • Adherents