WHYSE
ANOMALY

The engine found the COVID cliff in NYC taxi data without being told to look

Daily trip volume, 14 Mar 20202,114 forecast1,428 observed−686
Mid-fare, non-tipped
−686
All other segments
0
Mid-fare, non-tipped trips fell 32% below forecast on 2020-03-14 — outside the confidence interval
4 min
TIME TO ANSWER
8,400
SEGMENTS CHECKED
2020 full year
DATASET SIZE

The question we asked

> assuming today is 14 March 2020, run a trend and spike analysis on trip volume

What the engine found

No sustained trend across the period — and one sharp single-day drop on 14 March 2020, concentrated in the mid-fare, non-tipped segment.

Observed volume fell to 1,428 against a forecast of 2,114, well outside the confidence interval. The engine flagged it as worth investigating for an external disruption.

What it means

We know exactly what happened in New York on that date. The engine did not — it has no calendar of world events and no labels. It monitored every meaningful segment against its own forecast and surfaced the one that broke. That is the whole proposition: the finding did not depend on anyone suspecting there was something to find.

The honest caveat, and it belongs here: a single-day drop of this size is not subtle, and a competent analyst watching that chart would have seen it too. What they would not have done is check all 8,400 segments to establish that this one was anomalous and the others were not.

Observed 1,428 against a forecast of 2,114 — well outside the confidence interval, on a day nobody had flagged.

NYC Green Taxi, 14 March 2020

Check it yourself

NYC TLC trip record data is public. Dataset, dimensions and the exact window are listed to the right; the run takes about four minutes on commodity hardware.

GET STARTED

Ask your first why.

Bring one question you've been putting off. We'll build the cube and answer it on the call.