Long landing rollout — EJA843

EJA843 (Netjets Sales) was operating from KLUK to KSNA on 2026-08-23. SkyMeter detected a long landing rollout at John Wayne Airport-Orange County Airport (KSNA) on runway 20R at 20:12 UTC. Trace data at the event: 72 ft AGL, 0 kt GS, 0 fpm vertical. Approach stability score: 72/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 8 kt wind, 2 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.

• SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft

  El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 Local

  View FAA NOTAM →
• SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

  Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

  View FAA NOTAM →
• 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/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/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 →
• SECURITY6/3628 2026-08-17 12:00Z – 2026-08-23 23:59Z SFC–400 ft

  SAINT LOUIS, MO, Monday, August 17, 2026 through Sunday, August 23, 2026 Local

  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 →
• VIP6/5889 2026-08-20 21:15Z – 2026-08-23 21:15Z SFC–4,999 ft

  Cincinnati, OH, Thursday, August 20, 2026 through Sunday, August 23, 2026 Local

  View FAA NOTAM →
• HAZARDS6/7114 2026-08-22 23:15Z – 2026-08-25 03:00Z SFC–14,500 ft

  26NM NE RUIDOSO, NM, Saturday, August 22, 2026 through Tuesday, August 25, 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 →
• HAZARDS6/7128 2026-08-23 13:00Z – 2026-09-06 03:00Z SFC–14,500 ft

  26NM NE RUIDOSO, NM, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• VIP6/6937 2026-08-23 20:07Z – 2026-08-23 21:15Z SFC–4,999 ft

  Cincinnati, OH

  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.

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