Squawk 7700 transmission — WMN631

WMN631 (Jjj2 Holdings) was operating from KMTN to KMCI on 2026-07-01. SkyMeter recorded a 7700 transponder transmission at 14:33 UTC. Code 7700 indicates a general emergency declaration (e.g. engine, medical, smoke). A sustained transmission is normally accompanied by ATC priority handling. Trace data at the event: 12900 ft AGL, 335 kt GS. Approach stability score: 76/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 11 kt wind, 4 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY6/4120 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4125 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4151 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4155 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Riverside, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4157 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  PRAIRIE VILLAGE, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4162 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4206 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 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.

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