Long landing rollout — QQE226

EGMC · 23

2026-08-25 23:28 UTC· K1B2 EGMC· GA7C

QQE226 was operating from K1B2 to EGMC on 2026-08-25. SkyMeter detected a long landing rollout at Southend Airport (EGMC) on runway 23 at 23:28 UTC. Trace data at the event: 49 ft AGL, 2 kt GS, 0 fpm vertical. Approach stability score: 82/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 2 kt wind, 2 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)
  • SECURITY6/2790 2026-07-02 22:30Z – 2026-09-15 03:59Z SFC–400 ft

    St. George, ME, Thursday, July 2, 2026 through Monday, September 14, 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 23
  • 49 ft AGL at event
  • 2 kt ground speed
  • 0 fpm vertical
  • Approach stability 82/100
  • 2 kt wind
  • 2 kt crosswind component
  • 9,994 m visibility
  • EGMC 160650Z 28007KT 260V320 9999 FEW020 14/11 Q1018

Flight context

  • QQE226
  • GA7C
  • K1B2 → EGMC
  • 2026-08-25 23:28 UTC
  • EGMC runway 23

All events on this flight

Long landing rollout 23:28:43 UTC · EGMC runway 23 · 49 ft AGL · 2 kt GS
Long landing rollout 23:28:43 UTC · EGMC runway 23 · 49 ft AGL · 2 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· EGMC