Long landing rollout — FJO64J

BIRK · 01

2026-08-14 19:38 UTC· KHPN → BIRK· E550

▶ Replay 📊 Analyse

FJO64J was operating from KHPN to BIRK on 2026-08-14. SkyMeter detected a long landing rollout at Reykjavik Airport (BIRK) on runway 01 at 19:38 UTC. Trace data at the event: 0 ft AGL, 5 kt GS, 0 fpm vertical. METAR at the time reported 13 kt wind, 1 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 →
  • VIP6/4487 2026-08-14 17:15Z – 2026-08-14 21:15Z SFC–17,999 ft

    Garden City, NY, Friday, August 14, 2026 Local

    View FAA NOTAM →
  • VIP6/4488 2026-08-14 17:15Z – 2026-08-14 21:15Z SFC–17,999 ft

    Garden City, NY, Friday, August 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 01
  • 0 ft AGL at event
  • 5 kt ground speed
  • 0 fpm vertical
  • 13 kt wind
  • 1 kt crosswind component
  • 9,994 m visibility
  • BIRK 161200Z 13017G27KT 9999 -RA SCT015 OVC035 12/09 Q0978

Flight context

  • FJO64J
  • E550
  • KHPN → BIRK
  • 2026-08-14 19:38 UTC
  • BIRK runway 01

All events on this flight

Long landing rollout 19:38:51 UTC · BIRK runway 01 · 0 ft AGL · 5 kt GS
Long landing rollout 19:38:51 UTC · BIRK runway 01 · 0 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· BIRK