ADN110/111/112 all carry first-keyframe time 170 on their _p1F routes, and in a live run all three flipped from not-deployed to active at ~143s on the probe clock. The probe zero sits roughly 10-20s into the mission, putting the arrival at ~155-165s of mission time against a predicted 170. That pins the unit as seconds: 170 frames at 30fps is 5.7s, so they would have been active at the first sample and demonstrably were not. Three squadrons sharing one timetable entry changing state in the same 5s window is not coincidence. Flagged as a match rather than an exact measurement -- the probe clock is not aligned to phase start. Supersedes mission-arrival-watch.md's headline negative: 'no arrival has ever been observed across six runs' was an instrument limit, not a fact about the game. Its craft-counting analysis stays accurate -- craft counts conflate deployment with attrition and cannot see an arrival at all.