Long landing rollout — UAL681
KCDW · 222026-07-10 21:27 UTC· KEWR → KCDW· UNITED AIRLINES INC· B39M
UAL681 (United Airlines) was operating from KEWR to KCDW on 2026-07-10. SkyMeter detected a long landing rollout at Essex County Airport (KCDW) on runway 22 at 21:27 UTC. Trace data at the event: 0 ft AGL, 4 kt GS, 0 fpm vertical. Approach stability score: 55/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 4 kt wind, 3 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)- SECURITY6/3956 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Atlantic City, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3961 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Chester, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3965 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Galloway, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3967 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PHILADELPHIA, PA, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3973 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
WILMINGTON, DE, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4106 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
New Brunswick, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4115 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BASKING RIDGE, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4117 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Warren, NJ, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/6442 2026-06-10 04:01Z – 2026-07-20 03:59Z SFC–1,000 ft
Philadelphia, PA, Wednesday, June 10, 2026 through Sunday, July 19, 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/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/7980 2026-07-03 16:07Z – 2026-07-21 03:59Z SFC–400 ft
New Brunswick, NJ
View FAA NOTAM → - SECURITY6/7973 2026-07-07 16:07Z – 2026-07-21 03:59Z SFC–400 ft
Basking Ridge, NJ
View FAA NOTAM → - SECURITY6/7138 2026-07-10 14:07Z – 2026-07-21 03:59Z SFC–400 ft
Philadelphia, PA
View FAA NOTAM → - AIR SHOWS/SPORTS6/3030 2026-07-10 21:00Z – 2026-07-12 19:00Z SFC–4,000 ft
Sparrows Point, MD, Friday, July 10, 2026 through Sunday, July 12, 2026 UTC
View FAA NOTAM → - SECURITY6/3032 2026-07-10 21:00Z – 2026-07-15 03:59Z SFC–400 ft
Philadelphia, PA, Friday, July 10, 2026 through Tuesday, July 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 22
- 0 ft AGL at event
- 4 kt ground speed
- 0 fpm vertical
- Approach stability 55/100
- 4 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- METAR KCDW 180453Z AUTO 00000KT 10SM BKN025 OVC033 24/21 A3006 RMK AO2 SLP181 T02390211 402780194
Flight context
- UAL681
- United Airlines
- B39M
- KEWR → KCDW
- 2026-07-10 21:27 UTC
- KCDW runway 22
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