I recall one flight to an undisclosed location in South East Asia when I noticed the other pilot was carrying his passport in his front pocket. On asking why he was keeping it there and not his flight bag, the response was quite confronting – ‘in case something goes wrong, and we need to get out of here in a hurry…’

This got me thinking – every time we step foot in a foreign country, we are taking a risk – albeit a controlled one.

If we find ourselves on the wrong side of the law (guilty or otherwise), we are at the mercy of whatever legal system presides over us. This applies regardless of our nationality, the number of bars we have or even our preconceived notion of what constitutes a fair and reasonable legal process.

And pilots are maybe at higher risk – simply because of the sheer amount of time we spend abroad compared to the travelling public. You may not think it will happen to you, but even trivial offences can land us in hot water. If that happened, would you know what to do?

Guilty Until Proven Innocent

Perhaps the most likely way you may find yourself in trouble is in the aftermath of an accident or incident. Unfortunately, history has shown that in some cases the pilots become the default suspects regardless of who or what was at fault.

Take Nov 18 last year for instance, at Peru’s largest international airport, SPJC/Lima. An A320 collided with a fire truck during its take-off roll on an active runway. At the time, CCTV footage showed that for some reason a truck had entered the runway. Everything else was just speculation. Despite that, the crew of the A320 was immediately detained without charge.

The flight crew of this A320 was immediately arrested and detained.

This highlights a disturbing precedent – compulsion for authorities to act. Holding pilots responsible sometimes seems to be a knee-jerk reaction to allay the concerns of the public and an invasive media scramble that systems and processes had no part to play. Human error is the easiest explanation – after all, the pilots were there.

This is the risk that we are all taking, whether we are aware of it or not. We can very easily become scape goats. And with highly punitive investigations in some parts of the world, it’s no wonder we’re carrying our passports in our front pockets.

Wrong Place, Wrong Time

It isn’t just incidents and accidents though. Like the public, we can get also get caught up in the middle.

Around the same time last year, narcotics were found stashed in a maintenance bay of a Canadian CRJ shortly to depart the Dominican Republic. The drugs were discovered and dutifully reported by the crew to the authorities. Shortly afterwards, they were all detained – for months. There was no evidence linking any of them to the discovery, nor any charges laid.

The entire crew of this Canadian CRJ were detained without charge for months after drugs were discovered in a maintenance bay.

We can also find ourselves in trouble for exercising liberties that may be commonplace at home, but are still punishable abroad. Drugs and alcohol are obvious culprits, but this can also extend to our behaviour, preferences or even our freedom of speech in foreign countries. Then there are issues related to immigration. You and your crew can be held if there are issues with your paperwork, including visas and gendecs.

So what can we do?

On April 6, IFALPA published some guidance on what pilot associations, and individual crew should do if arrested in a foreign country. Here is a quick 2-minute summary:

Pilot Associations:

• Contact the local pilot association in the country where a pilot has been detained, and ask for help to get him or her released and out of the country asap. Failing that, look for legal assistance there or get in touch with the relevant embassy. Also contact the IFALPA emergency number +44 1202 653 110.
• Get in touch with the pilot’s employer and work along side them. You’ll also need to advise the pilot’s family – the big ticket advice here is to stop them talking to the media. If there is a lot of heat, you may need to help re-locate them.
• Likewise, unless you have media specialists on your team, don’t issue any statements.
• If practical, consider sending a rep to the pilot to assist. At the very least this would lift morale, along with providing a myriad of additional support.

Pilots:

• It may feel counter-intuitive but comply with the orders of police or authorities. Resisting arrest isn’t going to help. Make it clear you are willing to fully cooperate – but don’t make any statements until you have spoken to a lawyer.
• If you must say something, use the suggested safety phrase on the card below.
• Get onto your pilot association’s hotline without delay. If you can’t reach them, contact the IFALPA emergency number above. The sooner you get in touch, the sooner you’ll get help.
• Less is more – don’t volunteer or offer information, and never speculate on what has just happened. And for the love of Pete – don’t sign anything. Not unless it is written in a language you fully understand, and you have taken legal advice.

Quick Reference Card

IFALPA also recommend that associations produce a card or booklet with actions to follow if a pilot becomes incarcerated. Using IFALPA’s advice, we’ve put one together – it may be a good one for the flight bag. Click the image below for a downloadable PDF.

Click to download PDF.

Increasing military activity in the disputed South China Sea has been making headlines for civil aviation again recently.

We’ve seen reports of unauthorised clearances being issued over VHF, along with instances of GPS jamming. Here’s what we know, why it’s happening, and what pilots can do about it.

What’s your vector, Victor?

On March 2, IFALPA put out a new safety bulletin  – at the same time, several major carriers began to publish their own internal memos too.

There have been recent cases of civilian aircraft being contacted by Chinese military vessels on 121.5 or 123.45 and given vectors to avoid airspace above them. This has been happening not only in the South China Sea, but also the Philippine Sea and far eastern areas of the Indian Ocean.

In the eyes of aviation law, this is a big no-no. Unauthorised ATC transmissions are not only illegal, but highly dangerous because they can reduce your separation with other aircraft or lead to airspace busts. In this case the military vessels involved have no jurisdiction (or business) to be controlling aircraft in open airspace over international waters.

Military vessels have reportedly been broadcasting unlawful clearances to civilian aircraft on 121.15 and 123.45.

All the wrong signals

Then on March 20, reports emerged of another issue. Aircraft operating off Australia’s Northwestern coast have been encountering GPS jamming, purportedly from Chinese naval vessels in the area. This is unusual for the region.

The same problem has also been recurring over in the Western Pacific, and of course in the South China Sea itself.

Unfortunately, as we have seen in other parts of the world such as the Eastern Med, GPS signals are commonly interfered with in areas of high political tension as it makes it harder for the opposition to locate and gather whatever intelligence they are looking for.

It appears this region is no different.

Quit staring at me

So why is this happening?

We’ve written about the South China Sea dispute in detail in the past, and so this article may be a good place to start. But here is the thirty second version.

It may come as no surprise that the South China Sea is heavily disputed. Several states have staked some sort of claim on the region.

Disputed regions in the South China Sea. Map courtesy of AFP.

Attracting the most noise (and perhaps the most powerful claimant) China, has been steadily increasing its military presence in recent years including the construction of man-made islands, air bases and military warships.

All this activity attracts international attention, and the US military along with other countries have been keeping a close eye on what is going on – predominantly through aerial surveillance.

Herein lies the problem.

China maintains that under international law, foreign militaries cannot conduct intelligence gathering activities like surveillance inside its exclusive economic zone (or EEZ for short).

On the other hand, the US argues that under the UN Convention of the Law of the Sea (think of it as a legal rulebook for all marine and maritime activities), that freedom of movement through EEZs should be universal. And that essentially means that countries should not be required to provide notification of their military doings.

It’s worth pausing here – an EEZ is not the same thing as a country’s territorial waters. In the same document, the UN explains it is just a sovereign right to what is beneath the surface. The important part is this: the surface itself is still international water.

The result is lots of people looking, and some that don’t want to be seen which is why we are seeing interceptions, signal jamming and now unlawful clearances becoming more of a problem.

GPS Jamming is common elsewhere, but unusual in the Eastern Indian Ocean.

What can we do about it?

Essentially – protect yourself as best you can. These risks don’t look like they’ll go away anytime soonn, despite their disregard for civilian air traffic.

In their safety bulletin, IFALPA explains that IATA and ANSPs all recommend ignoring any unauthorised contact on the radio. Essentially, give them the silent treatment and continue on your cleared route. It is also important to let controlling ATC know immediately, and also to file a report.

Likewise, if you encounter GPS jamming it is also essential to let people know. You can read a little more about this issue here.

Let’s not normalise the risk

A recent high-profile interception in the region was described by a military official as just ‘another Friday afternoon on the South China Sea.’

These issues are no secret. But for civil aviation it is important we keep an eye on these trends and developments as our safety may depend upon it. The more present a risk is, the more comfortable we tend to become with it. We can’t allow that to happen.

OPSGROUP will continue to keep you updated with changes, along with our free conflict zone and risk database safeairspace.net.

**Update: April 12, 02:00z**

The launch has been delayed. It will now take place on April 17, with back up days on April 18 – 23. The new launch window will be from 12:00 – 15:05z each day.

——-

On April 10, SpaceX is planning on test launching a prototype re-useable superheavy rocket – Starship – from a launch facility in Southern Texas. The impact on the US NAS will be larger than most rocket launches due a reasonably high chance of failure of the ten million pound behemoth. Elon Musk himself has only given the launch a 50/50 shot of actually working. But he is ‘guaranteeing excitement’ either way.

The FAA are taking no chances, and on launch day several large hazard areas will be established for both liftoff, and subsequent reentry. This will impact coastal traffic over the Gulf of Mexico near the Texan coast, along with traffic in and out of Hawaii.

Let’s take a closer look.

Even Elon has only given the launch a fifty percent chance of working…

Launch

Liftoff will take place from a facility in Boca Chica, on the coast of Southern Texas.

The official launch date is April 10, with April 11 and 12 standing by as back ups. The action will take place between 12:00z and 16:00z (07:00 – 11:00am LT) each day.

In addition to a TFR extending 12nm off the coast from the launch site itself, for the ascent there will be two large hazard areas established well out into the Gulf of Mexico protected by Altitude Reservations.

Several airways off the coast will be impacted – primarily for those running north and south between the mainland US and Southern Mexico. Major ones include L207, L208, A766, A770, L214, and L333 impacting boundary waypoints IPSEV, DUTNA, KEHLI, IRDOV and PISAD between the KZHU/Houston Oceanic and MMFR/Mexico FIRs.

The good news for east/westbound traffic is that the hazard areas are fairly narrow, which means for the most part those published tracks will avoid the worst of the disruptions.

Additional congestion will be felt on alternative routes  – especially for aircraft transiting to and from Florida’s airspace via waypoint CANOA, and inland of the Texan Coast.

Reentry

Because this is simply a test flight, the rocket will reenter again on the same day as the launch, this time affecting Hawaii.

The reentry window is set for 13:10 – 17:45z (03:10 – 07:45 LT), with a hazard area established in a line from just north of the island group, extending well west into the Pacific.

Three airways connecting to the mainland US will be affected – A331, R463, R464 with transitions via waypoints ZIGIE, APACK and BITTA. There is also a Guam-bound airway to the west that will be impacted – A450 via the transition BRIUN.

Mission Accomplished

Once the mission is complete, the airspace will be returned to the US NAS and we’ll be back to ops normal. Likewise if the mission is scrubbed, the airspace will be opened up again and the launch rolled over to back up days.

If you’re tired of space related disruptions, we feel you. In fact it is a growing issue now that we’re having to share the skies with competing interests. We wrote an article on that very issue, which you may find an interesting read.

For more on this upcoming launch, see the official FAA briefing here.

On Feb 23, the US FAA re-issued its warning for overflights of Mali, with one essential difference:

It is now dangerous to overly Mali’s airspace at all levels, not just below FL260.

Here is what the new KICZ Notam says:

So what’s changed there, and why is the FAA so concerned?

The Stage

Mali is a large land locked country in Central Western Africa and borders several states including Niger, Algeria, Mauritania, Guinea and Burkina Faso.

Several major high altitude airways run through the country facilitating traffic both north and south, and east and west. They are major thoroughfares through the heart of Africa, which is why this new warning is significant.

Mali’s borders (blue) do not match the FIR regions for the airspace (red).

In the past three years Mali has suffered from continuous political instability after two armed coups – the first in 2020, and then again in 2021. This has been compounded by delays in holding an election.

It was dropped from ECOWAS (Economic Community Of West African States) as a result, and has faced several international sanctions. 

It has a long history of insurgent militant activity who oppose the government, along with the intervention of foreign military to try and restore peace and stability.

Despite best efforts, insurgent militia have continued to spread and strengthen in Mali allowing well funded groups such as Al Qaeda to increase their presence there. Military operations and terrorist attacks have become more frequent.

Of special concern is the fragmented tri-border region that divides Mali, Burkina Faso and Niger. It is a hotspot for fighting that targets both the existing government, along with the foreign military presence.

What has changed?

Hot on the heels of the new KICZ Notam, the FAA has published a new information note which raises major red flags to anyone considering overflights.

Historically the concern to aviation in Mali has been from militant use of MANPADs (man portable air defence system) to target low and slow flying aircraft up to FL250.

However as the transitional government continues to fight against insurgent militia, their emphasis has moved from the support of foreign peacekeeping forces to the use of private military. One in particular is of major concern – the Wagner Group.

In Spring last year, this Russian backed paramilitary group has deployed over one thousand troops in Mali near Bamako, along with an advanced radar guided air defence system capable of targeting aircraft as high as FL490. A similar system was used to shoot down MH17 in 2014.

This radar guided system is now present in Mali, which can target aircraft as high as FL490.

While there may be no specific intent to target civilian traffic, the FAA suggests the Wagner Group have a sordid history of unprofessional and heavy handed air defence activity. This was previously evident in Libya, where US operators have been completely banned for some time.

What we’re now seeing in Mali is that civilian aircraft may be at far greater risk of advanced anti-aircraft fire through mistaken identity or mis-targeting, which can likely reach higher than you can fly.

The risk is now two-fold.

The existing risks are still present – militant groups continue to be active with MANPADS. They are likely to target foreign and local military forces which are often located close to international airports including GABS/Bamako.

MANPADS are a known risk in Mali, and typically endanger aircraft flying low and slow. Landing and take-off are especially vulnerable times.

At higher levels, aircraft are now at risk from radar guided air defence systems that may be used with little verification that their target is correct.

It is a dangerous brew.

Why the FAA has only cautioned US operators, rather than ban them as is the case in Syria, Libya and Iran among others where similar weapons are also present is a question we don’t have an answer for yet.

We are actively seeking more information.

I still want to overfly. Can I?

Yes you can, but it’s dangerous at all levels. Once again, the new Notam is a precaution, not a ban. The new KICZ Notam allows room for you to do so, provided you:

• Take into account all current security and airspace warnings and perform your own risk assessment.
• Comply with and update your OPSPEC/LOA B450 approval to operate in internationally sensitive ares.
• Where possible, provide the FAA with at least 72 hours notice via FAA-WATCH@FAA.GOV
• Report any safety or security issues ASAP to the FAA on +1 202-267-3333.

Where to from here?

We will report on any new FAA information on the situation in Mali as it becomes available, along with any other security or risk alerts. These will be published on OPSGROUP, along with safeairspace.net – our free risk and conflict zone database.

Did you know that cow farts are one of the major contributors to global warming?

Go ahead – google it. Just know that your search history will take some explaining later.

In fact they account for eighteen percent of the problem. They’re flatulent creatures, and their trouser coughs contain methane gas which is almost one hundred times more powerful at trapping heat than good ol’ carbon dioxide. In fact their flatulence is so strong, it can cause acid rain. Umbrella anyone?

Why are you reading this on an aviation website? Fair question.

Because regardless of where you stand on the cause of global warming, we know for a fact that the earth is heating up. And aviation is poised to be one of the victims.

Regardless of the cause, the figures don’t lie…things are heating up.

Let me explain.

Bumpy Road

As the earth warms, jet streams will become stronger – along with wind shear. As we hitch a ride on those long routes eastbound, clear air turbulence is set to become much more frequent, and much more dangerous.

They’ve done studies, you know – and those jet streams are already fifteen percent more sheary than they were back in the 70s. And things are accelerating.

Jet stream related wind shear is already 15% stronger than the 70s…

The bottom line is this: scientists believe there is going to be two to three times as much severe turbulence in the next few decade thanks to cow farts (and of course all other contributing factors).

How severe is severe?

We’re not talking light chop.

There are two levels of turbulence we’re most concerned with. The first is severe – essentially large and abrupt changes in altitude or attitude. Your aircraft may even be out of control momentarily.

Beyond that turbulence can also be extreme. It doesn’t make for pleasant reading, but the official definition is when the aircraft is violently tossed about and almost impossible to control. You may even take damage.

Both are nasty.

The increase in reports of severe and extreme turbulence are cause for concern.

What does this mean for ops?

Perhaps the most at risk are flight attendants. The NTSB reckons they are twenty-four more times more vulnerable to injury from CAT than their passengers. They account for eighty percent of all turbulence related injuries. This make sense as they are often on their feet, pushing carts that can weigh upwards of 300lbs.

Here’s another startling statistic – between 2009 and 2018, in almost thirty percent of turbulence related incidents, there was no warning.

CAT is the enemy you cannot see, because it mostly happens in clear air. It isn’t associated with storms or clouds, and weather radars need moisture to work. Our eyes are useless too.

Granted, planes aren’t about to start falling from the sky. But we can expect the amount of time spent in turbulent conditions on an average flight across the Atlantic to exceed thirty minutes in the years to come. Darn cows.

Great, what can we do about it?

Actually three things. Protect your crew, predict where it will happen, and care about sustainability. Let’s dig a little deeper.

Crew

The absolute best way to protect everyone on board during CAT is to have them seated with their belts on. The head of a major flight attendant union is calling for changes. It is becoming increasingly dangerous for them to still be on their feet, while passengers are strapped in.

The NTSB agrees and is recommending more stringent rules when those seatbelt signs turn on – especially for crew. The notion is a seat for everyone – including infants and young children who may be sitting on an adult’s lap and riding gratis.

While it may feel reassuring that all pax are safely seated, don’t underestimate how at risk cabin crew are if they are still up and working.

Unions and the NTSB are calling for stricter rules when the seat belt signs are on in flight.

Spotting the stuff.

Predicting CAT isn’t an exact science, and this ain’t no met class. But in a nutshell it is caused due to the difference of speed at high altitude (usually well above FL150) when flying near the boundary of two air masses.

Jet streams are typically strongest in colder months, and weaker in warmer ones.

Two things to look out for: dramatic changes in temperature, and dramatic changes to wind speed and direction.

Both are tell tale signs of CAT.

Along with that information in your flight plan, shear rates, sig wx charts and pilot reports (pireps) are also valuable sources of information.

Likewise, if you find some let ATC (and the traffic around you) know.

There are also turbulence information sharing platforms available to crew which provide real time updates on where the rough air is.

Sustainability

There is a lot of noise at the moment about sustainability, alternative fuels and ‘net carbon zero.’ It can all get a little dry.

But it is the operational impact of global warming that is really going to matter to us on a day to day basis, which is why we need to care. More than numbers.

Asides from clear air turbulence, as the jets grow stronger, westbound flights will take longer, burn more fuel and cost more. Not to mention more time away from being poolside at the Holiday Inn.

Then there’s the sea level. It is rising as the polar ice cubes melt. One study suggested by 2100, one hundred airports around the world will be below sea level, and close to half a thousand will be at serious risk of flooding and storm surges unless things change  – affecting up to twenty percent of all routes. That’s a lot of water.

Where to from here?

Don’t be mis-steakin, that air will keep on moo-vin.

The cows aren’t about to stop farting, so we need to mitigate. This may mean spending more time and attention on the risk that clear air turbulence poses while we flirt with the time saving benefits of the world’s jet streams on a daily basis.

We can also support the overall industry push to operate cleaner in the long run. A great no-nonsense source to keep track of these industry trends are IATA updates – you can view those here.

On Jan 24, the Rwandan military shot at a fighter jet from the Democratic Republic of Congo which they claimed had busted Rwandan airspace near Goma.

This has captured our attention for three major reasons:

• There are no active airspace warnings for either the FZZA/Kinshasa or HRYR/Kigali FIRs.
• The incident occurred at low level, but in an area of open airways.
• The aircraft was hit in close proximity to an international airport.

This was a major escalation following months of conflict between the two countries – so much so that the DRC announced the shooting as an ‘act of war.’

Here’s a look at exactly what happened and what this might mean for risk to civil aviation operating into, or overflying the Central African region.

The January 24 Incident

During daylight hours, a Sukhoi-25 military jet operated by the Democratic Republic of Congo reportedly violated Rwandan airspace between Goma and Gisenyi, without a clearance.

There are several unverified videos circulating of the jet being struck at low level by a surface-to-air missile, fired from a MANPAD. These are small, light, shoulder launched anti-aircraft weapons

The jet landed safely but sustained heavy damage. The incident raises concerns because there are contradictory accounts of how the situation unfolded, debate over which side is responsible, and so a lack of reliable information over what the safety implications might be for civil aircraft.

The jet was damaged but landed safely.

Escalating Conflict

This is the latest escalation of a conflict that has been worsening for months, and a strong indication that it may be putting overflying aircraft at risk as it grows – especially near the shared border.

In late 2021 heavy tensions erupted between the Democratic Republic of the Congo and Rwanda. An armed insurgency is underway in the DRC by a recently re-emerged militant group known as the March 23 Movement (or just M23 for short).

The DRC (along with the US and UN) have accused Rwanda of supporting M23, and in some cases even fighting alongside them. Although this hasn’t been proven.

The ethnic and political background to the conflict run deep and are beyond the scope of this article, but the bottom line is frequent skirmishes by both Congolese and Rwandan forces in each other’s territory.

Skirmishes on both sides of the shared DRC/Rwandan border have been reported.

Airways

The January incident happened near Goma – a city that lies on the DRC side of the border, and straddles the boundary between the FZZA/Kinshasa and HRYR/Kigali FIRs.

Several international airways run through the same airspace where the incident occurred.

Also use caution on airways UM216, UA618 and UL442 away from Goma but which skirt the shared border where skirmishes have been occurring.

Is this a high or low-level threat?

Short answer, low – but there’s more to it than that.

Militaries from both sides, along with the M23 rebels, are all known to have anti-aircraft weaponry.

The most common is the MANPAD. They are easy to use, portable and require little if any training. They are unfortunately prolific throughout Africa in both legitimate and illegitimate hands – Rwanda and DRC are no exception. And the intent to use them is now clear.

They typically target aircraft flying low, and slow. Which means aircraft taking-off and landing are most at risk. However publicly available information indicates MANPADs can reach aircraft as high as FL250.

Anti-aircraft guns along with ballistic weapons such as rockets and other artillery are also known to be present, and are potentially dangerous to aircraft, once again at low level.

Neither side has shown any intent to actively target civilian aircraft. But there are several risk factors at play.

The DRC/Rwandan border is an active conflict zone, where military activity and the transport of troops and equipment is common. Aircraft surveillance in the area is rudimentary, and the conflict has become territorial not just on the ground, but now in the air too.

All the warning signs are there, only with no actual warnings.

Once again, mistaken identity has become the number one threat.

With this in mind, overflying jet traffic at higher flight levels are not at risk – if ops are normal.

The problem becomes if you need to descend or divert. And aircraft operating into the region’s airports are especially exposed. Extra caution needs to be taken at FZNA/Goma – the site of the January incident.

Official Warnings

There are none.

History has taught us that we need to be more responsive to airspace threats – a danger may exist or develop before states publish official airspace warnings or restrictions. All of that takes time. And if your flight is today, you need to know now.

We’ll continue to report on changes in Rwanda and DRC as they happen over at safeairspace.net – our conflict zone and risk database.

It’s time to stock up on chicken wings – Super Bowl LVII is just around the corner.

This year, kick-off will be in Glendale, Arizona on February 12.

Airports within the area will be extremely busy – not just in Arizona, but across the state line in Nevada too.

The FAA are onto it, and have published their safety plan for the event. If you’re flying into (or near) the game, here’s what you need to know.

Parking

A ramp reservation program is already open (including for drop-and-goes) for airports in the Phoenix area from Feb 8 – 14, along with those in Las Vegas. Essentially, you have to reserve a parking spot in advance during this period.

This includes the following airports:

Arizona

• KPHX/Phoenix Sky Harbor
• KSDL/Scottsdale
• KDVT/Phoenix Deer Valley
• KGEU/Glendale
• KGYR/Goodyear
• KCHD/Chandler
• KFFZ/Falcon Field
• KIWA/Williams Gateway

Nevada

•  KLAS/Las Vegas
• KVGT/North Las Vegas
• KHND/Henderson

Who to talk to for your reservation

Talk to your FBO (sooner rather than later). They are the ones with the slot allocations and will be able to keep you updated on any changes nearer the time. No FBO? You can also get in touch with the airport authority directly.

If previous Super Bowls are to go by, parking will be a major issue.

There will be Special Air Traffic Procedures

Expect traffic jams and hold ups. To help keep things flowin’, ATC will implement the usual culprits including ground delay programs, holding, reroutes, miles-in-trail and other restrictions.

Your best defence will be to avoid arriving and departing at peak periods.

These are expected to be between: 07:00am to 19:00pm local (14 – 00z) daily between Feb 8 – 13.

A head’s up that it can also be extremely busy for departures on game day well into the wee small hours of the morning too. Last year over one hundred and fifty jets had already left the LA Basin area within five hours of the game ending.

Also beware that ATC will not allow aircraft to pick up IFR clearances airborne, or change destinations within 200nm of Phoenix Terminal airspace.

Security

Two TFRs will be established on February 12, centred around State Farm Stadium in Glendale, approx. 7nm northwest of downtown Phoenix.

Those details will be published via the FDC Notams, usually 3-5 days before kick-off. But you can expect standard stuff – a very restrictive 10nm inner ring, and a less restrictive one out to 30nm.

There should be minor impact for IFR aircraft but expect additional communication requirements and discrete transponder operations.

You can expect two TFR rings centered around State Farm Stadium – don’t use this to navigate though, the real deal won’t be published by the FAA until a few days prior.

Getting in and out

There are preferred routes for all IFR turbojet aircraft arriving and departing the Phoenix area from 17z Feb 10 until 23z Feb 12. You can view those here.

The FAA has also summarised tower hours for major airports near the event, many of which will be extended.

For real time info on delays, airport status and other flow related issues, the FAA NASS website is the place to check.

Other stuff to think about

Consider your alternates. Options are going to be limited and restricted because of the high traffic levels. Unless you have a bona fide emergency, you’ll need to plan ahead.

Gas Up. With all the traffic management programs in place, there could be lengthy delays. Consider extra holding and taxi fuel.

Check your documents. Make sure you have everything you need onboard, including crew licences, medicals, aircraft docs and confirmation of all reservations and confirmations. Increased security measures may involve ramp checks, searches, or other TSA requirements.

One last thing…..chicken.

It’s just not Super Bowl weekend without wings. Looking for the best ones in Phoenix? This article may help.

On Dec 26, several North Korean drones entered South Korean airspace. Ops at both RKSI/Seoul and RKSS/Gimpo were disrupted while military jets were dispatched to intercept them.

While it’s no secret that North and South Korea don’t get along, this is the first drone incursion in the RKRR/Incheon FIR in half a decade. And it didn’t go down well. So much so that there is now talk of ending a military pact that has stood since 2018 – especially if there is another incursion.

From an aviation standpoint, this has potential to spell trouble as it threatens the status of a military no-fly zone that buffers the two countries. In which case, the risk to aircraft in the skies of South Korea could deteriorate quickly – especially anywhere near its northern border.

In the absence of any active airspace warnings, here’s what you need to know.

The Dec 26 Incident

At around 10:30am local time, at least five North Korean drones entered South Korean airspace over the Military Demarcation Line near the city of Gimpo – just northeast of Seoul.

It appeared to have caught South Korean military by surprise, who temporarily suspended ops at RKSI/Seoul and RKSS/Gimpo to scramble military jets to intercept them. They fired at least one hundred rounds at the drones supposedly as warning shots.

There are no reports that any of the drones were shot down. One returned to North Korea, while the status of the other four isn’t known.

This has attracted some negative shade in the media, where some felt that the military’s response was inadequate.

In the days that followed, South Korea responded by sending surveillance aircraft into the ZKKP/Pyongyang FIR. The South Korean president has also said that the drone incident could cast serious doubt on a military pact between the two countries – the one that protects border airspace from military incursions.

North Korea’s recent ballistic missile tests haven’t helped either – in recent weeks several unannounced launches have taken place with scant regard to civil aviation. The past twelve months have seen a huge upswing in these types of incidents, at one point triggering a ground stop on the US West Coast. And they send a very clear message to South Korea.

A flurry of North Korean missile tests in December has also increased tensions.

Political Posturing

So, are we about to see an outright conflict? Probably not, but ‘quid pro quo’ can be dangerous, especially where airspace is being used as the stage.

Add to that the potential for increased posturing on the border and civil aviation needs to take note. Mistaken identity and mis-targeting is a very real threat. This will escalate should the agreement which upholds the demilitarised buffer zone between them get dismantled.

Previous Airspace Warnings

The FAA has previously had warnings in place for the RKRR/Incheon FIR, but they have long since expired.

The first related to unannounced North Korean missile tests and regional instability. The second was a Notam on GPS interference that was cancelled back in 2019. It was purely advisory – that caution should be taken near the border as the signal may be interfered with.

Since then, things have been quiet. But it is worth keeping in mind that operations in and out of Seoul particularly, are only 30nm away from the demilitarised zone. And beyond it lies the ZKKP/Pyongyang FIR, where US operators are currently banned at all levels.

You can check Safeairspace.net for a summary of the airspace risk, including warnings issued by each country.

What does the South Korean AIP say?

Essentially, don’t stray north.

There is a large area of prohibited airspace which runs along the military demarcation line – a strip of land around 2.5 miles wide which acts as a buffer between North and South Korea more or less defined by the 38^th parallel.

No aircraft can enter the area at any level, 24 hours per day. As it is just north of RKSI/Seoul, operators there are advised to give it a wide berth. So much so there is a note to exercise extreme caution in a sector of airspace north of the field. You don’t want to bust it.

As a general rule, the military can impact civil aviation operations without prior notice. This is precisely what went down on December 26.

Where to from here?

We watch and wait. Tension on the Korean Peninsula isn’t new – but the December 26 incident is a reminder of just how volatile things can be at short notice. Should the military pact between the two countries genuinely implode, the risk to civil aviation could change overnight.

There’s mixed news from China.

On the one hand, it is finally about to get rid of quarantine on arrival. On the other, Covid is surging badly. Which means that nations around the world are beginning to introduce new rules for people who have been there – including the US.

News from the US is that from Jan 5, all passengers will need to provide a negative Covid test, or proof of recovery, to board a flight to the US.

Here’s everything you need to know.

What’s going on in China?

Its zero-covid strategy is being abandoned amidst sky-rocketing case numbers. So much so that it is estimated that up to forty percent of its 1.4 billion have had it.

It’s not panic stations yet though, as the same path has been well-trodden by other countries in the past twelve months. But there is international concern over the accuracy of the statistics being reported, and more importantly the tests that identify new or potentially dangerous strains of the virus that might emerge.

Which is why we’re seeing new rules again for passengers who have been there.

Ironically there has also just been a big announcement that anyone headed to China no longer has to quarantine from Jan 8. Which means demand for travel back to the US for those who return is about to soar.

Enough of that. What’s the impact?

From 00:01z on January 5, anyone allowing a passenger to board a flight from China to the US will need to see proof of a negative Covid test taken within two days of departure, or certified proof of recovery that is less than 90 days old.

The rule will apply to all flights from mainland China, Hong Kong and Macau including GA/BA flights.

It will apply to all passengers, including US citizens, regardless of vaccination status.

You can check the official announcement of all this from the US here.

The new US rule applies to arrivals from Hong Kong and Macau, as well as mainland China.

What type of tests will be accepted?

Viral tests that have been approved by the CDC.

Self-tests (including rapid antigen) are allowed, but must include at least a tele-health service to oversee the test, and certify the results along with the traveller’s identity.

Pax will be able self-test, but it will need to be monitored by an official health agency.

I’ve just had Covid. Do I need to test?

A certified proof of recovery is also acceptable, provided it meets two requirements – it has to be more than ten days old, but no more than 90.

I’ve only transited through China, do I still need to test?

No, provided passengers have stayed airside, they do not need to meet the new requirement.

What about crew?

Good news, you will be exempt. But you’ll need to be either operating, or positioning on the aircraft. It’s recommended you travel with a letter (paper or electronic) from your employer certifying you meet the requirements of the exemption. Another option for deadheading crew is that they are included on the gendec.

If you’re commuting, travelling for training (such as sims) or flying for other business reasons, bad luck. You will need to meet the same requirements as passengers.

Another gotcha.

The rule is also extended to passengers who have been in China, Hong Kong or Macau in the past ten days, and are arriving on flights from RKSI/Seoul, CYYZ/Toronto or CYVR/Vancouver.

What is the rest of the world doing?

It is likely we’ll see similar testing rules introduced globally, at least in the short term.

Several countries have already announced similar restrictions to the US: Canada, UK, France, Italy, Spain, Australia, India, Japan, Malaysia, Taiwan, South Korea, Morocco.

The good news is that there doesn’t appear to be any suggestion of quarantine or entry bans being added back to the mix. Just typical uncertainty of a pandemic-weary world. But we’ll continue to report on major changes that might affect you operationally as we see them.

If you’re headed to China, we recommend calling ahead.

Especially for crew.

Weren’t expecting to be trussed up like the xmas turkey? We need to hear from you!

China has had some of the most confusing and inconsistent entry rules since the start of the pandemic. They seem to vary from port-to-port. With the promise that crew no longer need to quarantine on a widespread scale, we’d love to hear from you if you’re headed there – especially if you encounter something you weren’t expecting.

Border Force workers are planning to strike at several major UK airports from December 23 – 31. In some case the impacts are expected to be major, and will affect GA/BA operations along with scheduled airlines.

Here’s a rundown of everything we know so far.

What’s happening?

The UK’s Border Force union has announced one thousand workers will strike over the holiday period amidst an ongoing dispute over pay and conditions.

It goes without saying it is a busy time of year – ten thousand flights, and hundreds of thousands of passengers, are set to be directly affected. The Government has rushed to bring in military staff, civil servants and other volunteers to temporarily try and take up some of the slack.

Which airports are affected?

Six big ones:

• EGLL/Heathrow (Terminals 2 – 5)
• EGKK/Gatwick
• EGBB/Birmingham
• EGFF/Cardiff
• EGPF/Glasgow
• EGCC/Manchester

Signature FBO advise that impacts will be felt at all airports, but EGLL/Heathrow looks set to be the most heavily affected.

There will be strikes at six major UK airports.

Dates and Times

The strike action will be 24 hours a day, with the exception of December 26 and 31, where it will end at 7am.

What will the impact be?

Passengers are likely to experience extensive delays through passport control. For FBOs, it is important to advise them of your planned arrival as early as possible so they can make arrangements. They may struggle to find available staff to attend to you and your passengers.

Inbound aircraft may also be hit with traffic jams leading to extended holding and possible diversions.

On December 22, the UK CAA published the following Notam:

The moral of the story seems to be to take more fuel.

If you do find yourself in a queue and low on gas, they want you to be familiar with the correct terminology with ATC to get the message across. The Notam above references the following three docs:

UK CAA Safety Notice – Protecting Final Reserve Fuel and The Minimum Fuel Declaration.

UK AIC W084/2022 – Diversion Requests in UK Airspace.

EASA Safety Bulletin 2018-08 – In Flight Fuel Management.

I don’t have time for that. Just give it to me straight.

The docs all deal with unanticipated delays and give a reminder that it is up to the crew to monitor fuel in flight and advise ATC if they will be landing with minimum legal reserves, or less.

There are two ways to do it:

Say ‘minimum fuel.’ This isn’t an emergency, but you’re already landing close to final reserve fuel. You cannot accept any further delays without chewing into your FRSV.

Declare an emergency, ‘Mayday, mayday, mayday fuel….’ The rule is pretty clear cut on this one. If you will be landing at the nearest suitable aerodrome with less than your planned reserve fuel, you must declare an emergency.

There is also some guidance on how to request a diversion. In a nutshell, ask for it early. The CAA advise it takes ATC 5-10 minutes to grant a request, sometimes longer. Behind the scenes, there are phone calls to be made.

It is also not uncommon in the UK for a requested diversion to be refused – it is at the aerodrome operator’s discretion. Stand availability, handling and other factors all come into play. They recommend operators pre-arrange their options for diversion.

Bear in mind the weather is also a challenge at the moment and may compound the situation!

More Information About the Strikes

The UK FCO has the official word. You can find it here.

We’ll Keep You Updated

We’ll update this article, along with any operational impacts, as more info comes to hand. If you experience disruptions yourself, we’d love to hear from you. You can reach us on news@ops.group

On November 14, a major runway incursion was narrowly avoided involving an Airbus A380 and Boeing 737. It sounds like the incident may have been caused by an ATC error – although an ATSB investigation is still underway.

Despite millions being spent in recent years to improve runway safety at the airport, this incident is a timely reminder that incursions can and will continue to happen in Sydney.

Here’s a look at why, and what you can do about it.

The Layout.

Sydney’s runway layout is complex. There are three runways – two parallel ones (16/34 LR) and another runway that runs perpendicular to them (07/25). The airport itself sits perched on the edge of Botany Bay, with the parallel runways extending well out over water. And all terminals and FBOs are found clustered together on the northern side of the airport, near the 16R threshold.

Which means taxis to/from all the other runways are lengthy and potentially confusing. And during those taxis, almost every aircraft will need to cross a runway. Often twice.

That’s a lot of crossing traffic when you consider that the airport processes up to eighty movements an hour at peak times – it is literally Australia’s busiest.

Mistakes Happen.

Authorities are well aware of the risk of runway incursions at Sydney airport. So much so that they have spent a commendable amount of time and money to improve runway safety.

Possibly the best advancement in recent years has been the installation of stop bar lighting at every single runway holding point, along with improved signage and markings.

And yet mistakes keep happening. The November incident is a great example – here’s what went down.

The November 14 Incident.

• In CAVOK conditions, a Boeing 737-800 was cleared to land on Runway 25. With their clearance they were informed that an Airbus A380 was holding position on Runway 34 waiting to depart.
• When the 737 had cleared the intersection of the two runways, the A380 was cleared for take-off and began to roll.
• After landing the 737 received its taxi clearance from ground which instructed them to cross runway 34L on Golf back to the domestic terminal.
• As the 737 crew approached the active runway, they were surprised to see it was still occupied with the departing A380. They queried the clearance with ATC who immediately told them to hold short.
• The closest the two aircraft came to each other was 300m (just shy of 1000’) thanks in part to the vigilance of the 737 crew. While not a particularly close shave, there was potential for this to have become a major accident. Which is why the ATSB are asking questions they are.

Here’s a simple animation of the incident with a bird’s eye view:

What can we learn from this?

Future incursions, although rare, will happen. But there are steps that all crew can take to help reduce those statistics and stay safe.

A good place to start is this. To cross a runway in Sydney always remember the ‘hat-trick.’ You know all about cricket right? Well if you’re headed to Australia, this phrase can also be used to impress Aussies at the bar over a cold Fosters  (disclaimer: no one drinks it there, and whatever you do never call a prawn a shrimp). It means three successes of the same kind. Or in other words: a set of three good things.

So, there are three things that you’ll need:

• A clearance from ATC
• Confirmation that the stop bar is out
• Runway is visually clear out both sides

If any of them are missing (or uncertain), do not enter the runway.

The crew of the 737 above captured a potential accident because at least one of their hat-trick was missing.

Remember the hat-trick every time you cross a runway.

The stop bars themselves are worth a mention too. What’s more obvious than a big row of blazing hot red lights to make you get on the brakes, right? They work really well, but in their simplicity, there can be confusion.

A while back, IFALPA released some pretty good stuff that is still relevant today. You can read it here, but there are a few scenarios to take away:

The stop bar’s out, but we haven’t been cleared…
Stop. An extinguished stop bar on its own is not an indication you are cleared to cross. It may have been turned off in error, or for a preceding aircraft.

We’re cleared, but the stop bar is still lit…
Yep you guessed it, stop. And this happens really often. You’ll need to ask ATC to turn it off. Never, ever cross a lit stop bar.

But didn’t he say we were cleared?

Help from ICAO

Did you know they have a whole manual dedicated to helping controllers and pilots alike avoid runway incursions? You can download it here.

Have some stories of your own to share?

We’d love to hear from you. They don’t need to be from Sydney, but we can all learn from them. You can reach our team completely anonymously at news@ops.group.

If you’re bound for Bali there are a few things you need to know, especially if it is your first time there. Ops there often seem to get disrupted, and you’ll need the option of having someplace else to go. Figuring out where – especially at night – may be harder than you think.

Let’s take a closer look.

At face value, ops at Bali seem straight forward. The runway is long, there is an instrument approach at both ends, SIDs and STARs link everything up and the place is towered 24/7.

But after years of flying in there with a scheduled operator, the number one biggest threat remained fuel in the tanks when it all went pear-shaped – which it sometimes did.

The airport just seems to have a habit of eroding your fuel margins. You may be carrying a healthy alternate enroute, but beware of giving it all away while holding once you arrive.

Delays and short notice closures.

The airport is especially vulnerable to them, and they can be unpredictable. Here’s why.

 1. Weather 

If you’re flying into Bali during rainy season (November – March), weather is likely to be a major factor. Like clockwork, towering cumulus clouds strengthen throughout the day into powerful thunderstorms in the afternoon and evening.

While the TAF may look identical day in and out, it is luck of the draw whether the airport itself will be affected. And when it is, traffic backs up quickly.

Severe thunderstorms are common in Bali during the wet season.

 2. Volcanic Ash 

Indonesia rests on the western portion of the Ring of Fire which renders it the third most volcanically active region on earth. There are no less than one hundred and forty-seven volcanoes there, seventy-six of which are currently active.

Eruptions are frequent and occur with little warning causing major disruptions to airports throughout the country – and extensive ash plumes. They can close airports like Bali for days on end, like one did in 2017. And the situation can develop when you’re already airborne.

The closest volcano to WADD/Bali airport is less than 40nm away.

Mount Agung erupted in 2017, closing Bali for several days. Courtesy: IBTimes UK

 3. VIP Movements 

Yep, someone important is inbound. And guess who has to make way? The airport often gets closed for short periods for VIP movements. You’ll find them in the Notams from time-to-time. Take it from me – apply a healthy buffer to either side as ATC will not necessarily be able to provide you with an accurate time the airport will re-open while you’re racing around that holding pattern.

VIP movements can occasionally close the airport.

4. Traffic Jams 

WADD/Denpasar is Indonesia’s second busiest airport second only to Jakarta. Which means it sees a lot of traffic. It also occupies a busy air corridor linking Europe to Oceania. Controllers manage a steady flow of both regional and international traffic from both directions.

It can be difficult to predict the effect of this ahead of time, but it is not unusual to hold inbound on your STAR. And you likely won’t have a head’s up beforehand that it is coming. Extra fuel for traffic holding is absolutely necessary.

 5. Congested Frequencies 

If you’re getting low on fuel, make a decision early. Don’t wait.

ATC has to manage large pieces of airspace here. On Ujung especially it can be challenging getting heard. Controllers are often managing multiple frequencies – it may seem like you’re being ignored, but you may not be able to hear everyone else talking to controllers over the top of you.

The language barrier can also be an issue – English will likely not be your controller’s first language, and their accents can make them hard to understand. The moral of the story is to be assertive on the radio, and speak slowly and clearly. Try and stick to standard phraseology such as ‘minimum fuel.’ And don’t take a back seat when trying to get an urgent request granted.

But where to go?

If you’re heading into Bali late, you’ll need to pay special attention to alternate planning. All the airports in the region still have special operating hours in place to “avoid the spread of Covid”, as per their notams. At present, WADD/Bali itself is open until 18z (02:00am local) but its closest alternatives are not.

Lombok (WADL/Praya), 85nm. Closed each night from 12z (20:00 local). [Notam B2226/22, valid until Feb 19].

Surabaya (WARR/Juanda) , 160nm. Closed each night from 14z (22:00 local). [Notam A2938/22, valid until Feb 18, actually due to runway closure for works].

Semarang (WAHS/Semarang), 295nm. Closed each night from 12z (20:00 local). [Notam B2231/22, valid until Feb 18].

If it’s late, you’ll need to carry more fuel than usual to reach WAAA/Makassar 320nm away, or WIII/Jakarta 512nm away.

Three of Denpasar’s closest alternates close at night.

And finally – watch out for terrain!

There are some big hills out there. If you’re flying into Bali, there’s a good chance you may yourself under radar vectors at night or in IMC nearby. Protect your aircraft – keep a close eye on where you are relative to that terrain at all times. Especially when it’s busy!

Aircraft arriving from or departing to the northwest need to be particularly wary. Sector MSA just north of the airport rises steeply to 9700’. Further west you’ll find Central and East Java with grid MORAs as high as 14,000’. Also be aware of escape routes if your cabin springs a leak.

On August 3, the FAA put out a new Safety Alert (SAFO) for KDEN/Denver. Here it is if you want a read.

The issue is the high number of TCAS alerts being recorded when aircraft are shooting parallel approaches to Runways 16L/16R.

It turns out that TCAS, high elevation, and reduced separation aren’t a great mix, and the FAA are worried there are chances of a collision.

Here’s a breakdown of the situation.

Elbow to Elbow.

Since 2004, KDEN has been operating two parallel runways (16L and R). The two runways sit literally elbow to elbow, with only 2600’ (709m) between them. For simultaneous close parallel approaches, 3600′ separation between runway centrelines is generally required. In Denver, typically two separate controllers are feeding traffic onto the approach cones for each runway, which means coordination can be a challenge.

From early on it became apparent that nuisance TCAS alerts were a problem. The FAA sought to fix the issue, and so in June 2019 Denver TRACON started separating aircraft vertically by 1000’ in case someone busted through a localizer.

Trouble is, this didn’t fix the issue. Instead, now the majority of TCAS events are happening when aircraft are established on the final approach course. The big threat here is the number of folk selecting TA only (a good 20%), and there is now a healthy dose of desensitisation thrown into the mix from so many nuisances warnings in the past.

The trouble runways.

Then there’s the elevation.

Fun fact: TCAS becomes more sensitive with altitude. Or in other words, the trigger thresholds for both TAs and RAs increase the higher you get.

Enter Denver – the ‘Mile High City’ – called that because it sits exactly a mile above sea level. That’s around a 5,300’ elevation.

The next iteration of TCAS, (the romantically named ACAS XO), promises better tolerances for these conditions but it’s not here yet, so right now users of TCAS 7.1 get all the warnings when all the warnings are not necessary.

What the FAA are concerned about.

Operate into Denver, and the threat of simultaneous parallel approaches isn’t new, but awareness of the threats needs to be improved. The basic idea is folk should:

• Have an awareness of how the close in approach setup might increase the threat
• Brief how operating in TA only mode adds to this
• Know exactly where to be and what’s around by listening out on the radio and monitoring TCAS carefully
• Think about to remember to re-select TA/RA mode in the event of a missed approach
• Be aware of how nuisance TCAS cautions and warnings may desensitize crew.

In fact, this could be useful guidance anywhere where there are similar operational and environmental conditions which might increase the risk of collision.

On August 2, the US Department of State updated its worldwide terrorism warning for the first time since 2019 – terrorist groups around the world may be actively planning attacks on US interests. This follows news on July 31 that the leader of a major terrorist organisation was killed during a military operation in Afghanistan.

My flight is tomorrow, what does this all mean?

For starters, no new airspace warnings have been issued due to the recent events. But it is equally important that operators (especially N-registered ones) heed the information that is already out there.

This comes from a combination of FAA SFARs, KICZ Notams and Background Information notes.

In the most dangerous airspace, the FAA bans US operators at all levels. In which case, the decision to overfly is an easy one because it has already been made for you. You just can’t do it.

But it’s not always that clear cut. Risk may be present, but not enough of it to justify closing entire pieces of airspace. So the FAA carries out assessments and decides on what precautions operators should take to stay safe.

This is where the lines start to get a little blurry because these assessments take time, and security risks can evolve more quickly than the papers can be signed. In other words, what was safe yesterday may not be safe today.

And so operators may need to re-evaluate their exposure to known risks, based on what is happening right now. With that in mind, here are some hotspots US aircraft are permitted to overfly that we think deserve a second look.

Iraq

Back in October, the FAA lifted its long running Notam barring US operators from entering the ORBB/Baghdad FIR. The SFAR is now in effect, meaning overflights are technically okay provided you stay above FL320. But just because you can, doesn’t mean you should.

Militant groups are active throughout the country and are known to have access to anti-aircraft weaponry. The have also have a proven track record of targeting US interests in the country. Scour through the OPSGROUP archives and you’ll see report after report of rocket, drone and mortar attacks on ORBI/Baghdad along with other regional airports.

Our advice hasn’t changed – avoid overflights at all levels if possible. Although the eastern airways UM860, UM688 and UL602 are frequently used and considered safe options by some major carriers.

Militant groups have been known to target aviation assets in Iraq – like this empty aircraft that was damaged by a missile attack at ORBI/Baghdad in January this year.

See: SFAR 77, Background Info Note.

Mali

The FAA currently advises US operators to use extra caution if overflying Mali below FL260. The main issue is the ever-fragile security situation on the ground. The FAA cites extremist or militant groups that may actively target civil aircraft with various weapons.

And things seem to be getting worse. On July 29, the US Embassy ordered the urgent departure of non-emergency US Government employees due to the risk of terrorism. Which is a warning sign for us that these risks may be escalating.

See: KICZ Notam A0009/22, FAA Background Information.

Somalia

The FAA currently allows US operators to overfly the HCSM/Mogadishu FIR above FL260. It’s important to remember though that the security situation on the ground there is unstable – especially since a controversial election back in April.

Terrorist groups are active in the country, and may have been motivated by recent events. These groups have a proven track record of targeting civilians and aviation interests. In June this year news broke that several local carriers were considering suspending flights over security concerns onboard aircraft and at airports.

There is also currently an active trial of Class A airspace throughout the Mogadishu FIR, which means Somalia may be seeing higher numbers of overflights than normal. The problem is that emergencies and diversions may put aircraft at risk, especially US-registered tail numbers.

The entire HCSM/Mogadishu FIR currently has Class A coverage – the problem is security if an aircraft needs to divert.

See: SFAR 107, KICZ Notam A0028/19.

Egypt

Back in March the FAA lifted its airspace warning for the HECC/Cairo FIR. It previously advised operators to stay above FL260 over the Sinai Peninsula – in the east of the country dividing the Red Sea from the Med.

The issue was the presence of extremist groups who may attempt to target civil aircraft. It’s not clear what improvements led to the warning being lifted, but other countries have kept theirs in place – including the UK and Germany.

Recent events have proven that all is not well. An attack in Western Sanai in May this year was one of the most significant in the past two years – and was a clear indicator that terrorist groups are still active in the region. If they have been motivated by the happenings in Afghanistan, this may put aircraft at renewed risk.

The UK and Germany warn operators to avoid overflights of the Sinai Peninsula below FL260

Where else to look.

As things change, airspace warnings get updated. For US operators the starting point is here – it contains everything officially put out by the FAA.

There’s also safeairspace.net – our conflict zone and risk database. The OPSGROUP team keeps this updated as new information comes to hand. You can view a global risk briefing by clicking here.

Update 1500z Aug 3: And bam! Just like that, the ATC strike in Morocco is cancelled! There’s no more info yet, but normal ops now expected for the whole period Aug 3-18. So say Eurocontrol on the NOP site.

—————–

Story from Aug 2:

News broke last week that Moroccan ATC are threatening to strike for a full two weeks from August 3 – 18, and it will affect the entire GMMM/Casablanca FIR. Similar strikes elsewhere typically last just hours or at worst a day or two.

While it will not be a complete walk-out, the airspace may be heavily restricted – a busy air corridor linking Western Europe to Sub-Saharan Africa and South America. On average Moroccan airspace services over a thousand flights a day, and ATC want to put the brakes on hard.

It’s all found in this letter written by the union responsible. Here’s our breakdown of what it says, along with some nice pictures.

Let Me In!

If you want to come in, you had better get in line. If the strike goes ahead, only one aircraft per hour will be allowed through each entry point to the GMMM/Casablanca FIR.

Trickle effect at airports.

All major airports in Morocco will be affected by heavy restrictions on aircraft movements. In each case, only two aircraft will be allowed depart each hour.

All of Morocco’s major airports (along with others) will be restricted to two departures per hour throughout.

Who’s not affected?

There will be limited exemptions, but they won’t apply to most operations. Aircraft engaged in state, RFF, medevac or humanitarian ops will be exempt. And if you experience an emergency, of course you’ll be allowed in asap.

You will also be able to get special handling permission by including ‘STS/AFTMX’ in Item 18 of your flight plan to get around the restrictions. This will be by prior approval only though. To ask for it, you’ll need to contact the CAA directly. You can reach them at civilair@menara.ma or on +212 537 67 94 07.

Watch out for Western Sahara

If you’re hoping to avoid the hold-ups in the GMMM/Casablanca FIR, you may be tempted to route further south over the Western Saharan region.

Something to be aware of first – there are still active airspace warnings in place for this disputed territory. Despite being quiet in the news lately,  there is a long running conflict happening there. Anti-aircraft weaponry has previously been identified as a possible threat to low flying aircraft below FL200. The risk to overflights in the upper flight levels is very low, but take extra care if planning for diversions or emergencies.

You can read a full briefing on the situation here. We’ve also written this article which may also help.

Right now it’s just a “potential” strike.

The nature of industrial action is that it can be hard to predict until it actually happens. On August 1, Eurocontrol advised the strike was imminent but also noted that the GMMM Notams were conspicuously quiet. We also reached out directly to the Moroccan CAA, but so far *crickets*.

Other ATC strikes in Africa

It must be the season! Also be aware that on August 25 another major strike is planned affecting five FIRs in Western Africa, along with another over Madagascar in the east. You can read more about that one here.

Update – July 26, 2022

There has been no major fighting in Ethiopia’s northern Tigray region since late Dec 2021. A ceasefire agreed in March 2022 has mostly been upheld, and Ethiopia’s federal and Tigray regional governments look set for negotiations soon.

For the time being though, airspace in the north of the country should still be avoided – several states maintain active airspace warnings for the HAAA/Addis FIR, and Ethiopia still have a Notam in place banning all flights at FL290 and below.

Here’s the current version of the Notam, the content of which hasn’t changed since its first iteration:

HAAA A0220/22 - FLIGHT IS PROHIBITED TO FLY AT OR BELOW FL290 WITHIN
MEKELE TMA AND WITHIN THE AIRSPACE DEFINED BY JOINING
THE FOLLOWING SUCCESSIVE POINTS AND LINES
135914.7N 0362048.9E
130042.8N 0365122.9E
ETOBU(132132N 0373433E)
TILUD(134116N 0375950E)
EVITO(142911N 0382424E)
THE COMMON FIR BOUNDARY BETWEEN ADDIS AND ASMARA AND
THE COMMON FIR BOUNDARY BETWEEN ADDIS AND KHARTOUM
REF AIP SUP A 04/2021. GND - FL290, 27 MAY 09:00 2022 UNTIL 27 AUG 09:00 2022. 
CREATED: 27 MAY 09:00 2022

Better yet, here’s a picture of what this actually looks like:

Update – Nov 18, 2021:

• The US published a new airspace warning and Background Information Note for Ethiopia, cautioning against overflights of the HAAA/Addis Ababa FIR below FL290. The conflict between the Ethiopian military and opposition forces had intensified. Aircraft below FL290 were at increased risk from anti-aircraft fire.
• The US, the UK, Germany and France all issued security warnings advising their citizens to leave immediately.

Update – Nov 9, 2021:

• Ethiopia is on the verge of civil war. The government declared a six-month nationwide state of emergency on Nov 2, following increased fighting between the Ethiopian military and opposition forces in the Tigray region in the north of the country.
• Concern that ATC services in the HAAA/Addis FIR may be affected with little notice. Overflights of Ethiopia may be at increased risk of anti-aircraft fire at all levels.
• Several factors impacting risk to overflights: military aircraft being used in combat roles, unmanned aircraft operating in region, unstable political situation on the ground, and conflict spilling over into adjacent regions. All of this pointed to an increased risk of misidentification and miscalculation – aircraft mistaken for something of military interest, or simply caught in the crossfire.
• Opposition forces in Tigray have access to conventional surface-to-air missile systems that can reach aircraft as high as FL260. They have also previously shown an intent to target aviation interests with rockets and ballistic missile attacks on airports within the region, as well as across the border in Eritrea. Other military interests in the area have weapons capable of reaching much higher – including the Ethiopian military. More sophisticated systems are present in or near the region that are capable of reaching as high as FL490. For context, in August 1999 the Ethiopian military shot down a Learjet near the border with Eritrea. Then in May 2020 they also downed an Embraer 120 in Somalia. Both were misidentified.

Further reading

SafeAirspace.net is our conflict zone and risk database. Click here for a full briefing on the situation in Ethiopia.

Scour the OPSGROUP vault over the past twelve months, and you’ll find a bunch of alerts we’ve posted about jet fuel shortages. In fact, we even wrote an article about the problem.

You’ll also see that a disproportionate number of them are for Africa – or more accurately, Sub-Saharan Africa. Also known as the epicentre of ‘tricky tech stops.’

Cape Verde, Nigeria, Sierra Leone, Senegal, Zimbabwe, Burundi, and South Africa have all graced our news feed in recent times for being low on gas. The problem for ops is that it is no coincidence. And for the next year at least, fuel availability is set to become public enemy number one there for flight planners and pilots alike…

All oil products (not just jet fuel) have become a scarcity in many African countries.

Feeling the pinch.

From an air travel perspective Covid is (more or less) behind us, and demand for jet fuel is surging. But at the same time, the world’s ability to produce it has fallen for the first time in three decades. Sanctions on Russia have been a big part of this – not surprising considering it produces ten percent of the world’s oil.

The pinch becomes higher prices for everyone. In more developed economies, supply isn’t a problem – the turbulence of the market is absorbed with price hikes. Which is why refuelling jets at your local FBO has become so eye-waveringly expensive. But if your pockets are deep enough, the fuel is there to be used.

But this just isn’t the case in less developed regions –  especially Africa, which is facing its worst supply shortage in forty years.

Drip Feeding

Many sub-Saharan countries have limited ability to refine their own oil domestically. And the refineries often operate below capacity. And so they are reliant on imports – so much so that the continent ships in three quarters of what it needs.

The problem then becomes the balance sheets of importers. Their pockets aren’t that deep, so they can only import small amounts at a time, effectively drip feeding their economies.

Combine the two issues, and there just isn’t much room for fuel reserves to ride out any bumps in the road. This strategy of storing less and refining less can be risky, especially in 2022.  It leaves African countries extremely vulnerable to market forces they can’t predict or control – exactly what is happening right now. Local crises such as civil war can also deepen the problem.

Hedging Bets

It’s no secret that oil exporters are in it to make money – like most businesses. The big gamble is what will happen next. When prices are low, exporters may store oil in expectation of things picking up again. This often takes the form of full oil tankers, which can supply African countries with small shipments of oil while in transit.

Many African country rely on oil imports, using tankers like these.

But right now, jet fuel is in demand. Fuel hedging doesn’t help either. Importers hedge their bets and if they think that more prices rises are coming, they enter into contract to secure prices now as it will save them money later. That’s where the cash flow to buy and store it comes in handy. Many African countries aren’t that lucky, and their lines of supply have been drying up as bullish prices charge on.

The result? Long term fuel shortages, and no guarantees things will get better in a hurry.

Crystal Ball

So, if fuel shortages at African airports are so intrinsically related to global prices, what does the future hold? There may be some relief on the horizon.

The super-charged rise of oil (and therefore jet fuel prices) is set to slow down, and in some forecasts even abate. But none show an outright collapse from the giddy heights they have reached today.

But of course, this is all conjecture. As Covid taught us, the world and the reaction of markets are unpredictable. Things have a habit of going either way, driven by forces we often don’t see coming. But while the cost of jet fuel remains high, shortages are set to become a feature of the landscape for operations in Africa for some time yet.

ICAO are hurriedly upgrading the SELCAL system to allow for new codes. There’s only a finite number of them available, and double ups are becoming are a problem. The potential for more than one aircraft to receive the same call in the same airspace is cause for concern.

ICAO have been onto it for some time, and on November 3 there is a soft deadline for Air Navigation Service Providers (ANSPs) to upgrade their ground equipment to communicate with the new codes.

But there is a problem on the NAT. Most of the ANSPs won’t be ready in time. Which means if an aircraft has one of the new codes, for up to six months they will not have SELCAL when crossing the pond.

Here’s a quick rundown of why, and what the impact will be.

SELCAL 101

If you are one of the few who already know what ’32-tone’ SELCAL is, top marks and feel free to skip this part.

If you don’t, fear not. This ain’t no radio shack, but a little bit of tech stuff will help here. All you need to know is the alphabet and how to count to ten. Chances are if you’re flying a plane, you already have that covered. Let me explain.

Unless you actually like the soothing sounds of static for hours on end, or distorted mumblings from halfway across the globe, chances are you have heard of Selective Calling (SELCAL). It does the listening, so we don’t have to.

In a nutshell it is a signaling system that lets us know via HF or VHF when ATC is trying to get a hold of us, so we don’t need to listen out all the time.

Here’s how it works. On the ground a SELCAL encoder transmits four audio tones at a time. Each tone is assigned a letter. When the four tones correspond to your aircraft’s four-letter code, a decoder in your avionics hears it and triggers a SELCAL with a noise and flashing light. That’s your cue to call ATC back. Simple.

Enter the problem. Until now, only 16 letters (and therefore tones) have been available. That means there are just shy of 11,000 codes for aircraft to use. And so far, 37,000 have been allocated. Which means double ups. And the problem isn’t going away.

There is an increasing risk that multiple aircraft in the same airspace may receive the same SELCAL, and that could spell danger. ICAO knows that, and so they’re adding 16 new tones (comprised of letters and numbers). That will bring the total to 32. And voila, ‘32-tone’ SELCAL.

This will create almost a quarter of a million unique code options and will cut the problem off at the knees.

But there’s a problem on the NAT…

On the ground, ANSPs need to upgrade their SELCAL encoders to include the new tones. ICAO has set them a target of November 3 to get it done.

However, three of the five ANSPs covering the NAT region (Gander, Shanwick and Santa Maria) have already indicated they won’t be ready until at least Spring next year. In the interim, they won’t be able to issue SELCALs to aircraft featuring the new codes (ones that contain T-Z or 1-9).

It’s not clear yet how many operators this will affect, so Nav Canada has reached out looking for more info.

They want to hear from you if:

• You are planning on equipping your aircraft with the capability to use the new codes.
• You have already applied for one.

You can email that info to kelly.mcilwaine@navcanada.ca, and cc in ocarrollk@iata.org. They want hear from you before August 31.

What will the procedure be without it?

NAT Doc 007 (6.1.22) seems to have the answer, and it’s not great. As a general rule, any aircraft that can’t be reached by SELCAL must maintain a listening watch on the assigned frequency – and unfortunately that means hours of annoying static (even if your CPDLC is working just fine). Hardly ideal.

Nav Canada has confirmed to us that this will indeed will be the case. An AIC will soon be published, which is due out in September.

Need more info?

You can read more on ICAO’s SELCAL upgrade project here.

Or feel free to reach out to us directly on news@ops.group and we’ll do our best to help find the answers you’re looking for.

Go-arounds are often described as routine. And the guiding principle is that we should be ready to execute them safely, accurately, and immediately on every approach, and without hesitation.

It sounds good on paper, but this expectation is among a myriad of niceties we tell ourselves that all competent pilots have covered. And I’m not sure I agree.

Rose tinted: “Go-arounds are normal, and we’re always ready and prepared for them!”

For starters go-arounds aren’t routine. They’re just not.

We know this to be true. On average, a long-haul pilot will do one every five to ten years.

Secondly there are the reasons behind them. Weather related go-arounds tend not to be the ones we’re struggling with. Why? Here’s one suggestion –  because when conditions are marginal, we are ready for it – we’ve briefed it, we believe it may happen. Our brains are primed for action.

But what about when we’re not expecting it – when we’re not primed? When the weather is good, the airplane is on rails and sign-off is within arm’s reach. Are we as prepared then?  

Incident histories are littered with go-arounds gone awry, and they often have a major trend in common – the crew weren’t ready for them. Because the reason for the go-around was unexpected, it wasn’t routine.

And when we encounter a non-routine event, we become fallible to limitations that all pilots possess in times of surprise or emergencies. Enter our ‘inner ape.’ It’s hard to tame, so when we have an emergency we fall back on one particular mantra. Ape repellent, if you will – ‘aviate, navigate, communicate.’ The idea is to break down an overwhelming situation into manageable chunks.

Poor little thing.

So why then are we failing to apply the same idea to unexpected go arounds?

A healthy dose of ‘deer in headlights’ might be the answer. It’s no secret that when we are surprised, our brains stop for moment. It is hard wired into us from the days when we were running away from woolly mammoths.

Fight or flight is instinctive in all of us.

Our instinct is to act now, and think later. And those big ol’ TOGA switches are a huge trigger. Once we push them, it’s on. We are bombarded with rapid fire mode changes, oodles of thrust, noise, configuration changes, high nose attitudes, and typically we’re going up faster than a fart in a bath.

Our brains can switch into overload mode – there is too much information coming at us and too fast to stay ahead of the airplane, or even with it.

Here’s a couple of scenarios to mull over – how would you manage your airplane?

• You’re instructed to go-around above the published missed approach altitude.
• ATC instructs you ‘caution traffic 1 o’clock 2 miles. Cancel published missed, maintain 1500′, turn left heading 180 degrees, expect visual circuit.’
• The pilot flying is about to bust through your missed approach altitude, but isn’t responding to you or ATC.

Had we not briefed the missed approach as routine, along with the runway lighting, expected taxiway turn-off and our parking bay, we might be more prepared. But the evidence is suggesting that we’re not.

There was nothing routine about this 400 pound seal that decided to take a nap on a runway in Barrow, Alaska.

Our approach to go-around training, along with other abnormals, needs to focus on the unexpected, the non-routine. The industry has already discovered that we learn less when we know what is coming in the sim, and that the real world is rarely as forgiving.

Danger Club returns!

We’re starting the conversation at sunset. Almost dark. A French Bee A350 is landing in Paris Orly, after an 11 hour flight from SFO. Almost home. But 3 miles out, the machine says “WINDSHEAR“, and the flight goes from routine to 🤡 go-around circus 🤡 in about 10 seconds.

The F/O checks out. Startled and frozen. The captain is now single pilot, but doesn’t know it. The airplane doesn’t know it either, so keeps flying- busting the altitude, heading for departing traffic. But nobody’s flying it.

Here’s your challenge: park any judgement on the crew at the door. Step inside DANGER CLUB, and ask, with your curious-raccoon-mind: “How could this happen to me?”

This is where we might start, but we don’t know where we’re going with this one …

> Go-Arounds ain’t always easy (even if they tell us they should be)
> How bad can startle be?
> How do we get ourselves back in the game?
> Was this all the Captains doing? (Even if the report focuses on the FO)
> Do we HAVE to go-around right away?

That’s where we start … this Thursday, July 14, at 1730Z.
Will you join us, curious raccoon?

> The (very readable) accident report is here.
> Also, there is an excellent – as always – video from Mentour Pilot  about the whole incident. Highly recommend!

In Honkers, things are about to change. The airport’s shiny new northerly runway (07L/25R) will become operational on July 8 – earlier than expected. Although there will still be some restrictions on its use.

AIP SUP 6/22 (an 111-page ‘über-sup’) which literally swallowed a bunch of other smaller sups, was published back in April with everything you might want to know about the new runway.

Now that you stand a pretty good chance of actually using it, let us help you out by hand-picking some of the more vital ‘need-to-know’ info to keep you out of trouble.

The slightly cryptic way of saying, yep you can use it.

The basics.

The recently constructed 07L/25R is  12,467′ (3,800m long) and 197′ (60m) wide.

There are ILS/LOC approaches at both ends. There are also RNP (AR) approaches, but as their names suggest, you’ll need prior approval to shoot those.

Runway 07L is also equipped with CAT II goodies (25R is CAT I only). A big head’s up though – you need to get permission from HK authorities to conduct low viz ops at VHHH before you get there. There’s a form to fill out, and of course you’ll also need to provide evidence of your state-issued approval (OpSpec C060 for US operators).

As you would expect, along with the runway will be a bunch of new taxiways too. The layout is quite straight forward:

The new ‘normal’ configuration.

The new runway (07L/25R) will normally be used for arrivals, while the southerly runway (07R/25L) will be used for departures. When winds are light or easterly, expect to land on 07L for noise abatement which is preferred.

Squashed in the middle is 07C/25C. It will be closed from July 7 until further notice, but recalled if another runway becomes blocked.

Keep an eye out for routine closures for maintenance, which may reduce the airport to single runway ops at quieter times. The weekly schedule for those closures has been published in this (much more bite-sized) SUP.

Watch those ‘fly-overs.’

There are new RNAV SIDs and STARs for 07L/25R. Tracking is straight forward, but the major thing to look out for are fly-over waypoints. They can be lost a little in the noise of a chart, but if there is a circle around a waypoint, turn-anticipation is a no-no. Make sure the fly-over is correctly coded in your FMS. There are also speed restrictions to keep your turn radius down. The reason for these is to keep traffic well clear of high terrain just a stone’s throw away – spot heights within a mile or two of the airport reach as high as 2000.’

Look out for overfly waypoints and speed restrictions on SIDs for the new runway.

Wind shear.

High terrain north of the airport means that in some conditions, wind shear is a real problem.

The new runway is the closest of all of them to those hills, which means it may be the most susceptible.

Be on alert when the wind is from the Northwest through to the Northeast above 20kts, it’s going to be sporty – especially if landing on 25R. Carry fuel for a comfortable missed approach, and possible diversion.

Look out wind shear in northerly conditions – especially on approach to the new 25R.

Bad signals and false captures.

ILS interference has long been reported at VHHH due to the effects of the terrain around it. It can lead to nasty stuff like false captures and excessive descent rates. Boeing aircraft are especially susceptible (although don’t ask us why). It is often recommended that the LOC is captured first, before arming the glide slope. This has been reported on both existing runways, and so it stands to reason the new one (07L/25R) will be no different. Keep an eye on the chart notes for this one. If it happens to you, its really important to report it – there’s a form available here.

IFALPA warning…

IFALPA has issued a safety bulletin for the new runway (07L/25R). Due to terrain, the ILS is broken into two parts – an RNAV transition, and the approach itself which are found on two different charts. The bulletin has useful recommendations to stay on the correct profile, and to avoid nuisance GPWS warnings – essentially slow down and configure early. It’s also important not to arm the glideslope before the point TOPUN, due to the risk of false captures.

We need your help!

As the new runway configuration gets up and running, we’d love to hear any feedback from operators heading in there. You can reach us on news@ops.group. Or if you’d prefer, you can submit a report to Airport Spy.

On June 13, crew entry rules were eased – under certain conditions, you no longer have to isolate in your hotel room. It’s great news for layovers – icy cold Asahi beer and delicious gyoza await.

The problem is where to find that information. The guidance online is all for passengers. So, we reached out to a local agent, who provided us with an ‘Administrative Circular’ recently issued by Japan’s CAA with all the rules just for crew.

But for some reason, we are not allowed to share it. Why? We’re not sure – it is apparently top secret. Before it becomes mission impossible and self-destructs, here is a rundown of what it contains. But you’ll have to take our word for it…

Blue, Yellow and Red

Japan has broken the world’s countries down into three categories – yep you guessed it, the colours above.

The rules you need to follow depend on where you have been in the past fourteen days – the most restrictive country applies.

Blue Countries:

This includes the US, Canada and much of Western Europe. If you haven’t been outside the list of blue countries, you will only need to provide a Covid test that is less than 72 hours old – more on that in a moment.

There is no need to provide proof of vaccination.

Yellow Countries:

Many South American, Caribbean and Eastern European countries fall into this category.

If you’ve been in one of these, you will need the same test as above with the additional requirement of being triple vaccinated – yep, all three jabs of an approved vaccine.

Red Countries:

There’s only a few of these. At the time of writing, just Pakistan, Fiji, Albania and Sierra Leone .

Unfortunately, if you have been in one of them, you will need to isolate in the hotel in addition to all the other requirements.

What Covid tests are accepted?

You can view the list in full here, which of course includes the gold standard PCR test.

The biggest gotcha is that rapid antigen tests (the super easy ones you can do at home) are not allowed. They are what are known as ‘qualitative’ antigen tests, and Japan has said no bueno. ‘Quantitative’ antigen tests are allowed, but they are not the same thing.

Here’s a little graphic that might help you get your head around which tests are okay for entry. Some of the details are in Japanese, but effectively the ones on the left in are okay, the ones on the right with crosses are no good.

A word about vaccines too.

 Any vaccine certificate must be issued by the government, or other official source. In either English or Japanese is fine.

You need to have received one of the following:

• Pfizer
• Astra Zeneca
• Moderna
• Janssen
• Bharat Biotech
• Novavax

In some cases, a single dose counts as two. You can also mix vaccine doses. More on that here.

I don’t meet some of these requirements – can I still go?

 Yep! But you’ll have to isolate in a hotel and use private transport to and from the airport.

Can I present a ‘Certificate of Recovery’ instead of a Covid test?

 It’s not mentioned in the official guidance, but local agents advise the answer is no. At this stage, you’ll have to stick to the guidelines above if you don’t want to isolate.

What do operators have to do?

Effectively screen all crew for symptoms beforehand – anyone with signs of cold and flu are not allowed to operate to Japan.

In flight, if someone starts feeling unwell, the operator needs to let the authorities know – the crew member will be tested on arrival. It will then be on the operator to get the rest of the crew tested too.

Just a note though – pilots and cabin crew are considered as being in ‘segregated’ areas. So there is no need to test a pilot if a flight attendant becomes unwell, and vice versa.

So, there you have it.

Crew are free to enjoy their layovers in Japan, as long as they meet these requirements. It also goes without saying that common precautions apply when out of your hotel – including hand washing and mask wearing.

Never washed your hands before? We’ve got you covered. Here is a detailed ‘how-to’ video along with some soothing electric keyboard.

Still have a question?

Reach out to us on news@ops.group, and we’d be happy to help.

Six months have passed since the FAA hurriedly reached an agreement with Telecoms AT&T and Verizon to delay switching on powerful new 5G antennas near major airports.

That agreement was set to expire on July 5. And the original concerns haven’t gone away – 5G can still interfere with radio altimeters, and the industry is still scrambling for a fix.  If safety buffer zones were to stop buffering at larger airports, where low visibility landings are more common, the impact would have become even worse.

However, on Friday the FAA released its first update since February – and the news is good…

A new agreement

AT&T and Verizon have agreed to extend the delay until July 2023 to allow the FAA and operators more time to get their ducks in a row.

There is compromise happening on both sides of the deal. While the FAA hasn’t gone into the specifics, they have said there is now a phased rollout plan to make sure that both sides are kept happy.

The FAA will begin work to identify which airports are safe enough for the Telecoms to start enhancing their services there right away, without turning everything on.

On the flip side, there will be more time for operators of aircraft fitted with radio altimeters vulnerable to interference to replace them, or install special filters. Regional aircraft are particularly affected by this.

Considering that the first customers are only just now receiving these filters from the radio altimeter manufacturers, the original goalposts were always fairly ambitious.

A new FAA deadline for operators to complete work on their fleets is set for the end of the year, and this time it looks to be firm. The Telecoms are expecting to be let loose at the end of the new deal.

Both Verizon and AT&T have agreed to delay their 5G rollout plans near major airports for another year.

In the meantime

The status quo – existing restrictions will remain in place. Back in January over a thousand Notams (1,478 to be precise) were issued when 5G hit the proverbial fan. Many of them restrict the use of Autoland, HUD to Touchdown, and Synthetic Vision Systems at specific airports. The FAA has also published a guide that explains the different types of Notams and what those limitations mean for operators at various airports.

The FAA has also since provided a number of exemptions for more common passenger jets to continue with low visibility landings. You can view those through the FAA’s handy map here.

The FAA have produced a summary of which exemptions for low viz landings apply where. Click the map for the interactive version.

Unfortunately, the support for business jets has not been as forthcoming. If your aircraft doesn’t have an exemption, you’ll have to stick to the Notams, which means paying extra special attention to the weather and alternate planning when it’s looking murky out there.

Buffers will also remain in place at several major airports to make sure that low visibility landings can continue without causing major headaches for operators. You can view that list here.

Other things to look at

If you’d like to know more about the problem with 5G networks and aviation in more detail, we wrote a blog article earlier this year that would be a great place to start.

There’s also the FAA’s official 5G website, where updates like the one above are published.

Get in touch

If you have other questions, we’d be happy to help. You can reach us on news@ops.group.

From June 29 – August 4, the world’s largest military exercise will be happening near Hawaii. It’s called the Rim of the Pacific Exercise, or RIMPAC for short.

It’s a big deal – this year over twenty-six major nations (including the US, Canada, the UK, and Australia) are taking part in extensive naval and aerial activity happening every day through a lengthy period.

If you’re operating into (or near) Hawaii during the exercise, it’d be a good idea to brief on what to expect. The FAA’s Impact Statement is the official guidance, but it’s a solid read. If you’re after something a little more bite-sized, we’ve got you covered.

Here’s a breakdown on the biggest need-to-know info…

Nearly two hundred aircraft from twenty-six nations will converge on Hawaii for RIMPAC.

Let’s Talk About Airspace

The vast majority of RIMPAC will be contained within Special Use Airspace. The usual suspects will be included – all permanent warning and restricted areas on your charts, along with other types of special use airspace with  scary looking abbreviations like ‘ATCAA,’ ‘ALTRV,’ and fancy names like ‘Nalu,’ ‘Haka’ and ‘Luna.’

Big picture – don’t go into the red boxes when they’re active (more on that in a sec).

Before you tackle the official FAA Impact Statement, for the love of Pete have a map open next to it. Once you can see where all this airspace actually is, as I learned, things suddenly get a lot easier – luckily the FAA has put one together:

Righto, timings.

Even though RIMPAC starts earlier, most of the actual flying won’t kick off until July 11.

As a general rule, any restricted airspace that goes high (Surface to FL600) will be active each day between 07:00 – 22:00 HST (17-08z). Outside of these times, any restrictions will generally be low level (less than 12,000’).

But, there are some exceptions to look out for. Got that map ready? Bueno…

The big one is that MILU East, MILU South, W-192/3/4 (all south of Oahu) will remain in effect 24/7, and at all levels.

There are also some subtle differences to timings for W189B and W190 which also extend up high. These are only active from mid-afternoon.

What will be the impact?

Just remember: 15 minutes. It seems to be the magic number.

You can still file as per normal, but if you’re operating on an affected route (including some PACOTS), you’ll have to accept delays for re-routes of up to 15 minutes. Which means more contingency fuel.

Here are the routes that the FAA’s guidance specifically mentions:

To/from Asia:

PACOT tracks 11/12 and A/B between Hawaii and the Far East.

To/from the US:

If you’re routing between the Pacific Northwest and Hawaii, try and plan above FL290. If you’re unable to, ‘Nalu’ will get in the way. ATC will be able to vector you onto another airway (A331), but it will mean a reroute. If you can stay above, there will be no impact.

If you’re headed to or from the Pacific Southwest, ‘Mahi’ and ‘Haka’ will affect flights at all levels, with the same delays.

To/from the South Pacific:

Flights between Hawaii and Tahiti, Fiji and Samoa will be impacted by Luna West, Central and East can also expect reroutes.

The FAA advise in all cases, the delays will not be worse than fifteen minutes (and that’s a worst case scenario).

What about Hono?

Retractable barriers are present on three of PHNL/Honolulu’s four runways, which are used to simulate carrier landings – pretty neat huh?

The only downside is that when a capture is needed, that runway will be unavailable for forty-five minutes. The FAA advise that this could cause delays of up to fifteen minutes while ATC juggles things around.

Barrier arrests will close a single runway in Honolulu for at least 45 minutes.

Then there’s the two nearby military airports – PHIK/Hickam and PHNG/Kaneoehe Bay. As they will be used to house a number of military aircraft transiting to and from the exercise (the rest will be on a carrier), ATC may need to implement flow control at PHNL/Honolulu to keep things within capacity. Again, nothing worse than 15 minutes…see, the magic number.

Hickam AFB is one of two airports near Honolulu that will host extra aircraft and may cause extra ATC congestion.

I need to speak to someone.

The FAA has listed two contacts over at the Honolulu Control Facility:

John Wennes – john.h.wennes@faa.gov, 808-840-6161

Antonio Carrilho – Antonio.a.carrilho@faa.gov, 808-840-6203

Or give the OPSGROUP team a shout on team@ops.group, and we’ll do our best to help.

The problem with black boxes is that they are attached to the airplane.

Although their contents are invaluable for figuring out the cause of an accident, if we can’t find the airframe, we don’t get the answers.

It took two years to find Air France 447, while Malaysian 370 remains lost to this day. The industry seems to be becoming more aware that there is something wrong with the way we have been tracking, searching for, and finding accident aircraft.

And as part of this, there is an emerging push for black box data to be streamed live during a flight using internet-based technology.

From a safety perspective, it makes sense. But from a practical standpoint, it’s not all smooth sailing. Here’s a brief look at how these new technologies might work, and why organisations such as IFALPA, along with some pilots, are still pushing back.

The ‘Cloud’.

Storing data in the cloud is becoming a reality with both flight data and voice. All you really need is an internet connection to let the magic happen.

With that in mind, the idea is that black box data could be streamed to the cloud constantly. Meaning it is immediately available to safety investigators if or when an accident or incident happens.

ICAO.

As a result of accidents like the ones mentioned above, ICAO is implementing a mandate for new aircraft with MTOWs over 27,000kg (60,000lbs) due to come into effect from 2023.

It’s an extension of their Global Aeronautical Distress and Safety System, or simply ‘GADSS’ – their initiative to make tracking and finding aircraft in emergencies much more efficient.

A big part of it is that onboard equipment will need to recognise abnormal or emergency conditions from parameters such as speed or unusual attitudes automatically, and then begin broadcasting very accurate position reports as often as once a minute – as opposed to the 15 minutes when ops are normal.

ICAO GADSS – systems must automatically detect situations of distress and broadcast position more frequently.

Big Tech.

Technologies are being developed to allow manufacturers to comply with these GADSS requirements, and in some cases they are taking things one stop further – to include flight data streaming.

Take Satellite Communication heavy hitter Inmarsat for example. Their ‘Black Box in a Cloud’ solution allows data to be live streamed via the internet, to the ground as soon as there is sign of trouble.

Honeywell and Curtiss-Wright have also joined forces to develop new recorders capable of continuous transmission to their own facilities on the ground.

Example of how black box data streaming works. Courtesy: Honeywell

IFALPA says nay…for now anyway.

So on the face of it, black box streaming seems like a no-brainer.

But there are still concerns. On May 9, IFALPA published a position paper on just this issue – and it seems they’re not on board yet, due to security concerns.

Streaming flight data on the internet may open the door to those wanting to leak, or corrupt it. It is important that the media and public domain don’t get a hold it before investigations have taken place, and there may even be those with more malicious intent who want to alter it in some way.

And there are no existing technologies that are 100% secure. IFALPA argue that as the technology develops, so too must our ability to protect it. And until then, IFALPA will remain opposed to it.

Other problems.

It’s not just security either. Here are some other roadblocks that live flight data streaming faces:

Privacy – across the board there may be push back from crew who, understandably, don’t want their voices recorded and broadcast to the internet. It may be for similar reasons why the industry has resisted the use of cockpit video recordings for the past two decades, despite the desires of the ATSB.

Cost – The suggestion of retrofitting this type of technology to existing airframes would be timely and very costly. And in the current industry environment, there is likely to be significant push-back on introducing additional expenses.

Speed – Have you ever tried to stream a movie on that hideously long red-eye? It can be notoriously slow and unreliable – especially in more remote parts of the world. Flight data recorders also save an immense amount of data, which means satellite time and storage could become uber-expensive.

For live flight data streaming to be effective and reliable, the logistics behind it also need to be rock solid. And there are concerns we’re not there yet.

Live flight data streaming will eventually become the new normal. But how long that takes depends on the aviation’s ability to overcome these hurdles.

It’s a busy few days in the skies of Los Angeles this week.

A major political event – The Summit of The Americas – is happening there from June 6-10. A number of TFRs will become active affecting access to numerous airports throughout the LA Basin.

The FAA has now published the details, so let’s took a closer look.

Update on Restricted Airspace

It looks as if some newer TFRs were issued after we posted this post. First up, check the list because we can’t predict changes and they do happen.

But right now, we can see a few more like 2/5019, 2/5016, 2/5015 which might get in your way if you’re not a scheduled commercial service. These don’t supersede the other, they are for shorter time periods. But they are a lot more prohibitive (particularly if you’re a GA or private flight wanting to get into KLAX).

Restricted Airspace

There will be four TFRs becoming active in the LA area. Three of them are further west near Santa Monica and Central LA, while the fourth is out east near Pomona. The upper limit of all of them is 2,999’.

They will be active each day of the event at various times which you can access here.

If you’re operating on a valid flight plan in or out of KLAX/Los Angeles, KSMO/Santa Monica or KEMT/San Gabriel Valley then you won’t be affected.

Otherwise only essential traffic will be allowed through – SAR, medical, fire-fighting, or if you’re experiencing an emergency.

If you are allowed into one, make sure you’re squawking a discrete code. The FAA are reminding us that the timings and positions of the TFRs are subject to last minute changes, so keep an eye on the Notams too. The current one is FDC 2/4276 – and it’s a solid read. So, here’s a picture, because we like pictures more.

Four TFRs will be activated at times this week, for the official FAA map, click here.

Impact

The majority of VIP movements will be via KLAX/Los Angeles. Although they are possible at other airports too.

Traffic may be given priority to enter the queue which means potential holding, slow-downs or delaying vectors. The impact will likely be minor, but a little common sense may prevail here – consider topping the tanks off with some extra contingency fuel just in case.

The largest impacts will be felt at KVNY/Van Nuys and KBUR/Burbank – flights in and out of these are not exempt from the TFR restrictions, so if you’re heading in or out of one, here is what to expect:

Head-to-Head

 Or in other words, opposite direction operations at both airports (weather permitting). It is not a normal configuration, and may take a little extra briefing – especially when it comes to traffic and runway awareness.

STARs (and not the Hollywood Type)

 Over at KBUR/Burbank arrivals from the east can expect and plan for the JANNY 5 when the TFRs are active. This will temporarily replace the usual THRNE 3.

Arrivals into Burbank from the East can expect this arrival.

Overflights

SOCAL Terminal Area Control traffic which usually routes via V186, V201 and V459 can expect to fly via the Palmdale (PMD) VOR instead.

Other tower en-route control (TEC) routes may be unavailable during the next few days too.

I still have questions…

Detailed information on the TFR can be found on the FAA’s official website, here. Or if you still have a conundrum to solve, you can contact Flight Service 800-992-7433.

Otherwise get in touch with us on team@ops.group and we’ll do our best to help!