Unstable approach — N2QG

N2QG (Marina District Development) was operating from KBZN to KJXN on 2026-08-07. SkyMeter detected a low approach-stability score at Jackson County Reynolds Field (KJXN) on runway 07 at 01:31 UTC. Trace data at the event: 2108 ft AGL, 145 kt GS. METAR at the time reported 4 kt wind, 3 kt crosswind component, 9,656 m visibility. The approach-stability score rates the final approach against stabilized-approach gates (glideslope, lateral deviation, descent rate, and IAS) at defined altitudes. A low score means one or more of those were outside the normal envelope for how the approach was flown. The score is graded by guidance type, so instrument approaches (ILS or an aligned straight-in) are held to the full gate set, while visual and pattern arrivals are surfaced only when the score is clearly low. The score is advisory and observational, a deviation measure, not an assertion of an accident. Detection algorithm and known limitations: see SkyMeter methodology.

• HAZARDS6/8871 2026-07-27 14:00Z – 2026-08-09 04:00Z SFC–8,000 ft

  83NM N SPEARFISH, SD, Monday, July 27, 2026 through Sunday, August 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9566 2026-07-28 17:15Z – 2026-08-11 04:00Z SFC–10,000 ft

  33NM SW PHILIP, SD, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1471 2026-08-04 14:00Z – 2026-08-19 04:00Z SFC–9,500 ft

  33NM SW BROADUS, MT, Tuesday, August 4, 2026 through Wednesday, August 19, 2026 UTC

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/0460 2026-08-06 13:00Z – 2026-08-17 05:00Z SFC–400 ft

  Milwaukee, WI, Thursday, August 6, 2026 through Monday, August 17, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2488 2026-08-06 14:00Z – 2026-08-20 05:00Z SFC–13,500 ft

  28NM W AFTON, WY, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2755 2026-08-07 00:59Z – 2026-08-08 04:00Z SFC–12,000 ft

  10NM SE LIVINGSTON, MT, Friday, August 7, 2026 through Saturday, August 8, 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.

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