OOC I realise I keep making a new thread for this every time. Well no more! Ship damage reports for any event can go here. Template provided below. Examples of damage reports can be seen here.
<abbr>SHIP NAME</abbr>
U.S.S. Ship
<abbr>COMMANDING OFFICER</abbr>
CAPT C. Officer
<abbr>MISSION</abbr>
*~insert link to AAR here~*
<abbr>STATUS</abbr>
*~delete as appropriate~*
[color=limegreen] Operational [/color]
[color=orange] Combat Ineffective[/color]
[color=red] Non-Operational[/color]
<hr>
<abbr>SYSTEMS</abbr>
*~edit as appropriate~*
|System|Status|Damage|
|-|-|-|
|Offensive|[color=limegreen] Online [/color]|No damage reported
|Defensive|[color=yellow] Online [/color]|Minor shield damage
|Impulse|[color=orange] Damaged [/color]|Three impulse drives damaged
|Warp|[color=red]Offline [/color]|Warp core ejected
|Sensors|[color=limegreen] Online [/color]|No damage reported
|Computer|[color=limegreen] Online [/color]|No damage reported
|Communications|[color=limegreen] Online [/color]|No damage reported
|Hull Integrity|[color=limegreen] Stable [/color] /[color=orange] Unstable [/color]/[color=red] Compromised [/color]|No damage reported
<hr>
<abbr>Decks</abbr>
* Deck 1: [color=darkred] Evacuated [/color]
* Deck 2, 3, 4: [color=red] Major Damage Sustained [/color]
* Deck 6, 7, 9: [color=orange] Moderate Damage Sustained [/color]
* Minor damage on all remaining decks
<abbr>CREW</abbr>
* KIA:
* MIA:
* WIA:
* Refugees:
* Prisoners:
<hr>
<abbr>NOTES</abbr> Any notes about the ship can be placed here.
<hr>
<span class="argobox ooc"><abbr>OOC</abbr> Any OOC information tied to this report can be listed here.
</span>
NOTES Ship was damaged by concentrated fire from a Terran dreadnought and its supporting vessels after performing an energy-intensive attack maneuver against said dreadnought during opening salvo of defensive efforts in Denovora system. Ship was rendered crippled after sustaining direct torpedo fire to forward saucer section and main hull and by resulting EPS overload (partially due to sudden total shields failure), but was defended and subsequently towed by other Starfleet vessels in the formation. Engineering teams managed to contain a breach of the warp core, and restore systems damaged by the EPS overload. Relative age of ship systems combined with recent necessary overhauls made underway may have contributed to severity of EPS failure.
Phaser systems operating at 50% effectiveness, Torpedo systems operating at 30% effectiveness
Defensive
Offline
Major Shield Damage
Impulse
Damaged
Right Impulse Drive Offline
Warp
Damaged
Left Nacelle damaged, warp field coils fused in Left Nacelle
Sensors
Online
No damage reported
Computer
Damaged
Primary Computer core operating at half capacity, and due to hull breach in the area, repairs unable to be carried out, by onboard engineering teams.
Communications
Online
No damage reported
Hull Integrity
Stable
Multiple Hull breaches contained by emergency forcefields, multiple dents across external hull plating
Decks
Deck 3: Evacuated
Deck 6 and 18: Major Damage Sustained
Deck 22: Moderate Damage Sustained
Damage on all remaining decks
CREW
KIA: 28
MIA: 2
WIA: 62, including CO, XO, Chief Operations Officer and Chief Engineering Officer.
Refugees: 0
Prisoners: 0
NOTES
Due to attempts by the Defender to draw the attention of hostile Warbirds from other damaged Starfleet Vessels, additional damage was obtained, attempts however where unsuccessful resulting in no reduction in damage to other Vessels.
Whilst the Defender is able to limp back to port for repairs, it remains combat ineffective with multiple phaser arrays disabled, and multiple torpedo tubes also disabled, in addition to this the ship’s Captain yacht was fused into it’s docking port, with the underside of the yacht also damaged and in need of repairs.
OOC First damage report, please let me know of any issues and I will correct them as needed
Topside warp nacelle offline, top speed is Warp 6.5
Sensors
Damaged
Primary senors down, tactical sensors unaffected, secondary systems down to 40% effectiveness. Internal sensors damaged.
Computer
Damaged
Computer core damaged, connection to Starfleet mainframe and database are unavailable. Replicators offline.
Communications
Damaged
Internal communications down, ship to ship unaffected
Hull Integrity
Unstable
Hull armor plating compromised but still holding at 18% effectiveness. No breaches to Hull.
Decks
Minor damage on all decks
CREW
KIA: Thirty Six
MIA: Two
WIA: Sixty Three
Refugees: N/A
Prisoners: N/A
NOTES Additional damage reported, Tractor beam emitters are offline, 80% of the emitters destroyed. Sixteen fighters lost, unable to replace due to loss of replicators. Main deflector dish offline, secondary deflector dish at 78% capability. Life support stable. Suspected hairline fractures within the starboard warp pylons.
Shields buckled during battle. Restored after battle.
Impulse
Online
No damage reported
Warp
Damaged
Port nacelle disabled. Can maintain warp 7.
Sensors
Damaged
Targeting sensors down.
Computer
Online
No damage reported
Communications
Online
No damage reported
Hull Integrity
Unstable
Breaches reported, see below
Decks
Deck 3: Evacuated
Deck 12: Hull breach. Breach patched
CREW
KIA: 37
MIA: 2
WIA: 45 including XO
Refugees: 905
Prisoners: 6
NOTES Forrestal made her way to DS13 under her own power and has since pulled into drydock for extensive repairs due to damage from this and prior engagements.
OOC Forrestal’s drydock time will coincide with my RL vacation time!
Stress damage to phaser-lance cannon, related power systems
Defensive
Online
Moderate damage to main deflector
Impulse
Online
No damage reported
Warp
Online
No damage reported
Sensors
Online
No damage reported
Computer
Online
No damage reported
Communications
Online
No damage reported
Hull Integrity
Stable
Decks
No damage on all remaining decks
CREW
KIA: 0
MIA: 0
WIA: 0
Refugees: 0
Prisoners: 0
NOTES The ship is in fully functional condition, but there are two areas that need a bit of repair and overhaul. Engineering had already been replacing many power conduits and junctions with more robust components, and catastrophic damage in some areas of the ship may have been possible without this. However, the phaser-lance cannon was utilized in a continuous-beam fire mode with higher than recommended power levels, for extended periods of time on this mission to destroy hardened electronic warfare platforms. While still functional, Engineering has identified several areas of metal fatigue, slight warping in the focusing apparatus, and other wear-induced issues that will become problematic with time and continued use. Separately, while utilizing a high-powered anti-graviton beam from the main deflector in conjunction with USS Mariner to defeat an advanced enemy shield, a feedback pulse did hit the main deflector. It is operational, but damage was sustained that will also degrade into complete failure with time and continued use. Current deflector effectiveness estimated at 40%.
Some repairs will need to be started via EVA activity while the ship is powered-down and at station-keeping. Other internal repairs can be continued by Engineering personnel while underway again, and will not require the full attention of drydock personnel to be taken away from ships more in need.
USS Dragon has returned to Starbase Deep Space 13 in stable docking orbit while repairs are affected, and personnel rotate for shoreleave.
Weapon systems themselves appear to be undamaged besides some minor scorching to aft-most emitters on the port-upper-nacelle phaser array, but damage to the EPS grid has rendered all but one phaser array inoperative at present
Defensive
Offline
Shield grid was overloaded during battle. An emergency, temporary restoration caused EPS burnouts across the grid and across the ship, and shields are currently inoperative
Impulse
Damaged
Port-saucer impulse nacelle sustained minor damage, primary stardrive impulse nacelle undamaged. Widespread power grid damage is affecting ability to route fusion power to certain systems.
Warp
Damaged
Current maximum speed of warp four (Chief Engineer recommends against any use of warp drive at all, due to power difficulties affecting supporting systems), widespread damage to EPS grid
Sensors
Online
No damage reported
Computer
Errors
Primary computer core is physically undamaged, however EPS grid issues are causing processing and data recovery errors, and making diagnostics of other systems difficult
Communications
Online
No damage reported
Hull Integrity
Unstable
Minor hull breaches across portside. No risk, but will require patching.
Decks
Deck 21 - 26, 34, 37: Moderate Damage Sustained
Most decks experiencing power brown-outs and black-outs. Power to Deck One (Primary Bridge) is maintained by its own backup systems, and Deck 42 (AM storage) has been equipped with a portable fusion generator to maintain power until these issues can be resolved. Engineering decks appear to be stable, though a minor hull breach on deck 37 has necessitated two workspaces remain sealed.
CREW
KIA: 2 (Lt Cmdr Ellen Vorderman, Engineering; Ensign Kuot Tam, Tactical - shipboard mourning service due to take place this Wednesday)
MIA: 0
WIA: 134
Refugees: Several thousand rescued from planet’s surface; medical department still conducting examinations/census. Housed in pre-existing refugee bays for the time being
Prisoners: 0
NOTES While Vincennes’ shields bore the brunt of the sudden attack, the ‘flash damage’, as Cmdr Fodd has taken to calling it, and resultant emergency measures our engineering team took to keep Vincennes operating under her own power in the immediate aftermath, has caused considerable damage to multiple aspects of the EPS grid. This is making it difficult to maintain (or even establish) power to many systems despite our powerplants and emergency batteries being undamaged, which in turn is causing difficulties in diagnosing problems with those systems which are confirmed to be damaged. In the meantime, portable generators are being used to ensure continuous power to critical systems until such a time as the EPS grid can be rendered reliable.
OOC I can’t remember the figure I said as to how many people Vincennes managed to beam up before I had to leave
Secondary deflector offline, EPS flow to main deflector disrupted, long-range sensors inoperative
Computer
Online
No damage reported
Communications
Online
EPS flow disrupted
Hull Integrity
Unstable
Multiple hull breaches sustained, major breach to dorsal starboard-side saucer section, minor breaches to forward saucer section and port-side secondary hull
NOTES The Heimdall sustained a direct hit from a Romulan plasma torpedo in opening engagements, and subsequent significant damage while executing a flanking offensive maneuver in conjunction with U.S.S. Pegasus as ordered. Ship remained combat capable at this time. Further command decision to remain on the forward combat line resulted in exposure to overwhelming force while attempting to break through the final wave of Star Navy heavy vessels.
Heimdall’s EPS grid still appears unstable after noted failures early in the Romulan conflict, theorized to be partially resulting from design flaws in the vessel class’ high-throughput system, and possibly magnified by the nature of Romulan plasma weaponry. Energy weapon and shield systems in particular appear to place greater-than-average strain on the conduit network, a drawback of higher available energy output and greater rerouting speed.
Shortened time-frame repairs at improvised facilities within the Fvillhaih system, after substantial damage sustained during fleet action in the capture of that system, likely contributed to ship operating at lower efficiency during Operation Edelweiss. This is indicated by evidence of stress failure to ship systems previously damaged at Fvillhaih.