Long landing rollout — EJA278
KUDD · 282026-08-23 18:26 UTC· KOMA → KUDD· NETJETS SALES INC· E545
EJA278 (Netjets Sales) was operating from KOMA to KUDD on 2026-08-23. SkyMeter detected a long landing rollout at Bermuda Dunes Airport (KUDD) on runway 28 at 18:26 UTC. Trace data at the event: 65 ft AGL, 0 kt GS, 0 fpm vertical. METAR at the time reported 7 kt wind, 3 kt crosswind component. 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)- HAZARDS6/1462 2026-08-04 13:00Z – 2026-09-01 04:00Z SFC–15,000 ft
20NM SW PUEBLO, CO, Tuesday, August 4, 2026 through Tuesday, September 1, 2026 UTC
View FAA NOTAM → - HAZARDS6/3101 2026-08-09 13:00Z – 2026-08-24 03:00Z SFC–15,000 ft
24NM SW PUEBLO, CO, Sunday, August 9, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/3156 2026-08-10 13:00Z – 2026-08-24 04:00Z SFC–13,000 ft
20NM NE SALT LAKE CITY, UT, Monday, August 10, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/3679 2026-08-11 12:00Z – 2026-08-25 08:00Z SFC–16,500 ft
1NM NE OURAY, CO, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/3659 2026-08-11 13:00Z – 2026-08-24 03:00Z SFC–14,000 ft
26NM SW PRICE, UT, Tuesday, August 11, 2026 through Monday, August 24, 2026 UTC
View FAA NOTAM → - HAZARDS6/3712 2026-08-11 14:00Z – 2026-08-25 04:00Z SFC–8,000 ft
18NM SW PRESCOTT, AZ, Tuesday, August 11, 2026 through Tuesday, August 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/4085 2026-08-12 04:00Z – 2026-08-25 04:00Z SFC–13,000 ft
4NM W RICHFIELD, UT, Wednesday, August 12, 2026 through Tuesday, August 25, 2026 UTC
View FAA NOTAM → - HAZARDS6/4894 2026-08-13 13:00Z – 2026-08-28 04:00Z SFC–15,000 ft
8NM SE TRINIDAD, CO, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC
View FAA NOTAM → - HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft
13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/5463 2026-08-17 13:00Z – 2026-08-30 04:00Z SFC–13,000 ft
20NM NE SALT LAKE CITY, UT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC
View FAA NOTAM → - HAZARDS6/5937 2026-08-18 13:00Z – 2026-08-31 03:00Z SFC–13,000 ft
4NM W RICHFIELD, UT, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC
View FAA NOTAM → - HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft
13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/6728 2026-08-20 13:00Z – 2026-08-27 03:00Z SFC–14,500 ft
8NM N ASPEN, CO, Thursday, August 20, 2026 through Thursday, August 27, 2026 UTC
View FAA NOTAM → - HAZARDS6/7092 2026-08-22 13:00Z – 2026-09-04 03:00Z SFC–14,000 ft
26NM SW PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7115 2026-08-22 23:30Z – 2026-09-04 03:00Z SFC–13,000 ft
41NM E PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC
View FAA NOTAM → - HAZARDS6/7117 2026-08-23 11:00Z – 2026-08-29 01:00Z SFC–13,500 ft
30NM SW PUEBLO, CO, Sunday, August 23, 2026 through Saturday, August 29, 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 28
- 65 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 3 kt crosswind component
Flight context
- EJA278
- Netjets Sales
- E545
- KOMA → KUDD
- 2026-08-23 18:26 UTC
- KUDD runway 28
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