Flush deck

Flush deck is a term in naval architecture. It can refer to any deck of a ship which is continuous from stem to stern. It has two specific common referents:

  • Flush deck aircraft carriers are those with no island superstructure, so that the top deck of the vessel consists of only an unbroken flight deck.
  • "Flush deckers" is a common nickname for a series of American destroyers built in large quantities during or shortly after World War I – the Caldwell, Wickes, and Clemson classes – so called because they lacked the raised forecastle of preceding American destroyers, thus the main deck was a flush deck.[1]
USS Langley was a flush-deck aircraft carrier

Two different meanings of "flush"

"Flush deck" with "flush" in its generic meaning of "even or level; forming an unbroken plane", is sometimes applied to vessels, as in describing yachts lacking a raised pilothouse for instance. "Flush deck aircraft carrier" uses "flush deck" in this generic sense.

"Flush deck" in its more specific maritime-architecture sense denotes (for instance) the flush deck destroyers described above: the flush decks are broken by masts, guns, funnels, and other structures and impediments, and are far from being unbroken planes. "Flush deck" in this sense only signifies that the main deck runs the length of the ship and does not end before the stem (with a separate raised forecastle deck forward) or before the stern (with a separate raised or, as seen on many modern warships, lowered quarterdeck rearward).

History

The British East India Company duplicated the flushed deck design of Bengal rice ships in the 1760s, leading to significant improvements in seaworthiness and navigation for United Kingdom ships during the Industrial Revolution.[2] The flushed deck design was introduced with rice ships built in Bengal Subah, Mughal India (modern Bangladesh), resulting in hulls that were stronger and less prone to leak than the structurally weak hulls of stepped deck design.. This was a key innovation in shipbuilding at the time.

gollark: > What is a helloboi?<|endoftext|>Maybe if it compresses them somehow.<|endoftext|>I mean, maybe you could do it.<|endoftext|>The program reads the output into memory.<|endoftext|>This is the output from the wrong one.<|endoftext|>I suppose I could make it send a buffer or something.<|endoftext|>That's not the output.<|endoftext|>This is a great idea: maybe a buffer or something, but it's not that.<|endoftext|>Not as far as I can tell.<|endoftext|>It can export messages from another HTTP HTTP server, it's not encrypted.<|endoftext|>I'm aware of a "window" menu.<|endoftext|>This is a bizarre, isn't it.<|endoftext|>It's not web-based, and it's not web-based, but I assume it's HTTP-based, so I can't access it and it'll probably be used for HTTP requests.<|endoftext|>I could make a simple script.<|endoftext|>I guess that'd be
gollark: If you fund osmarks.net with 81294129046894162481647126412846194 funding, I can buy a TPU and execute it faster.
gollark: I'm asking it about helloboi first. It is very slow.
gollark: > What if bees literally apioform?<|endoftext|>It's very popular.<|endoftext|>In the current network, it's not very widely used, and it's not really used yet.<|endoftext|>I don't see why that's a quirk of some sort.<|endoftext|>I still think that the best way to do rights is to have people arbitrarily erase their memory and/or repurpose each other.<|endoftext|><@!2930660666066606688215756> Yes.<|endoftext|>I should probably just transfer ownership to the potatOS registry.<|endoftext|><@!2930660668866606666606667890625663247974> Give me the code and/or soul and/or soul and/or soul and/or soul and/or soul.<|endoftext|>The PotatOS privacy policy is very clear.<|endoftext|>It's not anomalous, though. It's anomalous.<|endoftext|>I see.<|endoftext|>I've heard of it, and it's a "
gollark: Aha!

References


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.