View allAll Photos Tagged Payloader
S86-25254 (January 1986) --- Payload specialists in training for STS-51L take a break in shuttle emergency egress training at the Johnson Space Center's (JSC) Shuttle Mock-up and Integration Laboratory. Left to right are Gregory Jarvis of Hughes, Sharon Christa McAuliffe and Barbara Morgan of the Teacher-in-Space Project. McAuliffe was selected as NASA's first citizen observer in the Space Shuttle Program and Morgan was named her backup. The photo was taken by Keith Meyers of the New York Times.
EDITOR'S NOTE: The STS-51L crew members lost their lives in the space shuttle Challenger accident moments after launch on Jan. 28, 1986 from the Kennedy Space Center (KSC). Photo credit: NASA
CAPSTONE spacecraft, built by Terran Orbital and owned and operated by Advanced Space, being prepared for payload integration at Rocket Lab Launch Complex 1
Inside the Payload Hazardous Servicing Facility at the NASA's Kennedy Space Center in Florida, the first of two solar panels is being deployed on the agency's Transiting Exoplanet Survey Satellite (TESS). The satellite is scheduled to launch atop a SpaceX Falcon 9 rocket from Space Launch Complex 40 at Cape Canaveral Air Force Station. TESS is the next step in NASA's search for planets outside our solar system, known as exoplanets. TESS is a NASA Astrophysics Explorer mission led and operated by MIT in Cambridge, Massachusetts, and managed by NASA’s Goddard Space Flight Center in Greenbelt, Maryland. Dr. George Ricker of MIT’s Kavli Institute for Astrophysics and Space Research serves as principal investigator for the mission. Additional partners include Orbital ATK, NASA’s Ames Research Center, the Harvard-Smithsonian Center for Astrophysics and the Space Telescope Science Institute. More than a dozen universities, research institutes and observatories worldwide are participants in the mission. NASA’s Launch Services Program is responsible for launch management. Photo credit: NASA/Leif Heimbold
New Iteration - Grey Hawk - Mach 8-10 - 7th / 8th Gen Hypersonic Super Fighter Aircraft, IO Aircraft www.ioaircraft.com
New peek, very little is posted or public. Grey Hawk - Mach 8-10 Hypersonic 7th/8th Gen Super Fighter. This is not a graphics design, but ready to be built this moment. Heavy CFD, Design Work, Systems, etc.
All technologies developed and refined. Can out maneuver an F22 or SU-35 all day long subsonically, and no missile on earth could catch it. Lots of details omitted intentionally, but even internal payload capacity is double the F-22 Raptor. - www.ioaircraft.com/hypersonic.php
Length: 60'
Span: 30'
Engines: 2 U-TBCC (Unified Turbine Based Combined Cycle)
2 360° Thrust Vectoring Center Turbines
Fuel: Kero / Hydrogen
Payload: Up to 4 2,000 LBS JDAM's Internally
Up to 6 2,000 LBS JDAM's Externally
Range: 5,000nm + Aerial Refueling Capable
www.ioaircraft.com/hypersonic.php
-----------------------------
hypersonic fighter, hypersonic fighter plane, hawc, tgv, tactical glide vehicle, hypersonic commercial aircraft, hypersonic commercial plane, hypersonic aircraft, hypersonic plane, hypersonic airline, tbcc, glide breaker, fighter plane, hypersonic fighter, boeing phantom express, phantom works, boeing phantom works, lockheed skunk works, hypersonic weapon, hypersonic missile, scramjet engineering, scramjet physics, boost glide, tactical glide vehicle, space plane, scramjet, turbine based combined cycle, ramjet, dual mode ramjet, defense science, missile defense agency, aerospike, hydrogen aircraft, airlines, military, physics, airline, aerion supersonic, aerion, spike aerospace, boom supersonic, , darpa, onr, navair, afrl, air force research lab, office of naval research, defense advanced research project agency, afosr, socom, arl, army future command, mda, missile defense agenci, dia, defense intelligence agency, Air Force Office of Scientific Research,
-----------------------------
Unified Turbine Based Combined Cycle. Current technologies and what Lockheed is trying to force on the Dept of Defense, for that low speed Mach 5 plane DOD gave them $1 billion to build and would disintegrate above Mach 5, is TBCC. 2 separate propulsion systems in the same airframe, which requires TWICE the airframe space to use.
Unified Turbine Based Combined Cycle is 1 propulsion system cutting that airframe deficit in half, and also able to operate above Mach 10 up to Mach 15 in atmosphere, and a simple nozzle modification allows for outside atmosphere rocket mode, ie orbital capable.
Additionally, Reaction Engines maximum air breather mode is Mach 4.5, above that it will explode in flight from internal pressures are too high to operate. Thus, must switch to non air breather rocket mode to operate in atmosphere in hypersonic velocities. Which as a result, makes it not feasible for anything practical. It also takes an immense amount of fuel to function.
-------------
Advanced Additive Manufacturing for Hypersonic Aircraft
Utilizing new methods of fabrication and construction, make it possible to use additive manufacturing, dramatically reducing the time and costs of producing hypersonic platforms from missiles, aircraft, and space capable craft. Instead of aircraft being produced in piece, then bolted together; small platforms can be produced as a single unit and large platforms can be produces in large section and mated without bolting. These techniques include using exotic materials and advanced assembly processes, with an end result of streamlining the production costs and time for hypersonic aircraft; reducing months of assembly to weeks. Overall, this process greatly reduced the cost for producing hypersonic platforms. Even to such an extent that a Hellfire missile costs apx $100,000 but by utilizing our technologies, replacing it with a Mach 8-10 hypersonic missile of our physics/engineering and that missile would cost roughly $75,000 each delivered.
Materials used for these manufacturing processes are not disclosed, but overall, provides a foundation for extremely high stresses and thermodynamics, ideal for hypersonic platforms. This specific methodology and materials applications is many decades ahead of all known programs. Even to the extend of normalized space flight and re-entry, without concern of thermodynamic failure.
*Note, most entities that are experimenting with additive manufacturing for hypersonic aircraft, this makes it mainstream and standardized processes, which also applies for mass production.
What would normally be measured in years and perhaps a decade to go from drawing board to test flights, is reduced to singular months and ready for production within a year maximum.
Unified Turbine Based Combined Cycle (U-TBCC)
To date, the closest that NASA and industry have achieved for turbine based aircraft to fly at hypersonic velocities is by mounting a turbine into an aircraft and sharing the inlet with a scramjet or rocket based motor. Reaction Engines Sabre is not able to achieve hypersonic velocities and can only transition into a non air breathing rocket for beyond Mach 4.5
However, utilizing Unified Turbine Based Combine Cycle also known as U-TBCC, the two separate platforms are able to share a common inlet and the dual mode ramjet/scramjet is contained within the engine itself, which allows for a much smaller airframe footprint, thus engingeers are able to then design much higher performance aerial platforms for hypersonic flight, including the ability for constructing true single stage to orbit aircraft by utilizing a modification/version that allows for transition to outside atmosphere propulsion without any other propulsion platforms within the aircraft. By transitioning and developing aircraft to use Unified Turbine Based Combined Cycle, this propulsion system opens up new options to replace that airframe deficit for increased fuel capacity and/or payload.
Enhanced Dynamic Cavitation
Dramatically Increasing the efficiency of fuel air mixture for combustion processes at hypersonic velocities within scramjet propulsion platforms. The aspects of these processes are non disclosable.
Dynamic Scramjet Ignition Processes
For optimal scramjet ignition, a process known as Self Start is sought after, but in many cases if the platform becomes out of attitude, the scramjet will ignite. We have already solved this problem which as a result, a scramjet propulsion system can ignite at lower velocities, high velocities, at optimal attitude or not optimal attitude. It doesn't matter, it will ignite anyways at the proper point for maximum thrust capabilities at hypersonic velocities.
Hydrogen vs Kerosene Fuel Sources
Kerosene is an easy fuel to work with, and most western nations developing scramjet platforms use Kerosene for that fact. However, while kerosene has better thermal properties then Hydrogen, Hydrogen is a far superior fuel source in scramjet propulsion flight, do it having a much higher efficiency capability. Because of this aspect, in conjunction with our developments, it allows for a MUCH increased fuel to air mixture, combustion, thrust; and ability for higher speeds; instead of very low hypersonic velocities in the Mach 5-6 range. Instead, Mach 8-10 range, while we have begun developing hypersonic capabilities to exceed 15 in atmosphere within less then 5 years.
Conforming High Pressure Tank Technology for CNG and H2.
As most know in hypersonics, Hydrogen is a superior fuel source, but due to the storage abilities, can only be stored in cylinders thus much less fuel supply. Not anymore, we developed conforming high pressure storage technology for use in aerospace, automotive sectors, maritime, etc; which means any overall shape required for 8,000+ PSI CNG or Hydrogen. For hypersonic platforms, this means the ability to store a much larger volume of hydrogen vs cylinders.
As an example, X-43 flown by Nasa which flew at Mach 9.97. The fuel source was Hydrogen, which is extremely more volatile and combustible then kerosene (JP-7), via a cylinder in the main body. If it had used our technology, that entire section of the airframe would had been an 8,000 PSI H2 tank, which would had yielded 5-6 times the capacity. While the X-43 flew 11 seconds under power at Mach 9.97, at 6 times the fuel capacity would had yielded apx 66 seconds of fuel under power at Mach 9.97. If it had flew slower, around Mach 6, same principles applied would had yielded apx 500 seconds of fuel supply under power (slower speeds required less energy to maintain).
Enhanced Fuel Mixture During Shock Train Interaction
Normally, fuel injection is conducted at the correct insertion point within the shock train for maximum burn/combustion. Our methodologies differ, since almost half the fuel injection is conducted PRE shock train within the isolator, so at the point of isolator injection the fuel enhances the combustion process, which then requires less fuel injection to reach the same level of thrust capabilities.
Improved Bow Shock Interaction
Smoother interaction at hypersonic velocities and mitigating heat/stresses for beyond Mach 6 thermodynamics, which extraordinarily improves Type 3, 4, and 5 shock interaction.
6,000+ Fahrenheit Thermal Resistance
To date, the maximum thermal resistance was tested at AFRL in the spring of 2018, which resulted in a 3,200F thermal resistance for a short duration. This technology, allows for normalized hypersonic thermal resistance of 3,000-3,500F sustained, and up to 6,500F resistance for short endurance, ie 90 seconds or less. 10-20 minute resistance estimate approximately 4,500F +/- 200F.
*** This technology advancement also applies to Aerospike rocket engines, in which it is common for Aerospike's to exceed 4,500-5,000F temperatures, which results in the melting of the reversed bell housing. That melting no longer ocurrs, providing for stable combustion to ocurr for the entire flight envelope
Scramjet Propulsion Side Wall Cooling
With old technologies, side wall cooling is required for hypersonic flight and scramjet propulsion systems, otherwise the isolator and combustion regions of a scramjet would melt, even using advanced ablatives and ceramics, due to their inability to cope with very high temperatures. Using technology we have developed for very high thermodynamics and high stresses, side wall cooling is no longer required, thus removing that variable from the design process and focusing on improved ignition processes and increasing net thrust values.
Lower Threshold for Hypersonic Ignition
Active and adaptive flight dynamics, resulting in the ability for scramjet ignition at a much lower velocity, ie within ramjet envelope, between Mach 2-4, and seamless transition from supersonic to hypersonic flight, ie supersonic ramjet (scramjet). This active and dynamic aspect, has a wide variety of parameters for many flight dynamics, velocities, and altitudes; which means platforms no longer need to be engineered for specific altitude ranges or preset velocities, but those parameters can then be selected during launch configuration and are able to adapt actively in flight.
Dramatically Improved Maneuvering Capabilities at Hypersonic Velocities
Hypersonic vehicles, like their less technologically advanced brethren, use large actuator and the developers hope those controls surfaces do not disintegrate in flight. In reality, it is like rolling the dice, they may or may not survive, hence another reason why the attempt to keep velocities to Mach 6 or below. We have shrunken down control actuators while almost doubling torque and response capabilities specifically for hypersonic dynamics and extreme stresses involved, which makes it possible for maximum input authority for Mach 10 and beyond.
Paradigm Shift in Control Surface Methodologies, Increasing Control Authority (Internal Mechanical Applications)
To date, most control surfaces for hypersonic missile platforms still use fins, similar to lower speed conventional missiles, and some using ducted fins. This is mostly due to lack of comprehension of hypersonic velocities in their own favor. Instead, the body itself incorporates those control surfaces, greatly enhancing the airframe strength, opening up more space for hardware and fuel capacity; while simultaneously enhancing the platforms maneuvering capabilities.
A scramjet missile can then fly like conventional missile platforms, and not straight and level at high altitudes, losing velocity on it's decent trajectory to target. Another added benefit to this aspect, is the ability to extend range greatly, so if anyone elses hypersonic missile platform were developed for 400 mile range, falling out of the sky due to lack of glide capabilities; our platforms can easily reach 600+ miles, with minimal glide deceleration.
+++ DISCLAIMER +++
Nothing you see here is real, even though the conversion or the presented background story might be based historical facts. BEWARE!
Some background:
The Yakovlev Yak-38 (Russian: Яковлева Як-38; NATO reporting name: "Forger") was the Soviet Naval Aviation's first and only operational VTOL strike fighter aircraft, in addition to being its first operational carrier-based fixed-wing aircraft. It was developed specifically for and served almost exclusively on the Kiev-class aircraft carriers.
Some specimen of the initial variant were tested during the Soviet Union's intervention in Afghanistan. These trials revealed several weaknesses of the construction in the form of unacceptable hot and high capabilities as well as a low payload. A further development for the Soviet Navy was therefore decided in August 1981, the abilities of which were fixed in October 1982. Already in November 1982 the first flight experiments of the prototype, leading to the Yak-38M, took place. In mid-1983 the manufacturing tests were completed and the production release was granted.
Anyway, the Soviet Air Force also had interest in a VTOL attack aircraft, which could provide CAS duties in immediate front line theatres, complementing the new Suchoj Su-25 Frogfoot and various attack helicopter types - but the Yak-38 was outright rejected. The Frontal Aviation demanded a much better performance, a dedicated avionics suite for ground attack duties and a higher payload of at least 2.500 kg (5.500 lb) in VTOL mode, plus an internal gun, and 3.000 kg (6.600 lb) when operating in C/STOL mode at sea level and from semi-prepared airstrips. For its primary ground attack role, the machine was also to be armored against projectiles of up to 0.5” around the lower hull and against 20mm rounds in the cockpit section. Finally, the machine had to be, compared with the Yak-38, simplified and be more rugged in order to ease frontline service and endure survivability.
OKB Yakovlev accepted the challenge and dusted off studies that had been undertaken during the Yak-38’s design stage. One of these was the Yak-38L (for 'lift/cruise'), a design built around a single, modified the AL-21F turbojet with vectoring nozzles and no lift engines, which were just dead weight in normal flight. This route seemed to be the most promising option for the Frontal Aviation's demands, even though it would mean a severe re-construction of the airframe.
The new aircraft, internally referred to as 'Izdeliye 138', was based on the Yak-38 airframe, but adapted and literally built around a lift/cruise variant of the large Kuznetsov NK-32 low bypass turbofan engine (originally, with an afterburner, powering the late Tu-144 airliners and the Tu-160 bomber). This engine’s initial derivative, NK-32L-1, adapted for operation with four vectoring nozzles, had a dry thrust of roundabout 110 kN (25,000 lbf) – about 10% more than the Yak-38’s engine trio all together. And the massive engine bore potential for at least 10% more power for the service aircraft.
The overall layout differed considerably from the long and sleek Yak-38: in order to create enough space for the large turbofan stage and its bigger, fixed-configuration air intakes, the fuselage had to be widened behind the cockpit section and the wings' main spar was moved upwards, so that the wings were now shoulder-mounted. The overall arrangement was reminiscent of the successful Hawker Harrier, but differed in some details like the landing gear, which was a classic tricycle design.
Cold air from the NK-32L’s initial turbofan stage was ducted into vectoring nozzles at the forward fuselage flanks, just in front of the aircraft's center of gravity, while the hot exhaust gasses passed through a bifurcated jet pipe through another pair of vectoring nozzles behind the CoG, in an arrangement which was also used in the Yak-38.
Slow speed control was ensured through puffer jet nozzles, fed by bleed air from the engine and placed on both wing tips as well as under the nose and in the aircraft’s tail section.
Teething troubles with the new engine, as well as the new, vectored nozzle arrangement, postponed the Izedeliye 138 prototype’s first flight until March 1986. Work was also slowed down because OKB Yakovlev had been working on the supersonic Yak-41 V/STOL fighter for the Soviet Navy, too. The Soviet Air Force's Frontal Aviation kept interested in the project, though, since they wanted a dedicated attack aircraft, and no complex multi-role fighter.
State acceptance trials lasted until mid 1987, and a total of four prototypes were built (including one for static ground tests). The Yak-138 was found to be easier to handle than the Yak-38, and the single engine made operations and also the handling during flight mode transition much easier and safer.
The prototypes were soon followed by a pre-production batch of 21 aircraft for field trials in frontline units. By then, the NK-32L had been much improved and now offered 137 kN (31,000 lbf) of thrust for short periods, which made it possible to meet all the Frontal Aviations requirements (esp. the call for 2.000 kg ordnance in VTOL mode).
Among its test pilots, the Yak-138 was quite popular and called "Balkon" ("Balcony") because of the good frontal view from the armored cockpit (offering a 17° downwards sight angle).
For frontline service, the aircraft was now equipped with sophisticated avionics, including a Sokol-138 navigation suite with a DISS-7 Doppler radar and a digital computer. A comprehensive ECM suite was installed for self-defence, including SPS-141 and SB-1 active jammers, KDS-23 chaff/flare dispensers built into the ventral pylon and an SPO-10 radar himing and warning system.
In accordance with the Yak-138‘s strike and low-level attack requirements, provisions were made to mount missiles and precision-guided munitions, as well as retaining a nuclear capability in line with other Soviet combat aircraft. An S-17VG-1 optical sight was fitted, as well as a laser rangefinder and marked-target seeker behind a flat, sloped window in the lower nose section.In the upper nose, between the aircraft's two characterisitic pitot booms, a Delta-2NG beam-riding missile guidance system antenna was placed in a small bullet fairing.
By 1989, the initial batch of aircraft had been delivered (receiving the NATO ASCC code 'Flitchbeam') and successfully tested. An order for 42 more aircraft had been placed and a dual training facility with the Soviet Navy at Kaspiysk AB in the Dagestan region (where Soviet Navy Yak-38U trainers were used for transitional training) established , when the disruption of the Soviet Union suddenly stopped the program in 1991 before the Yak-138 could enter production and service on a large scale.
Most of the machines in Frontal Aviation service fell to the Ukraine, where most of the machines had been based. This situation sealed the fate of the promising Yak-138 more or less over night: the now independent Ukraine did not want to keep the exotic type in its arsenal (together with some Yak-38s of the former Soviet Navy, too), and Russia did not want (and could simply not afford) to pay anything for the machines, which had been offered for an unknown sum.
Officially, all Ukrainian Yak-138 were scrapped until 1994, even though rumor has it that one or two airframes had been sold behind the scenes to China. In Russia only five specimen had survived, and since the spares situation was doubtful none could be kept in flying condition. One Yak-138 was eventually handed over to the Ulyanovsk Aircraft Museum, while the rest was either mothballed or scrapped, too. Unfortunately, the sole museum exhibit was lost in 1995 in a fire accident.
General characteristics:
Crew: One
Length (incl. pitot): 15.84 m (51 ft 10 1/2 in)
Wingspan: 8,17 m (26 ft 9 in)
Height: 4.19 m (14 ft 3 in)
Wing area: 24.18 m² (260.27 ft²)
Empty weight: 7,385 kg (16,281 lb)
Max. takeoff weight: 11,300 kg (28,700 lb)
Powerplant:
1x Kuznetsov NK-32L-2 turbofan engine, rated at 137 kN (31,000 lbf)
Performance:
Maximum speed: 1,176 km/h (730 mph; 635 knots) at sea level
Combat radius: 230 mi (200 nmi, 370 km) lo-lo-lo with 4,400 lb (2,000 kg) payload
Ferry range: 2,129 mi (1,850 nmi, 3,425 km)
Endurance: 1 hr 30 min (combat air patrol – 115 mi (185 km) from base)
Service ceiling: 51,200 ft (15,600 m)
Time to climb to 40,000 ft (12,200 m): 2 min 23 s
Armament:
1x GSh-23L 23mm machine cannon with 250 RPG under the fuselage
5 hardpoints with a total external capacity of
- 3.000 kg (6,600 lb) for C/STOL operations and
- 2.000 kg (4.400 lb) in VTOL mode
Provisions to carry combinations of various types of unguided rockets (up to 240 mm), anti-ship
or air-to-surface Kh-23 (AS-7 Kerry) missiles (together with a Delta N guidance pod), R-60,
R-60M (AA-8 Aphid) or R-73 (AA-11 Archer) air-to-air missiles; tactical nuclear bombs, general
purpose bombs of up to 500 kg (1.100 lb) caliber, or incendiary ZB-500 napalm tanks or up to
three PTB-800 drop tanks under the fuselage and the inner pair of wing pylons
The kit and its assembly:
Sixth contribution to the “Soviet” Group Build at whatifmodelers.com in early 2017, on pretty short notice since the GB had been coming to its end. This totally fictional aircraft was inspired CG illustrations that had been roaming the WWW for some time: a hybrid between a Yak-38 (mostly the tail section), mated with an AV-8B Harrier II (cockpit, wings, landing gear). This did not look bad at all, yet a bit weird, with lift engines added in front of the fin. Certainly not conformal with a good CG balance – but I liked the idea of a single-engine Forger. And actually, OKB Yakovlev had been considering this.
So, the basic idea was a Harrier/Yak-38 kitbash. But the more I thought about the concept, the more additional donor parts came into play. One major addition was the nose section from a MiG-27 – with its slanted nose it would offer the pilot an excellent field of view, and the aircraft would, as a front line attack plane like the Harrier, not carry a radar, so the Flogger’s nose shape was perfect.
Therefore, initial ingredients for the Yak-138 were:
- Rear fuselage, wings and tail from a Tsukuda Hobby/Kangnam/Revell Yak-38
- Mid-fuselage with air intakes and front vectoring nozzles from a Matchbox Sea Harrier
- Cockpit from an Academy MiG-27
Work started with the MiG-27 cockpit, which was more or less taken OOB (except for side consoles in the cockpit and different seat), and the Yak-38 the tail section, built in parallel. To my surprise the Forger fuselage was easier to combine with the Harrier than expected, even though the position of the right cuts took multiple measurements until I came up with a proper solution. Since the Harrier is overall shorter than the Yak-38, the latter’s fuselage had to be shortened. I retained the tail cone, the Forger’s vectoring nozzles and the landing gear wells – and a 2cm plug was taken out between them. Instead of the Harrier’s tandem landing gear arrangement with outriggers under the outer wings, this one was to receive a conventional landing gear for optional C/STOL operations with a higher ordnance load, so that the Yak-38 parts were a welcome basis. Once the fuselage’s underside was more or less complete, the upper rest of the Yak-38 fuselage could be cut to size and integrated into the lower half and the Harrier parts.
After the rear end was settled, the MiG-27 cockpit could be mounted to the front end, which was slightly shortened by 2-3mm (since the Flogger’s is markedly longer than the short Harrier nose). In order to change the overall look of the aircraft, I eventually dropped the Harrier intakes and decided to use the Flogger’s boxy air intakes instead. These are considerably smaller than the gaping Harrier holes, and blending the conflicting shapes into each other for a more or less consistent look took several PSR turns. But it worked, better than expected, and it changes the aircraft’s look effectively, so that almost anything Harrier-esque was gone.
Once the fuselage was completed, I realized that I could not use the Yak-38 wings anymore. They are already pretty small, but with the more voluminous Harrier and Flogger parts added to the aircraft, they’d just be too small!
What to do...? I checked the donor bank and – in order to add even more individual flavor – used a pair of double delta wings from a PM Model Su-15! But only the core of them was left after considerable modifications: The inner delta wing sections were cut off, as well as the tip sections and parts of the trailing edge (for a planform similar to the Yak-38’s wings). On the underside, the landing gear openings were filled up and wing tips from the Yak-38, with puffer jet nozzles, transplanted. The inner leading edges had to be re-sculpted, too. The Su-15 wing fences were kept - a welcome, very Soviet design detail.
A lot of work, but I think it paid out because of the individual shape and look of these “new” wings?
As a consequence of the new, bigger wings, the little Yak-38 stabilizers could not be used anymore, either. In order to keep the square wing shape, I used modified stabilizers from an Intech F-16C/D – their trailing edges were clipped, but the bigger span retained. Together with the characteristic OOB Yak-38 fin they work well, and all of the aerodynamic surfaces IMHO blend well into the overall design of the aircraft.
After the hull was complete, work on smaller things could start. Under the fuselage, a GSh-23-2 pod from a MiG-21 was added, as well as pylons from the Tsukuda Yak-38 under the wings and a donor part from the scrap box in ventral position.
The landing gear is a mix, too: the main struts come from the Yak-38, the balloon wheels from the Matchbox Harrier. The front landing gear comes from the Academy MiG-27, including the wheels with mudguards. It was just mounted in a fashion that it now retracts forward.
The Harrier vectoring nozzles were modified, too, the exhaust “grills” replaced by square, simple ducts, scratched from styrene profile and putty. Care was taken that the nozzles would remain moveable in the fuselage flanks – for later hover pictures. The Yak-38’s nozzles were retained, but since they can OOB only be mounted in a single, fixed position, I added a simple pin to each nozzle, together with two holes in the hull, so that positions can now be switched between hover and level flight.
All around the hull, finally some small details like pitots, blade antennae and air scoops were finally added, and the ordnance consists of a pair of unguided 57mm rocket pods and a pair of Kh-23 (AS-7 Kerry) guided missiles – the latter come from the Yak-38 kit, but they are very crude and their tail sections were modified in order to come (slightly) closer to reality.
Painting and markings:
As an aircraft of the Soviet Frontal Aviation in the late Eighties, I settled upon a typical, disruptive four-tone camouflage with blue undersides. Very conventional, but with an exotic VTOL model I thought that a subtle look would be appropriate – and also separate it from the Naval Yak-38 cousin.
Design benchmark is the scheme on a contemporary MiG-21bis from a Soviert Frontal Aviation unit, chosen because of the disruptive pattern. The tones are guesstimates, though, based on various similar aircraft in more or less weathered condition. I settled for:
- Humbrol 195 (Dark Satin Green)
- Humbrol 78 (RAF Interior Green)
- Modelmaster 2005 (Burnt Umber)
- Humbrol 119 (Light Earth)
- Humbrol 115 (Russian Blue) for the undersides
The cockpit was painted in Russian Cockpit Green, opf course. The landing gear and their respective wells in a mix of Aluminum and Khaki Drab (Humbrol 56 & 26), and the wheel discs became bright green (Humbrol 131). Several di-electric panels and antennae were painted in Humbrol 106 (RAF Ocean Grey).
The kit received a thin black ink wash, in order to emphasize the panel lines, and panel post-shading with subtly lighter tones of the basic colors. National markings, codes and emblems come from several aftermarket sheets, mostly from High Decal Line and Begemot.
After some soot stains (grinded graphite) had been added, the kit was sealed with matt acrlyic varnish (Italeri) and the ordnace added.
Messy work, but I am surprised how consistent and normal the resulting aircraft appears? From certain angles, my Yak-138 creation reminds a good deal of the stillborn Hawker P.1154 (no similarity intended, though), the SEPECAT Jaguar or rather exotic Soko J-22 Orao/IAR-93 Vultur fighter bomber. IMHO, there’s also some A-4 Skyhawk style to it, esp. in planview? Anyway, there’s still some good Yak-38 heritage recognizable, and the tactical Frontal Aviation paint scheme suits the aircraft well - looks like a serious mud mover.
Inside the Payload Hazardous Servicing Facility at NASA's Kennedy Space Center in Florida, technicians and engineers test a solar array before it is integrated with the Origins, Spectral Interpretation, Resource Identification, Security--Regolith Explorer, or OSIRIS-REx spacecraft. Targeted for liftoff Sept. 8, 2016, aboard a United Launch Alliance Atlas V rocket, OSIRIS-REx will be the first U.S. mission to sample an asteroid, retrieve at least two ounces of surface material and return it to Earth for study. The asteroid, Bennu, may hold clues to the origin of the solar system and the source of water and organic molecules found on Earth.
Photo credit: NASA/Ben Smegelsky
Inside the Payload Hazardous Servicing Facility at the NASA's Kennedy Space Center in Florida, the first of two solar panels is being deployed on the agency's Transiting Exoplanet Survey Satellite (TESS). The satellite is scheduled to launch atop a SpaceX Falcon 9 rocket from Space Launch Complex 40 at Cape Canaveral Air Force Station. TESS is the next step in NASA's search for planets outside our solar system, known as exoplanets. TESS is a NASA Astrophysics Explorer mission led and operated by MIT in Cambridge, Massachusetts, and managed by NASA’s Goddard Space Flight Center in Greenbelt, Maryland. Dr. George Ricker of MIT’s Kavli Institute for Astrophysics and Space Research serves as principal investigator for the mission. Additional partners include Orbital ATK, NASA’s Ames Research Center, the Harvard-Smithsonian Center for Astrophysics and the Space Telescope Science Institute. More than a dozen universities, research institutes and observatories worldwide are participants in the mission. NASA’s Launch Services Program is responsible for launch management. Photo credit: NASA/Leif Heimbold
NROL-68 is mounted on top of the United Launch Alliance (ULA) Delta IV Heavy rocket ahead of launch for the National Reconnaissance Office. Photo Credit: United Launch Alliance
NROL-68 is mounted on top of the United Launch Alliance (ULA) Delta IV Heavy rocket ahead of launch for the National Reconnaissance Office. Photo Credit: United Launch Alliance
SpinLaunch is one of those rare companies that feels like it stepped out of a 1970s sci-fi paperback—except it’s real, and it’s quietly reshaping how we think about space access. The company uses rotational kinetic energy to hurl payloads into space without conventional rockets. Their system involves a vacuum-sealed centrifuge that spins a payload to hypersonic speeds and releases it through a launch tube. The goal: dramatically reduce launch costs, minimize fuel use, and enable frequent launches.
SpinLaunch’s Suborbital Accelerator at Spaceport America in New Mexico has successfully launched test payloads at hypersonic speeds since 2021– without rockets or chemical propellants. The company claims their system could reduce launch costs by up to 10x, especially for small satellites. Though still in development, the system could eventually launch small satellites into Earth orbit. The extreme acceleration forces (~10,000 g) needed to launch them from Earth mean only specially hardened electronics and components can survive.
SpinLaunch tech can theoretically be adapted for low-gravity environments, on the Moon and asteroids to launch raw materials into space. The materials could then be used to build orbital habitats or transported to Earth. NASA signed a Space Act Agreement to evaluate SpinLaunch’s technology for future missions.
-----------------------------------------------------
It’s the year 2075. nestled in the shadowed rim of Shackleton Crater near the lunar south pole, a sprawling base hums with quiet purpose. The sun never sets here—it just skims the horizon, feeding vast solar arrays that glint like obsidian wings.
At the heart of the base lies the SpinLaunch Lunar Accelerator, a sleek, vacuum-sealed launch tunnel embedded in regolith. It stretches like a silver arrow across the dust, aimed at Earth’s orbit. Inside, payloads of refined lunar ore—aluminum, titanium, even rare helium-3—are spun to hypersonic speeds and flung into space, feeding orbital foundries and Earth’s energy grid.
Modular habitats cluster nearby, their domes shielded with regolith and water ice. Inside, engineers monitor launch telemetry, biologists tend to greenhouse crops, and artists sketch Earthrise from the observation dome. Robotic miners trundle across the terrain, scooping regolith and feeding it into processing units that sort, refine, and package materials for launch.
A tall communications mast beams data to Earth and Mars, while a rover convoy returns from a nearby lava tube—potential site for expansion. The base is quiet, efficient, and beautiful in its starkness. It’s not a city yet, but it’s a beginning.
And above it all, Earth hangs in the sky—blue, fragile, and watching.
+++ DISCLAIMER +++
Nothing you see here is real, even though the conversion or the presented background story might be based historical facts. BEWARE!
Some background:
The Yakovlev Yak-38 (Russian: Яковлева Як-38; NATO reporting name: "Forger") was the Soviet Naval Aviation's first and only operational VTOL strike fighter aircraft, in addition to being its first operational carrier-based fixed-wing aircraft. It was developed specifically for and served almost exclusively on the Kiev-class aircraft carriers.
Some specimen of the initial variant were tested during the Soviet Union's intervention in Afghanistan. These trials revealed several weaknesses of the construction in the form of unacceptable hot and high capabilities as well as a low payload. A further development for the Soviet Navy was therefore decided in August 1981, the abilities of which were fixed in October 1982. Already in November 1982 the first flight experiments of the prototype, leading to the Yak-38M, took place. In mid-1983 the manufacturing tests were completed and the production release was granted.
Anyway, the Soviet Air Force also had interest in a VTOL attack aircraft, which could provide CAS duties in immediate front line theatres, complementing the new Suchoj Su-25 Frogfoot and various attack helicopter types - but the Yak-38 was outright rejected. The Frontal Aviation demanded a much better performance, a dedicated avionics suite for ground attack duties and a higher payload of at least 2.500 kg (5.500 lb) in VTOL mode, plus an internal gun, and 3.000 kg (6.600 lb) when operating in C/STOL mode at sea level and from semi-prepared airstrips. For its primary ground attack role, the machine was also to be armored against projectiles of up to 0.5” around the lower hull and against 20mm rounds in the cockpit section. Finally, the machine had to be, compared with the Yak-38, simplified and be more rugged in order to ease frontline service and endure survivability.
OKB Yakovlev accepted the challenge and dusted off studies that had been undertaken during the Yak-38’s design stage. One of these was the Yak-38L (for 'lift/cruise'), a design built around a single, modified the AL-21F turbojet with vectoring nozzles and no lift engines, which were just dead weight in normal flight. This route seemed to be the most promising option for the Frontal Aviation's demands, even though it would mean a severe re-construction of the airframe.
The new aircraft, internally referred to as 'Izdeliye 138', was based on the Yak-38 airframe, but adapted and literally built around a lift/cruise variant of the large Kuznetsov NK-32 low bypass turbofan engine (originally, with an afterburner, powering the late Tu-144 airliners and the Tu-160 bomber). This engine’s initial derivative, NK-32L-1, adapted for operation with four vectoring nozzles, had a dry thrust of roundabout 110 kN (25,000 lbf) – about 10% more than the Yak-38’s engine trio all together. And the massive engine bore potential for at least 10% more power for the service aircraft.
The overall layout differed considerably from the long and sleek Yak-38: in order to create enough space for the large turbofan stage and its bigger, fixed-configuration air intakes, the fuselage had to be widened behind the cockpit section and the wings' main spar was moved upwards, so that the wings were now shoulder-mounted. The overall arrangement was reminiscent of the successful Hawker Harrier, but differed in some details like the landing gear, which was a classic tricycle design.
Cold air from the NK-32L’s initial turbofan stage was ducted into vectoring nozzles at the forward fuselage flanks, just in front of the aircraft's center of gravity, while the hot exhaust gasses passed through a bifurcated jet pipe through another pair of vectoring nozzles behind the CoG, in an arrangement which was also used in the Yak-38.
Slow speed control was ensured through puffer jet nozzles, fed by bleed air from the engine and placed on both wing tips as well as under the nose and in the aircraft’s tail section.
Teething troubles with the new engine, as well as the new, vectored nozzle arrangement, postponed the Izedeliye 138 prototype’s first flight until March 1986. Work was also slowed down because OKB Yakovlev had been working on the supersonic Yak-41 V/STOL fighter for the Soviet Navy, too. The Soviet Air Force's Frontal Aviation kept interested in the project, though, since they wanted a dedicated attack aircraft, and no complex multi-role fighter.
State acceptance trials lasted until mid 1987, and a total of four prototypes were built (including one for static ground tests). The Yak-138 was found to be easier to handle than the Yak-38, and the single engine made operations and also the handling during flight mode transition much easier and safer.
The prototypes were soon followed by a pre-production batch of 21 aircraft for field trials in frontline units. By then, the NK-32L had been much improved and now offered 137 kN (31,000 lbf) of thrust for short periods, which made it possible to meet all the Frontal Aviations requirements (esp. the call for 2.000 kg ordnance in VTOL mode).
Among its test pilots, the Yak-138 was quite popular and called "Balkon" ("Balcony") because of the good frontal view from the armored cockpit (offering a 17° downwards sight angle).
For frontline service, the aircraft was now equipped with sophisticated avionics, including a Sokol-138 navigation suite with a DISS-7 Doppler radar and a digital computer. A comprehensive ECM suite was installed for self-defence, including SPS-141 and SB-1 active jammers, KDS-23 chaff/flare dispensers built into the ventral pylon and an SPO-10 radar himing and warning system.
In accordance with the Yak-138‘s strike and low-level attack requirements, provisions were made to mount missiles and precision-guided munitions, as well as retaining a nuclear capability in line with other Soviet combat aircraft. An S-17VG-1 optical sight was fitted, as well as a laser rangefinder and marked-target seeker behind a flat, sloped window in the lower nose section.In the upper nose, between the aircraft's two characterisitic pitot booms, a Delta-2NG beam-riding missile guidance system antenna was placed in a small bullet fairing.
By 1989, the initial batch of aircraft had been delivered (receiving the NATO ASCC code 'Flitchbeam') and successfully tested. An order for 42 more aircraft had been placed and a dual training facility with the Soviet Navy at Kaspiysk AB in the Dagestan region (where Soviet Navy Yak-38U trainers were used for transitional training) established , when the disruption of the Soviet Union suddenly stopped the program in 1991 before the Yak-138 could enter production and service on a large scale.
Most of the machines in Frontal Aviation service fell to the Ukraine, where most of the machines had been based. This situation sealed the fate of the promising Yak-138 more or less over night: the now independent Ukraine did not want to keep the exotic type in its arsenal (together with some Yak-38s of the former Soviet Navy, too), and Russia did not want (and could simply not afford) to pay anything for the machines, which had been offered for an unknown sum.
Officially, all Ukrainian Yak-138 were scrapped until 1994, even though rumor has it that one or two airframes had been sold behind the scenes to China. In Russia only five specimen had survived, and since the spares situation was doubtful none could be kept in flying condition. One Yak-138 was eventually handed over to the Ulyanovsk Aircraft Museum, while the rest was either mothballed or scrapped, too. Unfortunately, the sole museum exhibit was lost in 1995 in a fire accident.
General characteristics:
Crew: One
Length (incl. pitot): 15.84 m (51 ft 10 1/2 in)
Wingspan: 8,17 m (26 ft 9 in)
Height: 4.19 m (14 ft 3 in)
Wing area: 24.18 m² (260.27 ft²)
Empty weight: 7,385 kg (16,281 lb)
Max. takeoff weight: 11,300 kg (28,700 lb)
Powerplant:
1x Kuznetsov NK-32L-2 turbofan engine, rated at 137 kN (31,000 lbf)
Performance:
Maximum speed: 1,176 km/h (730 mph; 635 knots) at sea level
Combat radius: 230 mi (200 nmi, 370 km) lo-lo-lo with 4,400 lb (2,000 kg) payload
Ferry range: 2,129 mi (1,850 nmi, 3,425 km)
Endurance: 1 hr 30 min (combat air patrol – 115 mi (185 km) from base)
Service ceiling: 51,200 ft (15,600 m)
Time to climb to 40,000 ft (12,200 m): 2 min 23 s
Armament:
1x GSh-23L 23mm machine cannon with 250 RPG under the fuselage
5 hardpoints with a total external capacity of
- 3.000 kg (6,600 lb) for C/STOL operations and
- 2.000 kg (4.400 lb) in VTOL mode
Provisions to carry combinations of various types of unguided rockets (up to 240 mm), anti-ship
or air-to-surface Kh-23 (AS-7 Kerry) missiles (together with a Delta N guidance pod), R-60,
R-60M (AA-8 Aphid) or R-73 (AA-11 Archer) air-to-air missiles; tactical nuclear bombs, general
purpose bombs of up to 500 kg (1.100 lb) caliber, or incendiary ZB-500 napalm tanks or up to
three PTB-800 drop tanks under the fuselage and the inner pair of wing pylons
The kit and its assembly:
Sixth contribution to the “Soviet” Group Build at whatifmodelers.com in early 2017, on pretty short notice since the GB had been coming to its end. This totally fictional aircraft was inspired CG illustrations that had been roaming the WWW for some time: a hybrid between a Yak-38 (mostly the tail section), mated with an AV-8B Harrier II (cockpit, wings, landing gear). This did not look bad at all, yet a bit weird, with lift engines added in front of the fin. Certainly not conformal with a good CG balance – but I liked the idea of a single-engine Forger. And actually, OKB Yakovlev had been considering this.
So, the basic idea was a Harrier/Yak-38 kitbash. But the more I thought about the concept, the more additional donor parts came into play. One major addition was the nose section from a MiG-27 – with its slanted nose it would offer the pilot an excellent field of view, and the aircraft would, as a front line attack plane like the Harrier, not carry a radar, so the Flogger’s nose shape was perfect.
Therefore, initial ingredients for the Yak-138 were:
- Rear fuselage, wings and tail from a Tsukuda Hobby/Kangnam/Revell Yak-38
- Mid-fuselage with air intakes and front vectoring nozzles from a Matchbox Sea Harrier
- Cockpit from an Academy MiG-27
Work started with the MiG-27 cockpit, which was more or less taken OOB (except for side consoles in the cockpit and different seat), and the Yak-38 the tail section, built in parallel. To my surprise the Forger fuselage was easier to combine with the Harrier than expected, even though the position of the right cuts took multiple measurements until I came up with a proper solution. Since the Harrier is overall shorter than the Yak-38, the latter’s fuselage had to be shortened. I retained the tail cone, the Forger’s vectoring nozzles and the landing gear wells – and a 2cm plug was taken out between them. Instead of the Harrier’s tandem landing gear arrangement with outriggers under the outer wings, this one was to receive a conventional landing gear for optional C/STOL operations with a higher ordnance load, so that the Yak-38 parts were a welcome basis. Once the fuselage’s underside was more or less complete, the upper rest of the Yak-38 fuselage could be cut to size and integrated into the lower half and the Harrier parts.
After the rear end was settled, the MiG-27 cockpit could be mounted to the front end, which was slightly shortened by 2-3mm (since the Flogger’s is markedly longer than the short Harrier nose). In order to change the overall look of the aircraft, I eventually dropped the Harrier intakes and decided to use the Flogger’s boxy air intakes instead. These are considerably smaller than the gaping Harrier holes, and blending the conflicting shapes into each other for a more or less consistent look took several PSR turns. But it worked, better than expected, and it changes the aircraft’s look effectively, so that almost anything Harrier-esque was gone.
Once the fuselage was completed, I realized that I could not use the Yak-38 wings anymore. They are already pretty small, but with the more voluminous Harrier and Flogger parts added to the aircraft, they’d just be too small!
What to do...? I checked the donor bank and – in order to add even more individual flavor – used a pair of double delta wings from a PM Model Su-15! But only the core of them was left after considerable modifications: The inner delta wing sections were cut off, as well as the tip sections and parts of the trailing edge (for a planform similar to the Yak-38’s wings). On the underside, the landing gear openings were filled up and wing tips from the Yak-38, with puffer jet nozzles, transplanted. The inner leading edges had to be re-sculpted, too. The Su-15 wing fences were kept - a welcome, very Soviet design detail.
A lot of work, but I think it paid out because of the individual shape and look of these “new” wings?
As a consequence of the new, bigger wings, the little Yak-38 stabilizers could not be used anymore, either. In order to keep the square wing shape, I used modified stabilizers from an Intech F-16C/D – their trailing edges were clipped, but the bigger span retained. Together with the characteristic OOB Yak-38 fin they work well, and all of the aerodynamic surfaces IMHO blend well into the overall design of the aircraft.
After the hull was complete, work on smaller things could start. Under the fuselage, a GSh-23-2 pod from a MiG-21 was added, as well as pylons from the Tsukuda Yak-38 under the wings and a donor part from the scrap box in ventral position.
The landing gear is a mix, too: the main struts come from the Yak-38, the balloon wheels from the Matchbox Harrier. The front landing gear comes from the Academy MiG-27, including the wheels with mudguards. It was just mounted in a fashion that it now retracts forward.
The Harrier vectoring nozzles were modified, too, the exhaust “grills” replaced by square, simple ducts, scratched from styrene profile and putty. Care was taken that the nozzles would remain moveable in the fuselage flanks – for later hover pictures. The Yak-38’s nozzles were retained, but since they can OOB only be mounted in a single, fixed position, I added a simple pin to each nozzle, together with two holes in the hull, so that positions can now be switched between hover and level flight.
All around the hull, finally some small details like pitots, blade antennae and air scoops were finally added, and the ordnance consists of a pair of unguided 57mm rocket pods and a pair of Kh-23 (AS-7 Kerry) guided missiles – the latter come from the Yak-38 kit, but they are very crude and their tail sections were modified in order to come (slightly) closer to reality.
Painting and markings:
As an aircraft of the Soviet Frontal Aviation in the late Eighties, I settled upon a typical, disruptive four-tone camouflage with blue undersides. Very conventional, but with an exotic VTOL model I thought that a subtle look would be appropriate – and also separate it from the Naval Yak-38 cousin.
Design benchmark is the scheme on a contemporary MiG-21bis from a Soviert Frontal Aviation unit, chosen because of the disruptive pattern. The tones are guesstimates, though, based on various similar aircraft in more or less weathered condition. I settled for:
- Humbrol 195 (Dark Satin Green)
- Humbrol 78 (RAF Interior Green)
- Modelmaster 2005 (Burnt Umber)
- Humbrol 119 (Light Earth)
- Humbrol 115 (Russian Blue) for the undersides
The cockpit was painted in Russian Cockpit Green, opf course. The landing gear and their respective wells in a mix of Aluminum and Khaki Drab (Humbrol 56 & 26), and the wheel discs became bright green (Humbrol 131). Several di-electric panels and antennae were painted in Humbrol 106 (RAF Ocean Grey).
The kit received a thin black ink wash, in order to emphasize the panel lines, and panel post-shading with subtly lighter tones of the basic colors. National markings, codes and emblems come from several aftermarket sheets, mostly from High Decal Line and Begemot.
After some soot stains (grinded graphite) had been added, the kit was sealed with matt acrlyic varnish (Italeri) and the ordnace added.
Messy work, but I am surprised how consistent and normal the resulting aircraft appears? From certain angles, my Yak-138 creation reminds a good deal of the stillborn Hawker P.1154 (no similarity intended, though), the SEPECAT Jaguar or rather exotic Soko J-22 Orao/IAR-93 Vultur fighter bomber. IMHO, there’s also some A-4 Skyhawk style to it, esp. in planview? Anyway, there’s still some good Yak-38 heritage recognizable, and the tactical Frontal Aviation paint scheme suits the aircraft well - looks like a serious mud mover.
Fourth stage and payload bay of an engineering back-up for the Jupiter-C rocket designated "UE". On display in the Smithsonian Air and Space Museum in Washington, D.C.
The Jupiter rockets were linear descendants of the V-2 -- a ballistic missile developed by Nazi Germany during World War II. In 1954, two programs were under way to develop an American intermediate range intercontinental ballistic missile (IRBM). One was Project Vanguard, run by the U.S. Navy. The other was Project Orbiter, run by the Navy and the U.S. Army. By 1955, it was clear that Project Vanguard had won -- but the Jupiter rockets served a useful purpose for a time, and have a unique role in U.S. history.
The Redstone rocket (first launched in 1953) was derived from the V-2, and was the first short-range, surface-to-surface ballistic missile developed by the United States. Although other missiles had been used (the Corporal, the Sergeant), this was a BALLISTIC missile because it actually left the atmosphere before coming back down to hit its target.
The Jupiter-A was a rocket derived from the Redstone, and used only as a test vehicle for components that would later become the Jupiter medium-range ballistic missile (MRBM). Built in 1954 and deployed in 1956, the Jupiter MRBMs (by now woefully obsolete) would be pulled from service in 1961 as part of the agreement pulling nuclear missiles out of Cuba following the Cuban Missile Crisis.
The Jupiter-C was a sounding rocket. Sounding rockets were not intended to reach orbit. Rather, they were designed to reach high into the atmosphere (between 30 and 950 miles) to gather data and test instruments. Jupiter-Cs were launched from Cape Canaveral in Florida.
Like the Jupiter-A, the Jupiter-C was a test rocket. Its purpose was to test the re-entry capabilities of the nuclear bombs it carried. These bombs were wrapped in ablative material, and testing the ablative material was the reason for the Jupiter-C.
The Jupiter-C's first stage was a Redstone that was lengthened by eight feet accommodate more fuel. The motor was a Rocketdyne A-7 engine that burned liquid oxygen and "Hydyne" (a rocket fuel developed by Rocketdyne that used the highly toxic and unstable dimethylhydrazine and diethylenetriamine).
The second and third stages looked like a single stage, but they were not. The second stage was a ring of 11 rocket engines taken from the Sergeant short-range solid-fuel missile. These were scaled down by the Jet Propulsion Laboratory. They surrounded the fuel tank, and were held in place by steel rings. A webbed bulkhead fore and aft isolated the stage from the other stages. A cylinder of aluminum protected the engines.
The third stage was exactly like the second stage, but consisted of just three scaled-down Sergeant rocket engines.
The fourth stage was a single scaled-down Sergeant rocket.
The Jupiter-C had a variety of guidance systems. The first stage was topped by an instrument package that contained gyroscopic flight controls. Maneuverable fins and vanes in the rocket exhaust controlled the flight. The rocket was programmed to travel at a 40-degree angle when the first stage burned out at 157 seconds into the flight. The rocket coasted upward for another 100 seconds. At this point, electric motors began spinng the axle-mounted second/third/fourth stages. The rate of spin varied from 450 to 750 rpm, and was controlled from the ground (so that the motors would compensate only for the second/third/fourth stage attitude and not the first stage -- which was still firing). This stabilized them, so that a guidance system was not needed.
The instrument package and second/third/fourth stages separated from the first stage using explosive bolts and springs. A radio signal from the ground ignited the second stage, whose exhaust blew away the instrument package.
The third and fourth stages also used electric motors to spin up.
It was clear right away that the Jupiter-C was so powerful, it could launch a satellite into orbit. But it needed a fourth stage to do so.
Werner von Braun, the German scientist who ran the American space program, worried that the Jupiter-C looked too military and would be perceived as an offensive weapon. So when the fourth stage was added, von Braun re-designated the rocket as a "Juno I." (NASA considers the Jupiter-C and the Juno I the same rocket, although Wikipedia and other sources like to think they are not.)
There were just three launches of the Jupiter-C in the three-stage configuration, but six launches of it in the four-stage configuration.
It was in the four-stage configuration that the Jupiter-C made world history. On January 31, 1958, the Jupiter-C put Explorer I -- America's first satellite -- into orbit. Explorer I discovered the Van Allen radiation belts. On March 26, 1958, a Jupiter-C put Explorer III into orbit, and on July 26, 1958, a Jupiter-C put Explorer IV into orbit.
Remember, the Jupiter program was a military one. Rockets needed to be numbered, but the military did not want the Russians seeing how many rockets had been built or flown. The base where the Jupiter-Cs were built was Huntsville, Alabama. A simple cypher was used to name the rockets: H=1, U=2, N=3, T=4, etc. The Jupiter-C that launched Explorer 1 had "UE" painted on the side, indicating it was rocket number 29 (U=2, E=9).
A truck transports technicians wearing Self-Contained Atmospheric Protective Ensemble (SCAPE) suits and operations support personnel to the Multi-Payload Processing Facility (MPPF) at NASA’s Kennedy Space Center in Florida, for a test simulation of loading propellants into a replicated test tank for Orion on Aug. 16, 2019. Exploration Ground Systems is preparing for Artemis 1 with a series of hazardous hyper test events at the MPPF. The technicians will complete a tanking to test the system before Orion arrives for processing. During preparations for launch, these teams will be responsible for loading the Orion vehicle with propellants prior to transportation to the Vehicle Assembly Building, where it will be secured atop the Space Launch System rocket. SCAPE suits are used in operations involving toxic propellants and are supplied with air either through a hardline or through a self-contained environmental control unit. Photo credit: NASA/Isaac Watson
Inside the Multi-Operations Support Building near the Multi-Payload Processing Facility (MPPF) at NASA’s Kennedy Space Center in Florida, technicians and operations personnel review procedures for a test simulation of loading propellants into a replicated test tank for Orion, on Aug. 16, 2019. Exploration Ground Systems is preparing for Artemis 1 with a series of hazardous hyper test events at the MPPF. Technicians will practice putting on Self-Contained Atmospheric Protective Ensemble (SCAPE) suits and then complete tanking to test the system before Orion arrives for processing. During preparations for launch, these teams will be responsible for loading the Orion vehicle with propellants prior to transportation to the Vehicle Assembly Building, where it will be secured atop the Space Launch System rocket. SCAPE suits are used in operations involving toxic propellants and are supplied with air either through a hardline or through a self-contained environmental control unit. Photo credit: NASA/Isaac Watson
Encapsulated in its payload fairing, Tracking and Data Relay Satellite (TDRS-M) is mated to the United Launch Alliance Atlas V Centaur upper stage in the Vertical Integration Facility at Space Launch Complex 41 at Cape Canaveral Air Force Station in Florida. TDRS-M will be the latest spacecraft destined for the agency's constellation of communications satellites that allows nearly continuous contact with orbiting spacecraft ranging from the International Space Station and Hubble Space Telescope to the array of scientific observatories. Liftoff atop the ULA Atlas V rocket is scheduled for Aug. 18, 2017.
Photo credit: NASA/Kim Shiflett
First of two Galileo navigation satellites SATs 9-10 being attached to the payload dispenser system, which will first secure the satellites during their flight to medium-altitude orbit and then release them into space. The satellites were hoisted into position and secured during 27–28 August 2015.
SATs 9-10 are scheduled to lift off at 02:08 GMT on 11 September (04:08 CEST; 23:08 local time, 10 September) from Europe’s Spaceport in French Guiana on top of a Soyuz rocket. They are expected to become operational, after initial in-orbit testing, later in the autumn.
Credit: ESA–M. Pedoussaut, 2015
Inside the Multi-Operations Support Building near the Multi-Payload Processing Facility (MPPF) at NASA’s Kennedy Space Center in Florida, a technician is wearing a Self-Contained Atmospheric Protective Ensemble (SCAPE) suit to prepare for a test simulation of loading propellants into a replicated test tank for Orion, on Aug. 16, 2019. Exploration Ground Systems is preparing for Artemis 1 with a series of hazardous hyper test events at the MPPF. After donning their suits, the technicians will complete a tanking to test the system before Orion arrives for processing. During preparations for launch, these teams will be responsible for loading the Orion vehicle with propellants prior to transportation to the Vehicle Assembly Building, where it will be secured atop the Space Launch System rocket. SCAPE suits are used in operations involving toxic propellants and are supplied with air either through a hardline or through a self-contained environmental control unit. Photo credit: NASA/Isaac Watson
NROL-68 is mounted on top of the United Launch Alliance (ULA) Delta IV Heavy rocket ahead of launch for the National Reconnaissance Office. Photo Credit: United Launch Alliance
The Air Force's AEHF-4 mission, encapsulated inside a 5-meter payload fairing, is mated to its United Launch Alliance (ULA) Atlas V booster inside the Vertical Integration Facility (VIF) at Cape Canaveral's Space Launch Complex-41. Photo credit: United Launch Alliance
NASA Administrator Jim Bridenstine, left, and NASA Associate Administrator for the Science Mission Directorate, Thomas Zurbuchen, answer questions during an event where nine U.S. companies where named as eligible to bid on NASA delivery services to the lunar surface through Commercial Lunar Payload Services (CLPS) contracts, Thursday, Nov. 29, 2018 at NASA Headquarters in Washington. The companies will be able to bid on delivering science and technology payloads for NASA, including payload integration and operations, launching from Earth and landing on the surface of the Moon. NASA expects to be one of many customers that will use these commercial landing services. Photo Credit: (NASA/Bill Ingalls)
Edited NASA image of the bottom of the Perseverance rover. The caption mentions the helicopter being sent to Mars but the image doesn't really show it.
Original caption: NASA’s Mars Helicopter is installed on the agency’s Mars Perseverance rover inside the Payload Hazardous Servicing Facility at Florida’s Kennedy Space Center on April 6, 2020. Perseverance safely lands on Mars, the helicopter will be released to perform the first in a series of flight tests that will take place during a period of about 30 days. The helicopter will be the first aircraft to fly on another planet. Perseverance, carrying the helicopter, will touch down on the Red Planet on Feb. 18, 2021. Liftoff aboard a United Launch Alliance Atlas V 541 rocket is targeted between July 17 and Aug. 5 from Cape Canaveral Air Force Station.
+++ DISCLAIMER +++
Nothing you see here is real, even though the conversion or the presented background story might be based historical facts. BEWARE!
Some background:
The Republic P-47 Thunderbolt was one of the largest and heaviest fighter aircraft in history to be powered by a single piston engine. It was heavily armed with eight .50-caliber machine guns, four per wing. When fully loaded, the P-47 weighed up to eight tons, and in the fighter-bomber ground-attack roles could carry five-inch rockets or a significant bomb load of 2,500 pounds; it could carry over half the payload of the B-17 bomber on long-range missions (although the B-17 had a far greater range).
The P-47, originally based on the powerful Pratt & Whitney R-2800 Double Wasp engine, was to be very effective as a short-to-medium range escort fighter in high-altitude air-to-air combat and, when unleashed as a fighter-bomber, proved especially adept at ground attack in both the World War II European and Pacific Theaters.
The P-47 was one of the main United States Army Air Forces (USAAF) fighters of World War II, and served with other Allied air forces, notably those of France, Britain, and Russia. Mexican and Brazilian squadrons fighting alongside the U.S. were equipped with the P-47.
In 1943, two P-47D-15-RE airframes (serials 42-23297/23298) were selected for testing with the new experimental 2300 hp Chrysler XIV-2220-1 sixteen-cylinder inverted Vee liquid-cooled engine. These aircraft were re-designated XP-47H. The liquid-cooled Chrysler engine with its large under-fuselage radiator radically changed the appearance of the Thunderbolt, and increased overall length to 39 feet 2 inches. With the increased power and improved streamlining, a maximum speed of 490 mph was anticipated.
The two P-47D-15-RE airframes were converted until early 1944 and test flights began on July 26, 1945. During flight trails, one of the XP-47Hs actually attained a speed of 490 mph in level flight, and the new aircraft was primarily intended as a fast interceptor for the European theater, where especially Great Britain was endangered by the fast V1 missiles, and initial reports about German jet fighters and reconnaissance aircraft that were hard to counter with current piston-engine types, stirred the need for this fast aircraft.
Production P-47Hs received several amendments that had already been introduced with the late D types, e. g. the lowered back and a bubble canopy that offered excellent view. The P-47H also received the new wing from the P-47N, recognizable by its characteristic square wing tips which allowed better roll manoeuvers. Not visible at first glance were the integral wing tanks, which enhanced the internal fuel load to 4.792,3 liters, resulting in a range of 3.500 km (2.175 ml), so that the P-47H was also suited for long range bomber escorts. Air brakes were added to the wing's lower surfaces, too, to allow braking after a dive onto its prey.
Furthermore, serial production machines received an uprated, more reliable Chrysler XIV-2220-2 engine, which had an output of 2.450 hp.
The P-47H was put into limited production with 130 built, sufficient for one group. However, the type suffered serious teething problems in the field due to the highly tuned engine. Engines were unable to reach operating temperatures and power settings and frequently failed in early flights from a variety of causes: ignition harnesses cracked at high altitudes, severing electrical connections between the magneto and distributor, and carburetor valve diaphragms also failed. Poor corrosion protection during shipments across the Atlantic also took their toll on the engines and airframes.
By the time the bugs were worked out, the war in Europe was nearly over. However, P-47Hs still destroyed 15 enemy jet aircraft in aerial combat in March-May 1945 when aerial encounters with the Luftwaffe were rare. The type also proved itself to be a valuable V1 missile interceptor over the Channel.
The entire production total of 130 P-47Hs were delivered to the 358th Fighter Group, which was part of the 9th Air Force and operated from Great Britain, France and finally on German ground. From the crews the P-47H received several nicknames like 'torpedo', 'Thunderbullet' or 'Anteater', due to its elongated nose section.
Twelve P-47H were lost in operational crashes with the 358th Group resulting in 11 deaths, two after VE Day, and two (44-21134 on 13 April 1945 and 44-21230 on 16 April 1945) were shot down in combat, both by ground fire.
General characteristics:
Crew: 1
Length: 39 ft 2 in (11.96 m)
Wingspan: 40 ft 9 in (12.42 m)
Height: 14 ft 8 in (4.47 m)
Wing area: 300 ft² (27.87 m²)
Empty weight: 10,000 lb (4,535 kg)
Loaded weight: 13,300 lb (6,032 kg)
Max. takeoff weight: 17,500 lb (7,938 kg)
Powerplant:
1× Chrysler XIV-2220-2 sixteen-cylinder inverted Vee liquid-cooled engine, rated at 2.450 hp.
Performance:
Maximum speed: 503 mph at 30,000 ft (810 km/h at 9,145 m)
Range: 920 mi combat, 2.175 ml ferry (1.480 km / 3.500 km)
Service ceiling: 43,000 ft (13,100 m)
Rate of climb: 3,120 ft/min (15.9 m/s)
Wing loading: 44.33 lb/ft² ()
Power/mass: 0.19 hp/lb (238 W/kg)
Armament:
8× .50 in (12.7 mm) M2 Browning machine guns (3.400 rounds)
Up to 2,500 lb (1,134 kg) of bombs, drop tanks and/or 10× 5 in (127 mm) unguided rockets
The kit and its assembly:
I had the (X)P-47H on the agenda for some time, and even the respective MPM kit stashed away. But it took some time to start this project - one reason actually being the, well, crudeness of the MPM offering. Anyway, I wanted to build a service aircraft, and I wondered how this would have looked like, way beyond 1944? That brought me towards the late bubble canopy versions of the P-47D - and suddenly the idea was born to convert the XP-47H into a respective service aircraft which would not only carry the Chrysler XIV-2220-1 V16 engine, but also other improvements of the type. This eventually led to the decision to make this build a kitbash, as a spine implantation would be the easiest way to incorporate the lowered back - or so I thought...
I chose the ancient Heller P-47(N) as donation kit. Not because it was “good”, it just had the right ingredients and was cheap and easy to procure. What sounded like a simple plan turned into a twisted route to vague success. I took the front fuselage and the lower belly from the MPM kit, as well as the horizontal stabilizers and mated it with the upper and rear fuselage of the Heller Thunderbolt. This could have been easy, if both kits would not have had different fuselage diameters - the Heller kit is about 1mm too narrow, even though the length is fine. In order to compensate, I built two new fuselage halves from the salvaged pieces, and once these were stable and more or less sanded even, put together. Inside, the cockpit was taken from the Heller kit, but the seat comes from the MPM kit, and a pilot figure was added. Another problem is the fact that the MPM kit features engraved panel lines, while the Heller kit has old school, raised details and lots of rivets.
The propeller from the MPM kit is a joke, so I built a replacement from scratch - from a drop tank front half from an ancient Revell F4U, and the individual propeller blades were taken from an Italeri F4U. Inside the fuselage, a styrene tube was implanted which holds the new propeller on a metal axis, so it can spin freely.
Other personal mods include lowered flaps and the large cooler intake was opened, with foamed styrene placed inside which mimics some mesh. The same method was also used inside of the intercooler outlets (primarily in order to block any light from shining through). Inside of the landing gear wells I added some structure made from styrene profiles.
Another bigger challenge was the wing attachment - Heller and MPM kit differ considerably in this aspect, so that swapping parts is not easy. The MPM kit has the wing roots molded onto the fuselage halves, while the Heller wings are, more or less, directly attached to the fuselage. As a consequence the Heller wings hold the complete landing gear wells, while the MPM solution has divided sections. I decided to get rid of the MPM wing roots, about 3mm of material, and onto these stubs the Heller wings were attached. The landing gear came from the Heller kit, but the main wheels come from a (new) Revell Me 262 - both MPM and Heller parts are not recommended for serious use... Finally, the many exhausts and cooler flaps were either sanded away and replaced by scratched parts, or added - e. g. the vents behind the cockpit. While the Heller kit features bomb and missile hardpoints under the wings I decided to leave them away - this is supposed to be a fast interceptor, not a train-hunting plough.
Painting and markings:
As this was to be a very late WWII aircraft, NMF was certain, and I wanted to place the service P-47H into the European conflict theatre, where its speed would IMHO be best used against German jet threats. I wanted a colorful aircraft, though, and settled for a machine of the 358th FG. This group actually flew Thunderbolts in the 365-367th Squadrons, and I found several profiles of these gaudy things.
Common to all of them was an orange tail and a dark blue back, while the engine cowling would be decorated with a red front and the air outlets would carry bands in red, white and blue, with lots of tiny stars sprinkled upon. Furthermore, I found specimen with white cowlings behind the red front end, or even yellow cowlings. Pretty cool.
I tried to mimic this look. The model was basically painted with Aluminum Metallizer (Humbrol 27002) overall. The effect is really good, even without rubbing treatment. Some panels were contrasted with Aluminium Plate and Polished Steel Metallizer (Modelmaster), as well as with Aluminum (Humbrol 56, which is rather a metallic grey). The latter was also used on the landing gear. The anti-glare panel in front of the cockpit was painted with Olive Drab (ANA 613 from Modelmaster).
Since there is no air intake opening on the inline engine I decided to paint the spinner in bright red (Humbrol 19), and tried to incorporate the white and blue theme with stars decoration to the rest of the nose. As a convenient coincidence, I found decals from an Italeri B-66 in the stash: it features a version with dark blue jet air intake decorations in the right size, colors and style for what I had been looking for. So, instead of painting everything by hand I decided to incorporate this decal option.
The area behind the spinner was painted white and then the B-66 decals applied to the front flanks. The radiator air intake scoop had to be cut out, but the overall size and shape were a very good match. Even the transition into the blue spine and cockpit area worked well!
The tail was painted with Humbrol 18, later some shading with Humbrol 82 was added. The blue spine was done with a mix of Humbrol 104 and 15 (Oxford Blue and Midnight Blue) - not a perfect match for the B-66 decal colors, but after some dirt and weathering these differences would blur.
Cockpit interior was painted in Humbrol 159 (Khaki Drab) and Zinc Chromate Green from Model Master. The landing gear wells received a chrome yellow primer (Humbrol 225 - actually RAF Mid Stone but a perfect match for the task) finish.
For weathering the kit received a rubbing treatment with grinded graphite, which adds a dark, metallic shine and emphasizes the kit’s raised panel lines. Some dry painting with Aluminum was added, too, simulating chipped paint on the leading edges. I also added some oil stains around the engine, and serious soot stains at the exhaust.
Decals were, beyond the B-66 decoration, puzzled together. The aircraft' code 'CH-F[bar]' is another exotic twist, in two ways. The bar under the letter marks a second use of that code within the squadron, and as a difference from normal code placement (normally exclusively on the fuselage) I placed the aircraft's individual code letter on the fin, a practice on some P-51s and a consequence of the relatively large letter decals.
The nose art is a fictional puzzle, consisting of a Czech MiG-21 pin-up from the Pardubice '89 meeting. The “Ohio Express” tag comes from a Tamiya 1:100 F-105 Thunderchief. A neat combination that even matches the overall colors well!
As a final step, a coat of semi matt acrylic varnish was applied, with the exception of the anti glare panel, which became purely matt.
A better XP-47H? Hard to tell, since this kitbashing was a messy and rather crude work, so the overall finish does not look as good as I hoped for. But the lowered spine and the fin root extension adds to a fast look of this thing, more elegant (if that's possible in this case?) than the Razorback prototypes. I can't help, but the finished article looks like an Evel Knievel stunt vehicle? The red spinner looks a bit odd, but I'll leave it this way.
Inside the Multi-Operations Support Building near the Multi-Payload Processing Facility (MPPF) at NASA’s Kennedy Space Center in Florida, a technician prepares to put on a Self-Contained Atmospheric Protective Ensemble (SCAPE) suit inside a changing room on Aug. 16, 2019. SCAPE technicians are practicing putting on the suits for a test simulation of loading propellants into a replicated test tank for Orion. Exploration Ground Systems is preparing for Artemis 1 with a series of hazardous hyper test events at the MPPF. After donning their suits, the technicians will complete a tanking to test the system before Orion arrives for processing. During preparations for launch, these teams will be responsible for loading the Orion vehicle with propellants prior to transportation to the Vehicle Assembly Building, where it will be secured atop the Space Launch System rocket. SCAPE suits are used in operations involving toxic propellants and are supplied with air either through a hardline or through a self-contained environmental control unit. Photo credit: NASA/Isaac Watson
The Air Force's AEHF-4 mission, encapsulated inside a 5-meter payload fairing, is mated to its United Launch Alliance (ULA) Atlas V booster inside the Vertical Integration Facility (VIF) at Cape Canaveral's Space Launch Complex-41. Photo credit: United Launch Alliance
At NASA's Kennedy Space Center in Florida, the transportation canister carrying the STS-135 payload is lifted toward the payload changeout room on Launch Pad 39A's rotating service structure. From there, it will be transferred into Atlantis' cargo bay.
The canister holds the mission's main payload, the Raffaello multi-purpose logistics module, which contains supplies and spare parts for the International Space Station.
STS-135 is the final flight of the Space Shuttle Program.
June 17, 2011
NASA’s Educational Launch of Nanosatellites-19 (ELaNa-19) payload after separation from a Rocket Lab Electron rocket after successful liftoff from Launch Complex-1 at Māhia Peninsula in New Zealand. Launched at 6:33 a.m. UTC on Dec. 17 (1:33 p.m. EST on Dec 16), this marks the first flight of a payload under NASA’s Venture Class Launch Services (VCLS). Managed by NASA’s Launch Services Program at Kennedy Space Center in Florida, VCLS was developed to provide increased access to space specifically for payloads like this, carrying small spacecraft called CubeSats. The successful launch and deployment officially begins the venture-class era.
Inside the Payload Hazardous Servicing Facility at NASA's Kennedy Space Center in Florida, technicians and engineers inspect the Origins, Spectral Interpretation, Resource Identification, Security--Regolith Explorer, or OSIRIS-REx spacecraft. Targeted for liftoff Sept. 8, 2016, aboard a United Launch Alliance Atlas V rocket, OSIRIS-Rex will be the first U.S. mission to sample an asteroid, retrieve at least two ounces of surface material and return it to Earth for study. The asteroid, Bennu, may hold clues to the origin of the solar system and the source of water and organic molecules found on Earth.
Photo credit: NASA/ Dimitri Gerondidakis
On June 28, Goddard hosted a Media/VIP/Employee Day to explain the Robotic Refueling Mission (RRM) payload onboard STS-135. The joint effort between NASA and the Canadian Space Agency is designed to demonstrate and test the tools, technologies, and techniques needed to robotically refuel satellites in space. Reporters were also provided an in depth look into how Goddard has provided the communications network for voice, data and video support throughout the shuttle program.
Many visitors where able to try their hand manipulating a replica of the robotic arm that will be used during the Robotic Refueling Mission operations.
Credit: NASA/GSFC/Pat Izzo
NASA Goddard Space Flight Center enables NASA’s mission through four scientific endeavors: Earth Science, Heliophysics, Solar System Exploration, and Astrophysics. Goddard plays a leading role in NASA’s accomplishments by contributing compelling scientific knowledge to advance the Agency’s mission.
Follow us on Twitter
Like us on Facebook
Find us on Instagram
A bi-sector half of the payload fairing for a United Launch Alliance Delta II rocket is lifted up the side of the mobile service tower on Space Launch Complex 2 at Vandenberg Air Force Base in California. Preparations are underway for launch of the Joint Polar Satellite System (JPSS-1) spacecraft in 2017. JPSS-1 is part of the next-generation environmental satellite system, a collaborative program between the National Oceanic and Atmospheric Administration (NOAA) and NASA. To learn more about JPSS-1, visit www.jpss.noaa.gov. Photo credit: NASA/Randy Beaudoin
Inside the Payload Hazardous Servicing Facility at NASA's Kennedy Space Center in Florida, engineers and technicians prepare to install a NanoRack on a Cygnus cargo spacecraft. The Cygnus will be launched to the International Space Station, or ISS, on the upcoming Orbital ATK Commercial Resupply Services-6 mission delivering hardware and supplies to the orbiting outpost. A NanoRack is a low-cost research platform for payloads on the U.S. National Laboratory on the ISS. Based on CubeSats, the standardized minilabs allow low cost use by researchers and commercial customers, as well as elementary schools, high schools and universities.
Photo credit: NASA/Ben Smegelsky
Another old Front Loader that was sitting waiting to be fixed and put back to work.
Taken at Hamilton, Victoria in 2013.
Inside the Payload Hazardous Servicing Facility at NASA's Kennedy Space Center in Florida, technicians and engineers rotate the Origins, Spectral Interpretation, Resource Identification, Security--Regolith Explorer, or OSIRIS-REx spacecraft for testing. Targeted for liftoff Sept. 8, 2016, aboard a United Launch Alliance Atlas V rocket, OSIRIS-Rex will be the first U.S. mission to sample an asteroid, retrieve at least two ounces of surface material and return it to Earth for study. The asteroid, Bennu, may hold clues to the origin of the solar system and the source of water and organic molecules found on Earth.
Photo credit: NASA/ Dimitri Gerondidakis
KENNEDY SPACE CENTER, Fla. -A worker in the Payload Hazardous Servicing Facility pauses during checkout of one of the two Mars Exploration Rovers, MER-2. MER-1 and MER-2, their aeroshells and landers will undergo a full mission simulation before being integrated. After spin balance testing, each spacecraft will be mated to a solid propellant upper stage booster that will propel the spacecraft out of Earth orbit. Approximately 10 days before launch they will be transported to the launch pad for mating with their respective Boeing Delta II rockets. The rovers will serve as robotic geologists to seek answers about the evolution of Mars, particularly for a history of water. The rovers are identical to each other, but will land at different regions of Mars. Launch of the first rover is scheduled for May 30 from Cape Canaveral Air Force Station. The second will follow June 25. Image from NASA, originally appeared on this site: science.ksc.nasa.gov/gallery/photos/ Reposted by San Diego Air and Space Museum
The Air Force's AEHF-4 mission, encapsulated inside a 5-meter payload fairing, is mated to its United Launch Alliance (ULA) Atlas V booster inside the Vertical Integration Facility (VIF) at Cape Canaveral's Space Launch Complex-41. Photo credit: United Launch Alliance
Inside a clean room in Building 1555 at Vandenberg Air Force Base in California, technicians complete installation of the second half of the Northrop Grumman Pegasus XL payload fairing around NASA's Ionospheric Connection Explorer (ICON) on Oct. 4, 2018. ICON is being prepared for its launch on the Pegasus XL, which is attached to the company's L-1011 Stargazer aircraft, from the Skid Strip at Cape Canaveral Air Force Station in Florida. Launch is scheduled for Oct. 26. ICON will study the frontier of space - the dynamic zone high in Earth's atmosphere where terrestrial weather from below meets space weather above. The explorer will help determine the physics of Earth's space environment and pave the way for mitigating its effects on our technology, communications systems and society. Photo credit: NASA/Dan Quinajon
In June 1938, Lockheed began design work on an airliner to satisfy a Transcontinental Western & Air (later Trans-World Airlines) (TWA), requirement for a non-stop transcontinental airliner with a 3,500-mile range and 6,000 lb. payload capability. Construction of a prototype began in 1940. The U.S. was soon involved in the Second World War and all transport production was directed to military needs and consequently the prototype first flew on January 9, 1943, as a military aircraft. Hydraulic-powered controls were used, full feathering and reversing propellers were also installed. First known by its civil designator as Model 049, it soon became better known during wartime by its military designation, the C-69 Constellation. Improvements were steadily made, beginning with the L-649, which was the first Constellation built as a commercial type and the L-749 which was the long-range version of the 649.
The next stage in development led to the L-1049 Super Constellation. The first prototype Super Constellation was a "stretched" version of the original Model 049 (C-69), modified by lengthening the fuselage from 95’ 2" to 113’ 7", adding more fuel capacity, more powerful engines, higher gross weight, and increasing its tourist-class seating from 69 to 92. These L-1049 aircraft were powered by four 2700 hp Wright engines. The prototype aircraft was first flown on October 13, 1950. The production version of the Model L-1049, of which fourteen were built for Eastern Airlines, and ten for TWA, ended up with a strengthened fuselage, stiffened outer wing panels and rectangular windows instead of the Constellation’s round ones. This production version was first flown on July 14, 1951, and the type entered service on December 7, 1951, with Eastern Airlines (EAL). The last Model 1049 produced was delivered in September 1952. Passenger accommodations on the 1049 varied - 88 for Eastern; 65 over water or 75 domestic for TWA, with adaptation to 102 in high density configuration. The flight crew consisted of three, with two cabin attendants.
The Model 1049 was followed by an A version (military WV-2, WV-3, and RC-121D) the B version (USN R7V-1, USAF RC-121C, the presidential VC-121E), and the C version, the first commercial transport certificated with turbo-compound engines. These Double Cyclone Wright engines had three "blow-down" turbines, which converted the heat energy of exhaust gases into additional power, with a 20% reduction in fuel consumption.
The engine produced 3,250 h.p. for take-off for which the aircraft weight had been increased to 133,000 lb. The Model 1049C, Turbo-Cyclone-powered Super Constellation began flight trials on February 17, 1953. A convertible model, the 1049D was built for Seaboard and Western Airlines in 1954. They were fitted with reinforced flooring and they had main deck cargo loading doors on the part side of the fuselage, fore and aft of the wings. They could carry either 18 tons of freight or up to 104 passengers. Maximum take—off weight was 135,400 lb. A Model 1049E was delivered between May 1954 and April 1955 which was identical to the 1049C but with the increased take-off and landing weight of the 1049D. Next on the model list was the Model 1049F, which was Lockheed’s designation for 33 C-121C cargo/personnel transports built for the USAF and fitted with stronger landing gear. The F was followed by a "G" model which was determined to be the most successful version of the Super Constellation. It was powered by 3,400 h.p. engines, it had longer range than the E, and the maximum take-off weight was increased to 137,500 lb. with some models modified to 140,000 lb. Often known as Super Gs, 42 of these aircraft were delivered to domestic carriers (20 to TWA, 10 to EAL, and 4 to NW), and 50 to foreign carriers. The final version to the Super Constellation was the Model 1049H, a combination of Model 1049D, and the convertible and improved Model 1049G.
The Super Constellation and its derivatives represent, along with the Douglas DC-7, the ultimate step in the development of longer range, more capacity and more powerful piston-engined aircraft to meet the needs of both commercial and military aviation. Eastern Air Lines, the first airline to order Super Constellations, introduced the type on its New York-Miami route on December 15, 1951. It was able to take advantage of the 1049s additional capacity to absorb an increased holiday seasonal demand. A decade later on April 30, 1961, Eastern inaugurated its revolutionary air shuttle, no-reservation service, Washington-New York-Boston with Super Constellations. Incidentally, as it turns out, the last use of the Super Constellations by a major U.S. domestic airline was a backup for the shuttle until February 1968.
TWA, a co-sponsor with EAL on the design of the Super Constellation, first used the Model 1049 on its domestic network in September 1952, and when it received the higher performance "C" version, it began scheduled non-stop transcontinental service on October 19, 1953, a first for the industry. On its trans-Atlantic routes, TWA made use of its early Super Constellation models, but on November 1, 1955, it could offer improved service, using its newer Model l049Gs which enabled it to operate non-stop most of the time, at least in the eastbound direction.
Over the Atlantic and other long distance routes, the Super Constellation was also operated by several former Constellation operators, until Lockheed was again challenged by Douglas and its DC-7C, the first aircraft capable of flying non-stop in both directions over the North Atlantic. To compete, Lockheed responded by mating the Super Constellation’s fuselage and tail surfaces with an entirely new wing, resulting in a major redesign. The outcome, the Model 1649A Starliner, which entered service on June 1, 1957, it was the most attractive of the Constellation series, but its success was short lived for in six months it was overtaken in 1958 by the faster, turbine-powered (Bristol Britannia) and jet aircraft (the Boeing 707-120) which finally made all propeller-driven aircraft obsolescent in October 1958. A total of 44 Lockheed L-1649As were built, 29 went to TWA, 10 to Air France, 4 to Lufthansa.
When the age of piston-powered passenger transport aircraft was coming to a close, Lockheed offered to carriers a convertible Model 1049H, suggesting that when they were no longer competitive in the passenger market they could convert to carrying cargo. This second hand market did materialize briefly with the H model but the market for 1049s soon dried up as they were becoming too expensive to operate and maintain. The engines were giving problems not only in the Lockheed Super Connies, but also in the Douglas DC-7s, and the aircraft were becoming known as the "world’s best trimotors." A total of 579 Super Constellations were built but by the end of 1980 only four Super Constellations remained in airline service..
The Museum’s Lockheed C-121C (1049F-55-96), with former Air Force serial number 54-177, and now registered N-1104W, is one of the thirty-three C-l2lCs delivered to the USAF and the Atlantic Division of the Military Air Transport Service at Charleston AFB, South Carolina. This airplane arrived there in March 1956 and was assigned to the 1608th Air Transport Wing. Its original configuration was that of an over-water cargo/passenger transport, having eight crew members and accommodations for up to 80 passengers.
While with the 1608th ATW, the "Super Connies" flew throughout the Caribbean, made crossings of the North and South Atlantic to Europe, the Mediterranean, the Middle East and as far east as India. They participated in the Hungarian airlift during 1956-57, carrying refugees from Eastern Europe to the U.S. and flew troops to Lebanon during the crisis there in 1958. In general, this "Connie" and others of the unit flew a variety of transport missions including cargo, passenger, medical evacuation, and humanitarian support.
On October 30, 1962, the Museum’s C-121C left the regular USAF and was transferred to the 183rd Air Transport Squadron of the Mississippi Air National Guard. This unit was re-designated the 183rd Military Airlift Squadron as of January 1, 1966. While with the 183rd, it flew transport, evacuation, and support missions across the North Atlantic. It remained with the Guard unit until April 19, 1967, at which time it was transferred to the West Virginia ANG and the 167th Military Airlift Squadron. This and other C-l2lCs of this unit flew across the Atlantic and Pacific Oceans, the Caribbean, and to South America, taking part in operation "Creek Guardlift" in Europe from June 1971 to March 1972.
This Super Constellation served with the 167th until 1972 and was again transferred, this time to the 193rd Tactical Electronic Warfare (TEW) Squadron, Pennsylvania ANG, at Olmstead AFB, Middletown, Pennsylvania. This squadron had one other C-121, an electronic countermeasure configured aircraft. Together they took part in many exercises and training missions such as "Reforger VI," "Flintlock" and "Northern Merger" in 1974. While operating out of Ramey AFB in Puerto Rico, they took part in "Gallant Shield" and "Solid Shield," both in 1975.
This "Connie" remained with the 193rd and operations with the ANG until November 1977, when it was retired after 21½ years of military service, thousands of flying hours, and countless ocean crossings, which for propeller driven aircraft were long endurance flights often exceeding 12 or 14 hours. When taken out of service, it was transferred to the Military Aircraft Storage and Disposition Center (MASDC), at Davis Monthan AFB, Arizona, for storage. It remained there until August 1981, at which time it was sold at auction to Ascher Ward of Classic Air Inc., and flown to Van Nuys Airport, California, where the new company was forming. As a civil aircraft in a hoped-for new career, it was assigned FAA registration number Nll04W. It retained its 193rd TEW paint scheme of a royal blue cheat-line outlined in gold, with a white cabin roof and empennage, and pale blue under surfaces. It carried its small serial number on the left side under the stabilizer and a U.S. flag on the center fin.
The newly formed company Classic Air Inc., which intended to operate two or three passenger—carrying "Connies" between Los Angeles and Reno, Nevada, failed to receive FAA approval and the airplanes remained dormant. At this time the National Air and Space Museum was seeking a Super Constellation. Mr. Darryl Greenameyer soon became a party to this transaction as he had acquired two of the Constellations from Air Classics. He negotiated a trade with NASM a C-121C, NllO4W in exchange for two Grumman HU-16 Albatrosses drawn from the remaining holdings of spare Albatross belonging to the Smithsonian, and which had been used in support of one Albatross that was operated by the Museum of Natural History.
A technician performs an inspection of the United Launch Alliance Atlas V payload fairings as they are secured around NOAA’s Geostationary Operational Environmental Satellite-T (GOES-T) inside the Astrotech Space Operations facility in Titusville, Florida, on Feb. 7, 2022. The payload fairings will secure and protect the satellite during launch.
GOES-T is scheduled to launch on March 1, 2022, atop the Atlas V 541 rocket from Space Launch Complex 41 at Cape Canaveral Space Force Station.
GOES-T is the third satellite in the GOES-R series ― the Western Hemisphere's most advanced weather-observing and environmental monitoring system. Data from GOES-T will help meteorologists see the big picture as well as read the fine print, providing critical real-time information before, during and after severe weather and disasters strike.
The launch is being managed by NASA’s Launch Services Program based at Kennedy Space Center in Florida, America’s multi-user spaceport.
Photo credit: NASA/Ben Smegelsky
A forklift is used to load the Robotic Refueling Mission-3 (RRM3) payload onto a truck at the Fuel Transfer Building for transport to the SpaceX facility on Oct. 30, 2018, at NASA's Kennedy Space Center in Florida. The payload will be carried to the International Space Station on SpaceX's 16th Commercial Resupply Services mission. RRM3 demonstrates the transfer of xenon gas and liquid methane in microgravity, and advances technologies for storing and manipulating these cryogenic fuels robotically. RRM3 also supports development of technology for the Restore-L mission, a robotic spacecraft equipped to service satellites in-orbit. Photo credit: NASA/Cory Houston
KENNEDY SPACE CENTER, FLA. In the Payload Hazardous Servicing Facility at NASAs Kennedy Space Center, engineers move the gimbal closer to the Mars Reconnaissance Orbiter (MRO) in the background. The gimbal will be installed on the MRO solar panel. A gimbal is an appliance that allows an object to remain horizontal even as its support tips. In the PHSF, the spacecraft will undergo multiple mechanical assembly operations and electrical tests to verify its readiness for launch. A major deployment test will check out the spacecrafts large solar arrays. The MRO was built by Lockheed Martin for NASAs Jet Propulsion Laboratory in California. It is the next major step in Mars exploration and scheduled for launch from Cape Canaveral Air Force Station in a window opening Aug. 10. The MRO is an important next step in fulfilling NASAs vision of space exploration and ultimately sending human explorers to Mars and beyond. Image from NASA, originally appeared on this site: science.ksc.nasa.gov/gallery/photos/ Reposted by San Diego Air and Space Museum
The Air Force's AEHF-4 mission, encapsulated inside a 5-meter payload fairing, is mated to its United Launch Alliance (ULA) Atlas V booster inside the Vertical Integration Facility (VIF) at Cape Canaveral's Space Launch Complex-41. Photo credit: United Launch Alliance
The fiberglass section of the extended Telstar Logistics LOC IV rocket holds Fredrick Taylor's Principles of Scientific Management and Dilbert’s Pointy-Haired Boss, provided by a management conference that needed to blow them up.
I put a little extra gunpowder to singe the Boss, but alas, it popped the nose cone off so powerfully that the shock cord ripped in half (I don’t know how I forgot to plan for that… must have been bad process control). So the parachute left with the nose cone, and the heavy rocket returned ballistic as a big lawn dart.
• Launch video through "separation" and “coming in hot”
Amazingly, the G-Wiz LCX computer survived, beeping out the altitude reached. Almost everything else was destroyed by the G-forces of impact. All epoxy joints ripped apart, metal bolts ripped through wood bulkhead plate, even the Duracell battery deformed, but kept on ticking. G-Wiz makes one tough computer!
The Animal Motor Works motor also looks like it survived, and of course, the nose cone and parachute drifted softly back down wind.
• Remains of the Day “recovery” video
Inside the Payload Hazardous Servicing Facility at NASA's Kennedy Space Center in Florida, technicians and engineers test the release of the solar array deployment mechanism a on the Origins, Spectral Interpretation, Resource Identification, Security--Regolith Explorer, or OSIRIS-REx spacecraft. Targeted for liftoff Sept. 8, 2016, aboard a United Launch Alliance Atlas V rocket, OSIRIS-Rex will be the first U.S. mission to sample an asteroid, retrieve at least two ounces of surface material and return it to Earth for study. The asteroid, Bennu, may hold clues to the origin of the solar system and the source of water and organic molecules found on Earth.
Photo credit: NASA/Kim Shiflett
The payload canister containing the multi-purpose logistics module Leonardo for the STS-131 mission is nestled in the payload changeout room at Launch Pad 39A. The rotating service structure was rolled back from around space shuttle Discovery for the payload delivery.
March 19, 2010
Inside the Payload Hazardous Servicing Facility at NASA's Kennedy Space Center in Florida, the agency’s Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer, or OSIRIS-REx spacecraft undergoes final inspections and checkouts prior to encapsulation in its payload fairing. Targeted for liftoff Sept. 8, 2016, OSIRIS-Rex will be the first U.S. mission to sample an asteroid, retrieve at least two ounces of surface material and return it to Earth for study. The asteroid, Bennu, may hold clues to the origin of the solar system and the source of water and organic molecules found on Earth.
Photo credit: NASA/Glenn Benson
In the SpaceX Payload Processing Facility at Vandenberg Air Force Base in California, scientists and engineers are completing encapsulation of the Jason-3 satellite in its payload fairing. Once the encapsulating is complete, it will be mated to a SpaceX Falcon 9 rocket at Vandenberg's Space Launch Complex 4. Built by Thales Alenia of France, Jason-3 will measure the topography of the ocean surface for a four-agency international partnership consisting of NOAA, NASA, Centre National d’Etudes Spatiales, France’s space agency, and the European Organization for the Exploitation of Meteorological Satellites.
Photo credit: NASA/Thiep Nguyen and Christopher Wiant
The Educational Launch of Nanosatellites 19 (ELaNa 19) payload is encapsulated inside the Rocket Lab Electron rocket payload fairing on Dec. 1, 2018, at the company’s facility in New Zealand. The ELaNa 19 payload comprises 10 CubeSats selected through NASA’s CubeSat Launch Initiative. The liftoff marks the debut of the agency’s innovative Venture Class Launch Services (VCLS) effort. Managed by NASA’s Launch Services Program at Kennedy Space Center in Florida, VCLS was developed to offer small payloads dedicated rides to space.
In the SpaceX Payload Processing Facility at Vandenberg Air Force Base in California, the Jason-3 satellite is prepared for encapsulation in its payload faring. Launched by a SpaceX Falcon 9 rocket, Jason-3 will be the fourth in a series of spacecraft providing scientists with essential information about global and regional changes in the seas.
Photo credit: NASA