---
# System prepended metadata

title: 'SoP: Exploration'

---

# 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.

# 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. [[SoP: Chain of Command|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. [[SoP: Chain of Command|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
