AZU8730 was operating from SBKP to KORL on 2026-07-26. SkyMeter detected a low approach-stability score at Orlando Executive Airport (KORL) on runway 25 at 01:50 UTC. Trace data at the event: 1213 ft AGL, 145 kt GS. METAR at the time reported 3 kt wind, 1 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 → - 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 →
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 25
- 1213 ft AGL at event
- 145 kt ground speed
- 0 fpm vertical
- 3 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- METAR KORL 142153Z 19006KT 10SM FEW090 SCT110 26/24 A3012 RMK AO2 LTG DSNT SW RAB26E51 TSB07 SLP203 P0001 T02560239
Flight context
- AZU8730
- B763
- SBKP → KORL
- 2026-07-26 01:50 UTC
- KORL runway 25
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