Originally posted by Canada_EH
reply to post by StargateSG7
Haha Thanks for the reply Stargate it does help to clear up what you meant. I guess what I'm trying to get you to say is do you think they could
build and test a demonstrator in the time given from project announcement to cancellation. Also since it was a white world project why wouldn't we
see it being tested or developed in the open? My thought that they only way this could of work is announce and show a model do nothing with the money
and let the program die. But my problem with that is why bother saying anything white world at all.
I'm going to answer your questions in order and outline some reasons
why it's done the way it is.
1) The fastest I've every heard of a project from initial design to prototype
rollout is 15 months via the Burt Rutan-built prototype of the X-47B
large scale autonomous UAV combat aircraft
and even the SR-71 Blackbird was done in less than 3 years
and that was in the late 1950's/1960's so YES it is possible to
design and prototype an aircraft in the timeframe indicated.
Today it's even more possible because of
CNC (Computerized Numerical Control) machines that can cut out
very complex parts of titanium and ceramic in less than a day.
And with CAD/CAM software and Finite Element Analysis a whole
airplane could be prototyped and analyzed on a computer
using computational fluid dynamics to ascertain flight performance
profiles within various scenarios such as low-altitude, high wind,
sandy dusty high-heat environments, high-altitude freezing cold
and other computerized simulations of where a plane would be flying
and this could be done within 3 to 6 months depending upon the
available computer horsepower.
Once the body has been designed and refined, the engines are also
tested for burn rate, heat management, vibration and noise testing,
power output profiles, load conditions, and bird/sand ingestion
damage mitigation all on a computer and ONLY THEN is a prototype
sent to a CNC machine to "Print" out the 2000 to 3000 parts needed
for the engine within four to six weeks.
Then it takes about three to four months to actually put the parts
together and then another 3 to 6 months of flight simulator testing
for the pilots before the first prototype is engine tested and then
flown for real, so in an accelerated program one year to 18 months
is a REALISTIC possibility.
2) The NASA X33/X34 programs ARE the whiteworld portions of Blackswift
but are likely used for OPERATIONAL TESTING of specific portions
of specific technologies such as engine inlet duct design or airflow testing
over machined composite structures which will be used IN PART within
a larger but more covert testing program such as Blackswift.
There are two reasons for doing what they do in terms of keeping secrets.
In the western world we not only have to keep secrets from potential
rivals such as Russia, China, Iran, North Korea, etc. BUT ALSO keep
secrets from people like US at ATS who CAN BE very GOOD at acting
like spies...therefore there are specific internal programs in place
to allow publically-funded scientists who are working in the White-World
of public knowledge projects to still contribute their significant expertise
but who cannot be brought into the Black Budget world because
of certain rules such as non-citizenship or foreign-born status
or familial relations/family status or financial/criminal record status.
These scientists can also be used as cover to hide the real design team
from people like us!
Since Black-Budget programs that are SAP (Special Access Programs)
or on a Compartmentalized Need to know basis, groups members are
required to meet certain personal, political and military requirements
that are very strict and not anyone can just "Join The Club".
So white world projects are setup to allow identified EXPERTS to work
on specific applications or perfrom certain segments of
Research & development that will be used in more secretive
black budget programs. Basically these techs don't KNOW that parts
of their work will be used in more advanced systems.
The white world project is also used as a cover for us ATS'ers and to
fool/misdirect Russia and China on specific aspects of an SAP program.
The best way to hide a secret project is to keep it out in the open
obfuscated by lots of whiteworld projects that have too many things to
keep effective track of and then let the Black Budget people Cherry-Pick
the best parts for themselves.
Since our society is very open, we can use front companies
and warehouses in Sacramento to put all the cherry picked designs
and parts to work as a flyable prototype that gets shipped in pieces
via a household-moving oriented Allied Van Lines tractor trailor
to a non-descript warehouse in Austin, Texas for final assembly
and systems testing before being put on a Hercules C130, C17
or C5a Galaxy transport craft to be flown to Australia, Diego Garcia,
England, Utah, Alaska or Area 51 for operational flight testing.
The general reasons for this secrecy is really more to do with
keeping budgets intact while a program is still in design and test stages
until Congress or the President can approve a budget allocation
for an operational program that gets assigned to a specific arm
of the Defence Department. If we disclose a specific program
to Congress while its still in it's infancy, some congressman might
get all pissy that it's NOT in his home state and thus move to
kill it or if the higher ups don't like the people involved for whatever
reason, they might ALSO want to kill an infant program...ergo...
the favorite toys of certain boys will be kept secret until a
working prototype is flying in the wild blue yonder or until the program
is so big and important it CAN'T be politically killed without severe
hits to a political or military career. Keeping secrets from
Russia and China is really a mere after thought since most black-budget
programs have political/financial goals rather than pure military aims.