737 Flight Crew Operations Manual
Warning Systems -
System Description
Boeing Proprietary. Copyright © Boeing. May be subject to export restrictions under EAR. See title page for details.
D6-27370-866-EGP 15.20.17
Assumptions, Limitations and Constraints
Defined nominal runway length for landing and advisory hold times are options
specified by an operator.
In flight callouts and alerts are based on an algorithm that numerically subtracts
the landing runway touchdown zone elevation in the GPWS database from the
pressure altitude of the airplane. The term "above field elevation" is used in the
system description for these altitudes.
Note:
• RAAS callouts and alerts are based on RAAS airport runway database
details and GPS position
• RAAS does not include knowledge of ATC clearances or flight crew
intent
• RAAS does not take into account airplane performance factors such as
airplane weight, wind, runway conditions, slope, air temperature, or
airport altitude
• absence of a RAAS annunciation does not ensure that the that a runway
is appropriate for takeoff or landing
• RAAS annunciations do not ensure that a runway can, or cannot, be
safely used for takeoff or landing
• The Flight Crew is responsible by other means to ensure correct runway
selection. RAAS does not include knowledge of Notice to Airmen
(NOTAM) or Automatic Terminal Information Service (ATIS)
• RAAS callouts and alerts are not intended for navigation purposes
• RAAS is not designed to enhance traffic awareness.
RAAS callouts and alerts have a lower priority than any GPWS alert, including
Radio Altitude callouts. Some may reoccur, depending on airplane position, when
the higher priority advisory clears.
Voice Callouts, Alerts
and ND Messages
Description
ONE HUNDRED
REMAINING
Sounds once each time the airplane:
• is within 20 degrees of the runway heading,
and
• is within 100 feet of the end of a runway, and
• ground speed is less than 40 knots
September 25, 2014
To Next Page
Loading...
