We All Fall Down – Preliminary Incident Report 896-BRAVO-645-SIGMA-984
by Colonel James Darson
Post Details
ON:
<> SFMC – MARINE CORP INTELLIGENCE DIVISION (MCID)
<> INCIDENT REPORT – 2392.03.24.1200.P1.CO.00001
<> <*WARNING: ALL QUERIES WILL BE LOGGED!>
[MCID.SEC.PRTCL-QKL]
<> PUBLIC KEY: 154998719AD-624
<> PRIVATE KEY: RED
<>FILE NUMBER: 896-BRAVO-645-SIGMA-984
<> SUBJECT MATTER: OPERATION “POOLING WHIPPETS” DEEP SPACE 5 GUARDIAN PLATFORM INCIDENT PRELIMINARY REPORT
<> SECURITY CLASSIFICATION: SECRET//LEVEL 9 CLEARANCE REQUIRED//SIGMA 8//DTER//FTER//LES//ORCON//NOFORN//NOCONTRACT
<>FULL DISSEMINATION:
SFMC_HIGHCOM
SFMC_INTCOM
SFMC_UNICOM
SFMC_OPCOM
SFMC_OI (INVESTIGATION)
SFMC_SPECWEP [REDACTED]
STARFLEET_NAVCOM
STARFLEET_FLEETCOM
STARFLEET_INTELLIGENCE
STARFLEET_SECURITY (INVESTIGATION)
JUDGE_ADVOCACY_GENERAL
MARSHALS_SERVICE
<> SPECIAL DISSEMINATION (CLEARANCE GRANTED FOR THIS FILE ONLY)
DEEP SPACE 5
CO: CMDR T’VAUREK, ISHA (INTERIM CO, FORN [ORCON: OVERRIDE NOFORN], ASSET: “EVERGREEN”, [LOG ACCESS])
XO: LCMDR WALLACE, JARRED (SF INT, TRANSFER PENDING, [LOG ACCESS])
CSO: ENS HARRIS, DAVID (ASSIGNMENT PENDING [LOG ACCESS])
ACSO: LT TRELLIS, SI’LAR ([LOG ACCESS])
CIO: LT LOCKE, MIKAELA (ASSIGNMENT PENDING, SF INT, [LOG ACCESS])
CDM: DEP STEINER, WOLFGANG (MARSHAL, [LOG ACCESS])
MXO: MCAPT FLYNN, MIRANDA ([LOG ACCESS])
MILO: 2LT CHAU’SAURA CALSO ([LOG ACCESS])
<> FILE ORIGIN
COL DARSON, JAMES
MCO, DEEP SPACE 5
6th COMBINED OPERATIONS GROUP
9TH MARINE DIVISION
<>FILE AUTHOR
2LT CHAU’SAURA CALSO
MILO, DEEP SPACE 5
6TH COMBINED OPERATIONS GROUP
9TH MARINE DIVISION
<>KEY WORDS: SUSPECTED ACCIDENT, EQUIPMENT MALFUNCTION, SUSPECTED TERRORISM, WAFFLES, DOMESTIC TERRORISM, FOREIGN TERROISM, GUARDIAN PLATFORMS, WEAPON TESTING, LOSS OF LIFE, CASUALTIES
<> CONTENT BEGINS:
Please note that this has been a preliminary report filed by the Marine Regiment, as required by protocol. More information will be submitted when it becomes available.
An active case file has been started. All other departments and agencies, please attach all relevant reports using the master directory code and direct all links accordingly.
This is a preliminary report on the friendly fire incident that occurred during the testing of the GUARDIAN class defense platforms at Starbase Deep Space 5, on Stardate 69345. Contained within this document is a timeline of events, a summary of personnel and material lost, and preliminary findings as of 12 hours post-incident.
For several months prior to the incident in question, Starfleet had been working on reverse-engineering Cardassian defense drone technology, primarily based upon the planetary defense network in place at Chin’Toka during the Dominion war (See First Battle of Chin’Toka for more information). Engineering efforts were focused on solving the crucial failings present in the Cardassian implementations, as well as performing a full up-conversion to Starfleet standards. Specifically the installation of on-board reactors, Federation-spec weaponry and next-gen communications technology in order to circumvent traditional electronic countermeasures. Specifications and blue-prints remain classified, and will be issued to investigative personnel on a need-to-know basis.
On the day of the incident, testing was scheduled for 1500 hours, with members of both Starfleet and the Marines in attendance. It is well-documented that numerous bulletins had been issued by station personnel warning residents that the weapons testing range coordinates [Coordinates Appended] were off-limits and to be vacated by all unofficial personnel by 1300 hours on the day in question, extending another two hours past the expected conclusion of the platform test. Bulletins were also posted to all civilian and military traffic hubs with trade routes connecting to Deep Space 5, as well as the automated station status report. While the exact nature of the test was withheld from the general public for security purposes, the fact remains that it was well known that the area was restricted during the specified times.
The test was conducted from Main Operations on Deep Space 5, with all local station operations diverted to secondary stations for the duration of the test in order to not compromise integrity of the test. Alpha shift personnel were on hand for operational control during pre-flight checks and the testing operation itself. Also present were the station’s senior staff and Commodore [Redacted]. The timeline of events is documented below:
1200 (T-3.00 hrs): GUARDIAN platform maintenance
1300 (T-2.00 hrs): GUARDIAN platform final checks
1305 (T-1.92 hrs): Civilian ship strays close to designated testing range, contacted and redirected to new course heading. Ship complies.
1310 (T-1.83 hrs): Testing area declared clear of all ships and personnel. Tactical continues monitoring for any further disturbances
1400 (T-1.00 hrs): Operation pre-checks initiated. Orders and operation parameters confirmed by commanding officer.
1410 (T-0.83 hrs): Telemetry test performed for platforms. All communications reported as four by three, noise present in signal. Determined to not be detrimental to test, watch put on communications, primary array realigned.
1425 (T-0.58 hrs): Telemetry test performed for platforms. All communications reported as five by five, no noise present in signal. All preparations continued as scheduled
1430 (T-0.50 hrs): GUARDIAN platforms secured for live-fire testing. Ordinance loaded and secured in accordance with operational parameters.
1440 (T-0.33 hrs): Operational sub-routines primed and active.
1450 (T-0.17 hrs): GUARDIAN platforms moved to “Rest Mode”, prepared for launch.
1500 (T-0.00 hrs): Operation begins.
1501 (T+0.02 hrs): ADHA Generators active at 99.2% efficiency. GUARDIAN platforms reported all systems operating within operational parameters.
1502 (T+0.03 hrs): Commanding officer issues go-order. Platforms 1-7 disengage from station. Flight sub-routines active.
1503 (T+0.05 hrs): Sensors report incursion into testing range by civilian vessel, freighter class. All GUARDIAN platforms sensor back-up flags civilian vessel as Jem’Hadar attack ship, change to pursuit mode, and make course correction to engage. The staff on hand maintained operational discipline and performed several emergency procedures including the following:
Cycle main telemetry uplink to force rescan. – FAILED, platforms rejected new data
Shutdown order processed through main telemetry uplink – FAILED, platforms reject command – anti-intrusion protocols engaged, lockout majority of command protocols disregarded. Operations commands being interpreted as outside source.
Emergency Override Protocols initiated – FAILED, platforms reject override codes, now moving independently of station
Emergency Power Down Protocols Initiated – FAILED, all platform subspace communication modules are now offline.
GUARDIAN platforms move into tactical formation, arm weapons and target freighter. Freighter maintains course.
1504 (T+0.07 hrs): XO Wallace accesses Intelligence File 635 [CONTENT REDACTED]. MCO consulted. MCO scrambles Marine Fighter Squadron, combat payloads, with order to interdict GUARDIAN platforms, orders are to wait until GUARDIAN platforms fire before firing on Starfleet equipment. Rhino Squad Scrambles.
1505 (T+0.08 hrs): Emergency power diverted to Main Transporter array in effort to evacuate civilian crew members from freighter. Starfleet Medical alerted for incoming casualties.
Second civilian ship incursion. Designated civilian transport vessel “Waylorm”. Two GUARDIAN platforms break formation and move to engage the second ship.
1506 (T+0.10 hrs): GUARDIAN platforms engage both targets. CO issues order to focus efforts on protecting the transport ship “Waylorm”, freighter is of secondary concern. It was noted that the manifests of the two ships were compared.
1507 (T+0.12 hrs): Evacuation of “Waylorm” begins by transport of civilians. “Waylorm” issues general order to abandon ship, escape pods begin to launch. Transport takes heavy damage. GUARDIAN platforms initiate electronic countermeasures, jam ship-to-ship communications.
1508 (T+0.13 hrs): XO Wallace and MCO Darson approach Main Computer Core. XO Wallace orders control circuits disabled. No effect. Rhino Squadron engages GUARDIAN platforms, begins taking heavy fire.
1509 (T+0.15 hrs): XO Wallace and MCO Darson enter Main Computer Core chamber. Authorization and exigent circumstances acknowledged. Rhino 6 Destroyed, pilot lost.
1510 (T+0.17 hrs): XO Wallace and MCO Darson open fire on shielded ODN relay housing telemetry uplink. Platform 2 disabled. Platforms 1 and 3 caught in tractor beams. ADHA presents auxiliary target: Borg Cube. Rhino 8 Destroyed, escape pod found.
1511 (T+0.18 hrs): Civilian Freighter warp core breach detected. GUARDIAN platforms 1 and 3 lost, Rhino 11 destroyed, pilot lost. Platforms 4 through 7 disabled.
1512 (T+0.20 hrs): XO Wallace and MCO Darson identify program isolinear chip in computer core which houses a training simulation. Isolinear chip remanded to Starfleet Security as evidence.
1515 (T+0.25 hrs): Station stands down from combat readiness, recovery operation started by Marine regiment, MCO Darson heading it. Sick Bay begins receiving casualties. All personnel with medical experience are assigned to triage.
1520 (T+0.33 hrs): Operation terminated
2000 (T+4.00 hrs): Recovery operation underway, remaining GUARDIAN platforms under guard. Salvage placed under guard. Escape pods recovered, all live civilians recovered. Salvage recovery persists.
MATERIAL AND PERSONNEL:
During this incident, heavy loss of life and material was incurred. The following lists known personnel casualties:
3 Marine Pilots
6 Active Duty Starfleet Officers
4 Retired Starfleet Officers
340 Civilians (Including freighter crew)
2 missing, presumed dead (Check manifests against bodies recovered)
1 Civilian Freighter (Destroyed, Warp Core Breach)
Cargo: Self-sealing Stem Bolts, Feldspar, Beresium Ore
1 Civilian Transport ship (Disabled, towed into dock)
Cargo: Civilians (noted above)
3 GUARDIAN Platforms (Cost CLASSIFIED)
3 Valkyrie Class Fighters (Cost CLASSIFIED)
Misc. Computer Equipment (Bill SFMC)
PRELIMINARY ANALYSIS:
The incident in question is without doubt a considerable tragedy, however me must determine how to apportion responsibility and liability. JAG, Starfleet Security and the Marine CID will each be launching independent investigations into the matter, but will coordinate across task forces to share information.
So far, we have not heard any chatter of foreign or domestic terrorists / rebels / anarchists / agents to suggest that this was a pre-planned operation as of this point in time. However, intelligence analysts will be working to sift through all intercepts and intelligence as well as devoting considerable resources from this point on to determine if this was a deliberate attack. After all, an operation to cripple a potential technology such as this would be a boon to many other state entities with which we enjoy less than cordial relations.
Care should also be given to the idea that this was simply an internal, unintentional malfunction. The isolinear chip discovered could have been the root cause behind the incident, however we must conduct an investigation from the angle that that was the method, rather than cause.
The remaining GUARDIAN platforms are under guard by Starfleet Security and will be hard locked to prevent any activity until they have been disassembled and examined by accredited and certified investigators and engineers (Clearance pending). The salvage from the freighter and the destroyed platforms have been moved to an internal dock on Deep Space 5 and placed under guard by the station Marine Detachment by order of Colonel Darson.
The recovery operation is proceeding according to schedule, and the area containing the wreckage should be cleared within two days’ time of this report. After that, we will open up the area of space to travel once more.
One final note is that of liability. We have already had reports of several claims being filed by civilians who lost property or lives during the incident. Should the investigation bear out that this was a malfunction, Starfleet and the Federation may find themselves liable for damages. As of this report publishing date Deep Space 5 is requesting aid from JAG offices and the State Department to help document and contain this response.
CONCLUSION:
This incident is a tragedy, both for the loss of life and property and the setting back of defense research. All parties involved will be putting forth our best efforts to determine the cause and if necessary locate the perpetrators of this atrocity.
Please forward all applicable information to Starfleet Intelligence and Marine OI/CID.
BREAK BREAK BREAK
OFF:
Colonel James Darson
by Colonel James Darson
Post Details
| Title | Preliminary Incident Report 896-BRAVO-645-SIGMA-984 | |
| Mission | We All Fall Down | |
| Author(s) | Colonel James Darson | |
| Posted | Sun Sep 28, 2014 @ 6:13am | |
| Location | N/A | |
| Timeline | WAFD: Day 02 : 0800 |
<> SFMC – MARINE CORP INTELLIGENCE DIVISION (MCID)
<> INCIDENT REPORT – 2392.03.24.1200.P1.CO.00001
<> <*WARNING: ALL QUERIES WILL BE LOGGED!>
[MCID.SEC.PRTCL-QKL]
<> PUBLIC KEY: 154998719AD-624
<> PRIVATE KEY: RED
<>FILE NUMBER: 896-BRAVO-645-SIGMA-984
<> SUBJECT MATTER: OPERATION “POOLING WHIPPETS” DEEP SPACE 5 GUARDIAN PLATFORM INCIDENT PRELIMINARY REPORT
<> SECURITY CLASSIFICATION: SECRET//LEVEL 9 CLEARANCE REQUIRED//SIGMA 8//DTER//FTER//LES//ORCON//NOFORN//NOCONTRACT
<>FULL DISSEMINATION:
SFMC_HIGHCOM
SFMC_INTCOM
SFMC_UNICOM
SFMC_OPCOM
SFMC_OI (INVESTIGATION)
SFMC_SPECWEP [REDACTED]
STARFLEET_NAVCOM
STARFLEET_FLEETCOM
STARFLEET_INTELLIGENCE
STARFLEET_SECURITY (INVESTIGATION)
JUDGE_ADVOCACY_GENERAL
MARSHALS_SERVICE
<> SPECIAL DISSEMINATION (CLEARANCE GRANTED FOR THIS FILE ONLY)
DEEP SPACE 5
CO: CMDR T’VAUREK, ISHA (INTERIM CO, FORN [ORCON: OVERRIDE NOFORN], ASSET: “EVERGREEN”, [LOG ACCESS])
XO: LCMDR WALLACE, JARRED (SF INT, TRANSFER PENDING, [LOG ACCESS])
CSO: ENS HARRIS, DAVID (ASSIGNMENT PENDING [LOG ACCESS])
ACSO: LT TRELLIS, SI’LAR ([LOG ACCESS])
CIO: LT LOCKE, MIKAELA (ASSIGNMENT PENDING, SF INT, [LOG ACCESS])
CDM: DEP STEINER, WOLFGANG (MARSHAL, [LOG ACCESS])
MXO: MCAPT FLYNN, MIRANDA ([LOG ACCESS])
MILO: 2LT CHAU’SAURA CALSO ([LOG ACCESS])
<> FILE ORIGIN
COL DARSON, JAMES
MCO, DEEP SPACE 5
6th COMBINED OPERATIONS GROUP
9TH MARINE DIVISION
<>FILE AUTHOR
2LT CHAU’SAURA CALSO
MILO, DEEP SPACE 5
6TH COMBINED OPERATIONS GROUP
9TH MARINE DIVISION
<>KEY WORDS: SUSPECTED ACCIDENT, EQUIPMENT MALFUNCTION, SUSPECTED TERRORISM, WAFFLES, DOMESTIC TERRORISM, FOREIGN TERROISM, GUARDIAN PLATFORMS, WEAPON TESTING, LOSS OF LIFE, CASUALTIES
<> CONTENT BEGINS:
Please note that this has been a preliminary report filed by the Marine Regiment, as required by protocol. More information will be submitted when it becomes available.
An active case file has been started. All other departments and agencies, please attach all relevant reports using the master directory code and direct all links accordingly.
This is a preliminary report on the friendly fire incident that occurred during the testing of the GUARDIAN class defense platforms at Starbase Deep Space 5, on Stardate 69345. Contained within this document is a timeline of events, a summary of personnel and material lost, and preliminary findings as of 12 hours post-incident.
For several months prior to the incident in question, Starfleet had been working on reverse-engineering Cardassian defense drone technology, primarily based upon the planetary defense network in place at Chin’Toka during the Dominion war (See First Battle of Chin’Toka for more information). Engineering efforts were focused on solving the crucial failings present in the Cardassian implementations, as well as performing a full up-conversion to Starfleet standards. Specifically the installation of on-board reactors, Federation-spec weaponry and next-gen communications technology in order to circumvent traditional electronic countermeasures. Specifications and blue-prints remain classified, and will be issued to investigative personnel on a need-to-know basis.
On the day of the incident, testing was scheduled for 1500 hours, with members of both Starfleet and the Marines in attendance. It is well-documented that numerous bulletins had been issued by station personnel warning residents that the weapons testing range coordinates [Coordinates Appended] were off-limits and to be vacated by all unofficial personnel by 1300 hours on the day in question, extending another two hours past the expected conclusion of the platform test. Bulletins were also posted to all civilian and military traffic hubs with trade routes connecting to Deep Space 5, as well as the automated station status report. While the exact nature of the test was withheld from the general public for security purposes, the fact remains that it was well known that the area was restricted during the specified times.
The test was conducted from Main Operations on Deep Space 5, with all local station operations diverted to secondary stations for the duration of the test in order to not compromise integrity of the test. Alpha shift personnel were on hand for operational control during pre-flight checks and the testing operation itself. Also present were the station’s senior staff and Commodore [Redacted]. The timeline of events is documented below:
1200 (T-3.00 hrs): GUARDIAN platform maintenance
1300 (T-2.00 hrs): GUARDIAN platform final checks
1305 (T-1.92 hrs): Civilian ship strays close to designated testing range, contacted and redirected to new course heading. Ship complies.
1310 (T-1.83 hrs): Testing area declared clear of all ships and personnel. Tactical continues monitoring for any further disturbances
1400 (T-1.00 hrs): Operation pre-checks initiated. Orders and operation parameters confirmed by commanding officer.
1410 (T-0.83 hrs): Telemetry test performed for platforms. All communications reported as four by three, noise present in signal. Determined to not be detrimental to test, watch put on communications, primary array realigned.
1425 (T-0.58 hrs): Telemetry test performed for platforms. All communications reported as five by five, no noise present in signal. All preparations continued as scheduled
1430 (T-0.50 hrs): GUARDIAN platforms secured for live-fire testing. Ordinance loaded and secured in accordance with operational parameters.
1440 (T-0.33 hrs): Operational sub-routines primed and active.
1450 (T-0.17 hrs): GUARDIAN platforms moved to “Rest Mode”, prepared for launch.
1500 (T-0.00 hrs): Operation begins.
1501 (T+0.02 hrs): ADHA Generators active at 99.2% efficiency. GUARDIAN platforms reported all systems operating within operational parameters.
1502 (T+0.03 hrs): Commanding officer issues go-order. Platforms 1-7 disengage from station. Flight sub-routines active.
1503 (T+0.05 hrs): Sensors report incursion into testing range by civilian vessel, freighter class. All GUARDIAN platforms sensor back-up flags civilian vessel as Jem’Hadar attack ship, change to pursuit mode, and make course correction to engage. The staff on hand maintained operational discipline and performed several emergency procedures including the following:
Cycle main telemetry uplink to force rescan. – FAILED, platforms rejected new data
Shutdown order processed through main telemetry uplink – FAILED, platforms reject command – anti-intrusion protocols engaged, lockout majority of command protocols disregarded. Operations commands being interpreted as outside source.
Emergency Override Protocols initiated – FAILED, platforms reject override codes, now moving independently of station
Emergency Power Down Protocols Initiated – FAILED, all platform subspace communication modules are now offline.
GUARDIAN platforms move into tactical formation, arm weapons and target freighter. Freighter maintains course.
1504 (T+0.07 hrs): XO Wallace accesses Intelligence File 635 [CONTENT REDACTED]. MCO consulted. MCO scrambles Marine Fighter Squadron, combat payloads, with order to interdict GUARDIAN platforms, orders are to wait until GUARDIAN platforms fire before firing on Starfleet equipment. Rhino Squad Scrambles.
1505 (T+0.08 hrs): Emergency power diverted to Main Transporter array in effort to evacuate civilian crew members from freighter. Starfleet Medical alerted for incoming casualties.
Second civilian ship incursion. Designated civilian transport vessel “Waylorm”. Two GUARDIAN platforms break formation and move to engage the second ship.
1506 (T+0.10 hrs): GUARDIAN platforms engage both targets. CO issues order to focus efforts on protecting the transport ship “Waylorm”, freighter is of secondary concern. It was noted that the manifests of the two ships were compared.
1507 (T+0.12 hrs): Evacuation of “Waylorm” begins by transport of civilians. “Waylorm” issues general order to abandon ship, escape pods begin to launch. Transport takes heavy damage. GUARDIAN platforms initiate electronic countermeasures, jam ship-to-ship communications.
1508 (T+0.13 hrs): XO Wallace and MCO Darson approach Main Computer Core. XO Wallace orders control circuits disabled. No effect. Rhino Squadron engages GUARDIAN platforms, begins taking heavy fire.
1509 (T+0.15 hrs): XO Wallace and MCO Darson enter Main Computer Core chamber. Authorization and exigent circumstances acknowledged. Rhino 6 Destroyed, pilot lost.
1510 (T+0.17 hrs): XO Wallace and MCO Darson open fire on shielded ODN relay housing telemetry uplink. Platform 2 disabled. Platforms 1 and 3 caught in tractor beams. ADHA presents auxiliary target: Borg Cube. Rhino 8 Destroyed, escape pod found.
1511 (T+0.18 hrs): Civilian Freighter warp core breach detected. GUARDIAN platforms 1 and 3 lost, Rhino 11 destroyed, pilot lost. Platforms 4 through 7 disabled.
1512 (T+0.20 hrs): XO Wallace and MCO Darson identify program isolinear chip in computer core which houses a training simulation. Isolinear chip remanded to Starfleet Security as evidence.
1515 (T+0.25 hrs): Station stands down from combat readiness, recovery operation started by Marine regiment, MCO Darson heading it. Sick Bay begins receiving casualties. All personnel with medical experience are assigned to triage.
1520 (T+0.33 hrs): Operation terminated
2000 (T+4.00 hrs): Recovery operation underway, remaining GUARDIAN platforms under guard. Salvage placed under guard. Escape pods recovered, all live civilians recovered. Salvage recovery persists.
MATERIAL AND PERSONNEL:
During this incident, heavy loss of life and material was incurred. The following lists known personnel casualties:
3 Marine Pilots
6 Active Duty Starfleet Officers
4 Retired Starfleet Officers
340 Civilians (Including freighter crew)
2 missing, presumed dead (Check manifests against bodies recovered)
1 Civilian Freighter (Destroyed, Warp Core Breach)
Cargo: Self-sealing Stem Bolts, Feldspar, Beresium Ore
1 Civilian Transport ship (Disabled, towed into dock)
Cargo: Civilians (noted above)
3 GUARDIAN Platforms (Cost CLASSIFIED)
3 Valkyrie Class Fighters (Cost CLASSIFIED)
Misc. Computer Equipment (Bill SFMC)
PRELIMINARY ANALYSIS:
The incident in question is without doubt a considerable tragedy, however me must determine how to apportion responsibility and liability. JAG, Starfleet Security and the Marine CID will each be launching independent investigations into the matter, but will coordinate across task forces to share information.
So far, we have not heard any chatter of foreign or domestic terrorists / rebels / anarchists / agents to suggest that this was a pre-planned operation as of this point in time. However, intelligence analysts will be working to sift through all intercepts and intelligence as well as devoting considerable resources from this point on to determine if this was a deliberate attack. After all, an operation to cripple a potential technology such as this would be a boon to many other state entities with which we enjoy less than cordial relations.
Care should also be given to the idea that this was simply an internal, unintentional malfunction. The isolinear chip discovered could have been the root cause behind the incident, however we must conduct an investigation from the angle that that was the method, rather than cause.
The remaining GUARDIAN platforms are under guard by Starfleet Security and will be hard locked to prevent any activity until they have been disassembled and examined by accredited and certified investigators and engineers (Clearance pending). The salvage from the freighter and the destroyed platforms have been moved to an internal dock on Deep Space 5 and placed under guard by the station Marine Detachment by order of Colonel Darson.
The recovery operation is proceeding according to schedule, and the area containing the wreckage should be cleared within two days’ time of this report. After that, we will open up the area of space to travel once more.
One final note is that of liability. We have already had reports of several claims being filed by civilians who lost property or lives during the incident. Should the investigation bear out that this was a malfunction, Starfleet and the Federation may find themselves liable for damages. As of this report publishing date Deep Space 5 is requesting aid from JAG offices and the State Department to help document and contain this response.
CONCLUSION:
This incident is a tragedy, both for the loss of life and property and the setting back of defense research. All parties involved will be putting forth our best efforts to determine the cause and if necessary locate the perpetrators of this atrocity.
Please forward all applicable information to Starfleet Intelligence and Marine OI/CID.
BREAK BREAK BREAK
OFF:
Colonel James Darson