text:
Wheelwright

A wheelwright is a craftsman who builds or repairs wooden wheels. The word is the combination of "wheel" and the word "wright" (which comes from the Old English word "wryhta", meaning a worker or shaper of wood) as in shipwright and arkwright. This occupational name became the English surname Wright. It also appears in surnames like Cartwright and Wainwright. It corresponds with skilful metal workers being called Smith.

These tradesmen made wheels for carts (cartwheels), wagons (wains), traps and coaches and the belt drives of steam powered machinery. They also made the wheels, and often the frames, for spinning wheels. First constructing the hub (called the nave), the spokes and the rim segments called felloes, (pronounced fell low), and assembling them all into a unit working from the center of the wheel outwards. Most wheels were made from wood, but other materials have been used, such as bone and horn, for decorative or other purposes. Some earlier construction for wheels such as those used in early chariots were bound by rawhide that would be applied wet and would shrink whilst drying, compressing and binding the woodwork together. After many centuries wheels evolved to be straked with iron, a method of nailing iron plates onto the felloes to protect against wear on the ground and to help bind the wheel together. Straking was considered to be a less skilled practice and could be done with less knowledge and equipment, this made the wheels easier to service without the need for a blacksmith.

Over millennia the overall appearance of the wheel barely changed but subtle changes to the design such as dishing and staggered spokes helped keep up with the demands of a changing world. These small changes in design made a massive improvement to the strength of the wheel whilst reducing its weight; vehicles then became more efficient to build and use.

History
Early wooden wheels were solid, made from slabs of trees. They were heavy but the simple construction did not requiring much skill. Wheels with spokes were lighter. They could be constructed with smaller trees and built larger in diameter because they were not limited by the size of trees in the region. However, spoked wheels required precise spacing and careful calculations to construct a perfect circle. It is thought that the special craft of wheelwright started with the invention of the spoke. Rural areas without access to a wheelwright continued to make solid wheels.

Due to the skill and experience required for making wheels, in Europe the wheelwright was formed into an identifiable trade.

Parts and materials
The basic parts of a wooden wheel are nave (or hub), spokes, felloes (felly) and tyre (tire).

The nave is the central block of the wheel. In a wooden-spoked wheel, the nave acts as the hub. One end of each spoke is set into the nave in a process called tennoning. In older wheels, the nave had a 6-inch sleeve that fit over the axle to keep the wheel from wobbling; it required frequent greasing. More modern carriage wheels use bearings.

Spokes are wooden sticks that fit into the nave at one end, and into the felloe at the other end.

A felloe is one of several curved pieces of wood that when pieced together make the rim of a wheel. They are fitted onto the outer ends of the spokes. Sometimes spelled "felly". The number of felloes required to make a circle varied by region, era and size of wheel—with a minimum of two half-circles of bent wood, to multiple felloes per wheel with at least two spokes per felloe.

The rim is the outer edge of a wheel, although some refer to the tyre as rim.

The tyre or tire is a protective strip that goes outside the felloes. Tyres were make of iron or steel, usually as a hoop and fitted hot around the rim. As it cooled and shrank it tightened the joints of the spokes-to-felloes and spokes-to-nave, strengthening the wheel and making it more rigid. Metal tyres are very noisy on hard road surfaces, so many carriages wheels were made with solid rubber tyres fitted into a metal channel.

Due to age or dry climate, a wheel would shrink and the metal hoop tyre would become loose. Routinely, the hoop would be removed, 'shrunk', heated and refitted to make the wheel tight again. Tools to shrink the hoops were called "tire upsetters" or "tire shrinkers".

Industrial age
During the industrial age, iron strakes were replaced by a solid iron tyre custom made by a blacksmith after the wheelwright had measured each wheel to ensure proper fit. Iron tyres were always made slightly smaller than the wheel in circumference. They were expanded by heating in a fire, and while hot they were hammered, and pulled by a levered hook, onto the rim of the wheel. The hot tyre was then cooled by placing it into water. This shrank it onto the wood, and closed the wooden joints. Tyres were fastened to the wheels with nails, or tyre bolts. The metal tyres were drilled before being placed on the wheel. Tyre-bolts were less likely than tyre-nails to fall off because they were bolted through the felloes. Both countersunk and flush finished to the wheel's outer surface.

During the second half of the 19th century, the use of pre-manufactured iron hubs and other factory-made wood, iron and rubber wheel parts became increasingly common. Companies such as Henry Ford's developed manufacturing processes that soon made the village wheelwright obsolete. With the onset of two world wars, the trade soon went into decline and was very rare by the 1960s and almost extinct by the year 2000. However, owing to the efforts of organisations like the Worshipful Company of Wheelwrights, wheelwrights still continue to operate in the UK.

In modern times, wheelwrights continue to make and repair a wide variety of wheels, including those made from wood and banded by iron tyres. The word wheelwright remains a term usually used for someone who makes and repairs wheels for horse-drawn vehicles, although it is sometimes used to refer to someone who repairs wheels, wheel alignment, rims, drums, discs and wire spokes on modern vehicles such as automobiles, buses and trucks. Wheels for horse-drawn vehicles continue to be constructed and repaired for use by people who use such vehicles for farming, competitions and presentations of historical events such as reenactments and living history.

Wheelwrighting today
A modern wooden wheel generally consists of three main parts, the nave or hub at the centre of the wheel, the spokes radiating out from the centre and the felloes or rims around the outside. Generally the wheel would be bound by a steel or iron tyre depending on its historical period and purpose.

The main timbers used in a traditional wooden wheel are Elm for the nave, Oak for the spokes and Ash for the felloes although this can vary in some areas depending on availability of timber, climate and style of production. Sometimes Hickory is substituted for Oak and Ash as it is easier to bend for mass production and is quite springy for light wheels that require a bit of flexibility.

The Elm is used for its interwoven grain, this prevents the nave from splitting with the force of the spokes being driven in tight.

The Oak is used because it doesn't bend, compress or flex and transfers any load pressures directly from the felloes to the nave.

The Ash is used for its flexibility and springy nature, this acts as a form of suspension and protects against shock damage.

The future
In the second half of the 20th century, wheelwright training faded away due to a lack of demand for new wooden wheels. The skills were kept alive by small businesses, museums, societies and trusts such as The Colonial Williamsburg Foundation (USA) and The Countryside Agency (UK).

The Worshipful Company of Wheelwrights in London (UK) maintains a flourishing (government-backed) apprenticeship scheme that began in 2013.

Colonial Williamsburg (USA) has an ongoing apprenticeship program and has recently (2016) taken on new apprentices.

title: Wheelwright


text:
IBM System/3

The IBM System/3 was an IBM midrange computer introduced in 1969, and marketed until 1985. It was produced by IBM Rochester in Minnesota as a low-end business computer aimed at smaller organizations that still used IBM 1400 series computers or unit record equipment. The first member of what IBM refers to as their "midrange" line, it also introduced the RPG II programming language. It is the first ancestor in the product line whose current version is the IBM i series and includes the highly successful AS/400.

History
At its launch in 1969 it was available for $1000/month — less than half cost of an IBM System/360 Model 20; the smallest member of the IBM System/360 family.

Many of the original System/3 model 10 units were shipped diskless, with only the new IBM 5424 Multifunction Card Unit (MFCU) which read, punched, printed on and sorted the new, smaller 96-column punched cards introduced at the same time.

IBM delivered the following models:
 * 1969 — IBM 5410, or System/3 Model 10, introduced (shipped in 1970)
 * 1970 — IBM 5406, or System/3 Model 6, introduced (disk-oriented system)
 * 1973 — IBM 5415, or System/3 Model 15, introduced
 * 1974 — IBM 5408, or System/3 Model 8, introduced
 * 1975 — IBM 5412, or System/3 Model 12, introduced
 * 1976 — IBM 5404, or System/3 Model 4, introduced

The System/3 and successor models System/32, System/34, System/36 and System/38 are generally referred to in IBM terminology as "midrange systems" — in contrast to IBM's mainframes.

Hardware
The IBM System/3 was announced as a computer system that initially consisted of:
 * IBM 5410 Model 10 Central Processing Unit
 * IBM 5424 Multi Functional Card Unit (MFCU)
 * IBM 5203 Line Printer
 * IBM 5444 Disk Storage (optional)
 * IBM 5471 Printer Keyboard
 * IBM 5475 Data Entry Keyboard
 * IBM 5496 Data Recorder, a keypunch machine with print and verify functions
 * IBM 5486 Card Sorter

Memory
Entry models had as little as 4K (4096) bytes of magnetic-core memory.

Direct access storage
For mass storage, the System/3 used the IBM 5444 single-platter disk, roughly the size of a large pizza; initially each platter held 2.5 MB of data. Standard configuration for storage was one or two fixed disks, each in a separate pull-out drawer, which typically held the operating system and user-developed programs. Additionally, each fixed disc could have a removable cartridge disk attached; these typically contained the data-files associated with various applications, for example Payroll, and users frequently had a number of them. Thus the low-end systems could support a maximum of 10 MB of online storage (two fixed, two removable), although in practice this was very expensive and not common.

The System/3 was also available with the IBM 5445 disk drive (20mb) and later the model 15 allowed "winchester" style 3340 drives. On the smaller models, while you could attach 5445 drives, you had to keep the 5444 for the operating system and other programming libraries, however that limitation was changed with software called elimn8 which allowed 5445 drives to totally replace the 5444's. Other companies such as Memorex manufactured compatible 5445 drives for the System/3.

Multi-Function Card Unit
The most common punched-card device was IBM 5424 Multifunction Card Unit (MFCU) which read, punched, printed on and sorted the new, smaller 96-column punched cards. Instead of the rectangular punches in the classic 80-column IBM card, the new cards had tiny (1 mm), circular holes much like paper tape. Data was stored in six-bit binary-coded decimal code, with three rows of 32 characters each, or in 8-bit EBCDIC, with the two extra holes located in the top rows. The new cards had room for 128 printed characters in four rows of 32 characters each. They were about 1/3 the size of the older 80 column cards but held 20% more text data. The smaller, and thus lighter card could be processed with faster equipment and with fewer jams.

Available as RPQs (special order equipment) to handle 80-column cards were the IBM 2560 Multifunction Card Machine (MFCM) which could read, punch, interpret and sort, and the IBM 1442 which could only read and punch.

Magnetic tape
Offline storage was available with the purchase of an external tape drive which read and wrote standard IBM 9-track tape.

The System/3 Mod 10 optionally included the IBM 3410 magnetic tape subsystem.

Operator Console Facility
The System/3 Operator Console Facility (OCF) consisted of either a modified IBM Selectric typewriter interfaced into the computer, or a special purpose IBM 3270 display. Within the OCF, there was capability to 'cancel' processes and/or tasks that were running, including either partition (P1 or P2). The system could only run two programs simultaneously, except for the model 15 or systems running the Communications Control program, CCP. The CCP was a system control programming feature that allowed to support an online network of terminals.

Printers
A smaller (IBM 5203) printer was attached to the main system. The 5203 was a chain printer with interchangeable cartridges. It could run at 100 or 200 lines per minute, based on model. Later on, IBM offered multiple models of the existing IBM 1403 printer line, which had been originally built for the IBM 1401 computer.

Floppy disk
With the arrival of the IBM 3740 data entry system, the System/3 Model 10 got a feature called LCA (local communication adaptor) which allowed an IBM 3741 station to be "attached" to the system to transmit/receive data. Later models of the System/3 such as the Model 8 were cardless and used the 8" 3740 style floppy disk.

Instruction set
The instruction set was optimised for two key aspects of the product: limited availability of main memory, and the RPG II programming language. The original S/3 (models 10 and then 6, 8 and 12) had 29 instructions, all occupying between 3 and 6 bytes (24 to 48 bits).

The first 4 bits conveyed a lot of information: "1111" meant this was an instruction without operands, known as a command. e.g. Start I/O (the I/O op being defined by previously loaded I/O registers). "11xx" and "xx11" meant a 1-operand instruction, such as a Branch. If xx was 00 the operand was addressed by its full 16-bit address. xx=01 or 10 meant base-displacement addressing was used, using index register 1 or 2 respectively. A base address would previously have been loaded into one of the two index registers and the instruction contained the displacement of up to just 256 bytes (8 bits of addressing).

Other patterns for this first half-byte indicated a 2-operand instruction. "0000" meant both operands were addressed by their direct 16-bit address. "0100": operand 1 uses reg 1 as its base; operand 2 uses direct addressing. "0110": operand 1 uses reg 1 as its base, operand 2 uses reg 2. And so on.

The remaining 4 bits of the first byte further defined the instruction. This structure meant that there was the capability to have up to 64 operations in all: 16 commands (though there were never more than five across the whole product range); 16 1-operand instructions starting with 11xx; 16 1-operand instructions starting with xx11; 16 2-operand instructions.

As well as the two index registers already mentioned (referred to as 1 and 2, or binary 01 and 10) there were other registers. "Reg 4" (0100) was the instruction address register (IAR) which pointed at the current instruction. "Reg 8" (1000) was the address recall register (ARR), set by certain instructions. Among these was the conditional branch (mnemonic BC) which used it to point to the byte immediately following the branch operation. For programmers used to IBM mainframe behaviour, this meant that the S/3 branch operation could be likened to a conditional BALR (branch and link register) – very useful when branching to a sub-routine, and returning after it had processed. Finally, "Reg 16" (00010000) was the program status register (PSR), holding such things as the results of a compare instruction. Note that registers were used only for addressing and program status, not for arithmetic.

The arithmetic instructions provided among the 29 instructions were binary add/subtract (provided to help manipulate addresses) and decimal add/subtract. Multiplication and division were not provided for by the standard hardware, and had to be handled by software routines. There was no floating point provision at all. All this continued to be true even with the later and generally more sophisticated Systems/34 and 36.

All the above got more complicated with the System/3 model 15, and the Systems/34 and /36. Though still using 16-bit addressing, all these systems could support well over 64K of main storage (up to 512K and theoretically more), so address translation was used to swap from one 64K address space to another. Address Translation Registers were set to define the actual address space in use at any one time, their contents being concatenated with the 16-bit address used by a program to produce a real address. These "ATRs" were privileged, available only to the operating system.

The original S/3 model 10 (and the later model 12) had an optional crude form of multi-programming called the Dual Program Feature. This provided no more main memory addressing, but gave two sets of registers and instructions which flipped from one "program level" to the other. The standard I/O instructions were also modified to flip when an I/O was started.

So far, only the first byte of the instruction has been explained here. The next ("Q") byte was generally a qualifier, such as specifying the number of bytes to be moved in a move characters op or the condition to test for in a Branch. A couple of instructions used this byte for a 1-byte "immediate" operand. The remaining byte(s) were for the displacement(s) or address(es) for operands, or the details for some commands.

An example: a simple command, Conditional Jump, a special type of conditional branch (forward only, up to 256 bytes) suitable mainly for jumping over short blocks of code: Op code byte= F2 (this is in hexadecimal, Hex F is binary 1111, Hex 2 (0010) defines the op); Q byte= 00000001 specifies that we "jump" if the condition register has the "equal" bit on; Operand= 00011000: if the condition is met we jump forward 24 bytes.

Indicators were binary switches used to control program flow. Over 100 of these were available to the programmer. By using the instruction formats explained above, many of the indicator-oriented operations could be fit into just 3 bytes. For example, a line of RPG might test an indicator for "On": 3 bytes for a "Test Bits On" op; then 3 bytes for a Jump, as previously described, and useful to the RPG compiler. Saving the odd byte here and there was good when you had only 64K to play with—and, on the S/3 itself, that had to include the operating system (which grew to about 20K on the model 10 with the introduction of the "Communication Control Program", CCP).

Operation Control Language
A simple job control language called Operation Control Language (OCL) was superficially similar to the Job Control Language (JCL).

Operator control commands
Operator control commands (OCCs) were used to communicate with the system.

Languages
The System/3 supported RPG II, Fortran IV, COBOL, and Assembler.

RPG II compiler
The System/3 came standard with a RPG II compiler. In a card-only system, the RPG II compiler was supplied as two phases. The first phase would be booted from one input hopper of the MFCU, and the source would then be read following the compiler. An intermediate form was punched on cards, which were then read by the second phase of the compiler. An executable program deck was then punched. This executable could then be booted ("IPL'ed", for "Initial Program Load") to perform the processing desired. This process could require more than an hour for a significant-sized program.

Problems with System/3
The System/3 had no provision for halting a process once it had started to run. For instance, if a compile failed because of an error on the very first page, the user had to wait for a sometimes voluminous compile listing to print in its entirety. Users learned to reach under the printer and jostle the paper discharge chute, which would cause the machine to halt with a "P3" (printer error) displayed. The user could then dial in the response code FF to abort the run. Another way of stopping it was simply to press the green "Start" button on the console, causing the system to reboot.

Error codes were displayed on a two-digit seven-segment display (one of the first seen, and built with lamps rather than LEDs). The range of error codes included not only decimal and hexadecimal digits (as seven-segment displays are commonly used) but also a limited set of other letters; for example, "P3" was one of several printer error codes. A thick manual that came with the System/3 aided the operator in interpreting the error codes and suggested recovery procedures. The System/3 had no audible warning device, so a program that was not printing, reading cards, or causing other obvious activity could halt and the operator would not know it unless they happened to look at the status display. Models with the Dual Program Feature had two separate status displays.

Most/many users did not buy a console. Instead OCL code was either suppressed entirely or printed on the 5203 printer. The console offered by IBM slowed down program execution tremendously when it printed OCL commands, as it was basically a selectric typewriter.

The concept of keying your punched cards through the console was a marketing ploy. In reality, the System/3 could not be a computer and a keypunch at the same time, so when it was a keypunch, no computing was possible. The original IBM System/3, which was shown in July 1969, had the keypunch console so they could offer a computer for under $2,000/month. In reality it was unworkable and almost invariably users acquired a stand-alone keypunch/verifier.

Later several OEM companies built 96-column keypunches, sorters, and collators. This took the 'heavy lifting' off of the MFCU and freed the System/3 for actual computing functions.

Most experienced System/3 users minimized use of the MFCU as much as possible, since it was a system bottleneck.

Emulation
The later System/32, IBM System/34 and IBM System/36 were all able to run System/3 applications through emulation.

The System/32 used a vertically microcoded processor, with 16-bit microcode words, which emulated the System/3 instruction set, rather slowly, in microcode. The System/34 and System/36 both had two processors: a Control Storage Processor (CSP), as in System/32, which handled most supervisor and input/output operations, and a Main Storage Processor (MSP). This latter was a re-implementation of the System/3 model 15 processor; effectively providing "hardware emulation" of the System/3.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: IBM System/3


text:
Siderite

Siderite is a mineral composed of iron(II) carbonate (FeCO3). Its name comes from the Ancient Greek word, meaning "iron". A valuable iron ore, it consists of 48% iron and lacks sulfur and phosphorus. Zinc, magnesium, and manganese commonly substitute for the iron, resulting in the siderite-smithsonite, siderite-magnesite, and siderite-rhodochrosite solid solution series.

Siderite has Mohs hardness of 3.75 to 4.25, a specific gravity of 3.96, a white streak and a vitreous lustre or pearly luster. Siderite is antiferromagnetic below its Néel temperature of 37 K which can assist in its identification.

It crystallizes in the trigonal crystal system, and are rhombohedral in shape, typically with curved and striated faces. It also occurs in masses. Color ranges from yellow to dark brown or black, the latter being due to the presence of manganese.

Siderite is commonly found in hydrothermal veins, and is associated with barite, fluorite, galena, and others. It is also a common diagenetic mineral in shales and sandstones, where it sometimes forms concretions, which can encase three-dimensionally preserved fossils. In sedimentary rocks, siderite commonly forms at shallow burial depths and its elemental composition is often related to the depositional environment of the enclosing sediments. In addition, a number of recent studies have used the oxygen isotopic composition of sphaerosiderite (a type associated with soils) as a proxy for the isotopic composition of meteoric water shortly after deposition.

Carbonate iron ore
Although carbonate iron ores, such as siderite, have been economically important for steel production, they are far from ideal as an ore.

Their hydrothermal mineralisation tends to form them as small ore lenses, often following steeply dipping bedding planes. This makes them not amenable to opencast working, and increases the cost of working them by mining with horizontal stopes. As the individual ore bodies are small, it may also be necessary to duplicate or relocate the pit head machinery, winding engine and pumping engine, between these bodies as each is worked out. This makes mining the ore an expensive proposition compared to typical ironstone or haematite opencasts.

The recovered ore also has drawbacks. The carbonate ore is more difficult to smelt than a haematite or other oxide ore. Driving off the carbonate as carbon dioxide requires more energy and so the ore 'kills' the blast furnace if added directly. Instead the ore must be given a preliminary roasting step. Developments of specific techniques to deal with these ores began in the early 19th century, largely with the work of Sir Thomas Lethbridge in Somerset. His 'Iron Mill' of 1838 used a three-chambered concentric roasting furnace, before passing the ore to a separate reducing furnace for smelting. Details of this mill were the invention of Charles Sanderson, a steel maker of Sheffield, who held the patent for it.

These differences between spathic ore and haematite have led to the failure of a number of mining concerns, notably the Brendon Hills Iron Ore Company.

Spathic iron ores are rich in manganese and have negligible phosphorus. This led to their one major benefit, connected with the Bessemer steel-making process. Although the first demonstrations by Bessemer in 1856 were successful, others' initial attempts to replicate his method infamously failed to produce good steel. Work by the metallurgist Robert Forester Mushet showed that the reason for the discrepancy was the nature of the Swedish ores that Bessemer had innocently used; they were very low in phosphorus. Using a typical European high-phosphorus ore in Bessemer's converter gave a poor quality steel. To produce high quality steel from a high-phosphorus ore, Mushet realised that he could operate the Bessemer converter for longer, burning off all the steel's impurities including the unwanted phosphorus but also the carbon (which is an essential ingredient in steel), and then re-adding carbon, along with manganese, in the form of a previously obscure ferromanganese ore with no phosphorus, spiegeleisen. This created a sudden demand for spiegeleisen. Although it was not available in sufficient quantity as a mineral, steelworks such as that at Ebbw Vale in South Wales soon learned to make it from the spathic siderite ores. For a few decades, spathic ores were therefore in demand and this encouraged their mining. In time though, the original 'acidic' liner of the Bessemer converter, made from siliceous sandstone or ganister, was replaced by a 'basic' liner in the newer Gilchrist Thomas process. This removed the phosphorus impurities as slag produced by chemical reaction with the liner, and no longer required spiegeleisen. From the 1880s demand for the ores fell once again and many of their mines, including those of the Brendon Hills, closed soon after.

title: Siderite


text:
CFS Debert

Canadian Forces Station Debert (also CFS Debert) was a Canadian Forces station located in Debert, Nova Scotia. It was most recently used during the Cold War as a communications facility and was home to a "Regional Emergency Government Headquarters" (REGH) complex, more commonly known by their nickname "Diefenbunker."

Originally this facility was developed with an airfield and army training centre, however these facilities were partly decommissioned in the 1970s and ownership of the airfield and some lands/buildings transferred to the Government of Nova Scotia to be operated as the Debert Air Industrial Park. Following decommissioning of the REGH and removal of the last military presence at CFS Debert in the 1996, the rest facility was transferred to the Government of Nova Scotia and then the Colchester Regional Development Authority to operate as Colchester Park.

Debert Military Camp
Following the outbreak of the Second World War in the fall of 1939, the first Canadian units began shipping through the port of Halifax; however the end of the Phoney War in the spring of 1940 required a massive ramp-up in Canada's land forces in Europe. The sheer volume of soldiers who would be embarking through Halifax required staging facilities for training and marshalling combat units before embarking on the troopships.

To meet this requirement, the government announced that existing facilities at Camp Aldershot near Kentville, Nova Scotia and Camp Sussex near Sussex, New Brunswick would be upgraded to handle the requirements of housing and training brigade-size units. In spring of 1940, the government also began purchasing additional land in Debert for a division-size training and marshalling facility adjacent to those lands previously purchased in 1938 by the Royal Canadian Air Force for an aerodrome.

Located on the Montreal-Halifax main line of Canadian National Railways, the flat plain surrounding Debert Station were considered ideal for an army staging facility in addition to an aerodrome. The additional benefit that it was located only 100 km north of Halifax.

On August 9, 1940, the 6th Field Company Canadian Engineers arrived at the site and began work at clearing the forests and laying out what would become the Debert Military Camp (also referred to as Camp Debert). Employing 6,000 civilians and thousands more military members, the engineers cleared the trees and burnt the plain before building streets, sewer and water services, electricity, and buildings over an area of 80 km2. The camp was bisected with named avenues and numbered streets having innumerable quonset huts, mess halls, warehouses, canteens, and other buildings. At one point during its construction period, the camp housed more troops than the population of neighbouring Truro at the time.

The surrounding community of Debert grew rapidly with movie houses, restaurants, bars and other businesses being set up and the economic effects spilling over into Truro.

Camp Debert was the final staging area for units embarking from Halifax and was the location where the majority of troops received and trained with their personal weapons. For these purposes a large ammunition depot was built as well as extensive firing ranges. Component units arrived at Camp Debert from across Canada and were organized into larger formations before being carried by trains to troopships at Halifax, usually at night in black-out conditions.

All five divisions of the First Canadian Army were housed (all, or in part) at Camp Debert prior to departure for the European Theatre during the Second World War. In addition, the 7th Canadian Infantry Division of Atlantic Command was formed at Camp Debert, although its volunteer troops went overseas as reinforcements rather than an intact combat unit.

Following the war, Camp Debert was used in the repatriation of troops returning from Europe before undergoing significant downsizing with the majority of training and marshalling areas being decommissioned. In 1948, Camp Debert was reactivated and hosted several active army units during the 1950s.

Regiments formerly serving in Camp Debert
The regiments are listed in chronological order from date of arrival:
 * North Nova Scotia Highlanders (August 1939)
 * 6th Field Company Canadian Engineers (1940–1941)
 * 16th Field Company, RCE (1940–41)
 * 22nd Field Ambulance (1940)
 * 44th Field Battery, RCA (1940–41)
 * The Canadian Grenadier Guards (1940)
 * 1st Battalion, Canadian Scottish Regiment (June 1940 – August 25, 1941)
 * Royal Winnipeg Rifles (July 1940 – August 1941)
 * The Regina Rifle Regiment (September 1940 – August 25, 1941)
 * 12th Field Regiment, RCA (January 16, 1941 – July 19, 1941)
 * 13th Field Regiment, RCA (January 16, 1941 – July 19, 1941)
 * 14th Field Regiment, RCA (January 16, 1941 – July 19, 1941)
 * 3rd Anti-Tank Regiment, RCA (January 16, 1941 – July 19, 1941)
 * The Stormont, Dundas and Glengarry Highlanders (January 1941 – July 18, 1941)
 * Highland Light Infantry of Canada (February 1941 – July 18, 1941)
 * 16th Anti-Aircraft Battery (February 9, 1941 – April 5, 1941)
 * North Nova Scotia Highlanders (May 14, 1941 – July 18, 1941)
 * Halifax Rifles (July 18, 1941 – August 7, 1941)
 * 1st Battalion, The Grey and Simcoe Foresters (August 7, 1941 – February 7, 1942)
 * Lake Superior Regiment (August 11, 1941 – February 5, 1942)
 * The Irish Regiment of Canada (August 14, 1941 – December 1, 1941)
 * 4th Canadian (Armoured) Division (October 4, 1941 – August 21, 1942)
 * The Fort Garry Horse (October 1941 – November 9, 1941)
 * 16th/22nd Saskatchewan Horse (November 20, 1941 – April 9, 1942)
 * The British Columbia Regiment (Duke of Connaught's Own Rifles) (November 1941)
 * Princess Louise Fusiliers (January 30, 1942 – April 6, 1942)
 * The South Alberta Regiment (January 1942 – August 1942)
 * The Elgin Regiment (March 18, 1942 – August 20, 1942)
 * 14th Anti-Aircraft Battery (April 9, 1942 – June 1942)
 * 18th Anti-Aircraft Battery (April 20, 1942 – June 28, 1942)
 * 24th Anti-Aircraft Battery (April 28, 1942 – June 2, 1942)
 * 27th Anti-Aircraft Battery (April 28, 1942 – June 22, 1942)
 * 18th Armoured Car Regiment (12th Manitoba Dragoons) (June 1942)
 * Lake Superior Regiment (June 24, 1942 – August 20, 1942)
 * The Princess of Wales' Own Regiment (June 1942)
 * Princess Louise Fusiliers (August 9, 1942 – October 26, 1942)
 * Le Régiment de Québec (August 26, 1942 – August 7, 1943)
 * Le Régiment de Montmagny (August 28, 1942 – September 30, 1943)
 * 3rd Battalion, The Royal Winnipeg Rifles (September 27, 1942 – August 15, 1943)
 * 3rd Battalion, The Queen's Own Rifles of Canada (September 28, 1942 – June 16, 1943)
 * 2nd/10th Dragoons (September 30, 1942 – January 4, 1943)
 * Les Fusiliers de Sherbrooke (September 30, 1942 – October 13, 1943)
 * The Windsor Regiment 7th division (October 1942)
 * 7th Canadian Infantry Division (1943)
 * Le Régiment de Joliette (January 6, 1943 – February 1943)
 * The Algonquin Regiment (February 1943 – June 10, 1943)
 * No. 2 Port Company, RCASC (March 18, 1944 – November 30, 1944)
 * No. 2 Transit Camp (August 1, 1944 – March 31, 1946)
 * 1st Anti-Aircraft Searchlight Battery (August 7, 1944 – September 21, 1945)
 * No. 1 Ordnance Ammunition Depot (October 1, 1946 – November 16, 1947)
 * No. 31 Ordnance Ammunition Depot (November 17, 1947 – June 1965)
 * 3rd Regiment, Royal Canadian Horse Artillery (1948–1958)
 * 12th Regional Ordnance Depot (1948–1958)
 * 31st Ordnance Ammunition Depot (1948–1965)
 * Royal Highland Regiment of Canada (1950–1952)
 * 720 Communication Squadron (1964 – October 3, 1985)

RCAF Station Debert
In the fall of 1938 the Royal Air Force (RAF) purchased land for constructing an aerodrome on the north shore of Cobequid Bay near the farming community of Debert.

Construction of the aerodrome, which would host the RAF's No. 31 Operational Training Unit (O.T.U.), began in the fall of 1940 and was completed in April 1941, coinciding with the construction of the army's adjoining Camp Debert. The airfield itself consisted of three 5000 ft runways arranged in an overlapping triangle.

31 O.T.U was one of several similar facilities constructed in the Maritime provinces in support of the British Commonwealth Air Training Plan and RAF Ferry Command. Aircrew trained at Debert to ferry newly manufactured aircraft from the United States and Canada across the Atlantic. Aircrew were trained on the Lockheed Hudson and de Havilland Mosquito.

No. 31 OTU was later taken over by the Royal Canadian Air Force (RCAF) in 1944 and re-designated No. 7 O.T.U. After the cessation of hostilities in Europe, RCAF Debert briefly hosted 420 and 425 Squadrons as part of Tiger Force, a long-range Commonwealth bomber group formed to strike against Japan. 420 and 425 operated Avro Lancaster bombers as training aircraft to prepare for their new role. Tiger Force was disbanded after Japan's surrender in September. RCAF Station Debert closed soon after but was still owned and maintained by the RCAF.

Aerodrome
In approximately 1942 the aerodrome was listed as RCAF Aerodrome - Debert, Nove Scotia at 45.41667°N, -63.46667°W with a variation of 24 degrees west and elevation of 130 ft. The field was listed as "All hard surfaced" and had three runways listed as follows:

Relief landing field - Maitland
The relief landing field for RCAF Station Debert was located near the village of Maitland. In approximately 1942 the aerodrome was listed as RCAF Aerodrome - Maitland, Nova Scotia at 45.33333°N, -63.53333°W with a variation of 23.5 degrees west and no elevation was specified. The field was listed as "Hard under construction" and had one runway listed as follows::

Postwar
Following the closure, the aerodrome at Debert underwent some downsizing but continued to support active flight operations as a training, refueling, and maintenance base until 1954 even though no operational squadrons were stationed there.

In 1960, the RCAF transferred its aerodrome to the Royal Canadian Navy (RCN) which used the facility for aircraft carrier landing practise in support of naval aviation aircraft stationed at nearby Royal Canadian Naval Air Station (RCNAS) Shearwater. Also in the 1960s, some unused hangar space at the aerodrome was used to house a medical equipment supply depot which was used by all three branches of the armed forces.

On February 1, 1968, the merger of the three service branches into the unified Canadian Forces saw the end of flight operations at the Debert aerodrome and in 1971 the Department of National Defence designated 4800 acre, consisting of the aerodrome and the majority of the training area used by the former Camp Debert, as surplus. The provincial government purchased this land for development into the "Debert Air Industrial Park" while the aerodrome continues to be used as a municipal airfield, known as Debert Airport.

Maritime "Diefenbunker”
In 1958, at the height of the Cold War and the infancy of the ICBM threat, Debert was selected as the site for 1 of 6 communication centres and "Regional Emergency Government Headquarters" complexes being located across Canada. The Debert facility would be the only such complex built in the Maritime provinces.

A small part of Camp Debert was proposed to be used for the complex along with supporting surface structures and personnel housing. Construction began in 1960 on an underground 2-storey bunker (approximately half the size of the CEGHQ, located in Carp, Ontario) capable of withstanding a near-hit from a nuclear explosion (an approximate 1 - 1.5 mi radius). The underground building had blast doors at the surface, as well as extensive air filters (mainly against biological, chemical and radioactive contaminants). Underground storage was built for food, fuel, fresh water, and other supplies for the facility which was capable of supporting 350 people for 90 days. These blast shelters, nicknamed "Diefenbunkers", were administered by the Canadian Corps of Signals.

Opening in 1964, the Debert facility was already outdated, since ICBM targeting had improved to the point where a direct hit was possible on the bunker. However the site persisted as a Provincial Warning Centre (for Nova Scotia), staffed by the 720 Communication Squadron, along with the space for the emergency government. Antenna farms were dispersed from the bunker and were located on the shores of Cobequid Bay in nearby Masstown as well as in the Cobequid Hills near Londonderry.

On February 1, 1968, the merger of the three service branches into the Canadian Forces saw the Diefenbunker and support facilities, the last remnants of Camp Debert, change its name to Canadian Forces Station Debert (CFS Debert), in keeping with the naming convention for minor military facilities across Canada.

In the 1970s, CFS Debert, as with most Diefenbunker facilities across the country, was downgraded further as the number of personnel were reduced. Attempts to find other uses for the remaining military facilities took place through the 1980s with militia reserve units training at CFS Debert.

In 1982 CFS Debert was equipped with Telegraph Automated Relay Equipment (TARE) which was used to relay communications received at the nearby Satellite Ground Terminal Folly Lake.

The end of the Cold War and reduction in the ICBM threat, as well as the Diefenbunker's obsolescence, saw all remaining military personnel removed from CFS Debert by the mid-1990s. In 1998 the Department of National Defence finished all environmental assessments and decommissioned the facility, transferring the facility to "Colchester Park", a local development authority.

Today the only remnant of a once-vast military presence in Debert is a firing range used by militia reserve units from Cumberland, Colchester and Pictou counties.

In 1985 the Royal Canadian Air Cadets began to use the airfield for glider training. The first year saw air tow and winch operations, later years used a significant amount of auto tow supplemented with air tow launches. The regional gliding school used the agricultural college in Truro for the ground school, administration and dormitories.

In 2005, the Royal Canadian Air Cadets used the Diefenbunker for its Regional Gliding School (Atlantic) Headquarters. Air cadets from Atlantic Canada ranging in age from 15 to 18 trained at the adjacent Debert Airport for the Advanced Aviation Course and Glider Pilot Scholarship programs.

In December 2008 the 64000 ft2 Diefenbunker was sold by the Colchester Regional Development Association to a private data warehousing and data centre co-location services provider, Bastionhost. Bastionhost was going to renovate the facility as a high-density, groundwater-cooled data centre.

In November 2012 the Diefenbunker was sold again by the Municipality of the County of Colchester to recover unpaid taxes from the previous owner, Dataville Farms Ltd. It was purchased by Jonathan Baha'i for $31,300 along with the adjoining parking lot for $4150. The new owner has indicated he intends to use the facility for a data centre with an emphasis on cloud storage. Other parts of the facility may be used for unspecified research and development. In 2013, a part of the bunker was used to film an independent movie, Bunker 6. It was also used for a paintball game.

The previous CBC Studio located in the bunker has been turned into a media recording studio called Top Secret Sounds.

June 2014 the official website for the Debert Diefenbunker revealed the intent to offer leased space within the bunker including self-storage.

Debert Military Museum
The Debert Military Museum maintains Debert's military history with a nineteen-room museum located in "Colchester Park". The museum is a registered charity and is managed by a volunteer board of directors. The museum has a diverse collection of military memorabilia from both World Wars as well as the Cold War and Korean War. The Debert Military Museum is the only museum in Canada that houses a display of Russian photographs presented to the Museum by the Russian Ambassador of Canada. The museum features items donated by members and family members of the Canadian and British militaries, including uniforms, decorations, communications equipment and documents. It no longer offers tours of the Debert Bunker, while still retaining information and artifacts about it.

title: CFS Debert


text:
Boeing Defense, Space & Security

Boeing Defense, Space & Security (BDS) is a division of The Boeing Company based in Arlington, Virginia, near Washington, D.C. The division builds military airplanes, rotorcraft, and missiles, as well as space systems for both commercial and military customers, including satellites, spacecraft, and rockets.

It was formerly known as Boeing Integrated Defense Systems (IDS), which was formed in 2002 by combining the former "Military Aircraft and Missile Systems" and "Space and Communications" divisions. The group that brought together major names in aerospace; Boeing Military Airplane Company; Hughes Satellite Systems; Hughes Helicopters (the civilian helicopter line was divested as MD Helicopters); Piasecki Helicopter (subsequently known as Boeing Vertol and Boeing Helicopters); the McDonnell division of McDonnell Douglas; and the former North American Aviation division of Rockwell International.

Boeing Defense, Space & Security made Boeing the third-largest defense contractor in the world in 2021 and helped make Boeing the second-largest U.S. federal government contractor in fiscal year 2019.

History
Boeing Defense, Space & Security was headquartered in Greater St. Louis north of St. Louis Lambert International Airport in the northern St. Louis suburb of Berkeley, Missouri, until January 2017, when top executives and support staff were relocated to Arlington, Virginia. There are also significant operations in nearby Missouri communities, such as Hazelwood and St. Charles. It remains one of the largest employers in Greater St. Louis with 13,707 local employees as of 2018.

Other major locations of BDS are in California and Washington state. Boeing chose to locate the defense systems offices in the St. Louis area because of the role of the space and aircraft programs of the former McDonnell Douglas location, and bipartisan support from area politicians.

In 2016, Boeing moved the division headquarters from St. Louis to Arlington, Virginia in the Washington, D.C. area and located close to The Pentagon.

Organization
Boeing BDS has four divisions focused on vertical lift; mobility, surveillance and bombers; air dominance; and space, intelligence and weapons systems.

 * Vertical Lift – The world's largest provider of military rotorcraft including cargo, tiltrotor, and attack.
 * Mobility, Surveillance & Bombers – Includes KC-46, SAOC, E-7, VC-25B, P-8, Bombers, AWACS/AEW&C.
 * Air Dominance – Includes classified programs; the F/A-18, F-15, T-7, MQ-25 and MQ-28 programs; and the non-space Phantom Works portfolio.
 * Space, Intelligence & Weapon Systems – Includes space exploration and launch programs, satellites, munitions, missiles, weapon system deterrents, maritime undersea, Phantom Works Space and subsidiaries (BI&A, Millennium, Insitu, Liquid Robotics, Spectrolab, Argon and DRT).

Bomber aircraft

 * Boeing YB-9
 * Boeing XB-15 (1 prototype)
 * Boeing B-17 Flying Fortress
 * Boeing XB-38 Flying Fortress
 * Boeing YB-40 Flying Fortress
 * Boeing C-108 Flying Fortress
 * List of Boeing B-17 Flying Fortress variants
 * Boeing Y1B-20
 * Boeing B-29 Superfortress
 * Boeing KB-29 Superfortress
 * Boeing XB-39 Superfortress
 * B-29 Superfortress variants
 * Boeing B-47 Stratojet
 * Boeing B-50 Superfortress
 * Boeing B-52 Stratofortress
 * Boeing B-54
 * Boeing XB-55
 * Boeing XB-56
 * Boeing XB-59
 * Boeing TB – torpedo bomber
 * Rockwell B-1 Lancer — from acquisition of North American Aviation division of Rockwell International

Rotorcraft

 * Boeing AH-6
 * Boeing AH-64 Apache
 * Boeing Vertol CH-46 Sea Knight (Vertol Aircraft Corp.)
 * Boeing Vertol CH-47 Chinook (Vertol Aircraft Corp.)
 * Boeing Chinook (UK variants)
 * Boeing Vertol YUH-61
 * Boeing Vertol XCH-62
 * MH-139 Grey Wolf (with Leonardo S.p.A.)
 * V-22 Osprey (with Bell Helicopter)
 * Quad TiltRotor (with Bell Helicopter)
 * RAH-66 Comanche (with Sikorsky), reconnaissance and light attack helicopter, canceled
 * SkyHook JHL-40

Fighter and attack aircraft

 * Boeing Model 15
 * Boeing F2B
 * Boeing F3B
 * Boeing XF6B
 * Boeing XF8B
 * Boeing F-15E Strike Eagle
 * Boeing F-15SE Silent Eagle
 * Boeing F-15EX Eagle II
 * Boeing F/A-18E/F Super Hornet
 * Boeing EA-18G Growler
 * Lockheed Martin F-22 Raptor (partner with prime contractor Lockheed Martin)
 * Boeing GA-1
 * Boeing XP-4
 * Boeing XP-7
 * Boeing XP-8
 * Boeing XP-9
 * Boeing P-12
 * Boeing XP-15
 * Boeing P-26 Peashooter
 * Boeing P-29
 * Boeing X-32, Boeing's entry for the Joint Strike Fighter program

Experimental aircraft

 * Boeing Bird of Prey
 * Boeing X-40
 * Boeing X-53 Active Aeroelastic Wing

Tankers and transport aircraft

 * Boeing YC-14
 * Boeing C-17 Globemaster III
 * Boeing C-22
 * Boeing VC-25
 * Boeing C-32
 * Boeing C-40 Clipper
 * Boeing KC-46 Pegasus
 * Boeing C-97 Stratofreighter
 * Boeing KC-97 Stratofreighter
 * Boeing C-127
 * Boeing C-135 Stratolifter
 * Boeing EC-135
 * Boeing KC-135 Stratotanker
 * Boeing NC-135
 * Boeing OC-135B Open Skies – (3 Treaty on Open Skies observation aircraft)
 * Boeing RC-135
 * Boeing WC-135 Constant Phoenix
 * Boeing C-137 Stratoliner
 * Boeing CC-137
 * Boeing KC-767
 * Boeing Pelican

Trainer aircraft

 * Boeing Model 2
 * Boeing XAT-15
 * Boeing NB
 * Boeing T-43 navigator trainer
 * Boeing Skyfox
 * Boeing–Saab T-7 Red Hawk

Electronic warfare, surveillance and other military variants

 * Boeing 737 AEW&C (E-7 Wedgetail)
 * Boeing Model 42
 * Boeing YAL-1 Airborne Laser
 * Boeing E-3 Sentry (an Airborne Early Warning and Control or AWACS surveillance aircraft)
 * Boeing E-4 (Advanced Airborne Command Post)
 * Boeing E-6 Mercury
 * Boeing E-767 (AWACS)
 * Boeing P-8 Poseidon (Anti-submarine warfare)
 * Boeing XPB
 * Boeing XP3B
 * Boeing XPBB Sea Ranger
 * Boeing RC-135

Utility aircraft

 * Boeing Model 1
 * Boeing L-15 Scout

Unmanned aerial vehicles

 * Boeing Insitu RQ-21 Blackjack
 * Boeing YQM-94
 * Boeing CQM-121 Pave Tiger – anti-radar drone
 * Boeing X-45//Phantom Ray – technology demonstrators
 * Boeing X-46
 * Boeing X-48
 * Boeing X-50 Dragonfly – experimental Gyrodyne UAV
 * Boeing X-51
 * Boeing A160 Hummingbird – development UAV helicopter
 * Boeing Condor
 * Boeing DARPA Vulture
 * Boeing HALE
 * Boeing Insitu ScanEagle
 * Boeing MQ-25 Stingray
 * Boeing Phantom Eye – a high altitude, long range UAV
 * Boeing Persistent Munition Technology Demonstrator
 * Boeing SolarEagle
 * GQM-163 Coyote
 * MA-31
 * Boeing MQ-28 Ghost Bat – previously known as Airpower Teaming System

Missiles

 * Arrow 3
 * CIM-10 Bomarc
 * LGM-30 Minuteman
 * AGM-69 SRAM
 * AGM-86 ALCM cruise missile
 * MGM-118 Peacekeeper
 * Ground-Based Midcourse Defense
 * Ground-Based Interceptor
 * UUM-125 Sea Lance
 * AGM-131 SRAM II
 * Boeing Ground-to-Air Pilotless Aircraft
 * Harpoon (missile)
 * Standoff Land Attack Missile
 * AGM-84H/K SLAM-ER

Space launch and spacecraft

Boeing Launch Services Inc. (BLS) is Boeing's commercial launch service provider. On behalf of its commercial customers, BLS administers launch service contracts for Delta II and Delta IV launches conducted by United Launch Alliance. In November 2010, Boeing Defense, Space & Security was selected by NASA for consideration for potential contract awards for heavy lift launch vehicle system concepts, and propulsion technologies.
 * S-IC first stage
 * Lunar Roving Vehicle
 * X-38 Crew Return Vehicle
 * Inertial Upper Stage (Titan IV and Space Shuttle)
 * International Space Station
 * Space Shuttle orbiter (Rockwell)
 * Delta (rocket family) (aka Thor-Delta)
 * Delta II rocket
 * Delta III rocket
 * Delta IV rocket
 * Sea Launch (with Energia, Aker Kværner, and Yuzhnoe)
 * Starliner crewed space capsule
 * Space Launch System core stage
 * Human Landing System

Spaceplanes

 * Boeing X-20 Dyna-Soar (canceled)
 * Boeing X-37
 * Boeing X-40

Satellites

 * ARGOS (satellite)
 * Autonomous Space Transport Robotic Operations (ASTRO)
 * GPS Satellites (Rockwell)
 * Integrated Solar Upper Stage
 * Kinetic Energy Anti-Satellite Weapon System
 * XSS Micro-satellite
 * 376 (formerly Hughes Satellite Systems – HSS)
 * 601 (formerly HSS)
 * 702 (formerly HSS)

Space probes

 * Lunar Orbiter program
 * Surveyor program
 * Mariner 10
 * Mars Science Laboratory

Other

 * AN/TWQ-1 Avenger – lightweight air defense vehicle
 * Pegasus-class hydrofoil – patrol craft (6 built by Boeing Marine)
 * GBU-39 Small Diameter Bomb – 250 lb glide bomb
 * Compact Laser weapon system
 * Tactical Laser weapon system

Facilities
On July 21, 2006, Boeing announced that it would be consolidating its Southern California locations. The Boeing facility in Anaheim will be moving to Huntington Beach, California.
 * Huntsville, Alabama (Spacelab, International Space Station, Delta, Ground-based Midcourse Defense)
 * Mesa, Arizona (AH-64, AH-6i)
 * Anaheim, California
 * El Segundo, California (satellite complex: 601, 702)
 * Long Beach, California (C-17 until 2015)
 * Palmdale, California (Space Shuttle)
 * Pleasanton, California
 * Seal Beach, California Saturn V rocket and Apollo Capsule (original contractor North American later Rockwell International)
 * Huntington Beach, California (Saturn V, X-51A, Apollo, Skylab, Space Shuttle, Delta, and ISS)
 * Kennedy Space Center, Florida (as part of United Space Alliance and United Launch Alliance)
 * Macon, Georgia (C-17, a-10, ch-47) Closing down December 2016
 * New Orleans, Louisiana (S-IC stage – Boeing was the prime contractor where the Michoud Assembly Facility was used for the final assembly)
 * St. Louis, Missouri (F-15, F/A-18)
 * St. Charles, Missouri (weapons)
 * Tulsa, Oklahoma (F-15/F-15E)
 * Philadelphia, Pennsylvania (H-47, V-22) H-46 production ended.
 * El Paso, Texas (B-1B, PAC-3, power and electronics components for ISS, F-22, and F-15, assembly and test for Minuteman III missile guidance system)
 * Houston, Texas
 * San Antonio, Texas (military aircraft maintenance)
 * Puget Sound region, Washington
 * Washington, D.C. area

title: Boeing Defense, Space & Security


text:
Boeing Commercial Airplanes

Boeing Commercial Airplanes (BCA) is a division of the Boeing Company. It designs, assembles, markets, and sells commercial aircraft, including the 737, 767, 777, and 787, along with freighter and business jet variants of most. The division employs nearly 35,000 people, many working at the company's division headquarters in Renton, Washington or at more than a dozen engineering, manufacturing, and assembly facilities, notably the Everett Factory and Renton Factory (both outside of Seattle), and the South Carolina Factory.

It includes the assets of the Douglas Aircraft division of the former McDonnell Douglas Corporation, which merged with Boeing in 1997. As of the end of 2021, BCA employed about 35,926 people.

Organization
Boeing Commercial Airplanes (BCA) is organized as:
 * Airplane Programs
 * Boeing Renton Factory – 737
 * Boeing Everett Factory – 767 and 777
 * Boeing South Carolina – 787
 * Fabrication Division
 * Global Partners
 * Propulsion Systems
 * Commercial Aviation Services

BCA subsidiaries:
 * Aeroinfo Systems
 * Aviall
 * Aviation Partners Boeing, a 50/50 joint venture with Aviation Partners Inc.
 * Boeing Canada
 * Boeing Capital
 * Boeing Training & Flight Services (was Alteon Training)
 * CDG
 * Jeppesen, formerly Jeppesen Sanderson.
 * Preston Aviation Solutions

Management
In November 2016, Boeing announced that Ray Conner would step down immediately as BCA's president and CEO. He was succeeded by Kevin G. McAllister, who was the first outside recruitment in BCA history. McAllister was instructed by Dennis Muilenburg to triple revenue from aftermarket services from $15 billion to a target of $50 billion over 10 years, with a new purpose-built unit headed by Stan Deal. Keith Leverkuhn was the vice president and general manager of the 737 MAX program in March 2017 when it received certification.

McAllister was eventually ousted by Boeing in October 2019, in the midst of a company crisis following two fatal crashes of its 737 MAX jets. Stan Deal succeeded him in both of his positions. One insider called McAllister a "scapegoat" as he had only joined BCA during the later stages of the 737 MAX's development. In March 2024, Deal was in turn replaced by Stephanie Pope, formerly head of the Boeing Global Services division.

Model naming convention
For all models sold beginning with the Boeing 707 in 1957, except the Boeing 720, Boeing's naming system for commercial airliners has taken the form of 7X7 (X representing a number). All model designations from 707 through 787 have been assigned, leaving 797 as the only 7X7 model name not assigned to a product.

For models 707 to 777, the full model number consists of an airplane's model number, for example, 707 or 747, followed by a hyphen and three digits that represent the series within the model, for example, 707-320 or 747-400. In aviation circles, a more specific model designation is sometimes used where the last two digits of the series designator are replaced by the two-digit, alpha-numeric Boeing customer code, for example, 747-121, representing a 747-100 originally ordered by Pan American World Airways (Boeing customer code 21) or 737-7H4, representing a 737-700 originally ordered by Southwest Airlines (Boeing customer code H4). Codes do not change for aircraft transferred from one airline to another. Unlike other models, the 787 uses a single digit to designate the series, for example, 787-8. This convention was followed in the development of the newest version of the 747, the 747-8, along with the 737 MAX and 777X series.

Additional letters are sometimes appended to the model name as a suffix, including "ER" to designate an "extended range" version, such as the 777-300ER, or "LR" to designate a "long range" version, for example 777-200LR. Other suffix designators include "F" for "freighter" (747-400F), "C" for "convertible" aircraft that can be converted between a passenger and freighter configuration (727-100C), "SR" or "D" for "short range" and "domestic" (747-400D, 747SR), and "M" for "combi" aircraft that are configured to carry both passengers and freight at the same time (757-200M, 747-400M). Passenger aircraft that are originally manufactured as passenger aircraft and later converted to freighter configuration by Boeing carry the suffix "BCF" designating a Boeing converted freighter (747-400BCF).

Orders and deliveries
The table below lists only airliners from the jet era. Data from Boeing through April 2023

Specialty and other aircraft
Airlines commonly order aircraft with special features or options, but Boeing builds certain models specifically for a particular customer.
 * The Boeing 707-138B was a shortened-fuselage, long-range model only sold to Qantas.
 * The Boeing 757-200M was a single-example model built for Royal Nepal Airlines (now called Nepal Airlines). This plane could be converted between passenger and freighter configuration. It was launched by Royal Nepal Airlines in 1986 and delivered two years later.
 * Boeing 747
 * The Shuttle Carrier Aircraft
 * The Boeing 747 Large Cargo Freighter (now named the Dreamlifter) is a wide-body cargo aircraft.
 * The 747SP production resumed nearly four years after the supposedly final 747SP was built. It had a cockpit crew of two instead of the three-crew layout of other 747SPs.
 * Two Boeing VC-25s were built for the US Air Force as Presidential Air Force One transports. This model was a highly modified 747-200B.
 * Four Boeing 747-100SRs were built for Japan Airlines for a domestic flight service.
 * Nine Boeing 747-100Bs were built for Iran Air and Saudi Arabian Airlines, which had a stronger airframe and landing gear, as well as an increased fuel capacity.
 * Boeing was a consultant to Sukhoi on the Russian Regional Jet program that subsequently became the Sukhoi Superjet 100 twin-engine narrowbody airliner.

Concepts

 * Boeing 2707 – supersonic airliner, canceled
 * Boeing 7J7 – high-efficiency propfan airliner, canceled
 * Boeing 747-300 Trijet – high-efficiency trijet version of the Boeing 747-200, canceled
 * Boeing 777-100/777 trijet – the original proposed version of the Boeing 777
 * Boeing New Large Airplane – double-deck jumbo airliner, canceled
 * Boeing New Midsize Airplane – targeting the middle of the market segment
 * Boeing RC-1 – cargo aircraft, canceled
 * Boeing Sonic Cruiser – near-sonic airliner, canceled
 * Boeing Liquid Hydrogen (LH2) airplane that uses liquid hydrogen as fuel
 * Hypersonic Airliner Concept. Mach 5 speed
 * Boeing 747-500 – larger ultra-haul version of the Boeing 747
 * Boeing X-66 – experimental Transonic Truss-Braced Wing airliner

Airfoils

 * Boeing 103 – used on Model 40 and F2B
 * Boeing 103A – used on F2B and F3B
 * Boeing 106 – used on Model 80, P-12, Monomail, Model 226
 * Boeing 106B – used on Model 95, Model 247D, P-12
 * Boeing 106R – used on various Beriev models
 * Boeing 109 – used on Model 95 and P-26
 * Boeing 117 – used on XPBB, B-29 and derivatives (307, 367, 377), all Aero Spacelines models, Tupolev Tu-4, Tu-70, Tu-75 and Tu-80.

Major facilities

 * Long Beach, California – Former McDonnell Douglas aircraft assembly, currently supports Boeing Commercial Airplanes
 * Seattle – Puget Sound region, Washington
 * Boeing Field, Seattle – Final delivery of 737, flight testing of all aircraft
 * Boeing Everett Factory, Everett – 767 and 777 production and final assembly plant
 * Boeing Renton Factory, Renton – 737 production and final assembly plant
 * Boeing South Carolina, North Charleston, South Carolina – 787 production and final assembly plant

title: Boeing Commercial Airplanes


text:
Talk:Hapa

Wikipedia's Problem Exemplified
A quick review of this talk page and the article's edit history demonstrates one user consistently chasing others away under the claim of accuracy.

"The loose collective running the site today, estimated to be 90 percent male, operates a crushing bureaucracy with an often abrasive atmosphere that deters newcomers who might increase participation in Wikipedia and broaden its coverage." - Tom Simonite, "The Decline of Wikipedia" 64.25.200.86 (talk) 05:00, 25 March 2014 (UTC)

Polyglottz Returns With Anonymous IPs
If we're going to talk about the edit history, it's worth noting that the only person who's constantly been reverting has been Polyglottz, who has been banned from Wikipedia for his use of sockpuppets.

Every month or two, someone from a 64.x.x.x IP address returns to the article to make the exact same claims as Polyglottz and make the exact same reversions. If anyone should be accused of "one user consistently chasing others away under the claim of accuracy", it would be Polyglottz and his new anonymous IPs. — Preceding unsigned comment added by GaryKia (talk • contribs) 05:55, 27 March 2014 (UTC)

Let's keep this simple people
Replaced intro section with Oxford dictionary def. Linguistic arguments should be handled in the article's body.64.80.128.4 (talk) 16:19, 12 June 2014 (UTC)

Edit War - Please Stop!
There apparently is an edit war started by 166.170.x.x. Please stop. If you don't stop, the edit war will be reported to the Wikipedia authorities.

RfC: Should we use the Oxford English Dictionary definition for "hapa"?
Should the article opening use the Oxford English Dictionary definition of "hapa"? One argument states the word has moved into mainstream English, as evidenced by the OED definition ("a person who is of partial Asian or Pacific Islander descent"), then follows article lead with the word's usage in Hawaii. Another edit argues the OED is not a reliable source on non-English words and leads with a Hawaiian-centric definition ("a person of mixed ethnic heritage"), then follows with California-centric usage. Sinoboalt (talk) 05:48, 15 April 2015 (UTC)

 * Comment: Why would we explicitly favo[u]r one source over another? The talk page here is evidence that this term is controversial, so we should treat it from multiple reliable sources, not take a stand on what one source says it "does" mean.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  13:51, 22 April 2015 (UTC)

Oppose First, as SMcCandlish stated, we shouldn't be favoring a single source over another. Second, we can't anyway because of copyright and Wikipedia is not a dictionary. The suggestion that the word has entered the English language is awkward at best with only a primary dictionary source and no secondary source making the claim. The suggestion that this is entering the English language would make this a Neologism and therefore should probably be deleted, as is increasingly likely due to the history of this article and recent edit warring. Per WP:NEO: "Care should be taken when translating text into English that a term common in the host language does not create a neologism in English." I feel this needs to be formally addressed at AFD.--Mark Miller (talk) 09:59, 1 May 2015 (UTC)
 * Comment/Sorta: I agree with SMcCandish; would both disputing parties be in favor of two definitions? Personally, I always find disputes like this interesting reading and think much of what is on our talk pages should also be on our article pages. That said, OED isn't the most reliable source for non-English words. Over and over again, I have seen them make great errors. So if for some reason this dispute cannot be resolved with multiple definitions from multiple sources, I would wholeheartedly give OED a big thumbs down. LesVegas (talk) 00:11, 30 April 2015 (UTC)
 * Comment The sources for this are not very strong. Hapa as a single word does NOT denote half white...it just means half. Has anyone gone through the sources and/or provided academic Hawaiian language sources or checked to verify the content from the sources currently in use? The article is rather insulting the way it is written and seems way off from the use as I understand it. It would appear that its use from pigeon may make this a neologism.--Mark Miller (talk) 08:04, 1 May 2015 (UTC)

The Current Edit is the Most Neutral and Objective
Sinoboalt, your characterization of the situation is not accurate. The way the article is right now (April 15, 2015) is the best way to present the word because the first sentence of the lead describes BOTH definitions. Whether one is a hapa of any mix (Hawaiian usage) or a hapa of partial Asian or Pacific Islander heritage (Californian usage), both are "person[s] of mixed ethnic heritage." Therefore, it isn't accurate to say that the current edit "leads with a Hawaiian-centric definition." The first sentence of the current edit's lead is the most neutral way to portray the two usages.

As for the Oxford English Dictionary, there are several problems with the contention that we should defer to the Oxford Dictionary. First of all, the link is actually to the OxfordDictionaries.com website, which is not the same as the official Oxford English Dictionary. Second, the OxfordDictionaries.com website doesn't actually distinguish between mainstream American English (i.e. English that is used nationally across the US) and regionalisms. For example, if you look up "wicked" on UrbanDictionary.com , you'll see that it's clearly a New England slang word. If you look up "wicked" on OxfordDictionaries.com , definition 1.4 makes it sound like the word is used nationally in the way that New Englanders use it. Since OxfordDictionaries.com does not even properly distinguish between regionalisms and true mainstream American English, there is no reason to trust that Oxford has properly verified that "hapa" has entered national usage merely due to its inclusion on the website.

As we can see, it makes most sense for the first sentence of the lead to be the generic definition of "a person of mixed ethnic heritage" which is inclusive of both the Hawaiian and Californian usages and then to elaborate on the two specific regional usages. Until there is substantial evidence that the Californian usage has spread beyond California, there is no reason to have the first sentence of the lead give primacy to the Californian usage when a neutral first sentence is much more appropriate and accurate.

 * As the defining sentence, "A hapa is a person of mixed ethnic heritage" does not include a definition that it is a person of a specific mixed ethnic heritage. The unqualified defining sentence states that there is no qualification.  An accurate definition, if we believe the word is actually used two ways, would be, "A hapa is a person of mixed ethnic heritage, in some usage a mixture of Asian or Pacific Islander and something else, and in other usage any mixture at all."

 * The regional variation is too complex to be in the intro at all. I doubt there is solid evidence that the Californian usage is limited to California, or that it pervades California, for example (and I personally doubt either of those is true), so a simple statement that the word is used a certain way in California is misleading.  The intro therefore should just generally state there are multiple usages, possibly varying regionally, and a later section should detail what is known about who uses the word which way.  Bryan Henderson (giraffedata) (talk) 00:56, 20 April 2015 (UTC)

 * Bryan, the two usages are already laid out. If you change the lead to your proposed sentence, it takes the usages out of historical context. The original word was—and continues to be, since Hawaii still exists—Hawaiian. Stating the Hawaiian definition clearly only makes sense since it's still used in Hawaii to mean "of any ethnic mix". As for the Californian usage, the sources cited in the article are mostly from California, and furthermore, some of them specifically cite California as where people use the term hapa to mean "of partial Asian or Pacific Islander heritage". When all the sources are either from California or specifically mention California, it's not hard to conclude that it's a Californian usage. — Preceding unsigned comment added by GaryKia (talk • contribs) 03:19, 21 April 2015 (UTC)
 * I'm sorry but that is simply not accurate. The word is from the Hawaiian language. If indeed it is being used in California (never heard it used here myself) then it really is likely to be a neologism. Anyway, there are more than a single definition:

--Mark Miller (talk) 08:14, 1 May 2015 (UTC)
 * Also adding the Kahako will not only change pronunciation but definition as well. The article might want to mention that.--Mark Miller (talk) 08:15, 1 May 2015 (UTC)

The problem is the topic of the article
The main article must include, at at a minimum, that many Caucasians find the term racist.

Please provide proof beyond your opinion that "many Caucasians find the term racist." That is not true in Hawai'i although I cannot provide at this moment a published cite to "prove" that per Wikipedia requirements. — Preceding unsigned comment added by 66.162.249.170 (talk) 02:38, 24 May 2016 (UTC)

This article is fundamentally flawed in that it is not an article about hapas. It's an article about the word hapa. If it were about hapas, it would be about one kind or the other and it would be clear what to say in the intro. And a terminology section could clear up any disputed usage. But as an article about the word, then the lead should read like, "The word hapa is used in English to mean either ..." and it should definitely say at some point what OED says about the word. Bryan Henderson (giraffedata) (talk) 01:04, 20 April 2015 (UTC)
 * It's a Hawaiian Language word. Wikipedia is not a dictionary. It should pertain only to that which has encyclopedic value and only mention the definition as part of the overall summary of the subject...but hapa as a subject...I'm really not sure.--Mark Miller (talk) 08:08, 1 May 2015 (UTC)

Some consider this term to be racist
Because some people have more sensitive cultural beliefs to others, therefore for those people, it's only fair; this should not be in Wikipedia. IllogicMink (talk) 07:46, 20 April 2015 (UTC)

And many others do not. The word haole is much more likely to be used in a racist context than the term hapa haole. Now, shall I find you a cite to "prove" that per Wikipedia requirements? — Preceding unsigned comment added by 66.162.249.170 (talk) 02:20, 24 May 2016 (UTC)

Sources, claims etc.
All of the sources for this article need to be gone over with a fine tooth comb. Wikipedia is not a place to propagate any racial animosities or falsehood based on weak sources or academic sources that may be limited in relevance. The article suffers greatly from a haphazard (no pun intended) structure with a list of terms that have no referencing. I also feel strongly that the Hawaiian language is being misrepresented in this article and for that reason, amongst many others, this article should be pared down to a stub if necessary to remove sources that do not support claims, claims and text of a contentious or controversial nature that have no sourcing and any content that is not directly related to the word itself. After that, an AFD nomination is very likely.--Mark Miller (talk) 10:13, 1 May 2015 (UTC)

Google results and this article - speedy delete request
It appears this article was created in violation of at least one BLP policy regarding the naming of multiple living persons under this umbrella term that is highly contentious and controversial. It is an attempt to create a neologism and push this into reality through Wikipedia. I'm a little offended, but that's not the point. While I am tempted to see this as a hoax article, it is likely it is just one of a number of anonymous IP created articles from before 2005 that has escaped any real scrutiny from anyone with knowledge of the Hawaiian language, its culture, customs etc.. The result of this ill informed and under researched article is a Google result that highlights this article and term in a Google spotlight on the search result page. I believe it is possible that this article may meet criteria for speedy deletion.--Mark Miller (talk) 21:04, 1 May 2015 (UTC)

 * (Bolding for emphasis)
 * The article began with biographical material about living persons (still in the history) that is entirely negative in tone and un-sourced. Calling someone a "Hapa hoale" is NOT a compliment and is NOT a neutral phrase. It is meant to disparage the ethnicity of the person as being less than someone else's with a higher blood quantum, nationality etc..

 * While I am not saying this was meant as an actual hoax, it still falls within the G3 criteria (bolding for emphasis):

Basically the issue is this; the article uses Wikipedia's voice of authority to create a non existing subject. A "Hapa" is not a person, it is not a phrase for a person. It is simply a Hawaiian language word with different meanings depending on how it is used. Hapa, in fact, also means "Harp".--Mark Miller (talk) 21:22, 1 May 2015 (UTC)

 * Doesn't violate any BLP policy as it is not a BLP and no living persons (or even dead ones) are mentioned in the article. Also, the article does not say "Hapa is a person" it says "Hapa is a term used to describe a person of mixed ethnic heritage". Nothing contentious about that. Softlavender (talk) 14:15, 3 May 2015 (UTC)
 * Actually, cleaned up or not, this article history clearly shows this listed living persons. That was never scrubbed and this offensive article should just be deleted.--Mark Miller (talk) 09:08, 29 May 2015 (UTC)
 * The article does not list a single specific person by name, living or dead, and it hasn't in over two years. And there is also nothing offensive about the term; on the contrary, it's just an everyday word to describe someone's ethnicity, and since the majority of people born in Hawaii are racially mixed (often extremely mixed with all kinds of ethnicities and nationalities in one person), it's a very common term. There is nothing offensive about this article; it is an informational article about a very common Hawaiian term. Softlavender (talk) 09:43, 29 May 2015 (UTC)

Note to IPs editing this article
Please stop edit-warring, IP-hopping, adding innumerable unnecessary, unreliable, and non-substantiating citations, and adding inaccurate and uncited sentences. Right now we have an IP-hopper from Wichita using at least four different IPs so far, and we have IPs and IP hoppers from California and Singapore and elsewhere. These contributions have not been constructive or within Wikipedia guidelines, and therefore a neutral, short, and cited version of the article has been instated. Please do not alter it, and please discuss all matters on this Talk page before proceeding further. Thank you. Softlavender (talk) 04:44, 29 May 2015 (UTC)

 * Softlavender, you're not making much sense. Your edit completely disregards the entire history of this article's talk page. Go back to the archives. In any case, the Taniguchi and Heidenreich citation makes it very clear that your edit is not the general definition of hapa in Hawaii. Furthermore, your edit is about the definition of hapa haole, not hapa.

 * By the way, you should stop being hypocritical. Why are you edit warring yourself and then telling others to stop edit warring? You're clearly vandalizing the article. Being an experienced editor doesn't mean you're not capable of vandalism yourself. — Preceding unsigned comment added by 216.4.56.185 (talk) 05:06, 29 May 2015 (UTC)

 * You've been edit-warring on this article for over two weeks (in this go-round) using at least four different IPs and instating content that is uncited opinion. You did the same thing last month, last year, and two years ago. Please stop. Softlavender (talk) 05:32, 29 May 2015 (UTC)

full protection
Okay, that's enough. The page is locked until consensus can be reached on this little opening paragraph. As I said on the RFPP page, the reverting editors are very fortunate not to be blocked for 3RR, so work it out here.  K rakatoa    K atie   05:56, 29 May 2015 (UTC)

 * , the IPs don't want to work it out, they want to edit-war and IP hop. If you look at the article history, you can see that from the three previous marathon non-stop IP edit wars: July 21 – October 5, 2013 (then semied for one week); October 14 – November 3 2013 (then semied for one month); and a 9-month nonstop IP edit war from July 2 2014 – April 14, 2015 (semied for three weeks, edit war started up again afterwards). The solution to the problem is not short-term semi-protection or full protection; it's permanent semi-protection. Otherwise, there will just be another marathon non-stop IP-hopping edit war, this time probably for possibly longer than 9 months. Softlavender (talk) 06:21, 29 May 2015 (UTC)
 * Well, now, semi-protection would solve your problem but not theirs, would it? This is not vandalism. This is a content dispute, and you were edit-warring right along with them. There is a compromise here, and you guys need to reach it or the page stays locked.  K rakatoa    K atie   07:17, 29 May 2015 (UTC)
 * , I agree edit warred (today only, and I posted an attempt at discussion on this Talk page, and I did not abuse multiple accounts [i.e., IP hop]). I do not believe you have looked thoroughly at the history of the article that I pointed out, nor observed the fact that these IP-hoppers are not here to build an encyclopedia or edit cooperatively. I have no desire to solve any problem except the two-year history of repeated marathon many-month-long edit wars, which if you take a look you will see that are always from and by IPs, not logged-in accounts. Softlavender (talk) 07:37, 29 May 2015 (UTC)
 * Since there are IP accounts that are reverting each other and there are user accounts have have reverted your edits, rather than one IP "hopper", I think it is more likely that there are a number of different editors, whether they are IPs or user accounts, who disagree about the content of this article. KrakatoaKatie is correct that this is a content dispute that needs discussion to settle upon a consensus. Liz  Read! Talk! 09:42, 29 May 2015 (UTC)
 * There is an IP-hopper from Wichita that has used four different IPs in the past two weeks alone (216.4.56.185, 128.177.161.152, 128.177.161.190, 128.177.161.165), and has done this with other IP addresses in the other marathon edit wars of the past two years. Regardless, as I have mentioned, all of the three previous many-month-long non-stop marathon edit wars of the past two years have been IPs warring with each other, both IP hoppers and single IP addresses. Please look at the article history since July 2013. The IP edit wars start back every single time semi-protection has been removed. The content disputes are not going to be resolved until the article is under permanent semi-protection, because the problem is not content, but rather incorrigible and perennially recurring IP edit-warring (the last one was 9 months straight). That's the only way that editors can civilly discuss content, because the various IP edit-warriors are not here to build an encyclopedia, they are here to edit-war for nine months or longer at a time and "get their way". Softlavender (talk) 10:10, 29 May 2015 (UTC)

Hapa Article Evaluation
This article could use more citations. A few more references would be beneficial to the reader. The article itself is also very contradictory and offers confusing, maybe even false, information on the term “hapa.” The etymology section of the article was highly informational it just needs to be fully citated. I think a section about how the term is used today would be a useful as well as informational addition to this article.

104.174.150.163 (talk) 06:46, 23 October 2015 (UTC)

Developing a 'Multiracialism' Article
Hello, all. I'm working on developing the multiracialism article here on Wikipedia, and I aim to broaden the scope of the article to make it less Euro/American-centric. Furthermore, because of the article's current focus, the experiences of multiracial individuals of Asian and Pacific Island heritage have been overlooked. I have outlined my revisions and country-specific contributions (ex: what it might mean to be multiracial in the Philippines) briefly in my sandbox if you're interested in the work I have planned. I'd also love to know if any of you have sources or suggestions for how to approach the topic of multiracial identity formation through the lens of a mixed-Asian experience. --Tmsloan (talk) 21:46, 14 October 2019 (UTC)

Use outside of Hawaii
This term is also in use in Canada (as evidenced by the link to a Cdn film), is there anyone who could write about the term beyond Hawaii? — Preceding unsigned comment added by 104.246.130.230 (talk) 01:20, 7 September 2020 (UTC)

Disambiguation
I came here expecting to find a disambiguation page or a reason why one does not exist, since the page does not mention or discuss the usage of the word 'hapa' within sailing, that is a type of kite flown in the water rather than the air. It has become popular again with the attempt by Alex Caizergues to break the world sailing speed record, and thus probably merits mention in wikipedia. — Preceding unsigned comment added by 88.97.62.77 (talk) 12:39, 5 January 2022 (UTC)

Use of hapa outside of Hawaii and California
Hapa is in use in other states, specifically Massachusetts, Ohio, & Oregon. An effort to document this, albeit in overgeneralized terms, led this this sequence of events.
 * 47.152.225.229 cited examples of contiguous U.S. usage. Daily Free Press (Boston), portlandorgegon.gov, Ohio State University Activities. This editor changed In California to In the contiguous United States.
 * 196.206.91.24 reverted these edits without an edit summary.
 * 47.146.71.193 restored the added text with the edit summary no explanation given for deleting multiple citations showing usage in continental U.S..
 * Rather than fix the locations, 134.6.56.139 reverted the addition of cited material with the edit summary random places in the US, not all of contiguous US, it’s misleading.
 * I, Peaceray, restored the addition with the edit summary Please read the WP:VNT essay. Just because you disagree with a cited statement does not mean you get to remove it. As WP:BRD, discuss on the talk page before trying another change like this.
 * Without discusion on the talk page & failing to acknowledge the citations, 134.6.56.139 reverted the addition with the edit summary Disagreement is the only reason anyone reverts, the person trying to change it to “contiguous US” should discuss before changing the long-standing “California” language.
 * I again restored the text with the edit summary As WP:VNT explains, "Editors may not add content solely because they believe it is true, nor delete content they believe to be untrue, unless they have verified beforehand with a reliable source." The onus for removing cited material is for that editor to discuss on the talk page, unless you have provide more authoritative citations.
 * 69.193.149.162 reverted the addition with the edit summary Peaceray is clearly undoing my edits because THEY believe that it's untrue without discussing the matter themselves. They're being a hypocrite. "Contiguous United States" is not supported by the citations. Plain and simple.

In retrospect, I should have changed the text from the blanket contiguous United States to California, Massachusetts, Ohio, & Oregon. I will next do so. The latter is verified by the citations.

I will oppose removal of cited material without editors discussing it here first. I will abide by any consensus achieved here.

We should not be surprised that the term hapa has spread elsewhere. This is clearly an instance of trans-cultural diffusion & the wave model. Peaceray (talk) 02:53, 10 December 2022 (UTC)

70.187.234.198’s Problematic Reversion
70.187.234.198’s justification for reverting back to the misleading “contiguous United States” language is to add a bunch of random citations. Peaceray’s December 10, 2022 edit was very precise and accurate. Most people on the mainland US, outside of California, do not use the term hapa. Based on 70.187.234.198’s citations, it is unclear whether “hapa” is actually being used to mean “part Asian,” considering the source material in those citations use the term “multiracial” or “mixed” along with hapa, implying that “hapa” is being used in the vein of the Hawaii usage. Furthermore, Peaceray’s edit is superior to 70.187.234.198’s edit because Peaceray’s edit clearly denotes the non-Hawaii usage to be primarily Californian in origin while other incidental mentions of the word in the US is a phenomenon of transcultural diffusion. 134.6.56.139 (talk) 21:02, 12 December 2022 (UTC)

134.6.56.139’s characterization of SmithsonianAPA as a “random citation”
The SmithsonianAPA link appears to use Hapa to mean part Asian/Pacific Islander. It seems a reputable citation. 64.98.201.206 (talk) 05:20, 17 December 2022 (UTC)

Use/mention error
This article is about hapa, not about the word 'hapa', because Wikipedia is not a dictionary. Most of the article must be rewritten. 2A01:799:CA3:B300:D932:8F3:E221:9ED1 (talk) 08:47, 13 January 2023 (UTC)

WP:OVERKILL
@Peaceray Do we really need THIS many citations in the lead? DarmaniLink (talk) 05:21, 22 February 2024 (UTC)

 * there's clearly been some contention, so I want to ask you first DarmaniLink (talk) 07:25, 22 February 2024 (UTC)
 * If anything, some of these sources should be used to expand the body of the article, and then moved down there. Alyo  (chat·edits) 14:31, 22 February 2024 (UTC)
 * This is the case where the WP:5P5 pillar, & the WP:IGNORE & WP:EDITCONSENSUS policies, prevail over the WP:OVERKILL essay.
 * There was continual removal of the use of Hapa outside of Hawaii. You may have looked at the history & only seen my addition & modification of these citations, but failed to examine the history further back to see the repeated deletion of non-Hawaiin use of Hapa. These repeated removals seem to have ceased after the addition of the all the citations to the lead.
 * This problem seems to have abated in recent years. As suggests, it may be time to use some of these sources [...] to expand the body of the article & then move those sources there.
 * , since you seem to object to the inclusion of the all the citations in the lead, will you volunteer to do as Alyo suggests? I object to simply removing the citations from the article, even if they seem contrary to the spirit of the OVERKILL essay. Peaceray (talk) 16:52, 22 February 2024 (UTC)
 * if there was disruptive editing prior, and that quantity of citations managed to stop it, they can stay
 * it was just jarringly many and I saw some contention on the talk page, so, I wanted to ask first :) DarmaniLink (talk) 17:08, 22 February 2024 (UTC)

Fixing the IPA
@Nardog Rather than have me seemingly edit war the proper way back in, and possibly get reverted again, can you fix it? I don't know what your objection is. DarmaniLink (talk) 18:50, 22 February 2024 (UTC)

 * Done, with a source. Wiktionary was very unhelpful as $⟨a⟩$ is ambiguous as to whether it's TRAP or PALM, and as [ɐ] is an allophone of /ə/ so the repetition was meaningless. Nardog (talk) 18:56, 22 February 2024 (UTC)

title: Talk:Hapa


text:
Wikipedia:Articles for deletion/HBD

Text of article: ''HBD is a three letter acronym meaning "Here Be Dragons". This is reputed to have been written on ancient maps to demarcate uncharted territory.''

Google shows several promising TLA possibilities for HBD, but "Here Be Dragons" is quite far down on the list. Author has a history of vandalism, so this is potentially an attempt at sneak vandalism. Delete - UtherSRG 14:42, 3 Aug 2004 (UTC)
 * Delete: That's poo. "Here be dragons" is not something a literate Englishman would have written at any age.  So, who would?  Are cartographers educated?  Yes, so not them.  Are surveyors?  Yes, so not them.  The "here be dragons" meme (ugh!) is supposed to be something pirates wrote.  Which pirates?  Why fictional pirates, of course.  The fact claims are piffle. Geogre 14:46, 3 Aug 2004 (UTC)
 * Delete - sounds like nonsense - Tεx  τ  urε  17:22, 3 Aug 2004 (UTC)
 * Besides, everyone knows that the correct and traditional phrase is "Here there be Dragons." Delete.-FZ 17:59, 3 Aug 2004 (UTC)
 * Delete. http://www.maphist.nl/extra/herebedragons.html says that there are no known maps with the legend "here be dragons" (but one single known map that does say "Hic sunt dracones.")  But the acronym HBD is surely private, or personal, or particular to some small ingroup.   I don't think Geogre is right, though; I think "here be" is perfectly good archaic English. (I see we do have an article on Talk Like a Pirate Day). Cartographers did fill up the gaps with fanciful pictures, though; Swift wrote "So Geographers in Afric Maps/With savage pictures fill their gaps/And o'er uninhabitable downs/Place elephants for want of towns." Prior to widespread use of aerial photography for mapping circa the Second World War, maps really did have empty spaces on it. My wife went to school in a small town in the 1950s and the classroom maps were so old that the map of Africa really did have areas on them simply labelled "unexplored." Did I say delete? [[User:dpbsmith|dpbsmith (talk)]] 18:51, 3 Aug 2004 (UTC)
 * Of course they drew pictures. They also had "terra incognita," and they also had the habit, which Swift particularly found amusing, of locating mythical continents wherever no one had been.  "New High Brasil" and "Ultima Thule" and "Hyperborea" were at the margins, wherever the map covered.  Swift, in particular, thought this was a hoot, as he studied cartography (and laughed at it) for Gulliver.  "Here be" is not regular English at any archaic period that I'm aware of, however.  It's dialect, and hence the "pirate talk" of pseudo-Irish inflected English.  To find pirates muttering like that, you've really got to get up pretty nearly to 20th century fiction, though.  Contemporary accounts tended to either represent them as speaking gutter English or to rewrite them in high standard English. Geogre 20:58, 3 Aug 2004 (UTC)
 * An article on the phrase "here [there] be dragons" would be interesting. This ain't it. Delete. Sean Curtin

title: Wikipedia:Articles for deletion/HBD


text:
Great Plains Art Museum

The Great Plains Art Museum is a fine arts museum located in Lincoln, Nebraska that is dedicated to the arts of the Great Plains in the United States.

The museum, which opened in 1981 at the University of Nebraska-Lincoln, was founded with the Christlieb Collection (sculptures, paintings, drawings, photographs and library), donated by John and Elizabeth Christlieb of Bellevue, Nebraska.

The Christlieb Collection includes works by Albert Bierstadt, William de la Montagne Cary, Robert Fletcher Gilder,  William Henry Jackson, Frederic Remington, Charles M. Russell and Olaf Wieghorst.

Subsequent acquisitions and donations have expanded the museum's collections with works by Lyman Byxbe,  Ray Ellis, John Philip Falter, Michael Forsberg,  Veryl Goodnight,  Chuck Guildner,  Cliff Hollestelle,  Laurie Houseman-Whitehawk,  Keith Jacobshagen,  Ted Long,  Herb Mignery,  Andrew Peters,  Del Pettigrew,  Martha Pettigrew,  Jackson Pollock, Norman Rockwell, Grant Wood and others.

The Great Plains Art Museum is part of the Center for Great Plains Studies at the University of Nebraska-Lincoln. Exhibits are typically rotated several times per year and include artwork from the permanent collection, guest-curated exhibitions, and traveling exhibits.

The center and the museum are located at Hewit Place, 1155 Q Street, in Lincoln, Nebraska. The museum is free and open to the public.

title: Great Plains Art Museum


text:
User talk:Leg-man

Hello and welcome to Wikipedia! Hope you like it here, and stick around.

Here are some tips to help you get started:

 * To sign your posts (on talk pages, for example) use the '~' symbol. To insert just your name, type ~~~ (3 tildes), or, to insert your name and timestamp, use ~~~~ (4 tildes).
 * Try the Tutorial, and feel free to experiment in the test area.
 * If you need help, post a question at the Help Desk
 * Follow the Simplified Ruleset
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Remember Neutral point of view
 * Explore, be bold in editing pages, and, most importantly, have fun!

Good luck!

title: User talk:Leg-man


text:
Wikipedia:WikiProject Dance/General

"Dance" lists and related articles
One thing that is going to need to be handled is the various dance related articles that are all over the place- probably requiring merging, and reworking into the main dance article. I for one, would like to get all the "main" articles, especially Dance, ready for the featured articles listing. We'll have to figure out a proper way to merge all these pages, and i'll attempt to start a list here of all those that look to be random and needing merging. They also may not need merging with the main Dance page, but could use other merging, to condense the information into proper areas. Or, they may need massive expansion, and just proper mention in the main dance article.Lyellin 14:48, Aug 3, 2004 (UTC)

(note: have split Lyellin's list into groups Ohka- 19:39, 3 Aug 2004 (UTC))

 * Dance and Cinema - main article: (new)
 * Dance for camera - expand
 * Dance film - merge: Dance for camera: sub catergory.
 * Dance in film - expand
 * Musical film - expand

how about a new main article for Dance and Cinema that briefly covers all the subsets and leads onto them. it could also be an subsection of the main dance page.

 * History of dance - expand - main article
 * Dance in mythology and religion - expand - merge: History of dance: fit into timeline as  mythological and religious context''
 * Dance and health - expand - merge: History of dance: sub catergory
 * Dance and society - expand - merge: History of dance: fit into timeline as social context

History of dance needs a lot of work. these sections could be added to give social and religious context.

 * dance reference pages
 * List_of_dance_style_categories - add to as needed
 * List of dances - add to as needed
 * Glossary of partner dance terms  - expand
 * Glossary of ballet terms  - expand
 * Dance music  - expand
 * Dance personalia - add to as needed

these pages are simply references, i'm not sure that they need to be merged. there is some potential for list of dances and dance music to be added to History of dance. possible inclusion of highly annotated dance bibliograhy.

 * Dance notation - expand - main article

redlinks need to be turned blue. and needs some mention on main dance page. again ref Ohka-

Dance etiquette varies according to context, form and style. perhaps this should be a part of other articles rather than and article itself?
 * Dance etiquette - ?

 * Musical terminology - ?

not sure about this one...

 * Dance basic topics - ?

should this be merged with WikiProject Dance pages ?

title: Wikipedia:WikiProject Dance/General