ddtk.pdf

HighlightsPage 1 of 2

November 2013Honeywell International Inc. Do not copy without express permission of Honeywell.

Honeywell International Inc.21111 N. 19th Ave.Phoenix, Arizona 85027-2708U.S.A.CAGE: 55939Telephone: 1--800--601--3099 (U.S.A.)Telephone: 1--602--365--3099 (International)Web site: https://myaerospace.honeywell.com

TO: HOLDERS OF THE FMZ SERIESFLIGHT MANAGEMENT SYSTEM (FMS) FOR THECESSNA CITATION X TOLD PILOT’S GUIDE, HONEYWELLPUB. NO. D201110000041

REVISION NO. 3 DATED NOVEMBER 2013

HIGHLIGHTS

Pages that have been revised are outlined below. Remove and insertthe affected pages listed. The revision number has been added to thebottom of the revised pages and revision bars have been used toindicate the revised or added text. Insert this highlights letter in themanual in your possession ahead of page T-1, Title Page. The List ofEffective Pages shows the order in which to insert the attached newpages into your guide.

Page No. Description of Change

T--1 Updated to reflect Revision 3.

RR--1 Updated to reflect Revision 3.

LEP--1, LEP--2 Updated to reflect Revision 3.

TC--1, TC--2,TC--6

Added Technical Operations Center (TOC) entryand text shifted to next page; added Appendix Asection and table title.

1--1 Added section and revision entries for newlyadded Appendix A.

1--3, 1--4 Added Technical Operations Center informationand text shifted to next page.

2--9 Modified last paragraph.

A--1 thru A--12 Added new appendix and Table A--1 listingapplicable PARs.

HighlightsPage 2 of 2

November 2013Honeywell International Inc. Do not copy without express permission of Honeywell.

Page No. Description of Change

Abbrev--1 thruAbbrev--4

Updated to reflect Revision 3.

Index--1 thruIndex--4

Updated to reflect Revision 3.

Printed in U.S.A. Pub. No. D201110000041--003 March 2012Revised November 2013

Page T--1Honeywell International Inc. Do not copy without express permission of Honeywell.

Honeywell International Inc.21111 N. 19th Ave.Phoenix, Arizona 85027-2708U.S.A.CAGE: 55939

Telephone: 1--800--601--3099 (U.S.A.)Telephone: 1--602--365--3099 (International)Web site: https://myaerospace.honeywell.com

FMZSeriesFlightManagementSystem

(FMS)

for theCessna Citation X TOLDSoftware Version NZ 6.1

Pilot’s Guide

FMZ Series Flight Management System (FMS) for the Cessna Citation X TOLD

D201110000041REV 1 Jun 2013Page T--2

Honeywell International Inc. Do not copy without express permission of Honeywell.

Honeywell--ConfidentialTHIS COPYRIGHTED WORK AND ALL INFORMATION ARETHE PROPERTY OF HONEYWELL INTERNATIONAL INC.,CONTAIN TRADE SECRETS AND MAY NOT, IN WHOLE ORIN PART, BE USED, DUPLICATED, OR DISCLOSED FORANY PURPOSE WITHOUT PRIOR WRITTEN PERMISSIONOF HONEYWELL INTERNATIONAL INC. ALL RIGHTSRESERVED.

Honeywell Materials License Agreement

The documents and information contained herein (“theMaterials”) are the proprietary data of HoneywellInternational Inc. and Honeywell Intellectual Properties Inc(collectively “Honeywell”). These Materials are providedfor the exclusive use of Honeywell Service Centers;Honeywell--authorized repair facilities; operators ofHoneywell aerospace products subject to an applicableproduct support agreement, their whollyowned--subsidiaries or a formally designated third partyservice provider; and direct recipients of Materials fromHoneywell’s Aerospace Technical Publication Distribution.The terms and conditions of this License Agreementgovern your use of these Materials, except to the extentthat any terms and conditions of another applicableagreement with Honeywell regarding the operation,maintenance, or repair of Honeywell aerospace productsconflict with the terms and conditions of this LicenseAgreement, in which case the terms and conditions of theother agreement will govern. However, this LicenseAgreement will govern in the event of a conflict betweenits terms and conditions and those of a purchase order oracknowledgement.

1. License Grant -- If you are a party to an applicable product supportagreement, a Honeywell Service Center agreement, or an authorizedrepair facility agreement, Honeywell hereby grants you a limited,non--exclusive license to use these Materials to operate, maintain, orrepair Honeywell aerospace products only in accordance with thatagreement.

If you are a direct recipient of these Materials from Honeywell’sAerospace Technical Publication Distribution and are not a party to anagreement related to the operation, maintenance or repair ofHoneywell aerospace products, Honeywell hereby grants you a limited,


D201110000041REV 1 Jun 2013 Page T--3


non--exclusive license to use these Materials to maintain or repair thesubject Honeywell aerospace products only at the facility to whichthese Materials have been shipped (“the Licensed Facility”). Transferof the Materials to another facility owned by you is permitted only if theoriginal Licensed Facility retains no copies of the Materials and youprovide prior written notice to Honeywell.

2. Rights In Materials -- Honeywell retains all rights in these Materialsand in any copies thereof that are not expressly granted to you,including all rights in patents, copyrights, trademarks, and tradesecrets. No license to use any Honeywell trademarks or patents isgranted under this License Agreement.

3. Confidentiality -- You acknowledge that these Materials containinformation that is confidential and proprietary to Honeywell. You agreeto take all reasonable efforts to maintain the confidentiality of theseMaterials.

4. Assignment And Transfer -- This License Agreement may beassigned to a formally designated service designee or transferred to asubsequent owner or operator of an aircraft containing the subjectHoneywell aerospace products. However, the recipient of any suchassignment or transfer must assume all of your obligations under thisLicense Agreement. No assignment or transfer shall relieve any partyof any obligation that such party then has hereunder.

5. Copies of Materials -- Unless you have the express writtenpermission of Honeywell, you may not make or permit making ofcopies of the Materials. Notwithstanding the foregoing, you may makecopies of only portions of the Material for your internal use. You agreeto return the Materials and any copies thereof to Honeywell upon therequest of Honeywell.

6. Term -- This License Agreement is effective until terminated as setforth herein. This License Agreement will terminate immediately,without notice from Honeywell, if you fail to comply with any provisionof this License Agreement or will terminate simultaneously with thetermination or expiration of your applicable product support agreement,authorized repair facility agreement, or your formal designation as athird party service provider. Upon termination of this LicenseAgreement, you will return these Materials to Honeywell withoutretaining any copies and will have one of your authorized officerscertify that all Materials have been returned with no copies retained.

7. Remedies -- Honeywell reserves the right to pursue all availableremedies and damages resulting from a breach of this LicenseAgreement.


D201110000041REV 1 Jun 2013Page T--4


8. Limitation of Liability -- Honeywell does not make anyrepresentation regarding the use or sufficiency of the Materials.THERE ARE NO OTHER WARRANTIES, WHETHER WRITTEN ORORAL, EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOTLIMITED TO, (i) WARRANTIES ARISING FROM COURSE OFPERFORMANCE, DEALING, USAGE, OR TRADE, WHICH AREHEREBY EXPRESSLY DISCLAIMED, OR (ii) WARRANTIESAGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTSOF THIRD PARTIES, EVEN IF HONEYWELL HAS BEEN ADVISEDOF ANY SUCH INFRINGEMENT. IN NO EVENT WILL HONEYWELLBE LIABLE FOR ANY INCIDENTAL DAMAGES, CONSEQUENTIALDAMAGES, SPECIAL DAMAGES, INDIRECT DAMAGES, LOSS OFPROFITS, LOSS OF REVENUES, OR LOSS OF USE, EVEN IFINFORMED OF THE POSSIBILITY OF SUCH DAMAGES. TO THEEXTENT PERMITTED BY APPLICABLE LAW, THESE LIMITATIONSAND EXCLUSIONS WILL APPLY REGARDLESS OF WHETHERLIABILITY ARISES FROM BREACH OF CONTRACT, WARRANTY,TORT (INCLUDING BUT NOT LIMITED TO NEGLIGENCE), BYOPERATION OF LAW, OR OTHERWISE.

9. Controlling Law -- This License shall be governed and construed inaccordance with the laws of the State of New York without regard tothe conflicts of laws provisions thereof. This license sets forth the entireagreement between you and Honeywell and may only be modified by awriting duly executed by the duly authorized representatives of theparties.

Copyright -- Notice

Copyright 2012, 2013, Honeywell International Inc. All rights reserved.

Honeywell and SPEX are registered trademarks of HoneywellInternational Inc.

All other marks are owned by their respective companies.


D201110000041REV 3 Nov 2013 RR--1

Record of Revisions


Record of Revisions

For each revision, put the changed pages in your guide and discard thereplaced pages. Write the revision number and date, and the date putin the guide. Put your initials in the applicable columns on the Recordof Revisions. The initial H shows that Honeywell put the changedpagesin the guide.

RevisionNumber

RevisionDate

InsertionDate By

1 Jun 2013 Jun 2013 H

2 Sep 2013 Sep 2013 H

3 Nov 2013 Nov 2013 H


D201110000041REV 1 Jun 2013

Record of RevisionsRR--2


Blank Page


D201110000041REV 3 Nov 2013 LEP--1

List of Effective Pages



Subheading and Page Date Subheading and Page Date

Title

T--1 H Nov 2013

T--2 Jun 2013

T--3 Jun 2013

T--4 Jun 2013

Record of Revisions

RR--1 H Nov 2013

RR--2 Jun 2013


LEP--1 H Nov 2013

LEP--2 H Nov 2013

Table of Contents

TC--1 H Nov 2013

TC--2 H Nov 2013

TC--3 Jun 2013

TC--4 Jun 2013

TC--5 Jun 2013

TC--6 H Nov 2013

TC--7 Jun 2013

TC--8 Jun 2013

Introduction

1--1 H Nov 2013

1--2 Jun 2013

1--3 H Nov 2013

1--4 H Nov 2013

Operational Example

2--1 Jun 2013

2--2 Jun 2013

2--3 Jun 2013

2--4 Jun 2013

2--5 Jun 2013

2--6 Jun 2013

2--7 Jun 2013

2--8 Jun 2013

2--9 H Nov 2013

2--10 Jun 2013

2--11 Jun 2013

2--12 Jun 2013

2--13 Jun 2013

2--14 Jun 2013

2--15 Jun 2013

2--16 Jun 2013

2--17 Jun 2013

2--18 Jun 2013

2--19 Jun 2013

2--20 Jun 2013

2--21 Jun 2013

2--22 Jun 2013

2--23 Jun 2013

2--24 Jun 2013

2--25 Jun 2013

2--26 Jun 2013

2--27 Jun 2013

2--28 Jun 2013

2--29 Jun 2013

2--30 Jun 2013

2--31 Jun 2013

2--32 Jun 2013

2--33 Jun 2013

2--34 Jun 2013

2--35 Jun 2013

2--36 Jun 2013

2--37 Jun 2013

2--38 Jun 2013

2--39 Jun 2013

2--40 Jun 2013

2--41 Jun 2013

2--42 Jun 2013

2--43 Jun 2013

2--44 Jun 2013

2--45 Jun 2013

2--46 Jun 2013

2--47 Jun 2013

2--48 Jun 2013

2--49 Jun 2013

2--50 Jun 2013

2--51 Jun 2013

H indicates a changed page.F indicates a foldout page.


D201110000041REV 3 Nov 2013

List of Effective PagesLEP--2


Subheading and Page Date Subheading and Page Date

Operational Example (cont)

2--52 Jun 2013

Performance

3--1 Jun 2013

3--2 Jun 2013

3--3 Jun 2013

3--4 Jun 2013

3--5 Jun 2013

3--6 Jun 2013

F 3--7/3--8 Jun 2013

3--9 Jun 2013

3--10 Jun 2013

3--11 Jun 2013

3--12 Jun 2013

3--13 Jun 2013

3--14 Jun 2013

3--15 Jun 2013

3--16 Jun 2013

3--17 Jun 2013

3--18 Jun 2013

3--19 Jun 2013

3--20 Jun 2013

3--21 Jun 2013

3--22 Jun 2013

3--23 Jun 2013

3--24 Jun 2013

3--25 Jun 2013

3--26 Jun 2013

3--27 Jun 2013

3--28 Jun 2013

3--29 Sep 2013

3--30 Sep 2013

3--31 Sep 2013

3--32 Sep 2013

3--33 Sep 2013

3--34 Jun 2013

Control Display Unit (CDU)Entry Format

4--1 Jun 2013

4--2 Jun 2013

Messages

5--1 Jun 2013

5--2 Jun 2013

5--3 Jun 2013

5--4 Jun 2013

Appendix A -- Applicable Program/ProductAction Requests (PARs)

A--1 H Nov 2013

A--2 H Nov 2013

A--3 H Nov 2013

A--4 H Nov 2013

A--5 H Nov 2013

A--6 H Nov 2013

A--7 H Nov 2013

A--8 H Nov 2013

A--9 H Nov 2013

A--10 H Nov 2013

A--11 H Nov 2013

A--12 H Nov 2013

Acronyms and Abbreviations

Abbrev--1 H Nov 2013




Index

Index--1 H Nov 2013

Index--2 H Nov 2013

Index--3 H Nov 2013

Index--4 H Nov 2013

H indicates a changed page.F indicates a foldout page.


D201110000041REV 3 Nov 2013 TC--1

Table of Contents


Table of Contents

Section Page

1. INTRODUCTION 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Honeywell Product Support 1-2. . . . . . . . . . . . . . . . . . . .Customer Support 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Global Customer Care (GCC) 1-3. . . . . . . . . . . . . . .Technical Operations Center (TOC) 1-3. . . . . . . . . .To Register Your Publication (if Required) 1-4. . . . .Honeywell Aerospace TechnicalPublications 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. OPERATIONAL EXAMPLE 2-1. . . . . . . . . . . . . . . . . . .

Introduction 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Pre--Departure 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Power--Up 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Position Initialization 2-7. . . . . . . . . . . . . . . . . . . . . . . . . .Active Flight Plan 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Waypoint Entry 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . .Airway Entry 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Performance Initialization 2-17. . . . . . . . . . . . . . . . . . . . . .Performance Data 2-22. . . . . . . . . . . . . . . . . . . . . . . . . . . .Departure Selection 2-25. . . . . . . . . . . . . . . . . . . . . . . . . .

Flight Plan Discontinuities 2-27. . . . . . . . . . . . . . . . . .Takeoff Initialization 2-28. . . . . . . . . . . . . . . . . . . . . . . . . . .Takeoff Data 2-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Runway Position 2-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Takeoff 2-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Climb 2-39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .En Route 2-40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descent 2-41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Arrival 2-41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Approach 2-45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Landing Initialization 2-45. . . . . . . . . . . . . . . . . . . . . . . . . .Landing Data 2-49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Missed Approach 2-50. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alternate Flight Plan 2-51. . . . . . . . . . . . . . . . . . . . . . . . . .Clearing of Flight Plans 2-52. . . . . . . . . . . . . . . . . . . . . . .

3. PERFORMANCE 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Performance Index 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . .

Performance Index Organization 3-4. . . . . . . . . . . .


D201110000041REV 3 Nov 2013

Table of ContentsTC--2


Table of Contents (cont)

Section Page

3. PERFORMANCE (CONT)

Performance Initialization 3-5. . . . . . . . . . . . . . . . . . . . . .Citation X Performance Initialization 3-5. . . . . . . . . .

TOLD Configuration 3-9. . . . . . . . . . . . . . . . . . . . . . . . . .Takeoff Initialization 3-9. . . . . . . . . . . . . . . . . . . . . . . . . . .

Takeoff Data 3-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Landing Initialization 3-16. . . . . . . . . . . . . . . . . . . . . . . . . .Landing Data 3-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Problems Page 3-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Field Loadable TOLD Aircraft DatabaseUpdating 3-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4. CONTROL DISPLAY UNIT (CDU) ENTRYFORMAT 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .List of Entries and Definition 4-1. . . . . . . . . . . . . . . . . . .

5. MESSAGES 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Message List and Definition 5-1. . . . . . . . . . . . . . . . . . .

A CITATION X FMS 6.1 APPLICABLE PROGRAM/PRODUCT ACTION REQUESTS (PARS) A--1. . . . .

Introduction A--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACRONYMS AND ABBREVIATIONS Abbrev--1. . . . . . . . . . . . . . .

INDEX Index--1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


D201110000041REV 1 Jun 2013 TC--3

Table of Contents



List of FiguresFigure Page

2--1 KPHX to KMSP Route of Flight 2-1. . . . . . . . . . . . . . . .2--2 Phoenix, AZ EAGUL3 Departure 2-2. . . . . . . . . . . . . . .2--3 Minneapolis, MN KASPR2 Arrival 2-3. . . . . . . . . . . . . .2--4 Minneapolis, MN ILS 30L Approach 2-4. . . . . . . . . . . . .2--5 FMS Preflight Procedure Flow Chart 2-5. . . . . . . . . . . .2--6 NAV IDENT 1/1 After Power--Up 2-6. . . . . . . . . . . . . . .2--7 POSITION INIT 1/1 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . .2--8 POSITION INIT 1/1 -- Reference Waypoint

Loaded 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--9 ACTIVE FLT PLAN 1/1 -- KPHX Loaded as

Origin 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--10 ACTIVE FLT PLAN 1/2 -- KMSP Loaded as

Destination 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--11 Waypoint Entry on ACTIVE FLT PLAN Pages 2-10. . . .2--12 Airway Entry on ACTIVE FLT PLAN Pages 2-10. . . . . .2--13 Waypoint Retrieval for Airway Entry on

ACTIVE FLT PLAN 1/4 2-11. . . . . . . . . . . . . . . . . . . . . .2--14 Waypoint Retrieval for Airway Entry on

ACTIVE FLT PLAN 2/4 2-11. . . . . . . . . . . . . . . . . . . . . .2--15 Waypoint Retrieval for Airway Entry on

ACTIVE FLT PLAN 3/4 2-12. . . . . . . . . . . . . . . . . . . . . .2--16 DVV Entered on the ACTIVE FLT PLAN 2-12. . . . . . . . .2--17 J114 Entered on the ACTIVE FLT PLAN 2-13. . . . . . . . .2--18 ONL Entered on the ACTIVE FLT PLAN 2-13. . . . . . . . .2--19 MCW Entered on the ACTIVE FLT PLAN 2-13. . . . . . . .2--20 Destination (KMSP) Moved to the Scratchpad 2-14. . . .2--21 Destination (KMSP) Entered as Last Waypoint

in Flight Plan 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--22 ALTERNATE FPL 2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . .2--23 KDLH Entered on the ALTERNATE FPL Page 2-15. . .2--24 Routing for Alternate Flight Plan Entered 2-16. . . . . . . .2--25 PERFORMANCE INIT 1/5 2-18. . . . . . . . . . . . . . . . . . . . .2--26 PERFORMANCE INIT 2/5 2-19. . . . . . . . . . . . . . . . . . . . .2--27 CRUISE MODES 1/1 2-20. . . . . . . . . . . . . . . . . . . . . . . . .2--28 PERFORMANCE INIT--LB 3/5 2-20. . . . . . . . . . . . . . . . .2--29 PERFORMANCE INIT 4/5 2-21. . . . . . . . . . . . . . . . . . . . .2--30 CONFIRM INIT Prompt on PERFORMANCE

INIT--LB 5/5 2-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--31 PERF DATA 1/4 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--32 PERF DATA 2/4 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--33 PERF DATA 3/4 2-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


D201110000041REV 1 Jun 2013




List of Figures (cont)

Figure Page

2--34 PERF DATA 4/4 2-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--35 DEPARTURE RUNWAYS 1/1 2-25. . . . . . . . . . . . . . . . . .2--36 SIDs 1/2 2-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--37 DEPARTURE TRANS 1/1 2-26. . . . . . . . . . . . . . . . . . . . .2--38 PROCEDURE 1/1 2-27. . . . . . . . . . . . . . . . . . . . . . . . . . . .2--39 TAKEOFF Prompt on the ACTIVE FLT PLAN

Page 2-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--40 TAKEOFF INIT 1/4 2-28. . . . . . . . . . . . . . . . . . . . . . . . . . .2--41 TAKEOFF INIT 2/4 2-29. . . . . . . . . . . . . . . . . . . . . . . . . . .2--42 TAKEOFF INIT 3/4 2-30. . . . . . . . . . . . . . . . . . . . . . . . . . .2--43 TAKEOFF INIT 4/4 2-31. . . . . . . . . . . . . . . . . . . . . . . . . . .2--44 TAKEOFF DATA 1/2 2-32. . . . . . . . . . . . . . . . . . . . . . . . . .2--45 TAKEOFF DATA 2/2 2-33. . . . . . . . . . . . . . . . . . . . . . . . . .2--46 RW POS Prompt on the ACTIVE FLT PLAN

Page 2-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--47 Runway Coordinates on the POSITION INIT

1/1 Page 2-35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--48 POSITION INIT 1/1 -- Runway 08R Threshold

Coordinates Loaded 2-35. . . . . . . . . . . . . . . . . . . . . . . . .2--49 ETAs Displayed on the ACTIVE FLT PLAN

Page 2-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--50 Waypoint Sequencing 2-37. . . . . . . . . . . . . . . . . . . . . . . . .2--51 Typical PROGRESS 1/3 Page 2-37. . . . . . . . . . . . . . . . .2--52 Typical PROGRESS 2/3 2-38. . . . . . . . . . . . . . . . . . . . . .2--53 Altitude Constraint Entered at ZUN VOR

(18,000 Feet) 2-39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--54 Cruise Speed and Altitude Information on the

PROGRESS 2/3 Page 2-40. . . . . . . . . . . . . . . . . . . . . . .2--55 ARRIVAL Prompt on the ACTIVE FLT PLAN

Page 2-41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--56 ARRIVAL 1/1 2-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--57 KMSP APPROACH 1/1 2-42. . . . . . . . . . . . . . . . . . . . . . .2--58 KMSP APPROACH TRANS 1/1 2-43. . . . . . . . . . . . . . . .2--59 KMSP STAR 1/1 2-43. . . . . . . . . . . . . . . . . . . . . . . . . . . . .2--60 KMSP STAR TRANS 1/1 2-44. . . . . . . . . . . . . . . . . . . . . .2--61 Typical ARRIVAL 1/1 Page 2-44. . . . . . . . . . . . . . . . . . . .2--62 LANDING INIT 1/3 2-45. . . . . . . . . . . . . . . . . . . . . . . . . . .2--63 LANDING INIT 2/3 2-46. . . . . . . . . . . . . . . . . . . . . . . . . . .2--64 RUNWAY FACTOR 1/1 2-47. . . . . . . . . . . . . . . . . . . . . . .2--65 LANDING INIT 3/3 2-48. . . . . . . . . . . . . . . . . . . . . . . . . . .2--66 LANDING DATA 1/1 2-49. . . . . . . . . . . . . . . . . . . . . . . . . .


D201110000041REV 1 Jun 2013 TC--5

Table of Contents



List of Figures (cont)

Figure Page

2--67 MISSED APPROACH Page 2-50. . . . . . . . . . . . . . . . . . .2--68 ALTERNATE FPL Page 2-51. . . . . . . . . . . . . . . . . . . . . . .

3--1 PERF Function Button 3-2. . . . . . . . . . . . . . . . . . . . . . . .3--2 PERF INDEX 1/2 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3--3 PERF INDEX 2/2 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3--4 Performance Index Organization With TOLD 3-4. . . . .3--5 Performance Initialization Block Diagram 3-7. . . . . . . .3--6 TAKEOFF INIT Page With Certification

Agency and Software Identification 3-9. . . . . . . . . . . .3--7 TAKEOFF INIT 1/4 Page 3-11. . . . . . . . . . . . . . . . . . . . . .3--8 TAKEOFF INIT 2/4 Page 3-11. . . . . . . . . . . . . . . . . . . . . .3--9 TAKEOFF INIT 3/4 Page 3-13. . . . . . . . . . . . . . . . . . . . . .3--10 TAKEOFF INIT 4/4 Page 3-14. . . . . . . . . . . . . . . . . . . . . .3--11 TAKEOFF DATA 1/2 Page 3-15. . . . . . . . . . . . . . . . . . . . .3--12 TAKEOFF DATA 2/2 Page 3-16. . . . . . . . . . . . . . . . . . . . .3--13 LANDING INIT 1/3 Page 3-17. . . . . . . . . . . . . . . . . . . . . .3--14 LANDING INIT 2/3 Page 3-18. . . . . . . . . . . . . . . . . . . . . .3--15 RUNWAY FACTOR 1/1 Page 3-19. . . . . . . . . . . . . . . . . .3--16 LANDING INIT 3/3 Page 3-20. . . . . . . . . . . . . . . . . . . . . .3--17 LANDING DATA 1/1 Page 3-21. . . . . . . . . . . . . . . . . . . . .3--18 TAKEOFF PROBLEMS 1/1 Page With

Takeoff Initialization Problems 3-22. . . . . . . . . . . . . . . .3--19 TAKEOFF PROBLEMS 1/1 Page With

Takeoff Data Calculation Problems 3-24. . . . . . . . . . . .3--20 LANDING PROBLEMS 1/1 Page With

Landing Initialization Problems 3-26. . . . . . . . . . . . . . . .3--21 LANDING PROBLEMS 1/1 Page With

Landing Data Calculation Problems 3-27. . . . . . . . . . .3--22 NAV IDENT 1/1 Page With MAINTENANCE

at 4L 3-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3--23 FMS 1 MAINTENANCE Page With DATA LOAD

at 4L 3-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3--24 DATA LOAD Page With TOLD DB Selection

at 4L 3-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3--25 Confirmation of Transfer 3-31. . . . . . . . . . . . . . . . . . . . . .3--26 Loading Progress Monitoring 3-32. . . . . . . . . . . . . . . . . . .3--27 Database Transfer Complete 3-32. . . . . . . . . . . . . . . . . .3--28 TAKEOFF INIT 1/4 With SW ID at 2R 3-33. . . . . . . . . . .


D201110000041REV 3 Nov 2013




List of Tables

Table Page

3--1 TAKEOFF INIT Problem Messages 3-23. . . . . . . . . . . . .3--2 TAKEOFF DATA Problem Messages 3-24. . . . . . . . . . . .3--3 TAKEOFF DATA Parameters 3-25. . . . . . . . . . . . . . . . . .3--4 LANDING INIT Problem Messages 3-26. . . . . . . . . . . . .3--5 LANDING DATA Problem Messages 3-27. . . . . . . . . . . .3--6 LANDING DATA Parameters 3-28. . . . . . . . . . . . . . . . . . .

4--1 CDU Entry Format 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . .

5--1 TOLD Message 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A--1 November 2013 Citation X FMS SW Ver. 6.1PAR Response List A-1. . . . . . . . . . . . . . . . . . . . . . . . .


D201110000041REV 1 Jun 2013 TC--7

Table of Contents



List of Procedures

Procedure Page

3--1 Field Loadable TOLD Database Updating 3-29. . . . . . .


D201110000041REV 1 Jun 2013



Blank Page


D201110000041REV 3 Nov 2013 1-1

Introduction


1. Introduction

This guide describes the normal and abnormal procedures for theTakeoff and Landing (TOLD) function of the Honeywell FlightManagement System (FMS) for the Cessna Citation X.

This guide, when used in conjunction with the FMZ Series FMS Pilot’sGuide (Honeywell Pub. No. D200802000002), covers all FMSoperations and options. The operator should refer to the Aircraft FlightManual (AFM) Supplement for current limitations related to the use ofTOLD.

This guide is divided into the following sections:

D Section 1 -- Introduction -- This section describes the structure ofthis guide and gives product and publications ordering information.

D Section 2 -- Operational Example -- This section describes thenormal operational procedures of the FMS and is repeated from theFMZ Series FMS Pilot’s Guide with the specific Citation X TOLDpages added.

D Section 3 -- Performance -- This section describes theperformance functions of the FMS.

D Section 4 -- Control Display Unit (CDU) Entry Format -- Thissection describes the correct format for entries on the CDU.

D Section 5 -- Messages -- This section lists TOLD--generatedmessages and FMS--generated messages.

D Appendix A -- Citation X FMS 6.1 Applicable Program/ProductAction Requests (PARs) -- This section containsProgram/ProductAction Requests (PAR) applicable to the Citation X.

The TOLD function for the Citation X is based on AFM data that usesthe following conditions:

D All takeoff performance is based on a paved, dry or wet runway.

D All landing performance is based on a paved, dry or wet runway.

This guide is based on TOLD software versions 1.0, 2.0, 5.0, and 6.0and reflects FMS 6.1 software. This revision is for the incorporation ofAppendix A: PAR listing for the Cessna Citation X FMS 6.1.

This publication is intended to be used as a guide and is written forsystem familiarization only. This guide does not supersede any FederalAviation Administration (FAA) or original equipment manufacturer(OEM)--approved procedures.


D201110000041REV 1 Jun 2013

Introduction1-2


HONEYWELL PRODUCT SUPPORT

The Honeywell spares exchange (SPEX) program for corporateoperators supplies an extensive exchange and rental service thatcomplements a worldwide network of support centers. An inventory ofmore than 9,000 spare components assures that the Honeywellequipped aircraft will be returned to service promptly and economically.This service is available both during and after warranty.

The aircraft owner/operator is required to ensure that units suppliedthrough this program have been approved in accordance with theirspecific maintenance requirements.

All articles are returned to Reconditioned Specifications limits whenthey are processed through a Honeywell repair facility. All articles areinspected by quality control personnel to verify proper workmanshipand conformity to Type Design and to certify that the article meets allcontrolling documentation. Reconditioned Specification criteria are onfile at Honeywell facilities and are available for review. All exchangeunits are updated with the latest performance reliability MODs on anattrition basis while in the repair cycle.

For more information regarding the SPEX program, includingmaintenance, pricing, warranty, support, and access to an electroniccopy of the Exchange/Rental Program for Corporate Operators, Pub.No. A65--8200--001, you can go to the Honeywell web site at:http://www.honeywell.com/sites/aero/Avionics_Services1.htm.


D201110000041REV 3 Nov 2013 1-3

Introduction


CUSTOMER SUPPORT

For support of products or to request the latest revision to a publication,contact the local Honeywell customer support.

Global Customer Care (GCC)

For all aerospace inquiries including:

D Technical assistance

D Aircraft--on--ground (AOG)

D Sales: new and exchange

D Repair and overhaul

D Supply chain optimization

D Rentals

D Return material authorization (RMA).

Use the following GCC contact numbers:

D Fax: 1--602--822--7272

D Phone: 1--800--601--3099 (U.S.A./Canada)

D Phone: 1--602--365--3099 (International).

Technical Operations Center (TOC)

For direct technical support for:

D Avionics technical support

D Mechanical support.

Use the following TOC contact numbers:

D Phone: 1--855--808--6500 (U.S.A./Canada)

D Phone: 1--602--365--6500 (International).

Choose Option 1 for avionics or Option 2 for mechanical.


D201110000041REV 3 Nov 2013

Introduction1-4


To Register Your Publication (if Required)

For future revisions, please contact Honeywell Technical PublicationsOrder Management via Fax at:

D 1--602--822--7272

Or via e--mail at:

D [email protected]

Please provide: NameAddressPhone NumberPublication Number

In addition, if required:

D Identify a change of address, telephone number, or e--mail address.

Honeywell Aerospace Technical Publications

If you have access to the Internet, go to theHoneywell OnlineTechnicalPublications web site at https://myaerospace.honeywell.com to:

D Download or see publications online

D Make an order for a publication

D Tell Honeywell of a possible data error (report a discrepancy) in apublication.

If you do not have access to the Honeywell Online TechnicalPublications web site and need technical publications information:

D Send an e--mail message to the GCC at:[email protected]

D Send a fax or speak to a person at the GCC contact numbers.


D201110000041REV 1 Jun 2013 2-1

Operational Example


2. Operational Example

INTRODUCTION

This section describes the normal operational procedures of the flightmanagement system (FMS) for a flight from Phoenix, Arizona (KPHX)to Minneapolis/St. Paul, Minnesota (KMSP). KMSP is forecast to beInstrument Meteorological Conditions (IMC) at arrival time; therefore,Duluth, Minnesota (KDLH) is used as the alternate.

The flight route, shown in Figure 2--1, begins in Phoenix and proceedsfrom Zuni (ZUN) by way of J102 to the Alamosa (ALS) VOR, direct tothe Denver (DVV) VOR, J114 to the O’NEILL (ONL) VOR, then directto theMasonCity (MCW)VOR. The flight departs Phoenix from runway08R using the EAGUL3 departure with the ZUN transition (KPHXRW08R EAGUL3.ZUN), shown in Figure 2--2. The arrival is by way ofthe Mason City transition to the KASPR2 arrival, shown in Figure 2--3,followed by the PRESS initial approach segment of the ILS approachfor runway 30L at KMSP (MCW.KASPR2 PRESS.ILS RW30L KMSP).The ILS 30L approach is shown in Figure 2--4.

NOTE: The standard instrument departure (SID), standard terminalarrival route (STAR), approach, waypoints, and airways usedin this example do not reflect current navigation data. Whenperforming this operational example on an actual FMS,waypoints, distances, and times differ from those shown.

Section 3, Performance, provides more detailed information on theTOLDpages listed in this section. Section 4, ControlDisplayUnit (CDU)Entry Format, provides details about entry format.

Figure 2--1KPHX to KMSP Route of Flight


D201110000041REV 1 Jun 2013

Operational Example2-2


Figure 2--2Phoenix, AZ EAGUL3 Departure


D201110000041REV 1 Jun 2013 2-3

Operational Example


Figure 2--3Minneapolis, MN KASPR2 Arrival


D201110000041REV 1 Jun 2013



Figure 2--4Minneapolis, MN ILS 30L Approach


D201110000041REV 1 Jun 2013 2-5

Operational Example


PRE--DEPARTURE

TheFMSguides thepilot through theground initialization process usingthe lower right line select key (4R). After completing thepage (or pages)for each step, selecting 4R moves to the next step. The flow chart inFigure 2--5 shows the preflight procedure for a normal flight.

Figure 2--5FMS Preflight Procedure Flow Chart


D201110000041REV 1 Jun 2013



Power--Up

The NAV IDENT 1/1 page, shown in Figure 2--6, is displayed whenpower is first applied.

Figure 2--6NAV IDENT 1/1 After Power--Up

The date and time shown on this page is synchronized with theglobal positioning system (GPS) date and time. The date and timecan be changed if the GPS has failed or does not have a validdate/time. A battery maintains the date and time when power isremoved from the FMS.

The software identifier is displayed at 3L for verification. Thesoftware identifier must be referenced when maintenance action isrequested.

The maintenance prompt (4L) is used to verify the FMS systemoperating configuration.

Navigation database (NDB) information is displayed on the rightside of the NAV IDENT page. The active database dates are shownat 1R. The dates for the alternate period are shown at 2R. Onpower--up, the FMS automatically chooses the active NDB thatcorresponds to the current date.

The WORLD3--04 NDB, shown at 3R in Figure 2--6, indicatesworldwide coverage and cycle of the NDB.

The next initialization step (POS INIT in reverse video) is displayedand selected at 4R.


D201110000041REV 1 Jun 2013 2-7

Operational Example


POSITION INITIALIZATION

The LAST POS coordinates are displayed at 1L on the POSITION INIT1/1 page, as shown in Figure 2--7. At 2L, the closest RAMPX within3 NM (nautical miles) of the last position (1L) is displayed. When noRAMPXwaypoint is available, the closest airport reference point (ARP)within 3 NM of the last position (1L) is displayed. When no ARP isavailable, the pilot is prompted to enter a waypoint or coordinates. Inthis example, the Phoenix airport is displayed. At 3L, the coordinatesof the highest priority valid GPS is displayed.

Figure 2--7POSITION INIT 1/1


D201110000041REV 1 Jun 2013



To initialize FMS position, the appropriate LOAD prompt (1R, 2R, or3R) is selected. The selected position becomes the FMS position,as shown in Figure 2--8. This initializes the connected sensors thatreceive inputs from the FMS.

Each FMS position must be initialized. Initialization positions arenever transferred between the FMSs. After initialization, the FLTPLAN prompt is displayed at 4R indicating the next step to beperformed. Selecting this prompt continues the preflight process.

Figure 2--8POSITION INIT 1/1 -- Reference Waypoint Loaded


D201110000041REV 3 Nov 2013 2-9

Operational Example


ACTIVE FLIGHT PLAN

When the initialization coordinates are within 3 miles of an airport in thedatabase, the airport (KPHX in this example) is already loaded in theORIGIN line, as shown in Figure 2--9. An entry option of estimated timeof departure (ETD) is entered in order to give the estimated time ofarrivals (ETAs) prior to takeoff. This supports predictive receiverautonomous integrity monitor (RAIM) calculations.

Figure 2--9ACTIVE FLT PLAN 1/1 -- KPHX Loaded as Origin

The destination (KMSP) is entered in the scratchpad and line selectedto the DEST prompt at 2R, as shown in Figure 2--10.

Figure 2--10ACTIVE FLT PLAN 1/2 -- KMSP Loaded as Destination

When there is a stored flight plan with the same origin and destination,the FLT PLAN LIST page is displayed (not shown in this example).Selecting the RETURN prompt (1R) on the FLT PLAN LIST pagereturns the display to the ACTIVE FLT PLAN page.


D201110000041REV 1 Jun 2013



Waypoint Entry

The en route waypoints are entered in the line labeled VIA.TO. In thisexample, the ZUN VOR is entered as the first en route waypoint, asshown in Figure 2--11. The entry is made by typing the identifier in thescratchpadandusing the line select key adjacent to theVIA.TOprompt.

Figure 2--11Waypoint Entry on ACTIVE FLT PLAN Pages

Airway Entry

The next entry in this example is a high altitude airway (e.g., J102) tothe ALS VOR. The airway identifier followed by the last desiredwaypoint of the airway is inserted on the line below the VIA.TO prompt.Both are separated by a period (J102.ALS), as shown in Figure 2--12.

Figure 2--12Airway Entry on ACTIVE FLT PLAN Pages


D201110000041REV 1 Jun 2013 2-11

Operational Example


The FMS retrieves all waypoints that define J102 between ZUN andALS, as shown in Figures 2--13 through 2--15.

Figure 2--13Waypoint Retrieval for Airway Entry on ACTIVE FLT PLAN 1/4



D201110000041REV 1 Jun 2013




The upper right corner of the ACTIVE FLT PLAN page indicates thereare four pages for the active flight plan. Pushing the NEXT buttonadvances to the next page of the active flight plan. Pushing the PREVbutton shows the previous active flight plan page.

In this example, GUP44 is a significant intersection on J102 located44 miles from theGallup (GUP) VOR. This same convention is used forother unnamed intersections. For distances greater than 100 NM, thehundreds digit is dropped and the number is prefixed to the NAVAIDidentifier.

The remainder of the flight plan to Mason City (DVV, J114.ONL, MCW)is entered in the samemanner as previously described. The remainderof the ACTIVE FLT PLAN pages are shown in Figures 2--16 through2--19.

Figure 2--16DVV Entered on the ACTIVE FLT PLAN


D201110000041REV 1 Jun 2013 2-13

Operational Example


Figure 2--17J114 Entered on the ACTIVE FLT PLAN

Figure 2--18ONL Entered on the ACTIVE FLT PLAN

Figure 2--19MCW Entered on the ACTIVE FLT PLAN


D201110000041REV 1 Jun 2013



The flight plan is closed bymoving KMSP to the VIA.TO line by pushingthe line select key (2R) adjacent to KMSP. This action moves KMSP tothe scratchpad, as shown in Figure 2--20.

Figure 2--20Destination (KMSP) Moved to the Scratchpad

KMSP is moved from the scratchpad to the VIA.TO prompt (2L), asshown in Figure 2--21, by pushing the adjacent line select key. Thedestination must be included as the last flight plan waypoint forestimated time en route (ETE) to the destination on the PROGRESSpage. The destination is also required to calculate performance data.

Figure 2--21Destination (KMSP) Entered as Last Waypoint in Flight Plan


D201110000041REV 1 Jun 2013 2-15

Operational Example


When an alternate flight plan is needed, pushing the NEXT buttondisplays the ALTERNATE FPL page, as shown in Figure 2--22. Thewaypoints for the alternate route of flight are entered on this page.

Figure 2--22ALTERNATE FPL

Duluth (KDLH) is entered as the alternate destination (2R) in thisexample, as shown in Figure 2--23.

Figure 2--23KDLH Entered on the ALTERNATE FPL Page


D201110000041REV 1 Jun 2013



The route to KDLH is by way of the GOPHER (GEP) VOR. Thealternate flight plan is entered the same way as for the en route flightplan. The alternate flight plan is closed by moving KDLH to the VIA.TOline, as was donewithKMSP in the active flight plan. The alternate flightplan for this example is shown in Figure 2--24.

Figure 2--24Routing for Alternate Flight Plan Entered

This completes the flight plan definition. Pushing the lower right lineselect key (4R) begins performance initialization (PERF INIT). ThePERF INIT selection is not shown when performance has beeninitialized prior to running this example.


D201110000041REV 1 Jun 2013 2-17

Operational Example


PERFORMANCE INITIALIZATION

Performance initialization is required for the operation of verticalnavigation (VNAV) and performance calculations. There are five (FAA)and six (JAA) PERFORMANCE INIT pages when FULL PERF isselected. This example illustrates the FULL PERF initialization. Thefollowing values are used in the planning of this example flight plan.Actual numbers used depend on the aircraft type.

BOW: 22,100 lb

FUEL: 12,000 lb

CARGO: 200 lb

PASSENGER: 5 @ 170 lb

CRUISE ALTITUDE: 41,000 feet

WINDS ALOFT: 250_@ 125 kts @ FL 410

The default values for most performance initialization data are thevalues from the previous flight. Assuming the aircraft is flown the sameway each flight, performance initialization consists of verifying thedefault values, making changes where required, and entering itemssuch as wind and weight.

Depending on the initialization configuration of the FMS, weights aredisplayed in either pounds or kilograms.

Data verified and entered under performance initialization affectsseveral performance functions important to the completion of the flight.For example, understatingwindmay indicate sufficient fuel to completethe flight. In reality, more fuel may be required. A careful review ofinitialization data is required to ensure accurate predicted aircraftperformance.


D201110000041REV 1 Jun 2013



All data must be entered on the PERF INIT pages in order for the FMSto show VNAV predictions.

Many values on the PERF INIT and PERF DATA pages areaircraft--dependent. Actual values may vary from those shown in theseexamples.

D PERFORMANCE INIT 1/5 -- The PERFORMANCE INIT 1/5 page,shown in Figure 2--25, displays the following:

— Aircraft type (1L)— Tail number (1R)— Data source (2L)— Access to aircraft database loading (4L).

The tail number (1R) must be entered on this page when the FULLPERF has been selected as the data source (refer to aircraft tailnumber).

Figure 2--25PERFORMANCE INIT 1/5


D201110000041REV 1 Jun 2013 2-19

Operational Example


D PERFORMANCE INIT 2/5 -- The PERFORMANCE INIT 2/5 page,shown in Figure 2--26, displays the current speed schedules.Selecting the OR prompt or entering the calibrated airspeed(CAS)/MACH data changes the respective mode. Default valuesare restoredby using the *DELETE* function on theappropriate line.


The descent angle entered on this page is used as the default valuefor each path. The descent angle is also used for computingtop--of--descent (TOD) points.

The FMS uses the climb, cruise, and descent speed schedules tosupply a speed command to the flight director system.


D201110000041REV 1 Jun 2013



As an example, when the OR prompt for cruise is selected, thecruise mode page, shown in Figure 2--27, is displayed. The cruisemode desired is selected from the available list. This action makesthe selected cruise mode active and returns to thePERFORMANCE INIT 2/5 page. In this example, long--range cruise(LRC) is the active mode.

Figure 2--27CRUISE MODES 1/1

The departure/approach speed prompt, as shown in Figure 2--26,(4L) is used to access departure, approach, and go--around speedschedules.

D PERFORMANCE INIT--LB 3/5 -- The PERFORMANCE INIT--LB3/5 page, shown in Figure 2--28, contains the step climb incrementused for performance planning, fuel reserve, and fuel allowance fortakeoff and landing. TO/LDG FUEL powers up with the defaultvalues from the aircraft database file. Entering *DELETE* restoresany of these lines to the default values. The FUEL RESERVE linehas an OR option.

Figure 2--28PERFORMANCE INIT--LB 3/5


D201110000041REV 1 Jun 2013 2-21

Operational Example


D PERFORMANCE INIT 4/5 -- The PERFORMANCE INIT 4/5 page,shown in Figure 2--29, contains the following:

— Transition altitude (1L)— Speed/altitude limit (1R)— Initial cruise altitude (2L)— International Standard Atmosphere (ISA) deviation (2R)— Cruise winds (3L and 3R).


Above the transition altitude, ACTIVE FLT PLAN and the PERFPLAN page altitudes are displayed as flight levels. Constraints fromSIDs, STARs, and approaches are displayed in feet or flight levelsas defined in the navigation database.

The SPD/ALT LIM is used to limit the speed target to the speed limitfor altitudes below the restriction altitude.When in adescent and theIASexceeds the speed limit, descent speed is higher than the speedlimit, the speed target is reduced before the restriction altitude isreached. The limit is either changed or eliminated by entering*DELETE*.

Initial cruise altitude can be entered. When OPTIMUM is displayed,the optimum cruise altitude is computed. The cruise altitude isdisplayed in small characters when PERFORMANCE INIT iscompleted. The optimum cruise altitude is rounded to the nearest1,000 feet.

Average cruise wind and ISA DEV are entered on this page. Theseentries are optional. The FMS assumes zero wind and ISA DEVwhen no entry is made. Wind information at each waypoint is alsoentered on the PERF PLAN pages.


D201110000041REV 1 Jun 2013



D PERFORMANCE INIT--LB 5/5 -- The PERFORMANCE INIT--LB5/5 page, shown in Figure 2--30, is where passenger and cargoweights are entered to calculate gross weight.

When performance initialization is complete, the CONFIRM INITprompt is displayed in the lower right corner of this page. TheCONFIRM INIT line select key (4R) must be pushed to initiate thecalculation of performance data.

Figure 2--30CONFIRM INIT Prompt on PERFORMANCE INIT--LB 5/5

PERFORMANCE DATA

There are four pages of PERF DATA. The data is based on thePERFORMANCE INIT pages as well as the active flight plan.Performance data is displayed for the destination and the alternatedestinationwhen one has been entered. These pages are continuouslyupdated during the flight.

D PERF DATA 1/4 -- The PERF DATA 1/4 page, shown inFigure 2--31, displays the following:

— Cruise/ceiling altitude (1L)— Step increment (1R)— ETE (2L and 2R)— Fuel required (3L and 3R)— Fuel figure--of--merit (FOM) (3L and 3R).

Fuel required is the total fuel that includes the following:

— Takeoff allowance— En route (climb/cruise/descent)— Landing allowance— Reserves.


D201110000041REV 1 Jun 2013 2-23

Operational Example


Pilot--entries are permitted on the cruise altitude and step incrementlines only. The cruise altitude value increases automatically whenthe altitude selector is dialed above the current cruise altitude.

Figure 2--31PERF DATA 1/4


— Distance to go (1L and 1R)— ETA (2L and2R) (only shownwhenairborne or following anentry

of ETD on the active flight plan)— Estimated fuel remaining (2L and 2R)— Estimated gross weight (3L and 3R).

No entries are permitted on this page.



D201110000041REV 1 Jun 2013




— Average cruise wind (1L)— Average cruise headwind or tailwind (1R)— Preflight plan destination fuel remaining (2R)— Updated plan destination fuel remaining (3R) (only shown when

airborne)— Difference between preflight and updated plan (3R) (only shown

when airborne).

No entries are permitted on this page.



— Method of reserve calculation (1L)— Required reserve (2R)— Preflight plan fuel remaining (2R)— Updated plan fuel remaining (3R) (only shown when airborne)— Difference between preflight and updated plan (3R) (only shown

when airborne).


D201110000041REV 1 Jun 2013 2-25

Operational Example


The DEPARTURE prompt, shown in Figure 2--34, is displayed onthe lower right corner (4R) of all the PERF DATA pages indicatingthe next step. When a runway has already been selected, theprompt reads TAKEOFF instead of DEPARTURE.


DEPARTURE SELECTION

Selecting the DEPARTURE prompt displays the DEPARTURERUNWAYS 1/1 page, as shown in Figure 2--35. The available runwaysfor the origin airport are displayed. In this example, runway 08R isselected with line select key 3L.

Figure 2--35DEPARTURE RUNWAYS 1/1


D201110000041REV 1 Jun 2013



After the runway has been selected, the SIDs page is displayedwith thepossible departure procedures, as shown in Figure 2--36. Theappropriate procedure is selected from the list. For this example,EAGUL3 at 2R is selected. When no SID is to be used, the ACTIVATEprompt (4R) selects the runway and shows the ACTIVE FLT PLANpage.

Figure 2--36SIDs 1/2

The DEPARTURE TRANS 1/1 page, shown in Figure 2--37, lists theen route transitions for the selected departure. For this flight, the ZUNtransition (2L) is selected.

Figure 2--37DEPARTURE TRANS 1/1


D201110000041REV 1 Jun 2013 2-27

Operational Example


At this point, the departure selection is complete and the flight crewmayeither REVIEW or ACTIVATE the SID, as shown in Figure 2--38.ACTIVATE (4R) inserts the runway and procedure into the active flightplan. The SID contains both the lateral waypoints and any verticalconstraints for the procedure contained in the database.

Figure 2--38PROCEDURE 1/1

Flight Plan Discontinuities

A discontinuity occurs in a flight plan when adding a SID or STAR. Thediscontinuity is caused by the lack of a common point between the flightplanand the insertedSID orSTAR. Thediscontinuity is removed by oneof the two following methods:

D Pushing the delete (DEL) button and the adjacent line select keydeletes the discontinuity.

D Moving any waypoint into the line where the discontinuity is located.


D201110000041REV 1 Jun 2013



TAKEOFF INITIALIZATION

Activating the departure returns to the ACTIVE FLTPLANpage, shownin Figure 2--39. The TAKEOFF prompt is displayed in the lower rightcorner (4R) indicating the next step: takeoff initialization. There are fourTAKEOFF INIT pages.

Figure 2--39TAKEOFF Prompt on the ACTIVE FLT PLAN Page

D TAKEOFF INIT 1/4 -- The TAKEOFF INIT 1/4 page, shown inFigure 2--40, displays the following:

— Aircraft type (1L)— Certification agency or rules (2L)— Software ID (2R)— TOLD database date and identifier (3L)— TOLD database ID (3R).No entries are permitted on this page.

Figure 2--40TAKEOFF INIT 1/4


D201110000041REV 1 Jun 2013 2-29

Operational Example


D TAKEOFF INIT 2/4 -- The TAKEOFF INIT 2/4 page, shown inFigure 2--41, displays the following:

— Runway (1L)— Runway length and magnetic heading (1R)— Temperature (2L)— Surface wind (2R)— Pressure altitude (3L)— BARO (barometric) setting (3L)— Runway elevation (3R)— Temperature compensation (4R).

Runway information is normally retrieved from the database. Whenthe runway is not in the database, the runway information is enteredby the pilot.


Static air temperature (SAT) is sensed or entered. Sensedtemperature is preferred before actual flight. When the temperatureis forecast to be significantly different at takeoff time, an enteredtemperature can be used for planning purposes. For takeoff, usingthe sensed temperature is recommended in place of the enteredtemperature that had been used for planning purposes.

If configured, TEMP COMP is displayed at 4R. For detailedinformation on the TEMP COMP CONFIG page and the TEMPCOMP page display, refer to the FMZ Series FMS Pilot’s Guide(Honeywell Pub. No. D200802000002).

Surfacewind is a required entry and is normally the only entry madeon this page.


D201110000041REV 1 Jun 2013



The FMS continuously performs a takeoff configuration check. Thischeck compares how the FMS is initialized to calculate takeoff dataagainst actual aircraft or environmental conditions. Takeoff data iscomputed when a miscompare exists using the values specifiedduring takeoff initialization. The FMS flags the item out ofconfiguration and the VSPEEDS with reverse video until themiscompare is resolved.

D TAKEOFF INIT 3/4 -- The TAKEOFF INIT 3/4 page, shown inFigure 2--42, displays the following additional runway information:

— Runway slope (1L)— Runway width and displayed threshold (1R)— Runway condition (2L)— Obstacle distance (3L)— Obstacle elevation (3R).

All entries are optional. There is no default value for runway slope.The default for runway width and displayed threshold is 100.Obstacle distance is entered in feet from the departure end of therunway and elevation is mean sea level (MSL) (default for both isNONE).



D201110000041REV 1 Jun 2013 2-31

Operational Example


D TAKEOFF INIT 4/4 -- The TAKEOFF INIT 4/4 page, shown inFigure 2--43, displays the settings for the following:

— Anti--ice (1L)— Flaps (2L)— Takeoff weight (3L).

NOTE: Depending on the configurationmodule of the aircraft, thetakeoff weight (3L) is shown in kilograms (kg) orpounds (lb). For illustration purposes, the example isdisplayed in pounds.

Default values are normal takeoff configuration settings. Changesare made using the right line select keys (1R and 2R).

The takeoff weight is computed from entries on thePERFORMANCE INIT 5/5 page. An overriding weight entry ispermitted on this page. This entry does not change thePERFORMANCE INIT gross weight.


Once all TAKEOFF INIT required entries have been made, theCONFIRM INIT prompt is displayed. The CONFIRM INIT prompt (4R)must be pushed to start takeoff computations and display theTAKEOFF DATA pages.


D201110000041REV 1 Jun 2013



TAKEOFF DATA

There are two TAKEOFF DATA screens.

D TAKEOFF DATA 1/2 -- The TAKEOFF DATA 1/2 page, shown inFigure 2--44, displays the computed values for takeoff.

When the takeoff is out of limits, the most restrictive limit is displayedin the center of the second line, adjacent to thewindvalue. Ascratchpadmessage of TAKEOFF OUT OF LIMITS is displayed and no takeoffdata is available.

Figure 2--44TAKEOFF DATA 1/2


D201110000041REV 1 Jun 2013 2-33

Operational Example


D TAKEOFF DATA 2/2 -- The TAKEOFF DATA 2/2 page, shown inFigure 2--45, displays the FMS computed VSPEEDS.

VSPEEDS in reverse video indicate that the aircraft configuration,defined under TAKEOFF INIT, has not yet been met.

Figure 2--45TAKEOFF DATA 2/2

NOTE: Takeoff data may be recomputedwhen changes occur in anyof the sensed values being used. The pilot should reconfirmcomputed speeds and distances prior to takeoff.


D201110000041REV 1 Jun 2013



RUNWAY POSITION

When a departure runway is selected, the prompt at 4R of the ACTIVEFLT PLAN shows RW POS after all other actions are completed. Oncetheaircraft is at the runway threshold, the FMSand long--range sensorscan be updated to the runway threshold position. This action is anoption.

The inertial reference systems (IRSs) are not normally updated at theend of the runway because a downmode align requires that the aircraftbe stationary for a minimum of 30 seconds during the procedure. Moreimportantly, when excessive motion is detected, a full IRS realignmentis required. Normal passenger and cargo loading is not consideredexcessive motion. When the IRSs have been in NAV mode for anextended period of time (i.e., greater than 1 hour) and/or excessivegroundspeed error has accumulated (i.e., greater than 2 knots), adownmode align is recommended prior to taxi--out to the runway.

The IRS downmode align zeros accumulated velocity errors andupdates heading. An option of position update during the procedurezeros any accumulated position error.

Pushing the line select key (4R) adjacent to theRW POS prompt on theACTIVE FLT PLAN page, as shown in Figure 2--46, displays thePOSITION INIT page for updates.

Figure 2--46RW POS Prompt on the ACTIVE FLT PLAN Page


D201110000041REV 1 Jun 2013 2-35

Operational Example


D POSITION INIT 1/1 -- The POSITION INIT 1/1 page, shown inFigure 2--47, displays the coordinates for the selected runway andmakes them available for loading.

Figure 2--47Runway Coordinates on the POSITION INIT 1/1 Page

D Threshold Position Update -- Pushing the line select key (2R)adjacent to the runway 08R coordinates loads the runway thresholdposition into the FMS, as shown in Figure 2--48. The position is alsoloaded into sensors set to receive an update.

Figure 2--48POSITION INIT 1/1 -- Runway 08R Threshold Coordinates

Loaded


D201110000041REV 1 Jun 2013



TAKEOFF

The FMS considers the aircraft airborne when exceeding 50 knotsgroundspeed (GSPD), 80 knots indicated airspeed (KIAS), orweight--off--wheels. When airborne, the ACTIVE FLT PLAN pageshows the ETA for each waypoint in place of ETE, as shown inFigure 2--49.WhenanETD is entered prior to takeoff, ETAs arealreadyshown. Once airborne, the ETA for theFROMwaypoint is replacedwiththe actual crossing time. ETEs for any waypoint in the flight plan areavailable on the PERF PLAN pages or the PROGRESS 1/3 page.

Figure 2--49ETAs Displayed on the ACTIVE FLT PLAN Page

The FMS can be selected and coupled to the flight director shortly aftertakeoff. Initially, the FMS is armed on the flight director. While within thecapture zone, the FMS captures and begins lateral guidance.

When VNAV coupling is required, the flight director VNAV mode isengaged. The FMS begins generating vertical guidance when thealtitude selector is set to the appropriate altitude. The FMS does notcommand a climb above, or descent below, the altitude selector.

The DEPARTURE prompt is displayed on the active flight plan pagesuntil the aircraft is more than 50 NM from the origin airport. TheDEPARTURE prompt is displayed only when the origin is an airport.


D201110000041REV 1 Jun 2013 2-37

Operational Example


D Waypoint Sequencing -- On takeoff, the runway becomes theFROM waypoint and remains on the top line of the ACTIVE FLTPLAN page. The TO waypoint is shown on the second line. As theaircraft passes the TO waypoint, all waypoints scroll up one line, asshown in Figure 2--50. This process is called waypoint sequencing.

Figure 2--50Waypoint Sequencing

D PROGRESS 1/3 -- Information available on the PROGRESS 1/3page, shown in Figure 2--51, is displayed by pushing the PROGfunction button. This page includes the NAV mode (GPS in thisexample), required navigation performance (RNP) value, andestimated position uncertainty (EPU) information.

Figure 2--51Typical PROGRESS 1/3 Page

The ACTIVE FLT PLAN page 1 and the PROGRESS 1/3 page areconsidered the primary pages of the FMS during flight.


D201110000041REV 1 Jun 2013



D PROGRESS 2/3 -- The PROGRESS 2/3 page, shown inFigure 2--52, displays the following:

— Speed command/altitude command (1L)— Top--of--climb (TOC) (2L)— Current fuel quantity (2R)— Top--of--descent (TOD) (3L)— Current gross weight (3R)— SET RNP (4L)— VNAV DATA (4R).

Figure 2--52Typical PROGRESS 2/3

The TOC and TOD points are not displayed as waypoints as part ofthe ACTIVE FLT PLAN. When available, the TOC and TOD pointsare displayed on the map and vertical profile. The position of thesepoints are dynamically updated. The positions relative to otherwaypoints in the flight plan can change. Changes to the flight planalso affect the TOC and TOD positions.


D201110000041REV 1 Jun 2013 2-39

Operational Example


CLIMB

As the climb continues, intermediate altitude clearances are enteredusing the altitude selector. The FMS commands the autopilot to climbto the selected altitude or the next altitude constraint, whichever islowest. When altitude restrictions are associated with a waypoint, theyare entered on the CDU adjacent to the appropriate waypoint. The18,000 feet at or above constraint on ZUN was entered in this fashionand is shown in Figure 2--53.

Figure 2--53Altitude Constraint Entered at ZUN VOR (18,000 Feet)


D201110000041REV 1 Jun 2013



EN ROUTE

Once at cruise altitude, the information on the PROGRESS 2/3 pagereflects the commanded speed and altitude information for the cruisesegment, as shown in Figure 2--54. In this example, long--range cruisewas selected as the active cruise mode and .92M represents thelong--range cruise speed for current conditions.

Figure 2--54Cruise Speed and Altitude Information on the

PROGRESS 2/3 Page

As the flight progresses, clearance revisions are completed using oneof the two following methods:

1. When the revision is after theTOwaypoint, the flight plan ismodifiedby adding or deleting waypoints.

2. When the revision affects the TOwaypoint (suchas clearancedirectfrom present position to another point), the flight plan is modified bypushing the direct (DIR) button.

Operation of the DIR button displays the ACTIVE FLT PLAN page 1,regardless of what page is currently on the CDU.

When thedirect--towaypoint is already in the flight plan, pushing the lineselect key to the left of the waypoint makes that waypoint the TOwaypoint. When the direct--to waypoint is not in the flight plan, enteringthe identifier for the direct--to waypoint where the dashes are locatedin the upper left corner of the page, makes that waypoint the TOwaypoint. Either of these actions results in the FMS immediatelyaltering course.


D201110000041REV 1 Jun 2013 2-41

Operational Example


DESCENT

TheFMScalculates aTODpoint basedon thedestination elevationandany entered altitude constraints. When VNAV is engaged and thealtitude selector is set to a lower altitude, the aircraft descends at theTOD. When VNAV is not engaged or the altitude selector is not setlower, the aircraft remains at altitude through the TOD. In the lattercase, the descent can be initiated by setting a lower altitude andselecting an appropriate flight director mode or manually flying thedescent. Once in descent, the FMS sets the target altitude to thealtitude selector or the next constraint, whichever is higher.

ARRIVAL

When within 200 flight plan miles of the destination airport, theARRIVAL prompt is displayed at 4R, as shown in Figure 2--55. Pushingthis button selects an arrival procedure or runway. The ARRIVAL pageis always accessed from the NAV INDEX page.

Figure 2--55ARRIVAL Prompt on the ACTIVE FLT PLAN Page


D201110000041REV 1 Jun 2013



Selecting the ARRIVAL prompt displays the ARRIVAL page, as shownin Figure 2--56. The destination airport is displayed at 1R with accessto selecting the runway, approach, and/or STAR. While the selectioncan be made in any order, this example selects 2L to choose anapproach. Selecting an approach automatically selects a runway.

Figure 2--56ARRIVAL 1/1

The APPROACH page with the available approach procedures isshown in Figure 2--57. The assigned or required approach is selectedfrom this page. Selecting an approach also includes the missedapproach procedure. For this example, the ILS 30L approach (2R) isselected.

Figure 2--57KMSP APPROACH 1/1


D201110000041REV 1 Jun 2013 2-43

Operational Example


Following the approach selection, the APPROACH TRANS page,shown in Figure 2--58, is displayed. The appropriate transition isselected. For this example, the PRESS approach transition (1L) isselected.

Figure 2--58KMSP APPROACH TRANS 1/1

After the approach is selected, the STAR page is displayed with theavailable arrival procedures, as shown in Figure 2--59. When an arrivalprocedure has been assigned, that procedure is selected from the list.For this example, the KASPR2 arrival is selected (3L).

Figure 2--59KMSP STAR 1/1


D201110000041REV 1 Jun 2013



When a STAR has transition fixes, the STAR TRANS page isautomatically displayed, as shown in Figure 2--60. When assigned, theSTAR transition is selected. For this flight, the Mason City (MCW)transition (3L) is selected.

Figure 2--60KMSP STAR TRANS 1/1

After the transition is selected, the ARRIVAL page is displayed with asummary of the selections, as shown in Figure 2--61. If no STARand/orSTAR TRANS is used, the ARRIVAL prompt (4R) returns the systemto the ARRIVAL summary page that has the ACTIVATE prompt, asshown inFigure 2--61. TheACTIVATEprompt at 4R inserts theselectedprocedures in the active flight plan.

Figure 2--61Typical ARRIVAL 1/1 Page


D201110000041REV 1 Jun 2013 2-45

Operational Example


APPROACH

Once thearrival selection is activated, theFMSguides theaircraft alongthe STAR and approach procedure. When a localizer based approachis selected as in this example, final approach can be flown using theflight director. When a non--precision approach is selected, the FMScan be used for guidance on final approach.

LANDING INITIALIZATION

Following activation of an arrival procedure, the LANDING prompt isdisplayed on the ACTIVE FLT PLAN page. The LANDING INIT pagesare displayed after selecting the landing prompt.

D LANDING INIT 1/3 -- The LANDING INIT 1/3 page, shown inFigure 2--62, displays the following:

— Runway (1L)— Runway length and magnetic heading (1R)— Temperature (2L)— Surface wind (2R)— Pressure altitude (3L)— BARO (Barometric) setting (3L)— Runway elevation (3R)— TEMP COMP (4R).

Figure 2--62LANDING INIT 1/3


D201110000041REV 1 Jun 2013



Runway information is retrieved from the database. For landing,both surface temperature andwind are required entries. Barometricsetting is from the digital air data computer (DADC) and used by theFMS to calculate the pressure altitude for the runway elevation.

If configured, TEMP COMP is displayed at 4R. For detailedinformation on the TEMP COMP CONFIG page and the TEMPCOMP page display, refer to the FMZ Series FMS Pilot’s Guide(Honeywell Pub. No. D200802000002).

D LANDING INIT 2/3 -- The LANDING INIT 2/3 page, shown inFigure 2--63, displays a page used to show/enter any of thefollowing additional runway information:

— Runway slope (1L)— Runway width and displayed threshold (1R)— Runway factor (2L)— Shows the RUNWAY FACTOR page. Selection between DRY,

WET, or USER DEFINED is permitted on this page. (2R).

NOTE: All landing performance is based on a paved, dry, or wetrunway.



D201110000041REV 1 Jun 2013 2-47

Operational Example


D RUNWAY FACTOR 1/1 -- The options for the landing factor settingare displayed on the RUNWAY FACTOR 1/1 page, shown inFigure 2--64.

— Shows the DRY runway factor setting. The DRY runway factorsetting is 1.67 times the actual landing distance from the aircraftflight manual (AFM). When selected, ACT is displayed next tothe setting (1L).

— Shows the WET runway factor setting. The WET runway factorsetting is 1.92 times the actual landing distance from the AFM.When selected, ACT is displayed next to the setting (2L).

— Shows the USER DEFINED runway factor setting. The USERDEFINED runway factor is a pilot--entered value between 1.00and 9.99 times the actual landing distance from the AFM. Whenselected, ACT is displayed next to the setting (3L).

— Enables direct access to the LANDING INIT 2/3 page (1R).

NOTE: When one of these settings is selected, the page returns tothe LANDING INIT 2/3 page with the selected runway factorin line 2L.

Figure 2--64RUNWAY FACTOR 1/1


D201110000041REV 1 Jun 2013



D LANDING INIT 3/3 -- The LANDING INIT 3/3 page, shown inFigure 2--65, displays aircraft normal landing configuration and thepredicted landing weight. This information is continually updated.This is the weight used for landing calculations unless the pilotenters a landing weight.

NOTE: Depending on the configurationmodule of the aircraft, thelanding weight (3L) is displayed in kilograms (kg) orpounds (lb). For illustration purposes, the example isdisplayed in pounds.


Once all LANDING INIT required entries have been made, theCONFIRM INIT prompt is displayed. The CONFIRM INIT prompt(4R) must be pushed to start landing computations and display theLANDING DATA page.


D201110000041REV 1 Jun 2013 2-49

Operational Example


LANDING DATA

The LANDING DATA 1/1 page, shown in Figure 2--66, displays thefollowing:

— Projected landing weight (1L)— Available landing distance/actual landing distance (ALD) (1R)— Maximum allowable weight based on the data entered on the

initialization pages, up to the maximum certified weight (2L)— Corrected landing distance/runway factor (2R)— VREF for the flap setting in the LANDING INIT page, and the

landing approach climb speed (VAPP) (3L)— Headwind and crosswind components (3R).

Figure 2--66LANDING DATA 1/1

When the landing is out of limits, a scratchpadmessage stating themost restrictive limit is displayed. The FMS computes landing dataand shows the data on the LANDING DATA page.

NOTES: 1. Due to tolerances in the calculation of landing data, itis possible for valid entered values to be displayed inreverse video on the LANDING DATA page. Theoperator should refer to the AFM Supplement forcurrent limitations related to the use of TOLD.

2. Landing data may be recomputed when changesoccur in any of the sensed values beingused. Thepilotshould reconfirm computed speeds and distancesprior to landing.


D201110000041REV 1 Jun 2013



MISSED APPROACH

TheMISSED APPROACH pages follow the ACTIVE FLT PLAN pageswhen an approach from the navigation database has been activated.The MISSED APPROACH pages contain waypoints for the missedapproach segment, as shown in Figure 2--67. The first waypoint on theMISSEDAPPROACHpage 1 is themissed approachpoint (MAP). TheMAP is also in the active flight plan. When activated, the missedapproach is inserted into the active flight plan after the MAP.

Figure 2--67MISSED APPROACH Page

Two nautical miles before sequencing the final approach fix (FAF) or5 nautical miles from the runway end, the MISSED APPR prompt isdisplayed at 4L on the ACTIVE FLT PLAN page. The missed approachcan be activated by selecting the MISSED APPR prompt (4L) orpushing the takeoff/go--around (TOGA) switch. The missed approachis then inserted into the active flight plan.

The MISSED APPR prompt must not be selected until the decision tomiss the approach has been made. When MISSED APPR is selected,any portion of the flight plan that is past the MAP is replaced with themissed approach procedure.


D201110000041REV 1 Jun 2013 2-51

Operational Example


ALTERNATE FLIGHT PLAN

A typical alternate flight plan page is shown in Figure 2--68. Analternateflight plan follows the active flight plan and missed approach pageswhen an alternate is entered. When a flight plan to an alternate hasbeenentered, theALTERNATEprompt is displayedon theACTIVEFLTPLAN page when the aircraft is within 25 NM of the destination. Whenthe flight plan contains an approach, the ALTERNATE prompt isdisplayed only after themissed approach has been activated. When anALTERNATE is selected before the destination is reached, the FMSguides the aircraft to the original destination and then to the alternate.ALTERNATE must not be armed until a decision has been made todivert to the alternate. Pushing the DIR button permits a direct flight tothe alternate airport without continuing to the original destination.

Figure 2--68ALTERNATE FPL Page


D201110000041REV 1 Jun 2013



CLEARING OF FLIGHT PLANS

The active flight plan is cleared 60 seconds after removing power whenthe aircraft is in flight or on the ground. The pilot configures the FMS toretain the active flight plan regardless of the power loss duration.

Activating a stored flight plan clears the previous active flight plan.Activating a stored flight plan while in flight is permitted, but the pilot isrequired to confirm that the present active flight plan is to be replaced.Whether on the ground or in flight, a stored flight plan or portion of aflight plan is inserted into the active flight plan as a string of waypointsstarting at the point of insertion. Flight plans are also cleared, onewaypoint at a time, using the DEL button.

While on the ground, entering a new origin after some or all of the flightplan has been defined is permitted. If the new origin is already awaypoint in the flight plan, the waypoints before the first appearance ofthe new origin are deleted. If the new origin is not already a waypointin the flight plan, the whole flight plan is deleted. Deleting the originclears the entire flight plan. This applies to both active and stored flightplans.

Within approximately 15 seconds after landing, theCLEARFPLpromptis displayed at 4R on the ACTIVE FLT PLAN page. Selecting thisprompt clears the entire active flight plan.

Another action performed on the ground that results in clearing theactive flight plan is to activate the previously inactive database on theNAV IDENT page of the control display unit (CDU).


D201110000041REV 1 Jun 2013 3-1

Performance


3. Performance

INTRODUCTION

The flight management system (FMS) performance computations arebasedon initialization data, flight plan, and inputs from aircraft systems.With this information, the FMS controls a variety of mission planningand speed control functions for the aircraft.

The control display unit (CDU) pages that control performance aresimilar to the navigation pages. As a general rule, when the systemsupplies the information, items are displayed in small characters. Theyare displayed in large characters when the pilot makes an entry.

There are several areas of initialization within the performancefunctions of the FMS. In order for the FMS to calculate performancedata, the initialization pages must be reviewed and the CONFIRM INITprompt at 4R on the last page of initialization must be pushed.

Performance information in the FMS is based on data entered by thepilot and calculated by the FMS. Mission planning data has not beenevaluated by the Federal Aviation Administration (FAA) for accuracyand is not approved by the FAA.

FMS fuel quantities are displayed two different ways. When showingcurrent fuel--on--board, the quantity is displayed in pounds or kilograms(e.g., 16250). When showing planned fuel remaining at waypoints andfuel required, the quantity is displayed in thousands of pounds orkilograms (e.g., 12.3, meaning 12,300). Fuel quantities that reflect thegauge value are displayed in pounds or kilograms. Fuel quantitiesassociated with the flight plan are displayed in thousands of pounds orkilograms. The FMS fuel management data is advisory informationonly. It must not be used in lieu of the aircraft primary fuel flow indicator.


D201110000041REV 1 Jun 2013

Performance3-2


PERFORMANCE INDEX

Theperformance index (PERF INDEX) pages are accessed by pushingthe PERF function button, shown in Figure 3--1.

Figure 3--1PERF Function Button


D201110000041REV 1 Jun 2013 3-3

Performance


When the PERF button is pushed, the PERF INDEX 1/2 page, shownin Figure 3--2, is displayed. The PERF INDEX 2/2 page, shown inFigure 3--3, is displayed by using either the PREV or NEXT pagingbuttons. Thesepages showperformance functions that canbeselectedat any time. Pushing the line select key adjacent to the respectivefunction selects the function. These pages are examples of the indexwhen FULL PERF is selected.

Figure 3--2PERF INDEX 1/2

Figure 3--3PERF INDEX 2/2


D201110000041REV 1 Jun 2013

Performance3-4


Performance Index Organization

Several FMS performance functions require initialization. For thesefunctions, when the related initialization selection is complete, theCONFIRM INIT prompt must be selected to compute the performancedata. The computed data is used for FMS functions. A block diagramof performance index organization is shown in Figure 3--4. The blockdiagram assumes the active flight plan has been closed and an activedeparture has been identified.

Figure 3--4Performance Index Organization With TOLD


D201110000041REV 1 Jun 2013 3-5

Performance


PERFORMANCE INITIALIZATION

The pilot selects one of the following three methods to completeperformance initialization:

D Full Performance -- The FMS uses an uploaded and learnedaircraft database file to perform time and fuel calculations. The timecalculations are also based on pilot--entered speed schedules andwinds. Computed cruise speed schedules, such as long--rangecruise (LRC) and maximum speed, can be selected.

D Pilot Speed/Fuel Flow -- The FMS uses pilot--entered speedschedules and winds to perform time calculations. The fuelcalculations are based on pilot--entered cruise fuel flow.Adjustments are made for the higher fuel flow in climb.

D Current Groundspeed/Fuel Flow -- The fuel calculations arebased on the current fuel flow displayed on the FUEL MGT page.A fuel flow entry made on that page takes the place of the sensedfuel flow. The time calculations are based on the currentgroundspeedwhile airborne.While on theground, theFMS uses thedefault groundspeed.

Figure 3--5 shows the sequence of initialization and data pages for theFull Performance method of performance calculations. The pilot mustverify and review all the entered and computed data.

Citation X Performance Initialization

In normal operations, once the parameters that do not change witheach flight, (e.g., BOW) have been entered the first time, the variouspages of initialization are essentially reviewed. While the performancecapability of the FMS is comprehensive and can require severaldecisions, normal operations do not require starting from zeroinitialization at the start of each flight. Outlined in Figure 3--5 are thetypical and simplified actions required for the following utilizing TOLD:

D Performance initialization

D Performance data

D Takeoff initialization

D Takeoff data.

For all operations, the pilot must verify both the entered data andcomputed data are sufficient to supply safe and effective aircraftoperation.


D201110000041REV 1 Jun 2013

Performance3-6


Blank Page


D201110000041REV 1 Jun 2013

Performance3-7/3--8


Figure 3--5Performance Initialization Block Diagram


D201110000041REV 1 Jun 2013 3-9

Performance


TOLD CONFIGURATION

TOLD operation and limits are dependent on the certifying agency andthe configuration of the aircraft. These items are displayed on theTAKEOFF INIT 1/4 page, as shown in Figure 3--6.

Figure 3--6TAKEOFF INIT Page With Certification Agency and Software

Identification

The certification agency or certification rules are displayed at 2L. Thesoftware identification is displayed at 2R.

The navigation computer part number differs for each certificationagency. Differences are indicated in this guide by reference to thecertification agency.

TAKEOFF INITIALIZATION

Takeoff initialization is required for theFMS to calculate takeoff dataandhave VSPEEDS posted on the primary flight display (PFD). There arefour pages of initialization.

The FMS continuously performs a takeoff configuration check. Thischeck compares the initialization inputs/selection against actual aircraftor environmental conditions. The following items are included in theconfiguration check:

D Pressure altitude (within 100 feet of sensed)D TemperatureD BARO setting (within 0.01 inHg of DADC setting)D Anti--iceD Flaps.


D201110000041REV 1 Jun 2013

Performance3-10


For this example, during takeoff initialization, the flaps are specified tobe 15_, but the flaps are actually set at 0_. Takeoff data is still computedunder this condition using the values specified during takeoffinitialization. The FMS identifies the flaps being out of takeoffconfiguration by reverse video of the flap selection on the takeoffinitialization pages. In addition, VSPEEDS are shown on the takeoff datapages in reverse video and not displayed on the PFD.

When all items covered by the configuration check are properly set, thereverse video is removed and takeoff speeds are displayedon thePFD.This indicates to thepilot that theaircraft configuration andenvironmentmatches those used to calculate takeoff data.

Entries to any of the TAKEOFF INIT pages are inhibited when throttlelever angle (TLA) is greater than 60_.

NOTES: 1. For runways recalled from the database, the pilotmustverify that the actual runway being used is entered.The FMS does not compare takeoff heading with theselected runway to verify the displayed takeoff data isappropriate (e.g., a runway change just beforedeparture).

2. A last minute decision to take off in other than theconfiguration entered in TAKEOFF INIT (such asturningonanti--ice) results in a configurationmismatchand inhibits auto VSPEEDS.


D201110000041REV 1 Jun 2013 3-11

Performance


D TAKEOFF INIT 1/4 -- The TAKEOFF INIT 1/4 page, shown inFigure 3--7, contains the following information:

— Aircraft type (1L)

— Certification agency or rules (2L)

— Software ID (2R)

— TOLD database date and identifier (3L)

— TOLD database ID (3R).

Figure 3--7TAKEOFF INIT 1/4 Page

D TAKEOFF INIT 2/4 -- The TAKEOFF INIT 2/4 page, shown inFigure 3--8, illustrates database information about the departurerunway (when one has been selected).



D201110000041REV 1 Jun 2013

Performance3-12


—1L -- The selected runway identifier is displayed in this field.Whenno runway has been selected on the DEPARTURE pages, thefield shows dashes. Entries are permitted and are made usingthe two--digit identification (e.g., 29 meaning 290_). Entries indegrees require a three--digit input.

—1R -- The length of the runway andmagnetic heading is displayedin this field. When no runway has been selected, entry promptsare displayed. Anentry of runway length can bemade to overridethe database information or supply the length when the runwayis not in the database.

—2L -- The sensed static air temperature is displayed in this field.Under normal circumstances, the sensed temperature must beused. An entry can be made for cases where the predictedtemperature for takeoff is different than the current sensedtemperature. Even in this case, a return to sensed temperatureprior to takeoff is recommended. An entry can be made indegrees Celsius. Entries in degrees Fahrenheit require a leadingbackslash (/).

—2R -- The surface wind is a required entry on this page.

—3L and 3R -- The computed pressure altitude and barometric(BARO) setting from the air data computer (ADC) are displayedin this field. Also displayed is the runway elevation from thedatabase. Entries are permitted for all of these items, but noentries are normally made. The only recommended entry iselevation in the case where the runway is not in the database.

Entry of BARO setting is permitted and can be made in inHg ormillibars. The default value and units are displayed when*DELETE* is selected for this line. When a runway has beenselected, the pressure altitude is computed based on the fieldelevation and the BARO setting. When an entry of pressurealtitude is made, elevation is computed using the BARO set.

— 4R -- TEMP COMP is displayed at 4R if configured by the FMS.T.O. DATA is displayed at 4R, following the initial selection ofCONFIRM INIT, if TEMP COMP conditions are not met. Formore detailed information on the TEMP COMP CONFIG pageand the TEMPCOMPpagedisplay, refer to theFMZ Series FMSPilot’s Guide (Honeywell Pub. No. D200802000002).


D201110000041REV 1 Jun 2013 3-13

Performance


D TAKEOFF INIT 3/4 -- The TAKEOFF INIT 3/4 page, shown inFigure 3--9, is used for entry of additional runway information.


— 1L -- The slope of the runway is displayed. Positive slopes areshown with an up arrow (). Negative slopes are shown with adown arrow (). When no runway has been selected, entryprompts are displayed. Anentry of slope canbemade to overridethe database information or supply the slope when the runwayis not in the database.

—1R -- An entry for displaced threshold is made in this field. Thedefault is 100 feet. The width of the runway, when available fromthe database, is also displayed.

—2L and 2R -- The selected runway condition for takeoffcalculations is displayed at 2L. The default is DRY. The settingis changed at 2R.

—3L and 3R -- An entry of obstacle distance and elevation is madein these fields. The default is none.

Obstacle distance is referenced from the departure end of therunway. Obstacle height is referenced from mean sea level(MSL).

Some departures specify obstacle clearance in terms of aminimum rate of climb or climb gradient. Unless that requirementcan be related to a specific obstacle at a givendistance, theFMSdoes not accept either of theseminimum values. This is becausethe FMS is basing obstacle clearance on the computed takeofffield length that is different than the runway length.


D201110000041REV 1 Jun 2013

Performance3-14


D TAKEOFF INIT 4/4 -- The TAKEOFF INIT 4/4 page, shown inFigure 3--10, gives defaults to the normal takeoff configuration.


— 1L and 1R -- The selected anti--ice setting for takeoff calculationsis displayed at 1L. The default setting is OFF. The setting ischanged at 1R. When the actual anti--ice setting is different thanthe selected setting, this line is displayed in reverse video.

—2L and 2R -- The selected flap setting for takeoff calculations isdisplayed at 2L. The setting is changed at 2R. When the actualflap setting is different than the selected setting, this line (2L) isdisplayed in reverse video.

—3L -- The takeoff grossweight is displayed in this field. The takeoffweight is the gross weight from the performance initializationpage. An overriding manual entry is permitted on this page. Thedefault takeoff weight is restored by using the *DELETE*function. When the PERF INIT weights have not been entered,the T.O. WEIGHT line shows a prompt. When weight changesduring ground operations, the takeoff data is automaticallycalculated using the new weight.

NOTE: Depending on the configuration module of the aircraft,the takeoff weight (3L) is displayed in kilograms (kg) orpounds (lb). For illustration purposes, the example isdisplayed in pounds.

—4R -- The CONFIRM INIT prompt is displayed when all requiredtakeoff initialization items are entered. The CONFIRM INITprompt must be selected to start takeoff data calculation.Changes made to takeoff initialization after selection of the


D201110000041REV 1 Jun 2013 3-15

Performance


CONFIRM INIT prompt are automatically recalculated withoutselecting CONFIRM INIT. Selection of the CONFIRM INITprompt is only required for initial calculation.

When the aircraft weight is above the maximum takeoff weight,the FMS shows the maximum takeoff weight on the TAKEOFFDATA page. No takeoff data calculations are displayed on thepage. For below minimum takeoff weight, the TAKEOFF INITpage shows the PROBLEMS prompt and no takeoff data iscalculated.

Takeoff Data

There are two TAKEOFF DATA pages that display the takeoffinformation based on the entered values.

D TAKEOFF DATA 1/2 -- The TAKEOFF DATA 1/2 page, shown inFigure 3--11, is a display--only page. The TAKEOFF DATA 1/2 pageshows the computed values for the takeoff.

Figure 3--11TAKEOFF DATA 1/2 Page

When the takeoff is out of limits, themost restrictive limit is displayedin the center of the second line adjacent to the wind value. Ascratchpad message of TAKEOFF OUT OF LIMITS is displayedand no takeoff data is available. Possible limiting conditions includethe following:

— Climb limited— Field length limited


D201110000041REV 1 Jun 2013

Performance3-16


D TAKEOFF DATA 2/2 -- The TAKEOFF DATA 2/2 page, shown inFigure 3--12, illustrates FMS computed VSPEEDS. As previouslynoted, the VSPEEDS in reverse video indicate the aircraftconfiguration, defined under TAKEOFF INIT, has not yet beenmet.

Figure 3--12TAKEOFF DATA 2/2 Page

LANDING INITIALIZATION

Completion of landing initialization is required for the computation oflanding data. There are three pages of initialization. Operation is similarto takeoff initialization: when landing initialization does not match thecurrent aircraft configuration, those items are displayed in reversevideo. Landing data is computed using the landing initializationconfiguration under these conditions.

NOTE: Due to tolerances in the calculation of landing data, it ispossible for valid entered values to be displayed in reversevideoon theLANDINGDATApage. Theoperator should referto the Aircraft Flight Manual (AFM) Supplement for currentlimitations related to the use of TOLD.


D201110000041REV 1 Jun 2013 3-17

Performance


D LANDING INIT 1/3 -- The LANDING INIT 1/3 page, shown inFigure 3--13, illustrates database information about the arrivalrunway (when one has been selected).

Figure 3--13LANDING INIT 1/3 Page

— 1L -- The selected runway identifier is displayed.Whenno runwayhas been selected on the ARRIVAL pages, the field showsdashes. Entries are made using the two--digit identification (e.g.,29meaning 290_). Entries in degrees require a three--digit input.

—1R -- The length of the runwayandmagneticheading isdisplayed.When no runway has been selected, entry prompts aredisplayed. Entry of a runway length is made at any time.

—2L -- Entry prompts are displayed in this field. An entry can bemade in degrees Celsius. Entries in degrees Fahrenheit requirea leading backslash (/). This is a required entry since the groundtemperature cannot be sensed while airborne.

—2R -- The surface wind is entered in this field. This is a requiredentry.

—3L and 3R -- When an arrival runway has been selected, the fieldelevation and the ADC BARO setting are used to compute thepressure altitude. Entry of BARO setting is permitted and can bemade in inches or millibars. The *DELETE* button is used toreturn an entry to the sensed value.


D201110000041REV 1 Jun 2013

Performance3-18


Pressure altitude can be entered or calculated. In the normalsituationwhere pressure altitude and baro set are not entered bythe pilot, pressure altitude is calculated using the current DADCbaro setting and runway elevation.When theDADC baro settingis changed, the new pressure altitude and landing data areautomatically recalculated. When pressure altitude and/orBARO set are entered, changes to the DADC baro setting haveno impact on pressure altitude and landing data.

— 4R -- TEMP COMP is displayed if temperature compensation isconfigured by the FMS. If temperature compensation has notbeen configured, LAND DATA is displayed following the initialselection of CONFIRM INIT.

D LANDING INIT 2/3 -- The LANDING INIT 2/3 page, shown inFigure 3--14, is used for entry of additional runway information.


— 1L -- The slope of the runway is displayed. Positive slopes areshown with an up arrow () and negative slopes are shown witha down arrow (). When no runway has been selected, entryprompts are displayed. An entry of slope is made to override thedatabase information or supply the slopewhen the runway is notin the database.

—1R -- An entry for displayed threshold is made in this field. Thedefault is 0 feet. Thewidth of the runway, whenavailable from thedatabase, is also displayed.


D201110000041REV 1 Jun 2013 3-19

Performance


—2L -- The selected runway factor for the landing calculations isdisplayed here. This setting is used to multiply the actual landingdistance by the selected runway factor to compute a correctedlanding distance. The runway factor can be DRY (1.67), WET(1.92), or USERDEFINED (X.XX). TheUSERDEFINED settingis set by thepilot and canhavea valueof 1.00 to 9.99. Thesettingis changed on the RUNWAY FACTOR page, accessible at 2R.

—2R -- This line shows the RUNWAY FACTOR page. Selectionbetween DRY, WET, or USER DEFINED is permitted on thispage.

D RUNWAY FACTOR 1/1 -- The options for the landing factor settingare displayed on the RUNWAY FACTOR 1/1 page, shown inFigure 3--15.

Figure 3--15RUNWAY FACTOR 1/1 Page

— 1L -- This line shows the DRY runway factor setting. The DRYrunway factor setting is 1.67 times the actual landing distancefrom the AFM. When selected, ACT is displayed next to thesetting.

— 2L -- This line shows the WET runway factor setting. The WETrunway factor setting is 1.92 times the actual landing distancefrom the AFM. When selected, ACT is displayed next to thesetting.


D201110000041REV 1 Jun 2013

Performance3-20


— 3L -- This line shows the USERDEFINED runway factor setting.The USER DEFINED runway factor is a pilot--entered valuebetween1.00and9.99 times theactual landingdistance from theAFM. When selected, ACT is displayed next to the setting.

— 1R -- This line provides direct access to the LANDING INIT 2/3page.

NOTE: When one of these settings is selected, the page returns tothe LANDING INIT 2/3 page with the selected runway factorin line 2L.

D LANDING INIT 3/3 -- The LANDING INIT 3/3 page, shown inFigure 3--16, illustrates aircraft landing configuration. This pagedefaults to standard landing configuration.


— 1Land 1R -- The selectedanti--ice setting for landing calculationsis displayed at 1L. The default setting is OFF. The setting ischanged at 1R.

—2L and 2R -- The selected flap setting for landing calculations isdisplayed at 2L. The default setting is FULL. The setting ischanged at 2R.

—3L -- The projected landing gross weight is displayed in this field.Changes to the projected landing weight results in an automaticrecalculation of landing data. Pilot--entry of landing weight ispermitted.

NOTE: Depending on the configuration module of the aircraft,the landing weight (3L) is displayed in kilograms (kg)or pounds (lb). For illustration purposes, the exampleis displayed in pounds.


D201110000041REV 1 Jun 2013 3-21

Performance


—4R -- The CONFIRM INIT prompt is displayed when all requiredlanding initialization items are entered. The CONFIRM INITprompt must be selected to start landing data calculation.Changes made to landing initialization after selection of theCONFIRM INIT prompt are automatically recalculated withoutselecting CONFIRM INIT. In other words, selection of theCONFIRM INIT prompt is only required for initial calculation.

LANDING DATA

The LANDING DATA page is accessed through the LANDING INITpages.

D LANDING DATA 1/1 -- The LANDING DATA 1/1 page, shown inFigure 3--17, is displayed by the following:

— Projected landing weight (1L)— Available landing distance/actual landing distance (ALD) (1R)— Maximum allowable weight based on the data entered on the

initialization pages, up to the maximum certified weight (2L)— Corrected landing distance/runway factor (2R)— VREF for the flap setting in the LANDING INIT page, and the

landing approach climb speed (VAPP) (3L)— Headwind and crosswind components (3R).

Figure 3--17LANDING DATA 1/1 Page


D201110000041REV 1 Jun 2013

Performance3-22


When the landing conditions are out of limits, a scratchpadmessagestating the most restrictive limit is displayed. The FMS computeslanding data and shows the data on the LANDING DATA page.Possible limiting conditions are as follows:

D Landing climb limited

D Field length limited.

NOTE: Due to tolerances in the calculation of landing data, it ispossible for valid entered values to be displayed in reversevideoon theLANDINGDATApage. Theoperator should referto the AFM Supplement for current limitations related to theuse of TOLD.

PROBLEMS PAGE

TOLD provides a TAKEOFF PROBLEMS and a LANDINGPROBLEMS page to supply additional details regarding initialization ordata calculation problems. A problem page exists for initialization anddata calculation for both takeoff and landing.

D TAKEOFF PROBLEMS 1/1 -- The TAKEOFF PROBLEMS 1/1page, shown in Figure 3--18, illustrates the problems with takeoffinitialization. This page is accessed from TAKEOFF INIT page 4.

Figure 3--18TAKEOFF PROBLEMS 1/1 Page With

Takeoff Initialization Problems


D201110000041REV 1 Jun 2013 3-23

Performance


Refer to Table 3--1 for possible messages shown on this page.

Table 3--1TAKEOFF INIT Problem Messages

Message Reason for Message

AFM DB INVALID AFM database is invalid

DATA NOTINITIALIZED

One or more initialization values aredashed

TEMP OUT OFENVELOP

Temperature is outside of computedenvelope

P ALT OUT OFLIMITS

Pressure altitude is outside of AFM limits

RWY SLOPE OUTOF LIMITS

Computed slope is greater than 2% orless than --2%

WIND OUT OFLIMITS

Headwind/tailwind is outside of AFMlimits

ANTI--ICE ONABOVE 10C

No table data when anti--ice is on above10 C

THRESH > RWYLENGTH

Threshold length is greater than runwaylength


D201110000041REV 1 Jun 2013

Performance3-24


D TAKEOFF PROBLEMS 1/1 -- The TAKEOFF PROBLEMS 1/1page, shown in Figure 3--19, illustrates the problems encounteredduring takeoff data calculations. This page is accessed fromTAKEOFF DATA.

Figure 3--19TAKEOFF PROBLEMS 1/1 Page WithTakeoff Data Calculation Problems

-- 2L -- The AFM data table that resulted in the takeoff datacomputation problem displaying. Refer to Table 3--2 forpossible AFM table messages shown on this line.

Table 3--2TAKEOFF DATA Problem Messages

Message AFM Data Table

MAXIMUMTAKEOFF WEIGHT

Maximum takeoff weight permitted byclimb requirements

FIELD LENGTHCORRECT

Takeoff field length -- takeoff corrections

2ND SEG NETCLIMB GRAD

Second segment takeoff net climbgradient

TAKEOFF FIELDLENGTH

Takeoff field length


D201110000041REV 1 Jun 2013 3-25

Performance


-- 3L -- The parameter that exceeds the AFM data table isdisplayed. Refer to Table 3--3 for possible parameters shownin this field.

Table 3--3TAKEOFF DATA Parameters

Message Parameter

ALT OUT OFBOUNDS

Altitude exceeds table limits

WGT OUT OFBOUNDS

Weight exceeds table limits

TEMP OUT OFBOUNDS

Temperature exceeds table limits

WIND OUT OFBOUNDS

Wind exceeds table limits

SLOPE OUT OFBOUNDS

Runway slope exceeds table limits

FLD LEN OUT OFBOUNDS

Field length exceeds table limits

NO TABLE DATA The table listed does not contain data forthe conditions entered


D201110000041REV 1 Jun 2013

Performance3-26


D LANDING PROBLEMS 1/1 -- The LANDING PROBLEMS 1/1page, shown in Figure 3--20, illustrates the problems with landinginitialization. This page is accessed from LANDING INIT page 4.

Figure 3--20LANDING PROBLEMS 1/1 Page With

Landing Initialization Problems

Refer to Table 3--4 for possible messages shown on this page.

Table 3--4LANDING INIT Problem Messages

Message Reason for Message

AFM DB INVALID AFM database is invalid

DATA NOTINITIALIZED

One or more initialization values aredashed

TEMP OUT OFENVELOP

Temperature is outside of computedenvelope

P ALT OUT OFLIMITS

Pressure Altitude is outside of AFM limits

RWY SLOPE OUTOF LIMITS

Computed slope is greater than 2% orless than --2%

WIND OUT OFLIMITS

Headwind/tailwind is outside of AFMlimits

ANTI--ICE ONABOVE 10C

No table data when anti--ice is on above10 C

THRESH > RWYLENGTH

Threshold length is greater than runwaylength


D201110000041REV 1 Jun 2013 3-27

Performance


D LANDING PROBLEMS 1/1 -- The LANDING PROBLEMS 1/1page, shown in Figure 3--21, illustrates the problems encounteredduring landing data calculations. This page is accessed fromLANDING DATA.

Figure 3--21LANDING PROBLEMS 1/1 Page WithLanding Data Calculation Problems

-- 2L -- The AFM data table that resulted in the landing datacomputation problem displaying. Refer to Table 3--5 forpossible AFM table messages displayed in this field.

Table 3--5LANDING DATA Problem Messages

Message AFM Data Table

MAXIMUMLANDING WEIGHT

Maximum landing weight permitted byclimb requirements or brake energylimits

LANDINGDISTANCE

Landing distance


D201110000041REV 1 Jun 2013

Performance3-28


-- 3L -- The parameter that exceeds the AFM data table isdisplayed. Refer to Table 3--6 for possible parametersdisplayed in this field.

Table 3--6LANDING DATA Parameters

Message Parameter

ALT OUT OFBOUNDS

Altitude exceeds table limits

WGT OUT OFBOUNDS

Weight exceeds table limits

TEMP OUT OFBOUNDS

Temperature exceeds table limits

WIND OUT OFBOUNDS

Wind exceeds table limits

SLOPE OUT OFBOUNDS

Runway slope exceeds table limits

FLD LEN OUT OFBOUNDS

Field length exceeds table limits

NO TABLE DATA The table listed does not contain data forthe conditions entered


D201110000041REV 2 Sep 2013 3-29

Performance


FIELD LOADABLE TOLD AIRCRAFT DATABASEUPDATING

Refer to Procedure 3--1 for instructions on updating the aircraft TOLDdatabase. For more detailed information on the dataloader and thegeneral dataloading process, refer to the FMZ Series FMS NZ 6.1Pilot’s Guide (Honeywell Pub. No. D200802000002).

Step Procedure 3--1 Field Loadable TOLD DatabaseUpdating

1 Transfer the TOLD database file ltold_db.bn0 from theappropriate CITX FMS TOLD DATABASE CD to a USBflash drive.

2 Insert the USB flash drive into the dataloader and push theSELECT button on the dataloader to select the pilot sideFMS (LEFT side light is ON).

3 On the pilot side CDU, access the NAV IDENT 1/1 page,shown in Figure 3--22. Select MAINTENANCE at 4L.

Figure 3--22NAV IDENT 1/1 Page With MAINTENANCE at 4L


D201110000041REV 2 Sep 2013

Performance3-30


Step Procedure 3--1 Field Loadable TOLD DatabaseUpdating (cont)

4 The FMS MAINTENANCE page, shown in Figure 3--23. isdisplayed. Select DATA LOAD at 4L .

Figure 3--23FMS 1 MAINTENANCE Page With DATA LOAD at 4L

5 The DATA LOAD page is displayed, shown in Figure 3--24.This page is used to access various dataloading functionsof the FMS. Select TOLD DB at 4L .

Figure 3--24DATA LOAD Page With TOLD DB Selection at 4L


D201110000041REV 2 Sep 2013 3-31

Performance



6 To confirm transfer of the TOLD database, select YES at4R, shown in Figure 3--25. This begins the dataloadingprocess.

Figure 3--25Confirmation of Transfer


D201110000041REV 2 Sep 2013

Performance3-32



7 Progress monitoring is shown in Figure 3--26, as the FMSindicates the percentage complete. When finished, themessage DB TRANSFER COMPLETE is displayed in thescratchpad, shown in Figure 3--27, and the FMS executesa restart.NOTE: When power is interrupted, ABORT is selected, or other problems

stopping the loading process occur, the dataload process must berepeated from the beginning.

Figure 3--26Loading Progress Monitoring

Figure 3--27Database Transfer Complete


D201110000041REV 2 Sep 2013 3-33

Performance



8 Using the SELECT button on the dataloader, select thecopilot side FMS (RIGHT side light is ON).

9 Repeat steps 3 through 7 using the copilot’s CDU.

10 Once the process is completed, verify that the TOLDdatabase has been updated by accessing the TAKEOFFINIT 1/4 page, shown in Figure 3--28, and viewing the SWID field at 2R. In this example, LT1.0 is shown, where LTindicates loadable TOLD and 1.0 is the software versionnumber.

Figure 3--28TAKEOFF INIT 1/4 With SW ID at 2R


D201110000041REV 1 Jun 2013

Performance3-34


Blank Page


D201110000041REV 1 Jun 2013 4-1

Control Display Unit (CDU) Entry Format


4. Control Display Unit (CDU)Entry Format

INTRODUCTION

Each entry made to the CDU must be checked for correct syntax orformat at the time the entry is line selected from the scratchpad.

NOTES: 1. Leading zeros and zeros after a decimal are notrequired unless otherwise specified.

2. Data entry limits shown for some parameters areexceeded.

LIST OF ENTRIES AND DEFINITION

Table 4--1 defines the requirements for each type of entry.

Table 4--1CDU Entry Format

Entry Format

Barometric(BARO) Set

D Entry in millibars or inches of mercury (decimalrequired)

D Leading zero not required

D Range from 16.00 to 32.00 (inHg), 542 to1083 (millibars)

LandingWeight

D Entry in pounds or kilograms depending onconfiguration

D Entry is either four or five digits

D Range is 0000 to 36,100 pounds

D Range is 0000 to 16,374 kilograms

ObstacleDistance

D Entry in feet is one to six digits

D Range is from 0 to 999,999 feet

D Entry in meters is one to five digits

D Range is from 0 to 303030 m

ObstacleElevation

D Entry in feet is one to five digits

D Range is from -1,000 to 99,999 (always infeet)


D201110000041REV 1 Jun 2013

Control Display Unit (CDU) Entry Format4-2


Table 4--1 (cont)CDU Entry Format

Entry Format

Outside AirTemperature

D Entry is in degrees up to three digits andnegative sign when required

D Range is from --54_ to 54_ Celsius

D Range is from --66_ to 129_ Fahrenheit

PressureAltitude

D Entry for airport pressure altitude is in feet upto five digits and negative sign when required

D Range is from -1,000 to 14,000

RunwayElevation

D Entry is in feet up to five digits and negativesign when required

D Range is from --1,000 to 16,000 feet

RunwayHeading

D Entry is in degrees or runway numbers

D Range is from 0 to 360, or 00 to 36 runwaynumber

RunwayLength

D Entry is in feet from 2,000 to 16,000

D Entry is in meters from 610 to 4877 m

RunwayThreshold

D Entry is up to 4 digits

D Range is from 0 to 9,999 feet/0 to 3000 m

Slope D Entry is in percent

D Range is from --2.0% to 2.0%

Surface Wind D Entry in degrees and knots

D Range is from 0 to 360 wind direction and 0 to250 wind speed

TakeoffWeight

D Entry in pounds or kilograms depending onconfiguration

D Entry is either four or five digits

D Range is 0000 to 36,100 pounds

D Range is 0000 to 16,374 kilograms


D201110000041REV 1 Jun 2013 5-1

Messages


5. Messages

INTRODUCTION

The flight management system (FMS) generates messages that alertthe pilot to certain conditions. The messages are displayed in thescratchpad and light the message (MSG) light on the control displayunit (CDU). Any entry already in the scratchpad is placed in a stack. TheCLEAR button clears a message and shows the next message or entryfrom the stack. Correcting whatever caused the message clears someof the messages.

Two types of messages are contained in the FMS; alerting andadvisory. Alerting messages are more important. The externalannunciator, located on the pilot’s and copilot’s instrument panel, andthe message annunciator are lit for alerting messages. Advisorymessages only turn on the message annunciator on the CDU.

MESSAGE LIST AND DEFINITION

Table 5--1 contains an alphabetical list of all messages. The list includesthe type of message and a brief explanation of the message.

Table 5--1TOLD Messages

Message Type Definition

ANTI--ICEINIT ABOVE10 C

ALERTING This message is displayed when thetemperature is greater than 10 Cand ANTI--ICE is ON.

CHECKVSPEEDS

ALERTING This message is displayed when notin dual mode and either CONFIRMINIT is pushed or a pilot entry ismade on both the takeoff andlanding initialization pages on theslave (non--master) FMS.

CROSSWINDEXCEEDS21 KTS

ADVISORY This message is displayed when thecrosswind exceeds thedemonstrated value.

EXCEEDS PALTITUDELIMIT

ALERTING This message is displayed when thepressure altitude limit is exceeded.


D201110000041REV 1 Jun 2013

Messages5-2


Table 5--1 (cont)TOLD Messages

Message DefinitionType

EXCEEDSWIND LIMITS

ALERTING This message is displayed when thewind (headwind and tailwind) limitsfor takeoff and landing areexceeded.

FIELDLENGTHLIMITED

ALERTING This message is displayed when thelanding calculations are field lengthlimited.

FLAPSPEED/CONFIG

ALERTING This message is displayed onlanding when either the flaps oranti--ice is out of configuration underthe following conditions: takeoffVSPEEDS have been dropped, theaircraft is within 50 NM of thedestination, and the aircraft is below1,000 feet AGL.

INVALIDENTRY

ADVISORY This message is displayed any timean entry is not in the correct format.

LANDINGCLIMBLIMITED

ALERTING This message is displayed when thelanding calculations are climblimited and the CDU is displayingthe landing initialization or landingdata pages.

LANDINGOUT OFLIMITS

ALERTING This message is displayed anytimethe landing calculation is out oflimits after the initial calculation.

OAT/ISALIMITEXCEEDED

ALERTING This message is displayed when thesensed outside air temperature orISA deviation exceeds the limit.


D201110000041REV 1 Jun 2013 5-3

Messages


Table 5--1 (cont)TOLD Messages

Message DefinitionType

PREV NOTALLOWED

ADVISORY This message is displayed whenselecting PREV on page 1 ofTAKEOFF INIT or LANDING INIT.

RUNWAYSLOPE OUTOF LIMITS

ALERTING This message is displayed anytimethe takeoff calculation is out of limitsafter the initial calculation.

TAKEOFFOUT OFLIMITS

ALERTING This message is displayed anytimethe takeoff calculation is out of limitsafter the initial calculation.

T.O.ENTRIESINHIBITED

ADVISORY This message is displayed anytimean entry is attempted to takeoffinitialization during the takeoff role.


D201110000041REV 1 Jun 2013

Messages5-4


Blank Page


D201110000041REV 3 Nov 2013 A--1

Citation X FMS 6.1 Applicable PARs


Appendix A

Citation X FMS 6.1 ApplicableProgram/Product Action Requests

(PARs)

INTRODUCTION

This section contains program/product action requests (PARs)applicable to theCessnaCitationX FMS6.1. PARsareHoneywell FMSprogram/product action requests detailing operational topics of note.These requests may have been generated by Honeywell or the originalequipment manufacturer (OEM).

The items listed are for pilot--reference and are grouped by area ofoperation. The pilot can correlate the note for each item back to thelisted reference page in the common FMS SW Ver. 6.1 Pilot’s Guide,publication number D200802000002.

The common FMS Pilot’s Guide is used on several aircraft platforms.The following notes may be pertinent to those platforms, however, thislist pertains to the Citation X.

Table A--1 lists applicable PARs for the Cessna Citation X FMS 6.1.

Table A--1November 2013 Citation X FMS SW Ver. 6.1

PAR Response List

PAR Area of Operation

Affected Location in FMZ SeriesFMS SW Ver. 6.1 Pilot’s Guide(Pub. No. D200802000002)

422 Control Display Unit(CDU)

Page 6--203 following Figure 6--226:

NOTE: When defining a holding pattern at awaypoint, the current aircraft altitude isused to determine the leg time anddistance for the hold. The pilot shouldreview the data prior to activating theholding pattern.


D201110000041REV 3 Nov 2013

Citation X FMS 6.1 Applicable PARsA--2


Table A--1 (cont)November 2013 Citation X FMS SW Ver. 6.1

PAR Response List

PAR

Affected Location in FMZ SeriesFMS SW Ver. 6.1 Pilot’s Guide(Pub. No. D200802000002)Area of Operation

545 CDU Page 9--46 following first bullet:

NOTE: An unexpected speed command maybe issued when sequencing a waypointjust prior to a holding fix, when theaircraft is near the holding fix andcruising at a high rate of speed.

1037 CDU Page 6--200 as Note 1 following step5 DETAILS paragraph (PAR 1597from this list is Note 2):

NOTE: When the aircraft entry angle into aholding pattern is approximately70 degrees (the boundary between aPARALLEL entry and a DIRECTentry), the holding pattern entry type onthe HOLDING PATTERN page mayoscillate between PARALLEL andDIRECT when the waypoint issequenced. If this is observed, the pilotshould exit the HOLDING PATTERNpage and then return to the HOLDINGPATTERN page to stop the oscillation.

1056 CDU Page 6--222 as second note underDUAL topic:

NOTE: While in DUAL mode, the performancedata pages (PERF DATA, CLIMB,CRUISE, DESCENT, etc.) on one FMScan display valid data while the otherFMS displays NOT INITIALIZED. Thiscan occur when the performance datahas been initialized and confirmed withvalid data and then the weights arechanged on the onside FMS to valuesexceeding gross weight. If thecross--side FMS is not onPERFORMANCE INIT page 5, thecross--side FMS will display NOTINITIALIZED.


D201110000041REV 3 Nov 2013 A--3




PAR Response List

PAR


1347 CDU Page 6--161 following GPS(X)STATUS 1/2 dashed items:

NOTE: The GPS GRD SPD displayed on theGPS SENSOR STATUS 1/2 Pageshould not be used as a groundspeedreference due to a current anomaly inthe system calculation.

1482 CDU Page 11--13 following first paragraph:

NOTE: For arc--to--fix (AF) and radius--to--fix(RF) legs, the turn direction is notdisplayed on the end of an arc on theACTIVE FLT PLAN page. The aircrafthowever, will turn in the directionspecified in the Navigation database.

1508 CDU Page 6--117 following last paragraph:

NOTE: Selecting a blank line select key on thedatalink ADDRESS CONFIG pagescould result in a LIST FULL scratchpadmessage.

1544 CDU Page 6--260 prior to Figure 6--277:

NOTE: The WIND entry on the CRUISE ALTWIND page will be displayed as zero,instead of the value calculated by thewind model, when the correspondingwaypoint is from the active flight plan.However, this has no effect on ETA,ETE, or fuel predictions.

1282 Lateral Navigation Page 6--205 at end of Step 5:

NOTE: The crosstrack error may be differentbetween FMS1 and FMS2 when exitinga parallel entry holding pattern wherethe actual inbound course and thedefault inbound course differ by morethan 90 degrees.


D201110000041REV 3 Nov 2013




PAR Response List

PAR


1457 Lateral Navigation Page 6--141 following caution note:

NOTE: When the aircraft is exiting an arc turnand the leg following the arc is veryshort, the lateral display of the short legon the MFD may be depicted with asharp kink in the flight plan as the FMSattempts to connect the legs. Thisissue only affects the display of theflight plan; the actual flight path will becorrect.

1495 Lateral Navigation Page 6--148 following Figure 6--169:

NOTE: Loading a VECTORS approach whileon--ground will result in the FAF to besequenced and become the FROMwaypoint once the FMS becomesairborne when the final approachsegment is behind the aircraft.

1597 Lateral Navigation Page 6--200 as Note 2 following step5 DETAILS paragraph (PAR 1037from this list is Note 1):

NOTE: The FMS may not enter the HOLDwhen a teardrop HOLD is inserted intothe flight plan using the slave FMS. Asthe aircraft reaches the hold fix theaircraft may turn toward the hold fixand sequence the waypoint withoutentering the HOLD or the EXIT promptbeing pushed.

1433 Flight Planning

Lateral Navigation

Page 6--141 following caution note:

NOTE: Full circles may be displayed for arclegs whose transitions onto or off of thearc are short or have sharp turns.Guidance is correct and the map willclear after the waypoints have beensequenced.


D201110000041REV 3 Nov 2013 A--5




PAR Response List

PAR



Lateral Navigation

Page 6--218 following first paragraph:

NOTE: The flight director mode may not dropto ROL from LNAV when exiting anORBIT pattern using the slave FMS.

425 CDU

Flight Planning

Page 5--35 following LSK 2R dasheditem:

NOTE: Clearing wind data displayed on oneFMS does not clear the wind datadisplayed on the offside FMS. Winddata must be cleared on both sidesindividually. Manual changes to thewind data are synchronized.

1539 Performance

Flight Planning

CDU

Page 5--52 following fourth paragraph:

NOTE: The temperature compensationfunction is only applied to altitudes upto 15,000 feet MSL. Altitudes above15,000 feet MSL are not temperaturecompensated but are still displayed inreverse video.

752 Flight Planning Page 6--146 following secondparagraph:

NOTE: When en route on a STAR andrepeatedly changing an approachwhich contains a vectors leg, the gapusually displayed for the vectors leg onthe EFIS may be dropped and the lineswill be connected. The leg will still beshown properly on the CDU and thelateral mode will drop as expectedwhen it is sequenced.


D201110000041REV 3 Nov 2013




PAR Response List

PAR


943 Flight Planning Page 5--57 following last paragraph:

NOTE: When making a change that results intemperature compensation to becanceled, the TEMP COMPCANCELLED scratchpad message isonly displayed on the CDU where thechange was made. The cross--sideCDU will also cancel temperaturecompensation but will provide noindication that it did so.

952 Flight Planning Page 6--208 following third paragraphand prior to Figure 6--231:

NOTE: When selecting RESUME HOLD inclose proximity to the holding fix, thepilot may be required to make theselection twice before it is accepted bythe FMS.

1582 Flight Planning Page 6--268 after first paragraphfollowing Figure 6--284:

NOTE: After loading the NAV database, theSLAVE FP CHNG OVERRIDDENscratchpad message may be displayedon both CDUs when the active NAVdatabase is changed from old to newor from new to old.

1709 Flight Planning Page 9--18 following fourth paragraph:

NOTE: When two of the same waypoints arecontained within a flight plan, one beingan en route waypoint and the other anarrival waypoint, inserting the samewaypoint at the first appearance of thewaypoint results in all three waypointsto be combined into one waypoint withthe arrival attribute and speedconstraint missing. If this occurs,restringing the arrival will correct theproblem.


D201110000041REV 3 Nov 2013 A--7




PAR Response List

PAR


1710 Flight Planning Page 9--6 following second paragraphafter discontinuities topic:

NOTE: When an approach is modified afterbeing combined with an arrival, the lastwaypoint of the arrival is removed anda discontinuity is inserted. When thisoccurs, the pilot must restring thearrival and the approach.

1720 Flight Planning Page 5--50 following last paragraphand on page 9--33 following secondparagraph under Path Descent(VPATH) topic:

NOTE: When a flight plan containing twowaypoints, one with an AT constraintand the other with a window constraint,are combined, the common waypointwill maintain the window constraintrather than the AT constraint.

1784 Flight Planning Page 9--5 following caution note:

NOTE: When flying closely spaced waypointsat high airspeeds, a turn arrow may bedepicted rather than a curved pathtransition on the MFD.

1792 Flight Planning Page 6--137 following Figure 6--165:

NOTE: When the runway and approach aremodified after an arrival had beenactivated, the constraints for anywaypoints contained in bothapproaches will retain the values of theinitial approach activated. The pilotmust restring the arrival after activatingthe runway change to get the correctconstraints.


D201110000041REV 3 Nov 2013




PAR Response List

PAR


807 Navigation

Nav--Tuning

Page 10--2 prior to 4L and 4R dasheditem:

NOTE: When an IRS is the only availablenavigation source and is aligned at therunway, an EPU value of 1 should beexpected.

1008 Navigation

Nav--Tuning

Page 8--4 as Note 2:

NOTE: Manual RNP may be canceled on theoffside FMS when all navigationsensors have been disabled except fora single GPS. This only occurs if amanual RNP was entered on theoffside FMS and the aircraft sequencesan approach waypoint. During theapproach, the specified RNP value willautomatically be set.

1046 Navigation

Nav--Tuning

Page 8--5 after second bulleted item:

NOTE: The default RNP value forRemote/Oceanic is set to 2.0 in theFMS software. Per FAA Order 8400.33(Authorization for RNP--4 inOceanic/Remote Area Operations) thedefault should be RNP 4.0. The pilotcan manually overwrite the defaultvalue if desired.

1383 Navigation

Nav--Tuning

Page 8--5 as second note underMissed Approach bulleted item:

NOTE: When flying a VOR approach, the RNPvalue does not change to the defaultvalue when flying a holding pattern atthe IAF. This occurs only when the holdis the first waypoint in the approach.On exiting the hold, or within 2 NM tothe FAF, the correct RNP value will bedisplayed.


D201110000041REV 3 Nov 2013 A--9




PAR Response List

PAR


1463 Navigation

Nav--Tuning

Page 8--8 after third bulleted item:

NOTE: When the PILOT RNP CANCEL NEXTWP scratchpad message is issued, themanual RNP value will be canceled ator before the next waypoint, not onentering terminal airspace.

963 Performance Page 5--43 at bottom of page:

NOTE: Performing a step climb to optimumaltitude with the speed mode selectedas Maximum Endurance instead ofLong Range Cruise or MaximumSpeed could result in the step altitudebeing calculated incorrectly.

1339 Performance Page 9--17 following first dashed item:

NOTE: During a descent, the predicted speedfor the first waypoint predicted to bebelow 10,000 feet is erroneouslypredicted as the PERF INIT descentspeed rather than the SPD/ALT LIMITspeed.

1548 Performance Page 9--8 following third and sixthbullets (after dashed items):

NOTE: When the top--of--climb (TOC) andtop--of--descent (TOD) are calculatedto be less than 1 minute apart, thevertical flight plan and associatedvertical profile display (VPD) may differbetween the master and slave FMSs.This anomaly is cleared when thealtitude preselector is changed and aVFLCH climb is commanded.


D201110000041REV 3 Nov 2013




PAR Response List

PAR


1293 Vertical Guidance

Performance

Page 9--50 following Figure 9--28:

NOTE: A transient display of the verticaldeviation scale may be seen on theslave FMS when a manual speedintervention is added and thenremoved while entering a hold.

1487 Vertical Guidance

Performance

Page 9--37 following fourth dash itemand on page 9--42 after item 3:

NOTE: When sequencing the TOD, thevertical deviation scale on thenon--coupled FMS side may beremoved from the display if the flightplan is not set up with normaldescending path.


Vertical Guidance

Page 9--45 after second bulleted item:

NOTE: When performing an automatictransition to a VFLCH climb, themaster FMS may indicate anerroneous speed command. Deletingthe erroneous speed command willresult in the correct speed command tobe indicated.

1044 Vertical Guidance Page 9--52 following fourth item:

NOTE: When entering the latched speedmode, it is possible for only the masterFMS to latch to a speed. When thisoccurs, the FMS speed becomeslatched to the current aircraft speedand is displayed as the commandedspeed on the master and slave PFDsand the master CDU. The slave CDUdoes not latch to the aircraft speed.


D201110000041REV 3 Nov 2013 A--11




PAR Response List

PAR


1405 Vertical Guidance Page 6--202 following step 9DETAILSparagraph:

NOTE: When approaching a hold fix or duringa hold, the speed target may notchange to the holding speed when theperformance mode is not FULL PERF.

1649 Vertical Guidance Page 6--208 prior to Figure 6--231:

NOTE: When flying a HOLD, a mismatchbetween the master and slave verticaldeviation indicators may be observedwhen RESUME HOLD is performedfollowed immediately by EXIT HOLD.The vertical deviation indicators willsynchronize within 60 seconds.


D201110000041REV 3 Nov 2013



Blank Page


D201110000041REV 3 Nov 2013 Abbrev--1



Acronyms and AbbreviationsAcronyms and abbreviations used in this guide are defined as follows:

TERMS DEFINITION

ACT activeADC air data computerAFM aircraft flight manualAGL above ground levelALD actual landing distanceALT altitudeAOG aircraft--on--groundAPPR approachARP airport reference point

BARO barometricBOW basic operating weight

CAS calibrated airspeedCDU control display unitCOMP compensationCONFIG configuration

DADC digital air data computerDB databaseDEL deleteDEST destinationDEV deviationDIR direct

EFIS electronic flight instrument systemEPU estimated position uncertaintyETA estimated time of arrivalETD estimated time of departureETE estimated time en route

FAA Federal Aviation AdministrationFAF final approach fixFL flight levelFLD fieldFLT flight


D201110000041REV 3 Nov 2013

Acronyms and AbbreviationsAbbrev--2


TERMS DEFINITION

FMS flight management systemFOM figure--of--meritFPL flight plan

GCC Global Customer CareGPS global positioning systemGRAD gradientGSPD groundspeed

IDENT identifierIMC instrument meteorological conditionsinHg inches of mercuryINIT initial,

initializationIRS inertial reference systemISA International Standard Atmosphere

JAA Joint Airworthiness Authorities

kg kilogramKIAS knots indicated airspeedkt, kts, KTS knot/knots

lb, LB pound(s)LDG landingLEN lengthLIM limitLNAV lateral navigationLRC long--range cruiseLSK line select key

m metersMAP missed approach pointMGT managementMSG messageMSL mean sea level

NAV navigationNAVAID navigational aid


D201110000041REV 3 Nov 2013 Abbrev--3



TERMS DEFINITION

NDB navigation databaseNM nautical miles

OAT outside air temperatureOEM original equipment manufacturer

P pressurePERF performancePFD primary flight displayPOS positionPREV previousPROG progress

RAIM receiver autonomous integrity monitorRMA return material authorizationRNP required navigation performanceRW, RWY runway

SAT static air temperatureSEG segmentSID standard instrument departureSPD speedSPEX spares exchangeSTAR standard terminal arrival routeSW software

T.O. takeoffTEMP temperatureTHRESH thresholdTLA throttle lever angleTOC top--of--climb,

Technical Operations CenterTOD top--of--descentTOGA takeoff/go--aroundTOLD takeoff and landingTRANS transition

USB universal serial bus

VAPP VOR final approach speed


D201110000041REV 3 Nov 2013

Acronyms and AbbreviationsAbbrev--4


TERMS DEFINITION

VFLCH vertical flight level changeVNAV vertical navigationVREF reference approach speedVOR very high frequency omni--rangeVPD vertical profile display

WGT weight


D201110000041REV 3 Nov 2013 Index--1

Index


IndexA

Abbreviations, Abbrev--1Acronyms, Abbrev--1Active flight plan, 2-9airway entry, 2-10waypoint entry, 2-10

Airway entry, 2-10Alternate flight plan, 2-51Approach, Minneapolis, MN ILS30L, 2-4

Arrival, 2-41Minneapolis, MN KASPR2, 2-3

B

Barometric set, 4-1

C

Citation X performanceinitialization, 3-5performance data, 3-5performance initialization, 3-5takeoff data, 3-5takeoff initialization, 3-5

Clearing flight plans, 2-52Climb, 2-39Control display unit (CDU) entryformatintroduction, 4-1list of entries and definition, 4-1

Customer support, 1-3Global Customer Care (GCC),1-3

Honeywell aerospace technicalpublications, 1-4

Technical Operations Center(TOC), 1-3

to register your publication(when required), 1-4

D

Departure, Phoenix, AZ EAGUL3,2-2

Departure election,flight plan discontinuities, 2-27

Departure selection, 2-25Descent, 2-41

E

En route, 2-40

F

Flight plan discontinuities, 2-27Fuelflow, 3-5gauge, 3-1management, 3-1quantity, 3-1

G

Global Customer Care (GCC), 1-3

H

Honeywell aerospace technicalpublications, 1-4

Honeywell product support, 1-2

I

Introduction, 1-1customer support, 1-3

Global Customer Care(GCC), 1-3

Honeywell aerospacetechnical publications, 1-4


D201110000041REV 3 Nov 2013

IndexIndex--2


Index (cont)Introduction (cont)customer support (cont)Technical Operations Center(TOC), 1-3to register your publication(when required), 1-4

Honeywell product support, 1-2

L

Landing data, 3-21landing data 1/1, 2-49, 3-21

Landing initialization, 2-45landing data, 3-21landing init 1/3, 2-45, 3-17landing init 2/3, 2-46, 3-18landing init 3/3, 2-48, 3-20runway factor 1/1, 2-47, 3-19

Landing problems, 3-22Landing weight, 4-1

M

Messagesintroduction, 5-1message list and definition, 5-1

Missed approach, 2-50

O

Obstacledistance, 4-1elevation, 4-1

Operational exampleactive flight plan, 2-9

airway entry, 2-10waypoint entry, 2-10

alternate flight plan, 2-51approach, 2-42, 2-45arrival, 2-41

clearing flight plans, 2-52climb, 2-39departure selection, 2-25

flight plan discontinuities,2-27

descent, 2-41en route, 2-40introduction, 2-1KPHX to KMSP flight route, 2-1landing data, 2-49landing initialization, 2-45Minneapolis, MN ILS 30Lapproach, 2-4

Minneapolis, MN KASPR2arrival, 2-3

missed approach, 2-50performance data, 2-22performance initialization, 2-17Phoenix, AZ EAGUL3 departure,2-2

position initialization, 2-7predeparture, 2-5

power--up, 2-6runway position, 2-34takeoff, 2-36takeoff data, 2-32takeoff initialization, 2-28

Outside air temperature, 4-2

P

Performancefield loadable TOLD aircraftdatabase updating, 3-29

introduction, 3-1landing initialization, 3-16

landing data, 3-21performance index, 3-2performance index organization,3-4

performance initialization, 3-5Citation X performanceinitialization, 3-5


D201110000041REV 3 Nov 2013 Index--3

Index


Index (cont)Performance (cont)problems page, 3-22takeoff initialization, 3-9

takeoff data, 3-15TOLD configuration, 3-9

Performance data, 2-22perf data 1/4, 2-22perf data 2/4, 2-23perf data 3/4, 2-24perf data 4/4, 2-24

Performance initialization, 2-17Citation X performanceinitialization, 3-5

current groundspeed/fuel flow,3-5

full performance, 3-5performance init 1/5, 2-18performance init 2/5, 2-19performance init 4/5, 2-21performance init--lb 3/5, 2-20performance init--lb 5/5, 2-22pilot speed/fuel flow, 3-5

Position initialization, 2-7POSITION INIT 1/1 page, 2-7

Power--upNAV IDENT 1/1, 2-6

Predeparture, 2-5power--up, 2-6

Pressure altitude, 4-2Problems pagelanding, 3-22landing problems 1/1, 3-26takeoff, 3-22takeoff problems 1/1, 3-22

R

RAMPX waypoint, 2-7Runwayelevation, 4-2heading, 4-2length, 4-2

threshold, 4-2Runway condition, 1-1Runway position, 2-34position init 1/1, 2-35threshold position update, 2-35

S

Slope, 4-2Step climb increment, 2-20

T

Tail number, 2-18Takeoff, 2-36progress 1/3, 2-37progress 2/3, 2-38waypoint sequencing, 2-37

Takeoff data, 2-32, 3-15takeoff data 1/2, 2-33takeoff data 2/2, 2-33

Takeoff initialization, 2-28anti--ice, 3-9baro setting, 3-9elevation, 3-9flaps, 3-9pressure altitude, 3-9takeoff data, 3-15takeoff init 1/4, 2-28takeoff init 2/4, 2-29takeoff init 3/4, 2-30takeoff init 4/4, 2-31temperature, 3-9

Takeoff problems, 3-22Takeoff weight, 4-2Technical Operations Center(TOC), 1-3

To register your publication (whenrequired), 1-4

TOLD configuration, 3-9


D201110000041REV 3 Nov 2013

IndexIndex--4


Index (cont)

W

Waypoint entry, 2-10Wind, surface, 4-2

Documents

ddtk.pdf