HT1000 GNSS Navigation Management System Pilot’s Guide This Pilot's Guide contains information developed by Honeywell/ Trimble to provide the operational procedures for the HT1000 GNSS Navigation Management System. The Supplemental Type Certifi- cate (STC) holder is solely responsible for the requirements for use and revision status of this manual. Pilots using the avionics system described in this document are required to maintain Lateral and Vertical Situational Awareness at all times through the use of current and approved en route, sectional, and other navigational charts. The avionics system herein described is designed to provide pilots with a TSO C-129 (A1) navigation capabil- ity. However, pilots are advised to use all available flight-following techniques appropriate for the phase of flight to ensure that a valid mental picture of the desired route is maintained at all times. Honeywell Helping You Control Your World Trimble €28-9653-011-03 August 1999 Printed in U.S.A. ©1999 Honeywell inc. Rev3 8/99PROPRIETARY NOTICE This document and the information disclosed herein are proprietary data of Honeywell Inc. Neither this document nor the information contained herein shall be reproduced, used, or disclosed to others without the written authorization of Honeywell Inc., except for training on recipient's equipment. NOTICE — FREEDOM OF INFORMATION ACT (5 USC 552) AND DISCLOSURE OF CONFIDENTIAL INFORMATION GENERALLY (18 USC 1905) This document is being furnished in confidence by Honeywell Inc. The information disclosed herein falls within exemption (b)(4) of 5 USC 552 and the prohibitions of 18 USC 1905.Honeywell's Continuous Quality Process Date. Date Received Ms AV2CC85Co {for Honeywell use only) READER COMMENTS (Mail or FAX this form to [602] 436-7125) Honeywell welcomes all comments and recommendations to improve future editions of this publication Your Name CompanyiAittine Address, State Country Zip Phone EMail Honeywell Pub, No_____________ Manual Title. Whatis important? Rating (Rate 1-10, 10= most | Way Boliow| Does Not Exceeds rm Description imponany) | Needs [Meet Needs| Satistactory| Needs | Delighted Color Binders: ‘Color Photos. Line Drawings: ]°)5]> Easy 10 Follow Graphics e ‘Accurate Data 6 Sections Contain Loge! Matorial 7. Datais Easy toFing ‘& Inkial Delivery is Timely ©. Revision is Timo, 40. System Faukts Well Documented 11. Uso of Book {or Trarsng 12 Other 13, Overall Raiing ‘COMMENTS/RECOMMENDATIONS: LOGAL REPRODUCTION ENCOURAGED (reusing by mal, ponte tape closed: postal reglatonsprchbt use staples) 20038000 (3198) Honea neHoneywell & Trimble HT1000 GNSS Navigation Management System Pilot’s Guide To all holders of the HT1000 GNSS Pilot's Guide: This is to inform HT1000 customers currently on distribution for the HT1000 Pilot's Guide that the current revision (Rev 3) supersedes all previous revisions. Revision 3 contains all changes to date and is compatible with NPU Operating Software Load 6.0 Revision 3 8/99 PUB. NO. C28-3653-011-03 Pilot’s Guide Owner Please Note: If you are not already on the Honeywell mailing list for revisions to this publication OR if you have a change of address, please call 602-436-6900 with the following information: Your Publication Number (lower right corner Cover Page) Airline Name or Company Name Your Full Name (last name first — please) Complete Current Address Telephone NumberHT1000 GNSS PILOT’S GUIDE TABLE OF CONTENTS Page 3) PILOT OVERVIEW... wie 1-1 2. FLIGHTMANAGEMENT.............. wed 24 2:2 2.3 2.4 25 SYSTEM DESCRIPTION . a 2-2 2.1.1. Navigation Processor Unit (NPU) ... 2-3 2.1.2 GPS Antenna ........ 2-3 2.1.3 Multifunction Control ‘Display Unit (MCDU).. 2-3 2. SYSTEM INTERFACES SYSTEM FUNCTIONS 2.3.1 Guidance 2.3.2 Navigation Database MULTIFUNCTION CONTROL DISPLAY UNIT . 2.4.1 ‘MCDU ‘Display Conventions 2.4.2 MCDU Functional Areas . 2.4.2.1 Display Screen . 2.4.2.2 Line-Select Keys (sk) 2.4.2.3 Annunciators 2.4.3 Keyboard... 2434 Function Keys a 2.4.3.2 Special Purpose Keys 2.4.3.3. Alpha Numeric Keys .. 2.4.4 Page Formats and Data Labels . 2.4.5 Data Entry... TERMINOLOGY 022 Late ccsslin nctieaciesanvensvenceoronn 218 9; “FLIGHT OPERATIONS tisrrawarcnrecraret ee el 31 PREFLIGHT 3.1.1 Identification Page 3.1.1.1 Position Reference Page.. 3:1:1.2 POS REF Page 2/2... 3.1.1.3. POS REF INFO Page... i Rev 3 8/99HT1000 PILOT’S GUIDE 3.1.2 Ow on Www oND 3.2 TAKEOFF/CLIMB 3:24 3:2:2 9.3; (CRUISE ares s2ey 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5, 3.4 DESCENT .. 3.44 3.4.2 3.4.3 Inertial Systems Interface 3.1.2.1. POS INIT Page Flight Planning ..... 3.1.3.1 Route Page 1 3.1.3.2 Route Page 2 3.1.3.3 Departure Selection Performance Initialization Route Legs 3.1.5.1 Flight Plan Route Activation Route Data Page ..............00 Wind Input STapelavnreat Automatic Flig| Direct-To Intercept Course . Route Modification 3.3.1.1 Erasing an ACT RTE Leg 1.2 Route Discontinuity... 1.3 Select Desired Waypoint Page . 1.4 Pilot-Defined Waypoints ....... e 1.5 ABEAM PTS> and RTE COPY> Prompts .. 3.3.1.6 OFFSET ACTIVE RTE LEGS Pages 3.3.2.1. RTE DATA.. PROGRESS Pages 3.3.3.1 Progress Page 1/2. 3.3.3.2 Progress Page 2/2 . Position Report . Holding Patterns 3.3.5.1 ACT RTE 1 — HOLD Pag 3.3.5.2 Holding Pattern Guidance 3.3.5.3. MOD HOLD PENDING .. Ww wo Descent Path Construction 3.4.1.1 Deceleration Segment 3.4.1.2 Descent Path Construction Display of VNAV Data (Summary) ... ACT RTE LEGS Page (VNAV Information) Rev3 8/99HT1000 PILOT’S GUIDE 3.4.4 PROGRESS Page (VNAV nrerpator) 3.4.5 DESCENT Page ... 3.4.6 A eee a DA SEONANOS eraaancee rc 3.5 ARRIVALIAPPROACH .........-. 3.5.1 Arrival Selection 3.5.2 Approach Terminology Use 3.5.3 Non-Precision Approaches (Lateral Guidance Only)... 3.5.3.1 Selecting a Non- Precision Approach ... EO OO 3.5.3.2 Course Deviation Indications .. 3.5-7 3.5.3.3 Flight Director Indications .. 3.5-7 3.5.3.4 Indications on the LEGS Page 3.5-7 3.5.3.5 Approach Scratchpad Annunciations . Ree iesersas 3.5.4 Example Non-Precision ‘Approach | (Lateral Guidance Only)... 3.5.4.1 En Route and Terminal Area : 3.5.4.2 Transition to the Approach from a Procedure Turn .. pens 3.5.4.3 Aircraft Inbound tothe Final Approach Course .. 3.5.4.4 Final Approach Fix Inboun 3.5.4.5 Missed Approach .... 3.5.5 SCAT 1 Precision Approaches 3.5.5.1 Differential GPS System Overview 3.5-15 3.5.5.2 DGPS Airborne Equipment.............3.5-17 3.5.5.2.1 Navigation Select Panel . 3.5-18 3.5.5.2.2 GPS Status Annunciators 3.5.6 SCAT 1 Example Approach ..... 3.5.6.1 Aircraft Outside Terminal Area 3.5.6.2 Aircraft in Terminal Area .. 3.5.6.3 Final Approach Fix Inboun« 3.5.7 Accuracy and Integrity Requirements. 3.5.7.1. RAlMat Destination . 3.6 MISCELLANEOUS . 3.6.1 REF NAV Dat iii Rev3 8/99HT1000 PILOT’S GUIDE 3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.6.7 3.6.8 3.6.9 3.6.10 3.6.11 3.6.12 APPENDIXA A.1 ALERTING MESSAGES . A.2 ADVISORY MESSAGES A3 ENTRY ERROR MESSAGES A4 MCDUANNUNCIATORLIGHTS APPENDIX B APPENDIX C APPENDIX D APPENDIX E APPENDIX F FIX INFO asecasesee Z .3.6-4 3.6.2.1 Fix Info Page . ACTIVE PLAN PREDICTION 3.6.3.1 Required Navigation Performance (RNP) 3.6.3.2 Active Route Integrity Data Index and Nearest Pages Dead Reckoning and HDG/TAS OVERRIDE .. i NAV Database (NDB) Crossload Transfer of USER DATABASES . SV Data Page .. Message Recall User Routes..... 3.6.10.1 Create and Save User Routes 3.6.10.2 Search the Data base for a User Route.......... se 3.6.10.3 Load a User Route... 3.6.10.4 Delete User Routes ..... User Waypoints Storage and Retrieval 3.6.11.1 User Waypoint Retrieval 3.6.11.2 Delete User aay nent HT1000 Page Tree.. HT1000 MESSAGES ....... CDU DISPLAYS... HOW THE GPS SYSTEM WORKG.............C-1 COUNTRY CODES........ sid GLOSSARY i. scosssevacissceaseeves sed INDEX sieccmmacaras: wl ad Rev3 8/99HT1000 PILOT’S GUIDE List of Revised Pages PAGENO. REV STATUS PAGENO. REV STATUS Title Page Rev3 8/99 3-2 Rev3 8/99 Proprietary 3-3/4 Rev3 8/99 Notice - 5/96 Table of Contents SECTION 3.1 i Rev 3 8/99 ‘ 3.44 Re 8/99 i Revs a9 344 Reva 8/99 i Rev 3 899 34.0 Rev3 8/99 iv Rev 3 8/99 3.13 Rev 3 3/99 3.14 Rev3 8/99 SECTION 4 31-5 Rev3 g/e9 4-1 Rev 3 8/99 3.16 Rev3 aso 34-7 Rev3 8/99 SECTION 2 3.1-8 Rev3 8/99 2i Rev3 3/99 31-9 Rev 3 8/99 3.1-10 Rev3 8/99 24 Rev 3 8/99 3.1-11 Rev3 8/99 22 Rev 3 6/96 34-12 Re : v3 8/99 rs Revs See sans Rev 3 8/99 oo Revs Bee aid Rev 3 8/99 2-5 Rev3 8/99 3.1-15 Rev 3 8/99 26 Rev 3 8/99 3.1-16 Rev3 8/99 27 Rev3 8/99 3.1-17 Rev3 8/99 28 Rev 3 8/99 3.1-18 Rev3 8/99 29 Rev3 6/96 31-19 Rev 3 8/99 240 Rev 3 8/99 3.1-20 Rev 3 8/99 211 Rev 3 3/99 3.1-21 Rev 3 8/99 242 Rev 3 8/99 3.1-22 Rev 3 8/99 2-13 Rev 3 8/99 3.1-23 Rev3 8/99 2-14 Rev3 8/99 3.1-24 Rev 3 8/99 245 Rev3 8/99 3.1-25 Rev3 8/99 2-16 Rev 3 8/99 47 Reva eo | 38 Rev3 8/99 . oy 3.1-27 Rev3 3/99 3.1-28 Rev3 8/99 SECTIONS 31-29 Rev3 8/99 34 Rev 3 8/99 3.1-30 Rev 3 8/99 3 Rev3 gg 34-31 Rev3 8/99 3: Rev3 B99 3.132 Rev3 8/99 iv Rev3 B99 3.133 Rev3 8/99 3-1 Rev 3 8/99 3.1-34 Rev 3 8/99 3.1-35 Rev 3 8/99HT1000 PILOT’S GUIDE PAGENO. REV STATUS 3.136 3.1-37 3.1-38 3.1-39 3.24 3.2-1 3.22 3.23 3.24 3.2-5 3.26 Rev 3 Rev 3. Rev3 Rev 3 SECTION 3.2 Rev 3 Rev 3 Rev 3 Rev3 Rev3 Rev3 Rev3 SECTION 3.3 Rev 3 Rev 3 Rev3 Rev 3 Rev 3 Rev 3 Rev 3 Rev3 Rev3 Rev3 Rev 3 Rev 3 Rev 3 Rev3 Rev 3 Rev 3 Rev 3 Rev 3 Rev 3 Rev 3 Rev3 Rev 3. Rev3 Rev 3 Rev 3 Rev 3 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 PAGENO. _REV 3.3-26 3.3-27 3.3-28 3.3-29 3.3-30 3.3-31 3.44 3.4-1 34-2 3.43 3.4-4 3.4-5 3.4-6 34-7 3.48 3.49 3.4-10 3.4-11 3.4-12 3.4-13 3.4-14 3.4-15 3.4-16 3.4-17 3.54 35-1 3.5-2 3.53 3.54 3.55 3.56 35-7 35-9 3.5-10 3.5-11 3.5-12 3.5-13, Rev 3 Rev 3 Rev3 Rev3 Rev 3 Rev 3 SECTION 3.4 Rev 3 Rev 3 Rev3 Rev3. Rev3 Rev3 Rev3 Rev 3 Rev3 Rev3 Rev 3 Rev3 Rev 3. Rev 3 Rev3 Rev 3 Rev 3 Rev 3 SECTION 3.5 Rev 3 Rev3 Rev3 Rev3 Rev3 Rev3 Rev 3 Rev3 Rev3 Rev3 Rev 3 Rev 3 Rev 3 Rev 3 STATUS 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99 8/99HT1000 PILOT’S GUIDE PAGENO. REV STATUS PAGENO. REV STATUS 35-14 Rev3 899 3.6-25 Rev 3 8/99 3.5-15 Rev3 8/99 3.6-26 Rev3 8/99 3.5-16 Rev3 899 3.6-27 Rev3 8/99 35-17 Rev3 8199 3.6-28 Rev3 8/99 35-18 Rev3 8/99 -3.6-29 Rev3 8/99 35-19 Rev3 8/99 3.6-30 Rev3 8/99 3.5-20 Rev3 8/99 -3.6-31 Rev 3 8/99 3.5-21 Rev3 899 3.6-32 Rev3 8/99 3.5-22 Rev3 899 3.6.33 Rev3 8/99 35-23 Rev3 899 3.6.34 Rev3 8/99 3.5-24 Rev3 899 3.6.35 Rev 3 8/99 3.5-25 Rev 3 899 3.6-36 Rev3 8/99 3.5-26 Rev3 899 3.6-37 Rev3 8/99 3.5-27 Rev3 899 3.6-38 Rev 3 8/99 3.6-39 Rev3 8/99 3.6-40 Rev3 8/99 Seas 3.6-41 Rev3 8/99 36-1 Rev3 899 3.6-42 Rev 3 8/99 3.64 Rev 3 899 3.6-43 Rev3 8/99 3.6-2 Rev 3 899 3.6-44 Rev3 8/99 3.6-3 Rev 3 899 3.6-45 Rev 3 8/99 3.6-4 Rev 3 8/99 3.6-46 Rev 3 8/99 3.6-5 Rev 3 8/99 3.6-47 Rev 3 8/99 3.6-6 Rev 3 8/99 3.6-48 Rev 3 8/99 3.6-7 Rev3 8/99 3.6-49 Rev 3 8/99 3.6-8 Rev3 8/99 3.6-9 Rev3 3/99 3.6-10 Rev3 8/99 BERENDIA: 3.6-11 Rev 3 egg A Rev 3 8/99 3.6-12 Rev3 eg A Rev 3 8/99 3.6-13 Rev 3 agg «= A Rev 3 8/99 3.6-14 Rev 3 agg | AS Rev 3 8/99 3.6-15 Rev 3 a9 AS Rev 3 8/99 3.6-16 Rev3 ag AS Rev 3 8/99 3.6-17 Rev 3 B99 AS Rev 3 8/99 3.6-18 Rev 3 B99 AT Rev3 899 3.6-19 Rev3 ggg AB Rev 3 8/99 3.6-20 Rev 3 ggg AD Rev3 8/99 3.6-21 Rev3 899 A10 Rev3 8/99 3.6-22 Rev3 8/99 3.6-23, Rev 3 8/99 3.6-24 Rev 3 8/99HT1000 PILOT’S GUIDE PAGENO. REV __ STATUS PAGENO. REV __ STATUS APPENDIX B APPENDIX F BA Rev 3 8/99 FA Rev 3 8/99 B2 Rev 3 8/99 [FF Rev3 8/99 B-3 Rev 3 8/99 F-3 Rev3 8/99 B4 Rev 3 8/99 F4 Rev3 8/99 B-5 Rev 3 8/99 F-5 Rev 3 8/99 F-6 Rev 3 8/99 APPENDIX C F7 Rev 3 8/99 C1 Rev 3 8/99 C-2 Rev3 8/99 C-3 Rev3 8/99 C4 Rev 3 8/99 C5 Rev3 8/99 C6 Rev 3 8/99 C7 Rev 3 8/99 C8 Rev 3 8/99 c-9 Rev 3 8/99 C10 Rev 3 8/99 C11 Rev 3 8/99 APPENDIX D D1 Rev 3 8/99 D-2 Rev 3 8/99 D-3 Rev 3 8/99 APPENDIX E E11 Rev 3 8/99 E-2 Rev 3 8/99 E-3 Rev 3 8/99 E-4 Rev 3 8/99 E5 Rev 3 8/99 E6 Rev 3 8/99 E-7 Rev 3 8/99 Es Rev 3 8/99 E-9 Rev 3 8/99 E10 Rev 3 8/99 LR-iv ‘a i i a aa aEun PILOT OVERVIEW INTRODUCTION The HT1000 Global Navigation Management System is a lightweight, state-of-the-art navigation system that receives and processes Global Positioning System (GPS) signals to provide worldwide navigation capability. The HT1000 meets or exceeds the en route, terminal, and instrument approach navigation standards set forth by TSO C129, AC 20-129, AC 20-138, and AC 20-130. The system also meets the requirements for primary means of navigation in Oceanic/Remote operation set forth in FAA Notice N8110.60. When interfaced to a frequency-agile DME transceiver or inertial system, the HT1000 meets the requirements of TSO C115b. The Honeywell/Trimble HT1000 Global Navigation Management System Pilot's Guide provides the information necessary to operate the HT 1000. It provides guidance in flight plan management, navigation, and information display. The pilot's guide contains details sufficient to answer the majority of operational questions that arise during system use. This guide is organized to: « Provide a general overview. * Step through system operation as it may be used in airline operations. ® Provide information about system functions. Appendices provide reference information useful in understanding this guide and the Honeywell/Trimble Global Navigation Management System Every effort has been made to ensure the accuracy of published information. Questions about aircrew related questions, problems, or comments should be directed to Honeywell Flight Operations at (602) 436-1446. This manualis intended as a guide and does not supersede Honeywell Trimble, any certifying authority, or any airline approved procedures. It is for system familiarization only. 14 Rev3 8/99Beours FLIGHT MANAGEMENT 2. FLIGHTMANAGEMENT........... 2A aie 2.3 24 25 TABLE OF CONTENTS SYSTEM DESCRIPTION 2.1.1 Navigation Processor Unit (| (NPU) .. 2.1.2 GPS Antenna 2.1.3. Multifunction Contro! isplay Unit (MCD SYSTEM INTERFACES.........0-04 SYSTEM FUNCTIONS 23.1 Guidance.......... 2.3.2 Navigation Database MULTIFUNCTION CONTROL DISPLAY 24.1 MCDU Display ‘Conventions 2.4.2 MCDU Functional Areas 2.4.2.1 Display Screen 2.4.2.2 Line-Select Keys (LSK) .. 2.4.2.3. Annunciators ..... 2.4.3 Keyboard... 2.4.3.1 Function | Keys ... 2.4.3.2 Special Purpose Keys : 2.4.3.3. Alpha Numeric Keys .. 24.4 Page Formats and Data Labels 24.5 Data Entry... . Boat OOmmOeON ANNAG5 OD YPYUYMYUYYOYYNYNNANND TERMINOLOGY a 2i Rev 3 8/99The HT1000 Global Navigation Management System is a full flight regime navigation system that performs navigation and route flight planning. It reduces the work load in route planning, navigation, aircraft guidance, and monitoring of flight progress. The pilot defines the route from the origin to the destination airport by data entry into the Multifunction Control Display Unit (MCDU). The system provides automatic aircraft guidance along the defined path while computing and displaying current and predicted progress along the route. DEPARTURE ARRIVAL Keaen PROCEDURES ENROUTE PROCEDURES ercuon (RWY, SID, TRANS (APPR, STAR, TRANS) IpRocEDURES| xo 1 nase 1 ' DEST rion aero | ! \ | lil 1 1 1 1 1 1 1 1 1 1 f Il ! 1 1 1 1 ' 1 ! 1 1 ' 1 ! ! 1 i) 1 ! 1 1 1 1 ! I 1 1 Loescent ! GOAROUND CLIMB ——="T—"— CRUISE “——-- APPROACH == TAKEOFF 63859-04-050# Figure 2-1 Flight Profile The HT1000 system provides en route and terminal area guidance, autopilot coupling, roll steering and vertical deviation (non-coupled), along defined lateral procedures, including Standard Instrument Departures (SIDs), Standard Terminal Arrival Routes (STARs), approaches, and holding patterns. It can fly lateral offsets to the defined path. In addition, the HT1000 computes predicted arrival times at waypoints along the route. It also predicts arrival time at the flight's destination. The HT1000 also provides vertical navigation guidance (no autopilot coupling) from the top-of-descent down to the end-of-descent point (for example, a runway or missed approach point). NOTE: The user must verify the legality of system certification for flying GPS Approaches with individual aircraft types. 2A Rev3 8/99HT1000 PILOT’S GUIDE 2.1 SYSTEMDESCRIPTION This section examines the following HT1000 components, which are pictured in Figure 2-2: * Navigation Processor Unit + GPS Antenna + Multifunction Control Display (MCDU) Figure 2-2 HT1000 System Components Rev3 8/99 22HT1000 PILOT’S GUIDE 2.1.1 Navigation Processor Unit (NPU) The NPU is the processing unit of the HT 1000 system. It contains the GPS receiver, computers, navigation data base, and the required external system interfaces. The NPU receives and processes the GNS/FMS signal data from the GPS Antenna and other aircraft systems, for example the Air Data Computer, to compute position and course information. It transmits data to the MCDU for display and to other aircraft systems such as the autopilot, HSI, and CDI. Anonvolatile, Honeywell-supplied regional data base is stored in the NPU. The HT1000 navigation data base includes the information the pilot would normally determine by referring to navigational charts and maps. This information is displayed on the Multifunction Control Display Unit (MCDU). 2.1.2 GPS Antenna The omnidirectional GPS Antenna receives, amplifies, and conditions signals from orbiting satellites. The Antenna transmits these signals to the GPS receiver in the NPU 2.1.3 Multifunction Control Display Unit (MCDU) The Multifunction Control Display Unit (MCDU)is the interface between the pilot and the HT1000. It is used to enter, monitor, and revise routes; to display information; and to select operational modes. It provides readout capability along with verification of data entered into memory. Route and advisory data are continuously available for display on the MCDU. The system is capable of handling seven 739 protocol subsystems. The MCDU provides a full alphanumeric keyboard plus function and line-select keys (LSKs). The keyboard assembly contains advisory annunciators and a display brightness control. The MCDU is shown in Figure 2-3. 23 Rev3 8/99HT1000 PILOT’S GUIDE PREV | § NEXT |— MENU, rN Ul [e) Vv 63653-07-01c Figure 2-3 HT1000 Multifunction Control Display Unit NOTE: A fold-out page illustrating the MCDU is located at the back of this Guide for your convenience. Rev 3 8/99 24T1000 PILOT’S GUIDE 2.2 SYSTEMINTERFACES Figure 2-4, Functional Block Diagram, shows the relationship of the HT1000 components, plus existing aircraft components that interface with the NPU; forexample, HSI, ADC, Compass, and Oleo (air/ground logic). Correct aircraft, engine, and data base configuration may be confirmed on the MCDU Identification (IDENT) page on aircraft power-up. | ANNUNCIATORS —>| HSI/ADI/CDI AUTOPILOT GPS ACU NPU MODE SELECT G3653-04-051# Figure 2-4 Functional Block Diagram 25 Rev3 8/99HT1000 PILOT’S GUIDE 2.3 SYSTEMFUNCTIONS The HT1000 processes pilot-entries from the Multifunction Control Display Unit (MCDU). It provides navigation and guidance information to the autopilot through lateral steering commands to the flight control systems. 2.3.1 Guidance The HT1000 provides guidance when a route has been entered and activated. The system automatically sequences and updates route legs. The guidance function compares the aircraft's actual position with the desired flight path and generates lateral steering commands to the autopilot. Direct guidance from the aircraft's present position to any NAV data base waypoint is possible. 2.3.2 Navigation Data Base The HT 1000 navigation data base includes information the pilot would normally determine by referring to navigational charts and maps. This information can be displayed on the Multifunction Control Display Unit (MCDU). The data base contains en route data, including waypoints and airways; terminal data such as airports, runways, marker beacons, and terminal waypoints; SIDs, STARs and approaches; and supplemental data including the names of facilities and countries. Navigation-based standard data is updated on a 28-day cycle that corresponds to the normal revision cycle for navigation charts. The HT1000 NPU can store two complete cycles of the navigation data base, and provides a window of time in which to load the new data base. The data base part number (which identifies the customer, data cycle, and revision number) and the effective date periods are displayed on the MCDU IDENT page. NOTE: The HT1000 is supplied with a non-volatile Honeywell regional data base stored in the NPU. Rev3 8/99 26HT1000 PILOT’S GUIDE 2.4 MULTIFUNCTION CONTROL DISPLAY UNIT The MCDU is the pilot interface for operation and data entry of the HT1000 and also displays routes and advisory data on a color 5.5" liquid crystal display. The display has 14 lines of data with 24 characters per line. The MCDU keyboard provides for data input and display selection and control. Refer to the MCDU as shown in Figure 2-5 for the following explanations. FUNCTION KEYS DISPLAY eas FIELD LINE SELECT KEYS SAS LOS73S 3NI7 BRIGHT/ Reais) DIMADJUST SPECIAL PURPOSE KEYS ANNUNCIATORS NUMERIC KEYS 63653.07-01¢ Figure 2-5 HT1000 Multifunction Control Display Unit NOTE: A fold-out page showing the MCDUis located at the back of this Guide for your convenience. 27 Rev3 8/99HT1000 PILOT’S GUIDE 2.4.1 MCDU Display Conventions A display title appears on the top line of every display screen. The number of the currently displayed screen appears in the upper right corner. A slash separates the display screen number from the number of pages of related data (for example, page 1 of Sis displayed 1/3). Ifmore than one page of data is available, the and (next) keys are used to change pages. Labels are shown in SMALL font except for the page title. The colors are assigned as follows: Data is generally {0M Waypoints, Courses, Distance, and ETAs. * The current active flight leg is displayed in [IXEEEEMBon the LEGS page, the RTE DATA page, and the PROG page. The active vertical waypoint on the descent page is also displayed in magenta. * Caution warnings Aig YELLOW | Entry error and advisory messages are GI - * Page TITLES, page numbers (1/3-2/3 etc.), altitudes (pilot-entered) and label lines are| * Action line-select keys such as and prompts indicate that if the LSK adjacent to the prompt is pressed a corresponding page of data will be displayed or an action will take place within the NPU. 2.4.2.3 Annunciators There are two annunciators located on the lower left side of the MCDU. These annunciators display the following: MSG - The WHITE MSG display light illuminates when a CDU message is pending. CALL — The AMBER CALL light will be used in the future for uplinks. Presently, it is inoperative. 29 Rev3 8/99HT1000 PILOT’S GUIDE 2.4.3 Keyboard There are 66 keys: 7 function keys, 8 special character keys, 12 line- select keys (LSK) (6 on the leftand6 on the right), and 39 alphanumeric keys. 2.4.3.1 Function Keys The function keys access the pages for display on the LCD. Once the desired page is displayed, the pilot can find information and enter or retrieve data. A brief description of these function keys follows. RTE Key — The (=) key provides access to the Route pages. Itis used for selection, entry, and modification of routes. LEGS Key — The [ts] key provides access to LEGs pages where details, such as course and distance, of each leg of the route are displayed. Modification of individual legs can be accomplished on the LEGs pages. DEP/ARR Key — The key provides access to departure and arrival information for selected airports. HOLD Key — The (#0) key allows for the definition and execution of holding patterns. PROG Key — The key provides access to flight progress data on the current leg of the flight. VNAV Key - The [«*) key provides access to the PERF INIT and DESCENT pages. The PERF INIT page allows entry of fuel, gross weight, and cruise altitude. The descent VNAV page allows selection of VNAV path data for display (if configured for VNAV). ATC Key - The [«e ) key is presently inoperative. Future software revisions will allow for ATC communication. Rev 3 8/99T1000 PILOT’S GUIDE 2.4.3.2 Special Purpose Keys The special purpose keys consist of the following: BRT/DIM Key — Pressing the (22) key alternately increases and decreases the brightness of the display. The key must be released for approximately one second before initiating another press to reverse the brightness level. Brightness level of the keyboard is controlled by a separate rheostat. CLR Key — This key clears the scratchpad and data fields. A single press clears one character and holding it down clears the entire scratchpad. If the key is pressed with nothing in the SP the word DELETE appears. Then by pressing an appropriate left or right LSK the data entered on the LSK line may be removed Slash Key — The key is included as one of the special purpose keys and is used to separate pairs of entries in the same field. For example, airspeed and Mach (280/.72), wind direction and velocity (240/75), bearing and distance (180/20), or airspeed and altitude (250/10000). The trailing entry of an entry pair must be preceded by the slash if it alone is entered PREV Key — The (f«) key moves the display backwards to the previous page (if a previous page is available), NEXT Key — The (nex) key moves the display forward to the next page (if a next page is available). MENU Key — The [e) key calls up a menu of the connected A739 subsystems. GPS/NAV or any A739 subsystem displayed may be selected. The HT1000 can be selected by pressing GPS/NAV prompt. DATA Key — The (2s) key provides access to a menu of advisory data displays. EXEC Key — The (Ee) key executes modifications to the active route. A green bar-light above the key indicates when the key is armed. 2-11 Rev3 8/99HT1000 PILOT’S GUIDE 2.4.3.3 Alpha Numeric Keys The alpha numeric keys enable the pilot to enter letters and numbers, including ©, ©, and the key. Alpha and numeric keys may be entered together as required. The Plus/Minus Key — The © key enters numeric characters into the scratchpad. The first momentary press of the @ key inserts a minus sign. A second press of the @ inserts a plus sign. The Space Key - The (s*) key is used to insert a space between characters. It is available for ATC downlink text messages in the future. 2.4.4 Page Formats and Data Labels HT1000 formats and data labels are displayed on the MCDU pages selected by the function keys. Two sizes of font (LARGE and SMALL) are used on the display pages. LARGE font indicates either primary flight data OR data entered by the pilot. Typical page format and data labels are illustrated in Figure 2-6. Rev 3 8/99 2-12HT1000 PILOT’S GUIDE RMANCE INITIALIZATION F SMALL FONT Tare ~ T N S e OFFSET --- MOD RTE 1 LE PAGE 00m ae ane | —— Nuiser ‘ee kPa naw The eer hen ea ae AUT 55.0NH ABEAM PTS> een RTE COPY> ee) Uhh Figure 2-6 MCDU Page Formats 2-13 Rev3 8/99HT1000 PILOT’S GUIDE The following are explanations for the data labels and page formats illustrated in Figure 2-6. Page Title (LARGE font) — The page title is at the top of the display. It indicates the subject or title of the page displayed on the MCDU. If aroute is displayed, ACT or MOD will be displayed to indicate that the route displayed is Active or Modified Scratchpad Line (SP) - Thisis the bottom line of the display. This line displays HT1000-generated messages, keyboard entries, and data thatis being moved from one line to another. All data entry is displayed on this line and then “line selected” to the appropriate location by pressing a LSK to the right or left of the display. Data can be entered into the SP with the alphanumeric keys, the LSK, or by the HT1000. System-generated messages are displayed in the scratchpad. Alert messages take precedence. System-generated messages appear only when pilot-entry is not in progress. When the system sends a message to the MCDU, the WHITE MSG annunciator light on the left side of the MCDU illuminates. Press the key once to remove a message from the scratchpad. If more than one message is waiting, the HT1000 displays the next new message when the key is pressed. The MSG annunciator is illuminated until all new messages have been cleared. Data entry to the scratchpad can be made while a system message is displayed. (MCDU Messages are summarized in Appendix B, MCDU Messages.) Scratchpad entries are independent of page selection and remain in view until cleared, even when page changes occur. LARGE Font — Indicates crew-entered data or crew-verified information. LARGE font may also represent certain navigational data base entries. SMALL Font — Represents predicted, default, or HT1000-calculated values. When adjacent to a LSK, the data may be changed in some instances by crew entry, which changes the SMALL font to LARGE font. SMALL font also is used on the label line to identify the data that appears on the data line. (See Label Line below.) Label Line — Identifies the data displayed on line(s) belowit. The line label is displayed in SMALL font. Rev3 8/99 2414HT1000 PILOT’S GUIDE Data Line — Contains box prompts, dashes, computer generated data (SMALL font), or crew entered data (LARGE font). Box Prompts (OO000) — Indicate that crew-entered data is required for minimum HT1000 operation. Data entry is performed by the crew entering alphanumeric data in the scratchpad and pressing the corresponding LSK. Entries into a box-prompt data line are displayed in LARGE font. Dash Prompts ( ———-— ) — Indicate that data entry is optional (Optional data is that data which is not required for the HT1000 to perform navigation tasks.) The crew may enter the optional data in the scratchpad followed by a press of the LSK adjacent to the dash prompts. Page Number — Displays that have more than one page of data include a page number, which is located in the top right corner of the display screen. The first digit indicates the page number that is currently displayed and the second digit indicates total number of related pages. For example, 1/2 identifies a page as the first in a series of two pages. This data is in SMALL font. Page or Action Prompts (< or > )— Indicates access to related page displays or actions. Waypoint — Waypoint identifiers are displayed in LARGE font. 2.4.5 Data Entry Data is entered into the scratchpad using the alphanumeric keys. As arule, the display field or data field acts as an example format that, when followed, results in successful data entry. After scratchpad entry and confirmation of correct data, pressing a LSK transfers data from the scratchpad to the data field. Data entry formats that are not obvious are explained. For specific formats, it is possible to transfer information from a data field into the scratchpad by pressing the LSK when the scratchpad is empty. The data subsequently can be transferred to another data field by an appropriate keyboard procedure, or it can be cleared from the scratchpad using the 2-15 Rev3 8/99HT1000 PILOT’S GUIDE 2.5 TERMINOLOGY The following information defines the terminology used to describe the flight crew interaction with the HT1000 MCDU. Active — Refers to route information currently being used to calculate lateral navigation guidance commands. The active waypoint is the point the system is currently navigating toward. ACT is displayed on the respective page titles. Activate — Designating one of two routes as active. It is a two-step ‘ocess. First, press the ACTIVATE> LSk, then press the illuminated (exc) key. Enter — Entering data into the system by typing or line-selecting alphanumeric characters into the MCDU scratchpad and then line- selecting the information to the desired location. Erase — Removes a modified flight path from the system by pressing the line-select key adjacent to the word ERASE. The prompt is present in anytime MOD Route is in progress. Execute — Refers to making pilot-entered information part of the active route by pressing the illuminated (= Inactive — Refers to route information currently not being used to calculate navigation commands. Initialize — Entering required information into the MCDU to make the HT1000 operative. Message — Refers to information that the HT1000 automatically writes in the scratchpad to inform the flight crew of conditions. Modify — Modification of data in the active route. When a modification is made to the active route, MOD is displayed in the page title, ERASE appears next to , and the (sec) key illuminates. Pressing the ERASE LSK removes the modification. Pushing the (sec) key makes the modified route active. Rev3 8/99 2-16HT1000 PILOT’S GUIDE Prompt —A symbol displayed on the MCDU page to prompt the crew for information. It may be boxes ((][J[JOI[) or dashes (----—). A boxed prompt indicates a required entry. A dashed prompt is an optional entry. Select — Pressing a key to obtain the desired information or action. Waypoint—A pointin the route. It may bea fixed point, suchas latitude and longitude, a VOR or NDB station, or an intersection on an airway. 217 Rev3 8/99Bes FLIGHT OPERATIONS 3), FLIGHT OPERATIONS 00.0: .egteerausaeminuanneccn Ss 3.1 3.2 3:3 TABLE OF CONTENTS o 0 io a © PREFLIGET secstiernrssseces 3.1.1 Identification Page... 3.1.1.1 Position Reference Page 3.1.1.2 POS REF Page 2/2... 3.1.1.3 POS REF INFO Page 3.1.2 Inertial Systems Interface .... 3.1.2.1 POS INIT Page 3.1.3 Flight Planning 3.1.3.1 Route Page 1 . 3.1.3.2 Route Page 2... : 3.1.3.3 Departure Selection Performance Initialization Route Legs ......... 3.1.5.1 Flight Plan Route Activation .. Route Data Page 2 Wind Input ........... Automatic Flight Plan Transfer SUAS So COND ob SwKOooOOHHSSAA VSdA5 G55 00nN POW ww 4 1 A TAKEOFF/CLIMB... 3.2.1 Direct-To ... 3.2.2 Intercept Course . LOW POWWWOOWWHHW WHOWWL ivy oh CRUISE 3.3.1 Route Modific 3.3.1.1 Erasing an n ACT RTE ‘Leg 3.3.1.2 Route Discontinuity ......... 3.3.1.3 Select Desired Waypoint Pag 3.3.1.4 Pilot-Defined Waypoints .. 3.3.1.5 ABEAM PTS> and RTE COPY> Prompts .. 3.3.1.6 OFFSET .. 3.3.2 ACTIVE RTE LEGS Pages 3.3.2.1 RTE DATA (2 69 9 69. Oo Reso hones ww ww 34 Rev3 8/99T1000 PILOT’S GUIDE 3.3-21 3.3-21 3.3-23, 3.3-25 3.3-26 3.3-26 3.3-30 3.3-31 3.3.3 PROGRESS Pages ....... 3.3.3.1 Progress Page 1/2 3.3.3.2 Progress Page 2/2 3.3.4 Position Report ... 3.3.5 Holding Patterns ... 3.3.5.1 ACT RTE 1-—HOLD Page. 3.3.5.2 Holding Pattern Guidance . 3.3.5.3 MOD HOLD PENDING .. 3.4 DESCENT. 3.41 Descent Path Construction 3.4.1.1 Deceleration Segment 3.4.1.2 Descent Path Construction 3.4.3 3.4.2 Display of VNAV Data (Summary) .........-..-. 3.4-4 3.4.3 ACT RTE LEGS Page (VNAV Information). 3.4-6 3.4.4 PROGRESS Page (VNAV Information) . 3.4.5 DESCENT Page 3.4.6 VINAV Messages 3.4.7 Scenarios 3.5 ARRIVAL/APPROACH 3.5.1 Arrival Selection 3.5.2 Approach Terminology Used In This Guide 3.5-5 3.5.3 Non-Precision Approaches (Lateral Guidance Only).. 3.5.3.1 Selecting a Non-Precision Approach .... wistes BOLO 3.5.32 Course Deviation Indications... 3.5-7 3.5-7 5-7 3.5.3.3 Flight Director Indications .. e 3.5.3.4 Indications on the LEGS Page...... 3. 3.5.3.5 Approach Scratchpad Annunciations .. Sie 3.5.4 Example Non-| Preci ion ‘Approach (Lateral Guidance Only)... 3.5.4.1. En Route and Terminal Area 3.5.4.2 Transition to the Approach from a Procedure Turn . 3.5.4.3 Aircraft Inbound to the Approach Course......... 3.5.4.4 Final Approach Fix Inbound . 3.5.4.5 Missed Approach .. 3.5.5 SCAT 1 Precision ‘Approaches \ 3.5.5.1 Differential GPS System Overview ........... in Rev3 8/99 341HT1000 PILOT’S GUIDE 3.5.6 3.5.7 3.5.5.2 DGPS Airborne Equipment... 3.5.5.2.1 Navigation Select PAG essence S18: 3.5.5.2.2 GPS Status Annunciators 3.5-19 SCAT 1 Example Approach ..... 3.5.6.1 Aircraft Outside Terminal Area 3.5.6.2 Aircraft in Terminal Area ...... 3.5.6.3. Final Approach Fix Inbound... . 3.5-24 Accuracy and Integrity Requirements 3.5.7.1 RAIM at Destination ........... 316 MISCELLANEOUS tscuscrecrvruem erence 3.6.1 3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.6.7 3.6.8 3.6.9 3.6.10 3.6.11 3.6.12 REF NAV Data FIX INFO .... 3.6.2.1 Fix Info Page ACTIVE PLAN PREDICTION .. 3.6.3.1 Required Navigation Performance (RNP)... 3.6.3.2 Active Route Integrity Prediction .. Data Index and Nearest Pages... Dead Reckoning and HDG/TAS OVERRIDE .. - 3.6-11 NAV Database ( ) Crossload . Transfer of USER DATABASES SV Data Page .. Message Recall USSG ROUTES icscovscsseasarvcrmemesracvecs 3.6-26 3.6.10.1 Create and Save User Routes ..... 3.6-27 3.6.10.2 Search the Data base for a User Route.......... 3.6.10.3 Load a User Route 3.6.10.4 Delete User Routes ......... User Waypoints Storage and Retrieval 3.6.11.1 User Waypoint Retrieval .. 3.6.11.2 Delete User Waypoint .. HT1000 Page Tree 5 Siii Rev3 8/99ection 3 This section describes the HT1000 operations used on a typical flight, in this case, a flight from Dallas-Fort Worth to Cancun (that is, KDFW to MMUN). It begins with system initialization prior to takeoff at Dallas- Fort Worth and continues to engine shutdown at the destination, Cancun. Not all system functions are described; however, those frequently used as part of the normal operations are covered. Table 3-1 FLIGHT DATA - DALLAS TO CANCUN Flight Number HT1649 Departure Airport Dallas-Fort Worth International Destination Airport Cancun International Alternate Airport Cozumel International B727 Aircraft Cruise Level FL330. Route as filed: KDFW RO455F330 JPOOL2 BILEE TNV J87IAH SBI A766 FIR38 UA766 EDGAR MMUNO206 Rev3 8/99HT1000PILOT’S GUIDE Symbols commonly used throughout this guide to illustrate the HT1000 functions include: SP Abbreviation for Scratchpad [U& (==) Press MCDU function or character key. TS Press MCDU line-select key. Also, review the special purpose keys in Section 2.4.3.2 and data entry in 2.4.5. NOTES and CAUTIONS for this guide use the following standard definitions: NOTE: Calls attention to methods that make the task easier or to pertinent information for the flight crew. Rev3 8/99 32ATI TOUU PILOT’S GUIDE TIME 0:00) 0:16 0:20 0:29 0:30 0.33 0.43 0:47 0:57 0:58 1:07 1:31 214 MAVERICK D FTWORTH (113.1 Tr | Naz 52.0 wo97 01.7 Hiwas 5 HUMBLE (Hy 116.6 ian | | NAVASOTA [2 15.9 NV N30 17.3 Wo9s 03.5 SABINE PASS le 115.4 SBI N29 41.2 woo 02.3 CANCUN D NULEY 113.4 CUN N21 01.5 W086 51.8 87 — 109 — 164 206 — 276 — 303 383 9394 — 463 —} 659 = 660 — 699 827 828 ll — 929 Use ‘0F disclosure ofthe information on this page is subject tothe restrictions on the tile page of this documant G3653-04-075# (WN) SONVISIC Flight Plan, Dallas - Cancun 3-3/4 Rev 3 8/99TABLE OF CONTENTS 3.1 PREFLIGHT. 3.1.1 Identification Page . 3.1.1.1 Position R Page 3.1.1.2 POS REF Page 2/2 .... 3.1.1.3 POS REF INFO Page... 3.1.2 Inertial Systems Interface 3.1.2.1 POS INIT Page . 3.1.3. Flight Planning ......... 3.1.3.1 Route Page 1 3.1.3.2 Route Page 2 3.1.3.3 Departure Selection 4 Performance Initialization .... 5 Route Legs .... 3.1.5.1 Flight Plan Route ‘Activation 3.1-31 .6 Route Data Page zs ie 8 Wind Input.. ie Automatic Flight Plan Transfer ..........00.:0:+ 3.1-37 3.14 Rev3 8/99HT1000 PILOT’S GUIDE 3.1 PREFLIGHT During preflight the pilot verifies the HT1000 status, initializes the system, enters or modifies the route, and configures the HT1000 for flight. 3.1.1 Identification Page When aircraft power is supplied, the HT1000 is powered up. It does not have a power on/off switch. The first screen the HT1000 displays is the IDENT page. The IDENT page allows the pilot to review the aircraft type, engine type, and navigational database. All data on the aircraft IDENT page should be reviewed for accuracy and applicability. The only data that can be changed on the IDENT page is the active navigational database. Any MCDU message can be cleared from the scratchpad using the (cs) key. (MCDU message explanations are in Appendix A.) CO — Beer UL TeLT\ BRED ee. — (in) OT Re TT 728-007. Figure 3.1-1 IDENT Page Explanations of the LSKs and the adjacent data in Figure 3.1-1 begin on the next page. 34-1 Rev 3 8/99HT1000 PILOT’S GUIDE (GL) MODEL- Displays the aircraft model stored in the configuration module. NAV DATA- Displays the identifier of the navigational database stored in the NPU. The first two digits of the database part number designate the airline or generic HT. The third digit designates the airline’s database number. The fourth and fifth digits designate the year the database was produced. The sixth and seventh digits designate the database cycle number. There are 13 database cycles in one year, so sometimes the database cycle number coincides with the month itis effective, and sometimes it does not. The eighth, ninth, and tenth digits designate the sequence number. The sequence number will display the number of revisions incurred within a database cycle. NOTE: TheNAV database identifier willbe displayed in yellow if the NAV database is corrupted or not yet validated. If it is corrupted, a NAV DATACORRUPT messagewillbe displayed in the SP. If this occurs on the ground, the NAV databases should be reloaded or the alternate database should be selected. If the failure occurs in flight, the current active route remains good, however, any attempt to use data from that database will result in the error message NOT IN DATABASE being displayed in the scratchpad. However, LAT/LON waypoints may still be created. After the navigation database has been loaded, it is normal for the NAV database identifier to be displayed in yellow while the validity checks are being run. Once the validity checks are complete and no problems are found, the navigation database identifier will turn white. SOFTWARE - Displays the operating program’s identifier part number. This is the operating system of the HT1000. Rev 3 8/99 3.1-2HT1000 PILOT’S GUIDE GR) ENGINES - Displays the engine model number contained in the configuration module (2R) ACTIVE - Displays the active navigational database effective dates in the HT1000. The INACTIVE navigational database effective dates are displayed next to LSK (SR) To change the ACTIVE database, carry out steps A and B. STEPS: A. [> GR) to copy the inactive database identifier to the scratchpad (see Figure 3.1-2). B. oS to make the INACTIVE database ACTIVE. The HT1000 moves the new date up to (2R) (see Figure 3.1-3). a ee PEN JT8D-9A fanaa) HT79964001 22APR2OMAY/99 Beats) RAE Se eee eee — RD HT1006-0060 PLES UA ees Figure 3.1-2 Change Active Database 3.1-3 Rev 3 8/99HT1000 PILOT’S GUIDE Pie PN NRE — (CR) ee) Ey Bee te ee a PARC Sees v2 Cee — OR) ee ey) Figure 3.1-3 New Active Navigation Database NOTES: 1. The ACTIVE navigation database can be changed only while the aircraft is on the ground 2. Changing the ACTIVE navigation database erases any flight plan information previously entered. 3. Following the prompts at LSK (A) will guide the pilot through the preflight initialization entries (6R) POS REF - Pressing the LSK (6R) provides access to the POS REF page. 3.1.1.1 Position Reference Page Pressing (6R) on the IDENT page or (2L) on the data index page provides access to the Position Reference (POS REF) page. The POS REF page displays present position, time, ground speed, RNP, and actual navigation performance. Rev3 8/99 3.14HT1000 PILOT’S GUIDE aD @ ay STEP: Lp (6A) from the IDENT page EERO. eye be ae) ei) 1125.32 ral 1.60/0.08 Figure 3.1-4 POS REF Page POS (GPS) — Displays the present HT1000-calculated position and source of position. Position source is identified by either (GPS), (DR), (DME), or (INS) on the display. UTC (GPS) - Universal Coordinated Time. UTC time is provided by the GPS signal. In the event GPS is lost, time will be replaced with the HT1000's own internal clock. RTC (Real Time Clock) will then be displayed adjacent to UTC time. When the system again acquires a GPS signal, the UTC time will be updated RNP/ACTUAL — Displays Required Navigation Performance (RNP) and Actual Navigation Performance values. The displayed RNP value is based on the aircraft's phase-of- flight. For oceanic/remote operations the RNP default is 12 NM. For en route operations the default RNP is 2.0 NM. For terminal operations itis 1.0 NM, and for approach operations the default RNP is 0.3 NM. The RNP value will automatically default to these values as the aircraft flies through the different phases of flight. These default values can be overridden by the pilot by typing in a value and Line-selecting the value to (3L). However, this will prevent the system from automatically defaulting to the 3.1-5 Rev3 8/99HT1000 PILOT’S GUIDE next phase-of-flight RNP. To return to the automatic default logic, press the key and line-select DELETE to (3L) The Actual navigation performance number is a measure of the navigation accuracy of the system. It computes the actual navigation performance number based on the Known satellite geometry and the known inherent system errors (such as receiver noise, multi-path and atmospheric effects). Ifthe ANP value exceeds the RNP value, the system will generate an UNABLE RNP message or annunciation. — SV data is displayed if no other sensors are configured. If the system is configured to use DME or INS, SV data is not displayed on this page, but it can be accessed on page 3/3. When the SV DATA> prompt is present, pressing will display a page of satellite data (azimuth, elevation, and signal quality.) DEST RAIM> - Accesses the Destination RAIM Prediction page. The Destination RAIM Prediction requires an active route and can be run in the air or on the ground. ROUTE> — Displays the RTE page, which is used to continue the preflight initialization sequence. Rev3 8/99 3.1-6HT1000 PILOT’S GUIDE 3.1.1.2 POS REF Page 2/2 (Available If DME or INS Is Installed) NOTICE The following pages 3.1-7 to 3.1-17 are for use only with GPS aircraft that have Inertial Systems installed, and in which the HT1000 is configured to interface with the INS system. If you do not have Inertial equipment installed, continue to page 3.1-18 (Section 3.1.3, Flight Planning). The POS REF page displays the different navigation solutions that have been calculated, and provides a means to access supplemental navigation data for each of the solutions. Figures 3.1-5, 3.1-6, and 3.1- 7 show examples of POS REF pages when either DME or INS equipment is installed. cy N33°26.25 W112°00.5 eee N33°26.2 N112°00.5 ey N33°26.2 W112°00.5 Figure 3.1-5 Sample POS REF Page DME-Equipped Aircraft in LAT/LON Pressing BRG/DIST> displays GPS at (2L) and DME at (GL) as a bearing distance from the position in line 1. (See Figure 3.1-6.) The HT1000-calculated position at (IL) will always be displayed in LAT/ LON 341-7 Rev 3 8/99