EJA928 (130r) was inbound to KPBI on 2026-08-05. SkyMeter detected a diversion to Castle Airport (KMER) on runway 13 at 00:21 UTC. Peak cruise altitude FL202, turnaround area near Mountain House, US. METAR at the time reported 0 kt wind, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/6491 2026-07-20 07:01Z – 2026-09-16 06:59Z SFC–1,499 ft

    Concord, CA, Monday, July 20, 2026 through Tuesday, September 15, 2026 Local

    View FAA NOTAM →
  • HAZARDS6/1795 2026-08-04 20:57Z – 2026-08-18 04:00Z SFC–6,000 ft

    27NM NE STOCKTON, CA, Tuesday, August 4, 2026 through Tuesday, August 18, 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 13
  • 0 ft AGL at event
  • 0 kt ground speed
  • 0 fpm vertical
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KMER 170055Z 36007KT 10SM CLR

Flight context

  • EJA928
  • 130r
  • C68A
  • 2026-08-05 00:21 UTC
  • KMER runway 13

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· KMER