Monthly Archives: October 2016

To Keep Your Proper Distance, Use the Correct CNS Capability Code on Every Flight Plan

Few pilots flying today would turn their backs on the aviation advances made possible by digital communication, navigation, and surveillance (CNS) avionics. Newer aviators grew up in the GPS generation, so really know nothing else. And for the VOR generation of pilots, maybe it has been so long that they take technology’s benefits for granted. But in either case, all the wonderful stuff modern CNS equipment does to make an aviator’s life easier comes with responsibilities. First among them is using the correct CNS capability code on every flight plan, so ATC can employ the proper separation standards and keep everyone safe.

Some may say that they always provide the proper CNS code, and this may well be the case with you. But it is not universal, which is why the FAA issued Information for Operators (InFO) 16015. “The Federal Aviation Administration continues to experience operators/pilots filing the incorrect CNS codes due to aircraft system deferrals, aircraft not properly equipped or approved, or pilots not qualified for CNS capability on the FPL [Flight Plan Filing]. Given the congested Chicagoland airspace, making sure your aircraft is properly equipped and approved, and that you are properly trained and qualified on that equipment, and that you use appropriate CNS code on every flight plan makes life easier, more efficient—and safer—for all who share the sky.

All of this became especially important in November 2012 when the FAA harmonized its flight plan with the International Civil Aviation Organization flight plan box 10, Equipment  & Capabilities,  and box 18, Other Information such as RNAV and Performance-Based Navigation (PBN) capabilities. To make sure you are employing the right CNS codes you can start with the handy FAA ICAO FPL Quick Guide. To get deeper into the topic, see FAA Operations Specifications/LOA [Letter of Authorization]/Approvals Required to File Various Capabilities. It is an overview and portal with links to the related regs and requirements.

Mr. Abbott Goes to Tokyo

Mr. Abbott Goes to Tokyo

jamie-tokyo

Jamie Abbott speaks to EMAS seminar audience in Tokyo last month

Late in September, Chicago Executive Airport Executive Director, Jamie Abbott, was invited to speak about EMAS, the engineered material arresting system installed on both ends of the airport longest runway 16/34. EMAS is designed to snag an airplane that normally might have run off the end of the runway, possibly spilling on to nearby highways. The airport’s EMAS was just installed last fall.

The seminar was organized to share information between an airport operator like PWK and a potential Zodiac Aerospace customer. Zodiac, the original designer of the EMAS, covered all travel expenses for Mr. Abbott’s trip. While this kind of invite normally wouldn’t raise anyone’s interest, this one did, because Zodiac’s customer was in Tokyo. In fact, the customer team was actually comprised of the Japan Civil Aeronautics Bureau, the Regional Civil Aeronautics Bureau, Narita International Airport and Japan Ministry of Defense. In all, about 50 people were in attendance. The team from Japan was trying to decide whether or not to install EMAS at Tokyo’s Narita International airport.

EMAS Falcon

Falcon 20 resting in the EMAS bed at the south end of the airport last January

EMAS is constructed of light concrete bricks that crumble beneath the weight of an aircraft, quickly slowing the machine to a halt, usually with minimal damage to the airplane. EMAS bricks safely stopped a Boeing 747 and an MD-11 aircraft when they overran runways at New York’s JFK airport some years ago. With the paint on Executive airport’s new EMAS barely dry last January, the system was put to the test about 4 a.m. when a Falcon 20 cargo jet struck the barrier at the south end of the airport after it was unable to stop while attempting to land on runway 16. The aircraft was barely scratched and there were no injuries to either of the two pilots.

With the training for airport and local firefighting crews still fresh, emergency crews responded quickly with each element of the incident response working just as expected. The aircraft was pulled out of the barrier later that day to be made ready to fly again.

The EMAS system, while still serviceable, did require repairs in order to bring it back to 100 percent strength. That meant ordering replacement blocks and scheduling crews to handle the repairs. Of course Executive airport had no experience with the process of repairing the EMAS, which meant quite a bit of interaction with insurance companies, the FAA and EMAS creator Zodiac Aerospace. These interactions were precisely what the people in Japan wanted to hear more about.

Mr. Abbott said the FAA spoke first about why U.S. airports have runway safety areas (RSA) and how valuable a product like EMAS can be to airports that don’t have the real estate for a standard RSA, like Executive. “Then they turned it over to me to explain how and why we chose the product,” Abbott explained.

“I also spoke about how we paid for the EMAS and details about the construction process, as well as how to inspect the system and maintain it.” In all, about 50 people attended the Tokyo event that was presented to the audience mainly through a Japanese translator.

md-11-at-jfk

MD-11 rests in JFK EMAS bed

When asked why it was important enough to bring our Executive Director to Japan, Abbott said, “I think because our use of the EMAS barrier by that Falcon was such a textbook case. Everything worked just the way it was intended.” Abbott said there seemed to be tremendous benefits for the Japanese in the airport operator-to-airport operator kind of format used during the event.