1 / 5

CFCG

CFCG. ICAO Communication Failure Coordinating Group. IPACG/40. Keith Dutch, AJV-84. 8-12 September 2014. CFCG. History Meetings CFCG/2 Outcome. CFCG History.

ian-stanley
Télécharger la présentation

CFCG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CFCG ICAO Communication Failure Coordinating Group IPACG/40 Keith Dutch, AJV-84 8-12 September 2014

  2. CFCG History Meetings CFCG/2 Outcome

  3. CFCG History • ICAO communication failure provisions revised six times since the Rules of the Air and Air Traffic Control (RAC) introduced in 1945 • In 2011, two ICAO regional offices offered proposals relating to communication failure provisions • EUR proposal merges flight crew Standards from Annex 10 Vol. II into Annex 2 and adds new provisions for an aircraft flying IFR that chooses to continue VFR • CPWG proposed that the aircraft maintain the last ATC assigned speed and level, without regard for changes filed in the flight plan, until exiting the airspace defined in the SUPPS proposal.

  4. CFCG Meetings • CFCG/1 October 2012 at ICAO HQ in Montréal • No agreements reached between conflicting “camps” • NAM and NAT affirm that safety and integrity guaranteed only if aircraft flies by last ATC clearance • EUR expects aircraft will change speed and altitude(s) in accordance with Current Flight Plan (CPL) Item 15. (Route) • CFCG/2 February 2014 at ICAO HQ • Proposed common procedure, without variation due to oceanic/remote or continental airspace • Simple, unambiguous for a rare single aircraft event • Reached consensus

  5. CFCG/2 Outcome • CFCG/2 Proposed • Aircrew must attempt to use all communication methods (“… all available means …” includes, inter alia, data link, satellite voice and mobile phones.) • Maintain last assigned speed, level, and routing for 20 minutes after squawking 7600 • Add RCF procedures to SIDs/STARs • “Filed Flight Plan” (FPL) revised to include mods prior to departure • IFR flights continue to destination according to last ATC clearance • ATC separates RCF aircraft from other aircraft, based on above • Squawk 7601 if pilot goes VFR to suitable airport • Rationales are being developed for proposed changes • Following rationales and CFCG satisfaction, submitted to • Air Traffic Management Operations Panel • Flight Operations Panel

More Related