Long landing rollout — AAY24
KMFR · 322026-03-27 04:21 UTC· KSNA → KMFR· SUNRISE ASSET MANAGEMENT LLC· A319
AAY24 (Sunrise Asset Management) was operating from KSNA to KMFR on 2026-03-27. SkyMeter detected a long landing rollout at Rogue Valley International Medford Airport (KMFR) on runway 32 at 04:21 UTC. Trace data at the event: 1295 ft AGL, 4 kt GS. METAR at the time reported 4 kt wind, 3 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)- SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft
Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local
View FAA NOTAM → - 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 32
- 1295 ft AGL at event
- 4 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KMFR 221253Z 00000KT 10SM CLR 12/09 A3001 RMK AO2 SLP153 T01170089
Flight context
- AAY24
- Sunrise Asset Management
- A319
- KSNA → KMFR
- 2026-03-27 04:21 UTC
- KMFR runway 32
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