id
stringlengths
19
24
title
stringlengths
1
110
content
stringlengths
1
1k
contents
stringlengths
7
1.11k
wiki_id
stringlengths
2
8
wiki20220301en020_105627
Steve Schirripa
Schirripa and Fleming also collaborated on two books about Nicky Deuce, a suburban teenager who is sent to visit his grandparents in Brooklyn. Nicky Deuce: Welcome to the Family was followed by Nicky Deuce: Home for the Holidays, which was the basis for the 2013 Nickelodeon film Nicky Deuce starring Noah Munck. Nicky Deuce also featured supporting roles filled by James Gandolfini, Michael Imperioli, Tony Sirico, and Vincent Curatola of The Sopranos fame. Theatre On April 3, 2014, Steve Schirripa gave a theatrical performance in a special production of Guys and Dolls alongside Nathan Lane, Patrick Wilson, and Megan Mullally at Carnegie Hall. Uncle Steve's Italian Specialties In 2014, Schirripa launched a line of organic vegan pasta sauces under the business name of Uncle Steve's Italian Specialties Group. Schirripa appeared on the Eric Andre Show to promote the sauce. Personal life Schirripa married Laura Lemos on April 22, 1989. They have two children, daughters Bria and Ciara.
Steve Schirripa. Schirripa and Fleming also collaborated on two books about Nicky Deuce, a suburban teenager who is sent to visit his grandparents in Brooklyn. Nicky Deuce: Welcome to the Family was followed by Nicky Deuce: Home for the Holidays, which was the basis for the 2013 Nickelodeon film Nicky Deuce starring Noah Munck. Nicky Deuce also featured supporting roles filled by James Gandolfini, Michael Imperioli, Tony Sirico, and Vincent Curatola of The Sopranos fame. Theatre On April 3, 2014, Steve Schirripa gave a theatrical performance in a special production of Guys and Dolls alongside Nathan Lane, Patrick Wilson, and Megan Mullally at Carnegie Hall. Uncle Steve's Italian Specialties In 2014, Schirripa launched a line of organic vegan pasta sauces under the business name of Uncle Steve's Italian Specialties Group. Schirripa appeared on the Eric Andre Show to promote the sauce. Personal life Schirripa married Laura Lemos on April 22, 1989. They have two children, daughters Bria and Ciara.
524751
wiki20220301en020_105628
Steve Schirripa
Personal life Schirripa married Laura Lemos on April 22, 1989. They have two children, daughters Bria and Ciara. When asked if he was bar mitzvahed, Schirripa answered no and stated that he was raised as a Catholic but that he ”very much identifies as being Jewish as well”. Filmography Film Television References External links
Steve Schirripa. Personal life Schirripa married Laura Lemos on April 22, 1989. They have two children, daughters Bria and Ciara. When asked if he was bar mitzvahed, Schirripa answered no and stated that he was raised as a Catholic but that he ”very much identifies as being Jewish as well”. Filmography Film Television References External links
524751
wiki20220301en020_105629
Steve Schirripa
Filmography Film Television References External links 1957 births Living people American Ashkenazi Jews Film producers from New York (state) Television producers from New York City American male singers American animators American male voice actors American people of Italian descent American male film actors American male television actors American people of Jewish descent People from the Las Vegas Valley Male actors from New York City 20th-century American male actors 21st-century American male actors Lafayette High School (New York City) alumni Musicians from Brooklyn People from Bensonhurst, Brooklyn Jewish American male actors American male writers American podcasters American men podcasters 21st-century American Jews
Steve Schirripa. Filmography Film Television References External links 1957 births Living people American Ashkenazi Jews Film producers from New York (state) Television producers from New York City American male singers American animators American male voice actors American people of Italian descent American male film actors American male television actors American people of Jewish descent People from the Las Vegas Valley Male actors from New York City 20th-century American male actors 21st-century American male actors Lafayette High School (New York City) alumni Musicians from Brooklyn People from Bensonhurst, Brooklyn Jewish American male actors American male writers American podcasters American men podcasters 21st-century American Jews
524751
wiki20220301en020_105630
Lancair
Lancair International, Inc. (pronounced "lance-air") is a U.S. manufacturer of general aviation aircraft kits. They are well known for their series of high-performance single-engine aircraft that offer cruise speeds that surpass many twin-engine turboprop designs. Along with the Glasair series, the early Lancair designs were among the first kitplanes to bring modern molded composites construction to light aircraft. In early 2017 the company, including all the older aircraft designs, was sold and moved from Redmond, Oregon to Uvalde, Texas under the name Lancair International, LLC. The newest model, the Lancair Evolution was retained by the existing company, Lancair International, Inc, which changed its name to the Evolution Aircraft Company. History
Lancair. Lancair International, Inc. (pronounced "lance-air") is a U.S. manufacturer of general aviation aircraft kits. They are well known for their series of high-performance single-engine aircraft that offer cruise speeds that surpass many twin-engine turboprop designs. Along with the Glasair series, the early Lancair designs were among the first kitplanes to bring modern molded composites construction to light aircraft. In early 2017 the company, including all the older aircraft designs, was sold and moved from Redmond, Oregon to Uvalde, Texas under the name Lancair International, LLC. The newest model, the Lancair Evolution was retained by the existing company, Lancair International, Inc, which changed its name to the Evolution Aircraft Company. History
524755
wiki20220301en020_105631
Lancair
History Introduction The company was founded by Lance Neibauer in 1981 as a producer of composite homebuilt aircraft kits. Neibauer had been introduced to aviation by his uncle Ray Betzoldt, who had collaborated with Al Meyers to build the Meyers 200. Whenever he visited his aunt and uncle, he always took a ride in the Meyers. Hooked, he went looking for an aircraft twenty years later and found nothing that he liked, and decided to join the Experimental Aircraft Association (EAA) and design his own.
Lancair. History Introduction The company was founded by Lance Neibauer in 1981 as a producer of composite homebuilt aircraft kits. Neibauer had been introduced to aviation by his uncle Ray Betzoldt, who had collaborated with Al Meyers to build the Meyers 200. Whenever he visited his aunt and uncle, he always took a ride in the Meyers. Hooked, he went looking for an aircraft twenty years later and found nothing that he liked, and decided to join the Experimental Aircraft Association (EAA) and design his own.
524755
wiki20220301en020_105632
Lancair
Neibauer began working on the new design after asking every builder he could find what features they were seeking in a homebuilt design. Looking to improve performance with the latest possible features, he selected the new NASA NLF 0215-F airfoil designed by Dan Somers at Langley. The NLF, short for "Natural Laminar Flow", is a series of designs that replaced the older GAW series with more forgiving laminar flow characteristics. By 1983 the aircraft's basic parameters were fixed, and Neibauer rented a shop in Santa Paula, California and started work on the design.
Lancair. Neibauer began working on the new design after asking every builder he could find what features they were seeking in a homebuilt design. Looking to improve performance with the latest possible features, he selected the new NASA NLF 0215-F airfoil designed by Dan Somers at Langley. The NLF, short for "Natural Laminar Flow", is a series of designs that replaced the older GAW series with more forgiving laminar flow characteristics. By 1983 the aircraft's basic parameters were fixed, and Neibauer rented a shop in Santa Paula, California and started work on the design.
524755
wiki20220301en020_105633
Lancair
Intending to introduce aircraft at Oshkosh in 1984, a minor fuel leak in the wing tanks forced them to miss the show so they could fix the problem. A modified version of the prototype, with re-shaped cowling and some changes to the wing profile, emerged as the Lancer 200 in December 1984. Equipped with a 100 hp Continental O-200 engine, the Lancer easily outflew anything powered by the same engine and generated intense interest at Oshkosh '85. However, a naming conflict forced the design to be re-christened, finally going on sale in 1985 as the Lancair 200. The 200 was quickly replaced by the Lancair 235, equipped with the slightly more powerful Lycoming O-235. Re-engined versions quickly followed; the Lancair 320 with the 150 hp Lycoming O-320, and the Lancair 360 with the 180 hp Lycoming O-360. A new tail was introduced for the later models in order to address stability problems at low speeds with the larger engines.
Lancair. Intending to introduce aircraft at Oshkosh in 1984, a minor fuel leak in the wing tanks forced them to miss the show so they could fix the problem. A modified version of the prototype, with re-shaped cowling and some changes to the wing profile, emerged as the Lancer 200 in December 1984. Equipped with a 100 hp Continental O-200 engine, the Lancer easily outflew anything powered by the same engine and generated intense interest at Oshkosh '85. However, a naming conflict forced the design to be re-christened, finally going on sale in 1985 as the Lancair 200. The 200 was quickly replaced by the Lancair 235, equipped with the slightly more powerful Lycoming O-235. Re-engined versions quickly followed; the Lancair 320 with the 150 hp Lycoming O-320, and the Lancair 360 with the 180 hp Lycoming O-360. A new tail was introduced for the later models in order to address stability problems at low speeds with the larger engines.
524755
wiki20220301en020_105634
Lancair
The Lancair designs provided the highest performance in the single-engine GA class, and as the kit-build market was dominated by pilots looking to outperform existing "off-the-shelf" designs, the Lancair's kits sold well. By the end of 1990 they had sold over 600 kits for the various two-seat models, giving them what Neibauer claimed was 30% of the kit-built market. A Lancair 320 appeared in a 1995 exhibit at the New York Museum of Modern Art. New models Starting in 1990, Neibauer turned his attention to a four-seat design that would retain the qualities of the earlier two-seaters. These efforts culminated in the Lancair IV, a four-seat optionally pressurized (IV-P) single-engine aircraft with a high cruise speed. The IV broke the speed record for planes in its class in February 1991 when it averaged 360.3 mph between San Francisco and Denver.
Lancair. The Lancair designs provided the highest performance in the single-engine GA class, and as the kit-build market was dominated by pilots looking to outperform existing "off-the-shelf" designs, the Lancair's kits sold well. By the end of 1990 they had sold over 600 kits for the various two-seat models, giving them what Neibauer claimed was 30% of the kit-built market. A Lancair 320 appeared in a 1995 exhibit at the New York Museum of Modern Art. New models Starting in 1990, Neibauer turned his attention to a four-seat design that would retain the qualities of the earlier two-seaters. These efforts culminated in the Lancair IV, a four-seat optionally pressurized (IV-P) single-engine aircraft with a high cruise speed. The IV broke the speed record for planes in its class in February 1991 when it averaged 360.3 mph between San Francisco and Denver.
524755
wiki20220301en020_105635
Lancair
Already stretching the limits of their existing facilities, the company started looking for a new factory and after examining 200 potential sites they moved to Roberts Field in Redmond, Oregon in 1992. The company became Lancair International with the move. As of August 1998, according to Flight International, Lancair had sold 1,400 kits, 300 of them the Lancair IV model. Soon after the IV was introduced, Neibauer started work on a simpler fixed-gear version that emerged as the Lancair ES. Columbia Aircraft
Lancair. Already stretching the limits of their existing facilities, the company started looking for a new factory and after examining 200 potential sites they moved to Roberts Field in Redmond, Oregon in 1992. The company became Lancair International with the move. As of August 1998, according to Flight International, Lancair had sold 1,400 kits, 300 of them the Lancair IV model. Soon after the IV was introduced, Neibauer started work on a simpler fixed-gear version that emerged as the Lancair ES. Columbia Aircraft
524755
wiki20220301en020_105636
Lancair
Columbia Aircraft Lancair's designs were prominent in the homebuilt market, and in 1994 NASA and others encouraged Neibauer to develop a type certified aircraft. On 3 April 1993 he spun off a new company, Pacific Aviation Composites USA, in nearby Bend, Oregon. The new Lancair LC-40 was based on the fixed-gear Lancair ES. The first prototype flew in July 1996, followed by the certification prototype in early 1997. After a lengthy certification process, the design emerged as the Columbia 300 in 1998, followed by the turbocharged Columbia 400 in 2000. The Lancair Company was formed as a separate entity on 7 April 2000, and Pacific Aviation Composites was merged into The Lancair Company on 4 May 2000.
Lancair. Columbia Aircraft Lancair's designs were prominent in the homebuilt market, and in 1994 NASA and others encouraged Neibauer to develop a type certified aircraft. On 3 April 1993 he spun off a new company, Pacific Aviation Composites USA, in nearby Bend, Oregon. The new Lancair LC-40 was based on the fixed-gear Lancair ES. The first prototype flew in July 1996, followed by the certification prototype in early 1997. After a lengthy certification process, the design emerged as the Columbia 300 in 1998, followed by the turbocharged Columbia 400 in 2000. The Lancair Company was formed as a separate entity on 7 April 2000, and Pacific Aviation Composites was merged into The Lancair Company on 4 May 2000.
524755
wiki20220301en020_105637
Lancair
Deciding to focus on the Columbia models, in March 2003 Neibauer sold the kit side of the company to Joseph Bartels, a Louisiana attorney and Lancair IV-P builder and owner. Bartels had already formed Aero Cool to sell air conditioners for the various Lancair models. On 15 July 2005 Neibauer's portion of the company became Columbia Aircraft. The Columbias competed relatively unsuccessfully with the new and first-to-market Cirrus SR22. In 2010, major stockholders, the Wolstenholme family of Colmar, Pennsylvania, purchased the company and appointed Bob Wolstenholme as CEO. Following its entry into bankruptcy in 2007, Columbia Aircraft was sold to Cessna in November 2007. Cessna introduced their models as the Cessna 350 and Cessna 400.
Lancair. Deciding to focus on the Columbia models, in March 2003 Neibauer sold the kit side of the company to Joseph Bartels, a Louisiana attorney and Lancair IV-P builder and owner. Bartels had already formed Aero Cool to sell air conditioners for the various Lancair models. On 15 July 2005 Neibauer's portion of the company became Columbia Aircraft. The Columbias competed relatively unsuccessfully with the new and first-to-market Cirrus SR22. In 2010, major stockholders, the Wolstenholme family of Colmar, Pennsylvania, purchased the company and appointed Bob Wolstenholme as CEO. Following its entry into bankruptcy in 2007, Columbia Aircraft was sold to Cessna in November 2007. Cessna introduced their models as the Cessna 350 and Cessna 400.
524755
wiki20220301en020_105638
Lancair
Selling off older designs In July 2016 Lancair announced it would be selling the older Lancair lines of aircraft to concentrate on the Lancair Evolution instead. In February 2017 the 200-360, IV, IVP, IVPT, ES, ESP, and Legacy designs were sold to Mark and Conrad Huffstutler, who now operate the company as Lancair International, LLC, in Uvalde, Texas. They purchased all the assets, intellectual property and will provide parts and other support for all the older Lancair models. They plan to resume production of some of the older models and will develop new models as well. With the sale announced Lancair changed its name to Evolution Aircraft.
Lancair. Selling off older designs In July 2016 Lancair announced it would be selling the older Lancair lines of aircraft to concentrate on the Lancair Evolution instead. In February 2017 the 200-360, IV, IVP, IVPT, ES, ESP, and Legacy designs were sold to Mark and Conrad Huffstutler, who now operate the company as Lancair International, LLC, in Uvalde, Texas. They purchased all the assets, intellectual property and will provide parts and other support for all the older Lancair models. They plan to resume production of some of the older models and will develop new models as well. With the sale announced Lancair changed its name to Evolution Aircraft.
524755
wiki20220301en020_105639
Lancair
Aircraft Summary of aircraft built by Lancair: Lancair 200 (originally "Lancer 200") 2-seat kit powered by a Continental O-200 engine, flown in 1984 and released in 1985 Lancair 235 2-seat kit powered by a Lycoming O-235 engine, released in 1986 Lancair 320 2-seat kit powered by a Lycoming O-320 engine, released in 1988 Lancair 360 2-seat kit powered by a Lycoming O-360 engine, released in 1988 Lancair ES 4-seat kit powered by a Continental IO-550 Lancair IV Lancair IV-P Lancair Legacy Lancair Tigress Lancair Propjet Lancair Sentry Lancair Evolution Lancair Mako first flown on 18 July 2017 Lancair Barracuda first flown 2018 References External links Aircraft manufacturers of the United States Manufacturing companies based in Texas Uvalde County, Texas Manufacturing companies established in 1981 1981 establishments in Oregon Privately held companies based in Texas
Lancair. Aircraft Summary of aircraft built by Lancair: Lancair 200 (originally "Lancer 200") 2-seat kit powered by a Continental O-200 engine, flown in 1984 and released in 1985 Lancair 235 2-seat kit powered by a Lycoming O-235 engine, released in 1986 Lancair 320 2-seat kit powered by a Lycoming O-320 engine, released in 1988 Lancair 360 2-seat kit powered by a Lycoming O-360 engine, released in 1988 Lancair ES 4-seat kit powered by a Continental IO-550 Lancair IV Lancair IV-P Lancair Legacy Lancair Tigress Lancair Propjet Lancair Sentry Lancair Evolution Lancair Mako first flown on 18 July 2017 Lancair Barracuda first flown 2018 References External links Aircraft manufacturers of the United States Manufacturing companies based in Texas Uvalde County, Texas Manufacturing companies established in 1981 1981 establishments in Oregon Privately held companies based in Texas
524755
wiki20220301en020_105640
Voiceless uvular plosive
The voiceless uvular plosive or stop is a type of consonantal sound, used in some spoken languages. It is pronounced like a voiceless velar plosive , except that the tongue makes contact not on the soft palate but on the uvula. The symbol in the International Phonetic Alphabet that represents this sound is , and the equivalent X-SAMPA symbol is q. There is also the voiceless pre-uvular plosive in some languages, which is articulated slightly more front compared with the place of articulation of the prototypical uvular consonant, though not as front as the prototypical velar consonant. The International Phonetic Alphabet does not have a separate symbol for that sound, though it can be transcribed as or (both symbols denote an advanced ) or (retracted ). The equivalent X-SAMPA symbols are q_+ and k_-, respectively. Features Features of the voiceless uvular stop: Occurrence See also Guttural Index of phonetics articles Qoph Voiced uvular stop Notes References
Voiceless uvular plosive. The voiceless uvular plosive or stop is a type of consonantal sound, used in some spoken languages. It is pronounced like a voiceless velar plosive , except that the tongue makes contact not on the soft palate but on the uvula. The symbol in the International Phonetic Alphabet that represents this sound is , and the equivalent X-SAMPA symbol is q. There is also the voiceless pre-uvular plosive in some languages, which is articulated slightly more front compared with the place of articulation of the prototypical uvular consonant, though not as front as the prototypical velar consonant. The International Phonetic Alphabet does not have a separate symbol for that sound, though it can be transcribed as or (both symbols denote an advanced ) or (retracted ). The equivalent X-SAMPA symbols are q_+ and k_-, respectively. Features Features of the voiceless uvular stop: Occurrence See also Guttural Index of phonetics articles Qoph Voiced uvular stop Notes References
524759
wiki20220301en020_105641
Voiceless uvular plosive
Features Features of the voiceless uvular stop: Occurrence See also Guttural Index of phonetics articles Qoph Voiced uvular stop Notes References External links Uvular consonants Pulmonic consonants Voiceless oral consonants Central consonants
Voiceless uvular plosive. Features Features of the voiceless uvular stop: Occurrence See also Guttural Index of phonetics articles Qoph Voiced uvular stop Notes References External links Uvular consonants Pulmonic consonants Voiceless oral consonants Central consonants
524759
wiki20220301en020_105642
European cuisine
European cuisine comprises the cuisines of Europe including the cuisines brought to other countries by European settlers and colonists. Sometimes the term "European", or more specifically "continental" cuisine, is used to refer more strictly to the cuisine of the western parts of mainland Europe.
European cuisine. European cuisine comprises the cuisines of Europe including the cuisines brought to other countries by European settlers and colonists. Sometimes the term "European", or more specifically "continental" cuisine, is used to refer more strictly to the cuisine of the western parts of mainland Europe.
524762
wiki20220301en020_105643
European cuisine
The cuisines of Western countries are diverse, although there are common characteristics that distinguish them from those of other regions. Compared with traditional cooking of East Asia, meat is more prominent and substantial in serving size. Steak and cutlets in particular are common dishes across the West. Western cuisines also emphasize grape wine and sauces as condiments, seasonings, or accompaniments (in part due to the difficulty of seasonings penetrating the often larger pieces of meat used in Western cooking). Many dairy products are utilised in cooking. There are hundreds of varieties of cheese and other fermented milk products. White wheat-flour bread has long been the prestige starch, but historically, most people ate bread, flatcakes, or porridge made from rye, spelt, barley, and oats. The better-off also made pasta, dumplings and pastries. The potato has become a major starch plant in the diet of Europeans and their diaspora since the European colonisation of the
European cuisine. The cuisines of Western countries are diverse, although there are common characteristics that distinguish them from those of other regions. Compared with traditional cooking of East Asia, meat is more prominent and substantial in serving size. Steak and cutlets in particular are common dishes across the West. Western cuisines also emphasize grape wine and sauces as condiments, seasonings, or accompaniments (in part due to the difficulty of seasonings penetrating the often larger pieces of meat used in Western cooking). Many dairy products are utilised in cooking. There are hundreds of varieties of cheese and other fermented milk products. White wheat-flour bread has long been the prestige starch, but historically, most people ate bread, flatcakes, or porridge made from rye, spelt, barley, and oats. The better-off also made pasta, dumplings and pastries. The potato has become a major starch plant in the diet of Europeans and their diaspora since the European colonisation of the
524762
wiki20220301en020_105644
European cuisine
barley, and oats. The better-off also made pasta, dumplings and pastries. The potato has become a major starch plant in the diet of Europeans and their diaspora since the European colonisation of the Americas. Maize is much less common in most European diets than it is in the Americas; however, corn meal (polenta or mămăligă) is a major part of the cuisine of Italy and the Balkans. Although flatbreads (especially with toppings such as pizza or tarte flambée) and rice are eaten in Europe, they are only staple foods in limited areas, particularly in Southern Europe. Salads (cold dishes with uncooked or cooked vegetables, sometimes with a dressing) are an integral part of European cuisine.
European cuisine. barley, and oats. The better-off also made pasta, dumplings and pastries. The potato has become a major starch plant in the diet of Europeans and their diaspora since the European colonisation of the Americas. Maize is much less common in most European diets than it is in the Americas; however, corn meal (polenta or mămăligă) is a major part of the cuisine of Italy and the Balkans. Although flatbreads (especially with toppings such as pizza or tarte flambée) and rice are eaten in Europe, they are only staple foods in limited areas, particularly in Southern Europe. Salads (cold dishes with uncooked or cooked vegetables, sometimes with a dressing) are an integral part of European cuisine.
524762
wiki20220301en020_105645
European cuisine
Formal European dinners are served in distinct courses. European presentation evolved from service à la française, or bringing multiple dishes to the table at once, into service à la russe, where dishes are presented sequentially. Usually, cold, hot and savoury, and sweet dishes are served strictly separately in this order, as hors d'oeuvre (appetizer) or soup, as entrée and main course, and as dessert. Dishes that are both sweet and savoury were common earlier in Ancient Roman cuisine, but are today uncommon, with sweet dishes being served only as dessert. A service where the guests are free to take food by themselves is termed a buffet, and is usually restricted to parties or holidays. Nevertheless, guests are expected to follow the same pattern.
European cuisine. Formal European dinners are served in distinct courses. European presentation evolved from service à la française, or bringing multiple dishes to the table at once, into service à la russe, where dishes are presented sequentially. Usually, cold, hot and savoury, and sweet dishes are served strictly separately in this order, as hors d'oeuvre (appetizer) or soup, as entrée and main course, and as dessert. Dishes that are both sweet and savoury were common earlier in Ancient Roman cuisine, but are today uncommon, with sweet dishes being served only as dessert. A service where the guests are free to take food by themselves is termed a buffet, and is usually restricted to parties or holidays. Nevertheless, guests are expected to follow the same pattern.
524762
wiki20220301en020_105646
European cuisine
Historically, European cuisine has been developed in the European royal and noble courts. European nobility was usually arms-bearing and lived in separate manors in the countryside. The knife was the primary eating implement (cutlery), and eating steaks and other foods that require cutting followed. This contrasted with the Sinosphere, where the ruling class were the court officials, who had their food prepared ready to eat in the kitchen, to be eaten with chopsticks. The knife was supplanted by the spoon for soups, while the fork was introduced later in the early modern period, ca. 16th century. Today, most dishes are intended to be eaten with cutlery and only a few finger foods can be eaten with the hands in polite company. History
European cuisine. Historically, European cuisine has been developed in the European royal and noble courts. European nobility was usually arms-bearing and lived in separate manors in the countryside. The knife was the primary eating implement (cutlery), and eating steaks and other foods that require cutting followed. This contrasted with the Sinosphere, where the ruling class were the court officials, who had their food prepared ready to eat in the kitchen, to be eaten with chopsticks. The knife was supplanted by the spoon for soups, while the fork was introduced later in the early modern period, ca. 16th century. Today, most dishes are intended to be eaten with cutlery and only a few finger foods can be eaten with the hands in polite company. History
524762
wiki20220301en020_105647
European cuisine
Medieval
European cuisine. Medieval
524762
wiki20220301en020_105648
European cuisine
In medieval times, a person's diet varied depending on their social class. Cereal grains made up a lot of a medieval person's diet, regardless of social class. Bread was common to both classes- it was taken as a lunch for the working man, and thick slices of it were used as plates called trenchers. People of the noble class had access to finely ground flours for their breads and other baked goods. Noblemen were allowed to hunt for deer, boar, rabbits, birds, and other animals, giving them access to fresh meat and fish for their meals. Dishes for people of these classes were often heavily spiced. Spices at that time were very expensive, and the more spices used in dishes, the more wealth the person had to be able to purchase such ingredients. Common spices used were cinnamon, ginger, nutmeg, pepper, cumin, cloves, turmeric, anise, and saffron. Other ingredients used in dishes for the nobility and clergy included sugar, almonds and dried fruits like raisins. These imported ingredients
European cuisine. In medieval times, a person's diet varied depending on their social class. Cereal grains made up a lot of a medieval person's diet, regardless of social class. Bread was common to both classes- it was taken as a lunch for the working man, and thick slices of it were used as plates called trenchers. People of the noble class had access to finely ground flours for their breads and other baked goods. Noblemen were allowed to hunt for deer, boar, rabbits, birds, and other animals, giving them access to fresh meat and fish for their meals. Dishes for people of these classes were often heavily spiced. Spices at that time were very expensive, and the more spices used in dishes, the more wealth the person had to be able to purchase such ingredients. Common spices used were cinnamon, ginger, nutmeg, pepper, cumin, cloves, turmeric, anise, and saffron. Other ingredients used in dishes for the nobility and clergy included sugar, almonds and dried fruits like raisins. These imported ingredients
524762
wiki20220301en020_105649
European cuisine
pepper, cumin, cloves, turmeric, anise, and saffron. Other ingredients used in dishes for the nobility and clergy included sugar, almonds and dried fruits like raisins. These imported ingredients would have been very expensive and nearly impossible for commoners to obtain. When banquets were held, the dishes served would be very spectacular- another way for the noblemen to show how rich they were. Sugar sculptures would be placed on the tables as decoration and to eat, and foods would be dyed vibrant colors with imported spices.
European cuisine. pepper, cumin, cloves, turmeric, anise, and saffron. Other ingredients used in dishes for the nobility and clergy included sugar, almonds and dried fruits like raisins. These imported ingredients would have been very expensive and nearly impossible for commoners to obtain. When banquets were held, the dishes served would be very spectacular- another way for the noblemen to show how rich they were. Sugar sculptures would be placed on the tables as decoration and to eat, and foods would be dyed vibrant colors with imported spices.
524762
wiki20220301en020_105650
European cuisine
The diet of a commoner would have been much more simple. Strict poaching laws prevented them from hunting, and if they did hunt and were caught, they could have parts of their limbs cut off or they could be killed. Much of the commoners food would have been preserved in some way, such as through pickling or by being salted. Breads would have been made using rye or barley, and any vegetables would likely have been grown by the commoners themselves. Peasants would have likely been able to keep cows, and so would have access to milk, which then allowed them to make butter or cheese. When meat was eaten, it would have been beef, pork, or lamb. Commoners also ate a dish called pottage, a thick stew of vegetables, grains, and meat. Early modern era
European cuisine. The diet of a commoner would have been much more simple. Strict poaching laws prevented them from hunting, and if they did hunt and were caught, they could have parts of their limbs cut off or they could be killed. Much of the commoners food would have been preserved in some way, such as through pickling or by being salted. Breads would have been made using rye or barley, and any vegetables would likely have been grown by the commoners themselves. Peasants would have likely been able to keep cows, and so would have access to milk, which then allowed them to make butter or cheese. When meat was eaten, it would have been beef, pork, or lamb. Commoners also ate a dish called pottage, a thick stew of vegetables, grains, and meat. Early modern era
524762
wiki20220301en020_105651
European cuisine
Early modern era In the early modern era, European cuisine saw an influx of new ingredients due to the Columbian Exchange, such as the potato, tomato, eggplant, chocolate, bell pepper, pumpkins, and other squash. Distilled spirits, along with tea, coffee, and chocolate were all popularized during this time. In the 1780s, the idea of the modern restaurant was introduced in Paris; the French Revolution accelerated its development, quickly spreading around Europe. Central European cuisines
European cuisine. Early modern era In the early modern era, European cuisine saw an influx of new ingredients due to the Columbian Exchange, such as the potato, tomato, eggplant, chocolate, bell pepper, pumpkins, and other squash. Distilled spirits, along with tea, coffee, and chocolate were all popularized during this time. In the 1780s, the idea of the modern restaurant was introduced in Paris; the French Revolution accelerated its development, quickly spreading around Europe. Central European cuisines
524762
wiki20220301en020_105652
European cuisine
Central European cuisines All of these countries have their specialities. Austria is famous for Wiener Schnitzel - a breaded veal cutlet served with a slice of lemon, the Czech Republic for world renowned beers. Germany for world-famous wursts, Hungary for goulash. Slovakia is famous for gnocchi-like Halusky pasta. Slovenia is known for German and Italian influenced cuisine, Poland for world-famous Pierogis which are a cross between a ravioli and an empanada. Liechtenstein and German speaking Switzerland are famous for Rösti and French speaking Switzerland for fondue and Raclettes.
European cuisine. Central European cuisines All of these countries have their specialities. Austria is famous for Wiener Schnitzel - a breaded veal cutlet served with a slice of lemon, the Czech Republic for world renowned beers. Germany for world-famous wursts, Hungary for goulash. Slovakia is famous for gnocchi-like Halusky pasta. Slovenia is known for German and Italian influenced cuisine, Poland for world-famous Pierogis which are a cross between a ravioli and an empanada. Liechtenstein and German speaking Switzerland are famous for Rösti and French speaking Switzerland for fondue and Raclettes.
524762
wiki20220301en020_105653
European cuisine
Ashkenazi Jewish cuisine Austrian cuisine Viennese cuisine Czech cuisine Moravian cuisine German cuisine Baden cuisine Bavarian cuisine Brandenburg cuisine Franconian cuisine Hamburg cuisine Hessian cuisine Lower Saxon cuisine Mecklenburg cuisine Palatine cuisine Pomeranian cuisine Saxon cuisine Ore Mountain cuisine Schleswig-Holstein cuisine Swabian cuisine Hungarian cuisine Polish cuisine Lublin cuisine Podlaskie cuisine Świętokrzyskie cuisine Liechtensteiner cuisine Silesian cuisine Slovak cuisine Slovenian cuisine Swiss cuisine Eastern European/Caucasian cuisines
European cuisine. Ashkenazi Jewish cuisine Austrian cuisine Viennese cuisine Czech cuisine Moravian cuisine German cuisine Baden cuisine Bavarian cuisine Brandenburg cuisine Franconian cuisine Hamburg cuisine Hessian cuisine Lower Saxon cuisine Mecklenburg cuisine Palatine cuisine Pomeranian cuisine Saxon cuisine Ore Mountain cuisine Schleswig-Holstein cuisine Swabian cuisine Hungarian cuisine Polish cuisine Lublin cuisine Podlaskie cuisine Świętokrzyskie cuisine Liechtensteiner cuisine Silesian cuisine Slovak cuisine Slovenian cuisine Swiss cuisine Eastern European/Caucasian cuisines
524762
wiki20220301en020_105654
European cuisine
Eastern European/Caucasian cuisines Armenian cuisine Azerbaijani cuisine Belarusian cuisine Bulgarian cuisine Georgian cuisine Kazakh cuisine Moldovan cuisine Gagauz cuisine Romanian cuisine Russian cuisine Bashkir cuisine Komi cuisine Mordovian cuisine North Caucasian cuisine Chechen cuisine Circassian cuisine Tatar cuisine Udmurt cuisine Yamal cuisine Ukrainian cuisine Crimean Tatar cuisine Odessite cuisine
European cuisine. Eastern European/Caucasian cuisines Armenian cuisine Azerbaijani cuisine Belarusian cuisine Bulgarian cuisine Georgian cuisine Kazakh cuisine Moldovan cuisine Gagauz cuisine Romanian cuisine Russian cuisine Bashkir cuisine Komi cuisine Mordovian cuisine North Caucasian cuisine Chechen cuisine Circassian cuisine Tatar cuisine Udmurt cuisine Yamal cuisine Ukrainian cuisine Crimean Tatar cuisine Odessite cuisine
524762
wiki20220301en020_105655
European cuisine
Northern European cuisines British cuisine Channel Islands cuisine English cuisine Cornish cuisine Devonian cuisine Dorset cuisine Victorian cuisine Northern Irish cuisine Scottish cuisine Welsh cuisine Cuisine of Carmarthenshire Cuisine of Ceredigion Cuisine of Gower Cuisine of Monmouthshire Cuisine of Pembrokeshire Danish cuisine Faroese cuisine New Nordic Cuisine Estonian cuisine Finnish cuisine Icelandic cuisine Irish cuisine Latvian cuisine Lithuanian cuisine Livonian cuisine Norwegian cuisine Sami cuisine Swedish cuisine Southern European cuisines
European cuisine. Northern European cuisines British cuisine Channel Islands cuisine English cuisine Cornish cuisine Devonian cuisine Dorset cuisine Victorian cuisine Northern Irish cuisine Scottish cuisine Welsh cuisine Cuisine of Carmarthenshire Cuisine of Ceredigion Cuisine of Gower Cuisine of Monmouthshire Cuisine of Pembrokeshire Danish cuisine Faroese cuisine New Nordic Cuisine Estonian cuisine Finnish cuisine Icelandic cuisine Irish cuisine Latvian cuisine Lithuanian cuisine Livonian cuisine Norwegian cuisine Sami cuisine Swedish cuisine Southern European cuisines
524762
wiki20220301en020_105656
European cuisine
Albanian cuisine Arbëreshë cuisine Aromanian cuisine Bosnian cuisine Corsican cuisine Croatian cuisine Cypriot cuisine Gibraltarian cuisine Greek cuisine Ancient Greek cuisine Byzantine cuisine Cretan cuisine Epirotic cuisine Greek Macedonian cuisine Ionian cuisine Italian cuisine Abruzzian cuisine Ancient Roman cuisine Apulian cuisine Arbëreshë cuisine Basilicatan or Lucanian cuisine Ligurian cuisine Lombard cuisine Mantuan cuisine Neapolitan cuisine Roman cuisine Sardinian cuisine Sicilian cuisine Tuscan cuisine Venetian cuisine Macedonian cuisine Maltese cuisine Monégasque cuisine Montenegrin cuisine Occitan cuisine Ottoman cuisine Portuguese cuisine Sammarinese cuisine Sephardic Jewish cuisine Serbian cuisine Kosovan cuisine Spanish cuisine Andalusian cuisine Aragonese cuisine Asturian cuisine Balearic cuisine Menorcan cuisine Basque cuisine Canarian cuisine Cantabrian cuisine
European cuisine. Albanian cuisine Arbëreshë cuisine Aromanian cuisine Bosnian cuisine Corsican cuisine Croatian cuisine Cypriot cuisine Gibraltarian cuisine Greek cuisine Ancient Greek cuisine Byzantine cuisine Cretan cuisine Epirotic cuisine Greek Macedonian cuisine Ionian cuisine Italian cuisine Abruzzian cuisine Ancient Roman cuisine Apulian cuisine Arbëreshë cuisine Basilicatan or Lucanian cuisine Ligurian cuisine Lombard cuisine Mantuan cuisine Neapolitan cuisine Roman cuisine Sardinian cuisine Sicilian cuisine Tuscan cuisine Venetian cuisine Macedonian cuisine Maltese cuisine Monégasque cuisine Montenegrin cuisine Occitan cuisine Ottoman cuisine Portuguese cuisine Sammarinese cuisine Sephardic Jewish cuisine Serbian cuisine Kosovan cuisine Spanish cuisine Andalusian cuisine Aragonese cuisine Asturian cuisine Balearic cuisine Menorcan cuisine Basque cuisine Canarian cuisine Cantabrian cuisine
524762
wiki20220301en020_105657
European cuisine
Kosovan cuisine Spanish cuisine Andalusian cuisine Aragonese cuisine Asturian cuisine Balearic cuisine Menorcan cuisine Basque cuisine Canarian cuisine Cantabrian cuisine Castilian-Leonese cuisine Vallisoletano cuisine Catalan cuisine Castilian-Manchego cuisine Extremaduran cuisine Galician cuisine Madrilenian cuisine Valencian cuisine Turkish cuisine
European cuisine. Kosovan cuisine Spanish cuisine Andalusian cuisine Aragonese cuisine Asturian cuisine Balearic cuisine Menorcan cuisine Basque cuisine Canarian cuisine Cantabrian cuisine Castilian-Leonese cuisine Vallisoletano cuisine Catalan cuisine Castilian-Manchego cuisine Extremaduran cuisine Galician cuisine Madrilenian cuisine Valencian cuisine Turkish cuisine
524762
wiki20220301en020_105658
European cuisine
Western European cuisines Belgian cuisine Dutch cuisine French cuisine Corsican cuisine Haute cuisine Cuisine classique Nouvelle cuisine Lyonnaise cuisine Luxembourgian cuisine Mennonite cuisine Monégasque cuisine Occitan cuisine See also Early modern European cuisine Medieval cuisine Jewish cuisine Romani cuisine Soviet cuisine References Further reading Food- and drink-related lists Cuisine by continent
European cuisine. Western European cuisines Belgian cuisine Dutch cuisine French cuisine Corsican cuisine Haute cuisine Cuisine classique Nouvelle cuisine Lyonnaise cuisine Luxembourgian cuisine Mennonite cuisine Monégasque cuisine Occitan cuisine See also Early modern European cuisine Medieval cuisine Jewish cuisine Romani cuisine Soviet cuisine References Further reading Food- and drink-related lists Cuisine by continent
524762
wiki20220301en020_105659
Curtiss SB2C Helldiver
The Curtiss SB2C Helldiver, also known as the A-25 Shrike, is a dive bomber developed by Curtiss-Wright during World War II. As a carrier-based bomber with the United States Navy (USN), in Pacific theaters, it supplemented and replaced the Douglas SBD Dauntless. A few survivors are extant. Initially poor handling characteristics and late modifications caused lengthy delays to production and deployment, to the extent that it was investigated by the Truman Committee, which turned in a scathing report. This contributed to the decline of Curtiss as a company. Neither pilots nor aircraft carrier skippers seemed to like it. Nevertheless, the type was faster than the Dauntless, and by the end of the Pacific War, the Helldiver had become the main dive bomber and attack aircraft on USN carriers.
Curtiss SB2C Helldiver. The Curtiss SB2C Helldiver, also known as the A-25 Shrike, is a dive bomber developed by Curtiss-Wright during World War II. As a carrier-based bomber with the United States Navy (USN), in Pacific theaters, it supplemented and replaced the Douglas SBD Dauntless. A few survivors are extant. Initially poor handling characteristics and late modifications caused lengthy delays to production and deployment, to the extent that it was investigated by the Truman Committee, which turned in a scathing report. This contributed to the decline of Curtiss as a company. Neither pilots nor aircraft carrier skippers seemed to like it. Nevertheless, the type was faster than the Dauntless, and by the end of the Pacific War, the Helldiver had become the main dive bomber and attack aircraft on USN carriers.
524763
wiki20220301en020_105660
Curtiss SB2C Helldiver
By the time a land-based variant, known as the A-25 Shrike became available, in late 1943, the Western Allied air forces had abandoned dedicated dive-bombers. A majority of A-25s delivered to the US Army Air Forces were transferred to the US Marine Corps, which used the type only in one side campaign and non-combat roles. The British Royal Navy and the Royal Australian Air Force also cancelled substantial orders, retaining only a few aircraft for research purposes. Nicknames for the aircraft included "Big-Tailed Beast" or just "Beast", "Two-Cee", and "Son-of-a-Bitch 2nd Class"; the latter nickname was derived from the name SB2C and the Shrike's reputation for having difficult handling characteristics. Design and development
Curtiss SB2C Helldiver. By the time a land-based variant, known as the A-25 Shrike became available, in late 1943, the Western Allied air forces had abandoned dedicated dive-bombers. A majority of A-25s delivered to the US Army Air Forces were transferred to the US Marine Corps, which used the type only in one side campaign and non-combat roles. The British Royal Navy and the Royal Australian Air Force also cancelled substantial orders, retaining only a few aircraft for research purposes. Nicknames for the aircraft included "Big-Tailed Beast" or just "Beast", "Two-Cee", and "Son-of-a-Bitch 2nd Class"; the latter nickname was derived from the name SB2C and the Shrike's reputation for having difficult handling characteristics. Design and development
524763
wiki20220301en020_105661
Curtiss SB2C Helldiver
Design and development The Helldiver was developed to replace the Douglas SBD Dauntless. It was a much larger aircraft, able to operate from the latest aircraft carriers and carry a considerable array of armament. It featured an internal bomb bay that reduced drag when carrying heavy ordnance. Saddled with demanding requirements set forth by both the U.S. Marines and United States Army Air Forces, the manufacturer incorporated features of a "multi-role" aircraft into the design.
Curtiss SB2C Helldiver. Design and development The Helldiver was developed to replace the Douglas SBD Dauntless. It was a much larger aircraft, able to operate from the latest aircraft carriers and carry a considerable array of armament. It featured an internal bomb bay that reduced drag when carrying heavy ordnance. Saddled with demanding requirements set forth by both the U.S. Marines and United States Army Air Forces, the manufacturer incorporated features of a "multi-role" aircraft into the design.
524763
wiki20220301en020_105662
Curtiss SB2C Helldiver
The Model XSB2C-1 prototype initially suffered teething problems connected to its Wright R-2600 Twin Cyclone engine and three-bladed propeller; further concerns included structural weaknesses, poor handling, directional instability, and bad stall characteristics. In 1939, a student took a model of the new Curtiss XSB2C-1 to the MIT wind tunnel. Professor of Aeronautical Engineering Otto C. Koppen was quoted as saying, "if they build more than one of these, they are crazy". He was referring to controllability issues with the small vertical tail. The first prototype made its maiden flight on 18 December 1940. It crashed on 8 February 1941 when its engine failed on approach, but Curtiss was asked to rebuild it. The fuselage was lengthened and a larger tail was fitted, while an autopilot was fitted to help the poor stability. The revised prototype flew again on 20 October 1941, but was destroyed when its wing failed during diving tests on 21 December 1941.
Curtiss SB2C Helldiver. The Model XSB2C-1 prototype initially suffered teething problems connected to its Wright R-2600 Twin Cyclone engine and three-bladed propeller; further concerns included structural weaknesses, poor handling, directional instability, and bad stall characteristics. In 1939, a student took a model of the new Curtiss XSB2C-1 to the MIT wind tunnel. Professor of Aeronautical Engineering Otto C. Koppen was quoted as saying, "if they build more than one of these, they are crazy". He was referring to controllability issues with the small vertical tail. The first prototype made its maiden flight on 18 December 1940. It crashed on 8 February 1941 when its engine failed on approach, but Curtiss was asked to rebuild it. The fuselage was lengthened and a larger tail was fitted, while an autopilot was fitted to help the poor stability. The revised prototype flew again on 20 October 1941, but was destroyed when its wing failed during diving tests on 21 December 1941.
524763
wiki20220301en020_105663
Curtiss SB2C Helldiver
Large-scale production had already been ordered on 29 November 1940, but a large number of modifications were specified for the production model. Fin and rudder area were increased, fuel capacity was increased, self-sealing fuel tanks were added, and the fixed armament was doubled to four 0.50 in (12.7 mm) machine guns in the wings, compared with the prototype's two cowling guns. The SB2C-1 was built with larger fuel tanks, improving its range considerably.
Curtiss SB2C Helldiver. Large-scale production had already been ordered on 29 November 1940, but a large number of modifications were specified for the production model. Fin and rudder area were increased, fuel capacity was increased, self-sealing fuel tanks were added, and the fixed armament was doubled to four 0.50 in (12.7 mm) machine guns in the wings, compared with the prototype's two cowling guns. The SB2C-1 was built with larger fuel tanks, improving its range considerably.
524763
wiki20220301en020_105664
Curtiss SB2C Helldiver
The program suffered so many delays that the Grumman TBF Avenger entered service before the Helldiver, even though the Avenger had begun its development two years later. Nevertheless, production tempo accelerated with production at Columbus, Ohio and two Canadian factories: Fairchild Aircraft Ltd. (Canada), which produced 300 (under the designations XSBF-l, SBF-l, SBF-3, and SBF-4E), and Canadian Car and Foundry, which built 894 (designated SBW-l, SBW-3, SBW-4, SBW-4E, and SBW-5), these models being respectively equivalent to their Curtiss-built counterparts. A total of 7,140 SB2Cs were produced in World War II. Operational history US Navy
Curtiss SB2C Helldiver. The program suffered so many delays that the Grumman TBF Avenger entered service before the Helldiver, even though the Avenger had begun its development two years later. Nevertheless, production tempo accelerated with production at Columbus, Ohio and two Canadian factories: Fairchild Aircraft Ltd. (Canada), which produced 300 (under the designations XSBF-l, SBF-l, SBF-3, and SBF-4E), and Canadian Car and Foundry, which built 894 (designated SBW-l, SBW-3, SBW-4, SBW-4E, and SBW-5), these models being respectively equivalent to their Curtiss-built counterparts. A total of 7,140 SB2Cs were produced in World War II. Operational history US Navy
524763
wiki20220301en020_105665
Curtiss SB2C Helldiver
Operational history US Navy The U.S. Navy would not accept the SB2C until 880 modifications to the design and the changes on the production line had been made, delaying the Curtiss Helldiver's combat debut until 11 November 1943 with squadron VB-17 on , when they attacked the Japanese-held port of Rabaul on the island of New Britain, north of Papua New Guinea. The first version of the SB2C-1 was kept stateside for training, its various development problems leading to only 200 being built. The first deployment model was the SB2C-1C. The SB2C-1 could deploy slats mechanically linked with landing gear actuators, that extended from the outer third of the wing leading edge to aid lateral control at low speeds. The early prognosis of the "Beast" was unfavourable; it was strongly disliked by aircrews due to its size, weight, and reduced range compared to the SBD it replaced.
Curtiss SB2C Helldiver. Operational history US Navy The U.S. Navy would not accept the SB2C until 880 modifications to the design and the changes on the production line had been made, delaying the Curtiss Helldiver's combat debut until 11 November 1943 with squadron VB-17 on , when they attacked the Japanese-held port of Rabaul on the island of New Britain, north of Papua New Guinea. The first version of the SB2C-1 was kept stateside for training, its various development problems leading to only 200 being built. The first deployment model was the SB2C-1C. The SB2C-1 could deploy slats mechanically linked with landing gear actuators, that extended from the outer third of the wing leading edge to aid lateral control at low speeds. The early prognosis of the "Beast" was unfavourable; it was strongly disliked by aircrews due to its size, weight, and reduced range compared to the SBD it replaced.
524763
wiki20220301en020_105666
Curtiss SB2C Helldiver
In the Battle of the Philippine Sea, 45 Helldivers, most of which had been launched from extreme range, were lost when they ran out of fuel while returning to their carriers.
Curtiss SB2C Helldiver. In the Battle of the Philippine Sea, 45 Helldivers, most of which had been launched from extreme range, were lost when they ran out of fuel while returning to their carriers.
524763
wiki20220301en020_105667
Curtiss SB2C Helldiver
Among its major faults, the Helldiver was underpowered, had a shorter range than the SBD, was equipped with an unreliable electrical system, and was often poorly manufactured. The Curtiss-Electric propeller and the complex hydraulic system had frequent maintenance problems. One of the faults remaining with the aircraft through its operational life was poor longitudinal stability, resulting from a fuselage that was too short due to the necessity of fitting onto aircraft carrier elevators. The Helldiver's aileron response was also poor and handling suffered greatly under airspeed; since the speed of approach to land on a carrier was supposed to be , this proved problematic. The 880 changes demanded by the Navy and modification of the aircraft to its combat role resulted in a 42% weight increase, explaining much of the problem.
Curtiss SB2C Helldiver. Among its major faults, the Helldiver was underpowered, had a shorter range than the SBD, was equipped with an unreliable electrical system, and was often poorly manufactured. The Curtiss-Electric propeller and the complex hydraulic system had frequent maintenance problems. One of the faults remaining with the aircraft through its operational life was poor longitudinal stability, resulting from a fuselage that was too short due to the necessity of fitting onto aircraft carrier elevators. The Helldiver's aileron response was also poor and handling suffered greatly under airspeed; since the speed of approach to land on a carrier was supposed to be , this proved problematic. The 880 changes demanded by the Navy and modification of the aircraft to its combat role resulted in a 42% weight increase, explaining much of the problem.
524763
wiki20220301en020_105668
Curtiss SB2C Helldiver
The solution to these problems began with the introduction of the SB2C-3 beginning in 1944, which used the R-2600-20 Twin Cyclone engine with and Curtiss' four-bladed propeller. This substantially solved the chronic lack of power that had plagued the aircraft. The Helldivers would participate in battles over the Marianas, Philippines (partly responsible for sinking the battleship ), Taiwan, Iwo Jima, and Okinawa (in the sinking of the battleship ). They were also used in the 1945 attacks on the Ryukyu Islands and the Japanese home island of Honshū in tactical attacks on airfields, communications and shipping. They were also used extensively in patrols during the period between the dropping of the atomic bombs and the official Japanese surrender, and in the immediate pre-occupation period.
Curtiss SB2C Helldiver. The solution to these problems began with the introduction of the SB2C-3 beginning in 1944, which used the R-2600-20 Twin Cyclone engine with and Curtiss' four-bladed propeller. This substantially solved the chronic lack of power that had plagued the aircraft. The Helldivers would participate in battles over the Marianas, Philippines (partly responsible for sinking the battleship ), Taiwan, Iwo Jima, and Okinawa (in the sinking of the battleship ). They were also used in the 1945 attacks on the Ryukyu Islands and the Japanese home island of Honshū in tactical attacks on airfields, communications and shipping. They were also used extensively in patrols during the period between the dropping of the atomic bombs and the official Japanese surrender, and in the immediate pre-occupation period.
524763
wiki20220301en020_105669
Curtiss SB2C Helldiver
An oddity of the SB2Cs with 1942 to 1943-style tricolor camouflage was that the undersides of the outer wing panels carried dark topside camouflage because the undersurfaces were visible from above when the wings were folded. In operational experience, it was found that the U.S. Navy's Grumman F6F Hellcat and Vought F4U Corsair fighters were able to carry an equally heavy bomb load against ground targets and were vastly more capable of defending themselves against enemy fighters. The Helldiver, however, could still deliver ordnance with more precision against specific targets and its two-seat configuration permitted a second set of eyes. A Helldiver also has a significant advantage in range over a fighter while carrying a bombload, which is extremely important in naval operations.
Curtiss SB2C Helldiver. An oddity of the SB2Cs with 1942 to 1943-style tricolor camouflage was that the undersides of the outer wing panels carried dark topside camouflage because the undersurfaces were visible from above when the wings were folded. In operational experience, it was found that the U.S. Navy's Grumman F6F Hellcat and Vought F4U Corsair fighters were able to carry an equally heavy bomb load against ground targets and were vastly more capable of defending themselves against enemy fighters. The Helldiver, however, could still deliver ordnance with more precision against specific targets and its two-seat configuration permitted a second set of eyes. A Helldiver also has a significant advantage in range over a fighter while carrying a bombload, which is extremely important in naval operations.
524763
wiki20220301en020_105670
Curtiss SB2C Helldiver
The advent of air-to-ground rockets ensured that the SB2C was the last purpose-built dive bomber produced. Rockets allowed precision attack against surface naval and land targets, while avoiding the stresses of near-vertical dives and the demanding performance requirements that they placed on dive bombers. The SB2C remained in active postwar service in active duty US Navy squadrons until 1947 and in Naval Reserve aviation units until 1950. Surplus aircraft were sold to the naval air forces of France, Italy, Greece, Portugal, and Thailand. Greek SB2Cs served in combat in the Greek Civil War with additional machine guns mounted in wing pods. French SB2Cs flew in the First Indochina War from 1951 to 1954.
Curtiss SB2C Helldiver. The advent of air-to-ground rockets ensured that the SB2C was the last purpose-built dive bomber produced. Rockets allowed precision attack against surface naval and land targets, while avoiding the stresses of near-vertical dives and the demanding performance requirements that they placed on dive bombers. The SB2C remained in active postwar service in active duty US Navy squadrons until 1947 and in Naval Reserve aviation units until 1950. Surplus aircraft were sold to the naval air forces of France, Italy, Greece, Portugal, and Thailand. Greek SB2Cs served in combat in the Greek Civil War with additional machine guns mounted in wing pods. French SB2Cs flew in the First Indochina War from 1951 to 1954.
524763
wiki20220301en020_105671
Curtiss SB2C Helldiver
US Army and US Marine Corps service Built at Curtiss' St. Louis plant, 900 aircraft were ordered by the USAAF under the designation A-25A Shrike. The first ten aircraft had folding wings, while the remainder of the production order omitted this feature. Many other changes distinguished the A-25A, including larger main wheels, a pneumatic tailwheel, ring and bead gunsight, longer exhaust stubs, and other Army-specified radio equipment. By late 1943, when the A-25A was being introduced, the USAAF no longer had a role for the dive bomber, as fighter aircraft such as the Republic P-47 Thunderbolt had shown their ability to carry out tactical air support missions with great success.
Curtiss SB2C Helldiver. US Army and US Marine Corps service Built at Curtiss' St. Louis plant, 900 aircraft were ordered by the USAAF under the designation A-25A Shrike. The first ten aircraft had folding wings, while the remainder of the production order omitted this feature. Many other changes distinguished the A-25A, including larger main wheels, a pneumatic tailwheel, ring and bead gunsight, longer exhaust stubs, and other Army-specified radio equipment. By late 1943, when the A-25A was being introduced, the USAAF no longer had a role for the dive bomber, as fighter aircraft such as the Republic P-47 Thunderbolt had shown their ability to carry out tactical air support missions with great success.
524763
wiki20220301en020_105672
Curtiss SB2C Helldiver
The USAAF transferred 410 Helldivers to the US Marines. The A-standard 25As were converted to the USMC variant, SB2C-1 and one squadron, VMSB-151, based on Enjebi (a.k.a. Engebi/Enjibe; part of Enewetak Atoll) conducted bombing missions on bypassed Japanese strongpoints nearby. Otherwise, the SB2C-1 variant never saw combat, and was used primarily as a trainer and target tug. Australian service At an early stage of World War II, the Australian government noted that the Royal Australian Air Force (RAAF) lacked dedicated dive bombers and ordered 150 Curtiss Shrikes. These aircraft were paid for by the US Government as Lend Lease aid. By November 1943, when the first shipment of 10 Shrikes arrived in Australia, the RAAF had decided that dive bombing was an outmoded tactic. Vultee Vengeance dive bombers, which were already in service with the RAAF, were being replaced by light bombers. As a result, the order for the remaining 140 Shrikes was cancelled.
Curtiss SB2C Helldiver. The USAAF transferred 410 Helldivers to the US Marines. The A-standard 25As were converted to the USMC variant, SB2C-1 and one squadron, VMSB-151, based on Enjebi (a.k.a. Engebi/Enjibe; part of Enewetak Atoll) conducted bombing missions on bypassed Japanese strongpoints nearby. Otherwise, the SB2C-1 variant never saw combat, and was used primarily as a trainer and target tug. Australian service At an early stage of World War II, the Australian government noted that the Royal Australian Air Force (RAAF) lacked dedicated dive bombers and ordered 150 Curtiss Shrikes. These aircraft were paid for by the US Government as Lend Lease aid. By November 1943, when the first shipment of 10 Shrikes arrived in Australia, the RAAF had decided that dive bombing was an outmoded tactic. Vultee Vengeance dive bombers, which were already in service with the RAAF, were being replaced by light bombers. As a result, the order for the remaining 140 Shrikes was cancelled.
524763
wiki20220301en020_105673
Curtiss SB2C Helldiver
While the 10 aircraft received were taken on strength, with the RAAF serial prefix A69, only one of these Shrikes officially took to the air in RAAF service. A69-4 was assigned to No. 1 Air Performance Unit, for performance testing, between December 1943 and April 1944. The RAAF and US Fifth Air Force already operated a joint pool of aircraft types common to both services in the South West Pacific theatre and, by mid-January 1944, the other nine Shrikes had been transferred to USAAF units. A69-4 was also transferred to the USAAF in December 1944. British service The Helldiver's service with the British resembled Australian experience with the type. A total of 26 aircraft, out of 450 ordered, were delivered to the Royal Navy's Fleet Air Arm, where they were known as the Helldiver I. After unsatisfactory tests by the A&AEE that pinpointed "appalling handling", none of the British Helldivers were used in action. Greek service
Curtiss SB2C Helldiver. While the 10 aircraft received were taken on strength, with the RAAF serial prefix A69, only one of these Shrikes officially took to the air in RAAF service. A69-4 was assigned to No. 1 Air Performance Unit, for performance testing, between December 1943 and April 1944. The RAAF and US Fifth Air Force already operated a joint pool of aircraft types common to both services in the South West Pacific theatre and, by mid-January 1944, the other nine Shrikes had been transferred to USAAF units. A69-4 was also transferred to the USAAF in December 1944. British service The Helldiver's service with the British resembled Australian experience with the type. A total of 26 aircraft, out of 450 ordered, were delivered to the Royal Navy's Fleet Air Arm, where they were known as the Helldiver I. After unsatisfactory tests by the A&AEE that pinpointed "appalling handling", none of the British Helldivers were used in action. Greek service
524763
wiki20220301en020_105674
Curtiss SB2C Helldiver
Greek service American aid provided the Royal Hellenic Air Force with 48 Curtiss SB2C-5 Helldivers from surplus U.S. Navy stocks. The aircraft were delivered by the aircraft carrier USS Sicily (CVE-118) in the spring of 1949. From the 48 aircraft, 6 were used for ground instruction or spare parts and 42 were given to 336th Fighter Squadron (336 Μοίρα Διώξεως) to replace Supermarine Spitfires and the squadron's name was changed to 336th Bomber Squadron (336 Μοίρα Βομβαρδισμού). Greek SB2C-5 Helldivers had minor changes for their COIN operations: the hard rubber tailwheel (for carrier use) was replaced by a bigger pneumatic tire for use on landing strips; and the rear gunner station and its twin MGs were deleted, as no aerial opposition existed and weight reduction was used for bombs and extra machine guns.
Curtiss SB2C Helldiver. Greek service American aid provided the Royal Hellenic Air Force with 48 Curtiss SB2C-5 Helldivers from surplus U.S. Navy stocks. The aircraft were delivered by the aircraft carrier USS Sicily (CVE-118) in the spring of 1949. From the 48 aircraft, 6 were used for ground instruction or spare parts and 42 were given to 336th Fighter Squadron (336 Μοίρα Διώξεως) to replace Supermarine Spitfires and the squadron's name was changed to 336th Bomber Squadron (336 Μοίρα Βομβαρδισμού). Greek SB2C-5 Helldivers had minor changes for their COIN operations: the hard rubber tailwheel (for carrier use) was replaced by a bigger pneumatic tire for use on landing strips; and the rear gunner station and its twin MGs were deleted, as no aerial opposition existed and weight reduction was used for bombs and extra machine guns.
524763
wiki20220301en020_105675
Curtiss SB2C Helldiver
Curtiss SB2C-5 Helldivers, Supermarine Spitfires, and North American T-6D/Gs were used in ground-attack missions against Communist ground forces, camps, and transports during the last stages of the Greek Civil War. Curtiss SB2C-5 Helldivers saw a relatively brief combat service and were gradually phased out by 1953. A few were in use until 1957 as photographic aircraft. One Curtiss SB2C-5 Helldiver was restored in 1997 and is displayed in the Hellenic Air Force Museum. French service Between 1949 and 1954, France bought 110 SB2C-5 Helldiver aircraft to replace their aging SBD-5 Dauntless that had been flying in combat in Vietnam. The French Aeronavale flew the Helldiver from 1951 to 1958. Some of these aircraft were allotted to flottilles 3F and 9F stationed on board the carriers Arromanches, Bois Belleau, and La Fayette, during the First Indochina War. The Helldivers were used to support French troops on the ground during the Battle of Dien Bien Phu in 1954.
Curtiss SB2C Helldiver. Curtiss SB2C-5 Helldivers, Supermarine Spitfires, and North American T-6D/Gs were used in ground-attack missions against Communist ground forces, camps, and transports during the last stages of the Greek Civil War. Curtiss SB2C-5 Helldivers saw a relatively brief combat service and were gradually phased out by 1953. A few were in use until 1957 as photographic aircraft. One Curtiss SB2C-5 Helldiver was restored in 1997 and is displayed in the Hellenic Air Force Museum. French service Between 1949 and 1954, France bought 110 SB2C-5 Helldiver aircraft to replace their aging SBD-5 Dauntless that had been flying in combat in Vietnam. The French Aeronavale flew the Helldiver from 1951 to 1958. Some of these aircraft were allotted to flottilles 3F and 9F stationed on board the carriers Arromanches, Bois Belleau, and La Fayette, during the First Indochina War. The Helldivers were used to support French troops on the ground during the Battle of Dien Bien Phu in 1954.
524763
wiki20220301en020_105676
Curtiss SB2C Helldiver
Variants XSB2C-1 Prototype powered by a 1,700 hp (1,268 kW) R-2600-8 engine SB2C-1 Production version for United States Navy with four 0.50 in (12.7 mm) wing guns and one 0.30 in (7.62 mm) dorsal gun, 200 built. SB2C-1A Original designation for United States Army Air Corps version which became A-25A later used for 410 A-25As transferred to the United States Marine Corps. SB2C-1C SB2C-1 with two 20 mm (0.79 in) wing-mounted cannons and hydraulically operated flaps, 778 built. First to see combat. XSB2C-2 One SB2C-1 fitted with twin floats in 1942. SB2C-2 Production float plane version, 287 cancelled and not built. XSB2C-3 One SB2C-1 re-engined with a 1,900 hp (1,417 kW) R-2600-20. SB2C-3 As SB2C-1c re-engined with a 1,900 hp (1,417 kW) R-2600-20 and four-bladed propeller, 1,112 built. SB2C-3E SB2C-3s fitted with APS-4 radar. SB2C-4 SB2C-1c but fitted with wing racks for eight 5 in (127 mm) rockets or 1,000 lb (454 kg) bombs, 2,045 built. SB2C-4E SB2C-4s fitted with APS-4 radar.
Curtiss SB2C Helldiver. Variants XSB2C-1 Prototype powered by a 1,700 hp (1,268 kW) R-2600-8 engine SB2C-1 Production version for United States Navy with four 0.50 in (12.7 mm) wing guns and one 0.30 in (7.62 mm) dorsal gun, 200 built. SB2C-1A Original designation for United States Army Air Corps version which became A-25A later used for 410 A-25As transferred to the United States Marine Corps. SB2C-1C SB2C-1 with two 20 mm (0.79 in) wing-mounted cannons and hydraulically operated flaps, 778 built. First to see combat. XSB2C-2 One SB2C-1 fitted with twin floats in 1942. SB2C-2 Production float plane version, 287 cancelled and not built. XSB2C-3 One SB2C-1 re-engined with a 1,900 hp (1,417 kW) R-2600-20. SB2C-3 As SB2C-1c re-engined with a 1,900 hp (1,417 kW) R-2600-20 and four-bladed propeller, 1,112 built. SB2C-3E SB2C-3s fitted with APS-4 radar. SB2C-4 SB2C-1c but fitted with wing racks for eight 5 in (127 mm) rockets or 1,000 lb (454 kg) bombs, 2,045 built. SB2C-4E SB2C-4s fitted with APS-4 radar.
524763
wiki20220301en020_105677
Curtiss SB2C Helldiver
SB2C-3E SB2C-3s fitted with APS-4 radar. SB2C-4 SB2C-1c but fitted with wing racks for eight 5 in (127 mm) rockets or 1,000 lb (454 kg) bombs, 2,045 built. SB2C-4E SB2C-4s fitted with APS-4 radar. XSB2C-5 Two SB2C-4s converted as prototypes for -5 variant. SB2C-5 SB2C-4 with increased fuel capacity, frameless sliding canopy, tailhook fixed in extended position, and deletion of the ASB radar, 970 built (2,500 cancelled). XSB2C-6 Two SB2C-1Cs fitted with 2,100 hp (1,566 kW) R-2600-22 engine and increased fuel capacity. SBF-1 Canadian built version of the SB2C-1, 50 built by Fairchild-Canada SBF-3 Canadian built version of the SB2C-3, 150 built by Fairchild-Canada. SBF-4E Canadian built version of the SB2C-4E, 100 built by Fairchild-Canada. SBW-1 Canadian built version of the SB2C-1, 38 built by Canadian Car & Foundry company. SBW-1B Canadian built version for lend-lease to the Royal Navy as the Helldiver I, 28 aircraft built by Canadian Car & Foundry company. SBW-3
Curtiss SB2C Helldiver. SB2C-3E SB2C-3s fitted with APS-4 radar. SB2C-4 SB2C-1c but fitted with wing racks for eight 5 in (127 mm) rockets or 1,000 lb (454 kg) bombs, 2,045 built. SB2C-4E SB2C-4s fitted with APS-4 radar. XSB2C-5 Two SB2C-4s converted as prototypes for -5 variant. SB2C-5 SB2C-4 with increased fuel capacity, frameless sliding canopy, tailhook fixed in extended position, and deletion of the ASB radar, 970 built (2,500 cancelled). XSB2C-6 Two SB2C-1Cs fitted with 2,100 hp (1,566 kW) R-2600-22 engine and increased fuel capacity. SBF-1 Canadian built version of the SB2C-1, 50 built by Fairchild-Canada SBF-3 Canadian built version of the SB2C-3, 150 built by Fairchild-Canada. SBF-4E Canadian built version of the SB2C-4E, 100 built by Fairchild-Canada. SBW-1 Canadian built version of the SB2C-1, 38 built by Canadian Car & Foundry company. SBW-1B Canadian built version for lend-lease to the Royal Navy as the Helldiver I, 28 aircraft built by Canadian Car & Foundry company. SBW-3
524763
wiki20220301en020_105678
Curtiss SB2C Helldiver
SBW-1B Canadian built version for lend-lease to the Royal Navy as the Helldiver I, 28 aircraft built by Canadian Car & Foundry company. SBW-3 Canadian built version of the SB2C-3, 413 built by Canadian Car & Foundry company. SBW-4E Canadian built version of the SB2C-4E, 270 built by Canadian Car & Foundry company.
Curtiss SB2C Helldiver. SBW-1B Canadian built version for lend-lease to the Royal Navy as the Helldiver I, 28 aircraft built by Canadian Car & Foundry company. SBW-3 Canadian built version of the SB2C-3, 413 built by Canadian Car & Foundry company. SBW-4E Canadian built version of the SB2C-4E, 270 built by Canadian Car & Foundry company.
524763
wiki20220301en020_105679
Curtiss SB2C Helldiver
SBW-5 Canadian-built version of the SB2C-5, 85 built (165 cancelled) by the Canadian Car & Foundry company. A-25A Shrike United States Army Air Corps version without arrester gear or folding wings and equipment changed, 900 built Helldiver I Royal Navy designation for 28 Canadian-built SBW-1Bs Operators Royal Australian Air Force French Navy Aviation Navale Royal Hellenic Air Force Italian Air Force operated 42 aircraft from 1950 until 1959 Portuguese Navy (until 1952) Portuguese Air Force (after 1952) Royal Thai Air Force Royal Thai Navy Royal Navy Fleet Air Arm United States Army Air Forces United States Marine Corps United States Navy Surviving aircraft NOTE: All surviving aircraft identified by original US Navy Bureau of Aeronautics (BuAer) Bureau Numbers (BuNo). Greece On display SB2C-5 83321 - Hellenic Air Force Museum, Decelea Air Base. Thailand On display SB2C-5 83410 - Royal Thai Air Force Museum, Don Muang Royal Thai Air Force Base, Bangkok.
Curtiss SB2C Helldiver. SBW-5 Canadian-built version of the SB2C-5, 85 built (165 cancelled) by the Canadian Car & Foundry company. A-25A Shrike United States Army Air Corps version without arrester gear or folding wings and equipment changed, 900 built Helldiver I Royal Navy designation for 28 Canadian-built SBW-1Bs Operators Royal Australian Air Force French Navy Aviation Navale Royal Hellenic Air Force Italian Air Force operated 42 aircraft from 1950 until 1959 Portuguese Navy (until 1952) Portuguese Air Force (after 1952) Royal Thai Air Force Royal Thai Navy Royal Navy Fleet Air Arm United States Army Air Forces United States Marine Corps United States Navy Surviving aircraft NOTE: All surviving aircraft identified by original US Navy Bureau of Aeronautics (BuAer) Bureau Numbers (BuNo). Greece On display SB2C-5 83321 - Hellenic Air Force Museum, Decelea Air Base. Thailand On display SB2C-5 83410 - Royal Thai Air Force Museum, Don Muang Royal Thai Air Force Base, Bangkok.
524763
wiki20220301en020_105680
Curtiss SB2C Helldiver
United States Airworthy SB2C-5 83589 - based at the Commemorative Air Force (Cactus Squadron) in Graham, Texas. This late-production Helldiver, built in 1945, makes frequent air show appearances. In 1982, it experienced engine failure and a hard emergency landing that caused extensive damage; volunteers of the CAF put in thousands of hours and spent in excess of $200,000 to restore the aircraft to flying condition once more. As of October 2018, it is still the only flying example in the world. On display SB2C-5 83479 - Steven F. Udvar-Hazy Center of the National Air and Space Museum in Chantilly, Virginia. Under restoration A-25A Shrike/SB2C-1A 75552 - under restoration at the National Museum of World War II Aviation in Colorado Springs, Colorado. 76805 - for display at the National Museum of the United States Air Force at Wright-Patterson AFB in Dayton, Ohio. SB2C-3 19075 - for display at the Yanks Air Museum in Chino, California SB2C-4
Curtiss SB2C Helldiver. United States Airworthy SB2C-5 83589 - based at the Commemorative Air Force (Cactus Squadron) in Graham, Texas. This late-production Helldiver, built in 1945, makes frequent air show appearances. In 1982, it experienced engine failure and a hard emergency landing that caused extensive damage; volunteers of the CAF put in thousands of hours and spent in excess of $200,000 to restore the aircraft to flying condition once more. As of October 2018, it is still the only flying example in the world. On display SB2C-5 83479 - Steven F. Udvar-Hazy Center of the National Air and Space Museum in Chantilly, Virginia. Under restoration A-25A Shrike/SB2C-1A 75552 - under restoration at the National Museum of World War II Aviation in Colorado Springs, Colorado. 76805 - for display at the National Museum of the United States Air Force at Wright-Patterson AFB in Dayton, Ohio. SB2C-3 19075 - for display at the Yanks Air Museum in Chino, California SB2C-4
524763
wiki20220301en020_105681
Curtiss SB2C Helldiver
76805 - for display at the National Museum of the United States Air Force at Wright-Patterson AFB in Dayton, Ohio. SB2C-3 19075 - for display at the Yanks Air Museum in Chino, California SB2C-4 19866 - for display at the National Naval Aviation Museum at Naval Air Station Pensacola, Florida. It crashed on 28 May 1945 in Lower Otay Reservoir, near San Diego, California after engine failure during a training exercise. Both pilot E.D. Frazer and his passenger escaped uninjured, but the Helldiver sank in 90 ft. of water. The aircraft was discovered in February 2010 by a fisherman and recovered on 20 August 2010 for restoration. SB2C-5 83393 - for display at the Fagen Fighters WWII Museum in Granite Falls, Minnesota. Wrecks
Curtiss SB2C Helldiver. 76805 - for display at the National Museum of the United States Air Force at Wright-Patterson AFB in Dayton, Ohio. SB2C-3 19075 - for display at the Yanks Air Museum in Chino, California SB2C-4 19866 - for display at the National Naval Aviation Museum at Naval Air Station Pensacola, Florida. It crashed on 28 May 1945 in Lower Otay Reservoir, near San Diego, California after engine failure during a training exercise. Both pilot E.D. Frazer and his passenger escaped uninjured, but the Helldiver sank in 90 ft. of water. The aircraft was discovered in February 2010 by a fisherman and recovered on 20 August 2010 for restoration. SB2C-5 83393 - for display at the Fagen Fighters WWII Museum in Granite Falls, Minnesota. Wrecks
524763
wiki20220301en020_105682
Curtiss SB2C Helldiver
SB2C-5 83393 - for display at the Fagen Fighters WWII Museum in Granite Falls, Minnesota. Wrecks A SB2C-4E Helldiver belonging to the United States Navy crashed and burned in foul weather on October 9, 1945, while en route from New Cumberland, Pennsylvania to its base at Naval Air Station Grosse Ile, Michigan after participating in Nimitz Day celebrations held in Washington, D.C. Pilot Frank Campbell and gunner George Cohlmia, both World War II veterans, were killed in the crash. The remains of the plane are still located at the crash site on Laurel Hill in Ligonier Township, Pennsylvania, three miles southeast of the village of Waterford.
Curtiss SB2C Helldiver. SB2C-5 83393 - for display at the Fagen Fighters WWII Museum in Granite Falls, Minnesota. Wrecks A SB2C-4E Helldiver belonging to the United States Navy crashed and burned in foul weather on October 9, 1945, while en route from New Cumberland, Pennsylvania to its base at Naval Air Station Grosse Ile, Michigan after participating in Nimitz Day celebrations held in Washington, D.C. Pilot Frank Campbell and gunner George Cohlmia, both World War II veterans, were killed in the crash. The remains of the plane are still located at the crash site on Laurel Hill in Ligonier Township, Pennsylvania, three miles southeast of the village of Waterford.
524763
wiki20220301en020_105683
Curtiss SB2C Helldiver
In January 2010, a scuba diver discovered a SB2C-1C Helldiver that was ditched in Maalaea Bay off South Maui in August 1944. The Helldiver is covered in coral and is missing its tail section. The aircraft experienced problems with its empennage after dive bombing maneuvers which forced pilot Lieutenant William Dill to ditch. It lies in 50 ft of water facing east. The site, which is protected under state and federal law, is in the process of being marked with a plaque by the U.S. Navy. A mooring may be installed at a later point in time to facilitate dives on the site. On 25 March 2010, the Oregon State Police, Tillamook County Sheriff's Office, and the United States Navy announced that during a logging operation near Rockaway Beach, Oregon, the wreck of an SB2C Helldiver was located. Initial responders believe there may be human remains on the scene.
Curtiss SB2C Helldiver. In January 2010, a scuba diver discovered a SB2C-1C Helldiver that was ditched in Maalaea Bay off South Maui in August 1944. The Helldiver is covered in coral and is missing its tail section. The aircraft experienced problems with its empennage after dive bombing maneuvers which forced pilot Lieutenant William Dill to ditch. It lies in 50 ft of water facing east. The site, which is protected under state and federal law, is in the process of being marked with a plaque by the U.S. Navy. A mooring may be installed at a later point in time to facilitate dives on the site. On 25 March 2010, the Oregon State Police, Tillamook County Sheriff's Office, and the United States Navy announced that during a logging operation near Rockaway Beach, Oregon, the wreck of an SB2C Helldiver was located. Initial responders believe there may be human remains on the scene.
524763
wiki20220301en020_105684
Curtiss SB2C Helldiver
On 19 December 2011 Scuba divers off the coast of Jupiter, Florida came across an SB2C Helldiver while under water. The aircraft is mostly intact and was found inverted with the landing gear retracted. In May 2012, the US Navy conducted a survey of the aircraft, recovering a data plate from the horizontal stabilizer. The Naval History and Heritage Command's Underwater Archaeology Branch is actively trying to determine if the numbers stamped on the data plate are readable and will identify the aircraft.
Curtiss SB2C Helldiver. On 19 December 2011 Scuba divers off the coast of Jupiter, Florida came across an SB2C Helldiver while under water. The aircraft is mostly intact and was found inverted with the landing gear retracted. In May 2012, the US Navy conducted a survey of the aircraft, recovering a data plate from the horizontal stabilizer. The Naval History and Heritage Command's Underwater Archaeology Branch is actively trying to determine if the numbers stamped on the data plate are readable and will identify the aircraft.
524763
wiki20220301en020_105685
Curtiss SB2C Helldiver
Specifications (SB2C-4 Helldiver) See also References Notes Bibliography
Curtiss SB2C Helldiver. Specifications (SB2C-4 Helldiver) See also References Notes Bibliography
524763
wiki20220301en020_105686
Curtiss SB2C Helldiver
Abzug, Malcolm J. and E. Eugene Larrabee. Airplane Stability and Control: A History of the Technologies that Made Aviation Possible (Cambridge Aerospace Series). Cambridge, UK: Cambridge University Press, 1997. . Andrews, Harald. The Curtiss SB2C-1 Helldiver, Aircraft in Profile 124. Windsor, Berkshire, UK: Profile publications Ltd., 1967, reprinted 1971 and 1982. No ISBN. Bowers, Peter M. Curtiss Aircraft 1907-1947. London: Putnam & Company Ltd., 1979. . Brown, Eric, CBE, DCS, AFC, RN., William Green and Gordon Swanborough. "Curtiss Helldiver". Wings of the Navy, Flying Allied Carrier Aircraft of World War Two. London: Jane's Publishing Company, 1980, pp. 90–99. . Crosnier, Alain and Jean-Pierre Dubois. Douglas SBD-5 Dauntless & Curtiss SB2C-5 Helldiver: Bombardiers en piqué de l’Aéronautique Navale (in French). Clichy-la-Garenne, France: DTU sarl., 1998. . Donald, David, ed. American Warplanes of World War II. London: Aerospace Publishing, 1995. .
Curtiss SB2C Helldiver. Abzug, Malcolm J. and E. Eugene Larrabee. Airplane Stability and Control: A History of the Technologies that Made Aviation Possible (Cambridge Aerospace Series). Cambridge, UK: Cambridge University Press, 1997. . Andrews, Harald. The Curtiss SB2C-1 Helldiver, Aircraft in Profile 124. Windsor, Berkshire, UK: Profile publications Ltd., 1967, reprinted 1971 and 1982. No ISBN. Bowers, Peter M. Curtiss Aircraft 1907-1947. London: Putnam & Company Ltd., 1979. . Brown, Eric, CBE, DCS, AFC, RN., William Green and Gordon Swanborough. "Curtiss Helldiver". Wings of the Navy, Flying Allied Carrier Aircraft of World War Two. London: Jane's Publishing Company, 1980, pp. 90–99. . Crosnier, Alain and Jean-Pierre Dubois. Douglas SBD-5 Dauntless & Curtiss SB2C-5 Helldiver: Bombardiers en piqué de l’Aéronautique Navale (in French). Clichy-la-Garenne, France: DTU sarl., 1998. . Donald, David, ed. American Warplanes of World War II. London: Aerospace Publishing, 1995. .
524763
wiki20220301en020_105687
Curtiss SB2C Helldiver
Donald, David, ed. American Warplanes of World War II. London: Aerospace Publishing, 1995. . Drendel, Lou. U.S. Navy Carrier Bombers of World War II. Carrollton, Texas: Squadron/Signal Publications, Inc., 1987. . Ethell, L. Jeffrey. Aircraft of World War II. Glasgow: HarperCollins Publishers, 1995. . Forsyth, John F. Helldivers, US Navy Dive-Bombers at War. St. Paul, Minnesota: Motorbooks International, 1991. . Kinzey, Bert. SB2C Helldiver in Detail & Scale, D&S Vol.52. Carrollton, Texas: Squadron/Signal Publications, 1997. . Ociepka, Paweł P. "Curtiss SB2C Helldiver" (in Polish). Skrzydła w miniaturze 12. Gdańsk, Poland: Avia-Press, 1995. ISSN 1234-4109. Shettle, M.L. Jr. United States Marine Corps Air Stations of World War II. Bowersville, Georgia: Schaertel Publishing Co., 2001. . Smith, Peter C. SB2C Helldiver. Ramsbury, Marlborough, Wiltshire, UK: The Crowood Press Ltd., 1998. .
Curtiss SB2C Helldiver. Donald, David, ed. American Warplanes of World War II. London: Aerospace Publishing, 1995. . Drendel, Lou. U.S. Navy Carrier Bombers of World War II. Carrollton, Texas: Squadron/Signal Publications, Inc., 1987. . Ethell, L. Jeffrey. Aircraft of World War II. Glasgow: HarperCollins Publishers, 1995. . Forsyth, John F. Helldivers, US Navy Dive-Bombers at War. St. Paul, Minnesota: Motorbooks International, 1991. . Kinzey, Bert. SB2C Helldiver in Detail & Scale, D&S Vol.52. Carrollton, Texas: Squadron/Signal Publications, 1997. . Ociepka, Paweł P. "Curtiss SB2C Helldiver" (in Polish). Skrzydła w miniaturze 12. Gdańsk, Poland: Avia-Press, 1995. ISSN 1234-4109. Shettle, M.L. Jr. United States Marine Corps Air Stations of World War II. Bowersville, Georgia: Schaertel Publishing Co., 2001. . Smith, Peter C. SB2C Helldiver. Ramsbury, Marlborough, Wiltshire, UK: The Crowood Press Ltd., 1998. .
524763
wiki20220301en020_105688
Curtiss SB2C Helldiver
Smith, Peter C. SB2C Helldiver. Ramsbury, Marlborough, Wiltshire, UK: The Crowood Press Ltd., 1998. . Stern, Robert. SB2C Helldiver in Action, Aircraft Number 54. Carrollton, Texas: Squadron/Signal Publications inc., 1982. . Swanborough, Gordon and Peter M. Bowers. United States Navy Aircraft since 1911. London: Putnam, Second edition, 1976. . Taylor, John W. R. "Curtiss SB2C/A-25 Helldiver." Combat Aircraft of the World from 1909 to the present. New York: G.P. Putnam's Sons, 1969. . Tillman, Barrett. Helldiver Units of World War 2. London: Osprey Publishing, 1997. . Tillman, Barrett and Robert L. Lawson. U.S. Navy Dive and Torpedo Bombers of WWII. St. Paul, Minnesota: Motor Books Publishing, 2001. . Winchester, Jim. "Curtiss SB2C Helldiver." Aircraft of World War II: The Aviation Factfile. Kent, UK: Grange Books plc, 2004. .
Curtiss SB2C Helldiver. Smith, Peter C. SB2C Helldiver. Ramsbury, Marlborough, Wiltshire, UK: The Crowood Press Ltd., 1998. . Stern, Robert. SB2C Helldiver in Action, Aircraft Number 54. Carrollton, Texas: Squadron/Signal Publications inc., 1982. . Swanborough, Gordon and Peter M. Bowers. United States Navy Aircraft since 1911. London: Putnam, Second edition, 1976. . Taylor, John W. R. "Curtiss SB2C/A-25 Helldiver." Combat Aircraft of the World from 1909 to the present. New York: G.P. Putnam's Sons, 1969. . Tillman, Barrett. Helldiver Units of World War 2. London: Osprey Publishing, 1997. . Tillman, Barrett and Robert L. Lawson. U.S. Navy Dive and Torpedo Bombers of WWII. St. Paul, Minnesota: Motor Books Publishing, 2001. . Winchester, Jim. "Curtiss SB2C Helldiver." Aircraft of World War II: The Aviation Factfile. Kent, UK: Grange Books plc, 2004. .
524763
wiki20220301en020_105689
Curtiss SB2C Helldiver
External links "I Ride 'The Beast'." by J. Runyan, Popular Science, February 1945 The Commemorative Air Force's flying SB2C Helldiver WW2DB: SB2C Helldiver ENS Bob Barnes: Helldivers of the Big E "The Greek Civil War, 1944-1949" Flight 1943 article Interior and exterior spherical panoramas of Commemorative AF flying museum SB02C Helldiver 1940s United States bomber aircraft Single-engined tractor aircraft Low-wing aircraft Carrier-based aircraft World War II dive bombers World War II ground attack aircraft of the United States Aircraft first flown in 1940
Curtiss SB2C Helldiver. External links "I Ride 'The Beast'." by J. Runyan, Popular Science, February 1945 The Commemorative Air Force's flying SB2C Helldiver WW2DB: SB2C Helldiver ENS Bob Barnes: Helldivers of the Big E "The Greek Civil War, 1944-1949" Flight 1943 article Interior and exterior spherical panoramas of Commemorative AF flying museum SB02C Helldiver 1940s United States bomber aircraft Single-engined tractor aircraft Low-wing aircraft Carrier-based aircraft World War II dive bombers World War II ground attack aircraft of the United States Aircraft first flown in 1940
524763
wiki20220301en020_105690
Petty officer
A Petty Officer (PO) is a non-commissioned officer in many navies and is given the NATO rank denotion OR-5 or OR-6. In many nations, they are typically equal to a sergeant in comparison to other military branches. Often they may be superior to a seaman, and subordinate to more senior non-commissioned officers, such as a chief petty officers. Petty officers are usually sailors that have served at least several years in their respective navies. Petty officers represent the junior and mid-grade non-commissioned officer ranks of many naval services, and are generally responsible for the day-to-day supervision of ranks junior to them. They may also serve as technical specialists within their rating (military occupation). Origin
Petty officer. A Petty Officer (PO) is a non-commissioned officer in many navies and is given the NATO rank denotion OR-5 or OR-6. In many nations, they are typically equal to a sergeant in comparison to other military branches. Often they may be superior to a seaman, and subordinate to more senior non-commissioned officers, such as a chief petty officers. Petty officers are usually sailors that have served at least several years in their respective navies. Petty officers represent the junior and mid-grade non-commissioned officer ranks of many naval services, and are generally responsible for the day-to-day supervision of ranks junior to them. They may also serve as technical specialists within their rating (military occupation). Origin
524764
wiki20220301en020_105691
Petty officer
Origin The modern petty officer dates back to the Age of Sail in the Royal Navy. Petty officers rank between naval officers (both commissioned and warrant) and most enlisted sailors. These were men with some claim to officer rank, sufficient to distinguish them from ordinary ratings, without raising them so high as the sea officers. Several were warrant officers, in the literal sense of being appointed by warrant, and like the warrant sea officers, their superiors, they were usually among the specialists of the ship's company. The Oxford English Dictionary suggests that the title derives from the Anglo-Norman and Middle French "petit", meaning "of small size, small, little".<ref>"petty officer", Oxford English Dictionary', Oxford University Press</ref>
Petty officer. Origin The modern petty officer dates back to the Age of Sail in the Royal Navy. Petty officers rank between naval officers (both commissioned and warrant) and most enlisted sailors. These were men with some claim to officer rank, sufficient to distinguish them from ordinary ratings, without raising them so high as the sea officers. Several were warrant officers, in the literal sense of being appointed by warrant, and like the warrant sea officers, their superiors, they were usually among the specialists of the ship's company. The Oxford English Dictionary suggests that the title derives from the Anglo-Norman and Middle French "petit", meaning "of small size, small, little".<ref>"petty officer", Oxford English Dictionary', Oxford University Press</ref>
524764
wiki20220301en020_105692
Petty officer
Two of the Royal Navy petty officer's rates, midshipman and master's mate, were a superior petty officer with a more general authority, but they remained no more than ratings. However, it was quite possible for a warrant officer (such as the armourer), in his role as a superior officer, to be court-martialed for striking a midshipman. This is because the midshipman was regarded as future sea officer, with the all-important social distinction of having the right to walk the quarterdeck. Midshipmen wore distinctive uniforms, master's mates dressed respectably, and both behaved like officers. The master's mate rating evolved into the rank of sub-lieutenant, and midshipman evolved into naval cadet. Usage in navies
Petty officer. Two of the Royal Navy petty officer's rates, midshipman and master's mate, were a superior petty officer with a more general authority, but they remained no more than ratings. However, it was quite possible for a warrant officer (such as the armourer), in his role as a superior officer, to be court-martialed for striking a midshipman. This is because the midshipman was regarded as future sea officer, with the all-important social distinction of having the right to walk the quarterdeck. Midshipmen wore distinctive uniforms, master's mates dressed respectably, and both behaved like officers. The master's mate rating evolved into the rank of sub-lieutenant, and midshipman evolved into naval cadet. Usage in navies
524764
wiki20220301en020_105693
Petty officer
Usage in navies Canada There are two petty officer ranks in the Royal Canadian Navy. Petty officer, 2nd class (PO2) (maître de deuxième classe or m2 in French) is equivalent to a sergeant and petty officer, 1st class (PO1) (maître de première classe or m1) is equivalent to a warrant officer. Petty officers are normally addressed as "Petty Officer Bloggins" or "PO Bloggins", thereafter as "PO". The "1st class" and "2nd class" designations are normally only used when such a distinction needs to be made, such as on a promotion parade or to distinguish two petty officers with similar names but different ranks. The NATO rank denotion for "petty officer, 2nd class" is OR-6 (petty officers, 2nd class with less than 3 years seniority are considered OR-5). The NATO rank denotion for "petty officer, 1st class" is OR-7.
Petty officer. Usage in navies Canada There are two petty officer ranks in the Royal Canadian Navy. Petty officer, 2nd class (PO2) (maître de deuxième classe or m2 in French) is equivalent to a sergeant and petty officer, 1st class (PO1) (maître de première classe or m1) is equivalent to a warrant officer. Petty officers are normally addressed as "Petty Officer Bloggins" or "PO Bloggins", thereafter as "PO". The "1st class" and "2nd class" designations are normally only used when such a distinction needs to be made, such as on a promotion parade or to distinguish two petty officers with similar names but different ranks. The NATO rank denotion for "petty officer, 2nd class" is OR-6 (petty officers, 2nd class with less than 3 years seniority are considered OR-5). The NATO rank denotion for "petty officer, 1st class" is OR-7.
524764
wiki20220301en020_105694
Petty officer
India A petty officer is a non-commissioned officer in the Indian Navy, equivalent to the NATO rank enlisted grade of OR-6. They are equal in rank to a sub inspector of police in the Indian Police Services, or sergeant in the Indian Army and Indian Air Force. A petty officer is superior in rank to a leading rate and subordinate to a chief petty officer, as is the case in the majority of Commonwealth navies. A petty officer has the ability to work as a leader, capable of taking charge of a group of personnel, and taking roles in the training and recruitment of new members of the Indian Navy. United Kingdom In the Royal Navy, the rate of petty officer comes above that of leading rating and below that of chief petty officer. It is the equivalent of sergeant in the Royal Marines, British Army and Royal Air Force. Petty officer is the lowest of the senior rating grades. Petty officers, like all senior rates, wear "fore and aft" rig. United States
Petty officer. India A petty officer is a non-commissioned officer in the Indian Navy, equivalent to the NATO rank enlisted grade of OR-6. They are equal in rank to a sub inspector of police in the Indian Police Services, or sergeant in the Indian Army and Indian Air Force. A petty officer is superior in rank to a leading rate and subordinate to a chief petty officer, as is the case in the majority of Commonwealth navies. A petty officer has the ability to work as a leader, capable of taking charge of a group of personnel, and taking roles in the training and recruitment of new members of the Indian Navy. United Kingdom In the Royal Navy, the rate of petty officer comes above that of leading rating and below that of chief petty officer. It is the equivalent of sergeant in the Royal Marines, British Army and Royal Air Force. Petty officer is the lowest of the senior rating grades. Petty officers, like all senior rates, wear "fore and aft" rig. United States
524764
wiki20220301en020_105695
Petty officer
United States The title of petty officer in the United States Navy and United States Coast Guard has three separate "classes" (in order from junior to senior: 3rd class, 2nd class, 1st class) and three senior grades (chief petty officer, senior chief petty officer, master chief petty officer). Petty officer, first class is equivalent in paygrade to staff sergeant in the United States Army and Marine Corps, and technical sergeant in the United States Air Force and United States Space Force. Petty officer, second class is equivalent in paygrade to sergeant in the United States Army, Marine Corps, and Space Force, and staff sergeant in the United States Air Force. Petty officer, third class is equivalent in paygrade to corporal in the United States Army, corporal in the United States Marine Corps, senior airman in the United States Air Force, and specialist 4 in the United States Space Force.
Petty officer. United States The title of petty officer in the United States Navy and United States Coast Guard has three separate "classes" (in order from junior to senior: 3rd class, 2nd class, 1st class) and three senior grades (chief petty officer, senior chief petty officer, master chief petty officer). Petty officer, first class is equivalent in paygrade to staff sergeant in the United States Army and Marine Corps, and technical sergeant in the United States Air Force and United States Space Force. Petty officer, second class is equivalent in paygrade to sergeant in the United States Army, Marine Corps, and Space Force, and staff sergeant in the United States Air Force. Petty officer, third class is equivalent in paygrade to corporal in the United States Army, corporal in the United States Marine Corps, senior airman in the United States Air Force, and specialist 4 in the United States Space Force.
524764
wiki20220301en020_105696
Petty officer
In the Navy, Petty Officer, Third Class is the juniormost of the Non-Commissioned Officer ranks, and thus a sailor must demonstrate satisfactory performance in the previous rank (E-3) in the form of a favorable performance review(s) by his/her superiors, and the passing of an exam, in order to be promoted to PO3. Enlisted rank has two components: rate (pay grade) and rating (job specialty). Both components are reflected in the title. A sailor in the rate of petty officer first class with a rating of Aviation Machinist's Mate, would be an Aviation Machinist's Mate 1st Class (abbreviated "AD1"). In the Navy, it is acceptable to refer to a Petty Officer as such, while in the Coast Guard, rating is always used. Non-English-speaking countries In some countries the same term is used as for a non-commissioned officer (NCO) in land forces, e.g. "suboficial" in some Spanish-speaking countries. The Russian equivalent is Starshina''.
Petty officer. In the Navy, Petty Officer, Third Class is the juniormost of the Non-Commissioned Officer ranks, and thus a sailor must demonstrate satisfactory performance in the previous rank (E-3) in the form of a favorable performance review(s) by his/her superiors, and the passing of an exam, in order to be promoted to PO3. Enlisted rank has two components: rate (pay grade) and rating (job specialty). Both components are reflected in the title. A sailor in the rate of petty officer first class with a rating of Aviation Machinist's Mate, would be an Aviation Machinist's Mate 1st Class (abbreviated "AD1"). In the Navy, it is acceptable to refer to a Petty Officer as such, while in the Coast Guard, rating is always used. Non-English-speaking countries In some countries the same term is used as for a non-commissioned officer (NCO) in land forces, e.g. "suboficial" in some Spanish-speaking countries. The Russian equivalent is Starshina''.
524764
wiki20220301en020_105697
Petty officer
See also Boatswain's mate (disambiguation) List of United States Navy ratings Royal Navy ratings rank insignia United States Navy enlisted rates References Military ranks of the Commonwealth Military ranks of Australia Military ranks of Canada Military ranks of the Royal Navy Military ranks of the United States Navy Naval ranks Marine occupations
Petty officer. See also Boatswain's mate (disambiguation) List of United States Navy ratings Royal Navy ratings rank insignia United States Navy enlisted rates References Military ranks of the Commonwealth Military ranks of Australia Military ranks of Canada Military ranks of the Royal Navy Military ranks of the United States Navy Naval ranks Marine occupations
524764
wiki20220301en020_105698
Tymnet
Tymnet was an international data communications network headquartered in Cupertino, California that used virtual call packet-switched technology and X.25, SNA/SDLC, BSC and Async interfaces to connect host computers (servers) at thousands of large companies, educational institutions, and government agencies. Users typically connected via dial-up connections or dedicated asynchronous connections. The business consisted of a large public network that supported dial-up users and a private network that allowed government agencies and large companies (mostly banks and airlines) to build their own dedicated networks. The private networks were often connected via gateways to the public network to reach locations not on the private network. Tymnet was also connected to dozens of other public networks in the United States and internationally via X.25/X.75 gateways.
Tymnet. Tymnet was an international data communications network headquartered in Cupertino, California that used virtual call packet-switched technology and X.25, SNA/SDLC, BSC and Async interfaces to connect host computers (servers) at thousands of large companies, educational institutions, and government agencies. Users typically connected via dial-up connections or dedicated asynchronous connections. The business consisted of a large public network that supported dial-up users and a private network that allowed government agencies and large companies (mostly banks and airlines) to build their own dedicated networks. The private networks were often connected via gateways to the public network to reach locations not on the private network. Tymnet was also connected to dozens of other public networks in the United States and internationally via X.25/X.75 gateways.
524766
wiki20220301en020_105699
Tymnet
As the Internet grew and became almost universally accessible in the late 1990s, the need for services such as Tymnet migrated to the Internet style connections, but still had some value in the Third World and for specific legacy roles. However the value of these links continued to decrease, and Tymnet shut down in 2004. Network Tymnet offered local dial-up modem access in most cities in the United States and to a limited degree in Canada, which preferred its own DATAPAC service. Users would dial into Tymnet and then interact with a simple command-line interface to establish a connection with a remote system. Once connected, data was passed to and from the user as if connected directly to a modem on the distant system. For various technical reasons, the connection was not entirely "invisible", and sometimes required the user to enter arcane commands to make 8-bit clean connections work properly for file transfer.
Tymnet. As the Internet grew and became almost universally accessible in the late 1990s, the need for services such as Tymnet migrated to the Internet style connections, but still had some value in the Third World and for specific legacy roles. However the value of these links continued to decrease, and Tymnet shut down in 2004. Network Tymnet offered local dial-up modem access in most cities in the United States and to a limited degree in Canada, which preferred its own DATAPAC service. Users would dial into Tymnet and then interact with a simple command-line interface to establish a connection with a remote system. Once connected, data was passed to and from the user as if connected directly to a modem on the distant system. For various technical reasons, the connection was not entirely "invisible", and sometimes required the user to enter arcane commands to make 8-bit clean connections work properly for file transfer.
524766
wiki20220301en020_105700
Tymnet
Tymnet was extensively used by large companies to provide dial-up services for their employees who were "on the road", as well as a gateway for users to connect to large online services such as CompuServe or The Source. Organization and functionality In its original implementation, the network supervisor contained most of the routing intelligence in the network. Unlike the TCP/IP protocol underlying the internet, Tymnet used a circuit switching layout which allowed the supervisors to be aware of every possible end-point. In its original incarnation, the users connected to nodes built using Varian minicomputers, then entered commands that were passed to the supervisor which ran on a XDS 940 host.
Tymnet. Tymnet was extensively used by large companies to provide dial-up services for their employees who were "on the road", as well as a gateway for users to connect to large online services such as CompuServe or The Source. Organization and functionality In its original implementation, the network supervisor contained most of the routing intelligence in the network. Unlike the TCP/IP protocol underlying the internet, Tymnet used a circuit switching layout which allowed the supervisors to be aware of every possible end-point. In its original incarnation, the users connected to nodes built using Varian minicomputers, then entered commands that were passed to the supervisor which ran on a XDS 940 host.
524766
wiki20220301en020_105701
Tymnet
Circuits were character oriented and the network was oriented towards interactive character-by-character full-duplex communications circuits. The nodes handled character translation between various character sets, which were numerous at that time. This did have the side effect of making data transfers quite difficult, as bytes from the file would be invisibly "translated" without specific intervention on the part of the user. Tymnet later developed their own custom hardware, the Tymnet Engine, which contained both nodes and a supervisor running on one of those nodes. As the network grew, the supervisor was in danger of being overloaded by the sheer number of nodes in the network, since the requirements for controlling the network took a great part of the supervisor's capacity.
Tymnet. Circuits were character oriented and the network was oriented towards interactive character-by-character full-duplex communications circuits. The nodes handled character translation between various character sets, which were numerous at that time. This did have the side effect of making data transfers quite difficult, as bytes from the file would be invisibly "translated" without specific intervention on the part of the user. Tymnet later developed their own custom hardware, the Tymnet Engine, which contained both nodes and a supervisor running on one of those nodes. As the network grew, the supervisor was in danger of being overloaded by the sheer number of nodes in the network, since the requirements for controlling the network took a great part of the supervisor's capacity.
524766
wiki20220301en020_105702
Tymnet
Tymnet II was developed in response to this challenge. Tymnet II was developed to ameliorate the problems outlined above by off-loading some of the work-load from the supervisor and providing greater flexibility in the network by putting more intelligence into the node code. A Tymnet II node would set up its own "permuter tables", eliminating the need for the supervisor to keep copies of them, and had greater flexibility in handling its inter-node links. Data transfers were also possible via "auxiliary circuits". History Beginnings: Tymshare Tymshare was founded in 1964 as a time sharing company, selling computer time and software packages for users. It had two SDS/XDS 940 computers; access was via direct dial-up to the computers. In 1968, it purchased Dial Data, another time-sharing service bureau.
Tymnet. Tymnet II was developed in response to this challenge. Tymnet II was developed to ameliorate the problems outlined above by off-loading some of the work-load from the supervisor and providing greater flexibility in the network by putting more intelligence into the node code. A Tymnet II node would set up its own "permuter tables", eliminating the need for the supervisor to keep copies of them, and had greater flexibility in handling its inter-node links. Data transfers were also possible via "auxiliary circuits". History Beginnings: Tymshare Tymshare was founded in 1964 as a time sharing company, selling computer time and software packages for users. It had two SDS/XDS 940 computers; access was via direct dial-up to the computers. In 1968, it purchased Dial Data, another time-sharing service bureau.
524766
wiki20220301en020_105703
Tymnet
In 1968, Norm Hardy and LaRoy Tymes developed the idea of using remote sites with minicomputers to communicate with the mainframes. The minicomputers would serve as the network's nodes, running a program to route data. In November 1971, the first Tymnet Supervisor program became operational. Written in assembly code by LaRoy Tymes for the SDS 940, with architectural design contributions from Norman Hardy, the "Supervisor" was the beginning of the Tymnet network. One instance of the supervisor would be running at all times and choose a path (circuit) through the network for each new interactive session. The Varian 620i (8K of 16 bit words) was used for the TYMNET nodes. Initially, Tymshare and its direct customers were the network's only users. In February, 1972, the National Library of Medicine became the first non-Tymshare network customer with a toxicology data base on an IBM 360.
Tymnet. In 1968, Norm Hardy and LaRoy Tymes developed the idea of using remote sites with minicomputers to communicate with the mainframes. The minicomputers would serve as the network's nodes, running a program to route data. In November 1971, the first Tymnet Supervisor program became operational. Written in assembly code by LaRoy Tymes for the SDS 940, with architectural design contributions from Norman Hardy, the "Supervisor" was the beginning of the Tymnet network. One instance of the supervisor would be running at all times and choose a path (circuit) through the network for each new interactive session. The Varian 620i (8K of 16 bit words) was used for the TYMNET nodes. Initially, Tymshare and its direct customers were the network's only users. In February, 1972, the National Library of Medicine became the first non-Tymshare network customer with a toxicology data base on an IBM 360.
524766
wiki20220301en020_105704
Tymnet
It soon became apparent that the SDS 940 could not keep up with the rapid growth of the network. In 1972, Joseph Rinde joined the Tymnet group and began porting the Supervisor code to the 32-bit Interdata 7/32, as the 8/32 was not yet ready. In 1973, the 8/32 became available, but the performance was disappointing and a crash-effort was made to develop a machine that could run Rinde's Supervisor. In 1974, a second, more efficient version of the Supervisor software became operational. The new Tymnet "Engine" software was used on both the Supervisor machines and on the nodes. After the migration to the Tymnet Engine, they started developing Tymnet accounting and other support software on the PDP-10. Tymshare sold the Tymnet network software to TRW, who created their own private network, TRWNET.
Tymnet. It soon became apparent that the SDS 940 could not keep up with the rapid growth of the network. In 1972, Joseph Rinde joined the Tymnet group and began porting the Supervisor code to the 32-bit Interdata 7/32, as the 8/32 was not yet ready. In 1973, the 8/32 became available, but the performance was disappointing and a crash-effort was made to develop a machine that could run Rinde's Supervisor. In 1974, a second, more efficient version of the Supervisor software became operational. The new Tymnet "Engine" software was used on both the Supervisor machines and on the nodes. After the migration to the Tymnet Engine, they started developing Tymnet accounting and other support software on the PDP-10. Tymshare sold the Tymnet network software to TRW, who created their own private network, TRWNET.
524766
wiki20220301en020_105705
Tymnet
Tymes and Rinde then developed "Tymnet II". Tymnet II ran in parallel with the original network, which continued to run on the Varian machines until it was phased out over a period of several years. Tymnet II's different method of constructing virtual circuits allowed for much better scalability. In 1996, the third and final version of the Supervisor was written in C for a Sparc multiprocessor work station by Tymes and Romolo Raffo. Node code software was ported from the Tymnet Engine to a Sparc platform by Bill Soley. Up to 10 old-style Tymnet Engines were replaced by a single Sparc node in the network switching centers. Tymnet, Inc. spun off
Tymnet. Tymes and Rinde then developed "Tymnet II". Tymnet II ran in parallel with the original network, which continued to run on the Varian machines until it was phased out over a period of several years. Tymnet II's different method of constructing virtual circuits allowed for much better scalability. In 1996, the third and final version of the Supervisor was written in C for a Sparc multiprocessor work station by Tymes and Romolo Raffo. Node code software was ported from the Tymnet Engine to a Sparc platform by Bill Soley. Up to 10 old-style Tymnet Engines were replaced by a single Sparc node in the network switching centers. Tymnet, Inc. spun off
524766
wiki20220301en020_105706
Tymnet
Tymnet, Inc. spun off In about 1979, Tymnet Inc. was spun off from Tymshare Inc. to continue administration and operation of the Tymnet network and its VAN services. The network continued to grow, and customers who owned their own host computers and wanted access to them from remote sites became interested in connecting their computers to the network. This led to the foundation of Tymnet as a wholly owned subsidiary of Tymshare to run a public network as a common carrier within the United States. This allowed users to connect their host computers and terminals to the network, and use the computers from remote sites or sell time on their computers to other users of the network, with Tymnet charging them for the use of the network. Sold to McDonnell Douglas McDonnell Douglas Tymshare
Tymnet. Tymnet, Inc. spun off In about 1979, Tymnet Inc. was spun off from Tymshare Inc. to continue administration and operation of the Tymnet network and its VAN services. The network continued to grow, and customers who owned their own host computers and wanted access to them from remote sites became interested in connecting their computers to the network. This led to the foundation of Tymnet as a wholly owned subsidiary of Tymshare to run a public network as a common carrier within the United States. This allowed users to connect their host computers and terminals to the network, and use the computers from remote sites or sell time on their computers to other users of the network, with Tymnet charging them for the use of the network. Sold to McDonnell Douglas McDonnell Douglas Tymshare
524766
wiki20220301en020_105707
Tymnet
Sold to McDonnell Douglas McDonnell Douglas Tymshare In 1984 Tymnet was bought by the McDonnell Douglas Corporation as part of the acquisition of Tymshare. The company was renamed McDonnell Douglas Tymshare, and began a major reorganization. A year later, McDonnell Douglas (MD) split Tymshare into several separate operating companies: MD Network Systems Company, MD Field Service Company, MD RCS, MD "xxx" and many more. (This is sometimes referred to the Alphabet Soup phase of the company). At this point, Tymnet had outlived its parent company Tymshare.
Tymnet. Sold to McDonnell Douglas McDonnell Douglas Tymshare In 1984 Tymnet was bought by the McDonnell Douglas Corporation as part of the acquisition of Tymshare. The company was renamed McDonnell Douglas Tymshare, and began a major reorganization. A year later, McDonnell Douglas (MD) split Tymshare into several separate operating companies: MD Network Systems Company, MD Field Service Company, MD RCS, MD "xxx" and many more. (This is sometimes referred to the Alphabet Soup phase of the company). At this point, Tymnet had outlived its parent company Tymshare.
524766
wiki20220301en020_105708
Tymnet
McDonnell Douglas acquired Microdata and created MD Information Systems Group (MDISC), expecting to turn Microdata's desktop and server systems along with Tymshare's servers and Tymnet data network into a major player in the Information Services market. Microdata's systems were integrated into many parts of McDonnell Douglas, but Tymnet never was. MDC really did not seem to understand the telecommunications market. After five years, peace was breaking out in many places in the world and McDonnell Douglas sold off MDNSC and MDFSC at a profit for much needed cash.
Tymnet. McDonnell Douglas acquired Microdata and created MD Information Systems Group (MDISC), expecting to turn Microdata's desktop and server systems along with Tymshare's servers and Tymnet data network into a major player in the Information Services market. Microdata's systems were integrated into many parts of McDonnell Douglas, but Tymnet never was. MDC really did not seem to understand the telecommunications market. After five years, peace was breaking out in many places in the world and McDonnell Douglas sold off MDNSC and MDFSC at a profit for much needed cash.
524766
wiki20220301en020_105709
Tymnet
Earlier, in 1986, the Canadian Radio-television and Telecommunications Commission (CRTC) liberalized the interconnection rules in the provinces it then regulated (Ontario, Quebec and British Columbia) and this allowed McDonnell Douglas to expand the network into select Canadian cities. The Canadian operation was part of McDonnell Douglas Computer Systems Company (MDCSC) as this was the only MDxxx company operating in Canada. MDCSC hired David Kingsland to spearhead this expansion into Canada. Sold to British Telecom BT Tymnet, BT North America, BTNA
Tymnet. Earlier, in 1986, the Canadian Radio-television and Telecommunications Commission (CRTC) liberalized the interconnection rules in the provinces it then regulated (Ontario, Quebec and British Columbia) and this allowed McDonnell Douglas to expand the network into select Canadian cities. The Canadian operation was part of McDonnell Douglas Computer Systems Company (MDCSC) as this was the only MDxxx company operating in Canada. MDCSC hired David Kingsland to spearhead this expansion into Canada. Sold to British Telecom BT Tymnet, BT North America, BTNA
524766
wiki20220301en020_105710
Tymnet
Sold to British Telecom BT Tymnet, BT North America, BTNA On July 30, 1989 at the Marriott Hotel in Santa Clara, it was announced that British Telecom was purchasing McDonnell Douglas Network Systems Company, and McDonnell Douglas Field Service Company was being spun off as a start-up called NovaDyne. British Telecom (BT) wanted to expand and the acquisition of Tymnet, which already a worldwide data network, was projected to help to achieve that goal. On November 17, 1989 MDNSC officially became BT Tymnet with its parochial U.S. headquarters in San Jose, California. BT brought with it the idea of continuous development with teams in America, Europe, and Asia-pacific all working together on the same projects. BT renamed the Tymnet services, Global Network Services (GNS).
Tymnet. Sold to British Telecom BT Tymnet, BT North America, BTNA On July 30, 1989 at the Marriott Hotel in Santa Clara, it was announced that British Telecom was purchasing McDonnell Douglas Network Systems Company, and McDonnell Douglas Field Service Company was being spun off as a start-up called NovaDyne. British Telecom (BT) wanted to expand and the acquisition of Tymnet, which already a worldwide data network, was projected to help to achieve that goal. On November 17, 1989 MDNSC officially became BT Tymnet with its parochial U.S. headquarters in San Jose, California. BT brought with it the idea of continuous development with teams in America, Europe, and Asia-pacific all working together on the same projects. BT renamed the Tymnet services, Global Network Services (GNS).
524766
wiki20220301en020_105711
Tymnet
British Telecom brought new life to the company with development of hardware and software for the Tymnet data network using contacts BT already had with telecommunication hardware vendors. There was a trial of "next-generation" nodes scattered throughout the network, called "TURBO engine nodes" based on the Motorola 68000 family. In the mid to late 1980s, serious node-code development was migrated from the PDP-10s to UNIX. Sun-3 (based on the Motorola 68000) and later Sun-4 (SPARC based) workstations and servers were purchased from Sun Microsystems, though the majority of PDP-10s were still around in the early '90s for legacy code, as well as documentation storage. Eventually, all of the code development trees were on the Sun-4s, and the development tools (NAD, etc.) had been ported to SunOS.
Tymnet. British Telecom brought new life to the company with development of hardware and software for the Tymnet data network using contacts BT already had with telecommunication hardware vendors. There was a trial of "next-generation" nodes scattered throughout the network, called "TURBO engine nodes" based on the Motorola 68000 family. In the mid to late 1980s, serious node-code development was migrated from the PDP-10s to UNIX. Sun-3 (based on the Motorola 68000) and later Sun-4 (SPARC based) workstations and servers were purchased from Sun Microsystems, though the majority of PDP-10s were still around in the early '90s for legacy code, as well as documentation storage. Eventually, all of the code development trees were on the Sun-4s, and the development tools (NAD, etc.) had been ported to SunOS.
524766
wiki20220301en020_105712
Tymnet
Another project begun a few months before the BT purchase was to migrate the Tymnet code repository from the PDP-10s to Sun systems. The new servers were dubbed the Code Generation Systems or CGS. They were initially six Sun-3 servers upgraded eventually to two Sun-4/690 servers for redundancy. A second pair of servers for catastrophic failover were also installed in Malvern, PA and later moved to Norristown, PA as part of later site consolidation efforts. After the migration, there was code for more than 6000 nodes and 38,000 customer interfaces. Tymnet was still growing, and at several times reached its peak capacity when some of its customers held network intensive events. One of these of note was a live, on-line presentation and chat on America On-Line (AOL) with Michael Jackson. Tymnet usage statistics showed AOL's call capacity was greater than its maximum volume for the duration of the event. Sold to MCI, Concert MCI, NewCo, Concert
Tymnet. Another project begun a few months before the BT purchase was to migrate the Tymnet code repository from the PDP-10s to Sun systems. The new servers were dubbed the Code Generation Systems or CGS. They were initially six Sun-3 servers upgraded eventually to two Sun-4/690 servers for redundancy. A second pair of servers for catastrophic failover were also installed in Malvern, PA and later moved to Norristown, PA as part of later site consolidation efforts. After the migration, there was code for more than 6000 nodes and 38,000 customer interfaces. Tymnet was still growing, and at several times reached its peak capacity when some of its customers held network intensive events. One of these of note was a live, on-line presentation and chat on America On-Line (AOL) with Michael Jackson. Tymnet usage statistics showed AOL's call capacity was greater than its maximum volume for the duration of the event. Sold to MCI, Concert MCI, NewCo, Concert
524766
wiki20220301en020_105713
Tymnet
Sold to MCI, Concert MCI, NewCo, Concert In 1993 British Telecom (BT) and MCI Communications (MCI) negotiated what they called the "Deal of the Century", where MCI would take ownership of the US-based portions of Tymnet and they would create a 50/50 joint venture called "Concert". (The joint venture was called "NewCo" for more than a year while they decided on a name.) Concert was also aligned with another acquisition of BT, called Syncordia which was headquartered in Atlanta, Ga. Tymnet was then referred to as: The Packet network, the BT/MCI network and Concert Packet-switching Services (CPS). As MCI cut away at Tymnet, expecting it to die, it became a cash cow that just wouldn't go away. In May 1994, there were still three DEC KL-10s under TYMCOM-X. At this time, the network had approximately 5000 nodes in 30 foreign countries. A variety of protocols can be run over a single packet-switching-network, and Tymnet's most-used protocols were X.25, asynchronous (ATI/AHI), SNA.
Tymnet. Sold to MCI, Concert MCI, NewCo, Concert In 1993 British Telecom (BT) and MCI Communications (MCI) negotiated what they called the "Deal of the Century", where MCI would take ownership of the US-based portions of Tymnet and they would create a 50/50 joint venture called "Concert". (The joint venture was called "NewCo" for more than a year while they decided on a name.) Concert was also aligned with another acquisition of BT, called Syncordia which was headquartered in Atlanta, Ga. Tymnet was then referred to as: The Packet network, the BT/MCI network and Concert Packet-switching Services (CPS). As MCI cut away at Tymnet, expecting it to die, it became a cash cow that just wouldn't go away. In May 1994, there were still three DEC KL-10s under TYMCOM-X. At this time, the network had approximately 5000 nodes in 30 foreign countries. A variety of protocols can be run over a single packet-switching-network, and Tymnet's most-used protocols were X.25, asynchronous (ATI/AHI), SNA.
524766
wiki20220301en020_105714
Tymnet
BT and Concert also continued to develop the network, and after the failure of the "Turbo nodes" to take off, decided to have an outside company add Tymnet protocols to existing hardware used in their frame-relay network. Telematics International developed a subset of the Tymnet protocols to run on their ACP/PCP nodes. The Telematics nodes were connected in a mesh network via Frame-relay and appeared to Tymnet as super-nodes that were directly connected to as many as 44 other super-nodes interconnecting most of Europe, Asia and the Americas as a high-speed-data network. MCI took a different direction and looked to migrate the network protocols to run over TCP/IP and use Sun Microsystems SPARC technology. The supervisor technology was rewritten in C to run as standard UNIX applications under Sun's Solaris operating system. Funding for this project was at a minimum but the Tymnet engineers believed it was a superior method and proceeded anyway.
Tymnet. BT and Concert also continued to develop the network, and after the failure of the "Turbo nodes" to take off, decided to have an outside company add Tymnet protocols to existing hardware used in their frame-relay network. Telematics International developed a subset of the Tymnet protocols to run on their ACP/PCP nodes. The Telematics nodes were connected in a mesh network via Frame-relay and appeared to Tymnet as super-nodes that were directly connected to as many as 44 other super-nodes interconnecting most of Europe, Asia and the Americas as a high-speed-data network. MCI took a different direction and looked to migrate the network protocols to run over TCP/IP and use Sun Microsystems SPARC technology. The supervisor technology was rewritten in C to run as standard UNIX applications under Sun's Solaris operating system. Funding for this project was at a minimum but the Tymnet engineers believed it was a superior method and proceeded anyway.
524766
wiki20220301en020_105715
Tymnet
Times were changing and the Internet and World Wide Web were becoming a practical and even important part of corporate and personal life. Tymnet technology needed improvements to keep pace with TCP/IP and other internet protocols. Both BT and MCI decided not to compete with the Internet, but to convert their customer base to IP based networks and technologies. However, the Tymnet network was still bringing in much cash (in some cases more than current IP-based services), so both BT and MCI needed to keep their customers happy.
Tymnet. Times were changing and the Internet and World Wide Web were becoming a practical and even important part of corporate and personal life. Tymnet technology needed improvements to keep pace with TCP/IP and other internet protocols. Both BT and MCI decided not to compete with the Internet, but to convert their customer base to IP based networks and technologies. However, the Tymnet network was still bringing in much cash (in some cases more than current IP-based services), so both BT and MCI needed to keep their customers happy.
524766
wiki20220301en020_105716
Tymnet
MCI, MCI Worldcom, Worldcom vs. BT, Concert, AT&T In 1997 talks were underway for British Telecom (BT) to acquire MCI. The deal fell through, and in September, 1998 MCI was acquired by WorldCom after they made a better offer for the company. Actually, the Worldcom offer was nearly identical to the BT offer, but where BT planned to buy out MCI shares of stock, WorldCom offered a stock-swap which was more attractive to the stockholders. Worldcom took control in September 1998 and dissolved the BT/MCI alliance as of October 15, 1998. Concert - headquarters in Reston, Va. With the alliance gone, BT and MCI/Worldcom began the process of unraveling and separating their extensive voice and data communications systems.
Tymnet. MCI, MCI Worldcom, Worldcom vs. BT, Concert, AT&T In 1997 talks were underway for British Telecom (BT) to acquire MCI. The deal fell through, and in September, 1998 MCI was acquired by WorldCom after they made a better offer for the company. Actually, the Worldcom offer was nearly identical to the BT offer, but where BT planned to buy out MCI shares of stock, WorldCom offered a stock-swap which was more attractive to the stockholders. Worldcom took control in September 1998 and dissolved the BT/MCI alliance as of October 15, 1998. Concert - headquarters in Reston, Va. With the alliance gone, BT and MCI/Worldcom began the process of unraveling and separating their extensive voice and data communications systems.
524766
wiki20220301en020_105717
Tymnet
Concert - headquarters in Reston, Va. With the alliance gone, BT and MCI/Worldcom began the process of unraveling and separating their extensive voice and data communications systems. Concert created Project Leonardo to separate the BT and MCI/Worldcom voice and data networks. At times over the next five years, advancements were made or stalled due to BT and MCI management negotiating and renegotiating the terms of their contractual obligations to each other made during the alliance. At times, things came to a standstill, or decisions made were reversed, and some reversed again at a later time. Parts of the project were to migrate customers from X.25 to IP based networks, while others created a duplicate set of services so that both Concert and MCI could separately continue to run and manage their own portions of the network. Accounting data for network usage was also shared by the two companies and had to be separated before clients could be billed properly.
Tymnet. Concert - headquarters in Reston, Va. With the alliance gone, BT and MCI/Worldcom began the process of unraveling and separating their extensive voice and data communications systems. Concert created Project Leonardo to separate the BT and MCI/Worldcom voice and data networks. At times over the next five years, advancements were made or stalled due to BT and MCI management negotiating and renegotiating the terms of their contractual obligations to each other made during the alliance. At times, things came to a standstill, or decisions made were reversed, and some reversed again at a later time. Parts of the project were to migrate customers from X.25 to IP based networks, while others created a duplicate set of services so that both Concert and MCI could separately continue to run and manage their own portions of the network. Accounting data for network usage was also shared by the two companies and had to be separated before clients could be billed properly.
524766
wiki20220301en020_105718
Tymnet
Concert - headquarters in Atlanta, Ga.
Tymnet. Concert - headquarters in Atlanta, Ga.
524766
wiki20220301en020_105719
Tymnet
In 2000 BT then went searching for another alliance, and created a new "Concert" alliance between BT and AT&T Corporation, moving the headquarters to Atlanta, Georgia. This alliance did not help the negotiations between BT and MCI Worldcom as their partners from MCI and AT&T were corporate enemies. For Tymnet, the data network portion of the split, and the "CPS Leonardo" project, the split was never fully realized. Instead, MCI Worldcom completed their migration of services from Tymnet to IP based services in March 2003 and disconnected their supervisor nodes and their portion of the network on March 31, 2003. British Telecom continued to run the network using their own supervisor and other utility nodes until February 2004 when their last customer was able to move all of its customers to other access services. BT and AT&T dissolved their Concert alliance on September 30, 2003 and the remaining BT assets were combined with BTNA assets into BT Americas, Inc. Sometime in early March
Tymnet. In 2000 BT then went searching for another alliance, and created a new "Concert" alliance between BT and AT&T Corporation, moving the headquarters to Atlanta, Georgia. This alliance did not help the negotiations between BT and MCI Worldcom as their partners from MCI and AT&T were corporate enemies. For Tymnet, the data network portion of the split, and the "CPS Leonardo" project, the split was never fully realized. Instead, MCI Worldcom completed their migration of services from Tymnet to IP based services in March 2003 and disconnected their supervisor nodes and their portion of the network on March 31, 2003. British Telecom continued to run the network using their own supervisor and other utility nodes until February 2004 when their last customer was able to move all of its customers to other access services. BT and AT&T dissolved their Concert alliance on September 30, 2003 and the remaining BT assets were combined with BTNA assets into BT Americas, Inc. Sometime in early March
524766
wiki20220301en020_105720
Tymnet
to other access services. BT and AT&T dissolved their Concert alliance on September 30, 2003 and the remaining BT assets were combined with BTNA assets into BT Americas, Inc. Sometime in early March 2004, without ceremony, BT Americas disconnected the last two remaining Tymnet supervisors from the network, effectively shutting it down.
Tymnet. to other access services. BT and AT&T dissolved their Concert alliance on September 30, 2003 and the remaining BT assets were combined with BTNA assets into BT Americas, Inc. Sometime in early March 2004, without ceremony, BT Americas disconnected the last two remaining Tymnet supervisors from the network, effectively shutting it down.
524766
wiki20220301en020_105721
Tymnet
Worldcom bankruptcy Worldcom executives were involved in a financial scandal. In June 2002, Worldcom admitted to nearly 4 billion dollars of incorrect accounting. The scandal resulted in the CEO, Bernard Ebbers, being ousted and later brought up on federal charges for conspiracy and securities fraud. The scandal sent the stock price down to ten cents per share. A month after the revelation of accounting "mishaps", Worldcom filed for bankruptcy. MCI name revived and sold to Verizon Worldcom came out of bankruptcy renamed as "MCI" in April 2004. In less than a year, the remains of MCI was sold for $6.7B bid to what is today known as Verizon Business, a division of Verizon. Verizon had been formed in 2000 when Bell Atlantic, one of the Regional Bell Operating Companies, merged with GTE. Prior to its transformation into Verizon, Bell Atlantic had merged with another Regional Bell Operating Company, NYNEX, in 1997.
Tymnet. Worldcom bankruptcy Worldcom executives were involved in a financial scandal. In June 2002, Worldcom admitted to nearly 4 billion dollars of incorrect accounting. The scandal resulted in the CEO, Bernard Ebbers, being ousted and later brought up on federal charges for conspiracy and securities fraud. The scandal sent the stock price down to ten cents per share. A month after the revelation of accounting "mishaps", Worldcom filed for bankruptcy. MCI name revived and sold to Verizon Worldcom came out of bankruptcy renamed as "MCI" in April 2004. In less than a year, the remains of MCI was sold for $6.7B bid to what is today known as Verizon Business, a division of Verizon. Verizon had been formed in 2000 when Bell Atlantic, one of the Regional Bell Operating Companies, merged with GTE. Prior to its transformation into Verizon, Bell Atlantic had merged with another Regional Bell Operating Company, NYNEX, in 1997.
524766
wiki20220301en020_105722
Tymnet
AT&T sold to SBC On January 31, 2005, SBC Communications announced that it would purchase AT&T Corp. for more than $16 billion. Shortly thereafter the name was changed to AT&T Inc. to distinguish itself from AT&T Corp. Electronic Data Interchange (EDI & EDI*Net) Tymshare EDI, MD Payment Systems Company, BTNA/MCI EDI*Net Services Tymshare was one of the pioneers in the EDI field. Under McDonnell Douglas, the Payment Systems Company continued that legacy and maintained its own EDI*Net network monitoring and support group.
Tymnet. AT&T sold to SBC On January 31, 2005, SBC Communications announced that it would purchase AT&T Corp. for more than $16 billion. Shortly thereafter the name was changed to AT&T Inc. to distinguish itself from AT&T Corp. Electronic Data Interchange (EDI & EDI*Net) Tymshare EDI, MD Payment Systems Company, BTNA/MCI EDI*Net Services Tymshare was one of the pioneers in the EDI field. Under McDonnell Douglas, the Payment Systems Company continued that legacy and maintained its own EDI*Net network monitoring and support group.
524766
wiki20220301en020_105723
Tymnet
EDI*Net used a fault-tolerant Tandem NonStop computer with a second synchronized remote disaster NonStop computer over 100 miles apart. Mirrors of each other, and maintaining uptimes over 99.994%, they were each connected to a high speed data links using Tymnet as the connection and translation medium. Tymshare developed a bi-sync modem interface (HSA), a translation module to translate between EBCDIC and ASCII (BBXS), and a highly customized X.25 module (XCOM). EDI*Net used these interfaces on the Tandems. EDI*Net supported & contributed to many EDI standards, with the United Nations' EDIFACT and ANSI X12 dominating. As a store-and-forward service, EDI*Net supported multiple delivery protocols besides X.25 and BiSync, including FTPS, SMTPS and ZModem, and allowed the enveloping structure of supported EDI standards to extend into X.400 and SMTP envelopes.
Tymnet. EDI*Net used a fault-tolerant Tandem NonStop computer with a second synchronized remote disaster NonStop computer over 100 miles apart. Mirrors of each other, and maintaining uptimes over 99.994%, they were each connected to a high speed data links using Tymnet as the connection and translation medium. Tymshare developed a bi-sync modem interface (HSA), a translation module to translate between EBCDIC and ASCII (BBXS), and a highly customized X.25 module (XCOM). EDI*Net used these interfaces on the Tandems. EDI*Net supported & contributed to many EDI standards, with the United Nations' EDIFACT and ANSI X12 dominating. As a store-and-forward service, EDI*Net supported multiple delivery protocols besides X.25 and BiSync, including FTPS, SMTPS and ZModem, and allowed the enveloping structure of supported EDI standards to extend into X.400 and SMTP envelopes.
524766
wiki20220301en020_105724
Tymnet
Developed to utilize X.25 (XCOM) and BiSync (BSC), there was no TCP/IP equivalent service within Tymnet. To continue use of this service after the shutdown of Tymnet, a solution was selected. A special version of Tymnet Engine node code which allows nodes and interfaces to communicate with one another and the rest of the network was created. Instead of relying on the "supervisor" to validate calls, a table of permitted connections was defined per customer to allow an incoming call to be made from the HSA interface to the BBXS interface to the XCOM interface and on to the Tandem computer. In effect, a "Tymnet Island" consisting of a single Tymnet node that accepted calls for a pre-determined list of clients was utilized by EDI*Net. No supervisor needed. These islands of Tymnet have not only outlived the parent company, Tymshare, and the operations company, Tymnet, but also the Tymnet Network itself. As of 2008, these Tymnet Island nodes are still running and doing their jobs.
Tymnet. Developed to utilize X.25 (XCOM) and BiSync (BSC), there was no TCP/IP equivalent service within Tymnet. To continue use of this service after the shutdown of Tymnet, a solution was selected. A special version of Tymnet Engine node code which allows nodes and interfaces to communicate with one another and the rest of the network was created. Instead of relying on the "supervisor" to validate calls, a table of permitted connections was defined per customer to allow an incoming call to be made from the HSA interface to the BBXS interface to the XCOM interface and on to the Tandem computer. In effect, a "Tymnet Island" consisting of a single Tymnet node that accepted calls for a pre-determined list of clients was utilized by EDI*Net. No supervisor needed. These islands of Tymnet have not only outlived the parent company, Tymshare, and the operations company, Tymnet, but also the Tymnet Network itself. As of 2008, these Tymnet Island nodes are still running and doing their jobs.
524766
wiki20220301en020_105725
Tymnet
Operations Organization In operation, Tymshare's Data Networks Division was responsible for the development and maintenance of the network and Tymnet was responsible for the administration, provisioning and monitoring of the network. Each company had their own software development staff and a line was drawn to separate what each group could do. Tymshare development engineers wrote all the code which ran in the network, and the Tymnet staff wrote code running on host computers connected to the network. It is for this reason, that many of the Tymnet projects ran on the Digital Equipment Corporation DECSystem-10 computers that Tymshare offered as timesharing hosts for their customers. Tymnet operations formed a strategic alliance with the Tymshare PDP-10 TYMCOM-X operating systems group to assist them in developing new network management tools. Trouble tracking
Tymnet. Operations Organization In operation, Tymshare's Data Networks Division was responsible for the development and maintenance of the network and Tymnet was responsible for the administration, provisioning and monitoring of the network. Each company had their own software development staff and a line was drawn to separate what each group could do. Tymshare development engineers wrote all the code which ran in the network, and the Tymnet staff wrote code running on host computers connected to the network. It is for this reason, that many of the Tymnet projects ran on the Digital Equipment Corporation DECSystem-10 computers that Tymshare offered as timesharing hosts for their customers. Tymnet operations formed a strategic alliance with the Tymshare PDP-10 TYMCOM-X operating systems group to assist them in developing new network management tools. Trouble tracking
524766
wiki20220301en020_105726
Tymnet
Trouble tracking Origins From its earliest days, Tymnet had an on-line and real time network trouble reporting tool called the Consolidator. That, along with the network node interrogation capabilities (known as Snap or Snapshot), provided unique and real time operation of the network. However, trouble reports were initially tracked on a traditional paper ticket system. This was until Bill Scheible, a manager at Tymnet, wrote a small FORTRAN IV program to maintain a list of problem reports and track their status in a System 1022 database (a hierarchical database system for TOPS-10 published by Software House). The program was called PAPER after the old manual way of managing trouble tickets. The program grew as features were added to handle customer information, call-back contact information, escalation procedures, and outage statistics.
Tymnet. Trouble tracking Origins From its earliest days, Tymnet had an on-line and real time network trouble reporting tool called the Consolidator. That, along with the network node interrogation capabilities (known as Snap or Snapshot), provided unique and real time operation of the network. However, trouble reports were initially tracked on a traditional paper ticket system. This was until Bill Scheible, a manager at Tymnet, wrote a small FORTRAN IV program to maintain a list of problem reports and track their status in a System 1022 database (a hierarchical database system for TOPS-10 published by Software House). The program was called PAPER after the old manual way of managing trouble tickets. The program grew as features were added to handle customer information, call-back contact information, escalation procedures, and outage statistics.
524766