explaingit

s-leo-de/following-the-jets

Analysis updated 2026-05-18

0PythonAudience · researcherComplexity · 4/5Setup · hard

TLDR

Following the Jets rebuilds and rigorously tests the idea that tracking acquirer jet flights can predict mergers, and finds the signal mostly does not hold up.

Mindmap

mindmap
  root((following-the-jets))
    What it does
      Tests jet flight merger signal
      Rebuilds trade from scratch
      Adversarial self audit
      Reports honest null result
    Tech stack
      Python
      R
      SQLite Parquet
      Flight tracking data
    Use cases
      Study signal auditing method
      Reproduce event study backtest
      Learn control matching techniques
    Audience
      Researchers
      Quant analysts
      Data skeptics

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Study a worked example of how to adversarially audit a promising looking data signal.

USE CASE 2

Reproduce an event study and backtest pipeline for testing alternative data trading ideas.

USE CASE 3

Learn statistical techniques like calendar matching and one firm one vote testing for detecting false positives.

What is it built with?

PythonRSQLiteParquet

How does it compare?

s-leo-de/following-the-jets0xallam/my-recipe0xhassaan/nn-from-scratch
Stars00
LanguagePythonPythonPython
Last pushed2022-11-22
MaintenanceDormant
Setup difficultyhardmoderatemoderate
Complexity4/52/54/5
Audienceresearchergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Requires licensed WRDS and OpenSky data credentials to reproduce the live data pulls.

No license information is stated in the explanation, so terms of use are unclear.

In plain English

Following the Jets is a research project that investigates a well known idea in alternative data investing: that tracking a company's private jet flights can reveal an upcoming merger before it is announced. The author rebuilt this trade from scratch using over 1.2 million flights and more than 200 acquiring companies, then tried as hard as possible to break the result rather than confirm it. The final conclusion is that there is no reliable signal that predicts mergers before they are announced, and no way to trade on it profitably. What does hold up is a smaller and less exciting fact: acquiring companies tend to fly slightly more often to the cities where their eventual targets are based, but this happens consistently over time rather than picking up right before a deal. A backward looking version of the analysis produces an impressive looking result, but that number only appears because the deals are already known and the flights are matched to them afterward. Once the question is flipped to ask how often a jet visits without a deal following, the apparent edge mostly disappears. Several rounds of more careful controls, including matching by calendar timing and by how active a company generally is, shrink the effect toward nothing. A test that only allows one vote per company, rather than counting individual flights, finds no effect in any version tried. A comparison group built to have no real signal also comes back null, pointing to ordinary business connections rather than early knowledge of a coming deal. The timing of flights actually increases after a merger is announced, not before, which argues against the predictive idea entirely. The author frames the real value of the project as the method itself, a demonstration of how to test a promising looking data signal using matched controls, careful statistics, and adversarial review, until only what is actually true remains. The project draws on large scale flight tracking data, aircraft registration records, and financial market data, combined with statistical techniques from event studies and quantitative finance. The underlying licensed financial data is not included in the repository, but the code and analysis scripts are provided so the work can be reproduced by someone with the right data access. This project is aimed at researchers, quantitative analysts, and anyone curious about how to rigorously test a data driven trading idea.

Copy-paste prompts

Prompt 1
Explain why the retrospective odds ratio in Following the Jets looked strong but collapsed under forward testing.
Prompt 2
Walk me through the calendar matching and placebo tests used to check the jet flight merger signal.
Prompt 3
What does the one firm one vote sign test show about the reliability of this trading signal?
Prompt 4
Summarize the six step audit process this project used to test its own headline result.

Frequently asked questions

What is following-the-jets?

Following the Jets rebuilds and rigorously tests the idea that tracking acquirer jet flights can predict mergers, and finds the signal mostly does not hold up.

What language is following-the-jets written in?

Mainly Python. The stack also includes Python, R, SQLite.

What license does following-the-jets use?

No license information is stated in the explanation, so terms of use are unclear.

How hard is following-the-jets to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is following-the-jets for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.