Long landing rollout — LXJ446

0Q3 · 17

2026-05-21 19:03 UTC· FLEXJET LLC, NURCON INC, CIAO AVIATION 750 LLC, IMMELT JEFFREY, · E545

▶ Replay 📊 Analyse

LXJ446 (Flexjet) was inbound to 0Q3 on 2026-05-21. SkyMeter detected a long landing rollout at Sonoma Valley Airport (0Q3) on runway 17 at 19:03 UTC. Trace data at the event: 0 ft AGL, 14 kt GS, 0 fpm vertical. METAR at the time reported 4 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)
  • SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

    BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

    SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/1501 2026-05-20 15:00Z – 2026-05-23 03:00Z SFC–6,000 ft

    50NM NE STOCKTON, CA, Wednesday, May 20, 2026 through Saturday, May 23, 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 17
  • 0 ft AGL at event
  • 14 kt ground speed
  • 0 fpm vertical
  • 4 kt wind
  • 3 kt crosswind component

Flight context

  • LXJ446
  • Flexjet
  • E545
  • 2026-05-21 19:03 UTC
  • 0Q3 runway 17

All events on this flight

Long landing rollout 19:03:00 UTC · 0Q3 runway 17 · 0 ft AGL · 14 kt GS
Long landing rollout 19:03:00 UTC · 0Q3 runway 17 · 0 ft AGL · 14 kt GS

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

SkyMeter · trace data observed via ADS-B· 0Q3