CURIOUS THING... i found this in MIT, and it's a apollo landing sequence storyboard... check that... it's interresting to read

. I found this in Google... and the link is break... i force the contain using HTML.... and i'm curious to see the original frame. The link is
http://web.mit.edu/aeroastro/www/labs/halab/media/Apollo-Landing1.ppt Apollo Landing Sequence Storyboard This is a storyboard of the Apollo Lunar landings.
DOI
PDI
Undocking
Separation
LM Descent Orbit
(60 N.M x 50,000 ft)
CSM Orbit
(62 x 58 N.M)
APOLLO
Post-DOI
Prior-PDI
Landing
Approach
Braking
P64
PDI
P63
P65
Optional Modes:
P66
P67
Landing Site
High Gate
Low Gate
Landing
260 N.M.
50,000 ft
~3000 ft
Post-DOI Check residuals (X,Y,Z)
All 0 if DOI burn was perfect
Null X & Z with hand controller
Purpose: avoid landing long/short of target
Compare PGNS and AGS Residuals
PGNS data comes from inertial platform
AGS data comes from body-mounted accelerometers
Re-initialize AGS to match PGNS for descent
Program P00 puts computer in “idle” state so that no other processing might change values sent up by Houston
Use rendezvous radar to track CSM to see that it is working properly and estimate altitude at PDI
Use VHF ranging (dopler measurement) to determine radial velocity relative to CSM
Prior-PDI Determine LM current altitude (~15 mins till PDI)
Scribe marks on MC’s window used to determine how quickly objects on ground move along scale altitude
Crudely, LM alt = (360*rmoon)/(PLM*ratesurface feature move along scale)
rmoon= 5,700,000 ft, PLM = 7200 sec
Crew has chart in cabin that compares tracking rates with expected values @ various positions along orbit
Difference between observation & expected estimate of altitude of perilune & time that will reach it
2nd method of computing altitude = relative motion from CSM
Superimpose 2 methods on graph to get idea of altitude and time history
Verb 47 – command to initialize AGS using PGNS data
Send state vector from one computer to another
Visual altitude check
v=rw
r = altitude that want to know, w = omega, avg rate determined by watching points on the ground, v = velocity (already known)
Alternate altitude check to ensure close to intended starting altitude – important to make sure that landing guidance converges
Change rate scale from 5 deg/sec to 25 deg/sec
Verb 77 – setting attitude control modes for DAP
Pitching & Yawing to gain radio contact
Set up camera
“Master Arm” switch – enable descent engine to fire & explosive bolts in case of descent abort
Check health of circuits that will detonate explosive charges for abort (2 lights)
Check DSKY time against stopwatch time & AGS
Perform manual backup if auto “ullage” to force propellant towards valves does not work
Power up landing radar
Yaw for high-gain aim
Check oxidizer levels
Cycle breaker to reset Propellant Quantity Measurement Device (PQMD) for good readings
Activate RCS system
Activate Digital Event Time (DET)
Press “PRO” on DSKY to accept desired attitude for PDI burn and allow computer to make adjustments to attitude
PDI (Powered Descent Initiation) Landmark Tracking to confirm trajectory prior & right after ignition
Yaw s/c to windows-up orientation (180 deg yaw)
So that when s/c pitches toward upright orientation for landing, will be looking out window at Landing Site (LS)
So that radar could see surface
Radar wasn’t reliable > ~ 30,000 ft
Radar info used to help guidance equation converge
10% thrust until guidance made distance correction to proper geometric position and then went full thrust
Done with hand controller
Timing when pass landmarks
Cross-range position difficult to tell b/c of skewed yaw attitude needed to maintain comm
Yaw vehicle to face-up, feet-forward position (~ 5 mins till P64 Pitchover)
Receive radar data from lunar surface
A11, radar showed 2900’ lower than PGNS altitude
Pitch @ ~77deg
90 deg would be backs parallel to lunar surface & feet forward, 0 deg pitch @ landing, 56 deg @ just prior to P64
Verb16Noun68 – displays range to LS & time remaining in braking phase
Monitor fuel
LMP compares PGNS & AGS
MC checking PGNS values with predicted values
Chart of delta-H as a function of time into burn compared with computer readout of radar data gives confidence in radar data
Update the AGS based on radar data
Use star to check accuracy of LPD
Enter Noun 69 for landing site position update
Compare velocities and attitude with chart showing desired values
Check voltage on descent batteries
Descent Engine Command Overide – allowed astronaut to overide computer’s commanded thrust level.
Altitude and velocity lights go out when computer gets acceptable data from landing radar
Computer uses 5 segment model of mountainous terrain. Delta-H-dot is the difference between the altitude from the landing radar and altitude according to this model (model of approach path terrain 1st included in A-14)
Monitor altitude, h-dot, fuel
Check manual control to ensure that it’s working properly
Call up Noun 68 to check time of P64 occurrence
Enter Verb 57 on DSKY to tell computer to begin accepting radar data
Tapemeter display showed radar data. Pair of tapes with #s on them which moved up and down behind a needle
Approach (P64 Pitchover) Relay info to determine where computer thinks LM will land
LM pilot reads #s to MC to look @ scribed window
1st look @ LS!
Retarget LM using hand controller & LPD
Forward move target downrange, etc
1 “blip” = 1 deg movement
Use of LPD is difficult to begin with, but vehicle is in constant slow pitch ever since P64, so LPD # are up to 2 sec old
Options for redesignation = L,R,down(short), or go over
Call up LPD display by pressing “PRO” on DSKY
MC immediately looks out window
Monitor fuel
Press PRPLNT_QTY MON switch to see fuel & oxidizer % remaining
LM pitches into more upright position
MC looks through scribe marks on window and uses info from PGNS that LMP is giving him to determine where computer thinks the LM will land
MC uses handcontroller to tell computer to redesignate landing site (NOT manual control)
LMP consulting descent profile chart – shows desired descent rate as a function of altitude
Landing (P66 Manual Control) Finish pitching LM over to 0 deg pitch
If take over manual control, vertical velocity is maintained (i.e. no control)
“BINGO” fuel call – “land in 20 sec or abort”
< 100 ft = dust disturbances obscured visibility
Difficult to determine downrange velocities (translational velocities)
Engine shut off @ < 10 ft = acceptable to landing gear
Probes from foot pads touch surface @ 67’
Kill rate of descent to hover and look around
Monitor fuel, speed, altitude
Use “8-ball” (inertial attitude gyro) to determine attitude and if level or not because of dust
MC has controls and is looking out window. In manual control model, MC actually controls pitch, roll, and yaw
Use Rate of Descent (ROD) switch to go in to P66 mode = primary means of controlling vertical velocity
Monitoring rate of descent now (not angles) because no more LPD mode
“cross-pointers” check – horizontal & lateral velocities on attitude gyro (2 needles like an instrument landing system give rate laterally, forward, & aft in fps – want to be 0 when land)
Mode Descriptions P63 = “Braking Phase Guidance”Ignition algorithms (when to ignite DPS for PDI)
Basic guidance logic to steer to desired conditions for beginning approach phase
P64 = “Approach Phase Guidance”Same basic guidance logic, but new set of targets
Provides window point logic for LPD Operation (LP will be maintained along LPD grid)
P65 = “Velocity Nulling Guidance”Nulls all components of velocity to pre-selected values
Used for automatic vertical descent if desired
No position control
P66 = “Rate of Descent”Crew controls s/c attitude & computer commands DPS throttle to maintain desired altitude rate (altitude rate can be adjusted with manual inputs from crew)
Normally entered late in P64 operation prior to P65 switching for manual control
P67 = “Manual Guidance”Maintains navigation and display operations for complete manual control of throttle and attitude
Not used unless P66 is inoperative
Landing ModesLanding Phases Manual Control
Low Gate Landing
Crew Visibility
High Gate
Approach
Min Prop Usage
PDI
Braking
DESIGN CRITERIA
INITIAL EVENT
PHASE
Landing Figures
POST-LANDING ACTIVITIES
Post-Landing
413 Command – contains variables that indicate LM has landed
So any abort will be from the surface
Therefore AGS saves attitude data from gyros
Prepare for immediate lift-off
If footpad starts sinking and lose stability or propellant tank pressure problem, etc.
LPD
Acronyms AGS: Abort Guidance System
PGNA: Primary Guidance & Navigation System
DAP: Digital Autopilot
DPS: Descent Propulsion System
RCS: Reaction Control System
LR: Landing Radar
LPD: Landing Point Designator
DSKY: Display & Keyboard Assembly
NOUN = Data
VERB = Actions
X-axis: Thrust axis (+ = up – away front engine toward rendezvous hatch)
Y-axis: L to R (+ = R side of s/c)
Z-axis: fore & aft (+ = out windows)
LS: landing site
LP: Landing point
That it's .... funny :!: