New ICAO requirements on aircraft tracking came into force on Nov 8. Large aircraft (over MTOW 45,500kg and with more than 19 seats) must now track their position every 15 minutes – down from the previously required 60 minutes. The tracking needs to take place in all regions where the local ATS gets position information at greater than 15 minute intervals. If you want to get into it, you can find it in ICAO SARPS, Annex 6,  Part I,  Section 3.5.

This requirement is part of ICAO’s “Global Tracking Initiative”, which came about shortly after the disappearance of Malaysia Airlines flight MH370 in March 2014.

When to track?

If your aircraft is outside range of radar, oceanic waters, remote areas, (anywhere that the ATS doesn’t get a position report in less than 15 minute intervals) you can count on needing to obtain and record your own position reports every 15 minutes (or less).

Where are these areas? ICAO is keeping a database to show where you’re going to need to make your own 15 minute records (it’s not the best tool at the moment):

click to open tool on ICAO site

How to track?

The important part of this: it must all be done automatically. You can’t just set a timer and manually record a position report. ICAO doesn’t have a preferred method for this, just as long as it’s automatic (use your ADS-B, GPS tracker, or a tracking service). It was important that ICAO keep this particular requirement in line with equipment and capabilities currently available.

Who’s watching?

ICAO has told us that although the new requirement is now in place, currently there is no requirement to share the data – unless it’s required for an incident.

Also, it is still yet to be seen if/how specific authorities will add this requirement into AIPs. For example, Canada has stated the below, but have yet to add any requirement into the Canadian Aviation Regulations:

Canadian air operators are reminded that they are subject to the laws and regulations of foreign jurisdictions and their respective civil aviation authorities (CAA) when abroad. Effective November 8, 2018, they may be subject to regulatory action by a CAA if they do not comply with ICAO GADSS SARPs requirements. CASA 09-2018

Will this be part of SAFA ramp checks?

No. We asked SAFA this very question, and here’s what they told us:

“For the time being we do not have any intention to request of ramp inspectors to perform an inspection of this new requirement.”

The future?

In January 2021, there will be a further requirement to tracking, called “Autonomous Distress Tracking”, which will require automatic position reports every minute when in a distress situation. This requirement will likely depend on new equipment, or depend on expansion of Space Based ADS-B.

ICAO is also populating a “Global Operational Directory” to help communication between OCCs and ANSPs. It’s not operational yet, but this will help when ANSPs and OCCs need to communicate. It’s free to participate, as long as OCCs share their information. More information for that is here.

For more reading of all the ICAO updates on Global Tracking Initiatives, head here.

As WSSL/Seletar prepares to open its new $80 million terminal on Nov 19, the authorities have announced that WSSL is now a “schedules facilitated” airport.

Don’t panic – at least, not yet. This basically just means that because demand is now getting close to the airport’s capacity, all airline and charter flights must confirm their schedules with the airport in advance  – BA/GA flights don’t need to do this.

It does not mean that the airport has become slot coordinated, although that might happen at some point in the future if congestion continues to be a problem.

As for the new terminal, it looks like it will be a decent improvement on the old one…

The new facility – six times bigger than the old terminal – will be split in two, with one large section for airline flights, and another separate section dedicated for GA/BA.

Here’s a video of what the new terminal looks like!

The idea is to free up capacity at WSSS/Singapore by moving all scheduled turboprop flights to WSSL/Seletar when the new terminal opens. At the moment, the only airline that falls into this category is Malaysia’s Firefly – which currently operates 20 daily flights at WSSS – to and from WMSA/Subang, WMKI/Ipoh and WMKD/Kuantan.

Important to note – all BA/GA traffic must switch to using the new terminal when it opens on Nov 19 at midnight local time. Jet Aviation have provided a handy printout which tells you all you need to know about using the new terminal. Note that the new terminal is on the other side of the runway from the old terminal!

The 2018 G20 Leaders meeting will be held in Buenos Aires on November 30 and December 1, 2018. GA/BA flights will be prohibited from operating to both SAEZ/Ministro Pistarini and SABE/Jorge Newbery – but also all the smaller airport across the city as well.

AIP SUP A28/2018 goes into all of the restrictions in detail, but here are the key takeaways.

The airports…

Between 1500L on Nov 29 to 2200L on Dec 1 (1800Z Nov 29 to 0100Z Dec 2), here are the restrictions:

• SABE/Jorge Newbery – will be totally closed to all non-G20 aircraft.
• SAEZ/Ministro Pistarini – will only accept regular airline flights. All GA/BA flights are prohibited. RWY 17/35 will be closed and used as a taxiway and for parking only. Many SID and STARS will be suspended and a full list is in Appendix 2 of the SUP. (UPDATE 22NOV: Notam A9669/18 has now been published which brings forward the start time for the ban at this airport to midnight local time on Nov 26).
• SADP/El Palomar – closed to civil ops, although 8 slots will be made available to airlines from 1800Z-2300Z on Nov 29.
• SADF/San Fernando, SADJ/Mariano Moreno, SADM/Morón – all closed to civil ops.

So with all the Buenos Aires airports out of action for GA/BA over these dates, there aren’t a lot of other options. The closest international airports are: SAAR/Rosario to the north, SAZS/Plata Del Mar to the south, or SUMU/Montevideo – but that’s in a different country!

Bottom line – if you’re GA/BA and you need to get to Buenos Aires at the end of the month, you’ll need to make sure you go there before the G20 restrictions come into force on 1800z on Nov 29.

The airspace…

SAEF/Ezeiza FIR will see the following restrictions in place between those same timings, 1800z Nov 29 – 0100z Dec 2:

• All users must submit a flight plan a minimum of 6 hours before estimated off blocks time.
• All aircraft must operate on discreet transponder codes at all times.
• An ADIZ is in place out to 250NM from EZE VOR from SFC-UNL within the FIR.
• There will be 3 temporary restricted areas in place, BAIRES, SPY GLASS and ROJO.
• The BAIRES airspace overlays on top of SAEZ/Ministro Pistarini  out to 55nm.
• Expect Air Force fast jets to be patrolling and operating with ‘due regard‘ overhead during various times.

Did we miss something? Get in touch!

Just a short update on a few things happening in Canada that you might have missed…

Nationwide

• There has been a change in the Maximum Indicated Airspeeds for holding patterns to bring them more in line with the rest of the world. This came into effect on 11OCT18 and will be reflected in the 08NOV18 AIP update. Refer AIC 25/18.

• It’s been over a year and a half since NavCanada suspended it’s Climb/Descend via SID phraseology, adding a complication for pilots that regularly cross the border from USA to Canada and v.v. It initially trialed then quickly suspended them “out of concern over altitude deviations we were seeing in the system and the unforeseen large increase in workload as a result. We are continuing to communicate with airlines, aircraft operators and our employees as we revert to the phraseology rules that were in place prior to this change.​” We understand this phraseology has now been officially put in the trash and wont be returning.

CYYZ/Toronto Pearson Airport

• There are new nighttime RNAV approaches starting in CYYZ/Toronto Pearson from 08NOV18. These RNAV (GNSS) X instrument approach procedures are for night-time ops between 0030L-0630L on runways 5/6L/6R/23/24L/24R. The procedures are designed to minimize the noise footprint. The ATIS will advertise these as the primary approach type when they are active. Pilots can expect to be cleared directly to the initial approach waypoint, then subsequently cleared for the approach including the appropriate transition. Refer AIC 28/18.

• Slots are currently required for all flights between 0030-0630 local time. The airport authority was planning to make slots mandatory for all GA/BA flights H24 from Nov 17 onwards, but this will now be delayed to some time in early 2019. For more info, contact the Airport Reservation Office at aro@gtaa.com

Do you know more? Drop us a line!

The US reimposed sanctions against Iran on Nov 5. Despite this, so far there has been no change to the FAA guidance to US operators issued on 9th September 2018: flights to Iran are not prohibited, but operators should “exercise caution” when flying in Iranian airspace.

However, with the reimposed sanctions comes a new problem if you’re a US operator: you’re allowed to overfly Iran, but you’re not allowed to pay for all the things needed to make that happen – things like overflight permits, and nav fees.

The rule is simple: no US person or business can pay for services in countries with sanctions against them (like Iran), unless that person or business has a licence to do so, issued by the Office of Foreign Assets Control (OFAC).

And you’re not allowed to get an agent to do it for you either; it’s illegal to skirt the OFAC laws by using a 3rd party company (unless, of course, they’ve been approved by OFAC).

So the big question we have now is this: if you’re planning to overfly Iran, have you figured out the legalities of paying for services? How are you making that work? Know someone who’s got an OFAC licence for Iran? Let us know!

And one other thing to watch out for – operators with US based insurers should double-check their policies, as you may now no longer be covered for flights to Iran, due to the new sanctions. This is worth checking, even if you’re only planning on overflying the Tehran FIR, as any unplanned landing (decompression, medical, engine fire) may force you into Tehran or another airport – it’s a big chunk of airspace.

Further reading:

• SafeAirspace page for Iran. SafeAirspace provides a current picture of International Airspace, so that you as the Aircraft Operator can make sound decisions on which routes to fly and which to avoid.
• Our break-down of the US guidance on Iran overflight risk
• What the sanctions mean to non-US operators

The 2018 APEC meeting will be held in AYPY/Port Moresby, Papua New Guinea on 15 and 16 November, 2018. If you’re trying to get there, here’s what you need to know…

What’s happening at the airport?

• Parking – There may not even be enough space for all the official delegations’ aircraft, let alone anyone else, so expect parking congestion also at YBCS/Cairns and YBTL/Townsville airports. YBTL will also be used as a base by Australian military aircraft tasked with assisting the airspace security during the event; if you are heading there, make sure you read and carry the AIP SUP H99/18.
• Night closures – Closures of the main runway (14L/32R) mean that the airport is effectively closed each night from 2100-0430 local time until 13 November.
• Customs – if you’re actually going to AYPY during this period, you can view the APEC Customs handbook here.
• Flight Plans – If you indicate the wrong ADS-B FLT ID (in Section 7 of your FPL) and are inbound or outbound to AYPY/Port Moresby or AYNZ/Lae Nadzab you can expect a 20 minute delay or holding (A1069/18 refers).

What’s happening in the airspace?

AIP SUPP 5/2018 outlines the airspace restrictions for APEC2018. Here are the important bits, all effective from Nov 2-20:

• Watch out for overflights of AYPY, as there’s a 90 NM ADIZ in place around the airport from SFC-FL600.
• There is a temporary restricted area (TRA931) 30 NM around AYPY, SFC-FL330. Anyone flying to/from AYPY with a valid flight plan and talking to ATC can enter this area.
• There is another more restrictive area (TRA930) over the CBD and event venue. Only APEC aircraft can enter this area.
• Actual activation times will be notified by NOTAM.
• Expect Royal Australia Air Force FA18 fast jets to be patrolling and operating with ‘due regard‘ overhead during various times

A real life report…

Here’s a report from an Opsgroup member trying to operate to AYPY/Port Moresby for the APEC summit:

- The closest parking spot we could get for a G650 is YPDN/Darwin. We were denied parking in YBCS/Cairns; we were told parking is reserved for head of states only. YBTL/Townsville denied us parking too, on the basis of no space available.

- The handler at AYPY/Port Moresby is not very responsive at the best of times, and has been unreliable also in the past, even when no special event was going on. In the past we once even got handling confirmed for an arrival during a scheduled runway closure!

- Until Nov 30, crew/pax visas cannot be arranged upon arrival, to enhance security during the APEC event. Instead, visa requests must be made through embassies during this time. This is normally not a problem outside of special events. The PNG Embassy in London have been very quick in getting visas approved for our crew, with a maximum turn of 5 working days, and as short as 3 working days.

Some other Supplementary information if you are operating to AYPY/Port Moresby:

• High terrain in close proximity.
• Navaids not monitored by ATC. Standby power reported to be available. Jackson and Parer locaters no longer in operational use. Disregard any procedures that use these aids.
• Navaids may not be accurate or serviceable. Review all available information prior to use and perform appropriate crosschecks to verify navaid integrity.
• ATC may give inappropriate radar vectors and ALT instructions. During radar outage, ATC will provide procedural control. Maintain situation awareness to ensure safety not
  compromised. Refer to Radar Terrain Clearance Chart to cross-check altitudes.
• RWY 14L has upslope for 3/4 of its length, then slopes downward to the RWY 32R threshold, giving the illusion that the runway is shorter than actual.
• In gusty winds, expect windshear on approach RWY 14L.
• T-VASIS may be unserviceable without prior warning.
• Engine start clearance not required unless notified on ATIS.
• POB should be given with pushback request.
• Airway B220 is a designated two-way airway. Beware potential late-notice opposite direction traffic given close proximity to FIR boundary.
• Short-notice deterioration of ATC services may occur. If ATC not available, revert to CTAF on tower frequency.

Did we miss something? Let us know!

“Beware all pilots traveling to Abidjan, Customs is waiting for you!”

That is the message we received in a disconcerting report this week from one of our long-time members which certainly troubled us here at OpsGroup. We thought it was important to share.

The pilot told us that he and his business jet were recently “held hostage” by airport custom officials in the port city of DIAP/Abidjan, Ivory Coast, West Africa.

The crew had all the appropriate landing and overflight permits as required. GenDec’s, passports and associated documents were also in order. Therefore, all the evidence points to a good old fashioned shakedown and a convoluted scheme setup between local Customs agents and certain ground handlers to extort bribes from foreign crew.

The report we received explains how the crew were ramp checked by Customs officials after landing. The aircraft documents were confiscated and the Captain was “interrogated until 1am” the following morning.

The officials claimed that the pilot both failed to declare their arrival, as well as the “aircraft contents, passengers and baggage.”

The fine was CFA 6,900,000,000 (yes billion!) francs, which equates to USD $12,066,720 (yes, million!)

Ay Caramba!

The offence was purported to be importing a high value item (aircraft) without customs approval. The high fine figure was “based on the insurance value of the aircraft.”

The crew were held hostage in the country for 10 days until senior Customs officials could finally agree on the appropriate “accusation” and that the associated fine was actually “legal”.

After the 10 days, the crew were able to negotiate a deal and depart safely – although not without having to involve the aircraft’s insurance underwriter, who paid a ‘substantial amount’ for the aircraft to be allowed to depart.

On reflection, the crew noted that if Customs does meet your aircraft without you arranging it in advance, “you can be sure you are about to be trapped.” They do not tell you why they are looking for documents, more specifically, your aircraft documents, and will not tell you anything as they walk away to call their seniors, carrying your documents with them.

So in short: do not let go of your documents!

The advice from our member:

• Contact the handling agent first hand and double check that they are an approved, recognized handler and have approval from the various authorities (immigration, customs, police, anti-drug) to operate airside. Also check that they can arrange for you to get to the Customs and Immigration officers landside. Do not assume because the handler takes all your documents and gives you an invoice and receipts that the authorities have been advised of your arrival and situation.
• The Abidjan Customs authority does not recognize a GenDec as an approved form of advice about passengers, health and cargo. They will also not sign off on the submitted GenDec. They will not come to your aircraft unless you specifically arrange for them to do so.

It’s important to stress that we are not talking about a small African airstrip in the back lots. This is a large international gateway with many major international airlines serving the city. Over 4 million people live here and it’s the economic capital of the Ivory Coast.  But corruption is endemic, it spills over every sector of the public administration; clearly even into Customs!

As Brookings put it, “for the inspector, the temptation is large because his salary is relatively small compared to the potential bribe.” It still doesn’t make it right and this experience serves a timely warning for all crew operating through the airport.

Have you been subjected to similar behavior when passing through DIAP/Abidjan? Let us know.

Extra Reading

• Cote d’Ivoire Travel Advisory
• Understanding the Roots of Corruption in Cote d’Ivoire
• Why there is (petty) corruption in Ivory Coast

The Civil Aviation Authority of Bangladesh recently published circular 02/2018 which outlines a $195 USD overflight permit fee for non-scheduled foreign aircraft transiting the VGFR/Dhaka FIR . The fee is certainly on the high side but the disappointing part is :

“The payment is non-refundable, irrespective of the approval or rejection to the permit request.”

Say what?

There was a similar type of no-refund situation within the TNCF/Curaco FIR but we now understand after some noise, operators are getting refunds as per normal industry practice.

We say it’s time for the CAA in Bangladesh to stop this non-refundable nonsense.

Have you had a permit denied and not received your money back? Reach out and Let us know!

PBCS has been an ongoing PITA for some time now. We wrote about it back in March. Here are the top three questions we’ve had on it since then – and now we finally have some answers!

Question 1: What happens if I still haven’t received my updated A056 LOA?

After the PBCS tracks were introduced in March 2018, the FAA published a Notice requiring all N-reg operators to update their A056 LOA authorization – regardless of whether or not they intended to fly these PBCS tracks. For private (Part 91) operators, the deadline to submit the application was 30th September 2018.

There was a barrage of applications, and the FAA still seem to have a bit of a backlog, as even now some operators have still not received their updated approvals.

The FAA’s unofficial policy is that as long as you have applied for a revised LOA, you can continue to use your old authorization after September 30th, while you wait for the new one to be issued.

Bottom line: This means you are allowed to keep flying in the North Atlantic, just not on the PBCS tracks.

Question 2: What about that problem with aircraft with Honeywell systems installed?

Back in March, a latency timer issue with certain Honeywell FMS systems meant that there were bunch of aircraft which weren’t able to get the PBCS approval.

In June, Honeywell issued a service bulletin fix for the issue, available at varying times for different aircraft. Since then, the FAA has been issuing the updated A056 LOA approvals to those aircraft with the Honeywell systems that reflect the new capabilities but the still don’t meet the PBCS requirement of RCP240 due to the latency timer issue.

Bottom line: Now those affected aircraft are able to receive the updated A056 LOA approvals, just with a PBCS restriction – meaning they can continue to operate in the North Atlantic, just not on the PBCS tracks.

Question 3: What the heck is PBCS anyway?

PBCS stands for ‘performance-based communication and surveillance’.

PBCS involves globally coordinated and accepted standards for Required Communication Performance (RCP) and Required Surveillance Performance (RSP), with the goal being to allow the application of reduced lateral and longitudinal separation to aircraft which meet the criteria.

To be PBCS compliant, you basically need CPDLC capable of RCP240 and ADS-C capable of RSP180; this effectively means having a 4 minute comms loop, and 3 minute position reporting.

PBCS has been implemented in various different chunks of airspace around the world, but most notably in the North Atlantic, where the three core daily NAT Tracks are assigned as PBCS tracks between FL350-390. To fly those, you will need to be PBCS compliant (read above) but also have RNP4 (the rest of the NAT only requires RNP10).

Feeling queasy? That’s okay, reading about PBCS makes us feel that way too. If you’re still hungry for more though, check out our recent article on all things PBCS!

More questions? Get in touch!

The NAT used to be simple. Fill your flask, fire up the HF, align the INS and away you went.

Now, it’s a little more complicated. Basic Instruments are not enough. Use this quick and dirty guide from FSB to figure out where you are welcome on the NAT, depending on what equipment and training you have. Valid for October 15, 2018.

The United States is rolling out En Route FANS CPDLC during 2018-19, for all equipped, trained and permitted operators. The FAA’s Advisory Circular AC 90-117 outlines the requirements for U.S. operators.

Trials have begun with KZID/Indianapolis going live with 24/7 ops starting last week.

We also understand that KZME/Memphis and KZKC/Kansas City are still in the testing phase with CPDLC and voice read back happening 1-2 nights per week during the midnight shift.

The current deployment schedule as it stands can be found in this graphic. [if you know what DFV means, let us know!]

How to participate:

• The FANS logon is “KUSA” for the entire country and you may logon at any time. The CPDLC connection will become active after departure, and the crew is notified via a welcome message uplink. If En Route FANS CPDLC enabled airspace is active, you will stay logged on. If the aircraft transitions from En Route FANS CPDLC enabled airspace into non-Data Link airspace with an active CPDLC connection then the connection will terminate approximately seven minutes after exiting.
• To participate, file “DAT/FANSE” in Field 18 of the ICAO Flight Plan.
• Equipment required is VDL Mode 2, indicated as “J4” in Field 10a of the ICAO Flight Plan.
• If an operator wants to use domestic En Route FANS CPDLC and is already using FANS DCL then the the majority of operations will fall into one of these scenarios:
  • (1) The operator uses FANS DCL via the “DAT/1FANS2PDC” preference in Field 18 of the ICAO Flight Plan. In that case, update the preference to “DAT/1FANSE2PDC“.
  • (2) The operator uses FANS DCL via the FAA’s Subscriber Database. In that case, the operator will want to add the entry “DAT/FANSE” in Field 18 of the Flight Plan.

Some things to keep in mind:

• Domestic En Route FANS CPDLC enabled airspace will be seamlessly integrated with foreign (Canadian) and Oceanic FANS CPDLC enabled airspace.
• The Oceanic Clearance will not be delivered via FANS CPDLC. You will still need to request the clearance via AFIS/ACARS or obtain it via voice.

Have you had the chance to try it out recently? Let us know!

Extra Reading:

• Rockwell Collins
• FAA Advisory Circular AC 90-117

We reported a few months back that the Airport Authority (AAHK) and the Hong Kong Schedule Coordination Office (HKSCO) have decided to trial an increase in slot availability from 4 to 6 total slots each night. It looks like the trial is being extended until March 2019.

The published details:

Notice on night slot availability (trial from 8 August 2018 until 31 March 2019)

1. The number of slots available for GA/BA operations between 0000 to 0500 local time (16-21 UTC) will increase from 4 slots daily to 6 slots daily.
2. The application procedure for these 6 slots will be the same as that for the 4 daily slots currently available.
3. The above are provided on a trial and temporary basis and are subject to continuous review jointly by AAHK and HKSCO.
4. Also important to note, as pointed out to us by our friends at the Asian Business Aviation Association (AsBAA) – these 6 slots will be made available to all aircraft types, not just the ones currently exempted from the noise abatement regulations. This means that BBJ’s/ACJ’s/Lineage 1000/Globals/G650ER etc can now operate in and out of Hong Kong at night-time, subject to slot availability.

In Short: The performance-based communication and surveillance (PBCS) framework allows for higher safety standards and more efficient airspace use. If your aircraft already has the equipment and you cross the Atlantic or Pacific Oceans often, it’s worth looking into getting your regulatory approval.

PB… what? It’s a good question. We have so many acronyms in aviation, it’s easy to forget what this one stands for and what it really means. So, let’s try and get to the bottom of it.

What is PBCS?

Official answer:

The ICAO performance-based communication and surveillance (PBCS) framework ensures that emerging technologies for communication and surveillance fully support ATM operations and are implemented and operated safely.

In plain speak:

With the technology already available on many aircraft and in the Air Traffic Control facility, aircraft can now fly closer than ever before, especially over non-radar oceanic airspace.

There are two key buzz words, so let’s define them. They are interlinked with RNP – Required Navigation Performance.

• RSP – Required Surveillance Officially known as “surveillance data delivery”, often stipulated in the Airplane Flight Manual. Basically, how often does the aircraft send its position to ATC/ground station. There are two specifications, RSP180 and RSP400. The numbers indicate the maximum number of seconds (180 or 400) for the transaction to occur.
• RCP – Required Communication ICAO has two specifications, RCP240 and RCP400. Again, the numbers indicate the maximum number of seconds (240 or 400), or “transaction time” taken for the controller to issue an instruction to the crew and for them to receive a response. This could be via CPDLC, HFDL, VDL or SATCOM.

So, we have a loop here, C-N-S. Communication, Navigation and Surveillance. An aircraft sends surveillance information to ATC about where it is; the aircraft stays within confines of RNP navigation requirements and ATC communicates with the aircraft within the required transaction times.  Pretty easy!

But why do we need PBCS?

The take away? If all given aircraft in a certain airspace have a lower RSP value and a lower RCP value, we can start putting these aircraft closer together.

Essentially – performance-based separation minima. This allows aircraft to be separated safely according to technological capability rather than “one-size-fits-all” prescriptive distances.

What are the differences from PBN?

They are similar but there are notable differences. In a simple sense, the PBN (RNP/RNAV) only requires that the operator obtains approval because it focuses on how the equipment works. PBCS (RSP/RCP) however requires the involvement and approval of the air traffic service provider because it’s a two-way communication and surveillance effort. There are dependencies and complexity with the equipment standards on both ends.

In this graphic you can see a high-level summary of who is responsible for what:

Where is it in place?

Currently PBCS is in effect in one form or another in the following FIR’s

• NZZC/Auckland Oceanic
• NFFF/Nadi
• KZAK/Oakland Oceanic
• PAZN/Anchorage Oceanic
• WSJC/Singapore
• VCCF/Sri Lanka
• NTTT/Tahiti
• RJJJ/ Fukuoka
• KZNY/New York Oceanic
• CZQX/Gander
• EGGX/Shanwick
• BIRD/ Reykjavik
• LPPO/Santa Maria Oceanic

The Air Traffic Service providers of China, Brazil and Indonesia have also shown interest to introduce PBCS in the future.

Specifically, PBCS is being used between FL350 and 390 on certain “half” NAT tracks as we have written about before.

What do I need to do?

Requirements vary from state-to-state on the exact procedure for obtaining approval. It’s important to note that not all aircraft are automatically PBCS ready (refer to your aircraft manufacturer and your airplane flight manual).

The FAA has outlined its approval process here and has a handy powerpoint document here.

An important element is to prove that you have signed the “PBCS Global Charter” which can be found at the FANS Central Reporting Agency (CRA) website.

When a PBCS authorization is obtained an operator is required to file both P2 (indicating RCP240) in item 10 and SUR/RSP180 in item 18 of the flight plan, in addition to the J codes for CPDLC and D1 or G1 for ADS-C in item 10.

The correct filing of these two codes will indicate to any ATM ground systems applying performance-based separation minima that the aircraft is eligible for these minima and that the crew have received the relevant training in order to safely operate using the reduced separations.

Will you notice that PBCS standards are being applied to your flight?

Ok this is the funny part of this story. The short answer, probably not.

While it may be easier for RCP240/RSP180 approved aircraft to obtain optimal flight profiles, especially during high traffic periods, and particularly for NAT flights using the OTS, the application of these standards is generally tactical in nature for ATC. An aircraft may not have performance-based separation applied at all on an individual flight, or possibly may never have had it applied to any of its flights. Even if a you have RCP240/RSP180 approvals, if the aircraft nearby does not also have the approvals, the separation standards cannot be applied!

What if I don’t have RCP240 and RSP180 approval?

If you do not have RCP240/RSP180 approvals you will always have the larger separations, e.g. 10-min, applied, and not be eligible for the lower standards in cases where it may be beneficial.

The only airspace that has implemented tracks that will require PBCS to file is in the NAT OTS. There are still non-PBCS tracks in the OTS for which PBCS approvals are not required.

All other airspace in which performance-based separation minima are currently applied will allow aircraft with and without RCP240 and RSP180 approvals to enter and use the airspace in a mixed-mode operation.

Will I be penalized if I don’t have it?

Probably not in the short term. In the future as more and more airspace corridors become PBCS only, then it is possible you may be subject to reroutes, delays or the requirement to fly outside of certain flight levels.

So, our conclusion?

PBCS is a great step forward in maximizing efficiency in a busier airspace environment thanks to the advent of better technology. If you fly the NATs often and have an aircraft capable of PBCS certification standards, then yes – do it! The approval process is not overly burdensome, and many modern transatlantic jets already meet most of the technical requirements.

Ultimately, reduced separation standards mean more great air-to-air views. So, pack your camera!

You were in a 4G inverted dive with a Mig 28? -Yes, ma’am. -At what range? -Um, about two meters. -Eh, lieutenant, what were you doing there? -Communicating. Keeping up foreign relations.

Did we miss something, or does something need more explaining? Let us know!

Extra Reading:

• The latest Nat Doc 007 North Atlantic Operations and Airspace Manual
• FAA-Performance-based Communication and Surveillance (PBCS) Monitoring
• FAA-PBCS FAQ
• FAA-PBCS: Operator Approvals
• FAA-Performance-based Communication and Surveillance (PBCS) Approvals and Monitoring
• FAA-PBCS Manual Doc 9869 Review
• ICAO-Operational Authorization Guide
• ICAO-PBS Overview
• NBAA -Revised Authorization Required for Performance-Based Comm, Surveillance Operations
• New Zealand -Performance Based Communication and Surveillance (PBCS) Implementation Plan

New NOTAMS (pretty poorly written ones – but hey that’s another topic) have been issued for SCEL/Santiago in Chile, outlining some runway configuration changes between 31 October and 20 December, 2018.

Operational Changes

• RWY 17L/35R will be closed for heavy maintenance between 1200z-2259z (0900L-2000L) daily except during low visibility operations.  (NOTAM A3273/18)
• New RWY 18/36 established on current Taxiway Alpha and will be used in place of 17L/35R for aircraft up to A321 size. It’s dimensions are 2280M x 36M. See updated ground chart here. (NOTAM A3262/18)
• New RWY 18 GNSS approach established. See this chart. (NOTAM A3263/18)
• The STARs currently used for 17L will be applicable for RWY 18. (NOTAM A3265/18)

Opsgroup members have also advised us that;

• Due to standard late night noise restrictions, departures will be required to use 17L (not 17R).
• Pay careful attention to the substantially different missed approach procedure for GNSS RWY 18 procedure. This has been designed differently to allow a “tighter” traffic sequence and permit simultaneous operations on 17R. This is not normally possible due to the conflicting departure and missed approach paths.

If you do get to head to Chile, grab the window seat and grab a camera! I took these last year!

It really is such a great approach!

You were all very supportive when we wrote the initial article on the BS Notam problem last year, and have followed our journey in fixing the problem since then.

Big news!

The NTSB called the Notam System a bunch of garbage on Tuesday this week, and assigned probable cause of the AC759 incident in SFO to the Notams that were missed.

What this means to OpsGroup is massive fuel to our fire: we are working hard to fix this problem, and having a public facing government organisation like the NTSB come down like a ton of bricks on the Notam System drives us forward in leaps and bounds.

The group members have been decisive in helping us to identify the problem and taking action to fix this. So, we want to acknowledge all of you! Great work!

In solving two of the above five problems, we have been working with ICAO for several months now. You all got involved in Norm, and 17,000 Notams later, we happy to report that version 0.1 of Norm is now live on the ICAO website. Norm is a bot – an AI, that has learned what Notams look like, and thanks to OpsGroup rating these 17,000 Notams, is also learning which ones are critical and which ones are not.

He’s still young. He doesn’t get everything, but if you feed him a Notam you’ll see him assign it a criticality of 1-5.

This will in turn allow us to sort Notams, putting the most important stuff first.

The pilot at the controls of a Beechcraft B200 Super King Air that crashed shortly after take off had the aircrafts rudder trim in the full left position for take off, the Australian Transport Safety Bureau (ATSB) has found.

The ATSB final report said the aircraft’s track began diverging to the left of the runway centre line before rotation and the divergence increased as the flight progressed.

It then entered a shallow climb followed by a “substantial left sideslip with minimal roll” before beginning to descend. At this point the pilot issued a mayday call seven times in rapid succession.

Approximately 10 seconds after the aircraft became airborne, and two seconds after the transmission was completed, the aircraft collided with the roof of a building.

What Happened?

The investigation found that the pilot did not detect that the aircraft’s rudder trim was in the full nose-left position prior to takeoff.

“Prior to takeoff, there were several opportunities in the pre-flight inspection and before takeoff checklists for the pilot to set and confirm the position of the rudder trim,” the ATSB final report said.

A King Air flight simulator was used to recreate the event as part of the ATSB investigation.

The pilot who performed the flight simulator test commented that:

The yaw on take-off was manageable but at the limit of any normal control input. Should have rejected the take-off. After take-off the aircraft was manageable but challenging up to about 140 knots at which time because of aerodynamic flow around the rudder it became uncontrollable. Your leg will give out and then you will lose control. It would take an exceptional human to fly the aircraft for any length of time in this condition. The exercise was repeated 3 times with the same result each time. Bear in mind I had knowledge of the event before performing the take-offs.

The pilot also stated that it could be possible for a pilot to misinterpret the yaw as being caused by an engine power loss rather than from a mis-set rudder trim.

Safety message

Cockpit checklists are an essential tool for overcoming limitations with pilot memory, and ensuring that action items are completed in sequence and without omission. The improper or non-use of checklists has been cited as a factor in some aircraft accidents. Research has shown that this may occur for varying reasons and that experienced pilots are not immune to checklist errors.

This accident highlights the critical importance of appropriately actioning and completing checklists.

Checklist discipline

In previous correspondence between the accident pilot and the ATSB when discussing checklists, the pilot stated that:

“You don’t get complacent as a pilot but you get into a routine. The same as your pre-take-off checks, you get a routine and you don’t need to use a checklist because you are doing it every day, you are flying it every day… I take-off with one stage of flap because it gets me of the ground quicker. And I never change my routine…”

Wait what!??? It is stating the obvious but it’s a timely reminder that checklists are an essential defense against pilot errors. 

Sadly, it could have been a life-saver in this instance.

The ATSB video to supplement the report.

Here’s the level of inconsistency we’ve reached in international air transport: we take each passenger, scrutinize their booking, check the no-fly-list, watch them on CCTV, pull them apart at TSA, remove anything sharper than a pen, question them, x-ray the bags, run Explosive Trace Detection tests, screen the hold baggage, background check every member of the crew, and then, once they’ve all boarded, fly this ultra-secure airplane straight into a war zone.

Welcome to the Eastern Mediterranean. It’s an active conflict zone. The Russian naval build up there this month is the largest since Moscow’s intervention in Syria began in 2015. Over Syria, 9 aircraft have been shot down this year.

The most recent was on Monday night this week, when Syria came under attack from Israel fighter jets, and started firing indiscriminately at anything off the coast that looked like a threat. They wanted to shoot something down, and they did — except it was a friend, not foe. They took out a Russian Ilyushin IL-20M transport category airplane. Even on the worst radar, that doesn’t look anything like an Israeli F-16.

50 miles away from where the Russian aircraft plunged into the sea on Monday night is the international airway UL620, busy with all the big name airline traffic heading for Beirut and Tel Aviv. If Syria can mistakenly shoot down a Russian ally aircraft, they can also take out your A320 as you cruise past.

And yet, most airlines continue to operate. Are we really so comfortable with operating in conflict zones again?

The lessons of MH17 seem to be fading fast. It’s a little over four years since 298 people lost their lives over Ukraine one summer afternoon, thanks to an errant missile fired during a civil war at an aircraft that they thought was a military threat. “Why were they over a war zone”, everyone cried afterwards.

Well, we all were. Me too. I was a pilot for Austrian Airlines at the time. I recall one morning in Vienna, some months before MH17. Boarding the last of the passengers, my BBC news app flashed up a story about a helicopter being shot down in eastern Ukraine .

As we were headed east, with my colleague in the cockpit, we quickly plotted the position on our enroute chart, and noted that it was really close to our route. Maybe 30 miles north. “We might see something interesting!”, we said, and pushed back. We didn’t, nor did we think much more about it.

Do you see the thought process though? Before MH17, we didn’t consider the risks to our aircraft from war zones. Especially being so high. Helicopters might be getting shot down, but we’re at 35,000 feet. No problem.

This is why all of these airlines — mine, at the time, included — operated on the route.

Image: Der Spiegel

And then it happened, and none of us could quite believe it.

But we learned. “Conflict Zone” became a buzzword. We had task forces and committees, whitepapers and promises, and — myself included — talked at length about how this happened, why, and how to avoid it in the future.

And yet, here we are flying unsuspecting passengers along the Syrian border. If you’re unsuspecting enough, and buy a SkyTeam codeshare ticket — you’ll actually overfly Syria on the Honey Badger airline of the region, Middle East Airlines.

Here we are flying passengers in the Eastern Mediterranean war zone. Why is this happening?

My guess: because we don’t think anything bad is going to happen, because the airspace boundary lines on the charts make that little bit of sea near Cyprus feel different from that little bit of sea near Syria, but mainly because there is no clear guidance from Aviation Authorities.

Let’s start with Cyprus. The Nicosia FIR has a big chunk of unsafe airspace. The Russian aircraft on Monday was shot down on the Nicosia FIR boundary. What do the Notams say? Take a look. There are 97 of them. Mostly about fireworks at local hotels. Critical stuff indeed. Then there are 20 or 30 about “Russian naval exercises”. A clue, perhaps, but where is the black and white “An Aircraft was Shot Down on our Border on Monday?” . Or, since we are still using teletype to communicate Notams to crews, “AN AIRCRAFT WAS SHOT DOWN ON OUR BORDER ON MONDAY”. Wait, we have to abbreviate that, and use codes, for some reason. “ACFT SHOT DOWN ON FIR BDY 17SEP”. That’s better.

What about Turkey? Anything on the Eastern Mediterranean risk? Let’s have a look. Nope, just 132 Bullshit Notams, and something about an AWACS aircraft. See you back here in 30 minutes when you’ve read them all.

Remember, I’m being a pilot, an airline, a dispatcher, trying to find information on the Risk in the Eastern Mediterranean. And this is how hard it is.

EASA (European Aviation Safety Agency), how are you doing? Let’s start here, at the “Information on Conflict Zones”. Paragraph 2 tells us that ICAO have a Central Repository on Conflict Zones, launched in 2015.

No, they don’t. That died — quite a long time ago. This is where it used to live. So, there is no ICAO Central Repository on Conflict Zones. There is a new ICAO document with guidance on managing Conflict Zone risk (and it’s a bloody good one, too) — but where is the picture of current risk?

Let’s plough on through the EASA site. Aha! Seems we have a Conflict Zone alerting system, and Conflict Zone bulletins. Here they all are: https://ad.easa.europa.eu/czib-docs/page-1

The last one on Syria was issued on April 17th. But it seems to be just a list of Notams issued by other states. And these are out of date. The German Notam has expired, the French AIC has been replaced.

And there’s no guidance. No Map. No routes to avoid. Nothing about Cyprus, or Beirut. No mention of the Russian shootdown. No mention of the 9 aircraft shot down this year.

How am I supposed to know, as an operator, or pilot, what the risks are and where to avoid. We’re getting closer to the point here. You’re not supposed to rely on the Aviation Authority. That is their message. You must conduct your own risk assessment. You must research and find out about the risks yourself.

You are on your own.

If you’re a big airline, that’s probably fine. You’ll make your own decisions about where to fly, anyhow. But what about everybody else?

While OpsGroup works hard to get information out to our members — and we spend a lot of time researching risk — I would greatly prefer that we didn’t have to.

Aviation Authorities must issue better guidance for the aircraft entering their areas.

Let me remind you. Airlines are operating 50 miles from a position where an airplane was shot down at night, by a missile type that’s already taken out a passenger airliner by mistake, fired by a beleaguered Syrian defence post, at a friendly aircraft that they did not take time to identify.

And the guidance to operators from Authorities: NIL.

Opsgroup has now published Note 31: Airspace Risk in the Eastern Mediterranean. There is a clear risk to civil aircraft operating on airways UL620, UW74, UR18, and UP62. In simple terms, if you find yourself planned overwater east of Cyprus, reconsider your route.

Further reading:

• ICAO Doc 10084 – Risk Assessment Manual for Civil aircraft flying over or near conflict zones. This was published this year, fully updated – read it!
• Safeairspace. Managed by OpsGroup, this is our public repository and first point of warning for Airspace Risk for airlines, pilots, dispatchers, and aircraft operators.

With planned runway and terminal constructions, LIML/Milan Linate will be closing from July 27, 2019 until October 27, 2019.  Work has already begun with Assoclearance (slot coordination) to work out summer schedules.

Today, September 20, a coordination meeting will take place to clarify the slot allocation process for S19. Following this, a September 25th meeting at Linate will be held to discuss the operational impact of the closure.

Milan Linate handled over nine million passengers in 2017, so a large portion of this traffic will now have to operate through LIMC/Milan Malpensa, which already stands as the second busiest airport in Italy, handling over 22 million passengers in 2017.

We’ll have more information after both the slot and operations meetings this coming week.

Do you know more? Feel free to comment or drop us a line!

Latest update: 1900z, Sept 17th.

Most airports have reopened, with the exception of KILM and KOAJ (see below).

The National Weather Service have warned – “Florence is forecast to bring a large area of rainfall of 20-40 inches to parts of NC/SC. We cannot overstate the threat of catastrophic flooding this storm will bring!”

Severe disruption is expected across the entire region spanning from KSAV/Savannah in the south up to KRIC/Richmond in the north, with multiple airport closures planned.

As of 1900z on Sep 17th, the situation is as follows:

• ASHEVILLE, NORTH CAROLINA (KAVL) @flyavlnow
  Airport is open and operational.
• CHARLESTON, SOUTH CAROLINA (KCHS) @iflyCHS
  Airport is open and operational.
• CHARLOTTESVILLE, VIRGINIA (KCHO) @CHOAirport
  Airport is open and operational.
• WILMINGTON, NORTH CAROLINA (KILM) @ILMAirport
  The airport is open, but it’s not recommended to operate, no power, no ILS, no tower. One runway is open for rotor aircraft.
• FAYETTEVILLE, NORTH CAROLINA (KFAY) @flyFAYairport
  Airport is open and operational.
  
• MYRTLE BEACH, SOUTH CAROLINA (KMYR) @FlyMyrtleBeach
  Airport is open and operational, some equipment outages, keep an eye on Notams.
  
• GREENSBORO, NORTH CAROLINA (KGSO) @flyfromPTI
  Airport is open and operational.
• HILTON HEAD, SOUTH CAROLINA (KHXD)  @hiltonheadSC
  Airport is open and operational.
• NORFOLK, VIRGINIA (KORF) @NorfolkAirport
  Airport is open and operational.
• RALEIGH-DURHAM, NORTH CAROLINA (KRDU) @RDUairport
  Airport is open and operational.
• SAVANNAH, GEORGIA (KSAV) @fly_SAV
  Airport is open and operational.
• WINSTON-SALEM, NORTH CAROLINA (KINT)
  Airport is open and operational.
• LYNCHBURG, VIRGINIA (KLYH) @lynchburggov
  Airport is open and operational.
• RICHMOND, VIRGINIA (KRIC) @flack4RIC
  Airport is open and operational.
• CHARLOTTE, NORTH CAROLINA (KCLT) @cltairport
  Airport is open and operational.
• NEW BERN, SOUTH CAROLINA (KFLO)
  Airport is open and operational.
  
• FLORENCE, NORTH CAROLINA (KEWN)
  Airport is open and operational.
• PITT-GREENVILLE, NORTH CAROLINA (KPGV)
  Airport is open and operational.
• JACKSONVILLE, NORTH CAROLINA (KOAJ)
  The airport is closed – scheduled to reopen Sept 18, accepting military and rescue flights.
• ROCKY MOUNT, NORTH CAROLINA (KRWI)
  Airport is open and operational.

Do you know more and can add to this list? Let us know!

Extra Reading:

• Google Crisis Map
• You can view the latest projections and forecast maps with the NOAA here.
• You can view the latest information from the FAA here. The latest flight delay information is here. 

In the recent France AIP August update a new requirement was added for all aircraft inbound to LFPB/Paris Le Bourget to list their parking position and handler on Field 18 of their flight plan.

Mentioned twice in the local traffic regulations (the translation is a little iffy but you get the idea):

Mandatory assistance by approved based companies. The name of the assistant society must be stated in field 18 of the FPL as a remark (RMK).

and

It is required to the crews to indicate in field 18 of the flight plan, the traffic area of destination and the name of the handling provider.

We understand that this came about due to “much confusion” of the parking stand locations after aircraft land.

Remark 18 should include

1. Handler Name
2. Your parking stand location (e.g. HANDLER ABC T1 APRON FOXTROT 2)
   • For heavy aircraft (A330/A340/A350/B747/B787/B767/C130) apron Golf, Sierra or Foxtrot 3 will suffice. Your local handler should give you confirmation ahead of your expected flight.
3. Your handlers phone number.

So it should look something like this:

(FPL-FGTRY-IG

-C525/L-SDFGRWY/S

-LFMD0610

-N0360F340 OKTET UM733 GIPNO UT26 LOGNI UN854 DJL

-LFPB0120 LFPN

-PBN/A1B2D2S1 DOF/180903 IFP/MODESASP ORGN/KBLIHAEX RMK/HANDLER ABC TERMINAL 1 APRON FOXTROT 2 TEL : +3312345678)

Do you know more? Feel free to comment or drop us a line!

Also- here is a video of a Beech Bonanza flying under the Eiffel Tower 

As a group of 4000 pilots, dispatchers, and controllers, we stand for safety ahead of commerce. Al Jazeera interviewed our founder, Mark Zee, about the current risk in Ethiopian airspace created by the ATC strike, and why we care so much about getting the truth out to our members.

https://www.facebook.com/flightservicebureau/videos/244638736242463/?t=1

5th September, update:

As of this morning, most controllers have returned to work. Some concessions made by ECAA. Addis ACC and TWR are again staffed with qualified controllers, so the safety situation, for now, is restored. However, 9 remain in jail. Returning controllers were forced to sign an ‘admission’ of illegal strike action in return for amnesty. IATA In Flight Broadcast Procedure requirement for Addis FIR remains in place, meaning you must broadcast on 126.9 as in other areas of concern in Africa. Further as we get it.

4th September:

Last week we were one of the first to expose the attempted ATC Strike cover up by the Ethiopian Civil Aviation Authority.

As a reminder, untrained and uncertified foreign controllers, retired and local non-operational ATC personnel are being used to control air traffic over Ethiopia. 

It is a catastrophic misjudgement, creating a safety risk in the Addis FIR and at Ethiopian Airports for pilots and passengers alike.

Here are some more updates since our last article:

• On August 29, The International Federation of Air Traffic Controllers Association (IFATCA) penned a letter to the Prime Minister of Ethiopia. You can read it here.
• The neighbouring controllers in Kenya warned that flights in and out of Addis Ababa are not safe. You can view their letter here – specifically they warned that the ‘possibility of air misses’ is real.
• The ECAA over the weekend rejected concerns regarding the safety of Ethiopian airspace, specifically calling the claims from Kenya as “outright lies.”  The ECAA has said that ATC are operating “in accordance with ICAO Annex 1 provisions.” They did not deny however that foreign and retired ATC are being used.
• The ECAA also outlined that the national carrier, Ethiopian Airlines, has “awarded” veteran Air Traffic Controllers,  who are performing their “national obligation.“
• However on Monday, the local state affiliated broadcaster, Fana BC, reported that the Federal Police Commission had detained nine individuals on suspicion of attempting to disrupt international flights and coordinating a strike that began last week. This has been quickly condemned on social media, as many locals called on the government to resolve the issues raised by the ATCs rather than resorting to intimidation.

The ECAA claims that “some” of the striking controllers have returned to work.

Major airlines and uninformed passengers continue to fly into and over Ethiopia and this continues to be a major safety risk.

Do you have more to add this story?  Please, let us know!

Australian traffic holding is a funny one; you can fly 16 hours directly from a place far far away, and then just before landing you get told to hold for 20 minutes – even though you have been in Australian airspace for sometimes 7 hours plus, they wait until the last few minutes to slow you down. ?

A recent AIP update and AIC Supp (H25/18) has updated the Airborne Holding Requirements for the four major Australian airports:

YBBN/Brisbane and YMML/Melbourne now are all in line with YSSY/Sydney

• Daily, 2000Z-1300Z (0600L-2300L) = 20 Minutes 

YPPH/Perth – Monday to Friday ONLY

• 0100Z-0500Z (0900L-1300L) = 10 Minutes
• 0500Z-0900Z (1300L-1700L) = 5 Minutes
• 0900Z-1300Z (1700L-2100L) = 10 Minutes

There has been a slight change in the AIP requirements also. Instead of publishing “holding fuel advisories” – it’s now called “airborne traffic delays”. So they aren’t really advising you on what fuel to carry anymore. In fact they go as far as saying that:

“All traffic delay estimates are an indication only. Actual holding may differ from the estimate, and operators should use their own judgement on fuel carriage decisions. More detailed historical holding data is available from the NCC on request.”

But… if you arrive at a destination without sufficient holding fuel for “actual traffic holding” then… “you will not be accorded a priority approach unless you declare an “emergency”.

So keep an eye on the NOTAMs for updated daily requirements. Even as recently as this week, 30 minutes holding was being required in YSSY/Sydney due to ATC shortages.

Insider tip: If you see the winds in Sydney from the west gusting more than 25 knots, you will see a NOTAM for traffic holding that increases the 20 minutes to 50 minutes or more due to single runway ops. You can expect to see similar NOTAMs when any low visibility operation kicks in at the other airports.

A few other quick updates for operations around Australia that you might have missed.

• YPPH/Perth now has a Category III Instrument Landing System. Perth is a very isolated airport, especially for long-haul widebody operations, with the nearest diversion alternates being over 600-1000nm away.
• YBBN/Brisbane‘s main runway, 01/19, will be changing designation to include a LEFT and RIGHT in early November in preparation for the certification of the parallel runway in 2020.

Have we missed anything? Then let us know!

A few months back an Air Canada A330 suffered a hydraulic failure as it started it’s Atlantic crossing from France to Canada. The crew decided to turn back and wanted to divert to EGLL/London Heathrow – this was denied.

Since then, other reports have been received of other aircraft requesting similar non-emergency diversions over the UK and them being denied. We understand the “non-acceptance of diverts” policy is in place for EGGW/Luton, EGSS/Stansted and even as far away as EGHH/Bournemouth. It is important to note however that if you declare an emergency (PAN/MAYDAY) – then all bets are off and you can divert wherever you like.

This week we saw EGGW/Luton go as far as publishing a NOTAM to that effect.

A2663/18 – DIVERTS SHALL ONLY BE ACCEPTED FOR ACFT THAT HAVE DECLARED AN  EMERGENCY.

So what’s going on?

We understand it’s a mix of things.

1. With the heavy summer traffic situation all across London (which is being compounded by the various curfew and overnight flight limitations) it seems that the major airports don’t want an aircraft landing and disabling their runway.
2. We have heard specific concerns stating that there is nowhere to park overflow aircraft. One aircraft might be manageable but multiple during peak disruption maybe not so easy.
3. Some Opsgroup members have reported that the main driver of this policy at EGGW/Luton and EGSS/Stansted may be down to ‘their fear of adverse publicity on social media’ regarding aircraft sitting there waiting to go somewhere else and passengers tweeting away the problems with the airport and its facilities.
4. Luton also put forward the argument that they do not want to interrupt the home-based operators by allowing other operators in. However, at the same time they are automatically denying home-based operators a diversion unless you declare an emergency.
5. Border Control has also bought into the argument, especially at EGSS/Stansted, saying their manning levels can’t cope with an influx of extra passengers at short notice.

There are a whole host of other factors at play which make diversions in the London area a headache, particularly at night time. Opsgroup member Diego Magrini from Jet Concierge Club sums it up nicely:

“Minor airports close early in the evening, for example EGSC/Cambridge, EGTK/Oxford, EGLF/Farnborough, EGWU/Northolt. These would all be very good alternatives, but become unavailable pretty early. Let’s be honest: no business jet want to divert to EGLL/Heathrow or EGKK/Gatwick (costs, slots, friendliness, etc), and most cannot go to EGLC/London City due to training and approval. This is of course on top of Heathrow and Gatwick not accepting diversions most of the time, or not having slots available. Some airports outside London, although open and accepting traffic, do not have an FBO presence during the night, and this cannot be arranged at short notice for a diversion. Combining all of this in the very short timeframe of a diversion can be very tricky!”

There is a cool video that shows just how busy London does get on any given day….

If you have any further knowledge or recent experience to share, please let us know!

Extra Reading

• UK AIP – ENR 1.1 – Diversion

Typhoon Rumbia is expected to make landfall just south of Shanghai early on Aug 17, with gusting winds of up to 55kts.

Just as before with Typhoons Ampil and Jongdari which hit Shanghai earlier this month, both Shanghai airports ZSPD/Pudong and ZSSS/Hongqiao now have restrictions in place for GA/BA flights. They are advising the following:

1. All GA/BA aircraft currently parked at the airports must either go in the hangar or leave before 1000 local time on Aug 16.
2. All landing and parking requests of GA/BA aircraft are unlikely to be accepted until 1200 local time on Aug 18, by which time the storm is expected to have passed.
3. Operators should report outbound schedules of GA/BA aircraft currently parked at the airports as soon as possible.

Best to get in touch with your handler if you haven’t already.

And if you are in the region and have more information to share, let us know!

Extra Information and latest warning texts and graphics:

• Joint Typhoon Warning Centre