Unstable approach — VIV7826

KF69 · 16

2026-08-25 18:53 UTC· MMMY KF69· A320

VIV7826 was operating from MMMY to KF69 on 2026-08-25. SkyMeter detected a low approach-stability score at Air Park Dallas Airport (KF69) on runway 16 at 18:53 UTC. Trace data at the event: 1776 ft AGL, 141 kt GS. Approach stability score: 40/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 9 kt wind, 5 kt crosswind component. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft

    South Padre Island, TX, Tuesday, May 6, 2025 Local

    View FAA NOTAM →
  • SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

    View FAA NOTAM →
  • SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft

    Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

    View FAA NOTAM →
  • HAZARDS6/6701 2026-08-21 05:00Z – 2026-08-26 05:00Z SFC–5,000 ft

    BROWNSVILLE, TX, Friday, August 21, 2026 through Wednesday, August 26, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7111 2026-08-24 05:00Z – 2026-09-05 05:00Z SFC–10,000 ft

    BROWNSVILLE, TX, Monday, August 24, 2026 through Saturday, September 5, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7589 2026-08-24 20:35Z – 2026-08-29 02:00Z SFC–5,500 ft

    2NM W PALO PINTO, TX, Monday, August 24, 2026 through Saturday, August 29, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7630 2026-08-25 12:00Z – 2026-09-01 02:00Z SFC–5,500 ft

    1NM W PALO PINTO, TX, Tuesday, August 25, 2026 through Tuesday, September 1, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7859 2026-08-25 17:21Z – 2026-08-26 17:21Z SFC–6,200 ft

    1NM NE EVANT, TX, Tuesday, August 25, 2026 through Wednesday, August 26, 2026 UTC

    View FAA NOTAM →
  • HAZARDS6/7885 2026-08-25 19:02Z – 2026-09-02 23:45Z SFC–5,500 ft

    PALO PINTO, TX, Tuesday, August 25, 2026 through Wednesday, September 2, 2026 UTC

    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 16
  • 1776 ft AGL at event
  • 141 kt ground speed
  • 0 fpm vertical
  • Approach stability 40/100
  • 9 kt wind
  • 5 kt crosswind component

Flight context

  • VIV7826
  • A320
  • MMMY → KF69
  • 2026-08-25 18:53 UTC
  • KF69 runway 16

All events on this flight

Unstable approach 18:53:46 UTC · KF69 runway 16 · 1,776 ft AGL · 141 kt GS
Unstable approach 18:53:46 UTC · KF69 runway 16 · 1,776 ft AGL · 141 kt GS

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

SkyMeter · trace data observed via ADS-B· KF69