On November 7, the FAA released a new roadmap for the “Integration of Civil Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS)” — which it is hoped will provide improved guidance for those extremely interested operators, manufacturers, systems suppliers and those with pending civilian applications of unmanned aircraft.
The forward to the Roadmap by FAA Administrator Michael Huerta says,
‘This roadmap outlines the actions and considerations needed to enable UAS integration into the NAS. The roadmap also aligns proposed FAA actions with Congressional mandates from the FAA Modernization and Reform Act of 2012. This plan also provides goals, metrics, and target dates for the FAA and its government and industry partners to use in planning key activities for UAS integration.”
The FAA, acting through the Unmanned Aircraft Systems Integration Office, aims to enable the integration of UAS safely and efficiently into the NAS. To do so, the FAA is working with stakeholders — manufacturers, vendors, industry trade associations, technical standards organizations, academic institutions, research and development centers, governmental agencies, and other regulators.
The premise is that UAS will be allowed to operate in the NAS, but in so doing cannot reduce existing capacity or decrease safety, cannot negatively impact current operators/operations, and cannot increase the risk to airspace users or people or property on the ground — any more than the integration of other new or novel technology. While progress has so far been significant, many challenges and opportunities apparently lie ahead.
Up to the recent Restricted Type Certification of a couple of unmanned aircraft systems by FAA — namely the Boeing/Insitu Scan Eagle and the AeroVironment’s Puma AE — operators have been and still are required to apply to the FAA for individual Certificates of Authorization (CoA) for each and every U.S. application of UAS. The FAA Roadmap is intended to provide an initial estimate of timing and to list tasks and considerations that will ultimately enable UAS integration into the NAS for the planning purposes of the UAS community.
Boeing/Insitu Scan Eagle loaded for launch.
Commercial operations that the FAA envisages include:
security awareness;
disaster response, including search and support to rescuers;
communications and broadcast, including news/sporting event coverage;
cargo transport;
spectral and thermal analysis;
critical infrastructure monitoring, including power facilities, ports, and pipelines;
commercial photography, aerial mapping and charting, and advertising.
Other commercial and public applications that the FAA might also want to add to the increasing demand for airspace access include:
crop monitoring;
precision surveying and GIS;
wildlife monitoring;
(ground) traffic monitoring and control;
firefighting support;
police services;
many, many more applications which will emerge rapidly once regulations permit ready access to airspace.
Of course, the FAA controls an ever increasingly complex airspace to which certified manned aircraft already have regulated access – it’s only fitting that existing safety and commercial use be primarily maintained and in no way compromised. Successful demonstration of UAS to achieve demanding communications, navigation, and surveillance performance will be essential.
U.S. National Airspace System.
The Roadmap quotes the International Civil Aviation Organization (ICAO) Circular 328, “Unmanned Aircraft Systems (UAS) Circular”:
“A number of Civil Aviation Authorities (CAA) have adopted the policy that UAS must meet the equivalent levels of safety as manned aircraft… In general, UAS should be operated in accordance with the rule governing the flight of manned aircraft and meet equipment requirements applicable to the class of airspace within which they intend to operate…To safely integrate UAS in non-segregated airspace, the UAS must act and respond as manned aircraft do. Air Traffic, Airspace and Airport standards should not be significantly changed. The UAS must be able to comply with existing provisions to the greatest extent possible.”
Another significant FAA statement:
“Except for some special cases, such as small UAS (sUAS) with very limited operational range, all UAS will require design and airworthiness certification to fly civil operations in the NAS.”
So, having set the tone that UAS will have to grow up in a major way to become equivalent to existing manned aircraft and to comply with virtually the same rules, the Roadmap goes on to provide much more detail of what will be required.
The FAA is working on UAS regulations — this is not really a big surprise. It would seem that there is significant effort underway to get rules in place, detailed rules which not everyone in the UAS industry will welcome. One scenario is that the huge range of UAS suppliers that we see regularly at the AUVSI annual convention/exhibit could be slimmed down if the market indeed transitions to commercial operations from the current level of military applications, and only the big companies who can afford to comply will remain. Reduced competition usually means increased costs for users, so this may not sit well with the market.
Then there are more difficulties in adapting existing airborne regulations for commercial aircraft to UAS and UAS applications. An example is given of regulations for commercial transport cockpit doors — what’s a “cockpit” when you think of UAS, and where’s the “door” for a ground-based control system in a mobile trailer, or a handheld iPad flying a small quad-rotor air vehicle? (Maybe a different thought process is required here.)
Then the air-traffic control system has to absorb flight of unmanned aircraft in an already overcrowded route network system. Of course, only some UAS operations will be intertwined with regular commercial transport air traffic, but there are huge numbers of “less-disciplined” General Aviation fixed-wing and rotor aircraft with which UAS are bound to interact. So ATC has to understand, control and regulate that interaction. Surely these are common-sense statements which most people would support?
Major technology challenges are anticipated due to the absence of an on-board pilot.
“Removing the pilot from the aircraft creates a series of performance considerations between manned and unmanned aircraft that need to be fully researched and understood to determine acceptability and potential impact on safe operations in the NAS.”
There’s that dreaded word — “researched.” For anyone in the business of selling UAS or UAS systems, including GNSS-based guidance systems, the need for potentially prolonged research may spell death for a nascent business, currently bursting with potential!
Development of Sense and Avoid and Control and Communications (C2) systems with adequate performance are seen as the principle challenges, so a phased introduction of UAS is anticipated while these core systems are fielded and matured over a lengthy period. The current CoA approach is termed “accommodation,” while evolution is expected towards more compliant vehicles and systems during the integration phase — ultimately, with fewer and fewer CoAs. Although the Roadmap talked about “broad timelines,” this key section doesn’t try to predict how long this all might take.
The FAA summarizes the accommodation phase as:
Accommodation of UAS in the NAS through evaluation and improvement of safety mitigations.
Work with industry and the Aviation Rulemaking Committee (ARC) to review the operational, pilot, and airworthiness regulations.
Development of required standards to support technological solutions to identified operational gaps (Minimum Operational Performance Standards [MOPS]).
Safety case validation for UAS operations in NAS — collect/analyze operational and safety data.
Robust research, modeling, and simulation for UAS Sense and Avoid, C2, and human factors.
The Integration phase is characterized by adoption of FAA regulations through certification of compliant UAS and UAS systems — the balance between CoA operations and regular operations in the NAS shifts toward more compliant, and presumably more unrestricted, access within FAA regulations. With UAS and UAS systems achieving airworthiness certificates, and trained and certificated UAS pilots filing regular flight plans for UAS operations, integration moves towards adoption. “All UAS must file and fly an IFR flight plan.” Lessons learned in earlier phases are moved into updated regulations and incorporated into equipment capabilities, and certificated UAS get increasingly better access to the airspace they require.
FAA also makes mention that in the integration phase, the six proposed UAS FAA test ranges will be selected. This has been in the works for considerable time. The assessment of proposals and award of contracts had initially been delayed on the basis of privacy questions, but these now appear to have been adequately addressed to allow these key parts of the UAS integration program to move ahead. A principle objective of the test ranges is to help provide a verification mechanism for safe operations before unmanned aircraft are integrated into the NAS. Tasks envisaged include development and proving of:
manned-unmanned operations,
certification standards and air traffic requirements,
coordination and leveraging of National Aeronautics and Space Administration (NASA) and DoD resources,
civil and public unmanned aircraft systems,
coordination with NextGen (a major NAS update program currently being undertaken by FAA).
Integration will have been successfully established when new operational rules and associated standards, policies, and procedures have been established for small UAS and other UAS, and C2 link standards have been defined for integrity, latency, and continuity. FAA will also need to have accepted Minimum Aircraft System Performance Specifications (MASPS) to enable development of detailed MOPS and the FAA should have published policy and operational guidance to define acceptable methods to comply with operational rules in accordance with an acceptable UAS certification basis for each applicant, along with flight-crew training and certification standards.
For the final “Evolutionary” phase of adoption of UAS, it’s expected that there will be seamless operations of certified UAS and crew members in the evolving NAS; FAA will have published Type Standard Orders (TSOs) based on system level MOPS; and certified Sense and Avoid algorithms will be available for collision avoidance and self-separation that are interoperable with evolving NextGen ATC systems and manned collision avoidance systems.
Quite a long list of extensive requirements to meet for a new industry that, so far, has been largely unregulated and has, so far, been used to providing rapid military/governmental solutions that prove themselves operationally over time. More empirical development to satisfy specific operational needs than compliance to published regulations. This isn’t exactly a sea-state change for the industry as it sits today, but perhaps rather a shift into another dimension.
To even get itself onto this road, let alone follow this extensive 74-page roadmap, the UAS industry may have to completely re-invent itself. But with military sales declining, the funding to take on even the simplest of these requirements may be drying up. The tendency for operators may be to try to cling to the CoA system indefinitely and just live with the hassle of applying for FAA authorization each time. FAA’s seeding of commercial applications using Restricted Type Certification of existing platforms that use existing uncertified systems and payloads may also be a way out for some time. If the Scan Eagle can gain limited access to take on commercial, paying applications because it has +800,000 proven military flight hours, eventually other UAS may also creep into some sort of equivalent eligibility. And if we manage to operate safely without major headlines, the FAA may relent in some of its extensive requirements.
Then again, the FAA just published a rather extensive roadmap, with separate backup, which says it has other ideas in mind….
I asked a couple of industry experts what they thought of the Roadmap. One comment was, “To me the real challenge is flexibility in the plan such that it will be a reasonable process to adapt to changes based on findings, experiences as this goes forward.” I agree, and believe that the FAA has gone to some length to make it clear that this is the first issue of the Roadmap, that there will be updates as more is learned. The whole process is one of learning from what has gone before in earlier stages.
Please join us Thursday, November 21, for a GPS World webcast on Unmanned Aircraft Navigation. We’ll have a number of industry leaders who will present their companies’ experience and capabilities in navigation for UAS, along with how they see this exciting market segment progressing, and how the FAA’s plans could impact their vision of the future for UAS navigation systems suppliers. Register today for free.
To fly a UAV in the U.S., you’d better be able to avoid any other aircraft — and ADS-B is one component of that capability. When the FAA and agencies around the world get their UAV regulations aligned with those levied on passenger-carrying aircraft, GNSS receivers on board UAVs will likely need to be qualified to equivalent standards. One company is already there.
When I was wandering around the show floor at the Association of Unmanned Vehicle Systems International (AUVSI) in Washington, D.C., in August, I got a pleasant surprise when I bumped into an old friend I knew from Calgary. Jayanta Ray was a grad student at the University of Calgary (U of C) when I was at NovAtel a few years ago. The students of the GNSS courses at U of C were often at local Calgary ION chapter meetings I organized or attended; there were also a few joint industry-university projects, and there were many, many discussions. So meeting Jayanta (Jay) at the Accord Systems/NexNav booth was a pleasant surprise, and it was good to renew our acquaintance.
This got me thinking that maybe some of that U of C receiver magic had somehow found its way through Jay into the airborne qualified receivers that Accord Technology is offering for UAVs. Jay is actually a member of the GPS World Advisory Board, and provides a great overview of what’s good and what’s different about airborne qualified receivers in this month’s issue of GPS World.
NexNav mini is also qualified for airborne GPS and ADS-B use.NexNav mini is also qualified for airborne GPS and ADS-B use.
Accord Technology is based in Phoenix, Arizona, and is the U.S. arm of Accord Software and Systems of Bangalore India, specializing in FAA-certified airborne versions of Accord’s GPS receivers.
At AUVSI, one of the hot topics was “Sense and Avoid” — if you are to fly a UAV in the U.S. National Airspace System (NAS), you’d better be able to avoid any other aircraft, and maybe also be able to tell other aircraft in the NAS where you are. ADS-B (Automatic Dependent Surveillance-Broadcast) is one component of that capability. ADS-B uses a network of ground stations that relay ADS-B transmissions from aircraft (called ADS-B Out) in the NAS to the Federal Aviation Administration (FAA) air-traffic management system, and the signal is also available to aircraft flying in the system if they are equipped to listen to the message (ADS-B In). Air Traffic Control (ATC) can then verify that you are where you are supposed to be, and your actual position shows up more readily on their tracking systems. Right now, ATC makes extensive use of radar tracking and aircraft transponder signals to track aircraft — ADS-B will be more efficient, less costly to maintain, and is capable of aircraft-to-aircraft position reporting. By 2020, it will be mandatory if flying within the U.S. NAS.
The other part of this story is that, eventually, when the FAA and other agencies around the world get their UAV certification regulations aligned with those levied on passenger-carrying aircraft, GNSS receivers on board UAVs will likely need to be qualified to equivalent airborne standards.
Accord has already done an enormous amount of work to qualify its NexNav receivers for both requirements, and was at the AUVSI conference to let the UAV community know that these receivers are available now. If you were developing a new UAV now, with a view to selling lots into the anticipated wide range of commercial applications, its certainly going to help your case with the certification authorities to install as much off-the-shelf certified avionics as you can. Accord already sells these receivers to a number of general aviation system manufacturers, and also supplies stand-alone ‘TSO’ed” receivers in enclosures for use on a number of aircraft types. When an airborne receiver is granted the TSO (Technical Standard Order) designation by the FAA, it recognizes that the receiver has been designed, built and qualified to stringent airborne technical requirements and is authorized by FAA for use on aircraft.
So how does a company with its HQ in India get to hold an FAA TSO for a GPS receiver? Well, other than taking years to develop the receiver in accordance with approved development standards, document the hardware and software design, and conduct test and verification activities, the company also proves to the FAA that the receiver meets the FAA-specified airborne GPS functional requirements. Loads of engineering work — and then you have to convince FAA that you did it all and did it right.
Accord in Bangalore actually teamed up with AvValues in Phoenix to form a joint venture known as Accord Technology (AT) to work the project together. Most of the original receiver development work was done in Bangalore, while AT in Phoenix became responsible as the design authority, and for production, certification activities, customer service, product support, and business development. Naturally, Accord in India still does ongoing engineering support and supplies receiver cards to AT under contract. The other twist to the story is that final assembly and test is carried out at the AT facility in Anchorage, Alaska, where the TSO was approved by the local FAA office.
But Accord isn’t only into airborne receivers. The company has been around since 1991 and has significant engineering resources (around 400 electronic and computer engineers) — with more than 700 man-years of GNSS R&D and production involvement. Here are some examples of the other GNSS products which Accord has in its technology/product inventory:
GPS L1 RF down-converter.
GPS RF & baseband.
GPS module.
GPS Spacecraft Positioning System (SPS).
Time-code generator.
SPS was developed for the Indian Space Research Organization (ISRO) and has been flown on all Indian low-Earth-orbit satellites, including IRS P4/5/6, TES, CartoSat, SRE and OceanSat.
IRNSS Reference Receiver.
The Reference Receiver is fielded in the ground-monitoring network for the Indian Regional Navigation Satellite System (IRNSS), which may mean that the ground network is using at least dual-redundant reference data, as NovAtel has also provided a similar receiver for IRNSS. Accord is also working on IRNSS user receivers.
Other receivers include high-dynamic GPS-GLONASS receivers, GPS/GLONASS/Gagan SBAS receivers, an internal GPS/GLONASS/Gagan simulator, and a handheld GPS/Gagan receiver with integrated three-axis compass and pressure altitude sensor — the latter used by a number of paramilitary forces.
Accord GNSS roamap.
And as can be seen from the Accord GNSS Roadmap, they aren’t done yet!
You might ask yourself, where in the heck did all this come from? Certainly, there is an element of internal support with work for ISRO and Indian forces, but you don’t jump into this without some background. Well, the principle activity for Accord has been and still remains high-integrity software development for avionics systems — this is probably what Accord is known for in Europe and to a certain extent in North America. Its customer list for RTCA DO-178B/C airborne software sounds like a who’s who of aircraft and helicopter manufacturers — including Airbus, Boeing, Mitsubishi, Gulfstream Eurocopter/AugustaWestland/NHIndustries, Sikorsky, and Hindustan Aeronautics Limited (HAL).
Accord’s activities have included complete and partial life-cycle activities — all the way from requirements definition, software design and development, to independent verification and validation. For those of us who’ve worked in this field, we recognize that these are considerable technical capabilities — indeed, more than 50 engineers at Accord have been trained in the art of airborne software development by FAA-qualified engineering representatives. Working in this area and successfully bringing avionics systems through the qualification/certification process, companies either become capable or break all their bones trying! Clearly, Accord has been schooled in systems that are at the forefront of avionics technology, and has passed through the practical fire of qualifying airborne systems successfully.
So, it’s not really surprising that Accord went on to spin off into airborne GNSS receiver development once it gained wide visibility and knowledge of aviation technology and began to look at related markets. And with the Indian government policy of developing indigenous industries, Accord likely had some internal Indian customers. Quite a number of parallels with the way Europe has encouraged its own GNSS industry through the Galileo program.
With several avionics OEM manufacturers already using embedded NexNav TSO certified receivers in their systems using incorporating licensed designs, Accord looks well positioned to continue its airborne market growth. Accord’s success has so far been in general aviation, but it has wider aspirations, which include commercial transport aircraft (airline aircraft) — this is a segment which has the highest level of development/certification scrutiny and is therefore the most expensive segment in which to compete. Let’s hope Accord continues its growth and there is room in an expanding market for these relative newcomers.
NovAtel, an OEM provider of high-precision GNSS positioning products, has been contracted by the Federal Aviation Administration (FAA) to produce and deliver 176 Wide Area Augmentation System (WAAS) third-generation reference receivers (G-III).
The contract includes engineering support for the receiver as well as support for the current generation reference receiver (G-II), Geostationary Earth Orbit Uplink Subsystem – Type 1 (GUST) receiver, and Signal Generator (SIGGEN).
The third-generation WAAS program is a technology refresh of the highly successful, currently operating second generation WAAS Satellite-Based Augmentation System (SBAS). WAAS provides integrity monitoring, correction data, and increased satellite availability to users of GPS within its coverage area. The integrity monitoring features of the WAAS allow the use of GPS L1 C/A for safety-of-life applications and in particular for the civil aviation industry. The third-generation WAAS will monitor and augment the modernized GPS L5 signal, allowing aviation receivers to operate in two protected aviation frequency bands with assured integrity.
NovAtel’s WAAS G-II receiver.
NovAtel’s reference receivers and uplink station equipment have been a central element of the WAAS since its inception. The G-III reference receiver uses fully updated hardware and tracks all GPS signals including the legacy GPS L1 C/A, L2P(Y) (semi-codeless), and the modernized L2C, L5, L1C signals as well as the WAAS L1 C/A and L5 signals.
The WAAS G-III reference receiver provides a rich set of range measurement data, signal integrity metrics, and logs for processing by the system’s data communication processor. The receiver architecture is designed to facilitate future expansion and reconfiguration to support the evolving needs of WAAS and other SBAS systems worldwide, including multi-constellation augmentation systems.
“We have a long relationship with the FAA and have worked very closely with the WAAS program team to develop a third-generation ground reference receiver that carries over the pedigree of our first and second generation products, while adding features and processing capacity required for the modernized system,” said Jason Hamilton, director of marketing for NovAtel. “The WAAS G-III was designed and tested specifically for ground reference networks requiring reliable continuous operation, high-longevity components, and DO-178B design assurance.”
Aerospace GNSS receivers constitute a class apart, compared to their more popular relatives used in automotive, cell phone, or survey applications. Automotive and cell-phone receivers can sometimes provide position information even in indoor environments. The survey class of receivers provides centimeter-level accuracies. However, neither group can guarantee the reliability and integrity of the position solution, and users rely upon them at their own risk, and only in non-critical applications.
On the other hand, an aerospace GNSS receiver not only provides decimeter-level accuracy, but it also guarantees that the position error is bounded by an integrity limit. The probability that the position error is more than the integrity limit is very rare: one in ten million times.
Now, isn’t that the best class of GNSS receiver?
A certified aerospace GNSS receiver stands as the keystone of the Federal Aviation Administration’s (FAA’s) ambitious NextGen Aviation program for the United States. The FAA developed NextGen to revolutionize the way an aircraft flies in the U.S airspace. In its June 2013 update report, the FAA states that “NextGen is providing major benefits to the general aviation community. The Wide-Area Augmentation System (WAAS) has improved general aviation access to more than 1,500 airports in all kinds of weather with no costly investment in ground infrastructure.”
According to the report, by the end of the NextGen mid-term in 2020, NextGen improvements will reduce delays by 41 percent from today. The FAA estimates that by 2018, NextGen will reduce aviation fuel consumption by 1.4 billion gallons, reduce emissions by 14 million tons, and save $23 billion in costs. NextGen also has an important safety impact for air travelers.
Tens of thousands of aircraft are already equipped with WAAS receivers, which improve the availability, accuracy, and integrity of GPS signals. Pilots take advantage of WAAS technology to fly approach procedures using Localizer Performance with Vertical Guidance (LPV) to altitudes as low as 200 feet. The FAA has published 3,123 WAAS LPV approaches as of May 2013 and expects to publish 5,218 by 2016.
The key to NextGen is the aerospace GPS-SBAS receiver.
How different are aerospace GNSS receivers from commercially available receivers, including high-precision receivers?
An aerospace GPS-SBAS receiver is characterized by very high reliability, accuracy, and availability. Among these attributes, the reliability factor is the most important parameter. Misleading information from an aerospace receiver should be extremely improbable, since that can lead to hazardous or severe major consequences to the aircraft, its passengers, and flight crew.
Table 1 shows the major differences between a standard GNSS receiver and an aerospace GNSS receiver.
Table 1. Differences between a standard GNSS receiver and an aerospace GNSS receiver.
Performance Requirements
The DO-229D standard document — formally, the RTCA Minimum Operational Performance Standards for GPS/WAAS Airborne Equipment — specifies the minimum performance standards of an aerospace GPS-SBAS receiver. In particular, an aerospace GNSS receiver needs to meet the GPS and SBAS signal processing requirements, GPS and SBAS data/message processing requirements, satellite integrity status requirement, accuracy requirements in presence of interference, dynamic range and sensitivity requirements, and so on, as defined in DO-229D standard.
Most importantly, the receiver must meet the Receiver Autonomous Integrity Monitoring (RAIM) requirements for en-route, terminal, non-precision and precision phases of flight of DO-229D. Additionally, the receiver must meet the fault detection, fault exclusion, missed alert, false alert, step detection, ramp detection, and other integrity-related requirements of DO-229D.
Further, the receiver needs to meet the environmental conditions specified in DO-160 standard for temperature, temperature variation, altitude, humidity, shock, vibration, magnetic effects, voltage spike, EMI/EMC, lightning, and so on.
Safety and Reliability Aspects
A Functional Hazard Assessment (FHA) based on the intended function of the GPS-SBAS receiver software needs to be carried out to determine whether the receiver meets the requirements of hazardously misleading information. The safety and reliability aspects of the receiver are computed through Failure Mode and Effect Analysis (FMEA) and Fault Tree Analysis (FTA). The effects of each failure mode are determined at the system level for each operating mode of the equipment.
RAIM. For an aerospace GPS-SBAS receiver, RAIM is of paramount importance. The measure of protection provided by RAIM is given by Horizontal/Vertical Protection Limits (HPL/VPL). HPL is used as the protection limit for en-route, terminal, and LNAV (Non-precision approach) phases of flight and compared against the Horizontal Alert Limit (HAL) for the phase of flight. Whereas, VPL is compared against the Vertical Alert Limit (VAL) for the LNAV/VNAV and LP/LPV phase of flight.
The most critical part of the integrity requirement is to detect a satellite failure and, if possible, to make corrective actions in addition to generating timely alerts. A Failure Detection and Exclusion algorithm, often known as FD/FDE, is to be implemented in an aerospace GNSS receiver. The effectiveness of the FD/FDE algorithm has to be tested extensively in off-line condition for availability of satellite failure detection and exclusion. Further, the algorithm has to be tested in on-line conditions as well as on a target environment. There has to be a match among the off-line,
on-line, and on-target test results for using the algorithm in
the GNSS receiver.
The integrity tests on an aerospace GNSS receiver are carried out as per the guidelines in DO-229D. This requires simulation of the GPS orbit and determination of satellite visibility at more than two thousands grid points on the Earth surface and for 12 hours at 5-minute time intervals. The FD/FDE algorithm is validated at each space-time point to determine the availability of failure detection and exclusion.
For the non-precision approach, the space-time points are arranged in terms of the HPL values and Horizontal Exclusion Limit (HEL) values and the most difficult to detect/exclude satellite is identified. Extensive Monte Carlo simulations are carried out at the selected space-time points to validate the false alert and missed alert requirements of DO-229D standard. Similar tests are carried out on the GNSS receiver for the precision approach, wherein the VPL values are considered instead of HPL values. Further, the test results of the off-line tests are validated through comprehensive on-line and on-target tests on the selected space-time points.
Certification Aspects
To ensure that the software and the firmware of the aerospace GNSS receiver are robust, providing adequate levels of safety and reliability, the receiver software and firmware need to be developed conforming to the software and hardware design assurance standards — DO-178B and DO-254 respectively. Based on the criticality of the end application, the design assurance should meet DO-178B and DO-254 objectives of Level A, B, or C criticality.
An aerospace GNSS receiver needs to be certified by the FAA (or other competent authorities in other countries) for airworthiness. The FAA gets involved in the certification process right from the planning stage and oversees the compliance of the entire development process as per DO-178B and DO-254 standards. The aerospace GNSS receiver software and firmware undergo extensive verification and validation processes. Further, the GNSS receiver is subjected to all the functional and environmental tests as per DO-229D and DO-160 standards respectively under FAA supervision. Only after the successful completion of all the software, hardware, and systems tests, the receiver is certified by the FAA for airworthiness through Technical Standard Order TSO-C145 Authorization (TSOA).
Conclusion
Aerospace GNSS receivers, by virtue of their inherent safety, reliability, and integrity, are far more suitable for critical applications, where an error could have hazardous or catastrophic consequences. These receivers must be used in commercial transport aircraft, business jets, general aviation aircraft, gliders, experimental aircraft, balloon, and so on. Further, in airport surface vehicles and mass-transport vehicles such as high-speed trains, trams, and unmanned autonomous vehicles of all sorts, whether ground or air, receivers similar to aerospace GNSS receivers should be used for navigation and surveillance purposes.
Jaynata Ray received his Ph.D. from the University of Calgary. He has worked in the GPS field since 1992, and is group manager at Accord Software and Systems in Bangalore, India. He is a member of GPS World’s Editorial Advisory Board.
Accord Technology, maker of NexNav products, is debuting its capabilities for enabling fully FAA compliant GPS for Detect and Avoid at the AUVSI Unmanned Systems annual convention, being held in Washington D.C. August 12-15.
Known for its certified, U.S. FAA ADS-B fully compliant GPS WAAS/SBAS sensors and receivers for NextGen solutions in the airline, business and general aviation industries, NexNav products include OEM circuit-card assembly receivers the size of a credit card as well as line replaceable sensor units.
This is the company’s first time exhibiting at the AUVSI conference.
“We are excited to be exhibiting at this show and I believe our NexNav products will fill a niche that the unmanned aircraft need,” commented Hal Adams, Chief Operating Officer for Accord Technology, LLC. “Our NexNav product already meets FAA requirements and us currently flying on many manned platforms as well as on EU UAS platforms now. I look forward to talking with attendees about the Detect and Avoid GPS solution NexNav can provide them.”
Accord Technology received TSO-C145c for its NexNav mini in 2010, and fully qualified as GPS source per the U.S. FAA ADS-B Advisory Circular 20-165. The NexNav mini GPS technology was the first GPS WAAS sensor to be authorized U.S. FAA TSO-C145c WAAS Class Beta-1 ONLY. It is a market-breaking hybrid of automotive technology and aviation requirements providing an affordable solution for ADS-B GPS source, Accord said.
Denver International Airport (DIA) has fully implemented its new arrival and departure procedures, the next phase in the Federal Aviation Administration’s mass overhaul of U.S. airspace, called NextGen. Denver is among the airports at the front end of the adoption process, and is highlighted in an in-depth feature in the Denver Post.
According to the article, “The recently completed phase at DIA trims arrival and departure fuel costs by eliminating several intermediary steps. The traditional system requires an airplane to come into and out of cruising altitude by firing its thrusters at every new altitude level, wasting hundreds of pounds of fuel… The traveling public will not likely notice an immediate difference in travel time, but proponents hope that the early investment pays off in the end.”
The FAA predicts that NextGen improvements will reduce flight delays by 38 percent and lead to a 1.4-billion-gallon total reduction of fuel burn by 2020.
Accord Technology’s NexNav GPS receiver will be supporting FreeFlight Systems with its recently awarded FAA Capstone Retrofit Project. In March 2013, FreeFlight and Accord announced their collaboration to develop practical and cost-effective ARINC 429 WAAS GPS solutions that enable aircraft operators to meet ADS-B, RNP (0.3) and other performance-based navigation mandates, worldwide.
The NexNav Circuit Card Assembly (CCA) will integrate with FreeFlight’s upgraded automatic dependent surveillance-broadcast (ADS-B) avionics to fulfill the requirements of the second phase of the FAA Capstone Project.
“This is an excellent example of how we are working closely with FreeFlight Systems to create state-of-the-art NextGen solutions that are not only meeting upcoming mandate requirements but doing it in a cost effective manner,” stated Hal Adams, Chief Operating Officer for Accord Technology, LLC.
The Accord Technology NexNav product line revolves around two key receivers, NexNav mini and NexNav MAX. The receivers are at the heart of embedded customer solutions whether as a Circuit Card Assembly (CCA) or embedded in the Line Replacement Unit (LRU) as a stand-alone GPS solution.
NexNav mini was the industry’s first GPS receiver and sensor qualified to fully support the known worldwide and U.S. FAA ADS-B GPS source requirements The NexNav mini and MAX are compatible with EGNOS and other Satellite Based Augmentation Systems (SBAS) to the extent they are is compatible with WAAS.
Unmanned aerial vehicles and civil aircraft may co-habit the airspace after September 2015.
As the U.S. Federal Aviation Administration (FAA) moves ahead with plans for unmanned aerial systems/vehicles (UAS/UAV) to have regular access to U.S. airspace by 2015, it has encountered several barriers. For UAVs to be treated like manned aircraft, their systems likley need to be qualified to the same standards as civil avioncs. This is a challenge, as each UAS has largely unique systems. UAS equipment standards are emerging, but threats to GNSS abound, requiring defense/mitigation.
Demand for UAS has produced many different types flying in a range of applications. With no apparent standard avionics fit or uniform safety standards, each UAS type is basically configured for specific tasks. Commercial UAS applications continue to emerge, and major market growth is anticipated. One forecast indicates that the UAS market could reach $7.26 billion this year alone. The promise of new and better ways to reduce costs, improve safety, and increase operational efficiency feeds market expansion.
However, in the United States the FAA currently requires each UAS commercial project desiring access to controlled airspace to obtain an FAA-approved Certificate of Authorization. While the FAA has made efforts to speed up approvals, this process slowed widespread commercial adoption of UAS. Nevertheless, opportunities abound in pipeline and transmission line inspection, crop spraying, law enforcement, security, and surveillance, survey/mapping, remote area mail delivery, and hundreds of other applications. The FAA may have felt some pressure to move forward, because Congress has put in place the Modernization and Reform Act of 2012, which calls on the FAA to fully integrate unmanned systems, including those for commercial use, into the national airspace by September 2015.
UAS in the NAS. Meanwhile, a project called the Unmanned Aircraft Systems Integration in the National Airspace System (UAS in the NAS), undertaken by NASA’s Dryden Flight Research Center, seeks to reduce technical barriers related to safety and operational challenges associated with enabling routine UAS access to the NAS.
Europe has also launched a study on the integration of UAS in non-segregated airspace for the future Single European Sky. The ICONUS study will be carried out by a consortium within the European air traffic management program called Single European Sky ATM Research Programme (SESAR). The study will drive the definition of the requirements, capabilities, and equipment which UAS will need to operate safely and efficiently in the coming European SESAR environment.
The U.S. RTCA SC-203 committee is drafting UAS operational requirements, and there has been significant progress towards publishing Minimum Aviation Performance Standards (MASPS), including requirements for navigation. Europe has similar activities underway aimed at improving UAS access to its airspace.
MOPS. The big picture is that requirements for unmanned aircraft are being brought into conformance with the standards applied to the performance and behavior of manned aircraft. Navigation requirements for UAS are expected to specify that systems will need to be qualified to Minimum Operational Performance Standards (MOPS). This means that on-board electronics, including GNSS systems, will probably need to be FAA Technical Standard Orders (TSO) qualified, just as they are now for manned aircraft.
Why do we need to investigate certified avionics now? In the scheme of avionics, more than two years breathing space to certify UAS avionics systems is not a long time, not at all, until the September 2015 deadline. FAA airborne software and hardware qualification will take much time and effort to implement, and re-configuration of systems, interfaces, and operating procedures may take even longer.
For Manufacturers. UAS makers have the option to move forward in stages. For instance, by selecting a few existing airborne-qualified OEM avionics, they could minimize the internal effort to comply. As the first UAS with certified avionics emerge, they will probably get good support from FAA to adopt U.S. operating rules for the NAS. Embedding an existing certified GPS receiver in UAS avionics will reduce the internal work needed and allow more effort for developing commercial market opportunities that look to quickly adopt UAS.
Meanwhile, efforts are in full swing to change the U.S. and European navigation landscapes over the next few years. So it would be better to be ready with a capable GNSS receiver that is already built to meet the challenges of NextGen and SESAR.
GPS III and Galileo. The L5 civil GPS frequency may be operational around the time that UAS unrestricted access becomes possible. GPS L1/L5 dual-frequency operations will enable higher navigation accuracy, reliablity, and integrity. The FAA is already developing NextGen WAAS to include L5, and revisions to the GPS MOPS to include L5 should begin shortly, in time for a usable GPS L5 constellation in 2015/2016. The FAA is already preparing for L5 avionics, and industry investigative work is underway. Its possible that GPS L1/L5 may meet the accuracy and integrity requirements for CAT II/III automated landings. In Europe, Eurocae work is expected to gain momentum for the Galileo E1/E5a MOPS as the Galileo satellite navigation system becomes operational.
The new GNSS environment also includes WAAS/SBAS precision approach (localizer performance with vertical guidance, or LPV) capability: LPV is available now in the United States and will soon be in wider operation in Europe. Automatic Dependendant Surveillance (ADS-B) is rolling out in the United States and around the world. ADS-B is being mandated within the U.S. NAS as the means for air-traffic control to track all aircraft, so UAS avionics will need to include certified ADS-B Out capability.
In one commercial instance, the Septentrio AiRx2 receiver comes out of the box as a certified L1 GPS with ADS-B and WAAS LVP, but is also ready for GPS L5 and Galileo E1/E5a.
Even as greater steps forward enhance how GNSS is used in this wider definition of aviation that will soon include UAS, a team at the University of Texas demonstrated how a UAV could be maliciously side-tracked (see article on page 30 of this issue) — reminiscent of the Iranian downing of a U.S. surveillance drone in December 2011.
Admittedly the GPS on the vehicle in the UT test was not a qualified airborne receiver, but how could this happen when there was also an inertial sensor and a radio-altimeter on the UAV? A good question, which UAV manufacturers will need to consider when they implement their on-board Kalman filters, knowing that spoofing is now an additional threat to parry.
Couldn’t we detect that high-power RF spoofing signal at the front-end of the GPS receiver? Even if only to tell the on-board systems that there could be hazardous misleading information about? Or run separate GPS and GPS/inertial position solutions, detect significant divergence, and set the same warning flag? And multi-constellation, multi-frequency receivers, and even controlled radiation pattern antennas — all things to investigate. More work for the aviation receiver guys who labor tirelessly to improve GNSS integrity.
Of course if you hijack a UAV with a high-power spoofer, you are also spoofing civil transports operating in the same airspace, so now there is the potential to trigger a Federal investigation. It will probably be easier to detect this stuff with moving airborne sensors rather than the fixed ground equipment used to find jammers on trucks at Newark airport, and lots of pilots likely providing real-time location information on radios if their GPS goes even a little haywire. All would help to quickly locate and shut down any spoofer. Nevertheless, it’s a threat to be mitigated.
Fatal Crash. In South Korea, the effects of intermittent North Korean jamming of GPS to disrupt seal, land, and air navigation in the South may have contributed to the recent fatal crash of a Schiebel Camcopter S-100 drone, a 150-kilogram rotorcraft capable of 220 km/h flight. It should have coped with loss of GPS as the Camcopter has multiple inertial measurement units that allow safe operation and recovery in the absence of GPS signals. Emergency procedures to ensure a safe recovery in such a situation do not appear to have been correctly and adequately followed, manufacturer Schiebel alleges.
NovAtel may have found one way to help mitigate spoofing on UAVs; the company released a combined civil/SAASM GPS receiver, the OEM625S, aimed specifically at UAVs. Granted, the idea is to add SAASM anti-spoofing capability to a number of UAVs which currently use NovAtel commercial receivers, mostly in military systems. That may be motivated by the desire to avoid further Iranian incidents!
BAE Systems has been thinking of giving GPS a back-up for just those situations where jamming or even spoofing is detected. BAE’s Navigation via Signals of Opportunity (NAVSOP) system was just announced at the Farnborough air show in the UK and is still in research phase, but looks extremely promising. It interrogates the radio environment for the ID and signal strength of local digital TV and radio signals, plus air traffic control radars, with finer grained adjustments coming from cellphone masts and Wi-Fi routers. Mapping the location of all these sources might be quite an undertaking, and given that these are all non-safety-of-life commercial signals, the sources are subject to the vagaries of power outages, regular maintenance, and breakdowns. Nevertheless, with such a multitude of signals, NAVSOP could well turn out to be a viable back-up for GNSS.
So, shared access to civil airspace, wider applications in commercial operations, and changes in equipment qualification, along with potential solutions for GNSS jamming and spoofing: lots to consider for the UAS industry.
Taking It to the House
U.S. House of Representatives Committee on Homeland Security; Subcommittee on Oversight, Investigations, and Management; Hearing, July 19, 2012: Using Unmanned Aerial Systems Within the Homeland: Security Game Changer?
Testimony by Todd E. Humphreys, Ph.D.; Assistant Professor, Cockrell School of Engineering, The University of Texas at Austin. [Excerpted. Prof. Humphreys is a co-author of the article “Drone Hack” in the August issue of GPS World.]
The vulnerability of civil GPS to spoofing has serious implications for civil unmanned aerial vehicles (UAVs), as was recently illustrated by a dramatic remote hijacking of a UAV at White Sands Missile Range.
Hacking a UAV by GPS spoofing is but one expression of a larger problem: insecure civil GPS technology has over the last two decades been absorbed deeply into critical systems within our national infrastructure. Besides UAVs, civil GPS spoofing also presents a danger to manned aircraft, maritime craft, communications systems, banking and finance institutions, and the national power grid.
Constructing from scratch a sophisticated GPS spoofer like the one developed by the University of Texas is not easy. It is not within the capability of the average person on the street, or even the average Anonymous hacker. But the emerging tools of software-defined radio and the availability of GPS signal simulators are putting spoofers within reach of ordinary malefactors.
There is no quick, easy, and cheap fix for the civil GPS spoofing problem. What is more, not even the most effective GPS spoofing defenses are foolproof. But reasonable, cost-effective spoofing defenses exist which, if implemented, will make successful spoofing much harder.
I recommend that for non-recreational operation in the national airspace civil UAVs exceeding 18 lbs be required to employ navigation systems that are spoof-resistant.
More broadly, I recommend that GPS-based timing or navigation systems having a non-trivial role in systems designated by DHS as national critical infrastructure be required to be spoof-resistant.
Finally, I recommend that the DHS commit to funding development and implementation of a cryptographic authentication signature in one of the existing or forthcoming civil GPS signals.
The potential vulnerabilities of U.S. national transportation, communications, banking and finance, and energy distribution infrastructure;
What does it take to build a spoofer? Buy a spoofer?
Range and required knowledge of target.
Fixing the problem:
• Jamming-to-noise sensing defense;
• Defense based on SSSC or NMA on WAAS signals;
• Multi-system multi-grequency defense;
• Single-antenna defense;
• Defense based on spread-spectrum security codes on L1C;
• Defense based on navigation message authentication on L1C, L2C, or L5;
• Correlation prole anomaly defense;
• Multi-antenna defense;
• Defense based on cross-correlation with military signals.
The Federal Aviation Administration (FAA) has awarded Raytheon Company a two-year contract extension to continue to provide services for the Wide Area Augmentation System (WAAS), a safety system that provides satellite-based navigation in the continental United States, Alaska, Canada and Mexico. The $30.1 million contract extends the period of performance through Sept. 24, 2013.
“Raytheon has been the FAA’s prime contractor for WAAS since the system was commissioned for operational use in the United States in 2003,” said Michael Prout, vice president of Security and Transportation Systems for Raytheon’s Network Centric Systems business. “The contract marks another milestone in the continuing partnership between Raytheon and the FAA to improve safety and efficiency for pilots.”
According to the announcement, Raytheon will provide life-cycle support and other services to improve service reliability and availability, and increase the coverage area through system enhancements. WAAS enables GPS to meet air navigation performance and safety requirements for en route, terminal, non-precision approach, and approach with vertical guidance operations.
When jamming interfered with GPS signals at Newark Airport, a three-month effort determined that low-power, mobile personal-privacy devices were responsible. This article describes how they were found and outlines how the observable parameters of such devices encompass a wide variation in RF spectra and internal modulation.
Personal privacy devices (PPDs) are now recognized as being responsible for causing interference to GPS receivers. However, in November of 2009, when the Local-Area Augmentation System (LAAS) installed its first Ground-Based Augmentation System (GBAS) at Newark International Airport (EWR), this fact was not known. Within the first month of its installation, anomalies in GBAS processing were correlated to the presence of radio-frequency interference (RFI). Initial efforts to determine the source of this unexpected RFI were not successful.
The Federal Aviation Administration (FAA) had a significant interest in finding this RFI source, leading to deployment of RFI detection and location equipment by several groups. Zeta Associates temporarily installed equipment in early January 2010 that was capable of detecting and characterizing RFI but did not have emitter location capability.
Determining that an RFI transmitter is in motion is more certain if the RFI is observed simultaneously by multiple sensors. However, analysis from hundreds of RFI events indicates that when an RFI source is in motion, observations collected by a single sensor can provide sufficient information to determine that the RFI transmitter is in motion.
Continuing interest in understanding PPD effects on GPS receivers led to the installation of remotely accessible monitoring equipment that provides detailed characteristics of these devices. Remote access facilitates monitoring, particularly since PPDs are present for 30 to 60 seconds at a time and only a few times a day.
Background
The January 2010 deployment included a WAAS GPS receiver, spectrum analyzer, and a Zeta custom-developed Snapshot System, assembled from commercial off-the-shelf (COTS) equipment for conducting WAAS site-installation surveys, and capable of capturing intermittent short-duration RFI events. It consists of a tuneable receiver (10 MHz to 3 GHz) whose RF front end spans 25 MHz that is digitized at a sample rate of 56 MHz, with storage capacity sufficient for up to 80 minutes. Once captured, the time-series data can be analyzed in many different ways. Possible analysis techniques include examination of the raw time samples, generation of spectral plots, or demodulation of the RFI signal. Each approach can lead to a better understanding of the underlying interference signal. If digital data is present and can be demodulated, it might be possible to associate the demodulated bits with a known transmitter.
Data can be captured manually or programmatically using a trigger determined by an algorithm that monitors WAAS GPS receiver automatic gain control (AGC) logs. The AGC function within a WAAS receiver has a well-behaved response for normal Gaussian noise RF environments. When RFI is present, the AGC exhibits atypical responses that then trigger the Snapshot System. As WAAS receivers utilize both L1 and L2, and each RF path has its own AGC, it is possible to detect the presence of potential RFI at either L1 or L2.
The Snapshot System RF input for this deployment was from a PCTEL antenna identical to those used at WAAS reference sites. This antenna incorporates a triplexer that provides three separate 40 MHz passbands each centered on L1, L2, and L5, with approximately 50 dB of gain. This antenna was located approximately one mile north of the four LAAS antennas within Port Authority of New York and New Jersey (PANYNJ) Building 80.
Within the first hour of being deployed on January 20, 2010 the Snapshot System had detected and captured one RFI event in the GPS L1 band. After one day, the Snapshot System had detected and captured more than 25 separate instances of RFI within the GPS L1 band. Most RFI events were narrowband (10s of kHz bandwidth) and short duration (no more than 3 seconds).
However, there also were five RFI events that spanned more than 15 MHz across L1 (Figure 1) were present as long as 20 seconds and at a power level as much as 25 dB above the receive antenna’s noise floor. Some of these RFI events were strong enough to reduce a WAAS G-II receiver C/N0 by as much as 20 dB and thereby resulted in loss of tracking for lower-elevation GPS satellites. Higher-elevation GPS satellites were able to continue tracking throughout these events but at a lower C/N0. The wideband RFI events were also detected by the SLS 4000 GBAS monitor and coincided with tracking problems in the LAAS GBAS receivers.
FIGURE 1. EWR wideband RFI.
Two of the captured broadband RFI events were demodulated and analyzed. The underlying linear frequency modulation (FM) signal swept over more than 15 MHz in less than 1 millisecond (Figure 2).
FIGURE 2. FM demodulated wideband RFI.
At that time, it was not known if the source of the RFI was stationary or moving, whether it was unintentional (emanating from a licensed transmitter but with malfunctioning electronics), inadvertent (equipment normally used for test purposes and capable of operating in the GPS band but accidentally left on), or intentional (purposeful jamming of GPS).
Since the RFI was observed by GPS receivers separated by 1,700 meters, a search was undertaken to identify any other GPS receivers in the vicinity of EWR. One National Geodetic Survey (NGS) continuously operating reference site (CORS) NJI2 is located near EWR about 4,500 meters northwest from Building 80. Analysis of data from NJI2 during the same time periods that RFI was detected by the WAAS and LAAS receivers did not contain any indication of RFI, and therefore suggested that the source of RFI was more localized to EWR.
The Snapshot System remained in place for approximately two weeks before moving to another location. Collected data was analyzed, showing that wideband RFI was associated with significant degradation to both the WAAS and LAAS receivers. Additional characteristics noted the RFI was intermittent, lasting typically 30 seconds but no more than 60 seconds, was observed more often Monday through Friday, and most frequently around 8 a.m. local time.
Locating The RFI
Figure 3 shows a Google map of EWR with blue dots indicating the location of the four LAAS antennas, a green dot for Building 80, and a yellow dot for the GBAS shelter. EWR is adjacent to the New Jersey Turnpike (NJT), which has seven southbound and seven northbound lanes of traffic.
FIGURE 3 Google map of EWR.
Since the Snaphsot System did not include location capability, other teams with direction-finding equipment, including beam-forming antennas, travelled to EWR to try to locate the RFI source. These teams were on site at various times from February to March. However, those efforts did not provide sufficiently reliable information to reduce the search area. By mid-March, the search area remained identical to that of January.
Zeta then deployed two WAAS G-II receivers separated by considerable distance (1,722 meters) to monitor for RFI, and analyze each receiver’s response only when RFI sufficient to significantly degrade GPS reception was detected. One receiver was located within Building 80, and the second receiver within the GBAS shelter near the LAAS antennas. This configuration was designed to determine degradation relative to each reference receiver and thereby establish probable search areas for the RFI emitter. The Zeta equipment also incorporated a rotating directional antenna (at the GBAS shelter shown in Figure 4) that was commanded to rotate only when significant RFI was detected.
FIGURE 4A. Antennas on roof of GBAS shelter.FIGURE 4B. Antennas on roof of GBAS shelter.
The expectation was that RFI would be detected simultaneously by both GPS receivers, and that the relative degradation in normalized C/ N0 would provide an indication as to which location lay in closer proximity to the RFI source. The rotating high-gain directional antenna would then indicate a reduced probable search area consistent with the relative degradation between the two receivers. At the time this equipment was deployed, it was still thought that the RFI was most likely stationary and high-power. However, the measurement results were quite different than expected. Subsequent data analysis from this equipment revealed that the RFI was low-power and moving, specifically moving along the NJT.
The Zeta equipment was deployed on March 19, 2010, and remained in place while operating automatically. On March 25, data collected during the previous week were analyzed. During this 1-week collection there were 11 instances when both receivers detected wideband RFI events and one antenna rotation even partially tracked one wideband RFI emitter. Such data was indicative of a non-stationary emitter, a finding that was quite significant. Based on data from the two receivers, the apparent velocity of the RFI emitters ranged between 45 miles per hour (mph) to 72 mph. Initial analysis of antenna-rotation data also indicated the RFI source was east of the GBAS shelter and moving south on the NJT.
Understanding the importance of degradations from both receivers was crucial in determining that the RFI has attributes of transmitting at low power and is moving. Had a single stationary RFI emitter been responsible for these observations, the degradations measured at each receiver would have occurred at essentially the same time, not 50 to 80 seconds apart. A high-power moving RFI emitter would also have produced degradations at both receivers at the same time, and since that was not observed, the conclusion was that the RFI emitter was relatively low in output power. Low-power RFI emitters will cause significant degradation to GPS receivers only when they are in close proximity to them, on the order of hundreds of meters.
Receiver data logs were processed specifically for degradation in normalized C/N0. Normalized C/N0 was only computed for those satellites above 20 degrees, and all of those results were averaged together. Prior knowledge regarding WAAS PCTEL antennas has established an expected C/N0 versus satellite elevation that is accurate to approximately ±1 dB with a nominal mean of 0 dB. This normalized C/N0 represents an average of all satellites in view. However, individual satellite signal strength can vary greater than ± 1 dB. Significant deviations of more than –3 dB are indicative of strong RFI within the GPS processing band. Normalized C/N0 was plotted for each day that data was collected, followed by expanding those time periods where significant degradation was present.
Figure 5 shows data of the first evidence of a low-power moving PPD. Data for Building 80 receiver is in blue and data from the GBAS shelter receiver in pink. Since Building 80 is north of the GBAS shelter, when degradations occurred first at Building 80, this implies that the RFI emitter is moving from north to south. Similarly, when degradations were first seen at the GBAS shelter, the RFI emitter was moving from south to north. This plot uses major time grids of 60 seconds and minor grids of 10 seconds.
FIGURE 5. Normalized C/N0 observed at Building 80 and GBAS shelter.
The double separate degradations observed by the Building 80 receiver have only been observed from monitoring equipment located at that building, and have since been associated with travel paths of PPDs on the nearby highways. Both GPS receiver and spectral data contain this same characteristic. This characteristic is due to the fact that vehicles traveling south on the NJT have clear line of sight to the roof of Building 80 (shown by Figure 6) before they travel under Interstate 78, after which they pass next to Building 80. During the time that they are under Interstate 78, their transmissions are blocked in the direction of the roof of Building 80.
FIGURE 6A. View of NJT near Building 80.FIGURE 6B. View of NJT near Building 80.
Spectral data as observed by the 4-foot reflector is shown in Figure 7. Figure 8 shows spectral maximum data as collected by the 4-foot linearly polarized reflector along with additional information.
FIGURE 7. Wideband RFI observed by 4-foot reflector (click to enlarge.)FIGURE 8A. Pink represents spectral maximum data as observed through the reflector, green represents the azimuth of that antenna, and blue the reported degradation of the GBAS shelter receiver.FIGURE 8B. Pink represents spectral maximum data as observed through the reflector, green represents the azimuth of that antenna, and blue the reported degradation of the GBAS shelter receiver.
When the GBAS shelter receiver at first detected RFI, the reflector began rotating from an azimuth of 0 degrees in a clockwise direction. At the same time, a spectrum analyzer began capturing spectra at a rate of 3 per second. The first spectral maximum was observed at an azimuth of 30 degrees, a direction in which the antenna was pointed towards the NJT, to a location approximately 900 meters away from the GBAS shelter. The next time spectra were at high levels occurred for azimuths between 145 to 195 degrees, or southeast of the GBAS shelter. The approach of using a rotating antenna was originally intended to provide a direction towards a stationary source and not to track a moving emitter. However, it appears that to some extent, the rotating antenna in fact did track a moving emitter from north to south.
On the afternoon of the day these results were communicated to the FAA lead for the EWR RFI investigation, all search activities were shifted to the NJT and away from the airport operating area. Just south of the GBAS shelter there is an official-use overpass that straddles the NJT. All detection equipment was positioned onto the overpass, under the hypothesis that the RFI was emanating from vehicles traveling the NJT. Evidence substantiating this initial finding was found within a day, and approximately one month later a concerted effort was undertaken to identify and stop a single vehicle that was using a PPD.
The Zeta equipment remained in place for many months and continued to provide additional evidence of PPD characteristics. Early in the investigation it was hoped that only a few PPDs had been responsible, but as more data was collected it became evident that many different types of PPDs were traveling along the NJT past EWR.
Modeling PPD Effect
Once it was realized that the RFI was from low power moving emitters, a simple model was used to predict their degradation effect on WAAS GPS receivers. The model shown in Figure 9 was used for the purpose of computing distance between the RFI emitter and a WAAS antenna and to then compute the additional level of interference noise power that the WAAS antenna would receive. Here, the WAAS PCTEL antenna is located 50 meters from a road that is 2000 meters long and straight and has an RFI emitter transmitting +25 dBm, moving at 32.5 meters per second (72.5 mph) and with clear line of sight to the WAAS antenna.
FIGURE 9. Simple model of moving emitter.FIGURE 10. Model of normalized C/No due to a PPD.
With these assumptions it is a simple matter to compute the additional noise power at the WAAS antenna. Non-coherent summation of the RFI noise and inherent system noise was used to compute the total noise power and therefore the additional degradation in C/N0. The resulting predicted degradation was overlaid on one of the actual RFI events and is shown as a green line in Figure 10. The predicted degradation closely resembles actual event data logged by receivers.
The shape of degradation in normalized C/N0 versus time has been observed in nearly all of the EWR RFI events that have been analyzed. The magnitude of degradation depends on the power of the RFI and its proximity to the GPS antenna, while its time duration depends on the velocity of the vehicle carrying the PPD. The shape is directly related to the distance versus time between the vehicle and the WAAS antenna. Faster/slower moving vehicles with PPDs will simply shrink/stretch the time scale. Curved roadways would have different shapes that could also be readily predicted.
CORS data was revisited after realizing that PPDs were traveling the NJT. Specifically, two CORS sites CTDA (70 meters from Interstate 95) and NJDY (380 meters from Interstate 95) were identified. Data from those two sites were analyzed for a couple of weekdays. Possible evidence of PPDs was found within that data. Reported Signal to Noise Ratio (SNR) from CTDA and NJDY contained variations similar to those observed by GPS receivers at EWR during times when PPD induced RFI has been detected.
Continued RFI Monitoring
The LAAS program desired continued monitoring of RFI from PPDs near EWR, including estimates of their effective isotropic radiated power (EIRP). Additional equipment was assembled to provide this capability and installed on March 3, 2011. This monitoring equipment is located within the GBAS shelter at EWR and comprises several COTS components that incorporate improvements beyond the first Snapshot System used at EWR. Improvements include an upgraded Snapshot System (Figure 11), an RHCP directional antenna, and a wireless modem that provides remote access to the monitoring equipment.
Figure 11A. Snapshot System ICEPOD6-M5.FIGURE 11B. Snapshot System laptop.
Remote access makes it possible to analyze captured RFI data from any computer connected to the Internet, and to modify software if necessary. The new equipment configuration, specifically the use of an AEL AST 1507AA RHCP antenna, was chosen with the explicit purpose of establishing more accuracy in estimated EIRP.
Analysis of data collected during 2010 indicated three significant sources of error in estimating EIRP; Free Space Loss (FSL) from not knowing the exact position of the PPD on the NJT, polarization mismatch loss between the PPD antenna and the receive antenna, and the effects due to transmission from within a vehicle. Differences in FSL loss between the closest southbound lane on the NJT and the most distant northbound lane is on the order of 11 dB. If it is known that the PPD is traveling south, the difference in FSL between the nearest to farthest southbound lanes is less but still about 6 dB. FSL differences for northbound lanes are smaller, on the order of 3 dB. Knowing the direction of travel reduces this uncertainty but does not eliminate it. The WAAS PCTEL antenna is RHCP, but at the horizon has an axial ratio of approximately 5 dB. Many PPDs appear to be using quarter wavelength dipole antenna that are mounted with a rotatable connector. Assuming all PPD antennas are linearly polarized, there would then be an uncertainty of about 5 dB when using data observed by the WAAS PCTEL antenna. The AEL antenna has an axial ratio of 0.2 dB at L1 and significantly reduces uncertainty of polarization mismatch loss. Even though the AEL antenna has a 3 dB mismatch loss, that loss has an uncertainty of 0.2 dB for any orientation of the PPD antenna. The PCTEL antenna has a symmetric gain response relative to the NJT. The AEL antenna was pointed to the north intentionally so that observed RFI power will be stronger when a PPD is north of the GBAS shelter. Simultaneous capture of real time samples from both antennas by the ICEPOD6-M5 provides an indication of the direction in which the PPD is traveling. The third uncertainty comes from the effects of the PPD being located within a vehicle. Vehicular effects on the PPD transmitters were not accounted for due to difficulty in using a simple model. Aloi [1] has measured vehicular effects of quarter wavelength dipole antenna (typically used by PPDs) and has previously published [1] [2] on the effect of vehicles on GPS signals. His most recent findings have not yet been published but indicate that the type of vehicle, the location of a dipole antenna within it, and the position outside of the vehicle from which power is being measured, can lead to significant variation (10 to 15 dB) of the observable power. Consequently, the reported EIRP estimates from the Snapshot System have been referenced to a point just outside the vehicle and do not attempt to account for vehicular effects.
Figure 12 shows a block diagram of the current monitoring equipment. The PCTEL antenna along with the WAAS G-II receiver is used for monitoring GPS signals. WAAS G-II receiver logs are monitored continuously and saved to disk, but snapshots are only taken if the RFI algorithms indicate that RFI is present. A snapshot will be taken if any of three tests (based on AGC, normalized C/N0, or spectral power) are exceeded. Narrowband RFI tends to most impact the AGC response, while wideband RFI tends to trigger the normalized C/N0 metric. Since the Snapshot System is also continuously monitoring the RF spectra from both antennas, an additional test checks if there are significant spectra changes.
FIGURE 12. Current Snapshot monitoring block diagram.
The AEL antenna is connected to a filter/low noise amplifier (LNA) (Delta Microwave L5995) identical to those within the PCTEL antenna, before it is connected to one of the two L-band tuners (900 to 2200 MHz) of the ICE-Online ICEPOD6-M5, which includes 1 TB of long-term storage and 8 GB of high-speed RAM and is capable of sustained data transfers of as high as 400 MB/s between the L-band tuners and disk. Sample rates and RF filtering are programmable and have been set to use a complex sample rate of 40 MSPS and an RF bandwidth of 30 MHz. When RFI is present, data transfers are 320 MB/s. The internal 1 TB disk can store approximately 100 minutes of RFI. Software parameters limit RFI data capture for any single event to no more than 90 seconds. Implementation of a circular buffer within the high-speed RAM (8 seconds for each L-band tuner path) allows continuous capture of RF data while waiting for a trigger indicating that RFI is present. To reduce false alarms, RFI must be present for at least 4 seconds before data is captured. However, no RFI data is lost, because the circular buffer is longer than 4 seconds. RFI data captures typically contain 3 seconds of data at the beginning, with no RFI, and therefore make it possible to observe the onset of the RFI.
The new equipment has captured hundreds of RFI events, spanning a wide range in bandwidth (7 MHz to an estimated 150 MHz), chirp rate (9 kHz to 170 kHz), and power levels (–10 dBm to as much as +20 dBm). Accurately estimating EIRP of moving emitters is a challenge and requires detailed knowledge of the characteristics of all components used in generating the estimate. Furthermore, distance to the RFI source can only be inferred, since its movement precludes exact measurement, and consequently there will always be some uncertainty in any reported EIRP. However, even with these qualifications, there is evidence from Snapshot System data that some of the RFI sources are transmitting at power levels as much as +20 dBm.
Modeling Antenna Responses
The use and orientation of the two antennas was chosen to determine the direction that PPDs are traveling and thereby reduce some of the uncertainty with respect to their exact location. Figure 13 shows the direction (58 degrees) in which the AEL antenna is pointed.
FIGURE 13. Pointing direction of the AEL antenna.
The combination of its beam width (70 degrees) and axial ratio (0.2 dB) results in a nearly uniform gain across all lanes north of the GBAS shelter. Although FSL still depends on the exact location of the PPD, this approach does reduce many of the uncertainties associated with estimating EIRP. Since the PCTEL antenna has an omnidirectional pattern it will have a symmetrical response.
To determine the time that maximum PPD power would be observed by each antenna, a model was used that assumed the PPD was transmitting at constant power, with fixed polarization, travelling at a constant velocity, and there were no obstacles between the transmitter and each antenna. FSL was calculated for each second of travel and used to determine the magnitude of RFI power that would be received. This value was then used to calculate a nominal Interference to Signal (I/S) relative to the GPS signal. The distance between each antenna and each of the travel lanes on the NJT were also used. The intent of this model was to understand how I/S would vary with time for each of the NJT travel lanes. Figure 14 shows the predicted I/S for the PCTEL antenna and Figure 15 for the AEL antenna. In each of these plots red, yellow and orange represent 3 of the 7 south bound travel lanes and green, blue and purple represent 3 of the 7 north bound travel lanes. A time of 0 was used for the time when the PPD is nearest physically to the GBAS shelter. A nominal velocity of 30 meters/second (67 MPH) was used for the PPD and I/S was computed for 30 seconds before and after its closest approach (± 900 meters north and south of the GBAS shelter). If the PPD travels slower than 30 m/s then the following curves would be wider for the same times. Similarly, if the PPD travels faster, these same curves would be narrower.
FIGURE 14. Predicted I/S for PCTEL antenna (click to enlarge.)FIGURE 15. Predicted I/S for AEL AST-1507AA (click to enlarge.)
Modeling of the AEL antenna took into account its pattern and orientation. It has less gain towards the south, and consequently observed power from a PPD located south of the GBAS shelter is much less. A southbound PPD will initially be within the main beam of the AEL antenna; therefore the expected interference to signal ratio (I/S) will gradually increase until it passes to the south of the GBAS shelter. Similarly, a northbound PPD will not exhibit significant I/S until north of the GBAS shelter. Figure 15 indicates that the maximum I/S occurs within 2 seconds of the point where the PPD is closest to the GBAS shelter. Typical GPS receivers can tolerate an I/S of 30 dB for CW type signals.
Processed RFI data does display some of these characteristics but with some important differences. PPD power was measured once every millisecond using Snapshot System data and total power within the bandwidth of that PPD was calculated. Total power from both the PCTEL (green) and AEL (pink) antennas were then plotted together with one example for a southbound PPD in Figure 16 and a northbound PPD in Figure 17.
FIGURE 16. RFI Power of southbound PPD (click to enlarge.)FIGURE 17. RFI Power of northbound PPD (click to enlarge.)
Although the envelope of the measured average power tends to have the shape that modeling predicts, there are significant variations over short periods of time. Figure 18 expands a portion of one example and indicates that RFI power varied by more than 17 dB in 0.2 seconds. Examination of spectral data for time intervals of less than one second frequently contains significant changes in observable power. Swept CW from PPDs should exhibit relatively flat RF spectral power, but typical observed spectra include sloping across the band and notches. Possible explanations for these observations include: blockage and diffraction from other vehicles near the one containing the PPD, multipath from other vehicles on the NJT, and the effect of transmitting from within a vehicle. Although some of the snapshot captures exhibit smooth power variation similar to predicted, the vast majority of the hundreds of snapshots exhibit significant variations in power.
FIGURE 18. RFI Power of southbound PPD (expanded).
Examples of Observed PPDs
The variety of PPDs observed by the updated EWR monitoring equipment has been surprising. Within its first month of operation, more than 40 PPDs were observed with no less than 19 from unique and different PPD transmitters. Classification of PPD transmitters is based on the combination of RF spectra and the spectrum of the FM demodulated data. Although the observed PPD transmitters use a linearly swept FM sawtooth, most contain deviations from a pure linear sweep. Figure 19 shows examples of FM demodulated time series. Rather than attempting to uniquely describe the attributes of each type of deviation, it is simpler to compute the spectrum of the FM demodulated data. The fundamental frequencies of chirp rates that have been observed have spanned 9 kHz to 170 kHz. Figure 20 shows a histogram of chirp rates observed near EWR and indicates that the most frequent rates have been 9, 26, 29, 72, 85, 118, 123, 159 and 170 kHz.
FIGURE 20. Histogram of EWR PPD chirp rates.
Examples of the 19 unique PPDs (detected within one month) are shown in Figure 22 through Figure 40, with the RF spectrum shown on the left, and the spectrum of the FM demodulated shown on the right. In each of these plots the scaling for the RF spectra is identical, spanning 40 MHz centered on 1575 MHz with a vertical scale using 10 dB per grid. All of the FM demodulated spectra use a horizontal axis that spans 0 to 200 kHz. For references purposes Figure 21 shows the RF spectra when no RFI is present.
Some of these PPDs were transmitting at power levels (observed by the PCTEL antenna) as much as 40 dB above the LNA noise floor. Most spectra were not centered symmetrically about L1 with some completely outside the mainlobe of the GPS C/A code. A few were transmitting outside the programmed 40 MHz bandwidth of the Snapshot System (1555 to 1595 MHz). For those PPDs transmitting outside this band, estimates were made of the upper or lower frequencies using the linear slope of the FM demodulated data, and then extrapolating that slope based on the chirp interval.
Some of the FM demodulated spectra contain a single spectral line that indicates the waveform modulating the RF has a very linear sweep. Most contain additional harmonic lines about the major component and a few appear to have bandwidth about their main spectral component. The current hypothesis is that many of these devices are poorly shielded and that the internal oscillator used to modulate the RF is affected by other nearby signals that are then appearing at the RF output. Some of the possible sources could be circuits that are within the device itself but there is some evidence that a few of these devices are susceptible to energy external to the PPD. A Snapshot System located near Houston International Airport (ZHU) has captured data from PPDs that contain strong components at 58.7 Hz in addition to its linearly swept 97 kHz waveform. Since this frequency is sufficiently different from utility AC power sources (60 ± 0.03 Hz), it has been hypothesized the vehicle carrying that PPD, also has a power inverter. Most power inverters are specified to provide a frequency output of 60 ± 3 Hz. Figure 32 shows a spectral notch that was present at that single frequency throughout the complete capture and suggests that that particular device may have had an impedance matching problem in its transmission path.
FIGURE 21. Spectra with No RFI Observed by PCTEL (click to enlarge).FIGURE 22. 1570 to 1583 MHz, Chirp 117.35 kHz.FIGURE 23. 1556 to 1583 MHz, Chirp 28.43 kHz.FIGURE 24. 1565 to 1578 MHz, Chirp 123.13 kHz.FIGURE 25. 1568 to 1583 MHz, Chirp 111.08 kHz.FIGURE 26. 1578 to 1589 MHz, Chirp 118.07 kHz.FIGURE 27. 1568 to 1584 MHz, Chirp 8.92 kHz.FIGURE 28. 1572 to 1584 MHz, Chirp 121.93 kHz.FIGURE 29. 1557 to 1622 MHz, Chirp 36.14 kHz.FIGURE 30. 1568 to 1582 MHz, Chirp 11.08 kHz.FIGURE 31. 1570 to 1585 MHz, Chirp 85.06 kHz.FIGURE 32. 1572 to 1582 MHz, Chirp 118.07 kHz.FIGURE 33. 1529 to 1577 MHz, Chirp 39.52 kHz.FIGURE 34. 1578 to 1594 MHz, Chirp 131.33 kHz.FIGURE 35. 1575 to 1582 MHz, Chirp 75.66 kHz.FIGURE 36. 1561 to 1586 MHz, Chirp 29.16 kHz.FIGURE 37. 1568 to 1592 MHz, Chirp 71.33 kHz.FIGURE 38. 1560 to 1595 MHz, Chirp 9.88 kHz.FIGURE 39. 1564 to 1582 MHz, Chirp 100.48 kHz.FIGURE 40. 1584 to 1599 MHz, Chirp 128.20 kHz.
A few snapshots have also provided evidence that some of the PPDs are erratic and probably not functioning as their manufacturer intended. Figure 41 contains a raster of 6 seconds of spectral data that shows a PPD whose output was meant to be between 1560 and 1580 MHz but for short periods of time was transmitting at frequencies above 1580.
FIGURE 41. Spectral Raster, PPD with Unstable Output.
Remarks on Additional PPDs
Since April 2011 the Snapshot System has captured many additional and different PPDs. No effort has been carried out to catalog all of the different types that have been observed but the following describes interesting and notable PPDs.
Figure 42 shows characteristics of a PPD that has had estimated EIRP approaching +20 dBm, to a point just outside the vehicle, and has also been associated with GPS receiver C/N0 degradation of more than -27 dB, strong enough to cause the WAAS receiver, located at the GBAS shelter, to lose lock on all GPS satellites for a short period of time.
FIGURE 42. 1568 to 1582 MHz, Chirp 118 kHz
Figure 43 shows a PPD that is one of the most frequently observed PPDs but that has not been associated with any significant degradation to the GPS receivers. Estimated EIRP for these PPDs has been on the order of no more than +10 dBm. One device with similar characteristics was procured and its measured power at the antenna output port was no more than +14 dBm. Marketing information on the internet for that PPD specified its output power as +25 dBm.
FIGURE 43. 1572 to 1589 MHz, Chirp 85 kHz.
Figure 44 shows a PPD that is transmitting at both L1 and L2. The EWR Snapshot System has been configured to only capture snapshot data at L1 due to the fact that LAAS only uses L1. However, the WAAS receiver used to monitor for RFI is a dual frequency receiver that on occasion has indicated simultaneous RFI at both L1 and L2. Even though the EWR Snapshot System has not captured data at L2, the simultaneous presence of both L1 and L2 RFI, provides strong circumstantial evidence that this RFI source was transmitting on both frequencies. A Snapshot System monitoring the WAAS Reference Station (WRS) at Leesburg Virginia has captured simultaneous L1 and L2 RFI events. Demodulation of that data indicated the two RF outputs had similar modulation but the demodulated data was not coherent. Therefore, that PPD was probably using individual, but similar waveform generators, for each RF output.
FIGURE 44. 1562 to 1583 MHz, Chirp 114 kHz.
Almost all PPDs have been observed individually. However, there have been at least three times in the last two years when two unique PPDs have been observed within 60 seconds of each other. Figure 45 plots normalized degradation in C/N0 while Figure 46 plots snapshot measured power for the same RFI event. Analysis of snapshot data for each of the times that had strong RFI power are shown in Figure 47 and Figure 48 and confirmed that there were in fact two unique PPDs observed approximately 40 seconds apart. Both were traveling south on the NJT and approximately 1200 meters apart.
FIGURE 45. Normalized C/N0 August 19, 2011FIGURE 46. Snapshot Power August 19, 2011.FIGURE 47. C/N0 -19.0 dB, Chirp Rate 78.97 kHz.FIGURE 48. C/No -28.0 dB, Chirp Rate 117.24 kHz.
Most of the observed RFI events last for no more than 50 seconds although a few that lasted much longer have been correlated with slow traffic on the NJT. Figure 49 is from June of 2010, before the updated monitoring equipment was in place, and displays normalized degradation of C/N0. The time duration for which this RFI was observed was more than 3 minutes and was during a time when traffic was ‘slow’ on the NJT.
FIGURE 49. June 9, 2010, PPD, Estimated Velocity 10 m/s.
Very wide-bandwidth PPDs have recently been observed more often. The frequency span these devices are transmitting has had to be estimated due to the fact that the Snapshot monitor has 40 MHz of bandwidth, and these PPDs are transmitting beyond this bandwidth. Figure 50 through Figure 52 show examples of these types of PPDs. The left plot in these figures is the RF spectra and the right plot is the FM demodulated waveform. The latter each contain a linear component that is present for only a portion of the chirp interval. Under the assumption that the modulating waveform would be linear for the repetition interval, the slope of the visible linear component was extrapolated to the total chirp time interval. It is not possible to estimate the upper and lower frequency points for the last two examples, since neither of those had a frequency that began or ended within the observable 40 MHz bandwidth of the monitor.
Although the Snapshot System L-band tuners can be programmed for greater bandwidth, the limiting bandwidth is the bandpass filters contained within the LNA modules, which have bandwidths of 40 MHz.
Data captured by a Snapshot System operating near ZHU contains evidence that external energy may have coupled into that PPD and affected the modulation waveform. Figure 53 shows a plot of the RF spectra and an expanded portion of the FM demodulated spectra indicating the presence of a 58.7 Hz component. A raster of the demodulated FM, shown in Figure 54, highlights the 58.7 Hertz component.
FIGURE 53A. ZHU chirp 118 kHz with 58.7 Hz.FIGURE 53B. ZHU chirp 118 kHz with 58.7 Hz.FIGURE 54. ZHU raster of FM showing 58.7 Hz (Click to enlarge).
Careful analysis of normalized C/N0 has also provided clues as to the possible travel paths that a PPD might be using. RFI was suspected at the WRS located at Leesburg Virginia (ZDC). A Snapshot System was installed to detect and characterize possible RFI. Analysis of snapshot data did confirm that a few PPDs were traveling past ZDC. One of the PPDs was more disruptive than the others but fortunately was also following a very predictable schedule. It was regularly detected twice a day, first within 10 minutes of 4:30 AM local and next within 30 minutes of 2:30 PM. Normalized C/N0 contained similar patterns for each time of day and are shown in Figure 55 and Figure 56. Examination of the local roadways, shown in Figure 57, suggested the possible roads and direction in which this PPD was traveling. The WAAS antennas on the roof of ZDC have clear line of sight to state highway 7 for vehicles that are east of ZDC. Normalized C/N0 for morning events tended to have a relatively abrupt onset followed by a gradual return to normal while the afternoon events exhibited a gradual increase in degraded C/N0 followed by a quick return to normal. This observation lead to hypothesizing that the PPD was traveling east in the morning and west in the afternoon.
FIGURE 55. ZDC Typical Morning Degradation.FIGURE 56. ZDC Typical Afternoon Degradation.FIGURE 57. Roads near ZDC (click to enlarge.)
FAA Spectrum personnel were informed of this analysis and confirmed that this hypothesis was correct. Using this information they were able to detect the vehicle that was responsible and remove this particular PPD from service.
EWR RFI Event Statistics
A large number of RFI events have been detected at EWR since the updated Snapshot System was installed on March 3, 2011. These RFI events have been ranked according to the magnitude of degradation in normalized C/N0, as reported by the GBAS shelter WAAS receiver. The following plots show the total number of RFI events per day (red dots) and for every seven consecutive days (blue line). On average, PPD-induced receiver degradation of at least 10 dB has been observed two times a day. Although a small number of narrowband RFI events produced receiver degradation of as much as 10 dB, the vast majority of RFI events causing 10 dB or more of receiver degradation are due to PPDs.
Figure 58 indicates that since March 2011, more PPD RFI events are being observed. However, Figure 60 indicates that the higher-power PPDs are not being observed as often. One possible explanation is that the previously observed PPDs have stopped working, and the individuals using them have either not acquired replacements or they have acquired different ones with less-damaging RFI.
FIGURE 58. History of RFI > –10 dB (click to enlarge).FIGURE 59. History of RFI > –15 dB (click to enlarge).FIGURE 60. History of RFI > –20 dB.
Many recent PPDs have been transmitting with estimated frequency spans of 65 MHz to 140 MHz. Although the estimated EIRP of many of these very wide bandwidth PPDs has been as much as +10 dBm, their effect on GPS receiver processing has not been as damaging due to the fact that the RFI is within the GPS receiver processing bandwidth for only a portion of the time.
Spectra of Swept FM with Multipath
One of the most commonly observed characteristics in PPD spectral data has been uniformly spaced nulls as shown in Figure 61 and Figure 62. Figure 63 displays a spectral raster that shows how the nulls shift in frequency over time. Initially, there was uncertainty as to the mechanism responsible for these observations. Under the hypothesis that multipath might be responsible, a single ray multipath model was used to predict the spectral characteristics of a PPD that includes a multipath component. This analysis was pursued in the hope that it might provide additional information as to the exact location of PPDs.
The swept CW signals used by PPDs provide a useful source for characterizing multipath between the PPD and monitoring antennas. Equation (1) models observed CW that is the sum of the direct path and a single reflection in which reflected component has a path length difference of d meters.
(1)
Assuming the reflection is from a metal surface, it should experience a phase reversal. Therefore, destructive cancellation between the direct and multipath component will be present for those frequencies that have a path length difference that is an integer multiple of the wavelength. Equation (2) represents this condition.
(2)
Simplification results in the following expression.
(3)
As an example, if spectral nulls are observed at intervals of 10 MHz, then the path length difference is approximately 30 meters. Spectral nulls have been observed at frequency intervals ranging from 2 MHz to as much as 30 MHz. These null spacing’s translate to path length differences of between 150 meters to 10 meters. Multipath with a path length difference of less than 8 meters will exhibit a single null in the 40 MHz bandwidth of the Snapshot System and therefore cannot be estimated accurately using this technique. A path length difference of 8 meters is also what might be expected for two vehicles traveling side by side on interstate highways since interstate highway specifications require lanes to be approximately 4 meters wide.
Once a possible mechanism for the spectral nulls was hypothesized, additional analysis was performed on specific RFI events in which uniformly spaced spectral had been observed. Snapshot and GPS receiver data indicates the direction of travel for a PPD. With direction of travel known, it is possible to approximate the distance that the PPD is from the monitoring equipment. However, for those RFI events that were examined, the calculated path length difference was similar to or greater than the distance between the PPD and monitoring equipment. The most likely location of surfaces that would reflect the PPD transmission was other vehicles on the NJT. Had the surfaces responsible for the reflections been stationary objects nearby, then it might have been possible to hypothesize the most likely location of the PPD by combining receiver proximity and path length differences.
The magnitude of the reflection coefficient can be estimated by comparing the relative power of the spectral maximum and minimum. However the magnitude of the reflection coefficient can only be bounded since it depends on both the reflection coefficient and the relative path length difference. Since the reflected path travels farther, its magnitude will inherently be reduced, in addition to the loss from the reflection, and therefore the observed relative difference will be smaller than shown by equation (4).
(4)
For the examples shown in Figure 61 and Figure 62 the spectral max/min was on the order of 10 dB. By using 10 dB for SpectraMaxMin in equation (4), a reflection coefficient of at least 0.5 is calculated. Reflection coefficients of trucks with shipping containers will probably be much greater than 0.5 and could easily be as high as 0.9.
Direction-Finding Methods
After examining more than a thousand examples of PPDs and their effect on GPS receivers, I have concluded that any type of ground-based direction finding system intended to detect and locate low power moving PPDs over a large area using time-difference-of-arrival (TDOA) or beam forming (angle-of-arrival, AOA) techniques will face significant challenges.
Accuracy of TDOA-based location systems can be decomposed into two components: measurement accuracy, and the geometry of the equipment used to make these measurements. In 1982, Paul Chestnut calculated the relationship between accuracy and these two components, showing that geometry is a multiplicative factor. Direction-finding conceptual design typically strives to position the measurement equipment such that it surrounds the area to be monitored, if possible. For those situations where it is not possible to encircle the area, the measurement equipment will typically have a long baseline between its sensors and with a perpendicular orientation with respect to the monitored area. This strategy reduces errors due to geometry.
Measurement error depends on the observable power of the signal to be located. This component will most likely limit the ability to accurately locate low-power moving PPDs. Measurement data from GPS receivers demonstrate the ability to reliably detect the presence of these PPDs, but only when they have been within hundreds of meters. Most PPDs have been observed for 30 to at most 60 seconds. For PPDs traveling along the NJT at a velocity of 30 m/s, this time span implies that they were not detected until they were within 900 meters. Reliable detection was not demonstrated unless they were within 500 meters. This is a direct consequence of the fact that all GPS antenna are designed for hemispherical coverage for satellites above the horizon. The PPDs are at the horizon or lower relative to most GPS antenna patterns. If GPS antennas were used as part of a TDOA-based system, they would need to be positioned no further apart than approximately 600 meters. Using GPS antennas to detect and locate PPDs is inherently limited to proximity detection.
The ability to locate low-power PPDs within a larger area requires a system to be able to detect a PPD by all of its sensors simultaneously from distances much greater than 600 meters. In principal, higher-gain antennas orienting their main beam along the NJT would increase the distance over which PPDs could be detected. Even when high-gain directional antennas have been positioned along the NJT, the observed power has not followed predictions based strictly on FSL. One reason for this is that clear line-of-sight could not be achieved between the high gain antenna and the PPD. Vehicular effects might also be responsible for these observations. What is known is that the power observed by ground-based antennas has shown significant fluctuation, much greater than could be explained by FSL propagation. Ground-based direction finding systems for low-power moving PPDs must be able to simultaneously detect RFI by multiple sensors, in an environment that may at times shield the PPD from its sensors, and that also has fluctuating observable power.
The ability to observe, detect, and locate low-power moving PPDs over a large area would require a system to have its monitoring antenna located high above the NJT, and oriented to look down on the NJT and the surrounding area. Although such a system must still contend with shielding from the vehicle itself, it would be the only approach that could potentially observe these PPDs over a large area, simultaneously by all of its measurement sensors. Implementing such a concept may be expensive.
A less expensive approach might rely on proximity detection, with many sensors on the ground, each monitoring their own small area, and only report PPDs that travel close to each of them. One such approach, referred to as crowd sourcing, uses cell phones to aid in detecting and locating PPDs. Crowd sourcing is a form of proximity detection.
Summary
The first evidence of low-power moving PPDs along the NJT used two GPS receivers separated by considerable distance and then correlated their responses. This approach is only useful for detection of PPDs traveling in close proximity to the GPS receivers. Analysis of GPS receiver normalized C/N0 also provided a basis for determining if RFI might be from a moving emitter. The shape of normalized C/N0 versus time not only provides clues that the RFI source is in motion, but may even be correlated with their possible travel paths, when blockage exists between the GPS antenna and local roadways.
Autonomous operation is a necessity for detecting low-power moving PPDs, since they may be observable only a few times a day and for less than 60 seconds.
Capturing real-time samples of these intermittent RFI events determined the existence of many different types of PPDs. Almost all use some form of swept FM modulation. Analysis of their spectra and modulation indicates that many devices are probably not operating as their manufacturer intended. Modulation waveforms of PPDs have included triangle, highly linear sawtooth, sawtooth with synchronous perturbations on top of the fundamental sawtooth, and sawtooth with analog modulation. The leading hypothesis for this observation is that the devices are not shielded very well and that the internal modulator is susceptible to coupling from either other circuits within the PPD itself or from external electronic devices operating in the vicinity of the PPD.
Acknowledgments
The author thanks the FAA for support in this investigation, Rich Holley of ICE-Online for help in utilizing capabilities of the ICEPOD6-M5, and Julian Babel of the FAA Technical Center for regularly swapping external hard drives attached to the Snapshot System.
Joe Grabowski is a systems engineer at Zeta Associates where he works on a variety of GPS projects in support of the FAA, as well as communications systems and digital signal processing applications. He received an M.S.EE from Purdue University. Since 2010 he has been involved in the investigation of personal privacy device impacts on FAA SBAS and GBAS sites.
U.S. federal agencies, aircraft and avionics manufacturers, airlines, and research centers are brainstorming ways to prevent a repeat of the tragic events of September 11, in which highjacked aircraft were used as missiles. Under these new circumstances, options previously dismissed out of hand suddenly are attracting renewed attention.
One recurring proposal is to automate the landing of hijacked aircraft. In this scenario, a “dead-man switch” would allow the pilot to turn over navigational control to an on-board GPS-based autolanding system. The system would broadcast a mayday to air traffic control (ATC), search an on-board database for the nearest suitable airport, alert that airport, receive landing authorization, and land the aircraft there. During these operations, no one on board would be able to regain control of the aircraft. The pilot would be like an employee who, when confronted by a robber, does not have the combination to the company’s safe. No amount of violence on board would allow hijackers to use an aircraft as a missile against a target.
Technologically feasible. The strong consensus of airline, industry, and academic experts interviewed for this article is that the above scenario is technologically feasible. In fact, the autolanding technique has been amply demonstrated and at least one major avionics manufacturer is actively working on producing an emergency landing system.
The Federal Aviation Administration (FAA) is working on two GPS-based systems that could enable this sort of antihijacking capability: the Wide Area Augmentation System (WAAS) that will enable aircraft to reach the so-called Category 1 decision point in an approach to an airport, and the Local Area Augmentation System (LAAS) that would enable aircraft to reach the ground in zero visibility, known as a Category 3B landing. The agency plans for many airports to be equipped with LAAS transmitters eventually and will require WAAS/LAAS systems on commercial airliners.
Although both systems still await final certification, testing, and installation at U.S. airports, commercial airliners and military aircraft have already demonstrated fully automatic instrument approach and landing under Category 3B conditions.
Features
Although technologically feasible, operational considerations pose obstacles for implementing an automated emergency landing system. The following scenarios address some of these issues as well as technical features of such a system:
A “multiple key” arrangement could restore manual control with codes from the pilot, the co-pilot, and the ground-based ATC operators. Ground control would con- tribute its code only when absolute sure that the aircraft could not be used to attack a population center.
To protect it from being disabled, the system would require a hardened compartment not accessible from the cabin and an autonomous power source not controlled from the cockpit circuit breaker panel.
Prior to landing, the onboard system would notify ATC, which, in turn, would alert and re-route other aircraft as needed.
If the highjackers jammed the GPS signal, the system would put the plane in a holding pattern until it reacquired a clear signal. By refusing to turn off the jammer, terrorists could force the aircraft to run out of fuel and crash – but could not guide it to a target.
According to an industry source, the system should first put the aircraft in a holding pattern in any case, to give a chase plane time to reach it and visually monitor it. In the very unlikely case that the highjackers were able to regain control of the aircraft and aim it toward a target, the chase plane could challenge the aircraft, order it to land, and shoot it down if it did not comply.
The airport database would need to include data on possible flight path obstructions – terrain or tall buildings – so that the system could select a clear approach path. Avionics systems coming onto the market that are designed to prevent controlled flight into terrain essentially have this capability now.
The autolanding system would require permission from the ground to land on a particular runway. If permission were denied for any reason, the system would search its database for the next-best runway.
Cockpit philosophy. An airline pilot who is now an aide for the operations chief of a major airline reacted very negatively to the idea of an emergency autolanding system that could not be disengaged by the pilot. Any system that restricts the crew’s options, he said, clashes with a key tenet of “cockpit philosophy”: to keep the pilot in charge and never relinquish control of an aircraft completely to automation.
An emergency autoland system also conflicts with a basic principle of aeronautical engineering – namely, that an aircraft should have multiple, redundant ways to control it.
However, in extreme emergencies, the alternative may warrant overriding such concerns, according to Bradford Parkinson, a professor emeritus at Stanford University’s School of Engineering who first proposed fully automated cargo planes years ago. He points out that, although an antihijacking system used routinely would have to be extremely reliable, when the alternative is a 100 percent probability of death for all aboard, “Boy, that sure changes the equation in a flash.”
Further reading: “Soft Landings: Navy Proves Hands-Off Touchdown,” by Matteo Luccio and Glenn Colby, GPS World, August 2001.