Home

Results 91 - 100 of 99,628 for Flight Terminal. Search took 8.615 seconds.  
Sort by date/Sort by relevance
This may include:  Data and Information Management  Static Data Output  Dynamic Data Output  Additional Products,  Pre- and Post-Flight Information, and  ATS Reporting Office (ARO). (...) The competency unit for dynamic data output include competencies related to NOTAM, Checklist of Valid NOTAM, SNOWTAM, and ASHTAM. Pre and Post Flight Information The competencies addresses pre-flight and post-flight information provided by Aerodrome AIS Units as outlined in Annex 15 and other related documents. Pre- and post-flight information is stated in Annex 15 as one of the AIS functions; however, it has been separated because it is often executed by ARO.
Language:English
Score: 1244592.1 - https://www.icao.int/NACC/Docu...AIS-AIMTrainingDevelopment.pdf
Data Source: un
The participants are authorized to arrive in Bangkok one day in advance prior to the Meeting date and depart one day after the Meeting has finished, depending on the availability of flights. 11. ESCAP will arrange your flight ticket through American Express Travel Agency. (...) Daily Subsistence Allowance and Terminal Expense). VIII. DAILY SUBSISTENCE ALLOWANCE AND TERMINAL EXPENSES 20. (...) Participants are responsible for booking their own accommodation and are requested to directly contact their preferred hotel at least 10 working days in advance to provide the participant’s full name, date and time of check-in and check-out, flight numbers and contact details. 27. The information below is provided for the convenience of the participants.
Language:English
Score: 1244504.9 - https://sdgs.un.org/sites/defa...ants_STI_for_SDGs_20190125.pdf
Data Source: un
Automation Benefits per RTCA 14 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Benefits (Continued) • Near Term Regional Automation activities – Cuba has upgraded their legacy ATC system and is looking to transition to the Galaxy System in the 2019-20 timeframe and up-level the NAM ICD interface to Class 2 – Cuba plans to upgrade their NAM ICD Class 1 interface with COCESNA to Class 2 when the INDRA software is available – Jamaica is operational with their Thales TOPSKY system and will be coordinating with both Cuba and COCESNA for implementing NAM ICD interfaces in 2019-2020 – Santo Domingo ACC is currently testing Class 1 with Miami ARTCC via the FAA Technical Center with very positive results prompting optimism the interface can be operational in 2019. 15 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Interface Testing Configuration 16 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Automated Handoff 17 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Automated Handoff – Class 3 • NAM ICD Automated Handoff for the international interfaces is based on the architecture and messaging used domestically in the U.S. and is termed NAM ICD Class 3 • Domestically the FAA has used automated handoff operationally for over 30 years – En Route to En Route – En Route to TerminalTerminal to Terminal • The Handoff capability advances the “voiceless” computer-human transfer of control interface technology enhancing automated data exchange 18 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Cross Border Handoffs Initially includes Canada and the US between CAATS and ERAM 19 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting 2019 Automation Infrastructure ERAM Enhancements 2 Cross Border Handoffs • Automated ‘voiceless’ transfer of control between U.S. and Canada helps shift the controller’s workload from manually intensive coordination tasks and focus on job-related tasks • Performance Enabler – 24 X 7 Handoff capability provides controller benefits to existing automated data exchange between countries • Preserves the five miles cross border separation standard currently used between U.S. and Canada 20 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting NAM ICD Message Classes Overview • Class 1 Capabilities – Active flight plans for IFR Flights (via CPL) – Proposed flight plans for IFR flights (via FPL) – where agreed between ANSPs – Logic Accept Message (LAM) • Class 2 Capabilities – Filed flight plans for IFR flights (via FPL and EST) – Modifications to CPL/FPLs that were activated by an EST (via MOD) – Modification of an FPL (via CHG) – Cancellation of CPL/FPLs (via CNL) – Logical Reject Message (LRM) • Class 3 Capabilities – Handoff – Radar Handoff (via RTI, RTU, RTA, RLA) – Point Outs (via POI, POA, POJ) – System Messages Application Status Message (new NAM message in Version E - IRQ, IRS ,TRQ ,TRS 21 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Handoff Developmental Interest Items • NAM Telecommunication - Direct Connectivity Required – Due to real time handoff messaging per NAM ICD • ICD Messages should be software selectable to maintain flexibility with adjacent ANSPs • First Order Dependency of Interface Messages – CPL Success Required/ FPL-EST Success Required then Handoff Sequence RTI – RLA – RTU - RTA 22 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting NAM ICD Communications Extract 23 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Cross Border Communication • Upgrade current AFTN to Internet Protocol (IP) and AMHS service – Direct IP service through NADIN MSN Replacement required • Load balancer is scheduled to extend the IP support for the ERAM – CAATS interfaces to NAV CANADA and SENEAM interfaces within the near term; testing is being planned for 2019 and implementing existing Class I and II messages using the new communications infrastructure to include the new system messages will be deployed 2019-2020 • MEVA III is being looked at to support enhanced capabilities between the U.S. and NACC partners for future interface support 24 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Communications Interface Control Document and Interface Requirements Document • Interface Requirements Document (IRD) NAS-IR-82422100 was prepared in accordance with FAA-STD-025f. (...) “voiceless transfer of control “ in the automation transaction • Examples of some boundary agreement changes will include: – Field 07(c) Implementation in RTI, RTU, and POI Messages • If the track for the flight does not have an established beacon code, RTI and POI messages will not be sent. • If the beacon code for a flight in handoff becomes dis-established, RTU messages will not be sent. • RTU messages will resume if the beacon code becomes established while the flight is in handoff 30 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Examples of some boundary agreement changes will include (cont) • Field 32 Implementation in RTI, RTU, and POI Messages – Field 32, including all subfields, is included in RTI, RTU, and POI messages – If the track for the flight being handed off or pointed out does not have an established ground speed, Field 32(c) will be set to N9999. – If the track for the flight being handed off or pointed out does not have an established heading, Field 32(d) will be set to 99999. – If the track for the flight does not have an established reported altitude, RTI and POI messages will not be sent. – If the reported altitude for a flight in handoff becomes dis-established, RTU messages will not be sent. RTU messages will resume if the reported altitude becomes established while the flight is in handoff. 31 Federal Aviation Administration Federal Aviation Administration Automation Interface and Radar Handoff Update ICAO NACC AIDC/NAM ICD Meeting Examples of some boundary agreement changes • HAND-OFF Related Messages – “Not Established” Values in Handoff/Point Out Messages – The material relating to “Not Established” Values in Handoff/Point Out Message may be added to the Boundary Agreement specific default values to be used in certain cases.
Language:English
Score: 1243670 - https://www.icao.int/NACC/Docu.../AIDCNAM/AIDCNAMICD-P04eng.pdf
Data Source: un
KPA/Access: Percentage of requested flight level versus cleared flight level  4. KPA/Access: Number of access denials due to equipment failure 5.  (...) Kilograms of fuel saved per flight  2. Average ATFM delay per flight at the international aerodrome  3.  (...) Number of changes approved to the flight plan 3. Number of  alternatives granted 7.  
Language:English
Score: 1241814.3 - https://www.icao.int/NACC/Docu...3ASBUWORKSHOP/ASBU2013WP13.pdf
Data Source: un
Microsoft Word - APIRG 17 WP 7 Appendix I-5 PBN Imp Tools - Approach Phase Action Plan- Mid Term APIRG 17 WP7 APPENDIX I-5 PBN IMPLEMENTATION TOOLS _________________ (State) NATIONAL PERFORMANCE OBJECTIVES AND ACTION PLAN OPTIMIZATION OF THE ATS ROUTE STRUCTURE IN TERMINAL AIRSPACE PERIOD: Mid Term (2013-2016) APPLICATION: Approach Phase Benefits Environment: Efficiency : Strategy PROCESS TASKS INPUT SOURCE OUTPUT TARGET DATE ACTION PERSON/GROUP STATUS Preliminary • Review AFI PBN Implementation Plan Key Targets (Terminal- Approach) AFI PBN Implementation Plan Mid Term: 2013-2016 [Ch. 20-24] • Review State PBN Implementation Plan Key Targets (Terminal Approach) State PBN Implementation Plan Mid Term: 2013-2016 [Ch. 5.2.2-5.2.3] APIRG 17 WP7 APPENDIX I-5 PROCESS TASKS INPUT SOURCE OUTPUT TARGET DATE ACTION PERSON/GROUP STATUS Terminal Applications Implementation Process 1 Determine Requirements Step 1- Formulate airspace concept PBN Manual, Vol. 1B Ch. (...) B 4.3.4 Step 5- Implementation decision PBN Manual, Vol. 1B Ch. B 4.3.5 Step 6- Flight inspection and flight validation PBN Manual, Vol. 1B Ch.
Language:English
Score: 1240902.7 - https://www.icao.int/WACAF/Doc...IRG/APIRG17/Docs/wp7_appi5.pdf
Data Source: un
Microsoft Word - APIRG 17 WP 7 Appendix I-6 PBN Imp Tools - Approach Phase Action Plan - Long Term APIRG 17 WP7 APPENDIX I-6 PBN IMPLEMENTATION TOOLS _________________ (State) NATIONAL PERFORMANCE OBJECTIVES AND ACTION PLAN OPTIMIZATION OF THE ATS ROUTE STRUCTURE IN TERMINAL AIRSPACE PERIOD: Long Term (2016 +) APPLICATION: Approach Phase Benefits Environment: Efficiency : Strategy PROCESS TASKS INPUT SOURCE OUTPUT TARGET DATE ACTION PERSON/GROUP STATUS Preliminary • Review AFI PBN Implementation Plan Key Targets (Terminal-Approach) AFI PBN Implementation Plan Long Term: 2016 + [Ch. 25-26] • Review State PBN Implementation Plan Key Targets (Terminal Approach) State PBN Implementation Plan Long Term: 2016 + [Ch. 5.3] APIRG 17 WP7 APPENDIX I-6 PROCESS TASKS INPUT SOURCE OUTPUT TARGET DATE ACTION PERSON/GROUP STATUS Terminal Applications Implementation Process 1 Determine Requirements Step 1- Formulate airspace concept PBN Manual, Vol. 1B Ch. (...) B 4.3.4 Step 5- Implementation decision PBN Manual, Vol. 1B Ch. B 4.3.5 Step 6- Flight inspection and flight validation PBN Manual, Vol. 1B Ch.
Language:English
Score: 1240902.7 - https://www.icao.int/WACAF/Doc...IRG/APIRG17/Docs/wp7_appi6.pdf
Data Source: un
Microsoft Word - APIRG 17 Wp 7 Appendix I-4 PBN Imp Tools - Approach Phase Action Plan - Near Term APIRG 17 WP7 APPENDIX I-4 PBN IMPLEMENTATION TOOLS _________________ (State) NATIONAL PERFORMANCE OBJECTIVES AND ACTION PLAN OPTIMIZATION OF THE ATS ROUTE STRUCTURE IN TERMINAL AIRSPACE PERIOD: Near Term (2008-2012) APPLICATION: Approach Phase Benefits Environment: Efficiency : Strategy PROCESS TASKS INPUT SOURCE OUTPUT TARGET DATE ACTION PERSON/GROUP STATUS Preliminary • Review AFI PBN Implementation Plan Key Targets (Terminal- Approach) AFI PBN Implementation Plan Near Term: 2008-2012 [Ch. 10-14] • Review State PBN Implementation Plan Key Targets (Terminal-Approach) State PBN Implementation Plan Near Term: 2008-2012 [Ch. 5.1.2-5.1.3] APIRG 17 WP7 APPENDIX I-4 PROCESS TASKS INPUT SOURCE OUTPUT TARGET DATE ACTION PERSON/GROUP STATUS Terminal Applications Implementation Process 1 Determine Requirements Step 1- Formulate airspace concept PBN Manual, Vol. 1B Ch. (...) B 4.3.4 Step 5- Implementation decision PBN Manual, Vol. 1B Ch. B 4.3.5 Step 6- Flight inspection and flight validation PBN Manual, Vol. 1B Ch.
Language:English
Score: 1240902.7 - https://www.icao.int/WACAF/Doc...IRG/APIRG17/Docs/wp7_appi4.pdf
Data Source: un
He is participating in ICAO Instrument Flight Procedure Panel (IFPP) meetings as advisor to the French member.He was instructor for previous ICAO PBN course in India, Hong Kong, Middle-East region and Africa. (...) Terminal objective 1: Conditions of performance Given maps and other documents containing validated data, Expected Behaviour The trainee will design a Basic-RNP 1 or RNAV 1 SID procedure based on use of GNSS sensor Standard In accordance with PANS OPS, Doc 8168 Terminal objective 2: Conditions of performance Given maps and other documents containing validated data, Expected Behaviour The trainee will design a Basic-RNP 1 or RNAV 1 STAR procedure based on use of GNSS sensor Standard In accordance with PANS OPS, Doc 8168 Terminal objective 3: Conditions of performance Given maps and other documents containing validated data, Expected Behaviour The trainee will design an RNP Approach procedure (APV Baro- VNAV), based on RNP APCH operations Standard In accordance with PANS OPS, Doc 8168 Terminal objective 4: Conditions of performance Given maps and other documents containing validated data, Expected Behaviour The trainee will design an RNP approach procedure (NPA), based on RNP APCH operations Standard In accordance with PANS OPS, Doc 8168 Terminal objective 5: Conditions of performance Given completed procedure design with all associated documents and data Expected Behaviour The trainee will document a Basic-RNP 1 or RNAV-1 SID and STAR, an RNP approach procedure (NPA), and an RNP approach procedure (APV Baro-VNAV), for validation, publication and traceability Standard Accurately, in a reasonable time, and in accordance with PANS OPS, Doc 8168, Annex 4, Annex 15, Quality Assurance Manual for Flight Procedure Design and other guidance PBN Course 3 PARTICIPANTS People involved in procedure design or with serious background in procedure design. (...)  Performance – notion of accuracy , precision , continuity , availability GNSS concept:  Aircraft based augmentation system (ABAS)  Satellite based augmentation system (SBAS) in a PBN context  Ground based augmentation system (GBAS) in a PBN context Quality assurance (Quality Assurance Manual for Flight Procedure Design)  Document and store procedure for traceability  Data origination  Procedure design process Procedure design criteria (Pans-Ops, Volume II, Part III, Sections 1, 2):  Underlying criteria  General criteria such as o Minimum length of segments o Turn protection o T and Y concept o TAA Procedure construction (Pans-Ops, Volume II, Part III, Section 3 and proposed amendments)  Departure criteria applicable for Basic-RNP 1 and RNAV 1 /2  Standard arrival for Basic-RNP 1 and RNAV 1/2  Approach procedure for RNP APCH operations  APV baroVNAV procedure  Document procedure for validation and publication (Pans-Ops, Volume II, Part III, Section 5)  Charting and coding PBN Course 5 MEANS  Theoretical lectures : Presentation and explanation of the rules and principles described in PANS OPS, Doc 8168-OPS/611  Laboratory exercises Lectures are followed by practical exercises, scheduled on a daily basis, that illustrate the elementary application of criteria in a simplified environment, in order to reinforce theoretical input.  Comprehensive On-the-Job Training (OJT) Project: Part of the second week is devoted to an OJT project.
Language:English
Score: 1240644.6 - https://www.icao.int/safety/pb...N%20PD%20Course%20syllabus.pdf
Data Source: un
This method can apply to the taxi phase or any flight phase as a first approximation. Vertical Inefficiency Measured by level flight segments on departure or approach as well as non-optimal cruise altitudes. (...) Although ANSPs attempt to minimise deviation from the optimum point-to-point flight trajectory at optimum speed and altitude, there are good reasons to do so, such as: — Maintaining safe separation from other aircraft and airspace users, — Absorption of necessary delay when airborne demand exceeds capacity, — Noise abatement procedures in terminal manoeuvring areas (TMAs), — Existence of military and other use airspace, — Weather, including wind direction in TMA operations, — Unplanned activities including medical priority flights, VIP aircraft and in-flight emergencies. (...) Attachment 1 provided a comprehensive guide for estimating ATM efficiency pools by phase of flight. NATS has also developed, with peer review from the M&M group and others in the aviation industry, a metric that seeks to reflect the vertical and horizontal inefficiencies in flights.
Language:English
Score: 1240620.1 - https://www.icao.int/NACC/Docu...%20and%20Fuel%20Efficiency.pdf
Data Source: un
This requires the ATM system to manage each flight in four dimensions (4D), the fourth being time. (...) This requires an ATM system that can manage each flight in four dimensions (4D), the fourth being time. (...) RNAV 1-based standard instrument departures (SIDs) are part of Canada’s latest developments in its busiest domestic flight corridor between Toronto and Montreal. Basic-RNP 1 has been developed primarily for application in non-radar, low-density terminal airspace.
Language:English
Score: 1239749 - https://www.icao.int/Meetings/...Ps/ANConf.12.IP.003.1.1.en.pdf
Data Source: un