View allAll Photos Tagged Webbing
I never noticed how thin the webbing was on Mr. Mallard's feet. It looks like you can see the log details right through the webbing.
Cormorant (Disambiguation)
Phalacrocoracidae is a family of approximately 40 species of aquatic birds commonly known as cormorants and shags. Several different classifications of the family have been proposed recently, and the number of genera is disputed. The great cormorant (P. carbo) and the common shag (P. aristotelis) are the only two species of the family commonly encountered on the British Isles, and "cormorant" and "shag" appellations have been later assigned to different species in the family somewhat haphazardly.
Cormorants and shags are medium-to-large birds, with body weight in the range of 0.35–5 kilograms (0.77–11.02 lb) and wing span of 45–100 centimetres (18–39 in). The majority of species have dark feathers. The bill is long, thin and hooked. Their feet have webbing between all four toes. All species are fish-eaters, catching the prey by diving from the surface. They are excellent divers, and under water they propel themselves with their feet with help from their wings; some cormorant species have been found to dive as deep as 45 metres (150 ft). They have relatively short wings due to their need for economical movement underwater, and consequently have the highest flight costs of any flying bird.
Cormorants nest in colonies around the shore, on trees, islets or cliffs. They are coastal rather than oceanic birds, and some have colonised inland waters – indeed, the original ancestor of cormorants seems to have been a fresh-water bird.[citation needed] They range around the world, except for the central Pacific islands.
Names
No consistent distinction exists between cormorants and shags. The names 'cormorant' and 'shag' were originally the common names of the two species of the family found in Great Britain, Phalacrocorax carbo (now referred to by ornithologists as the great cormorant) and P. aristotelis (the European shag). "Shag" refers to the bird's crest, which the British forms of the great cormorant lack. As other species were discovered by English-speaking sailors and explorers elsewhere in the world, some were called cormorants and some shags, depending on whether they had crests or not. Sometimes the same species is called a cormorant in one part of the world and a shag in another, e.g., the great cormorant is called the black shag in New Zealand (the birds found in Australasia have a crest that is absent in European members of the species). Van Tets (1976) proposed to divide the family into two genera and attach the name "cormorant" to one and "shag" to the other, but this flies in the face of common usage and has not been widely adopted.
The scientific genus name is Latinised Ancient Greek, from φαλακρός (phalakros, "bald") and κόραξ (korax, "raven"). This is often thought to refer to the creamy white patch on the cheeks of adult great cormorants, or the ornamental white head plumes prominent in Mediterranean birds of this species, but is certainly not a unifying characteristic of cormorants. "Cormorant" is a contraction derived either directly from Latin corvus marinus, "sea raven" or through Brythonic Celtic. Cormoran is the Cornish name of the sea giant in the tale of Jack the Giant Killer. Indeed, "sea raven" or analogous terms were the usual terms for cormorants in Germanic languages until after the Middle Ages. The French explorer André Thévet commented in 1558, "... the beak [is] similar to that of a cormorant or other corvid," which demonstrates that the erroneous belief that the birds were related to ravens lasted at least to the 16th century.
Description
Cormorants and shags are medium-to-large seabirds. They range in size from the pygmy cormorant (Phalacrocorax pygmaeus), at as little as 45 cm (18 in) and 340 g (12 oz), to the flightless cormorant (Phalacrocorax harrisi), at a maximum size 100 cm (39 in) and 5 kg (11 lb). The recently extinct spectacled cormorant (Phalacrocorax perspicillatus) was rather larger, at an average size of 6.3 kg (14 lb). The majority, including nearly all Northern Hemisphere species, have mainly dark plumage, but some Southern Hemisphere species are black and white, and a few (e.g. the spotted shag of New Zealand) are quite colourful. Many species have areas of coloured skin on the face (the lores and the gular skin) which can be bright blue, orange, red or yellow, typically becoming more brightly coloured in the breeding season. The bill is long, thin, and sharply hooked. Their feet have webbing between all four toes, as in their relatives.
Habitat
They are coastal rather than oceanic birds, and some have colonised inland waters – indeed, the original ancestor of cormorants seems to have been a fresh-water bird, judging from the habitat of the most ancient lineage. They range around the world, except for the central Pacific islands.
Behaviour
All are fish-eaters, dining on small eels, fish, and even water snakes. They dive from the surface, though many species make a characteristic half-jump as they dive, presumably to give themselves a more streamlined entry into the water. Under water they propel themselves with their feet, though some also propel themselves with their wings. Some cormorant species have been found, using depth gauges, to dive to depths of as much as 45 metres (150 ft).
After fishing, cormorants go ashore, and are frequently seen holding their wings out in the sun. All cormorants have preen gland secretions that are used ostensibly to keep the feathers waterproof. Some sources state that cormorants have waterproof feathers while others say that they have water permeable feathers.[8][9] Still others suggest that the outer plumage absorbs water but does not permit it to penetrate the layer of air next to the skin. The wing drying action is seen even in the flightless cormorant but commonly in the Antarctic shags and red-legged cormorants. Alternate functions suggested for the spread-wing posture include that it aids thermoregulation or digestion, balances the bird, or indicates presence of fish. A detailed study of the great cormorant concludes that it is without doubt to dry the plumage.
Cormorants are colonial nesters, using trees, rocky islets, or cliffs. The eggs are a chalky-blue colour. There is usually one brood a year. The young are fed through regurgitation. They typically have deep, ungainly bills, showing a greater resemblance to those of the pelicans, to which they are related, than is obvious in the adults.
Taxonomy
The cormorants are a group traditionally placed within the Pelecaniformes or, in the Sibley–Ahlquist taxonomy, the expanded Ciconiiformes. This latter group is certainly not a natural one, and even after the tropicbirds have been recognised as quite distinct, the remaining Pelecaniformes seem not to be entirely monophyletic. Their relationships and delimitation – apart from being part of a "higher waterfowl" clade which is similar but not identical to Sibley and Ahlquist's "pan-Ciconiiformes" – remain mostly unresolved. Notwithstanding, all evidence agrees that the cormorants and shags are closer to the darters and Sulidae (gannets and boobies), and perhaps the pelicans or even penguins, than to all other living birds.
In recent years, three preferred treatments of the cormorant family have emerged: either to leave all living cormorants in a single genus, Phalacrocorax, or to split off a few species such as the imperial shag complex (in Leucocarbo) and perhaps the flightless cormorant. Alternatively, the genus may be disassembled altogether and in the most extreme case be reduced to the great, white-breasted and Japanese cormorants.
Pending a thorough review of the Recent and prehistoric cormorants, the single-genus approach is followed here for three reasons: first, it is preferable to tentatively assigning genera without a robust hypothesis. Second, it makes it easier to deal with the fossil forms, the systematic treatment of which has been no less controversial than that of living cormorants and shags. Third, this scheme is also used by the IUCN, making it easier to incorporate data on status and conservation. In accordance with the treatment there, the imperial shag complex is here left unsplit as well, but the king shag complex has been.
The cormorants and the darters have a unique bone on the back of the top of the skull known as the os nuchale or occipital style which was called a xiphoid process in early literature. This bony projection provides anchorage for the muscles that increase the force with which the lower mandible is closed. This bone and the highly developed muscles over it, the M. adductor mandibulae caput nuchale, are unique to the families Phalacrocoracidae and Anhingidae.
Several evolutionary groups are still recognizable. However, combining the available evidence suggests that there has also been a great deal of convergent evolution; for example the cliff shags are a convergent paraphyletic group. The proposed division into Phalacrocorax sensu stricto (or subfamily "Phalacrocoracinae") cormorants and Leucocarbo sensu lato (or "Leucocarboninae") shags does indeed have some degree of merit. The resolution provided by the mtDNA 12S rRNA and ATPase subunits six and eight sequence data[25] is not sufficient to properly resolve several groups to satisfaction; in addition, many species remain unsampled, the fossil record has not been integrated in the data, and the effects of hybridisation – known in some Pacific species especially – on the DNA sequence data are unstudied.
List of genera
The family contains three genera:[26]
- Microcarbo (5 species)
- Phalacrocorax (22 species, including one extinct in 19th century)
- Leucocarbo (15 species)
Evolution and fossil record
Cormorants seem to be a very ancient group, with similar ancestors reaching back to the time of the dinosaurs. In fact, the earliest known modern bird, Gansus yumenensis, had essentially the same structure. The details of the evolution of the cormorant are mostly unknown. Even the technique of using the distribution and relationships of a species to figure out where it came from, biogeography, usually very informative, does not give very specific data for this probably rather ancient and widespread group. However, the closest living relatives of the cormorants and shags are the other families of the suborder Sulae—darters and gannets and boobies—which have a primarily Gondwanan distribution. Hence, at least the modern diversity of Sulae probably originated in the southern hemisphere.
While the Leucocarbonines are almost certainly of southern Pacific origin—possibly even the Antarctic which, at the time when cormorants evolved, was not yet ice-covered—all that can be said about the Phalacrocoracines is that they are most diverse in the regions bordering the Indian Ocean, but generally occur over a large area.
Similarly, the origin of the family is shrouded in uncertainties. Some Late Cretaceous fossils have been proposed to belong with the Phalacrocoracidae:
A scapula from the Campanian-Maastrichtian boundary, about 70 mya (million years ago), was found in the Nemegt Formation in Mongolia; it is now in the PIN collection. It is from a bird roughly the size of a spectacled cormorant, and quite similar to the corresponding bone in Phalacrocorax. A Maastrichtian (Late Cretaceous, c. 66 mya) right femur, AMNH FR 25272 from the Lance Formation near Lance Creek, Wyoming, is sometimes suggested to be the second-oldest record of the Phalacrocoracidae; this was from a rather smaller bird, about the size of a long-tailed cormorant.
As the Early Oligocene Sula" ronzoni cannot be assigned to any of the suloid families—cormorants and shags, darters, and gannets and boobies—with certainty, the best interpretation is that the Phalacrocoracidae diverged from their closest ancestors in the Early Oligocene, perhaps some 30 million years ago, and that the Cretaceous fossils represent ancestral suloids, "pelecaniforms" or "higher waterbirds"; at least the last lineage is generally believed to have been already distinct and undergoing evolutionary radiation at the end of the Cretaceous. What can be said with near certainty is that AMNH FR 25272 is from a diving bird that used its feet for underwater locomotion; as this is liable to result in some degree of convergent evolution and the bone is missing indisputable neornithine features, it is not entirely certain that the bone is correctly referred to this group.
During the late Paleogene, when the family presumably originated, much of Eurasia was covered by shallow seas, as the Indian Plate finally attached to the mainland. Lacking a detailed study, it may well be that the first "modern" cormorants were small species from eastern, south-eastern or southern Asia, possibly living in freshwater habitat, that dispersed due to tectonic events. Such a scenario would account for the present-day distribution of cormorants and shags and is not contradicted by the fossil record; as remarked above, a thorough review of the problem is not yet available.
Two distinct genera of prehistoric cormorants are widely accepted today, if Phalacrocorax is used for all living species:
- Limicorallus (Indricotherium middle Oligocene of Chelkar-Teniz, Kazakhstan)
- Nectornis (Late Oligocene/Early Miocene of Central Europe – Middle Miocene of Bes-Konak, Turkey) – includes Oligocorax miocaenus
The proposed genus Oligocorax appears to be paraphyletic – the European species have been separated in Nectornis, and the North American ones are placed in the expanded Phalacrocorax. A Late Oligocene fossil cormorant foot from Enspel, Germany, sometimes placed herein, would then be referable to Nectornis if it proves not to be too distinct. All these early European species might belong to the basal group of "microcormorants", as they conform with them in size and seem to have inhabited the same habitat: subtropical coastal or inland waters. Limicorallus, meanwhile, was initially believed to be a rail or a dabbling duck by some. There are also undescribed remains of apparent cormorants from the Quercy Phosphorites of Quercy (France), dating to some time between the Late Eocene and the mid-Oligocene.
Some other Paleogene remains are sometimes assigned to the Phalacrocoracidae, but these birds seem quite intermediate between cormorants and darters (and lack clear autapomorphies of either). Thus, they may be quite basal members of the Palacrocoracoidea. The taxa in question are:
- Piscator (Late Eocene of England)
- "Pelecaniformes" gen. et sp. indet. (Jebel Qatrani Early Oligocene of Fayum, Egypt) – similar to Piscator?
- Borvocarbo (Late Oligocene of C Europe)
The supposed Late Pliocene/Early Pleistocene "Valenticarbo" is a nomen dubium and given its recent age probably not a separate genus.
In human culture
Cormorant fishing
Humans have used cormorants' fishing skills in various places in the world. Archaeological evidence suggests that cormorant fishing was practiced in Ancient Egypt, Peru, Korea and India, but the strongest tradition has remained in China and Japan, where it reached commercial-scale level in some areas. In Japan, cormorant fishing is called ukai (鵜飼). Traditional forms of ukai can be seen on the Nagara River in the city of Gifu, Gifu Prefecture, where cormorant fishing has continued uninterrupted for 1300 years, or in the city of Inuyama, Aichi. In Guilin, China, cormorants are famous for fishing on the shallow Lijiang River. In Gifu, the Japanese cormorant (P. capillatus) is used; Chinese fishermen often employ great cormorants (P. carbo). In Europe, a similar practice was also used on Doiran Lake in the region of Macedonia.
In a common technique, a snare is tied near the base of the bird's throat, which allows the bird only to swallow small fish. When the bird captures and tries to swallow a large fish, the fish is caught in the bird's throat. When the bird returns to the fisherman's raft, the fisherman helps the bird to remove the fish from its throat. The method is not as common today, since more efficient methods of catching fish have been developed, but is still practiced as a cultural tradition.
In folklore, literature, and art
Cormorants feature in heraldry and medieval ornamentation, usually in their "wing-drying" pose, which was seen as representing the Christian cross, and symbolizing nobility and sacrifice. For John Milton in Paradise Lost, the cormorant symbolizes greed: perched atop the Tree of Life, Satan took the form of a cormorant as he spied on Adam and Eve during his first intrusion into Eden.
In some Scandinavian areas, they are considered good omen; in particular, in Norwegian tradition spirits of those lost at sea come to visit their loved ones disguised as cormorants.[36] For example, the Norwegian municipalities of Røst, Loppa and Skjervøy have cormorants in their coat of arms. The symbolic liver bird of Liverpool is commonly thought to be a cross between an eagle and a cormorant.
In 1853, a woman wearing a dress made of cormorant feathers was found on San Nicolas Island, off the southern coast of California. She had sewn the feather dress together using whale sinews. She is known as the Lone Woman of San Nicolas and was later baptised "Juana Maria" (her original name is lost). The woman had lived alone on the island for 18 years before being rescued. When removed from San Nicolas, she brought with her a green cormorant dress she made; this dress is reported to have been removed to the Vatican.
The bird has inspired numerous writers, including Amy Clampitt, who wrote a poem called "The Cormorant in its Element". The species she described may have been the pelagic cormorant, which is the only species in the temperate U.S. with the "slim head ... vermilion-strapped" and "big black feet" that she mentions.
A cormorant representing Blanche Ingram appears in the first of the fictional paintings by Jane in Charlotte Brontë's novel Jane Eyre.
The cormorant served as the hood ornament for the Packard automobile brand.
Cormorants (and books about them written by a fictional ornithologist) are a recurring fascination of the protagonist in Jesse Ball's 2018 novel Census.
[Credit: en.wikipedia.org]
Week 6: "Spun"
Decided to put my custom webbing to use again.
I make this stuff using a combination of jewelry wire and fishing line... it's braided, twisted and tied, then painted and bent to shape.
"We all have our own life to pursue, our own kind of dream to be weaving, and we all have the power to make wishes come true, as long as we keep believing."
Louisa May Alcott
Description: Small stocky cat species. Their toes have webbing between them to help them swim. Fishing cats have 2 layers of fur, one for keeping them warm and another for camouflage.
Habitat and Location: Found in wetland areas or near rivers in tropical dry forests. Distribution is spread across Southern Asia.
Diet: Carnivore. Mainly fish, crabs and frogs but will take rodents and young deer.
Reproduction: Females give birth to an average of two kittens a litter. Young will learn to fish from their mother and be independent at 10 months.
Conservation Status: Vulnerable.
Thanks for the information from 5 Sisters zoo
Ancient prophets, Isaiah, Mohammed, Ezekiel, Moses, Saul (Paul) and Jesus were ‘ascended’ into craft, to later suffer psychological distress, having met “God, or the Devil and His Angels”. Ancient alien abductions recorded in the Old Testament, reflect ontological shock after superior beings with miraculous technology identified themselves as,”God”, worshipped by Hebrews who called the skies above, ‘Heaven’ Their technology still looks like magic to us, 5000 years after the Old Testament’s documented encounters with this,”God”. Modern abductees report that during their abductions onboard craft, they often see a frightening alien race. These beings radiate rage and hatred, and appear to be overlords of the many alien races who frequent the crossroads of Earth for salvage, and to abduct humans and these beings command and pilot UFOs. Small greys, who act in unison like robots, are work beings, designed and created and labeled,’synthetic work beings’. There are similar descriptions of these overlords: Muscular, winged, sentient, highly technological, upright standing to seven or eight feet tall, scaled reptilian beings, with webbing between their claws, who have yellow/red cat-like eyes, upright saurian ‘monitor lizards’, Mothmen, alien reptilians who looked upon us, as we fancied veal. That may completely explain the ‘God-ordered’ Kosher dietary laws; strictly control what human animals eat,( as we do with snails and Omaha beef) and you will make them more tasteful as an edible. At Bud Hopkins’ house, during Saturday evening meetings, I learned that abductees had also somehow gleaned what reptoids regular diets consisted of: human young. It was a chilling story I was to hear repeatedly, echoed elsewhere, like Rod Serling’s “Twilight Zone” episode,”To Serve Man”, where our importance as a race in the Universe is that of a mere condiment. It reframed correctly, the true modus operandi behind this particular alien type and its ancient and continuing interaction/visitations with mankind. We were NOT the top of the food chain! Reading the O.T. Bible, again with alien-fresh eyes, even a non abductee can discern the elusive and controlling reptilian silhouette. Statue carvings of reptilians display the Mayan ‘God’ and Egyptian ‘God’ who created other similar “chosen people” sacrificial religions. This reptilian ‘God’, seated within a comparable “Holy of Holies”, in ancient Central America, was the centerpiece of power and evil, poised to eat and relish the Mayan God’s favorite dish, that of still beating human hearts.
This ‘God’ is the self-same demanding, controlling, punishing UFO ‘Heavenly’ “God” who insisted and demanded to the Hebrews that by ‘law’, much sacrificial blood be splashed on all four corners of His Altar.In the Garden of Eden tale, are clear reptilian fingerprints; alien advanced technological surgery (Adam put to sleep and a ‘rib’ removed for cloning and genetic manipulation) created a human-alien hybrid, the status of modern man and modern woman. Reptilians. horrid creatures. are completely in command of other alien subservient beings, aboard UFO craft and starships. Some wrongly and whimsically surmised about “God”, that pigs wrote the Bible, as half the world’s two major religions forbade the eating of swine… It is laughable, to us, today, that ancient human cultures throughout the ancient world wrongly mistook highly technological beings, who landed in craft, from the skies, as “God”, but the Mayans and Israelites were clearly and purposefully duped, by these beings. The impersonation, masquerade of ancient aliens as, “God”, helmeted and duped the world in the Old Testament .. God, our true spiritual father, is much too imbued within us, and within everything all around us, to be so easily discerned.
Religion, instead, is the bane.Gandhi said : ” I very much like your Christ , but not at all, your Christians”. There is a human unconscious remnant distant memory, of looking up, towards the stars for ‘God’. Earth, is the only planet, not named for a ‘God’. But God had nothing to do with an alien machine.
A closer look at the Ark of the Covenant, is more illuminating and revealing towards this realization of non-divine origins of the Old Testament; it was an object that breached the physical world of the Jews and the unseen paranormal world of the demanding “God” who had suddenly burst upon the scene.
Biblical evidence exists that the Ark of the Covenant was structurally designed as superior technology, acting as an alien transmitter-capacitor as well as a alien weapon.
The Ark, lethal when touched, was used to communicate with alien entities who masqueraded as “God”, who insisted a contrivance to be built, which would carry ‘God’s voice’, and aid Israelites when it was carried into battles: “And they shall make an Ark of shittim wood, two cubits and a half shall be the length thereof, and a cubit and a half the breadth thereof, and a cubit and a half the height thereof. ‘And thou shalt overlay it with pure gold, within and without shalt thou overlay it, and shalt make upon it a crown of gold around and all about.” One of the Gold plates was positively charged and one was negatively charged and together they formed the condenser.
If one of the cherubim’s positioned above the Mercy Seat acted as a magnet, then one has the rudimentary requirements of a two way communication set. The ‘Lord’, this “God”, even detailed what clothing should be worn when consulting “God” through this Ark device, so that no interference would be encountered and to limit the risk of electrocution. This discussion shall follow, shortly. Further proof of the Ark’s innate communication function can be found in the First Book Of Samuel, Chapter 3:3, when the Ark directly speaks to Samuel: “And ere the lamp of God went out in the temple of the Lord, where the Ark of God was, and Samuel was laid to sleep. ‘That the Lord called Samuel, and he answered here am I. ‘And he ran unto Eli, and said here am I, for thou calledst me. And he said. I called not, lie down again. And he went and lay down”. This repeated itself on two more occasions and eventually Eli realized that the Lord was speaking to Samuel via the Ark, which he then told to Samuel, and on the fourth occasion Samuel was able to converse with the “Lord”, directly THROUGH this contrivance.The only persons in the house at the time were Eli and Samuel, and it is quite blatant that it was indeed the Ark which ‘spoke’ to Samuel.
This Ark , clearly an alien technological invention, beyond ancient man’s technological understanding, seems a most unseemly ‘tool’ for our true, good and all powerful, God of the Universe, who communicates through angels, coincidences and signs, dreams, infused insights, inspiration and telepathy.
The True spirit God does not need such mechanical contrivances and HE, is down a long hall and somewhere else, than in that “Book” that pretends to delineate and define God. This machine/ weapon technological artifice was an alien designed three-in-one communication device set, religious receptacle and weapon of mass destruction. The Ark had these three uses; at all times of communication with ‘God’ and at all times of great battles, the Ark was invariably present. Unfortunately, not everyone had the same opinion of the Ark as lethally divine in intent. David decided for safety’s sake, to ‘steal away with it’, with Uzzah’s help, with tragic consequences as retold in the second book of Samuel, Chapter 6: “And when they came to Nachons threshing-floor, Uzzah put forth his hand to the Ark of God, and took hold of it, for the oxen shook it. ‘And the anger of the Lord was kindled against Uzzah, and God smote him there for his error, and there he died by the Ark of God.” Quite clearly the Ark , carrying a massive electrical charge, killed Uzzah on the spot when he touched it. Theologians mince words. Why didn’t “the God of the Universe”, kill Uzzah for attempting to sequester the Ark at the outset; why did He have to wait until the Ark was actually touched? Because, to theologians, ‘God’, accurately described in the Hebrew Old Testament, was a crafty, manipulative, and completely masquerading alien. Regard this startling photo of a Sumerian ‘God’, worshipped and obeyed 7000 years before Abraham, Isaac and Moses, with much the same sacrificial orders.ood technology always looks just like magic to a primitive.Consider the WWII “Cargo Cults” that developed in the South Pacific when native islanders took our pilots and airmen for “Gods from the Sky.”When the war ended, these primitive peoples sought to incite the return of the “Sky Gods” by making facsimile airplane out of palm trees and fronds.
This Ark ‘contrivance’, from the UFO document of the Old Testament, reveals more about this ancient,’God’ who used the Ark as an alien technological tool to conduct this masquerade.Insights about this ‘God Machine’ reveal the reptilian alien fingerprint and its fuller silhouette, unfurled in Biblical descriptions, that yield eve more truths.
The Ark of the Covenant alien ordered to be built, was an ornate golden chest used for electrical radiation/ radio communication, to both hear from ‘God’ and to speak to “God”, and was additionally used as a terrible weapon against the enemies of the Israelites.In order to operate it safely, the high priest from the family of Kohath (of the tribe of Levi), who knew even more of its ‘secrets’, had to wear a breastplate with twelve sacred gemstones called ‘the Stones of Fire’, for his own physical protection.
The ‘holiest’ part of the Ark was called the ‘oracle’, the place where one could literally discern audible orders to Israel from “God”, which were almost totally made through Moses.
When Moses entered into the tabernacle of the covenant to consult with this ‘oracle’, he heard a voice speaking to him from the ‘propitiatory’, a sectional ‘speaker’ that was over the ark between the two cherubim, the wings of which acted as separate battery terminal poles. This is technology, not spirituality. Specific directives, given to Moses, would now come from “God”, through this machine : “Thence will I give orders, and will speak to thee over the propitiatory, and from the midst of these two cherubim, which shall be upon the Ark of the testimony, all things which I will command the children of Israel by thee”. Unlike orders given from a ‘ burning bush’, a disembodied voice in a laser of light focused upon a bush, all of “God’s” future orders came from this ‘burning’ box , an electronic technological contrivance. There was an intermittent appearance of a “cloud” between the cherubim and at these times the Ark machinery was considered so dangerous that Moses, himself, would not approach it. I am personally sure that the accompanying sharp smell of ozone, a characteristic smell of a modern powerful radio transmitter, filled the room, at such times, as well. A “fire” which emerged from the Ark of the testimony was preceded by a “glow” which the Bible describes as the “glory of the Lord”.The army that carried the Ark of the Covenant, before it, was invincible. Is mankind a simple ‘speck’ of import, in an endless and timeless Universe? We are a considerable, “speck”, given that we are created as a harvest-able crop farmed throughout the Universe, by the masters of our Universe, Draco reptilians, and thus very much someone else’s valuable property. Though we are no more than a condiment in reptoids menu, we are also imbued with a soul/spirit, by God, a soul/spirit that is also garnered by reptoids after our ‘death’ and recycled by them.Disclosure will NOT EVER, will NEVER happen, simply because humankind could never handle the dismal alien-human ‘truth’.We figure, spiritually and physically, for both elements of mankind are harvested (abducted) much more than a mere speck, but instead one of a prized simian creature useful for reptilian’s purposes who deluded mankind in a God masquerade that has blinded and helmeted Earth.Director of CIA, Admiral R.H. Hillenkoetter: “It is time for the truth to be brought out in open Congressional hearings. Behind the scenes, high-ranking Air Force officers are soberly concerned about UFOs. But through official secrecy and ridicule, citizens are led to believe the unknown flying objects are nonsense. To hide the facts, the Air Force has silenced its personnel.” p. 58, quoted from New York Times, February 28, 1960, p. L30
Paul Schroeder, September 25th, 2017 Brooklyn, NY
Two fiery jets allegedly issued from between the cherubim above the Ark, burning up snakes, scorpions, thorns, and enemies in the Israelites' path. Such legendary attributes of ... In his first book,Chariots of the Gods, he explained that he believed the Ark of the Covenant was an alien invention that was electrically charged.Thelidonthe Ark ofthe Covenant hadtwocherubim facing each other. There isnoindication that these cherubim were ever removed from the lid, anditis certain thatthelid was never removed. Even so, two large cherubim standing on the floor and spreading their wings over the Ark were placed in the Most Holy Place.
The Ark of the Covenant (Hebrew: אָרוֹן הַבְּרִית, Modern Arōn Ha'brēt Tiberian ʾĀrôn Habbərîṯ), also known as the Ark of the Testimony, is a gold-covered wooden chest with lid cover described in the Book of Exodus as containing the two stone tablets of the Ten Commandments. According to various texts within the Hebrew Bible, it also contained Aaron's rod and a pot of manna. The biblical account relates that, approximately one year after the Israelites' exodus from Egypt, the Ark was created according to the pattern given to Moses by God when the Israelites were encamped at the foot of biblical Mount Sinai. Thereafter, the gold-plated acacia chest was carried by its staves while en route by the Levites approximately 2,000 cubits (approximately 800 meters or 2,600 feet) in advance of the people when on the march or before the Israelite army, the host of fighting men. When carried, the Ark was always hidden under a large veil made of skins and blue cloth, always carefully concealed, even from the eyes of the priests and the Levites who carried it. God was said to have spoken with Moses "from between the two cherubim" on the Ark's cover.[3] When at rest the tabernacle was set up and the holy Ark was placed under the veil of the covering the staves of it crossing the middle side bars to hold it up off the ground.According to the Book of Exodus, God instructed Moses on Mount Sinai during his 40-day stay upon the mountain within the thick cloud and darkness where God was and he was shown the pattern for the tabernacle and furnishings of the Ark to be made of shittim wood to house the Tablets of Stone. Moses instructed Bezalel and Oholiab to construct the Ark. In Deuteronomy, however, the Ark is said to have been built specifically by Moses himself without reference of Bezalel or Oholiab. The Book of Exodus gives detailed instructions on how the Ark is to be constructed. It is to be 2½ cubits in length, 1½ in breadth, and 1½ in height (approximately 131×79×79 cm or 52×31×31 in). Then it is to be gilded entirely with gold, and a crown or molding of gold is to be put around it. Four rings of gold are to be attached to its four corners, two on each side—and through these rings staves of shittim-wood overlaid with gold for carrying the Ark are to be inserted; and these are not to be removed. A golden lid, the kapporet (traditionally "mercy seat" in Christian translations) which is covered with 2 golden cherubim, is to be placed above the Ark. Instructions missing from the biblical account include the thickness of the mercy seat, but instruct that the cherubim cover be beaten out the ends of it and details concerning the cherubim except that they form the space that God will appear. The Ark is finally to be placed under the veil of the covering.The biblical account continues that, after its creation by Moses, the Ark was carried by the Israelites during their 40 years of wandering in the desert. Whenever the Israelites camped, the Ark was placed in a separate room in a sacred tent, called the Tabernacle. When the Israelites, led by Joshua toward the Promised Land, arrived at the banks of the Jordan river, the Ark was carried in the lead preceding the people and was the signal for their advance (Joshua 3:3, 6). During the crossing, the river grew dry as soon as the feet of the priests carrying the Ark touched its waters, and remained so until the priests—with the Ark—left the river after the people had passed over (Josh. 3:15-17; 4:10, 11, 18). As memorials, twelve stones were taken from the Jordan at the place where the priests had stood (Josh. 4:1-9). In the Battle of Jericho, the Ark was carried round the city once a day for seven days, preceded by the armed men and seven priests sounding seven trumpets of rams' horns (Josh. 6:4-15). On the seventh day, the seven priests sounding the seven trumpets of rams' horns before the Ark compassed the city seven times and, with a great shout, Jericho's wall fell down flat and the people took the city (Josh. 6:16-20). After the defeat at Ai, Joshua lamented before the Ark (Josh. 7:6-9). When Joshua read the Law to the people between Mount Gerizim and Mount Ebal, they stood on each side of the Ark. We next hear of the Ark in Bethel where it was being cared for by the priest Phineas the grandson of Aaron (Judges 20:26f, where 'Bethel' is translated 'the House of God' in the King James Version). According to this verse it was consulted by the people of Israel when they were planning to attack the Benjaminites at the battle of Gibeah. Later, however, the Ark was kept at Shiloh, another religious centre some 10 miles north of Bethel, at the time of the prophet Samuel's apprenticeship (1 Samuel 3:3), where it was cared for by Hophni and Phinehas, two sons of Eli (1 Samuel 4:3f).A few years later the elders of Israel decided to take the Ark out onto the battlefield to assist them against the Philistines, after being defeated at the battle of Eben-Ezer (1 Sam. 4:3-11). They were, however, heavily defeated with the loss of 30,000 men. The Ark was captured by the Philistines and Hophni and Phinehas were killed. The news of its capture was at once taken to Shiloh by a messenger "with his clothes rent, and with earth upon his head." The old priest, Eli, fell dead when he heard it; and his daughter-in-law, bearing a son at the time the news of the capture of the Ark was received, named him Ichabod — explained as "The glory has departed Israel" in reference to the loss of the Ark (1 Sam. 4:12-22). The mother of the child Ichabod died at his birth. (1 Sam. 4:20) The Philistines took the Ark to several places in their country, and at each place misfortune befell them (1 Sam. 5:1-6). At Ashdod it was placed in the temple of Dagon. The next morning Dagon was found prostrate, bowed down, before it; and on being restored to his place, he was on the following morning again found prostrate and broken. The people of Ashdod were smitten with tumors; a plague of mice was sent over the land (1 Sam. 6:5). The affliction of boils was also visited upon the people of Gath and of Ekron, whither the Ark was successively removed (1 Sam. 5:8-12). After the Ark had been among them for seven months, the Philistines, on the advice of their diviners, returned it to the Israelites, accompanying its return with an offering consisting of golden images of the tumors and mice wherewith they had been afflicted. The Ark was set up in the field of Joshua the Beth-shemite, and the Beth-shemites offered sacrifices and burnt offerings (1 Sam. 6:1-15). Out of curiosity the men of Beth-shemesh gazed at the Ark; and as a punishment, seventy of them (fifty thousand and seventy in some translations) were smitten by the Lord (1 Samuel 6:19). The Bethshemites sent to Kirjath-jearim, or Baal-Judah, to have the Ark removed (1 Samuel 6:21); and it was taken to the house of Abinadab, whose son Eleazar was sanctified to keep it. Kirjath-jearim remained the abode of the Ark for twenty years. Under Saul, the Ark was with the army before he first met the Philistines, but the king was too impatient to consult it before engaging in battle. In 1 Chronicles 13:3 it is stated that the people were not accustomed to consulting the Ark in the days of Saul.At the beginning of his reign over the United Monarchy, King David removed the Ark from Kirjath-jearim amid great rejoicing. On the way to Zion, Uzzah, one of the drivers of the cart that carried the Ark, put out his hand to steady the Ark, and was struck dead by God for touching it. The place was subsequently named "Perez-Uzzah", literally "Outburst Against Uzzah",[10] as a result. David, in fear, carried the Ark aside into the house of Obed-edom the Gittite, instead of carrying it on to Zion, and there it stayed three months (2 Samuel 6:1-11; 1 Chronicles 13:1-13). On hearing that God had blessed Obed-edom because of the presence of the Ark in his house, David had the Ark brought to Zion by the Levites, while he himself, "girded with a linen ephod ... danced before the Lord with all his might" and in the sight of all the public gathered in Jerusalem - a performance that caused him to be scornfully rebuked by his first wife, Saul's daughter Michal (2 Sam. 6:12-16, 20-22; 1 Chron. 15). In Zion, David put the Ark in the tabernacle he had prepared for it, offered sacrifices, distributed food, and blessed the people and his own household (2 Sam. 6:17-20; 1 Chron. 16:1-3; 2 Chron. 1:4).
The Levites were appointed to minister before the Ark (1 Chron. 16:4). David's plan of building a temple for the Ark was stopped at the advice of God (2 Sam. 7:1-17; 1 Chron. 17:1-15; 28:2, 3). The Ark was with the army during the siege of Rabbah (2 Sam. 11:11); and when David fled from Jerusalem at the time of Absalom's conspiracy, the Ark was carried along with him until he ordered Zadok the priest to return it to Jerusalem (2 Sam. 15:24-29).
In Solomon's Temple
When Abiathar was dismissed from the priesthood by King Solomon for having taken part in Adonijah's conspiracy against David, his life was spared because he had formerly borne the Ark (1 Kings 2:26). Solomon worshipped before the Ark after his dream in which God promised him wisdom (1 Kings 3:15). During the construction of Solomon's Temple, a special inner room, named Kodesh Hakodashim (Eng. Holy of Holies), was prepared to receive and house the Ark (1 Kings 6:19); and when the Temple was dedicated, the Ark—containing the original tablets of the Ten Commandments—was placed therein (1 Kings 8:6-9). When the priests emerged from the holy place after placing the Ark there, the Temple was filled with a cloud, "for the glory of the Lord had filled the house of the Lord" (1 Kings 8:10-11; 2 Chron. 5:13, 14).
When Solomon married Pharaoh's daughter, he caused her to dwell in a house outside Zion, as Zion was consecrated because of its containing the Ark (2 Chron. 8:11). King Josiah also had the Ark returned to the Temple (2 Chron. 35:3), from which it appears to have been removed by one of his predecessors (cf. 2 Chron. 33-34 and 2 Kings 21-23).
The Babylonian Conquest and aftermath[edit]
In 587 BC, the Babylonians destroyed Jerusalem and Solomon's Temple. There is no record of what became of the Ark in the Books of Kings and Chronicles. An ancient Greek version of the biblical third Book of Ezra, 1 Esdras, suggests that Babylonians took away the vessels of the ark of God, but does not mention taking away the Ark: And they took all the holy vessels of the Lord, both great and small, with the vessels of the ark of God, and the king's treasures, and carried them away into Babylon— 1 Esdras 1:54
In Rabbinic literature, the final disposition of the Ark is disputed. Some rabbis hold that it must have been carried off to Babylon, while others hold that it must have been hidden lest it be carried off into Babylon and never brought back.[11] A late 2nd-century rabbinic work known as the Tosefta states the opinions of these rabbis that Josiah, the king of Judah, stored away the Ark, along with the jar of manna, and a jar containing the holy anointing oil, the rod of Aaron which budded and a chest given to Israel by the Philistines.[12] This was said to have been done in order to prevent their being carried off into Babylon as had already happened to the other vessels. Rabbi Eliezer and Rabbi Shimon, in the same rabbinic work, state that the Ark was, in fact, taken into Babylon. Rabbi Yehudah, dissenting, says that the Ark was stored away in its own place, meaning, somewhere on the Temple Mount.
References in Scripture
Tanakh; The Ark is first mentioned in the Book of Exodus, and then numerous times in Deuteronomy, Joshua, Judges, I Samuel, II Samuel, I Kings, I Chronicles, II Chronicles, Psalms and Jeremiah. In the Book of Jeremiah, it is referenced by Jeremiah, who, speaking in the days of Josiah (Jer. 3:16), prophesied a future time, possibly the end of days, when the Ark will no longer be talked about or be made again: And it shall be that when you multiply and become fruitful in the land, in those days - the word of the LORD - they will no longer say, 'The Ark of the Covenant of the LORD' and it will not come to mind; they will not mention it, and will not recall it, and it will not be used any more.Rashi comments on this verse that "The entire people will be so imbued with the spirit of sanctity that God's Presence will rest upon them collectively, as if the congregation itself was the Ark of the Covenant."
Second Book of Maccabees
According to Second Maccabees, at the beginning of chapter 2: The records show that it was the prophet Jeremiah who ... prompted by a divine message ... gave orders that the Tent of Meeting and the ark should go with him. Then he went away to the mountain from the top of which Moses saw God's promised land. When he reached the mountain, Jeremiah found a cave-dwelling; he carried the tent, the ark, and the incense-altar into it, then blocked up the entrance. Some of his companions came to mark out the way, but were unable to find it. When Jeremiah learnt of this he reprimanded them. "The place shall remain unknown", he said, "until God finally gathers his people together and shows mercy to them. The Lord will bring these things to light again, and the glory of the Lord will appear with the cloud, as it was seen both in the time of Moses and when Solomon prayed that the shrine might be worthily consecrated."II Maccabees 2:4–8 (Douay-Rheims, 1899) The "mountain from the top of which Moses saw God's promised land" would be Mount Nebo, located in what is now Jordan.
The Ark in Islamic sources
Chapter 2 (Sura 2) of the Quran (Verse 248), is believed to refer to the Ark: And their prophet said to them, "Indeed, a sign of his kingship is that the chest (tābūt) will come to you in which is assurance (sakīnatun) from your Lord and a remnant of what the family of Moses (Mūsā) and the family of Aaron (Hārūn) had left, carried by the angels. Indeed in that is a sign for you, if you are believers." The Arabic word sakīna (variously translated "peace of reassurance" or "spirit of tranquility") is related to the post-Biblical Hebrew shekhinah, meaning "dwelling or presence of God". The Islamic scholar Al Baidawi mentioned that the sakina could be Tawrat, the Books of Moses.[15] According to Al-Jalalan, the relics in the Ark were the fragments of the two tablets, rods, robes, shoes, mitres of Moses and the vase of manna.[15] Al-Tha'alibi, in Qisas Al-Anbiya (The Stories of the Prophets), has given an earlier and later history of the Ark.
According to Uri Rubin the Ark of the Covenant has a religious basis in Islam, and Islam gives it special significance.[
Possible locations: Since its disappearance from the Biblical narrative, there have been a number of claims of having discovered or of having possession of the Ark, and several possible places have been suggested for its location. Mount Nebo..2 Maccabees 2:4-10, written around 100 BC, says that the prophet Jeremiah, "being warned by God" before the Babylonian invasion, took the Ark, the Tabernacle, and the Altar of Incense, and buried them in a cave on Mount Nebo, informing those of his followers who wished to find the place that it should remain unknown "until the time that God should gather His people again together, and receive them unto mercy."[17] Mount Nebo is also described in the Bible (Deuteronomy 34) as the site from which Moses views the Promised Land, and apparently also is his final burial place. Mount Nebo is approximately 47 km (29 miles) slightly south of due east from Jerusalem, near the east bank of the Jordan River. Ethiopia..The Chapel of the Tablet at the Church of Our Lady Mary of Zion in Axum allegedly houses the original Ark of the Covenant. The Ethiopian Orthodox Tewahedo Church claims to possess the Ark of the Covenant, or Tabot, in Axum. The object is currently kept under guard in a treasury near the Church of Our Lady Mary of Zion. Replicas of the Axum tabot are kept in every Ethiopian Orthodox Tewahedo church, each with its own dedication to a particular saint; the most popular of these include Mary, George and Michael. The Kebra Nagast was composed to legitimise the Solomonic dynasty, which ruled the Ethiopian Empire following its establishment in 1270. It narrates how the real Ark of the Covenant was brought to Ethiopia by Menelik I with divine assistance, while a forgery was left in the Temple in Jerusalem. Although the Kebra Nagast is the best-known account of this belief, it predates the document. Abu al-Makarim, writing in the last quarter of the twelfth century, makes one early reference to this belief that they possessed the Ark. "The Abyssinians possess also the Ark of the Covenant", he wrote, and, after a description of the object, describes how the liturgy is celebrated upon the Ark four times a year, "on the feast of the great nativity, on the feast of the glorious Baptism, on the feast of the holy Resurrection, and on the feast of the illuminating Cross." In his 1992 book The Sign and the Seal, British writer Graham Hancock suggests, contrary to the Kebra Nagast, that the ark spent several years in Egypt before it came to Ethiopia via the Nile River, where it was kept in the islands of Lake Tana for about four hundred years and finally taken to Axum.[20] Archaeologist John Holladay of the University of Toronto called Hancock's theory "garbage and hogwash," while Edward Ullendorff, a former Professor of Ethiopian Studies at the University of London, said he "wasted a lot of time reading it." On 25 June 2009, the patriarch of the Orthodox Church of Ethiopia, Abune Paulos, said he would announce to the world the next day the unveiling of the Ark of the Covenant, which he said had been kept safe and secure in a church in Axum, Ethiopia.[22] The following day, on 26 June 2009, the patriarch announced that he would not unveil the Ark after all, but that instead he could attest to its current status. The Lemba people of South Africa and Zimbabwe have claimed that their ancestors carried the Ark south, calling it the ngoma lungundu or "voice of God", eventually hiding it in a deep cave in the Dumghe mountains, their spiritual home.[On 14 April 2008, in a UK Channel 4 documentary, Tudor Parfitt, taking a literalist approach to the Biblical story, described his research into this claim. He says that the object described by the Lemba has attributes similar to the Ark. It was of similar size, was carried on poles by priests, was not allowed to touch the ground, was revered as a voice of their God, and was used as a weapon of great power, sweeping enemies aside. In his book The Lost Ark of the Covenant (2008), Parfitt also suggests that the Ark was taken to Arabia following the events depicted in the Second Book of Maccabees, and cites Arabic sources which maintain it was brought in distant times to Yemen. One Lemba clan, the Buba, which was supposed to have brought the Ark to Africa, have a genetic signature called the Cohen Modal Haplotype. This suggests a male Semitic link to the Levant. Lemba tradition maintains that the Ark spent some time in Sena in Yemen. Later, it was taken across the sea to East Africa and may have been taken inland at the time of the Great Zimbabwe civilization. According to their oral traditions, some time after the arrival of the Lemba with the Ark, it self-destructed. Using a core from the original, the Lemba priests constructed a new one. This replica was discovered in a cave by a Swedish German missionary named Harald von Sicard in the 1940s and eventually found its way to the Museum of Human Science in Harare.[25] Parfitt had this artifact radio-carbon dated to about 1350, which coincided with the sudden end of the Great Zimbabwe civilization.Chartres Cathedral, France
French author Louis Charpentier claimed that the Ark was taken to the Chartres Cathedral by the Knights Templar.. Rennes-le-Château, then to the United States
One author has theorised that the Ark was taken from Jerusalem to the village of Rennes-le-Château in Southern France. Karen Ralls has cited Freemason Patrick Byrne, who believes the Ark was moved from Rennes-le-Château at the outbreak of World War I to the United States.
The Ark of the Covenant was said to have been kept in the Basilica of St. John Lateran, surviving the pillages of Rome by Genseric and Alaric I but lost when the basilica burned. "Rabbi Eliezer ben José stated that he saw in Rome the mercy-seat of the temple. There was a bloodstain on it. On inquiry he was told that it was a stain from the blood which the high priest sprinkled thereon on the Day of Atonement."[In 2003, author Graham Phillips hypothetically concluded that the Ark was taken to Mount Sinai in the Valley of Edom by the Maccabees. Phillips claims it remained there until the 1180s, when Ralph de Sudeley, the leader of the Templars found the Maccabean treasure at Jebel al-Madhbah, and returned home to his estate at Herdewyke in Warwickshire, England taking the treasure with him.[34]
During the turn of the 20th century British Israelites carried out some excavations of the Hill of Tara in Ireland looking for the Ark of the Covenant—the Royal Society of Antiquaries of Ireland campaigned successfully to have them stopped before they destroyed the hill. In 1922 in the Valley of the Kings in Egypt, the royal tomb of the Pharaoh Tutankhamun (KV62) was opened by Howard Carter and Lord Carnarvon. Among the artifacts was a processional ark, listed as Shrine 261, the Anubis Shrine. Almost immediately after publication of the photographs[36] of this sensational archaeological find, some claimed that the Anubis Shrine could be the Ark of the Covenant. John M. Lundquist, author of The Temple of Jerusalem: Past, Present, and Future (2008), discounts this idea. The Anubis Shrine measures 95 centimetres (37 in) long, 37 centimetres (15 in) wide, and 54.3 centimetres (21.4 in) high in the shape of a pylon. The Biblical Ark of the Covenant is approximately 133 centimetres (52 in) long, 80 centimetres (31 in) wide, and 80 centimetres (31 in) high in the shape of a rectangular chest.
Lundquist observes that the Anubis Shrine is not strictly analogous to the Ark of the Covenant; it can only be said that the it is "ark-like", constructed of wood, gessoed and gilded, stored within a sacred tomb, "guarding" the treasury of the tomb (and not the primary focus of that environment), that it contains compartments within it that store and hold sacred objects, that it has a figure of Anubis on its lid, and that it was carried by two staves permanently inserted into rings at its base and borne by eight priests in the funerary procession to Tutankhamun's tomb. Its value is the insight it provides to the ancient culture of Egypt.
This is my all time best spider web photo, and I couldn't see it very well due to the angle. It took several shots to get it right.
It's Saturday, so I'm on my way back to the office. Meanwhile, here's the abdomen of a tarantula, using its spinnerettes to create webbing. The zoo keeper told me that the web isn't necessarily used to catch food. Instead, it may be there to protect eggs.
The greater racket-tailed drongo is a medium-sized Asian bird which is distinctive in having elongated outer tail feathers with webbing restricted to the tips. They are placed along with other drongos in the family Dicruridae.
Scientific name: Dicrurus paradiseus
You would think with the amount of spider webbing around our house it would be easy to find the spider. Finally got one.
Wasp spiders (Argiope bruennichi) make these amazing lantern-looking egg sacs to house their young for the winter.
They are suspended within the vegetation (gorse or grass stems) by a mesh of webbing.
Materials used:
Gel medium
Scrapbooking paper
Book text
Painted paper scraps (Gouache, acrylics, webbing spray, pastels, ink pen)
+++ 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!
Trying to figure out the best way to connect the webs though it won't stand up for long due to the combined weight. Still have a dozen more to connect and will be stronger when strung up on tree branches...
The Malabar gliding frog or Malabar flying frog (Rhacophorus malabaricus) is a Rhacophorid tree frog species found in the Western Ghats of India.
The term "gliding" frog refers to its ability to break its fall by stretching the webbing between its toes when making leaps down from the treetops. It can make gliding jumps of 9–12 m, a maximum of about 115 times its length.
Pictured is a soldier taking part in hugely realistic and challenging live firing package, fighting through vegetation as he puts down fire in support of other units other during.Exercise ULU RAJAH.
Exercise ULU RAJAH offered five weeks of tough, realistic training in a close country tropical environment.
Even the simplest of tasks becomes a challenge with visibility reduced to a few metres, intensely hot and humid conditions, clouds of biting insects, poisonous plants and animals, a canopy that blocks out the sun and extremely steep terrain.
From conducting long range reconnaissance to live firing in some of the most demanding terrain on the planet.. .Household Cavalry soldiers are very familiar to the public in the State Ceremonial role, the trusted guardians of HM The Queen on their famous black horses; however, at any given time the large majority of Household Cavalry soldiers are on operational duty as reconnaissance soldiers. ..Having just completed a year of being at high readiness to deploy across the world mounted in their light armoured vehicles, they have taken the opportunity to hone their dismounted skills.
-------------------------------------------------------
© Crown Copyright 2014
Photographer: Sgt Rupert Frere
Image 45162195.jpg from www.defenceimages.mod.uk
Use of this image is subject to the terms and conditions of the MoD News Licence at www.defenceimagery.mod.uk/fotoweb/20121001_Crown_copyrigh...
For latest news visit www.gov.uk/government/organisations/ministry-of-defence
Follow us:
86/365
Im on a yellow kick...don't really know why haha
I noticed a lot of people noting the grain, its actually flour haha but I appreciate the comments non the less.
This is a bridge of webbing in the cactus patch of the garden, with drops from the copious drizzle this morning. It runs between last year's ripe fruit and this year's flower bud. I reckon this web is the work of either a Sheet Web Weaver (Linyphiidae) or a Funnel Web Weaver (Agelenidae) spider - maybe the latter because the drops are relatively large? I like that one amber-colored drop. Happy Web Webnesday! (San Marcos Pass, 30 May 2018)
+++ 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!
Pictured are members of 40 Commando on patrol in Belize.
Taunton based 40 Commando exercising in Belize, Central America, conducting Exercise Curry Trail...Delta Company (D Coy), the Jungle Warfare Specialists of 40 Commando in the jungles of Belize conducting vital training under the watchful eye of BATSUB (British Army Training Support Unit Belize) staff known as Trackers, as well as Directing Staff from the Royal Marines...During the first phase of training the Royal Marines conduct break contact drills, close target reconnaissance, survival, patrol and navigation training in the depths of Sibun Gorge. ..The Trackers taught the elite Commandos all about operating in the jungle; providing instruction about survival, building shelters and animal traps, creating fire, and understanding what plants are edible, inedible and which are medicinal, as well as what insects and wildlife to avoid in this environment...When the eight Tracker instructors, who are locals of Belize, aren’t teaching Royal Marines, the British Army or the United States Marine Corps, they are maintaining the training area for the next group of troops...Live Fire Tactical Training (LFTT) was the second phase of training which saw the transition from individual CQB (Close Quarters Battle) to four and eight-man team assaults in another training area known as Manatee...During this phase, the troops were using the SA80 rifle, LMG (Light Machine Gun), GPMG (General Purpose Machine Gun) and grenades. They also learned how to employ demolitions in the jungle environment.
-------------------------------------------------------
© Crown Copyright 2014
Photographer: L(Phot) Will Haigh
Image 45162179.jpg from www.defenceimages.mod.uk
Use of this image is subject to the terms and conditions of the MoD News Licence at www.defenceimagery.mod.uk/fotoweb/20121001_Crown_copyrigh...
For latest news visit www.gov.uk/government/organisations/ministry-of-defence
Follow us:
"A circle is the reflection of eternity. It has no beginning and it has no end - and if you put several circles over each other, then you get a spiral." ~
Maynard James Keenan
+++ 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!
+++ 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!