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

# The declaration skyBlip Go needs, and the documents that go with it.

ADS-L has no ETSO and no MOPS. Under **ADS-L.4.SRD860.A.4** the manufacturer verifies its equipment against the specification and declares conformity on the template in the specification’s appendix. Under **A.5** it ships four documents with the product: that declaration, the declaration of conformity behind the CE marking, an installation manual and a user manual.

This page holds the declaration for skyBlip Go, filled in as far as the facts allow, and links each of the four documents. It will be signed in November or December 2026. The four statements the manufacturer must make hold, and the last table below gives the grounds for each. The firmware now transmits the configured ICAO address under F.2.3. Our reading that this overrides the manufacturer’s address on every payload remains subject to confirmation by EASA, as recorded on the [open questions page](https://skyblip.eu/ads-l/questions.md).

## Firmware and hardware

### skyBlip supplies the firmware, declared on one hardware: the LilyGO T-Echo.

skyBlip Go is skyBlip’s firmware on a LilyGO T-Echo. LilyGO builds the hardware, and the T-Echo has passed CE testing. The declaration covers the firmware on the T-Echo. skyBlip will revise it before it supports any other hardware.

The firmware checks the hardware it runs on. At every start-up it probes the SX1262 radio by a register written and read back, and the BME280 barometer by its chip id. Without either, the unit does not run: it shows its self-test page, neither transmits nor receives, and cannot be activated, because no service runs to answer the activation. A part that fails or is removed after activation stops the unit at its next start-up. A compile-time check rejects a build whose programmed power, with the declared antenna, would exceed 14 dBm e.r.p.

## The documents

### What A.5 asks a manufacturer to ship, and where each one is.

| Document | Where it stands |
| --- | --- |
| ADS-L declaration of conformity | drafted [below](#declaration), not signed |
| CE: radio, EMC, safety, health | skyBlip Go runs on a LilyGO T-Echo, which holds the [attestation of conformity SZ1220803-35313E-RF](https://cdn.shopify.com/s/files/1/0617/7190/7253/files/T-ECHO_CE.pdf?v=1691478157), issued by BACL Shenzhen on 18 Nov 2022 to LilyGO for model T-Echo, under the Radio Equipment Directive 2014/53/EU. It is a test lab’s attestation, not the manufacturer’s declaration. LilyGO lists it on [lilygo.cc/pages/certifications](https://lilygo.cc/pages/certifications), beside the T-Echo’s FCC and MIC certificates. |
| Installation manual | the [Install section](https://skyblip.eu/guides.md#install) of the guides. [Install](https://skyblip.eu/install.md) puts the firmware on the device, and [Cockpit mount](https://skyblip.eu/mount.md) fixes it to the glareshield and places its antenna upright, clear of metal, carbon fibre and the pilot, for vertical polarisation and an omnidirectional pattern. |
| User manual | the [guides](https://skyblip.eu/guides.md). The ADS-L parts are [Radio](https://skyblip.eu/radio.md), on channels, timing and what is transmitted, and activation at [skyblip.eu/activate](https://skyblip.eu/activate), which gives a unit its address. |

skyBlip Bravo, a Seeed SenseCAP MeshTracker X1, carries no ADS-L radio under skyBlip firmware: it receives ADS-B on 1090 MHz and transmits nothing, so no ADS-L declaration covers it. Its CE document is Seeed’s [verification of compliance LGT26F105C01](https://files.seeedstudio.com/Seeed_Certificate/documents_certificate/100093876-CE.pdf), issued by Shenzhen LGT Test Service on 8 Sep 2026 under the Radio Equipment Directive.

## The address

### Manufacturer page 49, AMT entry 58, prefix 0, assigned on 5 October 2026.

The declaration states that the product uses an approved address range (F.2.2). skyBlip applied to the ADS-L registry on 20 September 2026, and FLARM assigned manufacturer page 49, AMT entry 58, with manufacturer prefix 0, under ticket #228794. Each unit gets its 16 bits below the prefix at activation: skyblip.eu assigns the serial against the unit’s chip id and signs it, and a unit that holds no serial neither transmits nor receives. The application, the log of the exchange and the reasons behind it are on [the ADS-L registry page](https://skyblip.eu/ads-l/registry.md). When the pilot enters the aircraft’s ICAO address, Go transmits under AMT entry 5 with that address on every payload it sends: Traffic, Status and the payload 66 callsign record. Clearing the setting restores AMT entry 58 and the unit’s serial from the next burst.

## The declaration

### The appendix template, filled in for skyBlip Go.

The PDF to sign will be printed from this same text. The next section gives the grounds for each field and statement.

in accordance with ED Decision 2022/024/R and the attached Technical Specification for ADS-L transmissions using the SRD-860 frequency band (“ADS-L 4 SRD 860”)

The undersigned, representing the manufacturer:

François Catuhe EI  
23 cours de Verdun, 33000 Bordeaux, France

declares under sole responsibility that the following product:

Product NameskyBlip GoHardware ReferenceBrand LILYGO, model T-Echo, 868 MHz, with BME280Firmware VersionskyBlip v1, with ADS-L protocol v1

is in conformity with the ADS-L 4 SRD860 Standard Issue 2

The manufacturer supplies the firmware. This declaration covers it on one hardware, the LilyGO T-Echo, which has passed CE testing. The manufacturer will revise this declaration before supporting any other hardware.

At every start-up the firmware checks that the radio and the barometer answer. If either does not, the unit does not run: it neither transmits nor receives, and it cannot be activated.

The device operates on the following transmission parameters:

Transmission Bands and Power LevelsM-band only, on 868.2 MHz and 868.4 MHz. Transmit power set to 14 dBm (25 mW), within the M-band limit of 14 dBm e.r.p. Nothing is transmitted on the O-band.Optional Parameters Transmitted (ADS-L)None. The Traffic and Status payloads carry no optional parameters, and no secure signature (E.4) is appended.Receive capabilitiesM-band, scheduled every UTC second on 868.2 MHz from 447 to 822 ms and on 868.4 MHz from 827 to 1202 ms, 375 ms on each channel. Over the direct slot, 450 to 1000 ms, the average dwell is 49.5 % across the two channels, less the device’s own bursts, declared as Partial (G.2.2). O-band HDR, 869.525 MHz, scheduled from 207 to 442 ms of every second, 235 ms inside the uplink slot, for the Traffic Uplink. O-band LDR is not received.

The manufacturer additionally declares that:

- Robust design processes and production controls are in place during manufacturing to ensure consistent quality and compliance with the applicable standard,
- The product’s hardware, the LilyGO T-Echo, has passed CE testing for radio, EMC, safety and health under the Radio Equipment Directive 2014/53/EU (attestation of conformity SZ1220803-35313E-RF, BACL Shenzhen, 18 November 2022),
- The product uses an approved address range (Section ADS-L.4.SRD860.F.2.2)
- The product nominally transmits at least the “Traffic” and “Status” payloads (Subpart G)

DateAuthorized RepresentativeFrançois CatuhePositionEntrepreneur individuelSignature and Company Stamp

## The grounds

### What stands behind each field and statement.

The declaration names skyBlip firmware v1, which carries skyBlip’s ADS-L protocol v1, for ADS-L 4 SRD-860 Issue 2. Every v1 release of the protocol is covered, from v1.0.0. Development builds carry 0.1.0 until the first production release. The ADS-L protocol version is separate from the packet’s Protocol Version field in E.1.1. From v1.0.0, it changes only when ADS-L behaviour changes. Each firmware release lists the protocol versions it carries. A unit reports its ADS-L version through the companion link’s `protocols` command, and the briefing app’s device page displays it.

### Transmission parameters

M-band only. Traffic uses 868.2 MHz in an even UTC second and 868.4 MHz in an odd one. Status uses the other channel. Traffic and Status bursts start and finish inside C.5’s direct slot, 450 to 1000 ms after the UTC second. Their instants are drawn from the unit’s own address and UTC second, not from the configured ICAO address. The SX1262 is programmed for nominal +14 dBm conducted power, with a datasheet tolerance of ±2 dB. A 0.5 dB feed loss allowance and the antenna’s datasheet peak gain of 1.6 dBi give a computed e.r.p. of 12.95 dBm after the 2.15 dB conversion from dBi to dBd. A compile-time check rejects a computed e.r.p. above 14 dBm, the M-band limit in C.2. Output power, antenna gain and feed loss have not been measured on a unit. The appendix asks for 12 to 14 dBm e.r.p. on M-band. Nothing is transmitted on the O-band. The declaration states the 14 dBm the firmware sets.

No optional parameters within the defined Traffic and Status payloads. Both payloads are required by the appendix declaration. No secure signature (E.4) is appended. Each packet carries the lowest Protocol Version whose payload encoding is the same, as E.1.1 requires. Status always carries Protocol Version 1.

Channel access uses EN 300 220-2 band M’s 1 % duty-cycle limit over any hour. The firmware refuses a burst past that budget. D.3 also requires listen-before-talk. Before an unforced burst, Go assesses its channel for 200 µs, ending at most 2 ms before transmission. The -78.99 dBm limit for a 0 dBd antenna becomes -78.44 dBm at the antenna connector after correction for the antenna’s datasheet gain of -0.55 dBd. The 0.5 dB feed loss allowance between connector and chip puts the chip’s busy threshold at -78.94 dBm. Neither gain nor loss has been measured on a unit. The SX1262’s RSSI is uncalibrated, with no margin for its error. This is a known limit of the declaration. A busy channel defers the burst by a random 3 to 50 units of 5 ms, C.2’s backoff interval of 15 to 250 ms, as far as its window reaches. Only on the ground may Go force it after 3000 ms, followed by 2000 ms without its own transmissions.

The Status payload, type 3, is scheduled twice per 20 s cycle, airborne and on the ground in the same seconds. The cycle starts at the even second `c = 2 * (serial mod 10)`, where the serial is the low 16 bits of the unit’s own address, not the configured ICAO address. Status goes at c+2 on 868.4 MHz and c+11 on 868.2 MHz. The intervals are 9 then 11 s. Each channel carries one Status every 20 s, meeting G.2.11’s minimum for a receiver listening on one channel. These are nominal rates. An unsent burst retries at 2 s intervals on the same channel when its dwell is free, until sent or its type’s next turn is due.

| Status field | Declared value | Clause |
| --- | --- | --- |
| Max. Protocol Version | 1 | G.2.1 |
| M-band receive | 2, Partial | G.2.2 |
| O-band LDR receive | 0 | G.2.3 |
| O-band HDR receive | 0. Reception is confined to the uplink slot, which this field excludes | G.2.4 |
| ADS-L 4 Mobile | 0 | G.2.5 |
| E-conspicuity receive | Bit 0, FLARM-generation. Bit 4, ADS-B 1090, is also set while a paired Bravo is live | G.2.6 |
| E-conspicuity transmit | Bit 4, ADS-B 1090, once the aircraft’s transponder is known to send it. 0 otherwise, which the clause reads as unknown | G.2.7 |
| XPDR | 2, Mode S, once the aircraft’s transponder is known. 0 otherwise, which the clause reads as unknown | G.2.8 |
| Traffic Uplink client | 1 | G.2.9 |
| FIS-B client | 0 | G.2.10 |

The aircraft’s transponder is known once a paired Bravo, on the ground, hears the transponder at the configured ICAO address. A transponder heard at a 24-bit address is Mode S. Once Bravo hears it identify in an extended squitter, it also sends ADS-B 1090. An ICAO address alone proves nothing, since aircraft without a transponder can have one, and Bravo’s reception alone can be a neighbour’s on the apron. When the pilot accepted Bravo’s suggestion as the address, the match rests on that acceptance. Go keeps what it confirmed for as long as the configured address stays the same and the unit runs, so the Status still declares it in flight. Two limits follow from that. A transponder switched off or failed in flight stays declared until the address changes or the unit restarts, since Bravo names it on the ground only. A transponder that sends ADS-B positions but no identification is not counted as ADS-B out.

The callsign record is scheduled in slot 1’s tail in seconds c+4 and c+14, from 1000 to 1190 ms after each second starts, on 868.4 MHz. Those seconds follow the scheduled ground positions by 4 and 5 s respectively. The tail falls in the next UTC second’s reserved interval under C.5. skyBlip treats the record as its own payload, but it travels in the same ADS-L frame, with the same sync word, scrambling and CRC-24. Transmitting there is a deliberate deviation from C.5. The [callsign page](https://skyblip.eu/ads-l/callsign.md) explains the record and its planned replacement by Issue 3.

### What the manufacturer additionally declares

| Statement | Holds | Why |
| --- | --- | --- |
| Design processes and production controls | yes | LilyGO manufactures the T-Echo under its own production controls, and the model passed BACL Shenzhen’s CE tests. skyBlip designs the firmware, and CI runs the ADS-L component and device conformance suites, the EN 300 220 suite and both clause checks on every pull request and push to main that changes the firmware. The ADS-L suites have at least one case for each of Issue 2’s 80 clause headings. Nineteen cases are skipped: nine prose, two paperwork and eight optional. None is skipped as not implemented. The cases for F.2.3, the last clause marked as not implemented, now pass. Go refuses `FFFFFF`, an address no aircraft holds, and, on the ground while a paired live Bravo names the aircraft’s transponder, an entered address that differs from it. A clear is never refused. Each unit is checked again where it is used: at every start-up the firmware refuses to run without its radio and barometer, and skyblip.eu activates each unit on its own, signing its serial against its chip id. These software checks do not replace measurements on a unit. |
| Hardware has passed CE | yes | the T-Echo passed BACL Shenzhen’s tests for radio, EMC, safety and health under the Radio Equipment Directive. The declaration states this in place of the template’s wording, which says the product is CE marked. |
| Approved address range, F.2.2 | yes | AMT entry 58, manufacturer page 49, prefix 0, assigned by the registry. The unit retains that assignment while transmitting under AMT entry 5 with the aircraft’s configured ICAO address under F.2.3. |
| Traffic and Status payloads, Subpart G | yes | Traffic is scheduled at 1 Hz airborne and 0.1 Hz on average on the ground, with ground positions 9 then 11 s apart. This is skyBlip’s reading of G.1.16 with C.2.5’s channel alternation. Each position is a solution the receiver measured on .000 or .500 of the second, named to the quarter second under G.1.1, and leaves within 500 ms of that measurement under G.1.16. The receiver solves twice a second for this, and a position on 868.2 MHz that would carry an older fix waits for the half-second solution. The reading is one of our [open questions to EASA](https://skyblip.eu/ads-l/questions.md). Status, payload type 3, is scheduled twice per 20 s cycle, 9 then 11 s apart. Each channel carries one Status every 20 s, meeting G.2.11’s minimum. Under B.5, Traffic uses Issue 1 encoding beside a close neighbour that reads only Issue 1. A position with unknown altitude, ground speed or vertical rate is held rather than sent with a false Issue 1 value. |

## References

- **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. A.4 qualification system, A.5 documentation, the appendix declaration of conformity.
- **skyBlip firmware** — [the ADS-L conformance report](https://github.com/fcatuhe/skyblip/blob/main/docs/ADSL_CONFORMANCE.md). Every clause heading of Issue 2 in the specification’s order, with the test cases that check it and the file each one is in, every skipped case with its reason, then the EN 300 220 cases and the stack’s own tests. Generated from the suite as it runs, and checked in CI.
- **skyBlip firmware** — the ADS-L conformance suite in [`firmware/protocols/adsl/test/conformance/`](https://github.com/fcatuhe/skyblip/tree/main/firmware/protocols/adsl/test/conformance) and [`firmware/test/adsl/`](https://github.com/fcatuhe/skyblip/tree/main/firmware/test/adsl). The first half checks the ADS-L component on its own. The second checks what needs the device around it. Together they read all 80 clause headings of Issue 2. A skipped case records its reason as not implemented, prose, paperwork or optional.
- **skyBlip firmware** — [the EN 300 220 suite](https://github.com/fcatuhe/skyblip/tree/main/firmware/test/en300220). Eleven listed clauses of EN 300 220-1 V3.1.1 and EN 300 220-2 V3.3.1 for the 868 MHz transmitter. Two cases are skipped for optional adaptive frequency agility, which Go does not use.

[Where an aircraft's callsign goes in ADS-L](https://skyblip.eu/ads-l/callsign.md)  ·  [ADS-L NMEA proposal for Bluetooth displays](https://skyblip.eu/ads-l/nmea.md)
