Long landing rollout — AAL1508

KOPF · 30

2026-08-27 21:12 UTC· KMIA → KOPF· WILMINGTON TRUST CO TRUSTEE· B738

▶ Replay 📊 Analyse

AAL1508 (Wilmington Trust) was operating from KMIA to KOPF on 2026-08-27. SkyMeter detected a long landing rollout at Miami-Opa Locka Executive Airport (KOPF) on runway 30 at 21:12 UTC. Trace data at the event: 42 ft AGL, 18 kt GS, 0 fpm vertical. METAR at the time reported 5 kt wind, 2 kt crosswind component, 9,656 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)
  • 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 →

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 30
  • 42 ft AGL at event
  • 18 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 2 kt crosswind component
  • 9,656 m visibility
  • KOPF 161753Z 09014G24KT 6SM +RA FEW033 SCT049 BKN065 29/26 A3011 RMK AO2 LTG DSNT W RAB19E20B49 SLP195 6//// T02890256 10328 20278 58004 PNO $

Flight context

  • AAL1508
  • Wilmington Trust
  • B738
  • KMIA → KOPF
  • 2026-08-27 21:12 UTC
  • KOPF runway 30

All events on this flight

Long landing rollout 21:12:00 UTC · KOPF runway 30 · 42 ft AGL · 18 kt GS
Long landing rollout 21:12:00 UTC · KOPF runway 30 · 42 ft AGL · 18 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· KOPF