Rejected takeoff — SIY157

MBPV · 28

2025-11-26 15:38 UTC· MBPV → KMCO· VALIAIR LC TRUSTEE· E35L

▶ Replay 📊 Analyse

SIY157 (Valiair LC) was operating from MBPV to KMCO on 2025-11-26. SkyMeter detected a rejectedtakeoff at Providenciales Airport (MBPV) on runway 28 at 15:38 UTC. Trace data at the event: 16 ft AGL, 89 kt GS, 0 fpm vertical. 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 17 kt wind, 5 kt crosswind component, 9,999 m visibility. 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 →

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 28
  • 16 ft AGL at event
  • 89 kt ground speed
  • 0 fpm vertical
  • Approach stability 88/100
  • 17 kt wind
  • 5 kt crosswind component
  • 9,999 m visibility
  • METAR MBPV 272200Z 00000KT 9999 FEW018 BKN025 30/22 Q1013

Flight context

  • SIY157
  • Valiair LC
  • E35L
  • MBPV → KMCO
  • 2025-11-26 15:38 UTC
  • MBPV runway 28

All events on this flight

Rejected takeoff 15:38:41 UTC · MBPV runway 28 · 16 ft AGL · 89 kt GS
Rejected takeoff 15:38:41 UTC · MBPV runway 28 · 16 ft AGL · 89 kt GS
Rejected takeoff 15:38:41 UTC · MBPV runway 28 · 16 ft AGL · 89 kt GS
Rejected takeoff 15:38:41 UTC · MBPV runway 28 · 16 ft AGL · 89 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· MBPV