Long landing rollout — ABX3113
KTCY · 302026-05-14 04:53 UTC· KRFD → KTCY· ANDROMEDA LEASING I LLC· B763
ABX3113 (Andromeda Leasing I) was operating from KRFD to KTCY on 2026-05-14. SkyMeter detected a long landing rollout at Tracy Municipal Airport (KTCY) on runway 30 at 04:53 UTC. Trace data at the event: 26 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 63/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 5 kt wind, 4 kt crosswind component, 16,093 m visibility. A long landing rollout is detected when ground deceleration after touchdown is below the per-runway P10 envelope. It is an observational measure of rollout efficiency, not a runway-exit incident. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft
BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 30
- 26 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 63/100
- 5 kt wind
- 4 kt crosswind component
- 16,093 m visibility
- METAR KTCY 210115Z AUTO 34008KT 10SM CLR 25/11 A2984 RMK A01
Flight context
- ABX3113
- Andromeda Leasing I
- B763
- KRFD → KTCY
- 2026-05-14 04:53 UTC
- KTCY runway 30
All events on this flight
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data