Pilot Awareness: Correct

RNAV Departure Runway

Selection & Verification
Ensure broad distribution
throughout your organization
 A few pictures say a thousand words…..

• Please review the following slides to help your

organization understand the major operational
issue arising from the Atlanta RNAV SID
implementation.
• The operational model depicted in this scenario
(simultaneous parallel RNAV departures) will be
utilized at numerous locations in the NAS. The
importance of this operational concept can not
be over-emphasized.
• Ensure Pilot Awareness!
The magenta aircraft is the actual position of the airplane
for the purposes of this scenario.
ATC Clearance: DOOLY RNAV
SID…SPA…GSO…as filed

Tower clearance: “Phoenix 123, cleared for takeoff”

Valid Nav Display verification
Valid DOOLY RNAV departure
from runway 27R
 BUT, What if?.....
The pilot loaded runway 26L during his
FMS preflight prior to pushback? And, the
flight was subsequently cleared by ATC to
runway 27R for the DOOLY RNAV
departure… and the pilots do not
remember to change their departure
runway to from 26L to runway 27R……
This is the “God’s Eye” view of the LNAV path IF
the pilot MISTAKENLY inserts runway 26L in the
FMS and does NOT insert 27R before takeoff
 If the pilot loads runway 26L in the FMS, BUT
takes off of runway 27R, the following LNAV path
will be commanded after takeoff.

NOT A GOOD WAY TO LEAVE ATLANTA !!!!!!