Long landing rollout — AUA3VG

KEWR · 29

2026-07-03 17:58 UTC· LOWW KEWR· B789

AUA3VG was operating from LOWW to KEWR on 2026-07-03. SkyMeter detected a long landing rollout at Newark Liberty International Airport (KEWR) on runway 29 at 17:58 UTC. Trace data at the event: 6 ft AGL, 10 kt GS, 0 fpm vertical. Approach stability score: 51/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 10 kt wind, 4 kt crosswind component, 16,093 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 →
  • SECURITY6/3955 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Smithfield, RI, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3959 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Boston, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3963 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    FOXBOROUGH, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3969 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Waltham, MA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/4105 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    JERSEY CITY, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3949 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

    Providence, RI, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

    View FAA NOTAM →
  • SECURITY6/6851 2026-06-13 04:01Z – 2026-07-12 03:59Z SFC–1,000 ft

    Harrison, NJ, Saturday, June 13, 2026 through Saturday, July 11, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7230 2026-06-13 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft

    New York, NY, Saturday, June 13, 2026 through Sunday, July 19, 2026 Local

    View FAA NOTAM →
  • SECURITY6/7801 2026-06-15 04:00Z – 2026-07-07 03:29Z SFC–400 ft

    Whippany, NJ, Monday, June 15, 2026 through Monday, July 6, 2026 Local

    View FAA NOTAM →
  • SECURITY6/9462 2026-06-24 04:00Z – 2026-07-21 03:29Z SFC–400 ft

    Montclair, NJ, Wednesday, June 24, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • SECURITY6/1081 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft

    New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 2026 Local

    View FAA NOTAM →
  • SECURITY6/1240 2026-07-01 12:00Z – 2026-07-09 16:00Z SFC–2,000 ft

    New York, NY, Wednesday, July 1, 2026 through Thursday, July 9, 2026 Local

    View FAA NOTAM →
  • 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 29
  • 6 ft AGL at event
  • 10 kt ground speed
  • 0 fpm vertical
  • Approach stability 51/100
  • 10 kt wind
  • 4 kt crosswind component
  • 16,093 m visibility
  • KEWR 161151Z 20004KT 10SM BKN110 BKN160 BKN250 17/13 A3037 RMK AO2 SLP283 T01720133 10172 20156 51006 $

Flight context

  • AUA3VG
  • B789
  • LOWW → KEWR
  • 2026-07-03 17:58 UTC
  • KEWR runway 29

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· KEWR