1 - The Black Vault
1 - The Black Vault
1 - The Black Vault
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
PRAETORIAN STARSHIP<br />
of the command line receded and the bottom face<br />
increased its slope angle (bulges on the E<br />
square), the optimum flight vector could be exceeded<br />
without causing target penetration of the<br />
command line. Thus, a heavy aircraft, one weighing<br />
135,000 pounds and whose optimum flight<br />
vector was 3.8 degrees, would receive, if neces -<br />
sary, a pitch command that could double the optimum<br />
flight vector.<br />
In a dive the command line would react in the<br />
opposite direction. <strong>The</strong> front-face bulge would literally<br />
drop out and down toward the bottom of the<br />
E squared as if it were eager to meet new video.<br />
Because the display was exponentially scaled, the<br />
grass accelerated as it slid along the zero command<br />
line toward the aircraft.<br />
A satisfactory TFR would maintain terrain<br />
clearances within + or – (10 percent of set clearance<br />
+ 50 feet) over level terrain and at or above<br />
70 percent of set clearance over hilly terrain.<br />
Clearances were checked by radar altimeters, and<br />
substandard performance could normally be identified<br />
visually on the E squared presentation.<br />
Over level terrain the grass would hug the bottom<br />
face of the command line. Grass penetration of<br />
the command line normally occurred during<br />
lower-than-desired terrain clearances, whereas<br />
grass/command line separation was indicative of<br />
higher-than-programmed altitudes. <strong>The</strong> most<br />
common cause of terrain clearance problems was<br />
found in antenna stabilization. For this reason a<br />
“dual-angle indicator” mounted on the navigator’s<br />
panel was frequently monitored during level portions<br />
of flight to determine the most reliable pitch<br />
angle input.<br />
Occasionally, the aircraft might encounter an<br />
obstacle that it could not clear safely. For that<br />
reason a distinct obstacle warning (OW) zone was<br />
built into the TF template. Any obstacle that<br />
penetrated its parameters would trigger a full fly<br />
up and sound a beeping warning horn. This<br />
would rarely occur on a well-planned route with<br />
the aircraft flying a constant heading. <strong>The</strong> pilot,<br />
who was monitoring his E squared presentation,<br />
could see the obstacle penetrating the zero command<br />
line prior to its reaching the OW zone.<br />
Most frequent OW alarms were sounded by<br />
other aircraft flying through the OW portion of<br />
the TF scan or by hilly terrain that entered the<br />
OW area sideways during turning maneuvers or<br />
on-course corrections. Whenever an unplanned<br />
OW occurred, an immediate climb command<br />
was displayed on the ADI, and an immediate<br />
corrective evasive action was initiated. Evasive<br />
action included application of maximum climb<br />
power, initiation of a climb, and a turn in the<br />
direction of lower terrain or in the direction provided<br />
by the navigator.<br />
On occasions, TF flight was conducted over<br />
water, snow, sand, and other surfaces that did<br />
not reflect radio frequency energy, including<br />
very smooth and level terrain. Under these con -<br />
ditions radar echoes were of insufficient strength<br />
to produce video and generate necessary climb<br />
commands. To avoid a disastrous dive command<br />
into earth’s surface, the system was programmed<br />
to switch to radar altimeter operation whenever<br />
the TFR commanded a dive below desired clearance<br />
altitude, and there was no visible grass in<br />
the two well-defined altimeter override inhibit<br />
zones located within the template. While operating<br />
on altimeter override, the system’s performance<br />
tolerances were the same as for level<br />
terrain.<br />
<strong>The</strong> cross-scan mode of operation combined the<br />
features of TA and TF and was the mode most<br />
frequently employed during terrain-following<br />
flights. In this mode the antenna alternated between<br />
horizontal and vertical scans, providing<br />
either TF or TA video to the pilot’s indicator<br />
and TA video to the left navigator’s indicator.<br />
Because of alternating scans, there was a pause<br />
in the TF display during the TA antenna sweep<br />
and visa versa. This video pause did not affect<br />
continuous command input to the pitch bar. To<br />
keep the time interval between successive TF<br />
sweeps at a minimum, the horizontal-scan azimuth<br />
was reduced to + or –20 degrees. Even<br />
though this TA azimuth reduced the coverage of<br />
the normal TA mode by more than one-half, the<br />
compromise gave the left navigator sufficient<br />
sector scan to monitor above flight-level obstacles<br />
during terrain-following operations. TA monitoring<br />
was also available to the pilot who could<br />
select either E squared or TA video by flipping a<br />
toggle switch (fig. 18).<br />
During all TF turns, the scan pattern provided<br />
climb and dive commands based on terrain<br />
that passed laterally across the aircraft’s<br />
nose. Those commands could change rapidly,<br />
with changing terrain profile, from climb to dive<br />
and back again until the aircraft was firmly established<br />
on its new course. For this reason descending<br />
turns were never made during terrain<br />
following. A turn was made either level or<br />
climbing, provided the pitch bar commanded a<br />
climb. A dive command on the pitch bar would be<br />
ignored even when flying over water on altimeter<br />
46