Home Cart Quotation About-Us
www.ChineseStandard.net
SEARCH

MHT4029.3-2020 English PDF

Q: How long will the true-PDF of English version of MHT4029.3-2020 be delivered?

Upon your order, we will start to translate MHT4029.3-2020_English as soon as possible, and keep you informed of the progress. The lead time is typically 4 ~ 6 working days. The lengthier the document the longer the lead time.

Q: Can I share the purchased PDF of MHT4029.3-2020_English with my colleagues?

Yes. The purchased PDF of MHT4029.3-2020_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Q: Does the price include tax/VAT?

Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries). Avoidance of Double Taxation Agreements (DTAs) between Singapore and 100+ Countries: https://www.iras.gov.sg/taxes/international-tax

Q: Do you accept my currency other than USD?

Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.

Q: Should I purchase the latest version MHT4029.3-2020?

Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version MHT4029.3-2020 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.

US$1149.00 · In stock
Delivery: <= 6 days. True-PDF full-copy in English will be manually translated and delivered via email.
MHT4029.3-2020: (Civil Aviation Air Traffic Control Automation System - Part 3: Flight Data Exchange)
Status: Valid

MHT4029.3: Historical versions

Standard ID	USD	BUY PDF	Lead-Days	Standard Title (Description)	Status
MH/T 4029.3-2020	1149	Add to Cart	6 days	(Civil Aviation Air Traffic Control Automation System - Part 3: Flight Data Exchange)	Valid
MH/T 4029.3-2015	RFQ	ASK	5 days	Civil aviation air traffic control automation system. Part 3: Flight data exchange	Obsolete

Similar standards

GB/T 23420 MH/T 4029.2 MH/T 4042 MH/T 4028.1

Basic data

Standard ID: MH/T 4029.3-2020 (MH/T4029.3-2020)
Description (Translated English): (Civil Aviation Air Traffic Control Automation System - Part 3: Flight Data Exchange)
Sector / Industry: Civil Aviation Industry Standard (Recommended)
Classification of Chinese Standard: V54
Classification of International Standard: 03.220.50
Word Count Estimation: 46,464
Date of Issue: 2020-07-20
Date of Implementation: 2020-10-01
Older Standard (superseded by this standard): MH/T 4029.3-2015
Issuing agency(ies): Civil Aviation Administration of China

MHT4029.3-2020: (Civil Aviation Air Traffic Control Automation System - Part 3: Flight Data Exchange)

---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Civil aviation air traffic control automation system-Part 3.Flight data exchange ICS 03.220.50 V 54 MH Civil Aviation Industry Standard of the People's Republic of China Replace MH/T 4029.3-2015 Civil Aviation Air Traffic Control Automation System Part 3.Flight Data Exchange 2020-07 -20 released 2020-10 -01 Implementation Issued by Civil Aviation Administration of China

Foreword...II 1 Scope...1 2 Terms, definitions and abbreviations...1 3 General Data of Data Exchange Message...4 4 Data exchange message structure...7 5 Basic flight data fields...10 6 Basic Flight Data Exchange Message Format...18 7 Data Fields of Main and Standby Air Traffic Control Automation System...23 8 Data exchange message format of main and standby air traffic control automation system...29 9 Fields of flight data between control units...33 10 Flight data exchange message format between control units...33 References...40

Foreword

MH/T 4029 "Civil Aviation Air Traffic Control Automation System" has released the following parts. --Part 1.Configuration; --Part 2.Technical requirements; --Part 3.Flight data exchange. This part is part 3 of MH/T 4029. This section was drafted in accordance with the rules given in GB/T 1.1-2009. This part replaces MH/T 4029-2015 "Civil Aviation Air Traffic Control Automation System Part 3.Flight Data Exchange", and Compared with MH/T 4029-2015, the main technical changes except for editorial changes are as follows. -Modified the term "flight data coordination and exchange messages between control units" and its definitions (see 2.1.3,.2015 version 2.1.3); - Added the term "revised sea pressure update information" and its definition (see 2.1.11); - Modify the abbreviation "QFE surface pressure; --Modified the abbreviation "2.2 of QNH revised sea level pressure annual edition); - Modified the 15-character longitude and latitude expression method (see 3.4.3, 3.4.3 of the.2015 edition); - Modified the 11-character longitude and latitude expression method (see 3.4.4, 3.4.4 of the.2015 edition); -Modified the 7-character longitude and latitude expression method (see 3.4.5, 3.4.5 of the.2015 edition); - Deleted the basic data items in Table 8 -Added the basic data items in Table 8 (see Table 8); - Deleted in the main field of Table 9 basic flight data (see the.2015 edition Table 9); ---Added the requirement to modify sea pressure information (see 8.7); --Modified the requirements for flight plan coordination data (see 10.2.1, 10.2.1 in the.2015 edition). This part is proposed and explained by the Air Traffic Control Industry Management Office of the Civil Aviation Administration of China. This part is under the jurisdiction of the China Academy of Civil Aviation Science and Technology. Drafting organizations of this section. Air Traffic Management Bureau of Civil Aviation Administration of China, Second Research Institute of Civil Aviation Administration of China. The main drafters of this section. Huo Zhenfei, Shi Jianhua, Cheng Yansong, Hou Changbo, Zhang Jun, Xi Yuhua, Jiang Siwei, Wang Yu, Li Jing. The previous releases of MH/T 4029.3 are as follows. MH/T 4029.3-2015. Civil Aviation Air Traffic Control Automation System Part 3.Flight Data Exchange

1 Scope

This part of MH/T 4029 specifies the civil aviation air traffic control automation system (hereinafter referred to as the air traffic control automation system) and related The protocol, message type and data format used to transmit flight data between systems. This part is applicable to the planning, design, manufacturing, construction, inspection and use of various air traffic control automation systems. 2 Terms, definitions and abbreviations The following terms and definitions apply to this document. 2.1 Terms and definitions 2.1.1 Basic Flight Data Exchange Message Messages used for basic flight data exchange between air traffic control automation systems and related systems. Note. The message type starts with the letter "I". 2.1.2 Data exchange message of main and standby air traffic control automation system Messages used for data exchange between main and standby air traffic control automation systems. Note. The message type starts with the letter "B". 2.1.3 Flight data coordination and exchange messages between control units Messages used for the coordinated exchange of flight data between different control units. Note. The message type starts with the letter "C". 2.1.4 Individual flight plan A message used to notify the flight plan changes (additions, modifications). 2.1.5 Individual flight plan deletion Used to notify the deletion of the flight plan. 2.1.6 Individual flight plan cancellation data Used to notify the cancellation of the flight plan. 2.1.7 Ssr code assignment message Used to notify the secondary code allocation or recovery message of the flight plan. 2.1.8 Sector assignment message It is used to notify the news of the allocation of seat sectors in the air traffic control automation system. 2.1.9 Airport runway status message Used to notify the current status of the airport runway in the air traffic control automation system. 2.1.10 Restricted airspace status message Used to notify a restricted airspace in the air traffic control automation system (including danger zone, air restricted zone, military airspace, gun shooting point, NTZ zone Etc.) Current status messages. 2.1.11 CWP setting message Used to notify the current setting of a physical seat in the air traffic control automation system. 2.1.12 Revise the sea pressure update information QNH setting message Used to notify the air traffic control automation system to modify the news of sea pressure changes. 2.1.13 Coordination flight plan It is used to notify the information of flight plan changes (addition, modification) between control units. 2.1.14 Handover request message It is used as a message when the flight plan between control units requests the transfer. 2.1.15 Handover response message It is used to respond to the transfer of flight plans between control units. 2.1.16 Flight plan transfer logic confirmation data logic affirm message It is used for logical confirmation messages when the flight plan requests and the flight plan respond to the handover between control units. 2.2 Abbreviations The following abbreviations apply to this document.

3 General data of data exchange message

3.1 Time and date data 3.1.1 The time data of flight data exchange messages should use UTC, accurate to the minute or second. Time data accurate to the minute It should be represented by four consecutive digits, in the order of hour and minute, with two digits indicating hour and minute respectively. Time data applications accurate to the second Continuing the six-digit representation, in the order of hour, minute, and second, use two digits to represent hour, minute, and second respectively. Example 1.1030 means 10.30 UTC. Example 2.103010 means 10.30.10 in UTC. 3.1.2 The date data of flight data exchange messages shall be represented by consecutive eight digits, in the order of year, month and day, using two digits respectively Represents the month and day, and uses four digits to represent the year. Example..20110812 represents August 12,.2011 in UTC. 3.1.3 The date and time data of the flight data exchange message is accurate to the minute, and should be represented by consecutive twelve digits, in terms of year, month, day, hour, In the order of minutes, use two digits to indicate month, day, hour, and minute, and four digits to indicate year. Example..201108121030 means 10.30 UTC on August 12,.2011. 3.1.4 The date and time data of the flight data exchange message is accurate to the second, and should be represented by fourteen consecutive digits, in terms of year, month, day, hour, In the order of minutes and seconds, use two digits to represent month, day, hour, minute, and second, and four digits to represent year. Example..20110812103010 represents 10.30.10 on August 12,.2011 in UTC. 3.2 Speed data The speed data of the flight data exchange message uses the expression in Table 1. 3.3 Level data 3.3.1 The barometric altimeter is set when the sea level barometric pressure (QNH) altimeter is corrected to the positive value, the altimeter indicates "Altitude" (Altitude). 3.3.2 When the air pressure altimeter is set to the positive value of the surface air pressure (QFE), the altimeter indicates "high" above the reference surface of the surface air pressure (QFE) (Height). 3.3.3 When the barometric altimeter is set to 1 013.2 hPa, it can be used to indicate the flight altitude. 3.3.4 The height level data uses the presentation method in Table 2. 3.4 Location and route data 3.4.1 Two to seven characters shall be used to indicate the air traffic service route code to be flown. 3.4.2 Two to five characters shall be used to indicate the code assigned to a certain point on the route. 3.4.3 When 15 characters are used to express the latitude and longitude, the expression in Table 3 shall be used. 3.4.4 When using 11 characters to express the latitude and longitude, use the expression in Table 4. 3.4.5 When seven characters are used to express the latitude and longitude, the expression in Table 5 shall be used. 3.4.6 Use important points to locate, use two or five letters to represent the coding code of an important point, followed by six numbers. First three digits The word indicates the magnetic azimuth relative to the point, and the last three digits indicate the number of nautical miles from the point. In order to achieve the required number of bits, if necessary, the data Add "0" before it to make up the digits. Example. 40 n mile from the omnidirectional beacon station "VYK", the point with a magnetic bearing of 180° is indicated by "VYK180040". 3.5 Definition of plan status The life cycle of the flight plan includes the states listed in Table 6 or equivalent states. Table 6 is the abbreviated correspondence table of flight plan states and states. Note. The activation status is a collective term for non-control, first handover, control, and handover status.

4 Data exchange message structure

4.1 Data items and data fields 4.1.2 Data items 4.1.2.1 Refer to Table 7 for constant data items. 4.2 The composition of data exchange messages 4.2.1 The content of a data exchange message shall consist of a number of specified data fields, and each field shall consist of a set of sequentially arranged data items or numbers. According to the field structure. 4.2.2 All data fields start with the character "START_OF_FIELD", followed by the name of the field and its corresponding data item or number ......

Image

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of MHT4029.3-2020_English be delivered?

Answer: Upon your order, we will start to translate MHT4029.3-2020_English as soon as possible, and keep you informed of the progress. The lead time is typically 4 ~ 6 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of MHT4029.3-2020_English with my colleagues?

Answer: Yes. The purchased PDF of MHT4029.3-2020_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to Sales@ChineseStandard.net. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.

Question 5: Should I purchase the latest version MHT4029.3-2020?

Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version MHT4029.3-2020 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.