The Vertical Challenge of Low-Altitude Economy: Why We Need a Unified Height System?

This paper proposes adopting Height Above Ellipsoid (HAE) as a unified, GNSS-native vertical reference to resolve the safety and interoperability challenges caused by fragmented altitude systems in the low-altitude economy, demonstrating through real-world implementation and risk assessment that this transition enhances dynamic airspace capacity while maintaining safety standards.

The Gist

Here is an explanation of the paper, translated into simple language with creative analogies.

The Problem: Everyone is Speaking a Different "Height" Language

Imagine you are trying to organize a massive, chaotic party in a crowded city park. You have drones (like flying delivery robots), helicopters, and birds all trying to fly around without crashing.

Right now, the problem is that everyone is using a different ruler to measure how high they are flying:

• The Pilots use a Barometer (like a weather gauge). They measure height based on air pressure. But air pressure changes with the weather, like a rubber band stretching and shrinking. If the weather changes, their "height" changes even if they haven't moved!
• The Map Makers use Sea Level. They measure how high you are above the ocean. But the ocean isn't flat everywhere, and different countries measure "sea level" differently. It's like trying to measure a room using a ruler that shrinks in London but expands in Tokyo.
• The Obstacle Avoidance Systems use Ground Level. They measure how high you are above the grass or the roof of a building. But the ground changes! Trees grow, buildings get built, and rivers shift. It's like trying to measure your height relative to a floor that is constantly moving up and down.

The Result: It's a mess. A drone might think it's flying safely at 100 feet, while a helicopter thinks it's at 100 feet, but because they are using different rulers, they are actually at different heights. This creates a high risk of collisions and makes it impossible to automate the sky for the booming "Low-Altitude Economy" (delivery drones, air taxis, etc.).

The Solution: The "Earth's Skeleton" (HAE)

The authors propose a new, universal ruler called Height Above Ellipsoid (HAE).

The Analogy: Imagine the Earth isn't a bumpy potato with mountains and valleys, but a perfectly smooth, mathematical egg shape (an ellipsoid).

• HAE measures your height strictly from the surface of this perfect mathematical egg.
• It doesn't care about the ocean, the weather, or whether there is a mountain or a building under you.
• It is the "GPS height." When your phone tells you your coordinates, it is already using this system.

Why is this better?

1. It's Digital Native: It's built for computers. Just like your phone knows exactly where you are on a map, a drone knows exactly how high it is above the "math egg."
2. It's Stable: The "math egg" doesn't change. The weather doesn't change it, and the ocean tides don't change it.
3. It's Global: Everyone, from New York to Shanghai, uses the exact same egg. No more translating between different rulers.

The Bridge: How to Talk to the Old Guard

You might ask, "But what about the old pilots and regulations that use the old rulers?"

The authors propose a Translation Bridge.

• Think of HAE as the "Universal Translator."
• When a drone flies, it knows its HAE.
• If a human pilot needs to know their height above the ground (AGL), the computer instantly translates the HAE number into an AGL number using a digital map of the terrain.
• If a regulator needs to know the height above sea level (MSL), the computer translates it again.
• The Magic: The drone flies using the stable HAE, but everyone else gets the numbers they are used to, instantly and accurately.

The Proof: Why This Matters (The Shenzhen Experiment)

The team tested this idea in Shenzhen, a city packed with skyscrapers and drones.

1. The "Zoning" Test (Static Safety):
They divided the city into zones based on the "math egg." Instead of saying "Don't fly above the trees," they said "Don't fly above 60 meters on the math egg."

• Result: It was much easier to manage. Users didn't need secret government maps of the terrain; they just needed their GPS. It made the rules clear and fair for everyone.

2. The "Traffic Jam" Test (Dynamic Capacity):
This is the most exciting part.

• The Old Way: Because the old rulers (barometers) are shaky and inaccurate, safety rules force drones to stay very far apart vertically (like 32 meters) to avoid crashing. It's like driving on a highway where you must leave 3 car lengths between every car because your speedometer is broken.
• The New Way: Because HAE is precise (accurate to within a few centimeters), drones can fly much closer together safely (only 6 meters apart).
• The Result: By switching to HAE, the "highway" in the sky can hold 8 times more traffic.
  • Old System: Can handle about 294 flights per hour.
  • New System: Can handle over 2,300 flights per hour.

The Bottom Line

The paper argues that to unlock the future of flying cars and delivery drones, we need to stop using "weather-based" or "ground-based" rulers and start using the "GPS-based" ruler (HAE).

It's like upgrading from a paper map that gets wet and rips to a GPS app that updates in real-time. This change isn't just a technical tweak; it's the key to turning the sky from a dangerous, crowded mess into a safe, high-speed digital highway worth trillions of dollars.

Technical Summary

Here is a detailed technical summary of the paper "The Vertical Challenge of Low-Altitude Economy: Why We Need a Unified Height System?"

1. Problem Statement

The rapid expansion of the Low-Altitude Economy (LAE), driven by eVTOLs and UAVs, is hindered by the fragmentation of vertical reference systems. Current aviation relies on disparate height definitions that create ambiguity and safety risks for autonomous systems:

• MSL (Mean Sea Level): Used in cartography and manned aviation, but varies regionally due to geoid deviations and is not globally consistent.
• AGL (Above Ground Level): Critical for obstacle avoidance but relies on Digital Terrain Models (DTM) that are often outdated, restricted by security concerns, or inconsistent (e.g., DTM vs. DSM).
• Barometric Pressure (Q-codes): Used for flight levels but suffers from atmospheric variability (weather, temperature), leading to significant drift and measurement errors.

This fragmentation prevents interoperability between stakeholders (regulators, operators, service providers), complicates airspace integration, and forces excessive safety buffers, limiting the scalability of urban air mobility.

2. Methodology

The authors propose a shift to Height Above Ellipsoid (HAE) as the standardized vertical reference for lower airspace. Their methodology involves three core components:

A. Theoretical Framework & Criteria Analysis

The paper evaluates height systems against three criteria essential for the LAE:

1. Digital Compatibility: The system must be computationally tractable for automated management.
2. Reference Stability: The datum must be temporally and spatially consistent (immune to weather or terrain changes).
3. Operational Accuracy & Accessibility: The system must be precise and accessible via cost-effective, ubiquitous sensors.

HAE is identified as the optimal choice because it is a purely geometric system tied to a global ellipsoid (e.g., WGS84), directly measurable by GNSS (GPS, BeiDou, etc.) with centimeter-level precision, and independent of atmospheric or terrain variables.

B. Bidirectional Transformation Framework

To ensure backward compatibility with legacy systems, the authors propose a framework for converting between HAE and existing systems (MSL, AGL, Barometric):

• Forward Transformation: Converting legacy data to HAE using geoid models (e.g., EGM2008) for MSL and DTM/DSM for AGL.
• Backward Transformation: Converting HAE back to legacy formats for stakeholders requiring specific datums.
• Calibration: Using empirical calibration parameters or crowd-sourced data to correct inherent errors in legacy systems (e.g., barometric drift).

C. Case Studies & Empirical Validation

The framework was validated through two distinct case studies in Shenzhen:

1. Static Safety (Partitioned Airspace Management):
   • Approach: Used MERIT DTM data to convert elevation to HAE. Applied K-means clustering to group terrain into "Simple" (flat) and "Complex" (rugged) regions.
   • Outcome: Defined standardized HAE thresholds for Class W and G airspace, eliminating the need for users to access sensitive DTM data while maintaining safety.
2. Dynamic Capacity (Safety & Throughput Analysis):
   • Data Source: Real-world flight logs from the PX4 ecosystem (multicopters with RTK-GNSS).
   • Error Modeling: Compared Barometric altitude vs. RTK-GNSS (HAE) ground truth.
     • Barometric Error ($\sigma$): ~3.98 m.
     • HAE Error ($\sigma$): ~0.53 m.
   • Risk Modeling: Applied the Reich Collision Risk Model to calculate Vertical Separation Minimum (VSM) required to meet a Target Level of Safety (TLS) of $10^{-7}$.
   • Capacity Modeling: Applied the Erlang-B loss model to calculate maximum traffic throughput before congestion.

3. Key Contributions

• Identification of the "Vertical Gap": Highlighted that while horizontal coordinates (Lat/Long) are standardized, vertical references remain a critical bottleneck for LAE scalability.
• Proposal of HAE Standardization: Argued that HAE is the only "digital-native" vertical reference capable of supporting high-density, autonomous operations.
• Pragmatic Transition Framework: Developed a bidirectional transformation model that bridges the gap between legacy aviation infrastructure and the new digital standard, ensuring backward compatibility.
• Quantitative Proof of Concept: Provided empirical evidence using real flight data to demonstrate the economic and safety benefits of HAE over legacy systems.

4. Results

The empirical analysis yielded significant quantitative improvements:

• Reduced Vertical Separation Minimum (VSM):
  • Legacy Barometric System: Requires ~32 meters separation to maintain safety.
  • HAE System: Requires only ~6 meters separation.
• Increased Static Airspace Capacity:
  • In a 1,000-meter airspace ceiling, the legacy system supports 31 usable flight levels.
  • The HAE system supports 166 usable flight levels (5.3x increase).
• Enhanced Dynamic Throughput:
  • Using the Erlang-B model, the HAE system supports 2,354 flights/hour before reaching a 5% congestion threshold.
  • The legacy system saturates at 294 flights/hour.
  • Result: An 8-fold increase in dynamic traffic capacity.

5. Significance

This paper argues that standardizing on HAE is not merely a technical refinement but an economic necessity for the Low-Altitude Economy.

• Safety: Eliminates ambiguity in height referencing, reducing collision risks caused by datum mismatches.
• Efficiency: Drastically reduces the "safety buffer" required between aircraft, unlocking massive unused airspace capacity.
• Scalability: Transforms lower airspace from a scarce, uncertain resource into a scalable, digital infrastructure capable of supporting the projected trillion-dollar LAE market.
• Implementation: Offers a clear roadmap for regulators and industry stakeholders to transition from analog/barometric height keeping to a GNSS-native digital standard without discarding existing infrastructure.

The authors conclude that while challenges in stakeholder coordination and urban canyon signal multipath remain, the transition to HAE is the foundational step required to realize safe and efficient Urban Air Mobility.