Long landing rollout — UAL681
KCDW · 222026-07-02 21:22 UTC· UNITED AIRLINES INC· B39M
UAL681 (United Airlines) was inbound to KEWR on 2026-07-02. SkyMeter detected a long landing rollout at Essex County Airport (KCDW) on runway 22 at 21:22 UTC. Trace data at the event: 0 ft AGL, 3 kt GS, 0 fpm vertical. Approach stability score: 36/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 7 kt wind, 6 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/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/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/0081 2026-06-26 04:01Z – 2026-07-04 03:59Z SFC–400 ft
New York, NY, Friday, June 26, 2026 through Friday, July 3, 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 →
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
- 3 kt ground speed
- 0 fpm vertical
- Approach stability 36/100
- 7 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- METAR KCDW 071153Z 00000KT 10SM CLR 04/03 A3010 RMK AO2 SLP198 T00440028 10050 20033 51007
Flight context
- UAL681
- United Airlines
- B39M
- 2026-07-02 21:22 UTC
- KCDW runway 22
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