{'fraction_non_alphanumeric': 0.0228542407313357, 'fraction_numerical': 0.02031488065007618, 'mean_word_length': 5.061538461538461, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Experimental advanced RNP to xLS approaches with vertical path coding and automatic landings

ABSTRACT We report on the flight test results of an Airbus 320 during novel advanced required navigation performance (RNP) procedures which contain a fixed radius turn that delivers the aircraft onto a short instrument landing system (ILS) precision final. Moreover, the advanced RNP part contains altitude constraints and/or a coded vertical path angle. The approaches were flown automatically with guidance and autothrust as computed by the flight management system. We investigated the use of the fixed radius in conjunction with vertical path options onto (a) the performance of the speed profile for arrival time optimisation, (b) the vertical path during the RNP part of the procedure and (c) the performance of the autoland capability after a curved transition onto an ILS. For the trials, we designed five instrument approaches to a runway equipped with ILS. A RF curve terminates at the ILS intercept point at heights of 550, 750, 1000, 1500 and 2000 ft above aerodrome level and each approach had four different initial approach fixes which corresponded to a track angle change of 30°, 60°, 90° and 180° during the constant radius turn-to-final. We constructed the procedure such that the altitude constraints at initial, intermediate and final approach fix describe a continuous vertical path with minus 2° inclination, transitioning to the –3° glide path of the ILS and intercepting the glide path from below. In all cases, the land mode of the flight guidance computer became active between 316 and 381ft radar altitude. The vertical path following error depended on the coding of the procedure in the database. With coded vertical path angle and altitude constraints, the vertical path following error was never greater than +57 m (above desired flight path) during the RNP part when flown by the automatic flight guidance system without any pilot intervention.