redux-framework 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 /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf 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 /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce 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 /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap 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 /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer 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 /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon 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 /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 213355667 | Release Date | 2026/04/12 | List Price | $36.00 | Model Number | 213355667 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
The 'In Action' series presents a collection of valuable photographs from the actual scenes of military vehicles, aircraft, and ships in operation. It selects not only photographs from manufacturers and museums but also those owned by individuals. These vivid photos can serve as hints for modelers' creations. This volume focuses on the Sikorsky SH-60 Seahawk, a versatile helicopter introduced in 1979 and still in use worldwide. Initially adopted by the U.S. Navy as a general-purpose helicopter, it has since spawned variants for anti-submarine warfare, search and rescue, and counter-terrorism missions. The book showcases the UH-60 Seahawk and its variants with numerous photographs, including aerial shots and onboard footage, providing an immersive experience. It also offers glimpses of maintenance scenes, revealing details like engines. In addition to the SH-60 Seahawk, it covers the HH-60H Rescue Hawk, SH-60F Ocean Hawk, MH-60R Strike Hawk, and MH-60S Nighthawk. With over 260 color photographs, it's a must-see for both modelers and aviation enthusiasts, with English explanations for each photo.
| Scale | 1:24 Scale |
|---|---|
| Theme | Military |
| Sub Brand | Sikorsky SH-60 Seahawk |
| Brand Name | Platz |
| Manufacturer | スコードロン・シグナル |
| Material Type | Paper |
| Toy Vehicle Form | Helicopter |
| Included Components | Book |
| Age Range Description | Kid |
| Educational Objective | To provide detailed information and high-quality photographs of the SH-60 Seahawk helicopter for educational and reference purposes, particularly for modelers and aviation enthusiasts, and to serve as a historical record of the helicopter's operations and activities. |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form