Long landing rollout — UAL980
EIDW · 28L2026-08-23 08:56 UTC· KORD → EIDW· UNITED AIRLINES INC· B788
UAL980 (United Airlines) was operating from KORD to EIDW on 2026-08-23. SkyMeter detected a long landing rollout at Dublin Airport (EIDW) on runway 28L at 08:56 UTC. Trace data at the event: 203 ft AGL, 8 kt GS, 0 fpm vertical. METAR at the time reported 4 kt wind, 4 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 → - AIR SHOWS/SPORTS6/5669 2026-08-21 22:30Z – 2026-08-23 19:00Z SFC–10,000 ft
muskegon, MI, Friday, August 21, 2026 through Sunday, August 23, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/5491 2026-08-22 22:00Z – 2026-08-23 03:59Z SFC–400 ft
Foxborough, MA, Saturday, August 22, 2026 through Sunday, August 23, 2026 UTC
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 28L
- 203 ft AGL at event
- 8 kt ground speed
- 0 fpm vertical
- 4 kt wind
- 4 kt crosswind component
- 9,994 m visibility
- EIDW 161730Z 24008KT 200V280 9999 FEW018 BKN025 BKN028 15/10 Q1015 NOSIG
Flight context
- UAL980
- United Airlines
- B788
- KORD → EIDW
- 2026-08-23 08:56 UTC
- EIDW runway 28L
All events on this flight
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