PPRuNe Forums - View Single Post - RNP SID with RF leg
View Single Post
Old 19th Jul 2012, 17:20
  #65 (permalink)  
FlightPathOBN
 
Join Date: Mar 2011
Location: engineer at large
Posts: 1,409
Likes: 0
Received 0 Likes on 0 Posts
sounds good terpster,

I would also add that currently, the public RNP design criteria does not address DEP. It will be included in 8260.PBN, whenever that may happen...RNP 1 DP Specials


other RNP 1 reference....
RNP 1 AC90-105

(1) Pilots must not fly an RNP 1 procedure unless it is retrievable by the procedure name from the onboard navigation database and conforms to the charted procedure. Numeric values for courses and tracks should be automatically loaded from the RNP navigation database for required leg types. However, the procedure may subsequently be modified through the insertion or deletion of specific waypoints in response to ATC clearances. The manual entry or creation of new waypoints, by manual entry of latitude and longitude or rho/theta values is not permitted.
Additionally, pilots must not change any database waypoint type from a fly-by to a fly-over or vice versa.
(2) The pilot must confirm the correct procedure is selected. This process includes confirmation of the waypoint sequence, reasonableness of track angles and distances, and any other parameters that can be altered by the pilot, such as altitude or speed constraints. A navigation system textual display or navigation map display must be used.
(3) For RNP 1 procedures, pilots must use a lateral deviation indicator, flight director, or autopilot in lateral navigation (LNAV) mode. Pilots of aircraft with a lateral deviation display must ensure lateral deviation scaling is suitable for the navigation accuracy associated with the procedure.

Functional Requirements.
(1) Autopilot and Flight Director. RNP procedures with RF legs require the use of an autopilot or flight director with at least “roll-steering” capability that is driven by the RNP system. The autopilot/flight director must operate with suitable accuracy to track the lateral and, as appropriate vertical paths required by a specific RNP procedure.
(2) The aircraft must have an electronic map display depicting the RNP computed path of the selected procedure.
(3) The flight management computer, the flight director system, and the autopilot must be capable of commanding a bank angle up to 25 degrees above 400 feet AGL.
(4) Maintaining LNAV in missed approach. If abandoning a procedure while on an RF Leg or initiating a go-around or missed approach (through activation of TOGA or other means), the flight guidance mode should remain in LNAV to enable display of deviation and display of positive course guidance during an RF leg. If the aircraft does not provide this capability, crew procedures must be used that assure the aircraft will adhere to the specified flight path during the RF Leg segment.
NOTE: For missed approaches with a RF Leg, the flightcrew must be able to couple the autopilot or flight director to the RNP system (engage LNAV) by 500 feet AGL.

Last edited by FlightPathOBN; 19th Jul 2012 at 22:57.
FlightPathOBN is offline