conspiracy theories

[Soul Doctor]

---

YouTube - Top Gear Moon Buggy

ayus na kaayo ang technology ron bai, pero ge-deny ang ilang mission, ambot nganu, kwarta siguro

i-deny jud nila kay masakpan man nga wala jud sila nakaadto sa moon.

tan-awa ang area 51 sa nevada di ba parehag terrain sa moon landing photos ang satelite photo sa area 51.

[miket07]

if the conspiracy theory is wrong. then by now, USA already sent another mission to the moon.
with today's technology it would be as easier and could cost less.

But why there is no plan of going back to the moon?

Film producers will readily shoulder fraction of the budget if only to make a documentary from it.

Agree ko sir. Sakto jud ka.. Mas gi-una pa nila ang mars nga mas layo pa hinoon. Basin ilang argument kay didto naman sila gikan sa moon. hehehe!

[miket07]

If ganahan jud sila mo adto sa moon, instead of human ang ilang ipada didto kanang robotic para dili hazardous sa mga astronaut. Technologies now a days are very much capable of doing it. Tan-aw nako ma unhan jud ni ang US sa mga ASIAN countries ba. or naay lain way magpadala sila og kanang orbiter ba ron nga mo take a close up video or mga images sa moon. Basin ang argument nasad nila kay no need na kay daghan na mga pictures og videos ana. hehehe!

[rodsky]

if you've seen the lunar landing was perfect too perfect.

Perfect? Shakes head.

Here is a list I compiled of all the serious problems encountered by each of the actual flown missions in the Apollo Programme:

Apollo 8 (Lunar Fly-by, no landing): Unplanned manual re-alignment
Lovell used some otherwise idle time to do some navigational sightings, maneuvering the module to view various stars by using the computer keyboard. However, he accidentally erased some of the computer's memory, which caused the inertial measuring unit (IMU) to think the module was in the same relative position it had been in before lift-off and fire the thrusters to "correct" the module's attitude.

Once the crew realized why the computer had changed the module's attitude, they realized they would have to re-enter data that would tell the computer its real position. It took Lovell ten minutes to figure out the right numbers, using the thrusters to get the stars Rigel and Sirius aligned, and another 15 minutes to enter the corrected data into the computer.

If this problem was not fixed by Lovell, the crew of Apollo 8 would have calculated for a solar orbit and doomed to never return to earth.


Apollo 10 (test of the Lunar Module Descent to surface): Gyration of the Lunar Module during Rendezvous with CSM
At the low point of the LM's second swing around the moon, Stafford and Cernan prepared for insertion into rendezvous orbit, a delicate maneuver using the LM's ascent engine, to bring them up for a rendezvous and docking with Young in the CSM. Before firing the ascent engine, the descent stage, with its power plant capable of a wide range of power settings controlled by the crew, had to be cast off. Just before the lower segment was cut loose, the LM gyrated. Stafford took manual control of the LM and restored the proper orientation. Then the descent stage was jettisoned, as planned, and the LM stabilized. The episode took some eight seconds.

Analysis indicates that the problem was caused by a malfunction in the backup guidance system. When the trouble began, the LM was under the control of this system. The system shifted its control modes which produced the LM's erratic behavior. Once free of the descent stage, the astronauts shifted the ascent stage to the primary guidance system control and there were no further difficulties.

Apollo 11 (the actual landing): Problems with the PNGS/AGS
As the descent began, Armstrong and Aldrin found that they were passing landmarks on the surface 4 seconds early and reported that they were "long": they would land miles west of their target point (yes, people don't know this but Neil and Buzz missed their landing target).

Five minutes into the descent burn, and 6,000 feet (1,800 m) above the surface of the moon, the LM navigation and guidance computer distracted the crew with the first of several unexpected "1202" and "1201" program alarms. Inside Mission Control Center in Houston, Texas, computer engineer Jack Garman told guidance officer Steve Bales it was safe to continue the descent and this was relayed to the crew. The program alarms indicated "executive overflows", where the guidance computer could not complete all of its tasks in real time and had to postpone some of them. This was neither a computer error nor an astronaut error, but stemmed from a mistake in how the astronauts had been trained. Although unneeded for the landing, the rendezvous radar was intentionally turned on to make ready for a fast abort. Ground simulation setups had not foreseen that a fast stream of spurious interrupts from this radar could happen, depending upon how the hardware randomly powered up before the LM then began nearing the lunar surface: hence the computer had to deal with data from two radars, not the landing radar alone, which led to the overload.

When Armstrong again looked outside, he saw that the computer's landing target was in a boulder-strewn area just north and east of a 300 meter diameter crater (later determined to be "West crater", named for its location in the western part of the originally planned landing ellipse). Armstrong took semi-automatic control and, with Aldrin calling out altitude and velocity data, landed at 20:17 UTC on July 20 with about 25 seconds of fuel left.

Even the actual landing was far from perfect.


Apollo 12 (second manned landing): Lighting Strike at Liftfoff and the TV Camera Sunlight Exposure
Thirty-six-and-a-half seconds after lift-off, the vehicle triggered a lightning discharge through itself and down to the earth through the Saturn's ionized plume. Protective circuits on the fuel cells in the service module falsely detected overloads and took all three fuel cells offline, along with much of the CSM instrumentation. A second strike at 52 seconds after launch knocked out the "8-ball" attitude indicator. The telemetry stream at Mission Control was garbled. However, the Saturn V continued to fly correctly; the strikes had not affected the Saturn V's Instrument Unit.

The loss of all three fuel cells put the CSM entirely on batteries. They were unable to maintain normal 28V DC bus voltages into the heavy 75 amp launch loads. One of the AC inverters dropped offline. These power supply problems lit nearly every warning light on the control panel and caused much of the instrumentation to malfunction.

Legendary EECOM John Aaron (the original NASA "steely eyed missile man") remembered the telemetry failure pattern from an earlier test when a power supply malfunctioned in the CSM Signal Conditioning Equipment (SCE). The SCE converts raw signals from instrumentation to standard voltages for the spacecraft instrument displays and telemetry encoders.

Aaron made a call: "Try SCE to aux". This switched the SCE to a backup power supply. The switch was fairly obscure and neither the Flight Director, CAPCOM, nor Commander Conrad immediately recognized it. Lunar module pilot Alan Bean, flying in the right seat as the CSM systems engineer, remembered the SCE switch from a training incident a year earlier when the same failure had been simulated. Aaron's quick thinking and Bean's memory saved what could have been an aborted mission. Bean put the fuel cells back on line, and with telemetry restored, the launch continued successfully. Once in earth parking orbit, the crew carefully checked out their spacecraft before re-igniting the S-IVB third stage for trans-lunar injection. The lightning strikes had caused no serious permanent damage.

Initially it was feared that the lightning strike could have caused the command module's parachute mechanism to prematurely fire, disabling the explosive bolts that open the parachute compartment to deploy them. If they were indeed disabled, the command module would have crashed uncontrollably into the Pacific Ocean at the end of the mission and killed the crew instantly. Since there was no way to figure out whether or not this was the case, ground controllers decided not to tell the astronauts about the possibility. Fortunately, the parachutes did deploy and function normally at the end of the mission.

---------

To improve the quality of television pictures from the Moon, a color camera was carried on Apollo 12 (unlike the monochrome camera that was used on Apollo 11). Unfortunately, when Bean carried the camera to the place near the lunar module where it was to be set up, he inadvertently pointed it directly into the Sun, destroying the SEC tube. Television coverage of this mission was thus terminated almost immediately.

See? Astronauts can be forgetful/dumb...nobody's perfect.


Apollo 13 (3rd landing attempt, aborted)
I don't even need to tell you the many many problems associated with this mission, just watch the movie. And you still insist "perfection"?

Apollo 14 (3rd landing on the moon): Assorted Problems
At the beginning of the mission, the CSM Kitty Hawk had difficulty achieving capture and docking with the LM Antares. Repeated attempts to dock went on for 1 hour and 42 minutes, until it was suggested that pilot Roosa hold Kitty Hawk against Antares using its thrusters, then the docking probe would be retracted out of the way, hopefully triggering the docking latches. This attempt was successful, and no further docking problems were encountered during the mission.

After separating from the command module in lunar orbit, the LM Antares also had two serious problems. First, the LM computer began getting an ABORT signal from a faulty switch. NASA believed that the computer might be getting erroneous readings like this if a tiny ball of solder had shaken loose and was floating between the switch and the contact, closing the circuit. The immediate solution—tapping on the panel next to the switch—did work briefly, but the circuit soon closed again. If the problem recurred after the descent engine fired, the computer would think the signal was real and would initiate an auto-abort, causing the Ascent Stage to separate from the Descent Stage and climb back into orbit. NASA and the software teams at MIT scrambled to find a solution, and determined the fix would involve reprogramming the flight software to ignore the false signal. The software modifications were transmitted to the crew via voice communication, and Mitchell manually entered the changes (amounting to over 80 keystrokes on the LM computer pad) just in time.

A second problem occurred during the powered descent, when the LM radar altimeter failed to lock automatically onto the moon's surface, depriving the navigation computer of vital information on the vehicle altitude and groundspeed. This was later determined to be an unintended consequence of the software patch. After the astronauts cycled the landing radar breaker, the unit successfully acquired a signal near 50,000 feet (15,000 m), again just in the nick of time. Shepard then manually landed the LM closer to its intended target than any of the other six moon landing missions. Mitchell believes that Shepard would have continued with the landing attempt without the radar, using the LM inertial guidance system and visual cues. But a post-flight review of the descent data showed the inertial system alone would have been inadequate, and the astronauts probably would have been forced to abort the landing as they approached the surface.

The EVA almost became a drama when Shepard and Mitchell almost ran out of air after their journey to the edge of cone crater. They totally underestimated the distance they needed to cover and their air supply. Again, you call that perfection?

Apollo 15 (4th Landing): Only 2 chutes deployed
Only 2 of the three parachutes deployed, so the splashdown was harder than usual. Fortunately none of the astronauts were injured.

Apollo 16 (5th Landing): Misc. Problems
A malfunction in a backup yaw gimbal servo loop in the main propulsion system of the CSM Casper caused concerns about firing the engine to adjust the CSM's lunar orbit, and nearly caused the Moon landing to be aborted. After a delayed first landing attempt, it was determined that the malfunction presented relatively little risk, and Young and Duke (who were already undocked, and flying LM Orion when the problem occurred) were permitted to land on the Moon.

During the EVA, John inadvertently destroyed the heat-flow experiment module because he tripped on one of the data cables, because astronauts cannot much below 45 degrees of vision because of their helmets. Again, perfection?

when in fact back on earth where the conditions are controlled, they could not even make a decent landing.
even armstrong ejected seconds before the simulated landing. if he hadn't he should have been killed in the explosion in one other the landing simulations.

the landing was problematic because in space and in the moon a small thrust from its side rockets could send the ship into a tailspin..that is why it is very difficult to maneuver when landing.

and have you seen the take off. from the moon?
the rocket thrust was so low that alone could not have pushed the lander back to earth.
considering the gravity of the moon.

but if you look closedly at the video, it was as if a wire pulled the ship up during ignition.
just watch the clip. and open your mind.

Ok, I'll give you three challenges, and this is not only for Soul_doctor, but for ANYONE here who believes in the HOAX theories...

FIRST CHALLENGE: Please kindly read this book:
Spaceflight Dynamics by Wiesel

I personally have a copy of this book, and I'm willing to let any of you borrow it and to read it before you embarrass yourself further by talking about orbital and celestial mechanics without a proper background on it.

SECOND CHALLENGE: read this website and take the quiz in the end of the lessons:
Basics of Space Flight You can also view this website for supplement/reference: Basics of Space Flight: Orbital Mechanics

THIRD CHALLENGE: Download and install Orbiter: Space Flight Simulator Orbiter - Home and do the following maneuvers:
a) Take off (using the Delta Glider) from Cape Canaveral and manually put the spacecraft in low-earth orbit.
b) Take off from the moon (using ANY spacecraft) and manually put the spacecraft into lunar obit
There is no reason for you NOT to be able to do all this if you do CHALLENGE 1 and 2. So wala'y LUSOT!

Final word. I will personally demonstrate Orbiter: Space Flight Simulator and perform lunar transfers for anyone interested, for FREE. Just contact me 09198803142 and prepare a room with a computer for me (Pentium 4 class or higher CPU, with anything higher than an nVidia 9400 video card will do), and I will PERSONALLY show you HOW COMPLICATED it is to land on the moon and get back to the earth, but even with this complication, if you KNOW HOW TO, it CAN BE DONE.

Diba sige lang mo'g complain nga sige lang ta'g yaw-yaw diri? So instead of puro yaw-yaw, why not do a practical exercise? So here's your chance--I'm waiting.


-RODION

[Visual C#]

Rodsky, don't waste your breath or fingers responding to this nonsense. Conspiracy theorists will remain nutcases, no matter how solid your facts are. I don't think anyone (with clear thinking) will respond to your challenge.

Case closed: Apollo landing deniers, and 9/11 "truthers" are nutcases.

[rodsky]

I don't think anyone (with clear thinking) will respond to your challenge.

A pity. But still all good. That would mean their words are hollow, and thus the *undecided* readers of the thread have now a better basis from which to choose whom to believe in--between those who can back up their words with a demonstration, or those who just keep adding to the list based on their *belief* that the moon landings really didn't happen. That's just my simple goal.

-RODION

[neshem]

ot: nindot ning offer ni rodsky, simulation EB.. talagsa ra na nga offer, daghan mahibaloan.

[miket07]

Pa balika sa sila sa moon para makita jud sa tanan. Including katong ni tuo nga hoax ni..

[rodsky]

Pa balika sa sila sa moon para makita jud sa tanan. Including katong ni tuo nga hoax ni..

Right. Say, got $25.4 billion stashed around someplace?

In a more serious note...from Wikipedia:


"In 2008, Japan Aerospace Exploration Agency's SELENE probe observed evidence of the halo surrounding the Apollo 15 lunar module blast crater while orbiting above the lunar surface. In 2009, NASA's robotic Lunar Reconnaissance Orbiter, while orbiting 50 kilometres (31 mi) above the moon, photographed the remnants of the Apollo program left on the lunar surface, and photographed each site where manned Apollo flights landed.

In a November 16, 2009 editorial, The New York Times opined that:
“ [T]here’s something terribly wistful about these photographs of the Apollo landing sites. The detail is such that if Neil Armstrong were walking there now, we could make him out, make out his footsteps even, like the astronaut footpath clearly visible in the photos of the Apollo 14 site. Perhaps the wistfulness is caused by the sense of simple grandeur in those Apollo missions. Perhaps, too, it’s a reminder of the risk we all felt after the Eagle had landed — the possibility that it might be unable to lift off again and the astronauts would be stranded on the Moon. But it may also be that a photograph like this one is as close as we’re able to come to looking directly back into the human past.”

Proposed future lunar landing missions, such as the Google Lunar X Prize, intend to record close-up images of the Apollo Lunar Modules and other artificial objects on the surface."

I have a strong feeling it's John Carmack's Armadillo Team (yes, same John Carmack who invented the video game DOOM and QUAKE) will be the first to land the first commercial (non-government funded) unmanned Lunar Lander right beside one of the Apollo landing sites--can't wait to see the faces of the hoaxers on that day

Armadillo Aerospace - Home

-RODION

[SPRINGFIELD_XD_40]

Case close na sa LUNAR LANDING .

I wanna hear the CONSPIRACY THEORY of 9 - 11 for the nth time .

Bring it on .