A little follow-up post as I’m watching particularly X and the seemingly endless supply of posts and reactions:
For certain parties “demanding” video of the incident, don’t go looking too hard. Depending on which side the video was recorded (NAVAIR if the Hornet caught it, NAVSEA if the Gettysburg’s cameras were working), the classification level can vary wildly. In either case, you’ll be waiting about 25-50 years for the unredacted version depending on the sensitivity of the equipment and data from this incident. I say this having seen both sides of this particular aisle.
While this incident is by all accounts an embarrassment and wakeup call for all Aegis Systems Engineers and Contractors alike, initial lack of video, under normal circumstances, is not a cause for alarm or conspiracy theories. Classification of sensitive data exists for a reason, and any specifics to the overall operations of the ship and fighter squadrons must be protected.
Lecturing of classification and security aside for “muh video”, complete lack of transparency in this case is wholly unacceptable. This malfeasance constitutes a situation where the US puts its own warfighters into dangerous situations with their own equipment. The government cannot sweep this under the rug, as this violates security principles of using sensitivity levels to hide “embarrassing information”. Keep in mind this also does a disservice to the aforementioned contractors and Engineers, as we can’t effectively design or provide solutions and lessons learned when left in the dark.
If we don’t get answers now, God help us and God hoping Trump’s administration pries this thing wide open. The beginning stages of a global war are unraveling quick and we can’t afford to lose Engineering superiority just to save political face.
For certain parties “demanding” video of the incident, don’t go looking too hard. Depending on which side the video was recorded (NAVAIR if the Hornet caught it, NAVSEA if the Gettysburg’s cameras were working), the classification level can vary wildly. In either case, you’ll be waiting about 25-50 years for the unredacted version depending on the sensitivity of the equipment and data from this incident. I say this having seen both sides of this particular aisle.
While this incident is by all accounts an embarrassment and wakeup call for all Aegis Systems Engineers and Contractors alike, initial lack of video, under normal circumstances, is not a cause for alarm or conspiracy theories. Classification of sensitive data exists for a reason, and any specifics to the overall operations of the ship and fighter squadrons must be protected.
Lecturing of classification and security aside for “muh video”, complete lack of transparency in this case is wholly unacceptable. This malfeasance constitutes a situation where the US puts its own warfighters into dangerous situations with their own equipment. The government cannot sweep this under the rug, as this violates security principles of using sensitivity levels to hide “embarrassing information”. Keep in mind this also does a disservice to the aforementioned contractors and Engineers, as we can’t effectively design or provide solutions and lessons learned when left in the dark.
If we don’t get answers now, God help us and God hoping Trump’s administration pries this thing wide open. The beginning stages of a global war are unraveling quick and we can’t afford to lose Engineering superiority just to save political face.
👍24😢18❤3