Long landing rollout — UAL2119
MWCR · 262026-01-15 18:16 UTC· KEWR → MWCR· WILMINGTON TRUST CO TRUSTEE· B39M
UAL2119 (Wilmington Trust) was operating from KEWR to MWCR on 2026-01-15. SkyMeter detected a long landing rollout at Owen Roberts International Airport (MWCR) on runway 26 at 18:16 UTC. Trace data at the event: 9 ft AGL, 6 kt GS, 0 fpm vertical. Approach stability score: 62/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, 9,999 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/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 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 26
- 9 ft AGL at event
- 6 kt ground speed
- 0 fpm vertical
- Approach stability 62/100
- 10 kt wind
- 0 kt crosswind component
- 9,999 m visibility
- METAR MWCR 282100Z 15007KT 100V190 9999 FEW018 31/25 Q1012
Flight context
- UAL2119
- Wilmington Trust
- B39M
- KEWR → MWCR
- 2026-01-15 18:16 UTC
- MWCR runway 26
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