Long landing rollout — UAL146
EGWU · 252026-07-27 10:05 UTC· KEWR → EGWU· UNITED AIRLINES INC· B763
UAL146 (United Airlines) was operating from KEWR to EGWU on 2026-07-27. SkyMeter detected a long landing rollout at RAF Northolt (EGWU) on runway 25 at 10:05 UTC. Trace data at the event: 72 ft AGL, 7 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, 5 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 → - 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 25
- 72 ft AGL at event
- 7 kt ground speed
- 0 fpm vertical
- Approach stability 51/100
- 10 kt wind
- 5 kt crosswind component
- 9,994 m visibility
- EGWU 071450Z 36011KT 9999 BKN009 12/10 Q1012 TEMPO 6000 -RADZ RMK GRN TEMPO GRN
Flight context
- UAL146
- United Airlines
- B763
- KEWR → EGWU
- 2026-07-27 10:05 UTC
- EGWU runway 25
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