–
Unclassified movements
Near NMI or BOM, but landing vs. departure couldn't be determined automatically.
–
Unrecognized airline prefixes
Not in the static table and the live lookup found nothing — add these to collector/airlines.json.
–
No route data
The live lookup had no origin/destination on file — this is why the related event (if any) used the altitude heuristic, not route-based detection.
Unclassified movements
The track came close enough to NMI or BOM to be relevant, but neither the route lookup nor the climbing/descending heuristic could tell whether it was arriving or leaving. Check the first/last position and altitude to tag it manually.