npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

mode-s-adsb-parser

v0.3.2

Published

Parses Mode S Extended Messages (so called ADSB messages)

Readme

ADSB / Mode S Parser

Parses Mode S Extended Messages (so called ADSB messages)

Dependencies

  • none

Test Coverage

see coverage/lcov-report/index.html

Usage

install via npm:

npm i --save mode-s-adsb-parser

//Mode S
import {parseModeS} from 'mode-s-adsb-parser'

// parsing does minimal work and just makes sure the structure is correct
const parsedModeSMessage = parseModeS([255, 255, 255, 255, 255])

// decodeLocation will only decode the location part of the message (so you can tell wether this is an interesting packet for you, and you want to fully decode it)
decodeLocation()


// fully decodes the message into values that is human readable, self explanatory and uses real world units
decode()



// ADSB
import {parseADSB, decodeBasics} from 'mode-s-adsb-parser'

// downlinkFormat 19 = ADSB (or so call Mode-S Extended Squitter) Message
if(parsedModeS.downlinkFormat === 19){

    // parsing does minimal work and just makes sure the structure is correct
    const parsedADSBMessage = parseADSB(parsedModeSMessage)

    // decodeLocation will only decode the location part of the message (so you can tell wether this is an interesting packet for you, and you want to fully decode it)
    const decodedADSBMessageBasics = decodeBasics(parsedADSBMessage)

    if(decodedADSBMessageBasics.icaoAddress6charHexLowercase === 'ac09f4'){

        // fully decodes the message into values that is human readable, self explanatory and uses real world units
        decode(parsedADSBMessage)
    }
}

/* Decoding positon of a transponder
    Transponders do not just send gps coordinates, they encode it to save data bits.
    Because of that, you need multiple messages to reliably calculate the gps coordinates.

    In order to get unambigious (globally unique) aircraft position, you need 2 messages of type Airborne Position or Surface Position. One of the message has to be cpr format "odd", the other one has to be cpr format "even".

    The time difference between these 2 messages should be low (TODO: how low exactly?)


    Once you have computed the unambigious position, you can use a shortcut once you receive a new position message.
    But this only works if the distance between the two message is less than 180 nautical miles.

    You should enforce this distance limit e.g. by limiting the time between those two messages (e.g. 5 minutes works until mach 3.2 or 4000 km/h )
*/

Changelog

see CHANGELOG.md

For Developers

see DEV.md