Long landing rollout — BAW8

EGLL · 27L

2025-11-23 15:29 UTC· RJTT → EGLL· B789

BAW8 was operating from RJTT to EGLL on 2025-11-23. SkyMeter detected a long landing rollout at London Heathrow Airport (EGLL) on runway 27L at 15:29 UTC. Trace data at the event: 72 ft AGL, 5 kt GS, 0 fpm vertical. Approach stability score: 85/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 13 kt wind, 6 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/2811 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–1,000 ft

    NEW YORK, NY, 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 27L
  • 72 ft AGL at event
  • 5 kt ground speed
  • 0 fpm vertical
  • Approach stability 85/100
  • 13 kt wind
  • 6 kt crosswind component
  • 9,994 m visibility
  • EGLL 071320Z AUTO 35008KT 300V040 9999 -RADZ BKN009 13/12 Q1012

Flight context

  • BAW8
  • B789
  • RJTT → EGLL
  • 2025-11-23 15:29 UTC
  • EGLL runway 27L

All events on this flight

Long landing rollout 15:29:29 UTC · EGLL runway 27L · 72 ft AGL · 5 kt GS
Long landing rollout 15:29:29 UTC · EGLL runway 27L · 72 ft AGL · 5 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· EGLL