Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-terms-conditions domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-paypal-payments domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-paypal-payments domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-captcha domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themify domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themify domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the logo-carousel-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-tm-extra-product-options domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themify domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6114) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":9238,"date":"2022-04-12T14:46:20","date_gmt":"2022-04-12T14:46:20","guid":{"rendered":"https:\/\/oceanbuilders.com\/?p=9238"},"modified":"2023-01-11T20:35:25","modified_gmt":"2023-01-11T20:35:25","slug":"rd-can-we-build-a-bulletproof-seapod","status":"publish","type":"post","link":"https:\/\/oceanbuilders.com\/blog\/rd-can-we-build-a-bulletproof-seapod\/","title":{"rendered":"R&D – Can we build a Bulletproof SeaPod?"},"content":{"rendered":"\n
\n
\n
\n
\n \n
\n
\n

We had the idea to see if it was possible to make a bulletproof Pod<\/a> with exterior walls that are capable of stopping a bullet or other projectiles. Our plan was to substitute the sheets of fiberglass fabric that we typically use in our Pods for sheets of kevlar fabric. The construction process is basically the same concept so we made a section with our normal method and a matching piece using the kevlar.<\/p>

We mounted each piece on a piece of steel with a section of foam that is similar to what the SeaPod will have added between the steel and the section to help show what is happening to the bullet after or if it breaks through the exterior shell. You can\u2019t call something bulletproof unless you test it so we took our targets out to a safe island where we could test their strength against a bullet.<\/p>

We fired a single 9mm bullet at each of these sections from a distance of about two meters. 9mm is a relatively slow round that doesn\u2019t have as much energy behind it as something like a .45 ACP, .223, or .308 round. 9mm is a very common round all around the world so we felt that it was a good choice for the first test since it is common and also doesn\u2019t pack the biggest punch.<\/p>

R\u00fcdiger did the honors of testing the strength of these two pieces using his Glock 26 pistol. He started with the 7-layer fiberglass piece. The bullet entered through the surface and stayed inside the foam. The 9mm bullets that we used were jacketed so it stayed relatively intact going through the material and then carried enough energy to flatten itself on the steel backing.<\/p>

Next, we moved to the kevlar piece and fired an identical bullet from the same distance. The entry hole on the kevlar was clean so this means that the bullet maintained its shape until it hit the steel and flattened itself, similar to the fiberglass version. Both of these had the potential to be fatal so as far as a bulletproof SeaPod goes, it\u2019s back to the drawing board for now.<\/p>

While the kevlar version hadn\u2019t stopped the bullet like we had hoped, we don\u2019t consider anything that we can learn from and improve on a failure, it\u2019s merely a bump in the road. This idea is totally supplemental to the normal SeaPod design so it\u2019s just something extra that we are working on and won\u2019t slow the production process of the actual Pods. Hopefully, we will be able to revisit this again and deliver some different results in the near future!<\/p> <\/div>\n<\/div>\n\n

\n
\n
\n