View allAll Photos Tagged based
View from the interior of a former security booth looking towards the crumbling remains of a long disused army base, Truganina, Victoria
In diesem Jahr wurden wieder Demonstrationen und Kundgebungen an der Air Base Ramstein durchgeführt.
In diesem Jahr wurden ergänzend ein Zufahrt zur Air Base für eine dreiviertel Stunde blockiert und erst nach dreimaliger Aufforderung durch die Polizei aufgegeben.
Stopp AIR BASE Ramstein!
Drohnen töten täglich in vielen Teilen der Welt unschuldige Zivilisten. Die U.S. Air Base in Ramstein spielt eine Schlüsselrolle bei völkerrechtswidrigen Einsätzen, ohne sie wäre der weltweite Drohnenkrieg unmöglich.
Military bases worldwide are a backbone of global warfare.
Mainly the USA have huge armed forces and warfare material in other countries, including atomic bombs.
In the meantime no other country in the world has so many foreign soldiers, family afliates and civil contractors like Germany. These people and facilities are mainly located in the greater region of Kaiserslautern.
Therefore a central part of the action days by “Stopp Air Base Ramstein” was an international congress about military bases.
The well-atended event provided important impulses that will lead to a new networking of the long-standing worldwide resistance against military bases.
This anthology contains contributions from the ongress itself, as well as other materials that illustrate the worldwide diversity of resistance.
Inspired by Shaun D's superb photos of the newly refurbished Liverpool Library, I went to see it for myself. It is a most wonderful asset to the city, the architecture inside and out is truly fabulous, and the books contained within are a source of knowledge that can't be equalled by the internet in terms of the experience.
+++ DISCLAIMER +++
Nothing you see here is real, even though the conversion or the presented background story might be based historical facts. BEWARE!
Some background:
In the late 1970s the Mikoyan OKB began development of a hypersonic high-altitude reconnaissance aircraft. Designated "Izdeliye 301" (also known as 3.01), the machine had an unusual design, combining a tailless layout with variable geometry wings. The two engines fueled by kerosene were located side by side above the rear fuselage, with the single vertical fin raising above them, not unlike the Tu-22 “Blinder” bomber of that time, but also reminiscent of the US-American SR-71 Mach 3 reconnaissance aircraft.
Only few and rather corny information leaked into the West, and the 301 was believed not only to act as a reconnaissance plane , it was also believed to have (nuclear) bombing capabilities. Despite wind tunnel testing with models, no hardware of the 301 was ever produced - aven though the aircraft could have become a basis for a long-range interceptor that would replace by time the PVO's Tupolew Tu-28P (ASCC code "Fiddler"), a large aircraft armed solely with missiles.
Despite limitations, the Tu-28P served well in its role, but the concept of a very fast interceptor aircraft, lingered on, since the Soviet Union had large areas to defend against aerial intruders, esp. from the North and the East. High speed, coupled with long range and the ability to intercept an incoming target at long distances independently from ground guidance had high priority for the Soviet Air Defence Forces. Even though no official requirement was issued, the concept of Izdeliye 301 from the Seventies was eventually developed further into the fixed-wing "Izdeliye 701" ultra-long-range high-altitude interceptor in the 1980ies.
The impulse for this new approach came when Oleg S. Samoylovich joined the Mikoyan OKB after having worked at Suchoi OKB on the T-60S missile carrier project. Similar in overall design to the former 301, the 701 was primarily intended as a kind of successor for the MiG-31 Foxhound for the 21st century, which just had completed flight tests and was about to enter PVO's front line units.
Being based on a long range cruise missile carrier, the 701 would have been a huge plane, featuring a length of 30-31m, a wing span of 19m (featuring a highly swept double delta wing) and having a maximum TOW of 70 tons! Target performance figures included a top speed of 2.500km/h, a cruising speed of 2.100km/h at 17.000m and an effective range of 7.000km in supersonic or 11.000km in subsonic mode. Eventually, the 701 program was mothballed, too, being too ambitious and expensive for a specialized development that could also have been a fighter version of the Tu-22 bomber!
Anyway, while the MiG-31 was successfully introduced in 1979 and had evolved in into a capable long-range interceptor with a top speed of more than Mach 3 (limited to Mach 2.8 in order to protect the aircraft's structural integrity), MiG OKB decided in 1984 to take further action and to develop a next-generation technology demonstrator, knowing that even the formidable "Foxhound" was only an interim solution on the way to a true "Four plus" of even a 6th generation fighter. Other new threats like low-flying cruise missiles, the USAF's "Project Pluto" or the assumed SR-71 Mach 5 successor “Aurora” kept Soviet military officials on the edge of their seats, too.
Main objective was to expand the Foxhound's state-of the-art performance, and coiple it with modern features like aerodynamic instability, supercruise, stealth features and further development potential.
The aircraft's core mission objectives comprised:
- Provide strategic air defense and surveillance in areas not covered by ground-based air defense systems (incl. guidance of other aircraft with less sophisticated avionics)
- Top speed of Mach 3.2 or more in a dash and cruise at Mach 3.0 for prolonged periods
- Long range/high speed interception of airspace intruders of any kind, including low flying cruise missiles, UAVs and helicopters
- Intercept cruise missiles and their launch aircraft from sea level up to 30.000m altitude by reaching missile launch range in the lowest possible time after departing the loiter area
Because funding was scarce and no official GOR had been issued, the project was taken on as a private venture. The new project was internally known as "Izdeliye 710" or "71.0". It was based on both 301 and 701 layout ideas and the wind tunnel experiences with their unusual layouts, as well as Oleg Samoylovich's experience with the Suchoi T-4 Mach 3 bomber project and the T-60S.
"Izdeliye 710" was from the start intended only as a proof-of-concept prototype, yet fully functional. It would also incorporate new technologies like heat-resistant ceramics against kinetic heating at prolonged high speeds (the airframe had to resist temperatures of 300°C/570°F and more for considerable periods), but with potential for future development into a full-fledged interceptor, penetrator and reconnaissance aircraft.
Overall, “Izdeliye 710" looked like a shrinked version of a mix of both former MiG OKB 301 and 701 designs, limited to the MiG-31's weight class of about 40 tons TOW. Compared with the former designs, the airframe received an aerodynamically more refined, partly blended, slender fuselage that also incorporated mild stealth features like a “clean” underside, softened contours and partly shielded air intakes. Structurally, the airframe's speed limit was set at Mach 3.8.
From the earlier 301 design,the plane retained the variable geometry wing. Despite the system's complexity and weight, this solution was deemed to be the best approach for a combination of a high continuous top speed, extended loiter time in the mission’s patrol areas and good performance on improvised airfields. Minimum sweep was a mere 10°, while, fully swept at 68°, the wings blended into the LERXes. Additional lift was created through the fuselage shape itself, so that aerodynamic surfaces and therefore drag could be reduced.
Pilot and radar operator sat in tandem under a common canopy with rather limited sight. The cockpit was equipped with a modern glass cockpit with LCD screens. The aircraft’s two engines were, again, placed in a large, mutual nacelle on the upper rear fuselage, fed by large air intakes with two-dimensional vertical ramps and a carefully modulated airflow over the aircraft’s dorsal area.
Initially, the 71.0 was to be powered by a pair of Soloviev D-30F6 afterburning turbofans with a dry thrust of 93 kN (20,900 lbf) each, and with 152 kN (34,172 lbf) with full afterburner. These were the same engines that powered the MiG-31, but there were high hopes for the Kolesov NK-101 engine: a variable bypass engine with a maximum thrust in the 200kN range, at the time of the 71.0's design undergoing bench tests and originally developed for the advanced Suchoj T-4MS strike aircraft.
With the D-30F6, the 71.0 was expected to reach Mach 3.2 (making the aircraft capable of effectively intercepting the SR-71), but the NK-101 would offer in pure jet mode a top speed in excess of Mach 3.5 and also improve range and especially loiter time when running as a subsonic turbofan engine.
A single fin with an all-moving top and an additional deep rudder at its base was placed on top of the engine nacelle. Additional maneuverability at lower speed was achieved by retractable, all-moving foreplanes, stowed in narrow slits under the cockpit. Longitudinal stability at high speed was improved through deflectable stabilizers: these were kept horizontal for take-off and added to the overall lift, but they could be folded down by up to 60° in flight, acting additionally as stabilizer strakes.
Due to the aircraft’s slender shape and unique proportions, the 71.0 quickly received the unofficial nickname "жура́вль" (‘Zhurávl' = Crane). The aircaft’s stalky impression was emphasized even more through its unusual landing gear arrangement: Due to the limited internal space for the main landing gear wells between the weapons bay, the wing folding mechanisms and the engine nacelle, MiG OKB decided to incorporate a bicycle landing gear, normally a trademark of Yakovlew OKB designs, but a conventional landing gear could simply not be mounted, or its construction would have become much too heavy and complex.
In order to facilitate operations from improvised airfields and on snow the landing gear featured twin front wheels on a conventional strut and a single four wheel bogie as main wheels. Smaller, single stabilizer wheels were mounted on outriggers that retracted into slender fairings at the wings’ fixed section trailing edge, reminiscent of early Tupolev designs.
All standard air-to-air weaponry, as well as fuel, was to be carried internally. Main armament would be the K-100 missile (in service eventually designated R-100), stored in a large weapons bay behind the cockpit on a rotary mount. The K-100 had been under development at that time at NPO Novator, internally coded ‘Izdeliye 172’. The K-100 missile was an impressive weapon, and specifically designed to attack vital and heavily defended aerial targets like NATO’s AWACS aircraft at BVR distance.
Being 15’ (4.57 m) long and weighing 1.370 lb (620 kg), this huge ultra-long-range weapon had a maximum range of 250 mi (400 km) in a cruise/glide profile and attained a speed of Mach 6 with its solid rocket engine. This range could be boosted even further with a pair of jettisonable ramjets in tubular pods on the missile’s flanks for another 60 mi (100 km). The missile could attack targets ranging in altitude between 15 – 25,000 meters.
The weapon would initially be allocated to a specified target through the launch aircraft’s on-board radar and sent via inertial guidance into the target’s direction. Closing in, the K-100’s Agat 9B-1388 active seeker would identify the target, lock on, and independently attack it, also in coordination with other K-100’s shot at the same target, so that the attack would be coordinated in time and approach directions in order to overload defense and ensure a hit.
The 71.0’s internal mount could hold four of these large missiles, or, alternatively, the same number of the MiG-31’s R-33 AAMs. The mount also had a slot for the storage of additional mid- and short-range missiles for self-defense, e .g. three R-60 or two R-73 AAMs. An internal gun was not considered to be necessary, since the 71.0 or potential derivatives would fight their targets at very long distances and rather rely on a "hit-and-run" tactic, sacrificing dogfight capabilities for long loitering time in stand-by mode, high approach speed and outstanding acceleration and altitude performance.
Anyway, provisions were made to carry a Gsh-301-250 gun pod on a retractable hardpoint in the weapons bay instead of a K-100. Alternatively, such pods could be carried externally on four optional wing root pylons, which were primarily intended for PTB-1500 or PTB-3000 drop tanks, or further missiles - theoretically, a maximum of ten K-100 missiles could be carried, plus a pair of short-range AAMs.
Additionally, a "buddy-to-buffy" IFR set with a retractable drogue (probably the same system as used on the Su-24) was tested (71.2 was outfitted with a retractable refuelling probe in front of the cockpit), as well as the carriage of simple iron bombs or nuclear stores, to be delivered from very high altitudes. Several pallets with cameras and sensors (e .g. a high resolution SLAR) were also envisioned, which could easily replace the missile mounts and the folding weapon bay covers for recce missions.
Since there had been little official support for the project, work on the 710 up to the hardware stage made only little progress, since the MiG-31 already filled the long-range interceptor role in a sufficient fashion and offered further development potential.
A wooden mockup of the cockpit section was presented to PVO and VVS officials in 1989, and airframe work (including tests with composite materials on structural parts, including ceramic tiles for leading edges) were undertaken throughout 1990 and 1991, including test rigs for the engine nacelle and the swing wing mechanism.
Eventually, the collapse of the Soviet Union in 1991 suddenly stopped most of the project work, after two prototype airframes had been completed. Their internal designations were Izdeliye 71.1 and 71.2, respectively. It took a while until the political situation as well as the ex-Soviet Air Force’s status were settled, and work on Izdeliye 710 resumed at a slow pace.
After taking two years to be completed, 71.1 eventually made its roll-out and maiden flight in summer 1994, just when MiG-31 production had ended. MiG OKB still had high hopes in this aircraft, since the MiG-31 would have to be replaced in the next couple of years and "Izdeliye 710" was just in time for the potential procurement process. The first prototype wore a striking all-white livery, with dark grey ceramic tiles on the wings’ leading edges standing out prominently – in this guise and with its futuristic lines the slender aircraft reminded a lot of the American Space Shuttle.
71.1 was primarily intended for engine and flight tests (esp. for the eagerly awaited NK-101 engines), as well as for the development of the envisioned ramjet propulsion system for full-scale production and further development of Izdeliye 710 into a Mach 3+ interceptor. No mission avionics were initially fitted to this plane, but it carried a comprehensive test equipment suite and ballast.
Its sister ship 71.2 flew for the first time in late 1994, wearing a more unpretentious grey/bare metal livery. This plane was earmarked for avionics development and weapons integration, especially as a test bed for the K-100 missile, which shared Izdeliye 710’s fate of being a leftover Soviet project with an uncertain future and an even more corny funding outlook.
Anyway, aircraft 71.2 was from the start equipped with a complete RP-31 ('Zaslon-M') weapon control system, which had been under development at that time as an upgrade for the Russian MiG-31 fleet being part of the radar’s development program secured financial support from the government and allowed the flight tests to continue. The RP-31 possessed a maximum detection range of 400 km (250 mi) against airliner-sized targets at high altitude or 200 km against fighter-sized targets; the typical width of detection along the front was given as 225 km. The system could track 24 airborne targets at one time at a range of 120 km, 6 of which could be simultaneously attacked with missiles.
With these capabilities the RP-31 suite could, coupled with an appropriate carrier airframe, fulfil the originally intended airspace control function and would render a dedicated and highly vulnerable airspace control aircraft (like the Beriev A-50 derivative of the Il-76 transport) more or less obsolete. A group of four aircraft equipped with the 'Zaslon-M' suite would be able to permanently control an area of airspace across a total length of 800–900 km, while having ultra-long range weapons at hand to counter any intrusion into airspace with a quicker reaction time than any ground-based fighter on QRA duty. The 71.0, outfitted with the RP-31/K-100 system, would have posed a serious threat to any aggressor.
In March 1995 both prototypes were eventually transferred to the Kerchenskaya Guards Air Base at Savasleyka in the Oblast Vladimir, 300 km east of Mocsow, where they received tactical codes of '11 Blue' and '12 Blue'. Besides the basic test program and the RP-31/K-100 system tests, both machines were directly evaluated against the MiG-31 and Su-27 fighters by the Air Force's 4th TsBPi PLS, based at the same site.
Both aircraft exceeded expectations, but also fell short in certain aspects. The 71.0’s calculated top speed of Mach 3.2 was achieved during the tests with a top speed of 3,394 km/h (2.108 mph) at 21,000 m (69.000 ft). Top speed at sea level was confirmed at 1.200 km/h (745 mph) indicated airspeed.
Combat radius with full weapon load and internal fuel only was limited to 1,450 km (900 mi) at Mach 0.8 and at an altitude of 10,000 m (33,000 ft), though, and it sank to a mere 720 km (450 mi) at Mach 2.35 and at an altitude of 18,000 m (59,000 ft). Combat range with 4x K-100 internally and 2 drop tanks was settled at 3,000 km (1,860 mi), rising to 5,400 km (3,360 mi) with one in-flight refueling, tested with the 71.2. Endurance at altitude was only slightly above 3 hours, though. Service ceiling was 22,800 m (74,680 ft), 2.000 m higher than the MiG-31.
While these figures were impressive, Soviet officials were not truly convinced: they did not show a significant improvement over the simpler MiG-31. MiG OKB tried to persuade the government into more flight tests and begged for access to the NK-101, but the Soviet Union's collapse halted this project, too, so that both Izdeliye 710 had to keep the Soloviev D-30F6.
Little is known about the Izdeliye 710 project’s progress or further developments. The initial tests lasted until at least 1997, and obviously the updated MiG-31M received official favor instead of a completely new aircraft. The K-100 was also dropped, since the R-33 missile and later its R-37 derivative sufficiently performed in the long-range aerial strike role.
Development on the aircraft as such seemed to have stopped with the advent of modernized Su-27 derivatives and the PAK FA project, resulting in the Suchoi T-50 prototype. Unconfirmed reports suggest that one of the prototypes (probably 71.1) was used in the development of the N014 Pulse-Doppler radar with a passive electronically scanned array antenna in the wake of the MFI program. The N014 was designed with a range of 420 km, detection target of 250km to 1m and able to track 40 targets while able to shoot against 20.
Most interestingly, Izdeliye 710 was never officially presented to the public, but NATO became aware of its development through satellite pictures in the early Nineties and the aircraft consequently received the ASCC reporting codename "Fastback".
Until today, only the two prototypes have been known to exist, and it is assumed – had the type entered service – that the long-range fighter had received the official designation "MiG-41".
General characteristics:
Crew: 2 (Pilot, weapon system officer)
Length (incl. pitot): 93 ft 10 in (28.66 m)
Wingspan:
- minimum 10° sweep: 69 ft 4 in (21.16 m)
- maximum 68° sweep: 48 ft 9 in (14,88 m)
Height: 23 ft 1 1/2 in (7,06 m )
Wing area: 1008.9 ft² (90.8 m²)
Weight: 88.151 lbs (39.986 kg)
Performance:
Maximum speed:
- Mach 3.2 (2.050 mph (3.300 km/h) at height
- 995 mph (1.600 km/h) supercruise speed at 36,000 ft (11,000 m)
- 915 mph (1.470 km/h) at sea level
Range: 3.705 miles (5.955 km) with internal fuel
Service ceiling: 75.000 ft (22.500 m)
Rate of climb: 31.000 ft/min (155 m/s)
Engine:
2x Soloviev D-30F6 afterburning turbofans with a dry thrust of 93 kN (20,900 lbf) each
and with 152 kN (34,172 lbf) with full afterburner.
Armament:
Internal weapons bay, main armament comprises a flexible missile load; basic ordnance of 4x K-100 ultra long range AAMs plus 2x R-73 short-range AAMs: other types like the R-27, R-33, R-60 and R-77 have been carried and tested, too, as well as podded guns on internal and external mounts. Alternatively, the weapon bay can hold various sensor pallets.
Four hardpoints under the wing roots, the outer pair “wet” for drop tanks of up to 3.000 l capacity, ECM pods or a buddy-buddy refueling drogue system. Maximum payload mass is 9000 kg.
The kit and its assembly
The second entry for the 2017 “Soviet” Group Build at whatifmodelers.com – a true Frankenstein creation, based on the scarce information about the real (but never realized) MiG 301 and 701 projects, the Suchoj T-60S, as well as some vague design sketches you can find online and in literature.
This one had been on my project list for years and I already had donor kits stashed away – but the sheer size (where will I leave it once done…?) and potential complexity kept me from tackling it.
The whole thing was an ambitious project and just the unique layout with a massive engine nacelle on top of the slender fuselage instead of an all-in-one design makes these aircraft an interesting topic to build. The GB was a good motivator.
“My” fictional interpretation of the MiG concepts is mainly based on a Dragon B-1B in 1:144 scale (fuselage, wings), a PM Model Su-15 two seater (donating the nose section and the cockpit, as well as wing parts for the fin) and a Kangnam MiG-31 (for the engine pod and some small parts). Another major ingredient is a pair of horizontal stabilizers from a 1:72 Hasegawa A-5 Vigilante.
Fitting the cockpit section took some major surgery and even more putty to blend the parts smoothly together. Another major surgical area was the tail; the "engine box" came to be rather straightforward, using the complete rear fuselage section from the MiG-31 and adding the intakes form the same kit, but mounted horizontally with a vertical splitter.
Blending the thing to the cut-away tail section of the B-1 was quite a task, though, since I not only wanted to add the element to the fuselage, but rather make it look a bit 'organic'. More than putty was necessary, I also had to made some cuts and transplantations. And after six PSR rounds I stopped counting…
The landing gear was built from scratch – the front wheel comes mostly from the MiG-31 kit. The central bogie and its massive leg come from a VEB Plasticart 1:100 Tu-20/95 bomber, plus some additional struts. The outriggers are leftover landing gear struts from a Hobby Boss Fw 190, mated with wheels which I believe come from a 1:200 VEB Plasticart kit, an An-24. Not certain, though. The fairings are slender MiG-21 drop tanks blended into the wing training edge. For the whole landing gear, the covers were improvised with styrene sheet, parts from a plastic straw(!) or leftover bits from the B-1B.
The main landing gear well was well as the weapons’ bay themselves were cut into the B-1B underside and an interior scratched from sheet and various leftover materials – I tried to maximize their space while still leaving enough room for the B-1B kit’s internal VG mechanism.
The large missiles (two were visible fitted and the rotary launcher just visibly hinted at) are, in fact, AGM-78 ‘Standard’ ARMs in a fantasy guise. They look pretty Soviet, though, like big brothers of the already not small R-33 missiles from the MiG-31.
While not in the focus of attention, the cockpit interior is completely new, too – OOB, the Su-15 cockpit only has a floor and rather stubby seats, under a massive single piece canopy. On top of the front wheel well (from a Hasegawa F-4) I added a new floor and added side consoles, scratched from styrene sheet. F-4 dashboards improve the decoration, and I added a pair of Soviet election seats from the scrap box – IIRC left over from two KP MiG-19 kits.
The canopy was taken OOB, I just cut it into five parts for open display. The material’s thickness does not look too bad on this aircraft – after all, it would need a rather sturdy construction when flying at Mach 3+ and withstanding the respective pressures and temperatures.
Painting
As a pure whif, I was free to use a weirdo design - but I rejected this idea quickly. I did not want a garish splinter scheme or a bright “Greenbottle Fly” Su-27 finish.
With the strange layout of the aircraft, the prototype idea was soon settled – and Soviet prototypes tend to look very utilitarian and lusterless, might even be left in grey. Consequently, I adapted a kind of bare look for this one, inspired by the rather shaggy Soviet Tu-22 “Blinder” bombers which carried a mix of bare metal and white and grey panels. With additional black leading edges on the aerodynamic surfaces, this would create a special/provisional but still purposeful look.
For the painting, I used a mix of several metallizer tones from ModelMaster and Humbrol (including Steel, Magnesium, Titanium, as well as matt and polished aluminum, and some Gun Metal and Exhaust around the engine nozzles, partly mixed with a bit of blue) and opaque tones (Humbrol 147 and 127). The “scheme” evolved panel-wise and step by step. The black leading edges were an interim addition, coming as things evolved, and they were painted first with black acrylic paint as a rough foundation and later trimmed with generic black decal stripes (from TL Modellbau). A very convenient and clean solution!
The radomes on nose and tail and other di-electric panels became dark grey (Humbrol 125). The cockpit tub was painted with Soviet Cockpit Teal (from ModelMaster), while the cockpit opening and canopy frames were kept in a more modest medium grey (Revell 57). On the outside of the cabin windows, a fat, deep yellow sealant frame (Humbrol 93, actually “Sand”) was added.
The weapon bay was painted in a yellow-ish primer tone (seen on pics of Tu-160 bombers) while the landing gear wells received a mix of gold and sand; the struts were painted in a mixed color, too, made of Humbrol 56 (Aluminum) and 34 (Flat White). The green wheel discs (Humbrol 131), a typical Soviet detail, stand out well from the rather subdued but not boring aircraft, and they make a nice contrast to the red Stars and the blue tactical code – the only major markings, besides a pair of MiG OKB logos under the cockpit.
Decals were puzzled together from various sheets, and I also added a lot of stencils for a more technical look. In order to enhance the prototype look further I added some photo calibration markings on the nose and the tail, made from scratch.
A massive kitbashing project that I had pushed away for years - but I am happy that I finally tackled it, and the result looks spectacular. The "Firefox" similarity was not intended, but this beast really looks like a movie prop - and who knwos if the Firefox was not inspired by the same projects (the MiG 301 and 701) as my kitbash model?
The background info is a bit lengthy, but there's some good background info concerning the aforementioned projects, and this aircraft - as a weapon system - would have played a very special and complex role, so a lot of explanations are worthwhile - also in order to emphasize that I di not simply try to glue some model parts together, but rather try to spin real world ideas further.
Mighty bird!
New base is finished, hope you guys like, new video coming out soon, lower floor photos coming out shortly
In a picture only possible during the lightest months of the year, Alpine Travel Leyland Olympian / Alexander G230 VWL heads away from Rhyl Depot to take up a school contract. The bus was new to the Oxford Bus Company but was acquired from ARRIVA The Shires.
The new cable car installed in London Docklands rises from the base station to a height of 200ft on it's way to the North Greenwich Arena.mi had real trouble try to find the right angle for this shot, still not entirely happy but was unable to stand around to long with tight security due to the London 2012 Olympics.
+++ 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 TIE/LN starfighter, or TIE/line starfighter, simply known as the TIE Fighter or T/F, was the standard Imperial starfighter seen in massive numbers throughout most of the Galactic Civil War and onward.
The TIE Fighter was manufactured by Sienar Fleet Systems and led to several upgraded TIE models such as TIE/sa bomber, TIE/IN interceptor, TIE/D Defender, TIE/D automated starfighter, and many more.
The original TIEs were designed to attack in large numbers, overwhelming the enemy craft. The Imperials used so many that they came to be considered symbols of the Empire and its might. They were also very cheap to produce, reflecting the Imperial philosophy of quantity over quality.
However, a disadvantage of the fighter was its lack of deflector shields. In combat, pilots had to rely on the TIE/LN's maneuverability to avoid damage. The cockpit did incorporate crash webbing, a repulsorlift antigravity field, and a high-g shock seat to help protect the pilot, however these did next to nothing to help protect against enemy blaster fire.
Due to the lack of life-support systems, each TIE pilot had a fully sealed flight suit superior to their Rebel counterparts. The absence of a hyperdrive also rendered the light fighter totally dependent on carrier ships when deployed in enemy systems. TIE/LNs also lacked landing gear, another mass-reducing measure. While the ships were structurally capable of "sitting" on their wings, they were not designed to land or disembark their pilots without special support. On Imperial ships, TIEs were launched from racks in the hangar bays.
The high success rate of more advanced Rebel starfighters against standard Imperial TIE Fighters resulted in a mounting cost of replacing destroyed fighters and their pilots. That, combined with the realization that the inclusion of a hyperdrive would allow the fleet to be more flexible, caused the Imperial Navy to rethink its doctrine of using swarms of cheap craft instead of fewer high-quality ones, leading to the introduction of the TIE Advanced x1 and its successor, the TIE Avenger. The following TIE/D Defender as well as the heavy TIE Escort Fighter (or TIE/E) were touted as the next "logical advance" of the TIE Series—representing a shift in starfighter design from previous, expendable TIE models towards fast, well armed and protected designs, capable of hyperspace travel and long-term crew teams which gained experience and capabilities over time.
The TIE/E Escort, was a high-performance TIE Series starfighter developed for the Imperial Navy by Sienar Fleet Systems and it was introduced into service shortly before the Battle of Endor. It was a much heavier counterpart to the agile and TIE/D fighter, and more of an attack ship or even a light bomber than a true dogfighter. Its role were independent long range operations, and in order to reduce the work load and boost morale a crew of two was introduced (a pilot and a dedicated weapon systems officer/WSO). The primary duty profile included attack and escort task, but also reconnoiter missions. The TIE/E shared the general layout with the contemporary TIE/D fighter, but the cockpit section as well as the central power unit were much bigger, and the ship was considerably heavier.
The crew enjoyed – compared with previous TIE fighter designs – a spacious and now fully pressurized cockpit, so that no pressurized suits had to be worn anymore. The crew members sat in tandem under a large, clear canopy. The pilot in front had a very good field of view, while the WSO sat behind him, in a higher, staggered position with only a limited field of view. Both work stations had separate entries, though, and places could not be switched in flight: the pilot mounted the cockpit through a hatch on port side, while the WSO entered the rear compartment through a roof hatch.
In a departure from the design of previous TIE models, instead of two parallel wings to either side of the pilot module, the TIE Escort had three quadanium steel solar array wings mounted symmetrically around an aft section, which contained an I-s4d solar ionization reactor to store and convert solar energy collected from the wing panels. The inclusion of a third wing provided additional solar power to increase the ship's range and the ship's energy management system was designed to allow weapons and shields to be charged with minimum loss of power to the propulsion system.
Although it was based on the standard twin ion engine design, the TIE/E’s propulsion system was upgraded to the entirely new, powerful P-sz9.8 triple ion engine. This allowed the TIE/E a maximum acceleration of 4,220 G or 21 MGLT/s and a top speed of 144 MGLT, or 1,680 km/h in an atmosphere — almost 40 percent faster than a former standard TIE Fighter. With tractor beam recharge power (see below) redirected to the engines, the top speed could be increased to 180 MGLT in a dash.
In addition to the main thrusters located in the aft section, the TIE Escort's triple wing design allowed for three arrays of maneuvering jets and it featured an advanced F-s5x flight avionics system to process the pilot's instructions. Production models received a class 2, ND9 hyperdrive motivator, modified from the version developed for the TIE Avenger. The TIE/E also carried a Sienar N-s6 Navcon navigation computer with a ten-jump memory.
Special equipment included a small tractor beam projector, originally developed for the TIE Avenger, which could be easily fitted to the voluminous TIE Escort. Models produced by Ysanne Isard's production facility regularly carried such tractor beams and the technology found other uses, such as towing other damaged starfighters until they could achieve the required velocity to enter hyperspace. The tractor beam had limited range and could only be used for a short time before stopping to recharge, but it added new tactics, too. For instance, the beam allowed the TIE/E crews to temporarily inhibit the mobility of enemy fighters, making it easier to target them with the ship's other weapon systems, or prevent enemies from clear shots.
The TIE Escort’s weapons systems were primarily designed to engage bigger ships and armored or shielded targets, like armed freighters frequently used by the Alliance. Thanks to its complex weapon and sensor suite, it could also engage multiple enemy fighters at once. The sensors also allowed an effective attack of ground targets, so that atmospheric bombing was a potential mission for the TIE/E, too.
.
The TIE Escort Fighter carried a formidable array of weaponry in two modular weapon bays that were mounted alongside the lower cabin. In standard configuration, the TIE/E had two L-s9.3 laser cannons and two NK-3 ion cannons. The laser and ion cannons could be set to fire separately or, if concentrated power was required, to fire-linked in either pairs or as a quartet.
The ship also featured two M-g-2 general-purpose warhead launchers, each of which could be equipped with a standard load of three proton torpedoes or four concussion missiles. Depending on the mission profile, the ship could be fitted with alternative warheads such as proton rockets, proton bombs, or magnetic pulse warheads.
Additionally, external stores could be carried under the fuselage, which included a conformal sensor pallet for reconnaissance missions or a cargo bay with a capacity for 500 kg (1.100 lb).
The ship's defenses were provided by a pair of forward and rear projecting Novaldex deflector shield generators—another advantage over former standard TIE models. The shields were designed to recharge more rapidly than in previous Imperial fighters and were nearly as powerful as those found on capital ships, so that the TIE/E could engage other ships head-on with a very high survivability. The fighters were not equipped with particle shields, though, relying on the reinforced titanium hull to absorb impacts from matter. Its hull and wings were among the strongest of any TIE series Starfighter yet.
The advanced starfighter attracted the attention of several other factions, and the Empire struggled to prevent the spread of the technology. The ship's high cost, together with political factors, kept it from achieving widespread use in the Empire, though, and units were assigned only to the most elite crews.
The TIE/E played a central role in the Empire's campaign against rogue Grand Admiral Demetrius Zaarin, and mixed Defender and Escort units participated in several other battles, including the Battle of Endor. The TIE Escort continued to see limited use by the Imperial Remnant up to at least 44 ABY, and was involved in numerous conflicts, including the Yuuzhan Vong War..
The kit and its assembly:
Another group build contribution, this time to the Science Fiction GB at whatifmodelers.com during summer 2017. Originally, this one started as an attempt to build a vintage MPC TIE Interceptor kit which I had bought and half-heartedly started to build probably 20 years ago. But I did not have the right mojo (probably, The Force was not strong enough…?), so the kit ended up in a dark corner and some parts were donated to other projects.
The sun collectors were still intact, though, and in the meantime I had the idea of reviving the kit’s remains, and convert it into (what I thought was) a fictional TIE Fighter variant with three solar panels. For this plan I got myself another TIE Interceptor kit, and stashed it away, too. Mojo was still missing, though.
Well, then came the SF GB and I took it as an occasion to finally tackle the build. But when I prepared for the build I found out that my intended design (over the years) more or less actually existed in the Star Wars universe: the TIE/D Defender! I could have built it with the parts and hand and some improvisation, but the design similarity bugged me. Well, instead of a poor copy of something that was more or less clearly defined, I rather decided to create something more individual, yet plausible, from the parts at hand.
The model was to stay a TIE design, though, in order to use as much donor material from the MPC kits as possible. Doing some legwork, I settled for a heavy fighter – bigger than the TIE Interceptor and the TIE/D fighter, a two-seater.
Working out the basic concept and layout took some time and evolved gradually. The creative spark for the TIE/E eventually came through a Revell “Obi Wan’s Jedi Starfighter” snap fit kit in my pile – actually a prize from a former GB participation at phoxim.de (Thanks a lot, Wolfgang!), and rather a toy than a true model kit.
The Jedi Fighter was in so far handy as it carries some TIE Fighter design traits, like the pilot capsule and the characteristic spider web windscreen. Anyway, it’s 1:32, much bigger than the TIE Interceptor’s roundabout 1:50 scale – but knowing that I’d never build the Jedi Starfighter OOB I used it as a donor bank, and from this starting point things started to evolve gradually.
Work started with the cockpit section, taken from the Jedi Starfighter kit. The two TIE Interceptor cockpit tubs were then mounted inside, staggered, and the gaps to the walls filled with putty. A pretty messy task, and once the shapes had been carved out some triangular tiles were added to the surfaces – a detail I found depicted in SW screenshots and some TIE Fighter models.
Another issue became the crew – even though I had two MPC TIE Interceptors and, theorectically, two pilot figures, only one of them could be found and the second crewman had to be improvised. I normally do not build 1:48 scale things, but I was lucky (and happy) to find an SF driver figure, left over from a small Dougram hoovercraft kit (from Takara, as a Revell “Robotech” reboxing). This driver is a tad bigger than the 1:50 TIE pilot, but I went with it because I did not want to invest money and time in alternatives. In order to justify the size difference I decided to paint the Dougram driver as a Chiss, based on the expanded SW universe (with blue skin and hair, and glowing red eyes). Not certain if this makes sense during the Battle of Endor timeframe, but it adds some color to the project – and the cockpit would not be visible in much detail since it would be finished fully closed.
Reason behind the closed canopy is basically the poor fit of the clear part. OOB, this is intended as an action toy – but also the canopy’s considerable size in 1:50 would prevent its original opening mechanism.
Additional braces on the rel. large window panels were created with self-adhesive tape and later painted over.
The rear fuselage section and the solar panel pylons were scratched. The reactor behind the cockpit section is actually a plastic adapter for water hoses, found in a local DIY market. It was slightly modified, attached to the cockpit “egg” and both parts blended with putty. The tail opening was closed with a hatch from the OOB TIE Interceptor – an incidental but perfect match in size and style.
The three pylons are also lucky finds: actually, these are SF wargaming/tabletop props and would normally be low walls or barriers, made from resin. For my build, they were more or less halved and trimmed. Tilted by 90°, they are attached to the hull with iron wire stabilizers, and later blended to the hull with putty, too.
Once the cockpit was done, things moved more swiftly. The surface of the hull was decorated with many small bits and pieces, including thin styrene sheet and profiles, steel and iron wire in various strengths, and there are even 1:72 tank tracks hidden somewhere, as well as protective caps from syringes (main guns and under the rear fuselage). It’s amazing how much stuff you can add to such a model – but IMHO it’s vital in order to create some structure and to emulate the (early) Star Wars look.
Painting and markings:
The less spectacular part of the project, even though still a lot of work because of the sheer size of the model’s surface. Since the whole thing is fictional, I tried to stay true to the Imperial designs from Episode IV-VI and gave the TIE/E a simple, all-light grey livery. All basic painting was done with rattle cans.
Work started with a basic coat of grey primer. On top of that, an initial coat of RAL 7036 Platingrau was added, esp. to the lower surfaces and recesses, for a rough shading effect. Then, the actual overall tone, RAL 7047, called “Telegrau 4”, one of Deutsche Telekom’s corporate tones, was added - mostly sprayed from abone and the sides onto the model. Fuselage and panels were painted separately, overall assembly was one of the final steps.
The solar panels were to stand out from the grey rest of the model, and I painted them with Revell Acrylic “Iron Metallic” (91) first, and later applied a rather rich wash with black ink , making sure the color settled well into the many small cells. The effect is pretty good, and the contrast was slightly enhanced through a dry-brushing treatment.
Only a few legible stencils were added all around the hull (most from the scrap box or from mecha sheets), the Galactic Empire Seal were inkjet-printed at home, as well as some tactical markings on the flanks, puzzled together from single digits in "Aurebash", one of the Imperial SW languages/fonts.
For some variety and color highlights, dozens of small, round and colorful markings were die-punched from silver, yellow, orange, red and blue decal sheet and were placed all over the hull - together with the large panels they blur into the the overall appearance, though. The hatches received thin red linings, also made from generic decals strips.
The cockpit interior was a bit challenging, though. Good TIE Fighter cockpit interior pictures are hard to find, but they suggest a dark grey tone. More confusingly, the MPC instructions call for a “Dark Green” cockpit? Well, I did not like the all-grey option, since the spaceship is already monochrome grey on the outside.
As a compromise I eventually used Tamiya XF-65 "Field Grey". The interior recieved a black ink in and dry-brushing treatment, and some instruments ansd screens were created with black decal material and glossy black paint; some neon paint was used for sci-fi-esque conmtraol lamps everywhere - I did not pay too much intention on the interior, since the cockpit would stay closed, and the thick clear material blurs everything inside.
Following this rationale, the crew was also painted in arather minimal fashion - both wear a dark grey uniform, only the Chiss pilot stands aout with his light blue skin and the flourescent red eyes.
After an overall black ink wash the model received a dry brusing treatment with FS 36492 and FS 36495, for a weathered and battle-worn look. After all, the "Vehement" would not survive the Ballte of Endor, but who knows what became of TIE/E "801"'s mixed crew...?
Finally, the kit was sealed with matt acrylic varnish, and some final cosmetic corrections made.
The display is a DIY creation, too, made from a 6x6" piece of wood, it's edges covered with edgebonder, a steel wire as holder, and finally the display was paited with semi-matt black acrylic paint from the rattle can.
A complex build, and the TIE/E more or less evolved along the way, with only the overall layout in mind. Work took a month, but I think it was worth the effort. This fantasy creation looks pretty plausible and blends well into the vast canonical TIE Fighter family - and I am happy that I finally could finish this mummy project, including the surplus Jedi Starfighter kit which now also find a very good use!
An epic one, and far outside my standard comfort zone. But a wothwhile build!
A view of the base of Trajan's Column. Victorias (Winged Victorys) and other symbols of victory surround the inscription. It reads:
SENATVS POPVLVS QVE ROMANVS IMP CAESARI DIVI NERVAE F NERVAE TRAIANO AVG GERM DACICO PONTIF MAXIMO TRIB POT XVII IMP VI COS VI P P AD DECLARANDVM QVANTAE ALTITVDINIS MONS ET LOCVS TANT ( IS·OPER ) IBVS SIT EGESTVS
A rough translation is:
(From) the Senate and People of Rome to the Divine Emperor Caesar Nerva Trajan Augustus, son of Nerva, (conqueror of) Germany and Dacia, Pontifex Maximus, 17 years Tribune, 6 times Imperator, 6 times Consul, Father of the Nation, who demonstrated that a mountain and a place of huge height could be excavated for this work.
Notably, the inscription refers to the immense construction work directed by Trajan to build his Forum and Market. This seems to reflect what was being emphasized during that period. On the column itself, there are more scenes depicting soldiers doing construction work than in battle.
Rome; July 2019
Once the tower was opened, we were able to get right up to it and climb the stairs inside to the top. Photos available for purchase at Wits End Photography. Follow my blog Traveling at Wits End for ways to create travel adventures everyday.
Base-model Nissan Skyline with aftermarket alloy wheels.
Year: 1989
Series: R31
Engine: 3.0L 6 Cylinder Aspirated
Transmission: 5 Speed Manual
Fuel: LPG
Drive: Rear Wheel Drive
Colour: White
Plate Number: VJK-760 (SA)
Date Registered: 21/08/1992 (not confirmed)
Manhattan 2033
It's like yesterday the earthquake came and distroyed most of the city. It was like hell, death people everywhere. But there were survivors. At least, that how you could say it. We thought it was over when the earthquake stoped. But I am one of the few that know what happened that day. Yes, the earthquake was a disaster, but that's not the only thing that happened. When we got hit, a very dangerous gas came out of the ground. And it turned people into,.... ZOMBIES! So almost all the survivors turned into disgusting little zombies. Only a few are immune to it. I am, and so is my best friend. Be got ourselves a nice base, same for zombies, at least, what you can call save. Our mission is to survive, and survive we will.
----------------------------------------------------------------------------------------------------------------------------------
Ok, so the idea behind this one is basicaly the same as the previous one, but It does look a bit different. Some things I like more, others not. Please tell me if you like this one more or Consequenses of War.
Aslo this is an entry for the Zombie contest over at the LCN!
And thank you Julien for editing this one!
Previous Apoc moc
Consequenses of War:
www.flickr.com/photos/51675614@N05/6100227283/in/photostr...
Thanks, Daan.
From thedailylumenbox.blog LomoChrome Turquoise shot at ISO 100 with Leica Ic and Voigtlander 15mm, Heliar Super Wide. Developed by The Darkroom in San Clemente, CA
Based on the Renault 8, Dinky Toys #517 (1962). Meccano Tri-Ang released this Gordini version #1414 in 1968, together with rare 8S versions. This one was re-issued by Mattel / Atlas two years ago in a Gordini set, also including a yellow 8S and a white Dauphine. The one you see is the french model that I´ve bought in an almost complete but playworn condition back in 1991. I restored it immediately . Even in 1991 the original model was (too) expensive. I used duplicolor fjordblau 78 [01-114748-1578235] and repro stripes by Graph and Petra Perrel ("36" numbers). Years later I added the repro box .
The lights, tires, license plates and the driver are originals.
The Buffalo was one of the first U.S. monoplanes with an arrestor hook and other modifications for aircraft carriers. It won a competition against the Grumman F4F Wildcat in 1939 to become the U.S. Navy's first monoplane fighter aircraft.
(Source : Wikipedia)
552nd ACW Bids Farewell to First AWACS
The right side nose landing gear door of E-3 Sentry 75-0560 bears the names of current and former 552nd Air Control Wing members after a divestment signing event at Tinker Air Force Base, Oklahoma, March 31, 2023. This E-3 Sentry is the first aircraft to be divested. -USAF
DMAFB
Aircraft 0560 is the first E-3 Sentry Airborne Warning Air Control System aircraft to retire from the fleet this year. As part of the FY23 President’s Budget Request, the Department of the Air Force announced its intent to divest 13 E-3 AWACS aircraft and redirect funding to procure and field a replacement.