If necessary, a Guid can be explicitly specified instead. This was due in part to continued improvements in the B, airline deregulation in the U. Boeing realized it needed to fill this gap quickly or risk losing that portion of the airliner market entirely.
But Sutter had a different approach: Instead of a stretch, how about a "chop? His notion was to take the existing design and shorten it, thus reducing its weight and optimizing it for both transcontinental and international flight. Thus was born what was originally called the SB Short Body concept. The biggest problem Sutter and his crew faced was matching the fuel economy of the competition's tri-jets.
This would place one engine under each wing and one engine in the tail, much like the other tri-jets. However, this proved to be too difficult an engineering challenge, and would have required a time consuming and costly redesign of the wing. In the midst of this redesign process, Pan Am announced it was looking for an aircraft to fly "long and thin" routes that were too lengthy for the existing DC and L, but for which a standard offered too much capacity.
Douglas and Lockheed were already working on long range variants of their wide bodies to fill this niche. It was decided the best option for Boeing was to stick with the four-engine design and seek improved fuel economy by saving weight in other areas of the plane. By , the model had been renamed the SP Special Performance and was approved by the Boeing board in September of that year. Within weeks, Pan Am placed an order for ten aircraft, with options for another 15, with deliveries to begin in Boeing estimated that a market existed for aircraft, and the financial break-even point would be achieved with 45 aircraft.
The final design was approved, with the SP being 48 feet and four inches shorter than a full size comparable in length to today's , and carrying in the neighbourhood of passengers.
This resulted in an initial design weight reduction of 11, pounds, with fuselage sections being removed from in front of and behind the wings, and a redesigned center section.
The under-wing "canoes" which housed the flap mechanisms on full-size s were eliminated entirely on the SP. In all, an empty SP weighed roughly 45, pounds less than an empty Other visible differences were ten more feet of span in the horizontal stabilizer, a slightly taller vertical stabilizer, a double hinged rudder, and a tapering of the upper fuselage into the empenage. The redesigned center fuselage section also necessitated a redesign of the wing fillets to improve airflow.
The first SP msn was rolled out May 19, , and made its maiden flight less than two months later on July 4, ten days ahead of schedule. Jack Waddell, who flew the first test flight in , also flew the maiden SP flight, performing both a stall and a max speed Mach 0.
With a much lighter airframe, yet with the same power as a full-size , the SP exceeded many of its design estimates, and was proving to be a very strong performer. On November 12, , Boeing decided to showcase that performance, and flew the fourth SP msn non-stop from New York to Tokyo a distance of 6, miles with passengers on board in 13 hours, 33 minutes, setting a new world record.
After landing, the aircraft still had over 30, pounds of fuel remaining! The Boeing SP was granted a supplemental type certificate on February 4, A month later, on March 5th, the record setting SP, now name "Clipper Freedom" msn , was delivered to Pan Am, with revenue service commencing in April. The SP continued to be an exceptional performer, setting multiple distance and speed records.
If your Visual Studio Solution mixes generated and manually created project files, you can set explicit references to them. By default, a Guid for a project will be generated automatically. If necessary, a Guid can be explicitly specified instead. DefaultLanguage - String - Optional. Set the application environment property. Various options can be specified to control how each configuration is controlled. If the option is defined at the VCXProject level it will be applied to all configurations.
If defined at the. ProjectConfig level, it will be used for the given project configuration. Options can be specified at both levels, allowing for individual ProjectConfigs to override as needed. It can be convenient to take advantage of Visual Studio's runtime macro substitution to avoid having to manually specify this for every configuration.