AZU8707 was operating from KMCO to SBKP on 2026-04-18. SkyMeter detected a long landing rollout at Viracopos International Airport (SBKP) on runway 15 at 08:15 UTC. Trace data at the event: 2083 ft AGL, 8 kt GS. Approach stability score: 88/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 4 kt wind, 4 kt crosswind component, 9,994 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/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 →
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 15
- 2083 ft AGL at event
- 8 kt ground speed
- 0 fpm vertical
- Approach stability 88/100
- 4 kt wind
- 4 kt crosswind component
- 9,994 m visibility
- SBKP 211700Z 35013KT 9999 FEW048TCU BKN100 29/18 Q1014
Flight context
- AZU8707
- A339
- KMCO → SBKP
- 2026-04-18 08:15 UTC
- SBKP runway 15
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