[ADS-L](https://skyblip.eu/ads-l.md)

# A display should receive the fields ADS-L carries.

We propose one NMEA 0183 sentence family for the link from ADS-L equipment to a pilot’s navigation display. It carries the Traffic and Status fields without translating them into FLARM’s fields. It also replaces the position, alarm, barometer and battery sentences the display needs today.

The full proposal is [`docs/ADSL_NMEA_PROPOSAL.md`](https://github.com/fcatuhe/skyblip/blob/main/docs/ADSL_NMEA_PROPOSAL.md). It defines the fields, units, rates and widths, with their source clauses. The names below use the proposed NMEA code `DSL`. The family is not implemented yet.

## The stack today

### An ADS-L device speaks as a FLARM unit does.

Today’s electronic flight bags, or EFBs, read traffic through FLARM’s data port format. It combines NMEA position sentences, FLARM’s traffic and alarm sentences, and Garmin’s pressure-altitude sentence. skyBlip adds LK8000’s sensor sentence because it is the only one XCSoar and LK8000 read a battery level from.

| Sentence | Carries |
| --- | --- |
| `$GPRMC` | Own position, ground speed, track, date and time |
| `$GPGGA` | Own position, GNSS altitude and fix |
| `$PFLAU` | Targets heard, fix, transmitting and the one worst threat |
| `$PFLAA` | One target, relative to the receiving aircraft |
| `$PGRMZ` | Own pressure altitude on 1013.25 hPa, in feet, only with a barometer |
| `$LK8EX1` | Pressure, pressure altitude, vertical speed, temperature and battery |

skyBlip sends these sentence types on a once-per-second output pass. Its traffic table holds 48 targets. Each must reach the display within 5 s, so a pass sends at most 10 `$PFLAA` sentences and the next pass resumes where it stopped.

`$LK8EX1` is outside that format and breaks NMEA’s proprietary naming rule. Displays still read it by name. XCSoar reads all six sentence types through its generic parser, whatever driver the pilot selects. It does not read the standard `$--XDR` sensor sentence.

## What is lost

### Most ADS-L fields have no place in that stack.

| ADS-L carries | The stack gives it |
| --- | --- |
| Absolute position and ellipsoid altitude, G.1.5 and G.1.7 | Metres north, east and up from the receiving aircraft |
| Time of the target’s fix, G.1.1 | No field |
| 64 Address Mapping Table entries, F.2.2 | Three ID types. OGN-Tracker at entry 7 and skyBlip at entry 58 both read as FLARM |
| 18 aircraft categories, G.1.3 | 16 FLARM types, with several ADS-L categories merged |
| Flight state and emergency status, G.1.2 and G.1.4 | No field |
| Six integrity, assurance and accuracy indicators, G.1.11 to G.1.16 | No field |
| Status payload, G.2 | No field |
| Relayed or uplinked traffic, F.2 and G.3 | Ordinary traffic |
| A callsign, expected in Issue 3 | A share of the `$PFLAA` ID field, cut first when space runs out |

Issue 2 has no callsign field. EASA told us orally on 2 October 2026 that Issue 3 will carry one. There is no written source for that statement. The [callsign page](https://skyblip.eu/ads-l/callsign.md) records the question and skyBlip’s interim transmission.

## The proposed family

### Seven data sentences replace the stack. Two negotiate the version.

A device keeps sending the current stack until the display writes `$PDSLR` on its connection. The device answers `$PDSLV`, then sends this family instead on that connection. The display asks for the highest version it reads. The device answers with the lower of their supported versions. A display that never asks keeps its current output.

| Sentence | Carries | Sent | Widest |
| --- | --- | --- | --- |
| `$PDSLR` | Request: highest family version the display reads | Once after connecting, display to device | 14 |
| `$PDSLV` | Answer: family version sent, manufacturer, model, firmware | In answer to `$PDSLR` | 65 |
| `$PDSLA` | A target’s Traffic payload | Each reception, at most once a second per target | 81 |
| `$PDSLO` | Own-ship’s Traffic payload, as transmitted | 1 Hz while the device has a fix | 81 |
| `$PDSLI` | An address’s category, quality indicators and callsign | First reception, on change, every 10 s. Own-ship every 10 s | 52 |
| `$PDSLC` | An address’s Status payload | Each reception. Own-ship every 20 s | 44 |
| `$PDSLW` | The device’s alarm on one target | On change, then 1 Hz while the level is above 0. A level 0 sentence ends it | 23 |
| `$PDSLB` | Own barometer and vertical speed | 1 Hz, only with a barometer | 36 |
| `$PDSLS` | The device, UTC and its fix | 1 Hz | 56 |

Widths count characters from `$` through CR LF at the widest values each field’s range allows.

The Traffic and Status fields keep ADS-L’s table values. Measurements use metres, metres per second and signed decimal degrees, with enough precision to recover the encoded values. Positions are absolute. Each target retains the time of its fix. The device sends what it heard and does not extrapolate it.

One traffic sentence carries every source, identified by a letter: ADS-L direct or relayed, FLARM-generation, PilotAware, FANET, OGN, ADS-L 4 Mobile, ADS-B, ADS-R or TIS-B. The display uses own-ship to calculate the geometry. The alarm sentence carries the device’s decision, not a second copy of that geometry.

| Example | Sentence |
| --- | --- |
| The display asks for version 1 | `$PDSLR,1*44` |
| The device answers | `$PDSLV,1,skyBlip,Go,1.0.0+874*33` |
| A skyBlip glider, climbing | `$PDSLA,L,58,000012,7.25,2,4,45.21468,5.84731,31.5,1842,G,2.4,273.5*5C` |
| Its identity | `$PDSLI,58,000012,4,0,0,0,6,2,2,F-CGXY*10` |
| An ADS-B aircraft, pressure altitude | `$PDSLA,A,5,3C6589,7.00,2,1,45.36294,5.32906,61.0,1524,P,-2.5,211.6*2F` |
| An alarm on the glider | `$PDSLW,2,58,000012*4C` |

The byte stream keeps the Nordic UART and HM-10 Bluetooth services displays already use. A display writes the request on Nordic UART’s `6E400002` characteristic or HM-10’s `FFE1`. It reassembles lines on CR LF, independently of notification boundaries.

A full table of 48 targets at the proposed maximum traffic-line width is about 3.9 KB per second, plus identity sentences. At a 182-byte notification payload, traffic alone is about 22 notifications per second. This has not been measured on a device.

## Why not GDL 90

### GDL 90 cannot preserve all the ADS-L fields.

Garmin’s binary interface carries FIS-B and ForeFlight reads it. Its six address types describe ADS-B or TIS-B, not ADS-L’s 64-entry Address Mapping Table. It combines ultralight, hang-glider and paraglider in one category, has none for a paramotor or eVTOL, and carries pressure altitude in 25 ft steps. It has no battery or vario field.

GDL 90 also uses Wi-Fi in nearly every display in the proposal’s support table that reads it. ForeFlight specifies UDP port 4000 and no Bluetooth transport. An ADS-L device used with a paraglider pilot’s phone has no Wi-Fi link to spare. The proposal keeps the existing Bluetooth stream. Its technical document compares the formats field by field.

## The NMEA code

### We ask the governing body to hold the code.

A proprietary NMEA sentence starts with `$P` and a three-letter manufacturer code. NMEA issues codes to companies only, for a $200 administrative fee and purchase of the standard. The listed price is $1,150 for an NMEA manufacturer member, $7,500 for government, industrial and testing, or $10,000 for consumer electronics.

`ADS` is occupied by the standard sentence “Automatic Device Status”. `DSL` was free in the public identifier list of 1 August 2013. We found no sentence under it in public GitHub code on 13 November 2026. It reads as ADS-L and names no manufacturer. The live register is behind an NMEA login and must be checked before an application.

## What we ask

### Adopt one family for every ADS-L device.

1. Adopt the family as a companion to ADS-L 4 SRD-860 or an annex of a later issue.
2. Hold its NMEA manufacturer code, `DSL` or another.
3. Map Issue 3’s callsign onto field 10 of `$PDSLI`, with its length and character set.

Meanwhile skyBlip Go and skyBlip Bravo send the FLARM stack and nothing else. There is no setting. They will answer `$PDSLR` once the family is agreed. The repository, firmware included, has been MIT-licensed since November 2026. The firmware can serve as a reference implementation for other manufacturers.

## References

- **skyBlip** · [The technical proposal](https://github.com/fcatuhe/skyblip/blob/main/docs/ADSL_NMEA_PROPOSAL.md). Fields, clauses, rates, widths, examples, the GDL 90 comparison and current display support.
- **EASA** · [ADS-L 4 SRD-860](https://www.easa.europa.eu/en/document-library/agency-decisions/ed-decision-2022024r), ED Decision 2022/024/R, Issue 2. F.2 addresses and relaying, G.1 Traffic, G.2 Status and G.3 Traffic Uplink.
- **XCSoar** · [FLARM sentence parser](https://github.com/XCSoar/XCSoar/blob/03d7f98233e4b57dc16391c00bf96ed55fc93459/src/Device/Driver/FLARM/StaticParser.cpp), at commit 03d7f982. How the most widely used open display reads `$PFLAU` and `$PFLAA`.
- **Garmin** · [GDL 90 Data Interface Specification](https://www.faa.gov/sites/faa.gov/files/air_traffic/technology/adsb/archival/GDL90_Public_ICD_RevA.PDF), 560-1058-00 Rev A. The binary interface compared with the proposed family.
- **NMEA** · [NMEA 0183](https://www.nmea.org/nmea-0183.html). The standard and manufacturer-code application costs, read 13 November 2026.

[ADS-L declaration of conformity](https://skyblip.eu/ads-l/conformity.md)  ·  [Open questions on ADS-L](https://skyblip.eu/ads-l/questions.md)
