Starships, Space Stations, Small Craft, and their Components.
Education
Food
Grocery
Tourism
Agriculture
Entertainment
Technology
The My-T1-1A Phoenix Dropship was developed as a transportation platform for the My-M1-1A Variable Configuration Drop Pod. It entered service in YE31.
 |  |
| Back View | Diagonal View |
 | |
| Front View |
When the UOC Drop Pod was proposed as a design questions arose about a possible delivery platform for the pod. Designers of the pod felt that to make the most effective use of the rapid deployment and recovery an additional platform would need to be developed. The Phoenix was the result of that proposal, a shuttle that could carry up to 4 VCDPs at a time. The Phoenix was named after the mythological bird that symbolizes rebirth. It brought the ability to restore a city, an island, a country, and a people out of the ashes of war, disaster, and destruction.
After its initial design however another purpose was realized for both the Phoenix and the pods it carry: freight transport. Though the craft is merely a shuttlecraft, when 4 VCDPs are attached over 64,000 cubic feet of storage space is available. This allows the Phoenix to rapidly transfer large quantities of supplies and equipment between ships, from planet to space, or even between solar systems. Once designers realized this the second goal for both the Phoenix project and it's accompanying drop pod was to replace traditional cargo shuttlecraft for the UOC.
While capable of carrying passangers and a crew the cabin area available is significantly smaller than the Jilanth T2 Military Shuttle, the standard dropship for UOC personnel.
See Damage Rating (Version 3) for an explanation of the damage system.
Organizations Using This Vessel:
Type: Shuttlecraft Class: Phoenix Designer: Motoyoshi Fleet Yards Manufacturer: Motoyoshi Fleet Yards
Crew: 2 Maximum Capacity: 10 passengers comfortably
| Category | Type | Class | Sublight Engines | CDD | Hyperspace Drive |
|---|---|---|---|---|---|
| 7 | Fast Shuttle | Phoenix | .4c | 17,500c | None |
Speed (Aerial): Mach 5 Speed (Water): Mach 1
Range (Distance): Theoretically unlimited since it uses a Link Siphon as a power source, however due to lack of a hyperfold drive it would take a long time to go very far. Range (Support): Effectively unlimited due to the extremely efficient recycling systems Lifespan: 25 years Refit Cycle: For the most part the Phoenix only needs minor refits once every 3 years, however after every VCDP deployment the mounting clamps should be checked. The clamps should be replaced during a minor refit.
In spite of the height and width of the Phoenix the crew cabin is actually quite small. For the most part the Phoenix is composed of very large engines designed to support the weight of the VCDP cargo it carries in an atmosphere as well as to still be able fly with its shields offline to drop the pods. Because of that the crew cabin is actually in an extended pod on the bottom of the craft. The fore section of the pod consists of 2 pilot terminals, and the aft much like the VCDP can be configured to whatever the mission needs though is usually used to transport people and equipment. Both pilot terminals are in the same cockpit, arranged in a side by side fashion and separated by a thick wall and reinforced door from the rest of the crew cabin.
The Phoenix's systems are all run by the MIKO Electronics Suite. Standard configuration for the Phoenix is the [CORE] module. Usually this is more than sufficient, however there are times when no starship will be present or the situation demands it that further modules are added. The most common additions are the [Science and Explorer] and [Support] modules. The [Science and Explorer] module is usually deployed when the ship will not be present but communication between the two must be maintained. It also allows ground installations to be prepared for attacks with a superior sensor suite. The [Support] module is only deployed during an extremely large scale relief operation where a vessel with the Gateway-M logistical management software package is necessary but unavailable.
| Type 2A Construct Assembly | |||
|---|---|---|---|
| Frame | Durandium Alloy Truss and Titanium Boron Carbide rod frame | ||
| Lining | Yarvex Lining | ||
| Outer Layer | Carbon-Ring | ||
Reimei 'Twilight' Gravimetric Drive
| Statistics | |||
|---|---|---|---|
| Model | Reimei | ||
| Type | Shuttle/Fighter/Bomber/Small Craft Gravimetric Drive | ||
| Performance Maximums | .4c | ||
| Range | Limited to the power supply/vessel design | ||
| Statistics | |||
|---|---|---|---|
| Model | Ripple | ||
| Type | Shuttle/Fighter/Bomber/Small Craft Continuum Distortion Drive | ||
| Performance Maximums | 17,500c | ||
| Range | Limited to the power supply/vessel design | ||
| Maintenance | All distortion field coils, field regulators, and other components require repair or replacement as needed. | ||
| Coil Ejection System | Included: Entire coil nacelle can be separated from vessel | ||
Type 30 Link Siphon (Retconned)
The shields of the Phoenix are by default set up as a bubble that surrounds the ship as well as any attached drop pods, though it can be set to just cover the hull of the craft.
Spaced along the hull are 16 docking clamps designed to hold the VCDPs in place while in flight. These clamps are made from reinforced durandium alloy and designed to take a beating before failing. Each VCDP is held firmly in place by 2 sets of clamps, one set at the fore of the pod and the other at its aft. For pods mounted above the engine array the clamps fit snugly into place into grooves and around a reinforced durandium rod on the bottom of each VCPD, for pods mounted below the engine array the clamps fit snugly into groves and around a reinforced durandium rod.
Usually this form of pod deployment is used when the pods must be deployed quickly. The shuttle could be taking enemy fire or have failing systems, or their isn't time for a standard drop procedure. Using this mode a landing site must be chosen, once it is the ships MIKO will calculate when to drop based on ship speed and any other relevant factors. At drop time the shields must be taken off-line and the added wind resistance will assist the pods in not only escaping the ship, but also slowing them down before they hit the ground. As soon as the shields go offline the ship's MIKO will commence drop routine which consists of releasing the docking clamps and allowing the pods to seperate from the ship. The ship's computer will manually pilot each pod down to its landing site or as close as is possible.
Using this drop procedure the Phoenix manually sets the bottom two drop pods down at the appropriate coordinates. The pods located above the engine array will be flown using the ships MIKO to pilot input or designated mission coordinates. The Pheonix will need to be in close proximity to these coordinates however, as the drop pods do not have very strong thrusters nor do they have very large plasma stores.
