Unstable approach — AZU8706

KSFB · 09R

2026-06-30 21:27 UTC· SBKP → KSFB· A332

AZU8706 was operating from SBKP to KSFB on 2026-06-30. SkyMeter detected a low approach-stability score at Orlando Sanford International Airport (KSFB) on runway 09R at 21:27 UTC. Trace data at the event: 1147 ft AGL, 137 kt GS. Approach stability score: 39/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 4 kt wind, 3 kt crosswind component, 16,093 m visibility. 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

    Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

    View FAA NOTAM →
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/2698 2026-01-19 09:00Z – 2026-12-18 21:00Z SFC–5,000 ft

    VIEQUES, PR, Monday, January 19, 2026 through Friday, December 18, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4142 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7228 2026-06-13 04:01Z – 2026-07-06 03:59Z SFC–1,000 ft

    Miami, FL, Saturday, June 13, 2026 through Sunday, July 5, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0299 2026-06-26 04:00Z – 2026-10-18 03:59Z SFC–5,000 ft

    Key West, FL, Friday, June 26, 2026 through Saturday, October 17, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0777 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft

    Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/0782 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft

    Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 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 09R
  • 1147 ft AGL at event
  • 137 kt ground speed
  • 0 fpm vertical
  • Approach stability 39/100
  • 4 kt wind
  • 3 kt crosswind component
  • 16,093 m visibility
  • KSFB 080353Z 10SM -RA FEW120 22/22 A2989 RMK AO2 PK WND 33029/0310 SLP120 P0002 T02220222

Flight context

  • AZU8706
  • A332
  • SBKP → KSFB
  • 2026-06-30 21:27 UTC
  • KSFB runway 09R

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· KSFB