Get the latest from Weapons and Warfare right to your inbox.
Only two aircraft were built, the last one was destroyed in 1943. In December 1934, Tupolev was asked to design a naval heavy bomber (Morksoi Torpedonosets Bombardirovshik = naval torpedo bomber = MTB). With his seaplane specialist Ivan Pogosski dead, he gave the project to Aleksander Golubkov who came up with a more conventional design than the earlier ANT âhydroplanesâ…
Lockheed Martin unveiled its newest member to the F-16 family â F-21, where 21 stands for 21st century. It is an enhanced version of F-16 Block 70. Though it carries a lot of identical systems that are already available on Block 70, it does have its own unique specifications- that…
The Fiat G.50 was built in response to specifications issued by the Ministerio dellâ Aeronautica in 1936, calling for a lightly armed interceptor, a long-range escort fighter, and a fighter-bomber. While other manufacturers submitted four designs to address each of those requirements, Fiatâs Giuseppe Gabrielli designed his G.50 to satisfy…
An unprecedented long-range mission and a severe test for the Air Corpsâ new B-10 bomber was made in the summer of 1934, when Lt. Colonel Henry H. Arnold led ten of the Martin bombers on a grueling 7,360-mile round-trip flight from Washington, D. C, to Alaska and return. The airplanes…
XC-99 at Kelly AFB, Texas while attached to the Military Air Transport Service 1700th Air Transport Group, 1954. Note San Antonio Air Materiel Area (SAAMA) tail marking, indicating the aircraft was assigned to the Air Materiel Command. During its operational life, the XC-99 logged over 7,400 hours total time, and…
It would be fair to say that the Junkers Ju 86 was already obsolescent at the beginning of World War 11, and was accepted rather grudgingly by the Luftwaffe, which preferred the Heinkel He 111. It is all the more surprising, therefore, that within two years the type was operating…
CA.101 The Ca.101 was essentially an enlarged Ca 97 which appeared in 1927 as a commercial transport, powered by three AHa Romeo built 200 h. p. Armstrong-Siddeley Lynx radial engines. Specifications of this model included a span of 65 ft., a length of 44 ft. 8 in., a height of…
Arguably, the Focke-Wulf Fw 190 evolved into wartime Germanyâs most effective fighter, offering the Luftwaffe…
Douglas A-20 Havoc Douglas Aircraft developed the Model 7B twin-engine light attack bomber in the…
Final Encounter (Spitfire v Messerchmitt) by Michael Turner. Wing Commander J E Johnnie Johnson, Spitfire…
Weapons and Warfare
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortiumâs (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the websiteâs UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the websiteâs HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If youâve found a malfunction or have ideas for improvement, weâll be happy to hear from you. You can reach out to the websiteâs operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the websiteâs functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Hereâs how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the websiteâs components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the websiteâs images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the websiteâs HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as âMâ (menus), âHâ (headings), âFâ (forms), âBâ (buttons), and âGâ (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to
Sign in to your account